3 ms·
For a lot of "usual" webdev, any reasonably modern language will do. Even modern JavaScript will be fine. Something like C# would have been way better, though,
by jfkebwjsbx 6y ago
For a lot of "usual" webdev, any reasonably modern language will do. Even modern JavaScript will be fine. Something like C# would have been way better, though, but we cannot change that now.
However... software development has become a mess of slow technologies and abstractions one on top of the other.
Some people are working routinely in a text editor that is behind three operating systems: the VM/hypervisor, the usual operating system (Windows/macOS/Linux) and then a browser instance (which is like a operating system now). Then add all the drivers, libraries, frameworks etc. that go in-between.
While I don't like that WebAssembly is yet another abstraction, at least it is a chance for a resurgence of system programming languages and to proper software engineering...
- tracker1 6y agoWhy can't you use C#? .Net Core (upcoming .Net 5) are pretty decent to work with. I'd still rather use node for the most part though. I have been playing with Rust, but not sure about how good an idea it is for the front end yet though.
- jfkebwjsbx 6y agoWell, you can compile the .NET runtime into Wasm, send it to the client and run C# on top of it, but then you are adding yet another layer.
- tracker1 6y agoI didn't have the impression the discussion was a web context. In which case if lean straight js/react or rust/yew
- swebs 6y agoPretty sure the parent comment was talking about client side.
- LandR 6y agoYou can use C# on the front end now with Blazor. It's pretty new though so I don't know how good it is yet.