BigJono
Joined 10 years ago
Joined 10 years ago
Completely offtopic for this thread but I can't be the only one that would find this hilarious if it wasn't being said in earnest in every thread.
The only thing that is clear is that measuring programming is just as impossible as it has always been. In all my years of projects they've either been resounding successes or gone down in flames. The difference between good and bad is a difference in kind. Most of the bad ones didn't even know what the hell they were building and built the wrong thing.
Like, the entire idea that some omniscient manager is looking at a thousand timelines and pondering over whether to pick the $11.5M successful one or the $9.5M successful one is literally laughable. Half of them are going to make the Hindenburg look like a bit of a whoopsie and the other half you would lock in sight unseen without a second thought.
If you actually haven't used social media recently then I get why you'd be confused, because back in the day Facebook had a chronological timeline of people you specifically added in. The way a modern social media recommender algorithms work is completely different. If you, for example, say "I want to hear everything that Bob has to say" by "subscribing" to Bob or whatever, you "might" see when Bob says something, or instead you "might" see Mary's post from the other side of the world that has some strangely aggressive opinions about someone the billionaire platform owner happens to hate.
Social media companies have decided by buddying up to the US administration that they get to decide what everyone around you sees or hears. If a couple of billionaires decide that they don't like phyzix5761 you might just get lynched by an angry mob. That's not gonna do much for your freedom, in-fact it's kind of the opposite.
I can't really tell how you'd even use this. Is it supposed to be some sort of micro-optimisation thing to do with how HTML is parsed (now you can download chunks out of order, presumably with some performance gains since it's browser native?).
When I saw the title I was hoping it was going to be a very simple React-like API for constantly updating parts of the DOM with maximum performance since the browser devs are now involved. It doesn't look like that's what this is at all. And all these years later I'm still wondering why browsers aren't implementing an API like that when it's been obvious for over a decade now that real-time DOM updates are a vital browser feature that needs to be performant, and that developers vastly prefer a declarative model to a procedural one. Why after 15-16 years are we still building 100 versions of the same abstraction in user-land to turn Element.append into "refresh these elements when this data changes"?
That felt like an indicator to me. I only switched to Linux a year or two ago and haven't mentioned it to her once, so she got the idea from somewhere else, and had enough impetus from whatever she disliked about Windows to actually go through with the change. If I was in marketing at Microsoft I'd be shitting myself over that, assuming Windows even still fits into their long term plans somehow. It's one thing for 100,000 techies to preach Linux across the web, but if random normies start using it without fanfare, that's real change.
More unserious and unmaintained projects at 400k a pop. Sick.