I was willing to gloss over the AI usage because I really like the Bun DX. I used Bun in Shell scripts and small prototypes before and decided to use it for something bigger.
But then in a week or so of use, tons of issues appeared. Use-after-free bugs when a client disconnects (both in Zig and the Rust port, funnily enough) which will kill Bun. Unimplemented feature which just return “0” always. Many backpressure bugs which means something like “return new Response(fs.createReadStream(bigFile))” will greedily read and OOM your box.
All of these have been reported, robobun has made fixes of various quality, but none of this has been addressed. Some of them have been reported for months.
I’d prefer Bun to work on stability rather than fancy features like image processing or threads.
Note that this really isn’t anything except the agreement to send messages separated by 2 new lines. The SSE object in browsers is old and quirky; for example, it only supports GET requests, which means you’ll hit path length limits if you use it for something like LLM completion with large prompts.
Luckily since there’s nothing special about the browser support, you can very easily replace it with custom implementations. https://www.npmjs.com/package/@microsoft/fetch-event-source for example offers mostly the same API, but does offer POST requests and a bunch of other goodies.
I'm currently working as a senior software engineer (SDE3) in Amazon AWS, working on distributed services built on top of AWS, both frontend and backend.
What I would love is something that can give alternative tube sizes.
My bike uses 22x3 tubes, which are unusual and hard to come by. However, there have been reports of 20x4 bike tubes or 18x3 motorcycle tubes also fitting.
A website that recommends more widely available or cheaper “this will also fit” tubes would be amazing.
All these faster speeds won't do anything really for heavily populated areas. The most important thing is total available bandwidth (bytes/sec/hz), and it's unclear how better that will get. LTE itself doesn't improve a lot over 3G techniques, the thing that's making LTE faster in saturated conditions right now is that there's just more bandwidth compared to 3G.
Off shore wind power is about 25% of the wind power capacity of Denmark, the rest are 'normal' wind turbines. However, they'll contribute more to the total energy output. Off-shore wind turbines generate about 35-50% of their maximum capacity on average, compared to 20-30% of normal wind turbines.
Biggest thing I'm missing in the FF Aurora builds is a console in the Inspector / Debugger panes. Having to switch to the console pane all the time gets annoying quickly.
This still doesn't explain why the MRI implementation is accidentally threadsafe. Why doesn't the interpreter switch threads after reading the value from the hash but before storing the updated value?
Not really -- the directory server can just direct a user to connect to a MITM server. There's no need to control the entire network, you only need access to Skype's servers.
Skype has always relied on a central authentication server, which means that anyone with control of that server would be able to MITM any conversation. The recent changes of ownership and centralization of the service have nothing to do with this. Presumably the US government has been able to tap into any Skype conversation they want for a long time.
This is pretty cool. Anyone know what the retrieval pricing is? With Glacier you can limit the amount you pay by retrieving really slowly, but I'm not sure that works with the S3 frontend.
Note that you don't need to 'enable' the Meta key in Terminal on OS X.
By default, option does what it does in other programs, allowing you to type alternative characters. If you'd still like to keep that behaviour, you can send meta by pressing escape first -- Meta-b becomes escape, then b.
But then in a week or so of use, tons of issues appeared. Use-after-free bugs when a client disconnects (both in Zig and the Rust port, funnily enough) which will kill Bun. Unimplemented feature which just return “0” always. Many backpressure bugs which means something like “return new Response(fs.createReadStream(bigFile))” will greedily read and OOM your box.
All of these have been reported, robobun has made fixes of various quality, but none of this has been addressed. Some of them have been reported for months.
I’d prefer Bun to work on stability rather than fancy features like image processing or threads.