News for hackers. Stuff that matters.
Re:Webpack 5 by searchableguy on Saturday October 10, 2020 @07:45PM (#24742756)
Deno does away with most of the tooling configuration. You get linter, bundler, docs generator, formatter, watcher, version manager, std library, inbuilt tests, and many things that you would otherwise source from third parties in node ecosystem.

Support for webgpu and local storage incoming. Makes it a delight to write scripts. You can also scope them by permission.

https://deno.land/

Great community: https://discord.gg/deno

Re:Webpack 5 by ficklepickle on Sunday October 11, 2020 @12:51PM (#24747131)
I've been dabbling with Deno and I quite like it.

I wrote a CLI tool to try it out. It monitors CPU/GPU temps then generates an HTML chart on SIGINT.

I like top-level await, the standard library and first-class typescript support.

I do wish the sandboxing was more granular. My small CLI tool requires: --allow-read --allow-write --allow-run and --unstable. I only need a read/write in a single directory, run a single binary. Unstable is required for signal handling, but that shouldn't be the case forever.

I'm glad someone is re-imagining JS/TS on the back end. A robust and stable standard library could well improve the dependency hell and broken projects issues.

Re:Webpack 5 by akmittal on Sunday October 11, 2020 @03:42AM (#24744323)
Deno seem great, But third party libraries seem non existent compared to npm.
Re:Webpack 5 by leptons on Sunday October 11, 2020 @01:18AM (#24743889)
Deno is nowhere near ready for prime-time.
Re:Webpack 5 by drannex on Sunday October 11, 2020 @03:54AM (#24744353)
And likely will have similar issues in five years as node has now.

Node was once thought to be the cleaner alternative that had a lot of these features built in, it was the supposed savior of Javascript, and now look at where we are.

Re:Webpack 5 by ficklepickle on Sunday October 11, 2020 @12:55PM (#24747169)
I think that is an unnecessarily negative view. By that logic, nobody should do anything because it will probably suck someday.
Re:Webpack 5 by drannex on Sunday October 11, 2020 @04:54PM (#24749012)
I do believe constant iteration is better, but Javascript has many problems at its very core, and many Node developers transitioning to Deno are going to create and write solutions that are more akin to their comfort in Node.

This will lend itself to reproducing similar issues as they currently have.

I am primarily a javascript developer, I've written both Node and Deno projects, but I don't see the issues being solved by just rewrapping the source output.