Why can't it kill javascript?
Why can't it kill javascript?
Falling into your wing while paragliding is called 'gift wrapping' and turns you into a dirt torpedo pic.twitter.com/oQFKsVISkI
— Mental Videos (@MentalVids) March 15, 2023
Why can't it kill javascript?
Falling into your wing while paragliding is called 'gift wrapping' and turns you into a dirt torpedo pic.twitter.com/oQFKsVISkI
— Mental Videos (@MentalVids) March 15, 2023
That's not its purpose. Its a compliment to js
WA's use case is for performance sensitive code. But not everything is performance sensitive. WebGPU should help as well.
>But not everything is performance sensitive
Everything is performance sensitive. Do you enjoy waiting for a website/webapp to load for 8 seconds when it could have been instant?
A website that doesn't use js at all is very quick to load. But site owners want to pile more features onto theirs. They have no self control.
JS frameworks have been created by big tech to suppress competition. They pay to gaslight everyone to use them.
So. JavaScript is slow. Website creators want features. Webassembly is fast. Use webassembly to create those features. What if we could have a nice and easy to use language that compiles to wasm and is fast.
It isn't so much that js is slow so much that dom manipulation and the network connection is slow. Those two things would still be involved even with WA.
js on it's own is reasonably fast. It gets JIT compiled now days. Try running some tests from a terminal. But web browsers have every ui feature known to man included.
> implying a bunch of pictures in boxes couldnt be generated in miliseconds if done by competent people
no this stuff is plenty fast, the problem is there's too much of it.. especially on sites like your video.
if everyone had gigabit internet, the "too much of it to DL fast" would turn into a "too much of it doesn't use multiple cores" issue.
either way their sites are bloated pieces of trash that could look and function identically with 1/10th the code if there was some optimization shit going on but there never is.
Javascript needs to start compiling and stripping out shit that is unused per page
performance-sensitive means micro- and nanoseconds instead of milliseconds. nobody is talking about seconds. the reason websites don't load instantly isn't JS
>the reason websites don't load instantly isn't JS
yes, the reason is either network requests or poorly written code. JS in itself is fast. V8 can shuffle an array with 1000000 elements in <10ms. if you think JS is the reason a website takes 8000 ms to load then you're just computer illiterate
>V8 can shuffle an array with 1000000 elements in <10ms
Who gives a shit???
The thing that slows it down is GC
you're talking out of your ass. I just refreshed twitter.com and there was a single GC that took 20ms, even though the website took a few seconds to load.
>he unironically thinks js is the bottleneck
cope
because it is disabled by smart users who realize it's only used for coinminer ad malware like
describes
also, because it can't even do GC, it's a fucking rust wet dream
>rust wet dream
Yes it that why they're so keen. No GC inside WA means you can implement your own preferred mechanisms.
no, it simply can't do it
rustfags didn't think GC was important so it's not even considered
it has to be rewritten from scratch to handle GC which is what all the popular languages use
therefore, it's stillborn
wasm will never have any relevance and will be considered a legacy tech in the future
Yeah, rustfags can built their own GC collector and not need to mess with the js one that's so dirty to them.
>rustfags can built their own GC collector
which is laughably bad
it's not even embraced by rustfags at large because GC is antithietical to them
their language will never take off because of their own stubborn intolerance, and wasm is going down with that ship
so basically, you're saying wasm only works with rust and rust programmers are fine with that, because they are zealots
correct
wasm works with many languages, not only rust. But maybe wasm isn't the tool you'd want it to be.
>wasm works with many languages
it can't GC, which means every popular language is eliminated
Java, Python, Go, it can't even do Javascript and it's the backend of Javascript, how fucking ridiculous is that?
wasm is a complete and utter failure because it was created by the same exact homosexuals who created rust
and rust homosexuals don't even care enough about wasm to NOT write fucking coinmiers for it
they have no honor
they just do whatever they can to fuck end users
that's a key reason why they fail
Java, Python and Go would have a harder time to be used on to top js than wasm because js is more complex. A JavaVM could be built on top of wasm without too much trouble and get decent performance that way.
The wasm spec was worked on by epic games for their unreal engine to use. wasm is better for heavy number crunching in real time without GC penalties than js. But WebGPU will be better for that. I agree that rustfags have no honor.
graalvm can run wasm
wasm cannot run graalvm
I can tell you now it could. Maybe not with such great performance, but it would run. A whole pc can be emulated on top of wasm, as can docker.
You can compile a GC in WebAssembly. Do you even know what WebAssembly is?
I don't think OP understands it either.
RAII that they use is a form of GC. It's just different to how langs like c# or java do it. But I don't think wasm should be tarred with the same brush as rust. Wasm isn't the greatest thing in the tech world, but it is a useful to have. As I said, WebGPU should be good too.
>Its a compliment to js
t. Tc39 shitter.
> cope
JS is on the way of Flash. You only need 1 (ONE) major JS player to adopt WASM (my bet is on Angular, which is Typescript based. Typescript is Microsoft, and since Blazor has no fighting chance, the best MS can do to stay relevant is a Typescript to wasm compiler.), and JS is done for.
> iTs a mAlWarE vEctOr
So is JS. That's why you use a good adblocker, a DNS filter and CommonSense(TM) 4 Anno Corona.
Oh Microsoft.
Instead of translating the MSIL generated by their dotnet langs to WASM directly, they instead chose to port the fucking dotnet runtime itself and run your code as a DLL on the said runtime.
>Instead of translating the MSIL generated by their dotnet langs to WASM directly, they instead chose to port the fucking dotnet runtime itself and run your code as a DLL on the said runtime.
this is... a joke right? say sike nigga. what's the point of having yet-another-memey-do-everything-IR if you don't even use it?
Here's from microsoft's own demo
https://devblogs.microsoft.com/dotnet/use-net-7-from-any-javascript-app-in-net-7/
https://pavelsavara.github.io/dotnet-wasm-todo-mvc/
Here's the runtime
https://pavelsavara.github.io/dotnet-wasm-todo-mvc/dotnet.wasm
Then the whole host of standard libs like
https://pavelsavara.github.io/dotnet-wasm-todo-mvc/managed/System.Collections.Concurrent.dll
and
System.Linq.dll
System.Private.CoreLib.dll
System.Private.Uri.dll
System.Runtime.dll System.Runtime.InteropServices.JavaScript.dll
System.Text.Encodings.Web.dll
System.Text.Json.dll
System.Text.RegularExpressions.dll
And finally your code here
https://pavelsavara.github.io/dotnet-wasm-todo-mvc/managed/TodoMVC.dll
Afaik their excuse is that DLLs are smaller than WASM modules.
But the real reason is that .NEET sucks at AOT.
nobody wants to compile shit just for a website
>Why can't it kill javascript?
You literally can't load a WASM program without using JavaScript.
Not in a browser in any case, yeah.
JS is de-facto standard webshit language. It's good to have standards, and JS isn't the worst of languages. It doesn't change the fact that WA is based af. I managed to run my old C++/OpenGL game in a browser over a weekend with Emscripten.
I agree with you anon
because there is a superior option
That's still javascript
but better
Slightly better
bandaid on the asphalt
*much better
doesn't fix the biggest problem with js
which is... ? enlighten us please
gc
why is it bad?
because it's slow
It's an OO shitter language with a craptastic typesystem and doesn't even have OO staples like operator overloading. It's pretty obvious to anyone who's actually used JS what's wrong with it. Tc39 shitters keep making the language even more OO and retarded to add insult to injury.
>craptastic typesystem
which is exactly what TS fixes
>OO staples like operator overloading
you don't need this for client side web apps, you OO tard
TS does not fix the fundamental flaws of javascript's typesystem, it just adds a compile time strength to them.
>nooo operator overloading is le bad
ok, so tell me how you do a key lookup using an object as a key in js. oh wait, you can't because record/tuple proposal has been in committee hell for years now and something this basic is too advanced for js shitters like you.
you can use Map you retarded homosexual, is supports reference types for keys
>js shitter doesn't know
just stop.
>key lookup using an object as a key
sounds like you just do not know JS
thanks for proving you have no idea what is being discussed.
Clown.
Its purpose is to replace performance-critical parts of JS with a much faster language like C++. It was never truly meant to replace JS, except perhaps for something like full-stack data scientist positions or something.
Because they still haven't given it DOM access.
well, technically it has access to DOM. you can call JS from WA, so you could get access to DOM that way. kinda lame, but should work.
it can't link to webidl. it's really that simple.
also reminder that js is completely inconsitently retarded now. you can't add a BigInt to a normal Number without explicit casts, but you can still do the gay ass NaN batman shit that everyone mocks JS for
>but I can get play doom in the browser
You literally can't run a wasm code without Javascript.
Because switching the VM context from JS to WA has a terrible overhead.
Rust programmers are excited to use WASM, a platform where memory management barely matters and most of their language's memory safety mechanisms don't semantically mean anything.
Right now people just use either a simple bump allocator or some sort of arena allocator and let the VM clean up the rest.
It's almost like there is more to rust than "muh safety."
The only decent WASM toolchain right now is Emscripten.
Then you have shit like PyScript because python and javascript aren't slow enough on their own.
>running a binary (yes I know it's an intermediate representation like Java) in your web browser
What a genius idea. It's almost as if Java Applets and Flash taught people nothing.
Once again evil and malicious and irresponsible people prevent humanity from progress and great things. We can never have nice things; for every nice thing could be a weapon
As opposed to running a turing complete scripting language that has been proven multiple times to be able to make their underlying virtual machines do bad-touch, no-no ouchies to victim's machines? What makes you think using this same(ish) js virtual machine and allowing you to bypass most of the higher level fluff, like the compiler, and runtime features is somehow going to make it more or less unsafe? Who are you people and why are you so retarded?
It's far easier to pull up Javascript source and look at what it's doing than it is WASM. You can never recover the actual source of WASM as it can be compiled from a number of languages and the bytecode representation is absolute AIDs compared to obfuscated JS which can easily be parsed by ChatGPT at this point.
Because it's slower than JavaScript, so what's the fucking point?.
WA works alongside JavaScript not without it