3 ms·
I agree, I've basically gone the same path as you, just ended up with a different stack to solidify behind, but same idea. > YMMV but the point is, it's everso
by diggan 2y ago
I agree, I've basically gone the same path as you, just ended up with a different stack to solidify behind, but same idea.
> YMMV but the point is, it's everso tedious and unsettling to those involved trying to figure out what the next thing to focus on should be.
I think it would all be fine, if people could just accept they're are part of this turning wheel, but instead they'll kick and shout that "No, but it's different this time, this time we really found the silver bullet" while you continue to look at them changing from HypedThing to HypedThing, repeating the marketing pitch while running into new walls.
I'll get jumped but whatever: Currently this is happening with for example TypeScript, where some people are so into it, they don't see it as just another "Compile to JS" language that will eventually be replaced by something else once the hype wheel starts turning yet again.
- TeMPOraL 2y ago> they don't see it as just another "Compile to JS" language that will eventually be replaced by something else once the hype wheel starts turning yet again. In case of TypeScript, they might be right - given its peculiar positioning and staying power, as well as indirect effects from resurgence of popularity around type systems (Rust, type annotations being leveraged in LLMs, etc.), it wouldn't surprise me if at some point, browsers (read: Google) decided to start supporting it as first-class language. A decade down the line, it might be that JavaScript will end up being compiled down to TypeScript instead of the other way around.
- diggan 2y ago> it wouldn't surprise me if at some point, browsers (read: Google) decided to start supporting it as first-class language. A decade down the line, it might be that JavaScript will end up being compiled down to TypeScript instead of the other way around. If WASM still exists in some flavor at that point, but TypeScript ends up being the target for JS instead somehow, we can assume we probably have other, way worse issues in the world to deal with, because something clearly went wrong.
- rounce 2y agoI think it’s more likely that TypeScript’s features will just be subsumed into Ecma262 with some adjustments to support backward compatibility. IMHO part of TypeScript’s staying power has been that the changes it makes are more conceptually radical compared to the useful but relatively lightweight sugar of Coffeescript for example.