FranOntanaya

2006 subway accident in Valencia had a similar context, they used the FAP system, cheaper than ATP, which would have prevented the accident.

That was often a "mechanical" issue with analog captions. You could send only 4 bytes of caption content with each frame (and some were control codes) and the display only fit 32 characters per line. If several people were talking over each other, talking rapidly, or there were on screen texts that needed captioning too, they'd make compromises to try and fit everything.

Then, because of legacy broadcasts and backwards compatibility, that carried over well into the 2010s.

Being slower than a compiled language is not saying much for an interpreted language. But it's slower than PHP which is a closer comparison, and PHP has had JIT for six years now.

Captioning and subtitling has taken a direct hit from AI tools, but about half of it is from clients severely reducing their quality standards.

Back in the early 1990s the widely referenced BBC guidelines required 99.9% accuracy overall. Nowadays it is assumed that viewers will be used to and understanding about frequent errors, and that you don't need to take pride on your product to keep them in your platform.

I feel back in the day you still saw ads that were kind of creative and there was a certain glamour around being the one brand with the best ads.

Current ones are outright unpleasant, the "make the viewer feel bad about something" kind or directly spam folder level of scammy. Nobody takes pride anymore on their advertising.

Always puzzled me how much money can possibly be in trying to optimize sales by some low digit percentage points, versus how much is sacrificed for it.

This is one angle of the productivity story. You don't have any sort of plausible deniability covering all these bugs, test cases etc. when they are comprehensively discoverable by tooling. It's like having typing bugs on a strongly typed language with static analysis, you just can't make a lot of excuses.

So that's one measure of extra time that will be spent on every single feature, where in the past things would've been rolled out in a more barebones state. It's better overall, but is it going to be perceived as being more productive?

I'm kind of happy though that <marquee> still works. It's deprecated for a reason, but reminds me of when the web somewhat tried to have a language of common elements rather than being just a sandbox of styles.

It's already painful now.

I hope whoever registers index.php uses that power for good.

If you have a deadline for starting a fire you won't be happy looking at an unskilled person holding a lighter under a bunch of wet twigs.

The more we go in that direction we closer we get to reinventing frameworks in a more compute heavy way.

It just so happens that there's no framework (outside silos) for many specific tasks, and AI is the workaround to surface those patterns.

You really felt productive doing anything with Visual Basic 6, at least until things slowed to a crawl because it wasn't so performant or it was held back by the typical Access database. You didn't need 200 hours of YouTube tutorials about the front-ed UI framework du jour to get going.

A caveat is that in this case third parties have plenty logs of the bad behavior.

If classic companies were coming out with CCTV recordings of someone's employees breaking padlocks and rummaging warehouses any CEO would be in damage control mode, rather than silent.

But you may be still trying to teach kids that are going through a form of withdrawal for several hours because it's not managed outside school.