4 ms·
its a welcome addition to the cf worker ecosystem especially because of the features that are missing in most alternatives. however deno would lend itself much
by jFriedensreich 5y ago
its a welcome addition to the cf worker ecosystem especially because of the features that are missing in most alternatives. however deno would lend itself much better to running cf workers locally and also i feel after the 4th cf workers testing environment it would be time to focus not on "simulation" or local testing but to start projects with the goal of being a compatible production ready implementation. such a project could be used for local testing and also for creating cf worker compatible services like deno deploy or just a compatible docker container that runs in your datacenter as an alternative to a nodejs express server, the possibilities are endless.
- rad_gruchalski 5y ago> however deno would lend itself much better to running cf workers locally What would be the reason for this?
- lucacasonato 5y agoUnlike Node, Deno has fetch and a web API based HTTP server built in.
- jFriedensreich 5y agocf workers and deno both have a philosophy of web apis first where custom apis are mostly a last resort if the concept to be done does not exist in web apps or is out of scope. nodejs requires wrapper libraries like node-fetch etc. also deno and cf workers have both the idea to not share any access to host environments or siblings with js code and both use isolates to do this similar to chrome. nodejs usually shares the rights of the executing user.