Earlier quoted context omitted.
Java is not for sale.
Java can be depended on without buying anything.
Java's price is your time which you will need tons of as Java is highly verbose. The ultimate enterprise language
Anthropic acquires Bun
621–630 of 1001 posts
Re: Anthropic acquires Bun
#622I wonder what this means for Deno. Will this make it more or less likely for people to use Bun vs Deno? And now that Bun doesn't need to run a profitable cloud company will they move faster and get ahead of Deno?
I think Deno's management have been somewhat distracted by their ongoing lawsuits with Oracle over the release of the Javascript trademark. I started out with Deno and when I discovered Bun, I pivoted. Personally I don't need the NodeJS/NPM compatability. Wish there was a Bun-lite which was freed of the backward compatability.
What do you dislike about having node compatibility?
Re: Anthropic acquires Bun
#623I wonder what this means for Deno. Will this make it more or less likely for people to use Bun vs Deno? And now that Bun doesn't need to run a profitable cloud company will they move faster and get ahead of Deno?
I think Deno's management have been somewhat distracted by their ongoing lawsuits with Oracle over the release of the Javascript trademark. I started out with Deno and when I discovered Bun, I pivoted. Personally I don't need the NodeJS/NPM compatability. Wish there was a Bun-lite which was freed of the backward compatability.
Ironically, this was early Deno - but then adoption required backwards compatibility.
Re: Anthropic acquires Bun
#624From the comments here it sounds like most people think the amount Anthropic paid for the company was probably not much more than the VC funding which Bun raised. How would the payout split work? It wouldn’t seem fair to the investors if the founder profited X million while the investors get their original money returned. I understand VC has the expectation that 99 out of 100 of investments will net them no money. Bu…
Probably not much more than their valuation, which is the key difference since the investor will still get a net return.
Re: Anthropic acquires Bun
#625Earlier quoted context omitted.
Handmade Cities founder here. We never associated with Bun other than extending an invitation to rent a job booth at a conference: this was years ago when I had a Twitter account, so it's fair if Jarred doesn't remember. If Handmade Cities had the opportunity to collaborate with Bun today, we would not take it, even prior to this acquisition. HMC wants to level up systems while remaining performant, snappy and butter…
Finding this comment interesting, parent comment didn't suggest any past association but it seemingly uses project reference as pivot point to do various outgroup counter signaling / neg bun?
I understand the concern, but really? I found this quote enough to offer proper comments:
> had a vague idea that "Zig people" were generally "Software You Can Love" or "Handmade Software Movement" types
Folks at Bun are "Zig people" for obvious reasons, and a link was made with Handmade software. This happened multiple times before with Bun specifically, so my response is not a "pivot" of any kind. I've highlighted and constrasted our differences to prevent further associations inside a viral HN thread. That's not unreasonable.
I also explicitly congratulated them for the acquisition.
Re: Anthropic acquires Bun
#626Re: Anthropic acquires Bun
#627Earlier quoted context omitted.
This is a non sequitur. Both Rust and Zig and any other language has the ability to end in an exception state. Whether it be kernel exception, pointer exception, or Rust's panic! - these things exist. The reason why you see so many GitHub issues about it is because that's where the development is. Deno is great. Bun is great. These two things can both be great and we don't have to choose sides. Deno has it's use case…
Don't make a false equivalence, how many times does one get a panic from Deno versus a segmentation fault in Bun? It's not a similar number, and it's simply wrong to say that both are just as unsafe when that's plainly untrue.
I use Bun in production. Well, one of my clients.
We have yet to witness a segfault. Admitedly it's a bunch of micro services and not many requests/s (around 5k AVG).
Re: Anthropic acquires Bun
#628Re: Anthropic acquires Bun
#629Earlier quoted context omitted.
Not in the browser, and no – webassembly doesn't count, otherwise you can say the same about Go and others.
May I ask, what is this obsession with targeting the browser? I've also noticed a hatred of k8s here, and while I truly understand it, I'd take the complication of managing infrastructure over frontend fads any day.
HN has a hatred of K8s? That’s new to me
Re: Anthropic acquires Bun
#630I wonder what this means for Deno. Will this make it more or less likely for people to use Bun vs Deno? And now that Bun doesn't need to run a profitable cloud company will they move faster and get ahead of Deno?
> Will this make it more or less likely for people to use Bun vs Deno?
I'm not sure it will make much of a difference in the short term.
For those who were drawn to Bun by hype and/or some concerns around speed, they will continue to use Bun.
For me personally, I will continue to use Node for legacy projects and will continue using Deno for current projects.
I'm not interested in Bun for it's hype (since hype is fleeting). I have a reserved interested in Bun's approach to speed but I don't see it being a significant factor since most JS speed concerns come from downloading dependencies (which is a once-off operation) and terrible JS framework practices (which aren't resolved by changing engines anyway).
----------------------------
The two largest problems I see in JS are:
1. Terrible security practices
2. A lack of a standard library which pushes people into dependency hell
Deno fixes both of those problems with a proper permission model and a standard library.
----------------------------
> And now that Bun doesn't need to run a profitable cloud company will they move faster and get ahead of Deno?
I think any predictions between 1-10 years are going to be a little too chaotic. It all depends on how the AI bubble goes away.
But after 10 years, I can see runtimes switching from their current engines to one based on Boa, Kiesel or something similar.