I think I’ll always be listening to to him 🤣 First time I’ve seen him and very impressed

He’s the best

Why should he? It's neither a trend nor the future

Neither was Brazil. 😢

@@MC_DarkMaster Nor was the AI trend a year ago, so it's impossible to predict a trend. Also your point of view is subjective, for you it might not be the future, but for some it is.

@@gabrielilie4460 Your point is subjective too :) I think it is not possible to list all tiny projects that may become the next big thing. And actually HTMX is not something new. Knockout.js did almost the same thing 2011, Intercooler the predecessor of HTMX was also founded in 2013. So the idea behind that is alreay more than 10 years old. And it did not succeed.

First they ignore you, then they laugh at you, then they fight you, then you win.

Well in this talk he doesn't talk about any shortcomings from the different languages at all. Do you have an issue-number from github for us that we can upvote?

more than a couple of years for sure, they are working on preview 3 now which is about async

because some people want to generate html in the server and send that for some reason. they believe your server(s) generating html for thousands of users would be faster than doing the rendering on user's device, because it "might" be underpowered. not to mention the complexity behind it all because delineating the "static" parts and "interactive" parts and maintaining it (in your head, documentation etc.) is hard. unless you are a content heavy website, client side rendering is fine, fast, simple, and cheap! in the case of astro, if you have a content heavy website with very little interactivity here and there (like a newspaper that has dynamic visualisations) it is just fine, astro manages the delineation between what is static and what is dynamic very well (islands architecture) so that is the most promising one. but for most other stuff, rendering html in the server is just a losing proposition.

yeah exactly...every day a new fancy library / language / framework or feature everybody has to use...everything running in a docker container and managed by dozens of pipelines :/

but then you look at the network tab, how much javascript is being shipped to the browser your head will go nuclear.

WASM is not ajax. Similarities?? Yes all computer software work in scope of possibilities brought by hardware and networks, so nothing revolutionary should even be expected. And if you paid attention he marked evolutions (no even revolutionary) to be introduced on their time, and he had that time axis there. You're missing the message. It's not about revolution in web. It's about evolution over the time.

soy development

If you go from anything to anything (different)....it will look like a confusing mess at the start because it is not what you are use to seeing. Blazor is elegantly designed.

​@@PortalUser2elegant is the last word I'd used for blazor. Blazor can't even decide what it is. It is at least two separate frameworks.

You're not wrong @JeffreyRennie

Ok boomer. Meanwhile js goes brrrrrr.

Valid, but then how do we do logic and DBs, what would you suggest?

@@giorgos-4515 Sorry... are you saying we need JavaScript for logic and DBs? Two things that existed long before JS, both off and on the web?

@@Sammi84 Man-buns make me go LOL.

@PerryCodes Html itself is not enough that's for sure, but for interactivity and doing the actual processing(fetching from an API) you need JS.

Sadly without any comparable async/await. Like calling multiple different other apis concurrently without waiting for one after another

@@MC_DarkMaster I agree. But there is something great about templating html the way php does it. But it is true that it has its short comings. I wrote my own framework for bun that captures this early php vibe but still gives access to the js ecosystem and the js language features like promises and async await. That way we get the best of both worlds.

Is this seriously just the SSR grift from a few years ago? 27 minutes in

He spent the last half of his talk discussing WASI in apparent total ignorance of its many failed antecedents

It's kind of amazing that someone who apparently works for MS isn't aware that 'ecosystem bridging' is very much a failed idea in the bytecode VM world. Of all the useful things WASI does that is not one of them.

A decent internet connection is out of reach 90% of people in low- and middle-income countries and around 2.7 billion people - roughly one-third of the global population - remain unconnected to the Internet.

@@semikolondev for 99.99% companies its not target audience - its hard to make money in such countries. In developing countries internet is on par or better than EU\US. Fast internet will be there when they become viable market

The real question is the beginning of the end for writing JavaScript. The current state of affairs is a absolute mess. Why should I have to try and write + manage some class in JS, and then on a wing and prayer figure out to have the save class server side? (heck, the data types from JavaScript to server side code does not even match 1 to 1). With these new technologies, then I can write pure server side code, and if that code needs to run client side, then not only can it, but it by-passes JavaScript 100% and is native browser code (wasm). This finally marks the end of having to grab 30 different JavaScript libraries and THEN trying to cobble all those client side frameworks with sever side code. Gee, need a toast message system - yup, go find another JavaScript library and inject even MORE messy JavaScript libraries into what already has become a mess of epic proportions of tying to inject 25 different JavaScript libraries into that browser. The issue not really only about reducing bandwidth, but is about a clean coding environment, where I don't have to adopt anything more then a nice clean server side coding language (say like C#). The potential to by-pass all that JavaScript mess and attempting to load + send all that JavaScript library code to the browser is the greatest promise of these new frameworks. Why send a bunch of messy HTML markup + JavaScript to render a drop down box? Why not send some tight and clean native browser code to the client side that then displays the drop down box? We not there yet, but these new emerging technologies will once and for all get rid of the horrible dance between client side code (JavaScript) and server side code once and for all.

@@Albertkallal it is the beginning of the end of everything but javascript. We will keep all the other languages in a little wasm box and orchestrate everything with javascript.

@@spirobel2.0 Those little bit of JavaScript parts will be added automatic, and you not be reading or writing JavaScript code when the dust finally settles here. The simple matter is this attempt to put a round peg in a square hole (JavaScript playing nice with server side code) been a bad dream and experience for all of us. It what we have, and it is the current state of affairs as to what we have to deal with now. But, in short time, we all going to dump JavaScript, and write nice clean pure server side code, and it will do all the dirty work of sending bits and parts to the client side - including that of having such code run in the browser. As this video shows, what is around the corner is frameworks that figure out all the bits and parts for you, and being able to code out say a nice toast message in clean simple pure server side code? I can't wait...... Right now, all this wiring of JavaScript and trying to call web end points is a mess, and a costly development approach. Trying to have 2 vast different languages (Sever side and client side) play nice with each other? It's fast going away. The end result will be a VERY clean and simple approach to writing code, and building web applications. I can't wait! So, will some JavaScript exist? Yes, it will, but it will be very limited, and YOU the developer will not see, nor write that JavaScript anymore....

What that's not true?

node_modules.

The fastest platform and amazing languages - C# and F#