Don't have links anymore, but few months ago I came across some startup trying to sell AI that watches your production environment and automatically optimizes queries for you.
It is just a matter of time until we see first AI induced large data loss.
RCS is just stupid. When I was still building phones a decade ago we had some operators ask for it - but after reading the standards decided to just ignore it and hope it passes. Pretty much everybody did that, until google got interested - presumably because they figured it'd be a good way to get control of messaging on a lower level. As that's exactly what RCS is: control of messaging, and ideally the option to charge for it, just like SMS and MMS before that.
I wasn't quite sure what to think about this, so I've asked my local LLM. Seems it is fine.
Almost a decade ago there was a discussion how to draw into display buffers for Wayland. Everybody agreed on using Mesa GBM, nvidia wasn't really interested, but said they'd do EGLstreams.
As nvidia wasn't interested, and generally is a dick to everybody anyway Wayland development just progressed ignoring nvidia, and now they have to catch up to where all the other graphics driver were at already years ago. While ignoring most of the things those others learned, because they want to keep their own tiny proprietary island.
Just avoid supporting nvidias dickish behaviour by not giving them money, and eventually they might learn and change.
There were some rumours that he was pushing the commercial side too fast, potentially ignoring ethical issues. Given Altmans lobbying against AI regulation in the EU I find that plausible.
Since now apparently the investors won it proves that the special structure of for-profit owned by non-profit intended to keep them honest does not work - and we urgently need to have regulation in place, as self-regulation does not work.
For the usual candidates I either keep detailed notes, or make sure I can quickly find an earlier conversation (chat, email, whatever).
So in that case I'm then just answering "As we've discussed on 14.04. at 13:39, 17.04 14:30 and 20.04 at 14:15 already..."
They typically get the hint that when I'm capable of remembering in detail when we discussed it they maybe should make an effort of remembering what we discussed.
Somebody is pretty salty for no good reason. The maintainers own patch is nicer code than the suggested patch - and the change is small enough that there just isn't anything available to guide the reporter to a better solution without wasting everyone's time.
I'd probably have added a thanks for debugging effort into the commit message myself - but "please accept my patch because I want to have code in the kernel" is a very stupid thing to say, and the maintainer offering a suitable problem to fix is more than I'd have done in that situation.
I'm running both physical hardware and cloud stuff for different customers. The problem with maintaining physical hardware is getting a team of people with relevant skills together, not the actual work - the effort is small enough that you can't justify hiring a dedicated network guy, for example, and same applies for other specialities, so you need people capable of debugging and maintaining a wide variety of things.
Getting those always was difficult - and (partially thanks to the cloud stuff) it has become even more difficult by now.
The actual overhead - even when you're racking the stuff yourself - is minimal. "Put the server in the rack and cable it up" is not hard - my last rack was filled by a high school student in a part of an afternoon, after explaining once how to cable and label everything. I didn't need to correct anything - which is a better result than many highly paid people I've worked with...
So paying for remote hands in the DC, or - if you're big enough - just order complete racks with racked and pre-cabled servers gets rid of the "put the hardware in".
Next step is firmware patching and bootstrapping - that happens automatically via network boot. After that it's provisioning the containers/VMs to run on there - which at this stage isn't different from how you'd provision it in the cloud.
You do have some minor overhead for hardware monitoring - but you hopefully have some monitoring solution anyway, so adding hardware, and maybe have the DC guys walk past and inform you of any red LEDs isn't much of an overhead. If hardware fails you can just fail over to a different system - the cost difference to cloud is so big that just having those spare systems is worth it.
I'm not at all surprised by those numbers - about two years ago somebody was considering moving our stuff into the cloud, and asked us to do some math. We'd have ended up paying roughly our yearly hardware budget (including the hours spent on working with hardware we wouldn't have with a cloud) to host a single of one of our largest servers in the cloud - and we'd have to pay that every year again, while with our own hardware and proper maintenance planned we can let old servers we paid for years ago slowly age out naturally.
I just took my cat to the petrol station to give it a try, and have to report that not only does she not have any indicators like this, she also was vehemently opposed to being refuelled and scratched me up badly.
It's been shown over and over again for the last two decades that you can't build a reliable archive on platforms outside of your control. Stuff like Instagram can be useful for trying to draw traffic to your own platform - but you always should treat those platforms as throwaway content.
In Germany it's also mandatory - but learning the language at school unfortunately doesn't necessarily mean you can speak it. LucasArts adventures contributed more to my language skills than my first English teacher. I'm always shocked about the lack of English skills in a lot of Germans when I'm back visiting. Rather surprisingly one of my uncles born in the 30s spoke pretty good English, though.
We're now living in Finland - me German, wife Russian, we each speak to the kids in our native language, between each other English. So they're growing up with 4 languages.
It's quite interesting to watch them grow up in that situation. When learning about a new historical figure my daughter always asks which languages they spoke - and few weeks ago she was surprised someone only spoke two languages. So I explained that some people only speak one language - she gave me a very weird look, and it took a while to convince her that I'm not just making a bad joke.
That's some great thinking in a stressful situation.