geschichte VS bun

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!

It has a decent compatibility with both Jest and Vitest's APIs (you can track progress here so you can use it as almost a drop-in replacement for either. Just as Node's, it has describe/it, mock, test and others, but with the expect syntax (which I find more readable). For example:

In this third and final article in the series on HTML Streaming, we will explore the practical implementation of the Diff DOM Streaming library in web browsing. This approach will allow any website using web components to retain its state during browsing. We will discuss in detail how to achieve this step by step using VanillaJS and Bun.

At Node Conference 2023, Jarred Sumner (creator of Bun) showed a demo of server components in Bun, so there is at least partial support in that ecosystem. The Bun repo provides bun-plugin-server-components as the official plugin for server components. And while I haven’t looked at it in-depth, Marz claims to be a “React Server Components Framework for Bun”.

Continuously evolving, Bun is currently optimized for MacOS and Linux, with ongoing efforts towards Windows compatibility. Tailored for resource-constrained environments like serverless functions, it emerges as an ideal solution. The Bun team is committed to achieving comprehensive Node.js compatibility and seamless integration with prevalent frameworks. For those intrigued by Bun's potential and want to give it a try, more information is available on its website at https://bun.sh/.

Let’s say you are interested in learning more about Bun and probably give it a try. Bun has a website, where you can learn more about Bun and its features (including all the benchmark data captured in this issue), and here is the link.

Looks like it, it seems the 2% are mostly odd platform specific issues that the authors' did not deem very important (my assumption for the release happening anyway). AFAIK this[1] PR tries to fix them.

[1]: https://github.com/oven-sh/bun/pull/9729

Bun has a solution for it. First of all, it already has a list of trusted dependencies. For them, Bun will execute all necessary scripts by default. Otherwise, you can add it to trustedDependecies in your package.json file. In Bun community usage of trustedDependencies is a hot topic. There are several suggestions on how to improve it.

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

I think maybe I was unclear. I'm talking about writing libraries that abstract across these differences and provide a single API, as sibling describes. I already know it's possible. I made a simple filesystem abstraction here[0] and a very simple HTTP library that uses it here[1]. They both work in Node/Deno and the browser. Unfortunately I ran into issues with Bun's slice implementation[2]. But I suspect there's a much better way of detecting and using the different backends.

[0]: https://github.com/waygate-io/fs-js

[1]: https://github.com/waygate-io/http-js

[2]: https://github.com/oven-sh/bun/issues/7057