3 ms·
Honestly JavaScript is not so bad but I could see multiple things evolving web development pretty significantly. 1. WebAssembly is cool but can't currently rep
by BinaryIdiot 10y ago
Honestly JavaScript is not so bad but I could see multiple things evolving web development pretty significantly.
1. WebAssembly is cool but can't currently replace JavaScript. Now if the standard could get in gear and go a bit faster and work towards being the Java Bytecode / MSIL of the web? Then there would be zero reason to NOT develop in whatever language you want that compiled down to that. Yeah there is transpiling to JavaScript but that is more of a hack than anything; if you have to debug in an environment without source maps then it sucks hard core the further away you are from JavaScript.
2. The separation of HTML, CSS and JavaScript kinda sucks. CSS can do a lot but not everything, your HTML structure needs to be a certain way for some CSS to work correctly so the two are tied far more together than in the past. I'd like to see something eventually combine the two because let's face it, beyond basic things I almost never see the "swap a stylesheet to make everything different". Seems more of a novelty than a practical thing in my opinion.
3. I think the upcoming web component standards are going to make module web development a ton easier but the standards have been moving at a SNAILS pace. Poylmer's polyfills are great but don't cover everything and is extra overhead. When browsers support these natively it's going to make things so much easier to create 1 component that can end up being used in any web application regardless of framework.
- ktRolster 10y agoI think the upcoming web component standards are going to make module web development a ton easier but the standards have been moving at a SNAILS pace. Yeah tho, I'd rather have them go slowly and do a good job, because we're going to be stuck with it for a long time.