Now that Discord will start showing ads, is there any chance Bun will support a communication platform that is open & ad-free like IRC, XMPP, or Matrix?

What kind of question is this? He is working on a JavaScript/TypeScript runtime not building a communication product. Why would you run to him to solve your pet grievance with Discord?

I imagine the complaint is around Bun's use of Discord as community coordination tooling -- linked in the site's header. The post isn't implying Bun should be involved in the creation of an alternative.

(I'm not here to throw shade at using Discord for OSS "communities" - I do as well - And am concerned about the path forward. Just want to clarify the question's intent.)

If open source, free software is a good enough ethos for your code base, it should be good enough for your community communications. Supporting only a proprietary locks out a swath of users & Discord in particular is an information blackhole—and now with ads!

Which users are unable to use Discord? Note that unable is different from unwilling, and "locked out" is not an accurate description of the latter.

Me! Discord does not consider me a real person if I don't have a phone number it approves of.

Users that need special clients (accessibility, hardware, etc.). Users blocked by US sanctions. Users that have been moderated off the platform for something not in your community (account bans even happen accidentally). Users with privacy/anonymity concerns about the data collection (& now ads)—especially the chat rooms that require a SIM card. Users that take their FOSS or otherwise ethical software views or anti-corporate views to heart & want something built on those principle—from wanting to use free software to make free software, to wanting to outright avoid what some now call enshitification where a free (gratis) account clashes with the idea of freedoms, etc.

I'm assuming it is because Bun uses Discord? There are Discord links on their site and on Github, though the links don't seem to work.

I think they used the word "support" to mean "use", rather than "build". That is - they weren't asking Bun developers to _build_ an alternative to Discord, but rather to stop _using_ Discord.

Ship an open-source Discord alternative that more people want to use than Discord and we’ll happily switch.

Are there plans for adding concurrent or parallel execution to the test runner? I recently tried looking at the code base to maybe implement it myself, and it looks like it wouldn't be easy without some reworks.

We need to do some form of this but I’m not exactly sure what yet. I suspect same process but multiple globals might work well. A lot of tests spend time sleeping or waiting for things. They might benefit from that kind of paralellism (like async/await, except between things it runs a whole other global object)

Threads could also work but the problem is you have to re parse & evaluate all the code. That’s a lot of duplicate work. It’s probably still worth it for large enough apps

Isn't there some way of cloning a loaded vm after loading a module? I would imagine that should be possible some how, that way you could parse once then execute in multiple threads.

Is there a privacy policy available for the telemetry collected by default by Bun?

The opt-out telemetry is worrisome. Along with the fact that there doesn't appear to be a way to disable it for single-file executables if you plan to distribute a Bun cli app to users: https://github.com/oven-sh/bun/issues/8927

According to this, it seems they don't actually send the telemetry:

https://news.ycombinator.com/item?id=39901755

Hope my interpretation is correct.

Yeah I saw a Github discussion where he mentioned that the code for uploading telemetry data was disabled, but he also said he plans to re-enable that at some point: https://github.com/oven-sh/bun/discussions/2605#discussionco...

I would prefer to have the telemetry become opt-in before data collection is turned on.

Completely agree.

GG for Windows support and all the addition in 1.1 :) Thxx

When will `worker` API be ready for production?

love it, even `bun upgrade` is fast:

On my rpi 4 that I capped to 600mhz for performance testing:

Bun v1.1.0 is out! You're on 1.0.36 [3.93s] Upgraded.

> I work on Bun and happy to answer any questions.

I think I saw somewhere that 1.0 did not support NextJS. Does 1.1?

I think I answered my own question. According to https://bun.sh/guides/ecosystem/nextjs Bun does not yet support NextJS.

Not a question, but wanted to say: Great job!

When are we getting UDP/dgram support?

Yours and the team's performance is so impressive. I'm not brave enough to use Bun in production yet, but count me in in a year or so ... great stuff.