News for hackers. Stuff that matters.
Re:Ask HN: Did TeXmacs' doubly misleading name hold it back ... by b33j0r on Friday December 30, 2022 @10:13AM (#34185730)
If this is a problem, no one told Javascript
Re:Ask HN: Did TeXmacs' doubly misleading name hold it back ... by marssaxman on Friday December 30, 2022 @11:18AM (#34186429)
It was a problem, but everyone was forced to put up with Javascript anyway, and here we are...
Re:Ask HN: Did TeXmacs' doubly misleading name hold it back ... by b33j0r on Friday December 30, 2022 @11:47AM (#34186762)
Not disagreeing but here’s another lens. Applies to TeX as well.

“Java” in javascript kinda meant “modern computer programming” to the audience, in a very very inaccurate and zeitgeist-hype-train way.

People who thought “oh yeah, I’ve heard of java, and scripting sounds easier than programming,” looked into it.

ECMA wasn’t a thing yet, but it might have sounded like a skincare product to those same ears, or something that required college. The buzzwords worked.

Re:Ask HN: Did TeXmacs' doubly misleading name hold it back ... by dragonwriter on Saturday December 31, 2022 @06:08PM (#34201677)
> ECMA wasn’t a thing yet

ECMA is much older than JS.

ECMAScript wasn’t a thing yet, I think you mean.

Re:Ask HN: Did TeXmacs' doubly misleading name hold it back ... by b33j0r on Sunday January 01, 2023 @12:44AM (#34203959)
You are correct, my friend