What about people with disabilities, physical or mental, who can't get out, old people with no family or family who doesn't care? In theory it would be great if everyone got some attention and socialized, in reality a lot of people in society are forgotten, no one wants to talk to them.
For some of these people even talking to a robot would likely be a huge improvement in quality of life, and that's just talking. If said robots could also help them out in real life, sort of like a personal assistant, that would be even better.
Social people will be fine, I think this tech is far more important for lonely people who for any reason don't get to socialize much (if at all), this is especially common in older people. These people might not have any other alternatives.
Edge user here. For one, chromium is faster than firefox, any given page will load about 20% faster, another reason is edge workspaces feature, I've grown to like it, which seems to be some sort of chromium feature that everyone bakes in weird ways if at all, and I'm still running ublock origin on edge without any funky bypasses.
Then there's a fact that a bunch of sites/webapps straight up refuse to work on firefox and they ask you to install chrome or something. And lastly chromium the most popular browser flavor and as a web dev it helps to see pages through "the same eyes" as my users/customers.
That's about it, the only reason I use firefox every day is their superior picture-in-picture player, chromium one is waaay inferior.
If you check openrouter there are a tons of providers selling API access to open source LLMs at a fraction of the cost compared to SOTA models (codex/claude). What model you're serving and what kind of platform you serve is a big factor.
I'm no expert but I think eventually we'll have even more specialized ASIC like machines with models burned into them and a that will absorb a chunk of the market, similar to what happened to crypto mining but to a lesser degree since the work isn't as static.
Before they removed it, I was using groq Kimi K2 model for a chat bot in small community site/chat. It was really good, seemed to have incredibly vast general world knowledge and the fast speed (400tok/s if I remember right) meant that chat users got a response instantly which was a much better experience compared to other SOTA models at the time.
These are business class laptops, there's no dedicated GPU. Where are you're going to utilize this high refresh rate? I'm pretty sure 99% of the time the integrated graphics would be working hard to churn out 120 frames of static views.
I bet the vast majority of people would be perfectly happy to have 60hz display, longer battery life, and save a few bucks at the same time.
Funny bonus anecdote: I reinstall my OS in december, only a few weeks ago did I realize it wasn't set to 144hz but 60hz, since I was busy with work since and didn't play any games I did not even realize.
Damn, what a flashback. I forgot about that game, it was quite something for its time. I remember the gesture spell casting system not working very consistently, but it was still a ton of fun.
I found the opposite when I went through a split keyboard phase and did Colemak-DH layout. As far as english goes I found that a lot of words had a smoother "flow" when it comes to finger location.
In the end I went back to a regular qwerty because my WPM on split keyboards/colemak-DH was considerably worse even after many months of practice.
I can't find information on what would happen to Chromium, would google need to hand it over too? That's probably more important than the fate of Chrome.
Wasn't aware of "Claude Dev", just tried it out, it's pretty cool. I had this simple node chatbot with a handful of features but it was all just one big script, asked it to split up the logic into separate files that would make further dev work/maintenance easier.
5 minutes and 30 cents later it came up with a decent folder structure and split everything up nicely, even cleaned up a bunch of messy code into some helper functions. Vanilla claude API could've probably done all this as well, but it would've been much more of a hassle. I'll definitely be playing around with it some more!
A big issue that these articles never mention is that using browser dev tools to debug CSS becomes a huge pain with tailwind. It also makes it harder for community to create custom themes/user scripts for your website/app since targeting specific elements becomes incredibly hard when no class names exist.
The PPI ratio for 32" 4k with no scaling is actually pretty good (at least to my eye, since it's similar to my previous 24" 1080p, 27" 1440p monitors). If we can agree on that, then the solution is to just move the monitor closer to your eyes, 3rd party monitor arms help with that.
For some of these people even talking to a robot would likely be a huge improvement in quality of life, and that's just talking. If said robots could also help them out in real life, sort of like a personal assistant, that would be even better.