3 ms·
Ah, so TS types are basically only available at compile time? Does that make the "standard" way to do things to have both TypeScript types AND some alternative
by zapzupnz 8y ago
Ah, so TS types are basically only available at compile time? Does that make the "standard" way to do things to have both TypeScript types AND some alternative form of type information in object prototypes/classes for runtime use? That seems a bit redundant to my ignorant eyes, complicating what was already a complicated dance.
- patates 8y agoYou cannot deal with Javascript without a "complicated dance". I like JS, and TS even more, but facts are facts.
- zapzupnz 8y agoI wonder if that's one of the things that makes wasm appealing, being able to write for the web without having to learn the awkward dance.
- patates 8y agoI think it is. But I also think a significant amount of that awkwardness comes from the DOM and all the backward-compatible cruft that comes with it. I'm ready to be positively surprised but I'm not sure how much of those stuff you can abstract away.
- zapzupnz 8y agoMaybe. For me, the DOM is far from the oddest thing to deal with. That's just fine.
- z3t4 8y agoThe intermediate programmer likes to write smart and complicated code, but after a while you will go back to basics, and start to appreciate simplicity and convenience, and write code similar to a beginner, but without the bugs and inefficiencies (including your own time).
- patates 8y agoI didn't mean it was to be liked. I meant that I like it in spite of the unnecessary complexity.