#denoland — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #denoland, aggregated by home.social.
-
Reports of Deno's Demise Have Been Greatly Exaggerated
https://deno.com/blog/greatly-exaggerated
#ycombinator #deno #denoland #development #javascript #typescript #webassembly #wasm -
> I’ve been noticing a trend with #DenoLand Inc. products. Engagement with users is fleeting. What I mean is that many reported issues with #Deno products are never addressed. Often they’re not even acknowledged. From #DenoKV architecture, to #DenoDeploy startup times, I keep running into show stopping issues with little to suggest they’ll ever be fixed. It’s not a good look.
-
> I’ve been noticing a trend with #DenoLand Inc. products. Engagement with users is fleeting. What I mean is that many reported issues with #Deno products are never addressed. Often they’re not even acknowledged. From #DenoKV architecture, to #DenoDeploy startup times, I keep running into show stopping issues with little to suggest they’ll ever be fixed. It’s not a good look.
-
> I’ve been noticing a trend with #DenoLand Inc. products. Engagement with users is fleeting. What I mean is that many reported issues with #Deno products are never addressed. Often they’re not even acknowledged. From #DenoKV architecture, to #DenoDeploy startup times, I keep running into show stopping issues with little to suggest they’ll ever be fixed. It’s not a good look.
-
> I’ve been noticing a trend with #DenoLand Inc. products. Engagement with users is fleeting. What I mean is that many reported issues with #Deno products are never addressed. Often they’re not even acknowledged. From #DenoKV architecture, to #DenoDeploy startup times, I keep running into show stopping issues with little to suggest they’ll ever be fixed. It’s not a good look.
-
> I’ve been noticing a trend with #DenoLand Inc. products. Engagement with users is fleeting. What I mean is that many reported issues with #Deno products are never addressed. Often they’re not even acknowledged. From #DenoKV architecture, to #DenoDeploy startup times, I keep running into show stopping issues with little to suggest they’ll ever be fixed. It’s not a good look.
-
-
Choose to try #pino for the #NodeToDenoChallenge and worked first try. Would be interesting to dig deeper into all of Pino's functionality to see if it holds up but a promising start nonetheless. #deno #denoland
-
-
@deno_land If I want to make use of `deno_cron` with Deno Deploy, how would that work? The library uses `setInterval()` to continue waking up the process every second to perform tasks if necessary. I don’t have that many tasks to execute, but it seems this doesn’t really fit the edge model. Would the process be terminated once my tasks exceed the 10ms limit?
How do others solve such use cases with #Deno or in #Denoland? -
I think I've fallen out of love with #deno #denoland . It's a really good tool, specially since it has a better API than node, promise-based and typed. However, the lack of package managing is a terribly wrong choice
NPM did package managing so well that Rust's Cargo works almost the same. I'm not sure why Deno creators decide to throw it off.
The thing is, whenever I'm working with Deno I'm non stop struggling with the package managing. If I go for adeps.tsapproach I have to constantly be re-exporting libraries. Also in the app files it isn't clear where a package comes from.
If I just import where I need it will be impossible to update versions later, or it will required tools that look the entire source tree
And finally the sourcemaps approach don't work for libraries
The only good thing about the URLs approach is that I kind point tofile:///URL and develop libraries in a really fast fashion, that's all -
TIL that the #deno #freshframework `alive` connection used when a local server is run can be disabled by setting DENO_DEPLOYMENT_ID env var
see: https://discord.com/channels/684898665143206084/1050017193582153748/1050072105380757616
#denoland #deno -
I just published a post to my Craig's Deno Diary blog on the Ultra v2 framework which allows full-stack React apps to run in a Deno environment.
Ultra supports many React libraries and features including Tailwind, React Router and React Query. Version 2 works with React 18 which includes suspense for async rendering.
The blog post focuses on creating, developing and deploying a full-stack Ultra app.
https://deno-blog.com/Building_Fullstack_React_Apps_with_Ultra.2022-12-04
-
A new blog post has been published on Craig's Deno Diary showing how to use Preact Signals with Deno Fresh for reactive state management: https://deno-blog.com/Using_Preact_Signals_with_Fresh.2022-11-01
#deno
#denoland
#preactjs
#javascript -
I get more exited about #denoland every time I check in on the project. There are now a few standard modules, a module style guide and binary installation manager