it's a real shame no one warned us this would happen when a bunch of corporatists and opportunists wrested the term "open source" from the advocates of true freedom in the late '90s.
The day I stopped giving half a fraction of a shit was the day Google served me malware in an ad. It was one of those fake "Download" buttons on a very popular open source tool. I wonder how many people have been harmed by that.
> 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.
It pretends to be. But in reality it's always been a VC honey pot.
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.
you have a lot of faith that Big Balls hasn't been compromised. Because surely none of them are using their personal smartphones or laptops and are following strict access protocols. Seeing that they are so so careful with everything else they've been doing.
I feel like this is a bad episode of the Twilight Zone.
The deal still has me scratching my head. They tossed out the brand name and logo. Elon already had the X name and domain. For much less than $44B I feel like you could clone Twitter and come up with a strategy to acquire users. Hell, for $1 billion you could probably pay a good number of influencers to move to your platform. $44 billion is an absolute fuckton of money to kill Twitter and move those people to your pet project.
I know it's fashionable to use flatpak, Docker, etc. but I'd still rather not have 30 instances of Gtk running for every GUI app I decide to run. Consider that we still run on Raspberry Pi, etc.
> 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.
There was also Kahn, which was a similar competitor.
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.
EVs are the worst proposition for a car rental. When you rent a car, you're planning on driving it. Much more than the car that sits on your driveway and only takes you to work and back every day.
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.
I can understand why people wanted that, and the benefit of doing that.
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
you can have ten comments about the name of a variable, but no one bats an eye at a new npm package introduced. Also, devs that wrote code that Google depends on can't pass the leetcode gate check to get a job there.
You say all this after recent documents were revealed about Facebook intercepting and analyzing Snapchat encrypted traffic via a man-in-the-middle conspiracy.
I had a mk7 and it is the best interior + UX I've seen in a car. Everything is as simple and ergonomic as possible. The volume adjustment is a knob, with soft rubber knurling and indents for feedback. It's not some awful feeling smooth afterthought that you see on certain Toyotas or Hondas. It's not a push button (beep beep beep beep) you find on old Pioneer stereos from the '90s. It's exactly what you want to adjust the volume. The AC is similar. Heated seats are a button with 3 LEDs indicating high/med/low. Everything just makes sense.
And then VW got cheap and greedy. The mk8 is almost the complete opposite of what the mk7 was.
There are lots of reasons why Half-life was a success. You shouldn't discount stupid luck, as well. Their first iteration was awful, as mentioned in the YouTube video. They essentially had to start over with a "cabal" and pull the game together with the good scraps of work they had already done.
Here's a more detailed article on the cabal process (starting on page 2):
Now, game development is inherently waterfall. You work for years and built up to this huge release. Nowadays you might have some agile processes embedded into milestones, etc. But fundamentally it's all leading to a huge waterfall.
That's important. Because what agile does, today, is that it turns autonomous developers into cogs of a large machine. But Valve's "cabal" was entirely free to do whatever they felt best. Gabe Newell probably had final say and input, but ultimately the group had flexibility. The developers had full system awareness. They weren't pulling Jira tickets off a board like a blind man in the elephant parable[1]. They knew how the pieces fit because they put them there. And if the pieces weren't fitting, they had the authority to make them fit.
Perhaps more interesting is how the story of Half-life can be viewed through The Mythical Man-Month[2]
> When designing a new kind of system, a team will design a throw-away system (whether it intends to or not). This system acts as a "pilot plan" that reveals techniques that will subsequently cause a complete redesign of the system.
Their cabal has a bit of overlap with the "surgical team" concept and usage of formal documents. The rest of the employees did nothing while this group operated. Thus, they reduced manpower that actually allowed them to move forward. Slow is Smooth, Smooth is Fast (from the US Navy Seals). Most companies do the opposite. They crank up the number of employees to hit deadlines, which creates more bugs and more work.
Interestingly, Amazon's move to ad placement seems to coincide with how terrible Amazon's search is. It's a pay-to-play free-for-all wasteland. Not too dissimilar to the SEO wasteland of Google search.
I'm sure internal politics plays a large role. Managers knee-capping each other and so forth.
But there is another way to look at it. A company of Google's size will not be satisfied by a "small" $10M ARR business or perhaps even a $100M ARR business. It's not going to move the needle. The needle being, effectively, Google's stock price.
There are two ways to move the stock price: increased profit or decreased spend. Increase the pie or stop the number of people eating the existing pie.
All of those projects had more value in being ritualistic offerings to the stock gods. Much like the unreleased Batgirl film had more value being a tax write-off than selling for market value: https://en.wikipedia.org/wiki/Batgirl_(film)
But no, don't let me stop you from justifying your hatred of certain people through the ever-convenient excuse of "evolution".