Web Assembly and Go: A look to the future
Problem: The Javascript landscape is too fractured and complicted. There&#x27;s too many different frameworks and technologies that can be used to write front end code. There&#x27;s no way I can be expected to know all of them.<p>Solution: Let&#x27;s make it so anyone can write front-end code in any language they want!<p>Personally, I just don&#x27;t see how that makes sense. It seems allowing all these different languages to be used to write front-end code just creates more of a mess. Before you at least knew a front end project was probably written in JS, now... who knows?<p>Maybe WASM will catch on and what it means to be a front end dev will change to be more language based, but that seems like it would create its own problems. Most devs I know that want to write in Go and C don&#x27;t want to fuck with HTML and CSS.<p>For the record, from what I understand WASM offers from pretty big performance boost over JS and I think that is really where it will shine. I think the ability to bring really high performance applications into the browser will be the bog selling point of WASM.<p>That being said, I don&#x27;t foresee a future where every brochure website and online restaurant page is written in C or Go and compiled down to WASM. I think people who are excited for WASM because they don&#x27;t want to learn Javascript are going to be really disappointed in it&#x27;s adoption rate over the next few years.<p>IMO, WASM is an awesome new tool to add to your tool box, but not a technology that is going to change the development landscape as a whole.