Been doing some prototyping over the last couple days. It's noticeably faster in development and I'm loving the out-of-box support for TypeScript and for things like top-level await that are a pita to implement in Node. Gonna hopefully be able to test it in production soon. Not using it for anything serious until I've done some more testing.
The amount of features is impressive, although I haven't successfully been able to get it to work in a non Hello World project, and its docker image ends up being 2x larger and memory consumption is 3.5x more than in Node. If you simply traded speed for space/memory, then you effectively did nothing because your hardware costs will still be roughly the same (or more if you never needed the extra speed). I am excited, yet it feels there is still a long way to go, and I am skeptical if they rectify space and memory issues (and compatibility issues), that it won't turn about overall better than Nodejs, but we'll see. I give it another few months or so (sadly, 1.0 isn't actually a 1.0 in the colloquial sense, at least for the runtime) and if they are still in this non-quite-compatible zone, I will be severely concerned. This'll also prompt Node/Deno npm/yarn etc to step their game up and perhaps adopt some things Bun is better at, so I think overall it's good for the Javascript ecosystem either way.
Only thing I have to complain is how many errors they’re are when installing dependencies, and trying to resolve them. One day it works, the other it doesn’t. Also support for windows. I don’t think it’s 1.0 ready yet. Other than that, it’s incredible
U should make a tutorial on how one should use the official documentation for new frameworks to self learn and start developing projects using it , its something which is very ignored
Let's go top level await! Still, I can't make it work with my existing express codebase yet. It's got a lot to go until it can claim to be a true nodejs drop-in replacement. This is what bothers me the most. It's a spectacular runtime, the dev experience is faster, cleaner, and overall nicer than working with node, but the false advertisement is real.
Hello @Travis I hope you are doing well . Can you share some resources to learn android development from scratch , I will be really gratefull if you share . Thank You !!!
Hey Travis, your video actually impressed me, But the thumbnail not good at all. I'm a Thumbnail designer and I can increase your views up to 2x or 3x. Let me know if you need.
![[Live] : ONE 168 วันนี้!! "โจนาธาน vs ซุปเปอร์เล็ก"](http://i.ytimg.com/vi/0jIN65KgJsI/mqdefault.jpg)
Been doing some prototyping over the last couple days. It's noticeably faster in development and I'm loving the out-of-box support for TypeScript and for things like top-level await that are a pita to implement in Node. Gonna hopefully be able to test it in production soon.
Not using it for anything serious until I've done some more testing.
The amount of features is impressive, although I haven't successfully been able to get it to work in a non Hello World project, and its docker image ends up being 2x larger and memory consumption is 3.5x more than in Node. If you simply traded speed for space/memory, then you effectively did nothing because your hardware costs will still be roughly the same (or more if you never needed the extra speed).
I am excited, yet it feels there is still a long way to go, and I am skeptical if they rectify space and memory issues (and compatibility issues), that it won't turn about overall better than Nodejs, but we'll see.
I give it another few months or so (sadly, 1.0 isn't actually a 1.0 in the colloquial sense, at least for the runtime) and if they are still in this non-quite-compatible zone, I will be severely concerned.
This'll also prompt Node/Deno npm/yarn etc to step their game up and perhaps adopt some things Bun is better at, so I think overall it's good for the Javascript ecosystem either way.
Only thing I have to complain is how many errors they’re are when installing dependencies, and trying to resolve them. One day it works, the other it doesn’t. Also support for windows. I don’t think it’s 1.0 ready yet. Other than that, it’s incredible
Ah, thanks for these examples, I did miss a couple from the docs 😊
Although I mainly use Python, I still learn a lot from this video. Thanks Travis! Good work!
Eeew, datetime.datetime.now()
I've been programming for 19 years and I find Python so poorly thought out and tacked together.
U should make a tutorial on how one should use the official documentation for new frameworks to self learn and start developing projects using it , its something which is very ignored
I agree. This is a very important skill to develop. I'll try to put something together.
@@TravisMedia thanks Travis ,it'll be really helpful for beginners
Fyi, node doesn't need node fetch, it's built in these days. Hot reload is now built into node.
It can be the next deno! better to wait before refactor all the projects!
Thank you.
Let's go top level await! Still, I can't make it work with my existing express codebase yet. It's got a lot to go until it can claim to be a true nodejs drop-in replacement. This is what bothers me the most. It's a spectacular runtime, the dev experience is faster, cleaner, and overall nicer than working with node, but the false advertisement is real.
how you put things together soon nicely?
great video thanks
what is the autocomplete tools you use for the terminal?
zsh-autosuggestions
Hello @Travis I hope you are doing well . Can you share some resources to learn android development from scratch , I will be really gratefull if you share . Thank You !!!
Bun is really a no-brainer
Can it also be used over npm?
Yes
I have a bun in the oven!
Hey Travis, your video actually impressed me, But the thumbnail not good at all.
I'm a Thumbnail designer and I can increase your views up to 2x or 3x. Let me know if you need.