>year 2022
>javascript runtime runs faster than jvm
i just started learning javascript.
 Ape Out Shirt $21.68 |
 |
Ape Out Shirt $21.68 |
>year 2022. >javascript runtime runs faster than jvm
>year 2022
>javascript runtime runs faster than jvm
i just started learning javascript.
Ape Out Shirt $21.68 |
|
Ape Out Shirt $21.68 |
it's not compatible with Node.js
it's DOA
>Bun natively implements hundreds of Node.js and Web APIs, including ~90% of Node-API functions (native modules), fs, path, Buffer and more.
anon?
90% is not 100% and also those 90% are for sure full of bugs
no on will use it for serious
post nose
nose
The nose knows
He nose
it's not? the website and videos on it said it is. here i was planning on trying out Fresh + Deno. if Bun has a better ecosystem than Deno then it's pretty clear who's going to win in the runtime rat race.
i literally installed deno last night to try out fresh then deleted it once i saw bun's announcement. looks like bun doesn't have an edge service for it like deno does but since it's supposed to be node compatible i can just start using node then transition over once it matures.
deno's incompatibility with node packages seems like an oversight. did they really expect people to drop everything and start supporting yet another ecosystem? sure it might allow new devs to get their foot in early in the package ecosystem but their adoption is going to take a massive hit. have you tried out Bun yet?
>have you tried out Bun yet?
no. and after looking at the github issues page, i probably won't try it out for a few months.
>deno's incompatibility with node packages seems like an oversight
guess figured out themselves since nowadays deno has node compatible mode
its leeching off node ecosystem otherwise it wouldn't be a thing
THERES SO MANY FRICKING FRAMEWORKS IM FRICKING DONE
I THOUGHT AT LEAST NODE WAS THE FOUNDATION THERE'S NO WAY THEY'LL COME UP WITH ALTERNATIVES TO NODE RIGHT? OH NO WAIT DAHL HAS TO GO AND MAKE ANOTHER NODE BECAUSE HE DIDNT GET IT RIGHT THE FIRST TIME
ON THE LAST DAY OF CHRISTMAS YOU FRICKTARDS GAVE TO ME
TWELVE PACKAGE MANAGERS
ELEVEN BUILD MANAGERS
TEN BOOTSTRAPPERS
NINE SCAFFOLDERS
EIGHT TASKRUNNERS
SEVEN TRANSPILERS
SIX POLYFILLERS
FIVE CONTAINER MANAGERS
FOUR STATE MANAGERS
THREE REACT ROUTERS
TWO JS EXTENSIONS
AND ONE BIG FRICK YOU IM OUT OF HERE
it was always a only a matter of time. at the start there were only a few programming languages and look at where we are now.
No other ecosystem has a market place where at each junction you have half a dozen alternatives. Just give me a canonical set of tools I can invest in PLEASE.
>2018 you gotta use gulp and grunt and then pipe it to gobble and gobby goober
>2022 nah you should just use webpack
> frontend sufferings
your-tears.jpg
I want to crowdsource processing to the end user.
Uhm, sweaty, Webpack is deprecated, we use Vite now.
They should just let people use import on require on the browser
just ignore the homosexualry and use "no framework" JS. It's not even that bad, outside of how utter shit JS is as a whole. Generators let you build all your gay reactive elements and everything easily too.
Kek. The hymn of the buttblasted webdev. Bravo anon!
Best post on IQfy this entire month. Sometimes, this board is alright.
tears. Chills even
Sung to the tune of there ain’t no bugs on me
Is a build system that reuses Node's runtime not a whole thing from scratch. Shouldn't be that fast.
>bun embeds JavaScriptCore, which tends to be faster and more memory efficient than more popular engines like V8
I am having a hard time believing this.
V8 uses something called Isolates to lock the entire virtual machine during code execution on any thread. This essentially means that there is no way for multiple threads to concurrently call into a JavaScript context with V8.
JavaScriptCore locks specific contexts on the other hand (where a context is a part of the virtual machine, and consists of a stack pointer and packaged closure variables). If two contexts don’t share a closure, they can both run in parallel with no contention on different threads.
In the case where two contexts share a global/closure variable, one will acquire the lock and the other thread will have to wait, thus introducing atomic behavior.
So, to sumarize: V8 is simply not capable of supporting shared mutable state with its current approach and design philosophy. It would have to be rewritten from scratch to support such a use case. JavaScriptCore’s design provides a granular approach when it comes to concurrent locking.
So is JSCore only faster when doing concurrent operations or are there other certain optimizations that also make it faster than V8 when just doing normal operations?
>nodelets btfo
>nodelets found shitting and crying
Zigchads can't stop winning
>zig
this is considered idiomatic in zig
Looks better than Rust
> Who cares?
Javascript is a shit language. Typescript is 100% a shittier language built on top of a shit language.
Java is a dead, gay pajeet language that runs the most dead apps in the business sector, attracting Raj and Sanjay.
but Javascript takes the cake for being an absolutely horrendous maintenence nightmare, lack of compiler oversight, buggy, slow, piece of absolute garbage.
Javascript is a disgrace to programming and the whole field of computing. It needs to die.
Go do your website bullshit. Meanwhile my shitty C# app, which is very nicely compiled, and has no string constants whatsoever, no eval(), and is methodologically solid, is cranking out hundreds of thousands of dollars in revenue every hour.
It never crashes, or has a single bug at all, because the beauty of the strongly typed language standard, and *cough cough* compiler.
post github link for your project.
It was over when people thought that websites should be functional applications and not just libraries for information.
Fricking based. JS devs need to fricking kill themselves for the amount of pure dogshit they've unleashed on the world.
Except that moron is wrong.
I would use a shitty FOSS language over a well made and corporate financed one any day.
Except Javascript is both things, a shitty AND a corporate financed language. Inf' fact the fact is backed with billions and thousands of man hours is the only merit it has.
>when you use javascript the whole world works for you
yes
Purescript exists
>another compile to js language
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
>Javascript is a disgrace to programming and the whole field of computing. It needs to die.
python is worse honestly... but ya it's bad.
the best part?
Bun is written in Zig
Faster than V8 therefore Zig got good ads
redpill me on serverside rendering
why would i want to use my servers processing power when i can outsource it to the user?
because the client is useless and easily manipulated
so?
why are brainlets like this? go back to shitposting about video games or whatever you used to
>jskiddie thinks anyone wants to steal his uber GUI code
kys
Just use wasm lmao
It's better when you're serving static content. nobody wants to see a page dynamically loading some blog article. it also has the benefit of being easier to be cached with a CDN. if you're using it right, your static content should not put much burden on the server at all. and if you care, better SEO.
also if you want edge computing, then server side processing makes sense. these fast javascript runtimes are actually optimized for edge compute.
>cache renderings
>better seo/crawlability
>faster response time, not killing user battery
Some modern web pages are such a clusterfrick that anything lower than a modern i7 makes will render slower.
Because of consistent loading speeds
if some third worlder with a wooden pc and dial up internet gets a slow loading time that's his problem not mine
With JS being so much simpler than Java, I would believe that it is can be optimized more easily
what exactly is server side rendering? im not a webdev but i¨ve head the term used quite a bit
i presume its not actually rendering the website on the server side and sending back an imagine like it sounds like...so what is it exactly?
it's basically how IQfy works. you make a request. server builds the html and sends the html to the client with minimal javascript. the client barely does any work.
client side rendering is when the server spits out data to the client and the majority of the work is done by the client to render the html and form the page.
they both have pros and cons.
>you make a request. server builds the html and sends the html to the client
so...basically how any non-static site have always worked? like...php, etc? why is it being hyped up as if its some kind of new technology?
this is basically what web devs do. Reinvent the wheel under a different name every 5 or so years.
See: https://www.youtube.com/watch?v=UBUNrFtufWo
these two things are essentially the exact same fricking thing yet webdevs INSIST that because one stores the token in javascript, and the other in a session cookie its an entirely different concept. Its fricking not. This is literally the same story for 99% of new innovations in the field of web dev in the last ~10 years. This is why i despise & have no respect for webdevs. There are a couple of good ones, but my god they're hidden in a sea of morons & bullshit.
kind of, yes. but some things are different still. one of the reasons server side rendering has become popular again in recent years is because how fast javascript runtimes have become. There are services that run these javascript runtimes for you in every region of the world in many datacenters. We call these edge services. All you need to do is upload your javascript code, and it literally runs everywhere with low latency. You never have to maintain a server. Companies like cloudflare, vercel, deno, netlify, etc. all provide these edge services. so javascript is once again moving away from the client to the server side.
i think wasm will take javascript's place on the edge. no idea when that's actually going to happen tho.
Mostly because of how loading speeds now affects our page ranking on search engines.
It's not only for UX like some here suggest, good SEO actually helps to decrease expenses for paid advertisement.
hmm, another reason why useless bloated WebView apps became a thing.
This. It's how all php sites worked 10-20 years ago. It's not special.
because web devs are morons
This time they're doing clever stuff like delivering html diffs via webscoket and update the client html without refreshing the page.
It's cute but ultimately they're gonna end up rediscovering state management hell and push the work to client side again.
Time is a fat circle.
>filled with bugs
>doesn't work on windows
Yeah it's shit. Also even if the above was fixed, it still doesn't fix the main issues with JS runtimes:
>no true multithreading
>the only typed language option (Typescript) actively refuses to implement many necessary language features
>the only typed language option (Typescript) actively refuses to implement many necessary language features
Which features? I’m curious.
>v0.1.0
How many exploits?
javascript is the natural spiritual successor of Lisp. I don't get why it gets all that hate here.
>But it was a couple of not straight intuitive behaviors
stop being a brainlet
Javascript has nothing substantial to do with Scheme nowadays, is just just happen to have some functional features as the worst middle point between stacking a crap ton of features and having an inconsistent and anemic language at the same time. Is the proof that you only need a name and marketing to get funding.
Why so much panicking lol, at least bother to read the webpage
Seems neat, but definitely not ready for production use yet. I'll check on it again in a year or so.