I think this is a bit of a one-sided POV, so I’d like to share mine. I have been a Deno user, and loved its Web standards approach, but with both Node catching up, and Deno moving in Node’s direction there was too little differentation. I agree with the poster in another comment: the writing has been on the wall for Deno.
I think CF’s workers architecture is very good, and if that excellent team now works on making that a serious FLOSS offering, I think this is very good for the JS/Wasm ecosystem.
I agree with you about all this. Also it was really Bun not Node that was setting the pace. I might consider putting my own runtime into the field one of these days, as I have my own ideas about how to make it into a platform worth using.
I think this is a bit of a one-sided POV, so I’d like to share mine. I have been a Deno user, and loved its Web standards approach, but with both Node catching up, and Deno moving in Node’s direction there was too little differentation. I agree with the poster in another comment: the writing has been on the wall for Deno.
I think CF’s workers architecture is very good, and if that excellent team now works on making that a serious FLOSS offering, I think this is very good for the JS/Wasm ecosystem.
score 1 · canonical
I agree with you about all this. Also it was really Bun not Node that was setting the pace. I might consider putting my own runtime into the field one of these days, as I have my own ideas about how to make it into a platform worth using.
score 1 · canonical