@JLarky right, thanks! that file actually is used on both client and server. haven’t found a good convention for those yet. because I want to force the dev to make a conscious decision whether it’s client or server or both. and I hate the word isomorphic :P maybe html.both.ts ?!
@JLarky Let me know if you have criticism (constructive or otherwise :P) Does the readme make sense? what question in the motivation section is unanswered?
@jarredsumner@thdxr Not sure what that Go code does, but I’ve found Async Iterables to be the least painful way to deal with this kind of stuff in JS. You can define yourself a few helper functions like map, filter, drain, etc.
@RyanCarniato Doesn't mean it's never a good idea, just that frameworks need to be worth it (and yes, people are probably over-using React for cases where it's not worth it).
@RyanCarniato One more thing: I get the notion that frameworks get between the deverloper and the browser's native api insofar that it's yet another layer of abstraction that the dev needs to learn and debug when things go wrong.
@stratechery@benthompson One thing not taken into account in the article is that semiconductor-based LIDARs might arrive, which would then also follow Moore’s Law.
@msimoni That size of landing legs would be more than slightly heavier. Also that size of a rocket is probably not easy to move. Finally, faster turnaround to next flight.