Bun Is Better Than I Hoped 

This is lowkey genius

🐐

There is a project for that. It's npkill

​@@DatNguyen-vj1rolet's rename it to bunkill

Truly a missed opportunity not calling it npfree

isn't normal to ignoring under 1.0 product?

@@ricoaw500I agree, definitely hold out on it for now, play around with it, but don't transitoin your entire codebase just yet imo. Wait until the product is more stable, because there WILL be major changes and items being deprecated in future releases (meaning you have to remove and change all of your codebase again).

For my personal projects I will go with 1.0 But with team based or my company related projects I would prefer 2+ or 3+ version with more than sizeable community to even consider it.

@chyldstudios bro can you guide me in my career

aside from tailwind yes

Mainly because Theo won't be on RU-vid for a Thousand years.

@@trappedcat3615 💋🐴

@@trappedcat3615 Yes he will. Ever heard of immortal.js?

Lol I disagree with him in this one (and many more), benchmarking proves nothing since it has nothing to do with real world apps

1000%. I've spent wayyy too much time tweaking tsconfigs and package jsons trying to get modules to work the way I want them to. Having a "it just works" solution is a huge benefit.

⁠yea man, why did they make import incompatible with require 😢

yea, i was saying back then that node.js should added it like this. but "noo we will never be able to drop require then", for what i say the Date object is foobar too, the fix is add new syntax, so why can't we do it for import too.

@@wliaputs that's simply because ES standard vs Node Standard, the right question to be asked is, why the hell module is introduce very late in the language

I agree. Additionally, the fact that everything is splintered in first place for very little in terms of real world benefits is atrocious. Even if there was a benefit of sorts, there is no real reason why I shouldn't be allowed to just use both module types, at least on the backend. There is no benefit to treeshaking on the server unless you have a million dead packages in your node_modules. However, if you have that, you are probably doing something wrong or have implimented a build step to elminate all that dead code, in which case, how you import still means nothing.

Is this in their docs. Im trying to build something like pocketbase for fun

Where is this ? I see in build you can build to a bun target which optimizes a build but i don't think it's like hermes that compiles java-script statically.

​@@shadowangel-ou6bg you are correct it doesn't work like hermes. It packages the Buntime and JavaScript source files in the binary which is then run by Bun when it is executed

Psssh 3 is for entry level devs. 8 for seniors!

It feels like having it on WSL 2 is going to be faster than the alternatives

You done much on WSL2 yet? I've seen things be faster there than windows.

Oh yeah, linting out of the box would be great

why not just use WSL?

To be fair, Deno has supported this for quite a while now.

I think so, from what a quick search into the subject is yielding, so long as the drive is using APFS, since HFS does not support CoW, but APFS does, so any more recent mac should get the space savings as well.

exactly. this was missing for ages!

He opened a great PR to turbo recently.

Open source manager.

that's funny

Project management is tedious, don‘t underestimate it

@@MajorBreakfast He doesn't manage it

this is nice to know

True, clonefile copies only the metadata. "The cloned file (dst) shares its data blocks with the (src) file but has its own copy of attributes, extended attributes and ACL's which are identical to those of the named file" I love COW filesystems. I wonder if Bun does something similar in Btrfs.

Bro, it's just websites man.

Does hot reloading works, cause it doesn't work for ne

I've run into similar issues with `bun create preact`. This is the same sort of issue I've always run into getting Bun to work on projects since it was first announced. Some key step is just outright missing or incompatible, and the workaround is to tear apart the `npm install` or other such process to track it down and "fix" it. This is just to init a toy project. It's really disappointing. It all sounds great if you're building without a template from scratch (maybe) or if Bun-specific templates are created in the future, but I figured the whole point was to not have to get "Bun-specific" with everything.

you need `--bun` flag there

still way faster than Python.

How is it safer than Rust?

@@davidt01 yeah well that’s potentially a very long conversation that can go sideways quickly. If rust’s concept of safety works for you, then go for it. There are alternative opinions though.

@@steveoc64 Well from my understanding, Zig has manual memory management, which is inherently not as safe.

@@davidt01 while it may have manual memory management, it has a lot of in-code ways to help you making it safe, and the compiler alerts if there's a memory leak.

Did you figure it out?

let's tell ourselves the truth, many people aren't actually using Deno tbh

@@wisdomelue And more people are giving up Deno.

Well it took NodeJS like half a decade to add built-in Fetch support... so they have a lot of catching up to do