1,483 karma · joined March 2, 2016
For example, despite all the problems of JS, new devs don't need to create a virtual environment and activate it all the time. They don't need to manually add lines to a requirements.txt, or pick a tool like poetry or pip env [1]
[1] Edit: ok they have to pick yarn/npm, but even those share a common file base formate - package.json
But one thing that needs to be acknowledged is how difficult it is to coordinate a space with so many stakeholders (eg. Conda and Anaconda for Windows), and how python got so engrained in the sys admin (installing tools with pip.) that undoing that is a monstrous task [1]
[1] The other day my ansible playbooks stopped working because packages that you used to be able to install globally with pip, should now be installed through the package managers (eg. jsondiff should now be installed as apt-get install pyton3-jsondiff). Exactly to push people to use virtual environments where you can better manage depedencies.
Yes, it makes it easier for new programmers: They can skip learning a dependency management tool like poetry, or pipenv. But then these things happen.
Blame the tutorial makers and the dependency maintainers, not the Flask team.
I've made a sourdough starter last summer that smelled EXACTLY like pear. It led to discover that there's all these sorts of Esthers that are named after their smell.
https://en.m.wikipedia.org/wiki/Ethyl_decadienoate
My chemistry and biology is highschool level, and sourdough baking (+ kombucha brewing) has been a super interesting way of exploring and being curious about those fields.
But that would mean any app with link preview (eg. slack, whatsapp, discord) would also be affected...
What if the operating system started to bleep out swear words from the microphone? Or blurring out obscene gestures?
Sure, make the software available on install, or even prompt it's configuration and opt in on installation.
But it's not and should not be the responsibility of the OS to apply effects or manipulate or alter the data of the hardware.
Apple still makes some of the best hardware I know, but gosh, the software they make...
I remember reading that it is possible to end up in situations where your environments can end up in the layers of the docker image. Also, you can read the secrets of a container with inspect, and apparently linked containers might be able to access other containers's secrets.
I think it was this article: https://snyk.io/blog/keeping-docker-secrets-secure/
Docker: Don't use environment for config, it's insecure
I like and use many of the patterns of 12 factor, but indeed some of these were written in the context of VPS, where environment is stable, secure and more constant (unlike containers, where environment might end up shipped in one of the layers). In the age of containers, this particular point has been a bit of a struggle for me. Docker secrets don't always play well, and you need to do some gymnastics to make it work.
Your terminal emulator is one of the most security sensitive things you use. Sudo password? SSH keys? logs? A lot goes through your terminal, so I think about 5 times before trying out new terminals.
Putting in the freezer would allow me to boot it and backup the data. Fridge was not enough as it was not cold enough to dissipate the heat of the device on boot.
As soon as the phone was out of the freezer it would die in about 30 seconds.
Saved all the vacation pictures this way
However, in Digital Ocean, by design, you can't restrict keys to certain buckets. Once you issue a key, it can access all buckets within your project, with all operations (list, read, delete) files.
The issue has been reported and is known for a long time. It's even the top voted "idea" in the company portal.
Posting this here in hopes to bring awareness of this issue.
But then I started asking around and people REALLY described visualisation as a vivid clear picture of things in their heads, almost like they are there. Like literally projecting the image on their brain as you're saying.
I now think I do have some degree of aphantasia. I can describe as having low RAM, so I cannot paint the entire scene. I am able to briefly visualise some details and aspects of a scene (usually as flashes, and I cannot sustain them), but never the entire scene. If you ask me to visualise a beach, I can have visual "flashy" perceptions of the sand or the waves, but it's extremely hard for me to put everything together in a visual manner. It's much easer for me to imagine the feelings, sounds, and smells of a scene.
4. A critical mass of community packages and open source ecosystem so you don't re-invent the wheel for non core things (eg. Javascript, Python, Rails)
And sure, you can get some performance improvements by rewriting things in those languages, at the expense of losing the entire python open source environment.
So I would need way more information about the previous system to take this even remotely seriously.
Python scales quite reasonably for most small to medium companies.
"One of the systems that ran on 200 Python servers now runs on four Elixir servers"
This alone is a major telltale.
A rest endpoint is likely handy to use across your application without having to replicate the same serialization over and over again.
Also many frameworks remove all the boilerplate for those operations (eg. Django class views), so creating one is a really good starting point.
Just have a api/v1/rest/ base path for modular well defined resources that can be used across your application, without breaking changes, or even shared to third parties.
Then have a api/v1/features for coupled endpoints that return non standard objects, and with a more flexible lifecycle.
Chances are you're better off having both instead of trying to cram all the use cases into one approach
* Check you're storing secrets safely and not in the code
* Run a automated security scanner to check for the OWASP top 10
* Confirm your endpoints have correct auth/permission checks, and that all debug flags are off
* Ensure databases are protected (eg. Not exposed to the internet or heavily restricted)
* Enable 2FA for everyone in the company and use a password manager
* Check what are the data protection laws and disclosure sla of your country
So you refuse to work with people who do not want to re-invent the wheel for a shiny new framework because it is "better"?
But there's also the recent findings inversely correlating myopia with amount of time spent outdoors (and even some reduction in myopia for people who start spending more time outdoors). So vision could just be a proxy for sedentism?