Yeah during the reddit exodus, people were recommending to overwrite your comment with garbage before deleting it. This (probably) forces them to restore your comment from backup. But realistically they were always going to harvest the comments stored in backup anyway, so I don't think it caused them any more work.
If anything, this probably just makes reddit's/SO's partnership more valuable because your comments are now exclusive to reddit's/SO's backend, and other companies can't scrape it.
It is, but it probably shouldn't be any more. WebP has good support everywhere now and is slightly better than JPEG and PNG combined. (Better lossy compression than JPEG, plus transparency support, and better lossless compression than PNG). But even WebP is considered lame these days compared to the new crop.
E.g., JXL (JPEG XL) is much better WebP and is supported by everyone except Google (which is ironic since Google helped create it). Google seems to want AVIF to be the winner for the new image format, but not many others do.
Anyway, until the Google JXL AVIF hissy fit is dealt with, at least we've still got WebP. It's not super great, but it's at least better than JPEG and PNG. A lot of web developers are stuck in their old JPEG PNG mindset and are being slow to adapt, so JPEG is still hanging around.
After reading the article (and others), I think this is giving him too much credit.
He was the BBC studio controller at the time and pushed to have the matches broadcast in colour. The BBC ignored him for years and then suddenly changed their minds without reason, and in 1967 they ordered David Attenborough to do the next Wimbledon in colour.
However, the colour of the ball wasn't changed. Balls remained white even while being broadcast in colour.
Yellow balls had actually already been used since the 19th century, but not consistently, and not at Wimbledon. After a few years of tennis matches being broadcast in colour, the ITF (without David Attenborough's involvement) conducted a study and found that flourescent yellow balls were easiest for viewers to watch, and so they started being used at Wimbledon starting in 1972.
The last chip was manufactured 3.5 years ago and the last serious user was probably several years before that. Obviously no one's running Itanium with modern hardware.
But just because the hardware isn't modern, doesn't mean the software can't be modern. Tonnes of people run the most recent Linux kernels on 15 year-old laptops, so why not 10 year-old servers? Itanium is only for the hobbyists these days, but so what? Hobbyists have done a good job of ensuring modern Linux can run on 40 year-old 68k. Itanium can theoretically be done, too. It's just a question of whether the hobbyist community has enough of the right people that can actually maintain it.
Hm, he and his wife are getting on in years. If they want a son, they should probably get on that right away.
It's a cool idea and the example they gave actually seemed pretty neat.
I'd (somewhat perversely) love to see this feature tried in a terminal emulator. ANSI does actually define escape codes for switching to alternative fonts (ESC [ 10 m through ESC [ 19 m) though I don't know of any software or even term drawing library that uses it.
Article reads as propaganda
More like advertising. I'd put down a pretty big bet that Life360 sponsored this article and probably wrote a fair chunk of the copy, too.
I'm a university professor who uses whisper.cpp for video lecture transcriptions, so I'll chime in here. The thing about whisper.cpp compared to pretty well every other option is that whisper.cpp is really really really really really good. Like the accuracy is almost always completely 100% (and that's just on the 'medium' model. The 'large' model is probably even better)
There is only one problem with whisper that I've found, which is that if you use a low quantization model (I believe I'm using a 4-bit quantization model), whisper can get stuck into a "no punctuation mode" if that happens your transcription will suddenly start to look like this there will be no punctuation or capitalization it's quite annoying once it gets into this mode it can't get back out again
The way to get around that is to segment your audio. I use ffmpeg's silence detector to segment the audio whenever there's a >1 second pause in the audio (so that I don't accidentally segment in the middle of a sentence or the middle of a word). Break the audio up into roughly 10-minute segments and you should not see no-punctuation mode happening.
The other nice thing about Whisper is it'll tag fragments with confidence level and starting- and ending times. I use the confidence level so that I can quickly jump through low-confidence transcription points to see if it made a mistake (though it usually doesn't). I use the starting- and ending times to automatically generate an .srt subtitle file. Then I use ffmpeg to bake in hardsubs for the students.
So far it's been working very smoothly and quickly. Even on my crappy old GTX1060, I can get subtitles at about 2-3x real time. And with almost no manual intervention.
What advantages does it provide
ZFS, mostly. There are some smaller peripheral things (like much better manpages), but these days the big one is probably ZFS. Zero licensing conflicts allows it to be an integral part of the kernel.
Except for the fact that testing began before release, this is totally accurate.
To be honest I'm more concerned by
language-humor. Like not even saying what kind of humour, just any type of humour at all. Jokes are for adults only!