deckard1
Joined 11 years ago
Joined 11 years ago
But there was money to be made and the friends you thought were friends were just mercenaries with a shiv in their hand.
> medium you are consuming may not exist at all
I've realized that's not my problem. It's not like most of the internet is healthy anyway. It's psychologically manipulative and designed to keep you fearful, angry, spiteful, jealous, and above all, depressed.
Fuck Google. Fuck Meta. And fuck every single last person working for them.
I've stopped commenting here. I've made it a personal rule to only speak out against this tyranny and never talk about tech fluff, which is 100% of the front page of HN. I don't give two solid fucks about SQLite when the US government is throwing people in death camps in El Salvador.
This site is straight tech bro fascism. People are finally realizing that Elon isn't the guy his PR team created. He's not Tony Stark.
I feel like this is a bad episode of the Twilight Zone.
> aren’t these shared libraries a supply chain attack vector
Not any more than the apps themselves. If you're downloading a static binary you don't know what's in it. I don't know why anyone trusts half the Docker images that we all download and use. But we do it anyway.
I remember playing Duke3d over the internet. I was completely giddy as me and my friends all flew around with jetpacks on trying to kill each other with pipebombs.
The downside was that those games were obviously not optimized for internet latency and there wasn't much you could do about it. But I definitely had a blast.
But it doesn't help that Tesla is a tech company and their product is sold as a tech product. No one wants to buy a 3 year old used iPhone, either.
With that said, I also see benefit in having limitations. There is a certain comfort in knowing what a tool can do and cannot do. A hammer cannot become a screwdriver. And that's fine because you can then decide to use a screwdriver. You're capable of selection.
Take PostgreSQL. How many devs today know when it's the right solution? When should they use Redis instead? Or a queue solution? Cloud services add even more confusion. What are the limitations and weaknesses of AWS RDS? Or any AWS service? Ask your typical dev this today and they will give you a blank stare. It's really hard to even know what the right tool is today, when everything is abstracted away and put into fee tiers, ingress/egress charges, etc. etc.
tl;dr: limitations and knowledge of those limitations are an important part of being able to select the right tool for the job
Our industry is a laughingstock.
But no, don't let me stop you from justifying your hatred of certain people through the ever-convenient excuse of "evolution".