3 ms·
As someone who worked heavily with Cloudflare offerings (being it Pages or Workers), I am surprised how much they have invested in the tech to make it work (V8
by csomar 2y ago
As someone who worked heavily with Cloudflare offerings (being it Pages or Workers), I am surprised how much they have invested in the tech to make it work (V8 isolation) and then simply shipped a half-assed API/framework with little to no documentation. They are sitting on the revolution of serverless and wasting potential use cases because they keep chasing the next production to pump.
- davidgomes 2y agoOP here — yes, I absolutely agree! The "hard" work of creating the Workers technology and service is useless if they don't do the arguably easier (but more tedious) work of getting the ecosystem to play well with Workers. This means making a list of the Top 1000 most popular packages on Node.js, and finding ways to make as many of them work on Workers as possible. For the ones where it's too hard/impossible, there should be *well-documented* alternatives.
- prokopton 2y agoThe rise of Bun, Deno, and other not-Node environments will help this out. JSR also does a good job of indicating what packages work where—if it gains traction.
- arresin 2y agoI had the same thought. I very strongly advise people not to start with workers with the state the documentation is in unless you have the time to go through the source code (which is c++). Also, one thing that isn’t made clear in the documentation is that you cannot test in any real sense. They have buggy, toy PoC testing but there’s no way to do local testing for real world apps. If you’re making anything more complicated than a blog it gets very painful very quickly.
- csomar 2y agoI'd recommend going with Rust/Wasm since even though you can't live test, getting your code to compile gets you quite close to that.