3 ms·
This reply alone makes all the effort I’ve put into my stack worth it. Thank you :)
by theobr 5y ago
This reply alone makes all the effort I’ve put into my stack worth it. Thank you :)
- crate_barre 5y agoYou’d have to explain, I was certainly being vitriolic, but I hope HN hasn’t lost its poor taste for theatrics and poetry - granted, as a moron, I believe everything I’ve said. Edit: is it so much to ask to not want to write code that looks like gibberish? I don’t care what the benefits are, it looks like gibberish code. Can type safety be accomplished without gibberish code? I think in Java it goes something like this: Function (String s, int num) Ok, I’m on board. You Typescript bastards are writing gibberish code and I don’t care who disagrees.
- bmeski 5y agoI agree that this stuff is getting out of hand. The most important part of all that code is the part in the prisma calls, which would handle all the caching and request logic. The rest is literally just making sure you name your stuff correctly and render it. If you want actual type safety for your large client-side app, use rust/wasm. If your client side app is small, why do any of this?
- theobr 5y agoPoint me at one fast moving “large client side app” that uses Rust via WASM over Typescript and I will move my entire company over
- techpression 5y agoNot Rust, but Figma (which everyone seem to love) is using C++ and Web Assembly and they seem to be moving quite fast. I guess it’s not the entire stack but still, seems viable for them.
- theobr 5y agoThey use those things for some very specific math-heavy transforms and rendering - still all Javascript for the UI. I’ve used WASM for some ffmpeg-in-browser stuff too. The belief in WASM as a method to build client-facing software is an amusing self own. There is literally no production examples because it is not production ready for dom-heavy stuff.