Комментарии:
Opportunity lost, he should have coded in GoLang while he dyed his hair blue. Maybe he'll die his hair orange for Rust 😅.
ОтветитьAnother day another js runtime and framework
ОтветитьBro don't want to use excalidraw
Ответитьcan't wait for bun devs to unleash unsafe magic just to dunk on winterjs performance
Ответитьwe need Rust to Trust :)
ОтветитьDO HASKELL!!!! haha
ОтветитьWho left the fridge open?
ОтветитьThe speed shouldn't be their selling point, but having a wasmer runtime is actually really dope. Wasm will slowly take over. It's already being added to k8s as a runnable type because it solves a lot of the problems that docker does, but lighter and static with basically no cold start times
Ответитьldflags are just linker flags. They don't change the compiler optimization. You just stripped the debug info.
ОтветитьI noticed quite a lot of poorly informed people wanted to comment here, and that they seem to be JS developers. There's a correlation!
ОтветитьWhy are programmers so arrogant
ОтветитьShot out to Flip
ОтветитьAI wont be able to keep up with the web development tech, our jobs are safe
ОтветитьAnother day, another JS tech comes out... literally. The cycle never ends. 😂 boy how this new era sucks.
Ответитьhonestly anything is better than GoaJS - trust me
ОтветитьWhy don't they mention Deno? Smh.
ОтветитьOh it's engineer is an Iranian!
ОтветитьLOL took me a while to notice it was your Pixel that was getting notifications and not mine.
ОтветитьAt this point I'd rather learn Go or Rust for the backend.
ОтветитьInstead of taking a plane, some people keep trying to make their bike faster. 😂
ОтветитьShoutout to all of the Super Mario Kart enthusiasts, for those who are actually aware of its existence
Ответитьjavascript need to be destroyed, framworks and runtimes keep spawning
ОтветитьYou get the lightening bolt in Mario Kart when you're losing really badly. The only thing you should feel then is shame, utter shame!
ОтветитьWhen you shout you sound like Michael Scott from the Office
ОтветитьJs is like arms race
ОтветитьXNA... That was a shoutout I was not expecting!
ОтветитьRoses are red,
Violets are blue,
We do not want,
your stupid JS runtime.
I think I should start calling JS more unholy than C++.
OdenJS Im still waiting for you.
ОтветитьAnother fucking JS …. thing. I am so done with web development.
Ответитьbro my brain can't handle this anymore, that fact that I just started installing bun hours ago 💀
Ответитьis this linked to WinterCMS? Even the logo appears to be the same.
ОтветитьRidiculously fast 😂 all i heard was about been fast in entire documentation
ОтветитьWould be great to have a tutorial on how to build a winterjs Dockerimage
ОтветитьAfter the fifth "asteriks" I had to stop watching. I just can't.
Ответить3 cores will be slower than a single thread cuz of the caches if the cores share any state
ОтветитьMore Cilaka
ОтветитьIf a runtime or framework can't be properly instrumented- it's not Production ready.
Ответитьlike seriously, if i were to done my projects and building portfolio at the same rate as JS making another framework i will probably rich enough i'll retire in my 20, having my own yatch, and living on a mansion rather than thinking of hopping jobs and risking myself of early heart attack.
ОтветитьLies, dang lies, and benchmarks (statistics)
Ответитьwhen will we get a Rust powered JS runtime?
ОтветитьWhy would I want to compile a JavaScript runtime to wasm?! Please, people. Just stop, your software is slow enough already.
Ответитьgreat topic, thanks 👍
ОтветитьCheck the math. Go did 201k/sec. Bun did 155k/sec. WinterJS (according to their benchmark) has ~130% the throughput of Bun.
Which gets to you .... drum roll please .... 201k/sec.
Likely parallelism settings is the reason for absolute difference in your benchmarking.
I appreciate that the benchmark Bun uses for its built-in builder is Three.js, which is a fairly large project. It's at least a real benchmark.
In a way though, their hand was forced on that front, because they were just copying the benchmark that esbuild was using, since they wanted to demonstrate that bun was faster than esbuild.
guys what am i missing? what fucking difference does it all make if the bottleneck is ALWAYS your fucking shitty orm written sql queries that hog your db? for like 99% of devs is this speed chase even justified?
ОтветитьI'm dyinng in the summer heat and we didn't get any summerjs runtime
ОтветитьStill waiting for GoonJS
Ответитьdeno2.0 watching
Ответить