FranOntanaya

Maybe Clevo, since they are more of an OEM producer for other brands meaning they don't control all the eyes on the hardware all the way to the sale point, i.e. to sneak things in.

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.

I'd say the main difference is that you couldn't take a device with good media capabilities, good and cheap-ish networking and lasting battery everywhere. Laptops, netbooks, tablets were a tad too bulky, lasted only a few hours unplugged and mainly wifi, and mobile internet was not all that great.

Templated code generation is ancient. It's just that the latest "template engine s" are very comprehensive.

LLM is spicy memoizing, so it can potentially be faster than a tool call. But people will spend a month tweaking and testing to ensure they have the level of determinism they need, which means it's more expensive, and that they should have used actual memoization in the first place.

I always wonder when do they stop considering the outer layers part of the star and not relatively dense solar wind soup. Nobody says Earth has 7000km radius, even tho there's traces of exosphere past 500km.

Not really, the actual issue is delta V, launching near the equator requires less fuel because you are getting all the benefit from Earth's rotation. Mass is almost everything for rocket launches.

Northern launches are done sometimes for high inclination orbits since they reduce the need to maneuver from an equatorial orbit.

I still remember the "Visual" craze of the 90s when everybody was going to be able to make applications without writing code.

Visual Basic 6 wasn't even too esoteric, it could have happened already if it was a thing.

Troubleshooting SCC captions in the digital era is quite an experience. Haven't gotten any request for them in a couple years though.

Blows my mind that several trillions in I still see so much LLM text with no stylistic awareness.

"There Will Be Blood" but it's 2026 and Plainview's child is AI.

After a decade and half we had to restrict our public side and reorganize our old TED content because scrappers were really hungry for assorted captioned videos. If you have anything of value for training you get eaten alive if you stick out, it's like wearing short pants in the summer tundra.

It's going to change a lot the internet we knew, unless somehow we managed to agree on a common high quality dataset repository.

Well 2010 PHP and the frameworks at the time were still going through the 5.x desert journey, and the prospects weren't entirely clear with the cancellation of PHP 6, so you wouldn't fault your 2010 self for not trying to push some Drupal/Joomla/Magento to that scale.

Kinda took until Facebook showing off Hacklang in 2014 for people to believe in getting more canonical programming features into PHP and make it more performant. So it would have been a good decision if one could predict 10 years into the future, but nobody can.

Some specialized models may end solving themselves by helping fit the problem with the appropriate regular algorithms/formulas, which are a million times more efficient. So they are probably less attractive to dump money on. As of currently they still benefit from expressing lots of patterns that nobody bothered formalizing.

I think it's partly because of where they come from to the problem.

I have education/experience in both literature and coding, I have a pragmatic starting point when approaching text while also being able to recognize stylistic oddities, so I get to be the guy editing out AIsms sometimes.

But I've helped other people copywrite where their environment was all org-speak and academic writing, and AIsms don't really stand out in that case. AI is effectively "doing the right thing" writing the way it does for those tasks. Even tho the right thing is often a bad thing.

A lot of what would be the top "reference" works aren't even that good either, they were a successful marketing phenomenon or had cultural or social relevance at their time. So, you can get a lot of bad prose going by a number of somewhat logical, externally measurable parameters.