Stefan Baumgartner

Hey hackers, Shuttle ( https://github.com/shuttle-hq/shuttle ) & Stefan Baumgartner ( https://fettblog.eu/ ) are hosting a free workshop titled "Rust for Javascript Developers". So far, more than 800 hundred curious peeps have signed up, and we encourage you to do the same! :) Rust Linz organizer Stefan Baumgartner will take you from project initialization to deployment by rewriting an Express.js based chat application that uses web-sockets into Rust, using the Axum framework & shuttle. By doing so, he will highlight use cases, benefits, pitfalls, and major differences to other programming languages. All of that, in just 3 hours. More info & signup can be found here: https://workshop.shuttle.rs/

Hello hackers, Shuttle ( https://github.com/shuttle-hq/shuttle ) & Stefan Baumgartner ( https://fettblog.eu/ ) are hosting a free workshop titled "Rust for Javascript Developers". Rust Linz organizer Stefan Baumgartner will take you from project initialization to deployment by rewriting an Express.js based chat application that uses web-sockets into Rust, using the Axum framework & shuttle. By doing so, he will highlight use cases, benefits, pitfalls, and major differences to other programming languages. All of that, in just 3 hours. More info & signup can be found here: https://workshop.shuttle.rs/

After using TypeScript for the past couple of years, I've come to see it as simply another "embrace and extend" maneuver by Microsoft carve off a chunk of JavaScript mindshare, preying upon the naïveté of less-experienced developers who've fallen for the "static typing is safer" myth. TypeScript's decision to disallow JSDoc within .ts files [1] for example doesn't contribute anything positive to my impression of this syntactic pocket-protector. While the type hinting it provides is useful, the tradeoffs of added complexity, tool dependencies, and cross-compiling phase have made it more trouble than its worth in my opinion, particularly since tooling to provide code introspection and type hinting has already existed for a long time [2]. For new projects, I've begun using straight JSDoc, which is working beautifully with minimal setup [3] and provides all of the benefits I ever found useful about TypeScript, while remaining completely unobtrusive otherwise[4]. 1. https://github.com/microsoft/TypeScript/issues/20774 2. https://ternjs.net/ 3. https://medium.com/@trukrs/type-safe-javascript-with-jsdoc-7a2a63209b7… 4. https://fettblog.eu/typescript-jsdoc-superpowers/

Reminds me this old meme : https://fettblog.eu/wp-content/uploads/2020/node-modules-meme.png

JSX is just syntactic sugar for React.createElement [0]. This means that I can write any valid JS I want in there. For example, if I use a functional programming library with a match statement, I can have that in my JSX, I don't need to adhere to what the templating authors came up with. [0] https://fettblog.eu/jsx-syntactic-sugar/

JSX is syntactic sugar for JS[0]. C++ and ASM (actually, _which_ ASM?) are different languages. [0] https://fettblog.eu/jsx-syntactic-sugar/