Our mission is to introduce you to new technologies and show you little tricks in certain areas of programming. We also want to produce small tutorial series, which are not intended for beginners but rather for the average programmer. So this channel is for coding nerds who like programming and want to educate themselves further.
No, it has been 2 years and it hasn't happen and there is no sign is going to because WASM has no access to the DOM. WASM has been and will be used for calculations and other heavy processing stuff, but rendering will continue to be our headache with HTML+CSS+JS
Very good points of course. If it does not get direct DOM access, it won't replace JS. Bur what if it did not need the DOM? Gonna drop another video soon. And yes I just did an ad in a comment. Capitalism won.
As a data analyst, I am thrilled of the possibility of sharing my interactive shiny dashboards with colleagues without having to jump through the hoops of shiny app hosting.
Lots of things to be excited about with WASM, but I wish folks would stop saying things like "use any language to write UI", implying that Rust/C++/etc. would be a good choice for UI development, but that's really not true. High-level, relatively "loose" languages, like TS/Swift/Kotlin are ideal for UI work; no one's going to write UI in Rust/C++.
Those SO surveys are a joke, JS before html/css although one is mandatory for any website the other not, standalone node servers won't make it for it. Shell scripting that low although mandatory as well ? So they do everything from GUIs and never login to any remote server ? Even serious communities are now just a bunch of inexperienced folks.
One use-case I'm surprised people aren't talking about much: Compiling your models to WASM so you can use it on the frontend and the backend. That's something I'm trying to achieve rn with a fullstack app I'm building. My backend being written in C++ and my frontend being Typescript with Angular. So I have a model that I'm sending from the server to the client which then just displays it. And when something gets changed there it would get sent back to the server. So I'm using the same model on both the server (backend, written in C++) and the client (frontend, written in Typescript) for which I have to copy the same exact model. Why not just compile the server-model to WASM and simply use it from within the client-code? I could have the exact same code/algorithms for (de-)serializing (for sending it via HTTP) the objects which means whenever I change the server-model I just have to compile the WASM binaries and the client would be up-to-date as well. Maybe I'll learn about some problems with that, as I'm just about to really implement that. :D The few issues I found so far were that I couldn't just pass a JS Array for a C++ std::vector and Typescript definitions, which I wish could be generated while compiling the WASM binaries (Which is already possible for Rust WASM, so probably just a matter of time someone creates a good solution for this). I think JavaScript/TypeScript and it's frameworks are great for what they're supposed to do, which is all kinds of UI stuff. While I still prefer languages such as C++, Rust, C#, Java, ... for writing backends. I don't really like the "one language for everything" idea. But for that it'd be just a cool way to use WASM to save some time.
Hello, I'm just one year old in the programming world @ 28 years of age. I would like to learn more about how can I utilize C++ to create web pages or servers and stuff since I'm kind stuck with it for now while I try to practice problem solving. Do you have any specific recommendations? Most resources I found are not beginner friendly at all..
This was great, that last example got a tad confusing haha… I think I’m missing some TS fundamentals, I didn’t know about the whole looping over itself
What would be funny is Javascript developers trying to make a Webassembly in C/C++. I grew up with Turbo Pascal and C++, fled for my life to higher level languages eventually leading to Javascript when it finally grew up with the V8 engine and became a language actually worth using. Now I'm back to C/C++ working in embedded environments and talking myself out of smashing my brains into the wall daily. Now I'm hoping for faster progress in Rust in the embedded environment so I can flee from these horrible languages again. Yes, I know they're the foundation of most software, blah, blah, blah. I just wish something as basic as passing a method as a callback, because people have mixed C++ code with C libraries wasn't such a rediculous pain along with the many other various sink holes of insanity one can trip into while doing even some of the most basic coding that holds you up forever googling through various other people's attempts to climb out of their own similar sink holes of insanity. Just saying, more than anything else, it would be super funny to watch a Javascript developer learn C/C++. I used to know it, forgot a lot, but I at least had an understanding of the pain involved when I waded in. Younger coders who've never experienced an old style low level language with all its pitfalls and idiosyncrasies would just be walking into a bandsaw.
Will never take over. Too many plug-in like things and there will be major security holes. Java still future. You simply can’t get rid of a Titan without taking all the minions down that protect it, with it. It’s as simple as that. It’s like trying to get rid of the federal reserve. Or Amazon. Can’t be done without a worldwide takedown with enough backing to replace it. Too far gone.
Nodejs is pushing garbage to the server(with very few exceptions like Graphile). WASM is pushing high quality code and tools out to the browser it just needs to get good hooks into the DOM to fully deprecate JS.
I'm getting really excited about the prospects of browser-native game development in the future. We're way past the days of Homestar Runner now. Trogdor 2023 could be a banger with Web Assembly.
In its current state, it's a game changer for a tiny subset of work that is done on the web. if you're asking front end devs to switch from a dynamically typed lower learning curve language to something that is designed for systems (Rust C++) just to make the button point to a new URL so you can gain a couple ms of performance (That you don't need) you'll lose that battle - cost of switching is massive. it's cool you can do heavy computation in browser, but I'm not seeing a lot of use cases outside of games and CAD
The benefits of using WebAssembly is that you can write frontend apps using backend language like C#. Give Blazor a try if you want to see an example. It’s a joy to work on.
You get job security if you learn niche skills. Building anything that can be done on WordPress or other low-code tools is bad. Its also the ultimate cost saving tool if you don't mind losing a few ms. My friend got $1million dollars from venture capitalist for a WordPress site. Then he hired a few low salary WordPress guys from south east Asia to do their thing. The bankers, especially older ones, don't know web development and it shows. I just think he's so freaking lucky and makes me angry I took the time to learn web development.
Beacuse new stuff isnt gonna immedietaly start being used by big corporations my guy. And you dont learn webassembly, you learn a launguage that you then compile to webassembly
My prediction: TypeScript, a JavaScript's Super Set, will replace it as the W3C standard in the near future and for a long time (2 to 3 decades), while it slowly migrates to AssemblyScript, a TypeScript like compilable language, unless C# community, which is a way more mature language and fairly similar to JS, decides to implement the Frameworks and Libraries for it to lead the WASM Revolution. Only time will tell.....
