171–180 of 920 posts
It's a transpile. And not even a good one. The generated code is far from idiomatic rust. Some may consider it an abomination.
Is it important to be idiomatic if the project meets its goals around memory safety?
Earlier quoted context omitted.
What a load of bs. > Inevitable collapse According to who? You? The well ackshually guy? > Low in trust before acquisition Cite your sources. > Unreleased version v140 is the canary version which has been available for a long time. https://github.com/oven-sh/bun/releases/tag/canary > Not open source anymore Who died and made you the dictator of open source? Your post is just a bunch of opinions and lies and speculati…
> v140 is the canary version which has been available for a long time. https://github.com/oven-sh/bun/releases/tag/canary What is actually going on with that tag? It has files uploaded in Jul 29, 2024 and files uploaded "6 hours ago" (some hours after Simon first published his blog post). Do they not do proper releases with immutable tags and instead use one tag kind of like a git branch that mutates and changes over…
I don't like that, personally. I think the project would be easier to reason about if they shipped alpha versions instead.
Earlier quoted context omitted.
Rust as a language is irrelevant to this discussion, the problem is that bun was vibe coded by a single dude without any open source community involvement. “bun the open source project” is basically dead at that point: don't expect any of the zig enthusiasts who had their code being forcibly rewritten in a language they don't like to follow Jared. “bun the JavaScript runtime ” is not dead though.
Is the idea that a code base reset makes something stop being open source? Or that the number of people doing the reset matters? I don't see why either of those would be true. The project isn't dead just because it's in a different language now, and for liveness purposes it doesn't matter how it got to that different language.
A fast rewrite of Bun in Rust has effectively alienated most of the people in the Bun community, so in that sense the “open source project” has died. It’s no longer a community project, it’s just become a personal project again.
All the emotion of speculations aside, how it runs? It boots faster yeah, but what about RAM and CPU usage? Weird dead loop or dead locks? If it run as good as before or even better, then that's kinda impressive. I'm a developer so I really don't like it when AI might took my job, but if everyone on this planet could create a software for themselves exactly as how they wanted with just a few simple demands, that will…
> Think of it as a democratization of technology Incredibly naive take when these models are closed behind (for now subsidized) paywalls. This "democratization" argument is so nauseating, seems like the Bun port to Rust as a marketing piece (the primary motivator) sold it well!
When this happens, a link shows up to report the issue. It’s not clickable (likely due to the segfault), and perhaps more important: it’s encoded, so you can’t see what you would be sending in your report.
Hope it gets better.
Earlier quoted context omitted.
https://news.ycombinator.com/item?id=48843352 https://news.ycombinator.com/item?id=48837877
Your point being? None of my comments in either of those state that I'm upset about it moving from Zig to Rust?
Earlier quoted context omitted.
Please re read your original comment. AI rewrite is one thing and objecting to FOSS/non FOSS is a new argument, anti-Anthropic etc is moving the goal posts. The main argument was the blanket rewrite to Rust using Claude. Now, /you/ are trying to move the goalposts into an entirely different argument. Very likely it’s just anti Anthropic altogether. Like I said, a meme. Anthropic hasn’t done anything wrong but if they…
Airing two entirely separate objections to a project is not “moving the goalposts”. The original objection still stands! You’re using a phrase you’ve heard in an inappropriate context. I’m sorry but this is a nonsensical debate. > Now, /you/ are trying to move the goalposts into an entirely different argument. You said something and I responded to it. That’s invalid too now? There can only ever be one single objectio…
Earlier quoted context omitted.
Indeed as much I dislike the approach Bun took, at least the port appears to be working. TS7 is going to cause problems for downstream users because Go is the wrong language to use for something that has to run in WASM.
> TS7 is going to cause problems for downstream users because Go is the wrong language to use for something that has to run in WASM. Is there a huge need to run that typechecking on browsers?
It's not just typechecking, the typescript library is also the reference parser for TypeScript and reference emit. Emitting JS from TypeScript is non-trivial and non-local.
It's not just in browsers, you might want to run the typescript library on the edge or in some restricted environment where JS/WASM is OK but native code is not.
You may want to use the typescript library as a dependency in your own package. TypeScript becoming non-pure JS means that your library also becomes non-pure JS.
Earlier quoted context omitted.
Indeed as much I dislike the approach Bun took, at least the port appears to be working. TS7 is going to cause problems for downstream users because Go is the wrong language to use for something that has to run in WASM.
> TS7 is going to cause problems for downstream users because Go is the wrong language to use for something that has to run in WASM. Is there a huge need to run that typechecking on browsers?
Secondly, WASM isn't the right target for the browser anyway, JS and the DOM have to be what you consider "native", for the most rigorous UI projects at least (which building an IDE is). If you want to build a cross-platform UI product that doesn't require installation and has Emacs-like levels of extensibility, JS is the end of the line in terms of language selection. There are no other candidates.
Anecdotal, but I’ve been getting segfaults in Claude Code. I run inside Kitty tabs, and the entire tab becomes unusable when this happens. No response to inputs at all from that point. When this happens, a link shows up to report the issue. It’s not clickable (likely due to the segfault), and perhaps more important: it’s encoded, so you can’t see what you would be sending in your report. Hope it gets better.
If nothing prints "Segmentation fault", this just sounds like a hang