🚀Launching https://t.co/jA0CCu1H9v - create forms in seconds for students to answer. Teachers receive answers instantly as they type - perfect for AfL in lessons. 100% free and ad-free. Super-charge your lessons with it today.
@jarredsumner Yeah I get that. Currently "bun a.js b.js" will run a.js with Bun.argv[2] being "b.js". I was suggesting what if "bun a.js b.js" is shorthand for "bun --parallel a.js b.js", but actually that's a daft idea on second thought.
@cirospaciari@jarredsumner@xvaara Ok looks like it may be unrelated to websockets - seems like it wasn't the process I thought it was that was pegging the cpu, but another one that doesn't use websockets. Might be a different issue in Bun, or might be a user error eg infinite loop somewhere. Apologies.
@xvaara@jarredsumner I think I got this bug yesterday as well (in v1.3.2). I had my students hammer the server with websocket messages for a few minutes, and when they stopped, the CPU stayed at 100% until I restarted the server. It was still very responsive though.
I made a tiny 100 line library to abstract away pesky WebSocket messages and just invoke remote functions in @bunjavascript and web browsers. Works from server or client. https://t.co/qhJX0xpuiN
@MashStPaddy pretty sure when we first met you told me about hurricane Gilbert hitting Jamaica in 1988. I remember tales of houses with bits missing. Hope all is well with you.
@bunjavascript@jarredsumner Congrats on the release. While the v1.3 blog post is great... where can I find a list of changes vs v1.2.23? The v1.3 blog post lists all the changes vs v1.2 instead.