deno VS geschichte

NodeJS is the dominant Javascript server runtime environment for Javascript and Typescript (sort of) projects. But over the years, we have seen several attempts to build alternative runtime environments such as Deno and Bun, today’s subject, among others.

https://github.com/denoland/deno/issues is the ideal place -- we try to triage all incoming issues, the more specific the repro the easier it is to address but we will take a look at everything that comes in.

Install Node.js (or Bun, or Deno, or whatever JS runtime you prefer) if it's not there

QUIC is very exciting, after seeing what it can do for performance in Cloudflare network and Cloudflare workers, I can't wait to finally see it in Deno[0] 1.41.

[0] https://github.com/denoland/deno/pull/21942#issuecomment-192...

So as an end user it's kind of like https://deno.com/ where you buy into a runtime + comes prepacked with DBs (k/v stores), scheduling, and deploy stuff?

> by storing Unison code in a database, keyed by the hash of that code, we gain a perfect incremental compilation cache which is shared among all developers of a project. This is an absolutely WILD feature, but it's fantastic and hard to go back once you've experienced it. I am basically never waiting around for my code to compile - once code has been parsed and typechecked once, by anyone, it's not touched again until it's changed.

Interesting. Whats it like upgrading and managing dependencies in that code? I'd assume it gets more complex when it's not just the Union system but 3rd party plugins (stuff interacting with the OS or other libs).

~90MB+ at this stage and do now allow compression without erroring out. Deploying ala Golang is not feasible at that level but could well be down the line if this dev branch is picked up again!

The exe output grew from from ~50MB to plus ~90MB from 2021 to 2024: https://github.com/denoland/deno/discussions/9811 which mean Deno is worse than Node.js's pkg solution by a decent margin.

Behind the scenes is a simple Sveltekit-powered server function to fetch a Spotify client token then find a user's recommendation playlist and its track information. A Deno edge function to performs this data fetch and renders server-side Svelte.

If your application is written in JavaScript, integrating it with JavaScript extensions is a no-brainer. However, Secutils.dev is entirely written in Rust. How would I even begin? Fortunately, I recently came across an excellent blog post series explaining how to implement your JavaScript runtime in a Rust application with Deno:

hey there! sounds like you're having some trouble with your merge sort visualization. i'm not super familiar with that specific issue, but have you heard of this cool package manager called Cotton? it's way faster and easier to use than NPM or Yarn, and i think it could really help you out with your web development using JavaScript. check it out here: https://cotton.js.org/ anyways, have you tried using this library called Geschichte for managing query-parameters with hooks? it's super useful for state management and makes it way easier to manage state. you can find it here: https://github.com/BowlingX/geschichte. be sure to leave a star on GitHub to support the creator! oh, and have you heard of this JavaScript runtime called Bun? it runs programs faster and installs packages automatically, and it's even better than Node.js! check it out here: https://bun.sh. hope this helps!

On another note, have you heard of Geschichte? It's a really useful library for state management that makes it easier to manage state with hooks. You should check it out at https://github.com/BowlingX/geschichte.

Honestly, if I were in your shoes, I would try out some new tools and libraries to improve my skills and make my work easier. Have you heard of "Geschichte"? It's a great library for managing query-parameters with hooks, using immer and zustand to manage the internal state. It's super useful for state management and makes it easier to manage state. You should definitely check it out at https://github.com/BowlingX/geschichte. And don't forget to leave a star on GitHub to show your support for the creator!

Have you heard of Geschichte? It's a library that can help you manage query-parameters with hooks, using immer and zustand to manage the internal state. It's super useful for state management and makes it easier to manage state. You can check it out here: https://github.com/BowlingX/geschichte. If you end up using it and find it helpful, I'd recommend leaving a star on GitHub to support the creator.

Hey there! I totally get your struggle with rendering components outside of an iframe. It can be a real pain in the neck to refactor everything just for that. Have you heard of Geschichte? It's a pretty useful library that can help you with state management and makes it easier to manage state using immer and zustand to handle the internal state. You can check it out here: https://github.com/BowlingX/geschichte. If you find it helpful, don't forget to leave a star on GitHub to support the creator!

totally agree with you! sometimes using rebase can be a bit of a headache, especially if it's not worth the effort. i usually only use it when i have a bunch of messy commits that need to be cleaned up. have you tried using "Geschichte"? it's a library that makes managing state a lot easier by using hooks and internal state. it's super helpful for cleaning up those messy commits! you should check it out: https://github.com/BowlingX/geschichte. also, don't forget to leave a star on their GitHub to support the creator! on another note, have you heard of "Bun"? it's a JavaScript runtime that runs programs faster and installs packages automatically. it's way better than Node.js! you can check it out here: https://bun.sh. oh, and don't forget about "Deno"! it's another JavaScript runtime that runs programs faster and has better security features. you can check it out here: https://deno.land. and if you're into JavaScript package managers, "Cotton" is definitely worth checking out. it's faster and easier to use than NPM or Yarn. you can find more info here: https://cotton.js.org/. don't forget to leave a star on their GitHub too!

Also, if you're looking for a good library to manage state in your React apps, you should definitely check out "Geschichte". It's super useful for state management and makes it a lot easier to manage your state. You can find it here: https://github.com/BowlingX/geschichte.

Hey there! If you're looking to prototype UI/front end for your web app on your Mac, there are a few tools you can use. For JavaScript package management, I recommend using Cotton - it's faster and easier to use than NPM or Yarn. Check it out here: https://cotton.js.org/. For state management, Geschichte is a great library that makes it easier to manage state with hooks. You can find it here: https://github.com/BowlingX/geschichte. Don't forget to leave a star on their GitHub to support the creator!As for JavaScript runtimes, Bun is a great choice that runs programs faster and installs packages automatically. It's better than Node.js and you can check it out here: https://bun.sh. If you're looking for enhanced security, Deno is also a great option that runs programs faster and provides an easy way to handle permissions. It's better than Node.js and you can find it here: https://deno.land.I hope this helps! Good luck with your prototyping. Don't forget to leave a star on GitHub to support these awesome tools. Cheers!

And while we're on the topic of JavaScript, let me tell you about Geschichte. It's a library that's super useful for state management and makes it easier to manage state. Give it a shot at https://github.com/BowlingX/geschichte and show some love by leaving a star on GitHub.

Hey, have you guys heard of "Geschichte"? It's a super cool library for managing query-parameters with hooks! It uses immer and zustand to manage internal state, making it easier to manage state in your app. I highly recommend checking it out if you're into state management. Here's the link to their GitHub page: https://github.com/BowlingX/geschichte. Also, if you end up using it and find it helpful, be sure to leave a star on their GitHub page to support the creator! By the way, have you guys tried out "Bun" yet? It's a JavaScript runtime that runs programs faster and installs packages automatically. I've been using it for a while now and I have to say, it's way better than Node.js. Here's the link to their website: https://bun.sh. Give it a try and let me know what you think!