721 karma · joined April 3, 2013
It just so happens that there's no framework (outside silos) for many specific tasks, and AI is the workaround to surface those patterns.
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.
Northern launches are done sometimes for high inclination orbits since they reduce the need to maneuver from an equatorial orbit.
Visual Basic 6 wasn't even too esoteric, it could have happened already if it was a thing.
It's going to change a lot the internet we knew, unless somehow we managed to agree on a common high quality dataset repository.
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.
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.
Myself I have an e-ink reader but almost always take a paper book on the subway. It's still better quality print, not fragile in any way that matters, and I don't have to think about charge or aging electronics. I only bring the e-reader for manuals and such that change too often to be worth the paper cost, but still miss the old coding manuals with their ad-hoc page sizes, the spatial sense of where the information was in a book was part of the memory anchoring.
People use either some flavor of W3C's Timed Text or WebVTT instead (and it was already a pain to get them to drag their feet into them and drop the old analog broadcast formats). Now, here's the thing. WebVTT isn't radically different in format and features to (A)SSA and it has plenty of styling options... but, once again, a lot of platforms and software are dragging their feet to support them.
So the industry has been sloooowly doing the right thing moving to the W3C standards (not a huge fan of Timed Text myself, but it exists for a reason), but only with the most basic and safe features. Which are also about as many features you get out of plain speech to text output, so it's even easier to make that decision.