488 karma · joined June 27, 2018
Thanks for sharing this.
Porqué no los tres? CEOs pursuing yet another vacation home, under-educated consumers that lose their minds over 'saving' 1c ("$5.00" too expensive "4.99!" OHH THIS ONE!!), and regulators either with a private-sector agenda or who have no teeth because Congress is politically compromised.
There's more than enough blame to spread around.
It's only because it costs them exactly zero dollars and cents that they feel they can get away with bullying anyone they want.
In fact... hear me out. It might be that, those that own the paid private parking lots in high traffic areas exacerbate the parking issues in contested areas, creating pressure on free parking areas; then they lobby to put parking meters in those free areas because "the city needs all the money it can get" (ehh, it shouldn't, it doesn't), and voilá, no more free parking anywhere.
Just a thought.
ABSOLUTELY this.
Advertisements use MY bandwidth, MY compute resources, MY time, MY space, to harass me by showing me things I have zero interest in, all the while interrupting what I'm doing, distracting me, and then having the gall to tell me "but think of the poor publishers!!".
They have caused the appearance of an industry that's a pox on all ("influencers") who behave like society owes them the space, time, attention and deference that for whatever reason they think they need.
And for a cherry on top, it makes everything more expensive because WE pay for all of it.
Someone saying "how hard can it be" is kind of a flag that they have zero idea of how hard it is or isn't.
I want my 10 minutes back.
I would build it once for whatever required architectures are needed, build wheels for them, amd use those for packaging up the final apps that need deploying (through docker, k8s, whatever).
https://pip.pypa.io/en/stable/cli/pip_wheel/
The package should be installed first, then create wheels from all of them, finally upload them all to a repository for storage.
Publish a module as a wheel if you want to be able to use pip to install it in your servers, or anywhere really.
Once you've built out your virtual environment you can build your docker image and push it to a registry.
Your helm chart should include references to docker images that are getting deployed to a kubernetes cluster, among other entities that need to be built out for your app to work.
Those are all different layers of the deployment, independent of each other.
If someone prefers 1 over 2 (or viceversa), they don't understand what they think they know.
"There should be one-- and preferably only one --obvious way to do it."
That is different from "there's only one way of doing it" in so many ways that it's not even funny.
Myself? I consider them ephemeral: I create my Makefile with a 'venv' target to delete/rebuild the virtual environment in case of changes. Some do take longer to rebuild, but with a global pip cache it takes much less time to rebuild once it's been done the first time.
Hardcoded paths and symlinks? Not a problem, I know that virtual environments don't travel; and since they're ephemeral if I need it at a different location I can always rebuild them.
Do you have an example for your third paragraph?
And I've done the last one, converted all packages to wheels, uploaded to an artifact server, and used those for production deployments.
I'm curious, really; not bashing you for having troubles with it, but I don't understand the aversion given my lack of blockers when using them.
I don't know where you came by such a notion; Shamans, "Wizards", witches, "wise women/men", are usually shunned from society such that they tend to live near the outskirts of towns or cities, nobody really wants to live close to them; and when "bad things happen" tend to be the first ones to get blamed for it; then they also are commonly used as scapegoats for whatever political, economic or religious effort some corrupt officials try to push.
That doesn't sound very societal top-tier to me.
We're definitely not witches or wizards, at most we are scholars or [specialized] craftsmen. "Knowledge workers" if you will. Not as unlikable as the wise folk that live towards the edge of town, and not as at risk of getting tied to a post and lit on fire because the bishop believes we commune with unclean spirits.
Never again.
That second factor needs to be separate from the originating authenticating service, not that it has to be on a single device hidden away kept in a safe, or on your wrist, or in your pocket. It could be a single device [a server] running bitwarden and you're viewing it through a browser on your <whatever>.
Not everyone wants to follow every single recommendation from a data security perspective, and it becomes an anti-pattern when laymen start using workarounds to not have to comply with the safety recommendation of the week.
Once you get rid of the noose, it's no longer a hassle.
For everyone going through this situation, please do a little bit of homework and read up on the capabilities of whatever alternative you're going to pick, and make sure that your data is yours and under your control, and you can back it up in a readable format.
PS: There's something utterly contradictory announcing his passing on >Twitter< of all places. He's already rolling in his grave.
Implying "tail -f $LOGFILE" is akin to tmux reattaching to a console is a stretch.