Speaking of the early 2000's, man, Aqua was such a good design. I appreciate the nextstep paradigm and design, but Aqua was just so futuristic, in a good way.

Those tools are better than vanilla agents by dedicating expensive human time on evaluating and fine tuning models. You can also build various integration, management and reporting features to add value. If you freeze model progress today, or 12 months ago when most of those companies started, it's a viable business I think.

But any gains you make on the first part will be lost to newer models, and the 2nd part is not as valuable when llms allow people to build fairly complicated features quickly.

I don't if worthless but all those companies have very limited time to gather customers and at least make themselves valuable for an acquisition

Even if this purchase causes 100 new hardware startups to be funded tomorrow, nVidia is perfectly fine with that. Let's see how many survive 5 years down the line

It was added like 3 years ago which was probably a bit too late, not even sure why it's not the default. (File size?)

The worst was Pandora, which did recommendations based on breakdown of musical instruments and elements in the song. It did what it aimed to do pretty well, only it was a bad idea. It gave you a lot of uninspiring music that sounded like a bland copy of something you actually liked.

Spotify's recommendations are not super awful, but definitely feel closer to Pandora's style. I wonder why is the result like that even though I'm sure they train their model based on listening history.

My personal maybe somewhat "stubborn old man" opinion is that no node.js orm is truly production quality, but if I were to consider one I think I would start with it. Be aware it has only one (very talented) maintainer as far as I recall.

Like if you take React's server components, it has a ton of problems and gets excessive focus from react devs, but fundamentally I can agree on what's its trying to solve. I understand the need, even if i disagree in almost anything else regarding it. I still don't know what the css in js phase was about.

Genuinely asking, what other software company did something like this back then? I'm tempted to say (tounge in cheek) FB was the original PaaS, but maybe im not old enough

Also if you have kids 0-6 you can't schedule anything relaibly

My parents bought an AMD 486 100mhz at the end of 1995, it was still a viable low end machine for that time but they paid as if it was a Pentuim. Had to somehow make it work up until 2001 with that machine. Don't know if I had a career in tech if I wasn't forced to tinker with it.

Most of the population still despises Israel, another revolution in Egypt and its a matter of time until there is another war. Now with western equipment for both sides!

At the same time, it is a major risk for browser compatibility. Despite many articles claiming otherwise, I think we mostly avoided repeating the "works only on IE6" situation with chrome. Google did kinda try at times, but most things didn't catch on. This I think has the potential to do some damage on that front.

Too many duplicated efforts, the wayland migration while needed was a complete mess, and actually the worst time I had using Linux since like 2005. This kind of complete breakage of user experience is unimaginable even in MacOS and it's hostile approach to power users.

I think otherwise it's going to continue being a frustrating two steps forward one step back.