cinnamon VS bun

Many mobile apps are written in JS/TS with React Native.

Linux desktop environments like Cinnamon [1] also use JavaScript for the UI. Linux Mint with Cinnamon is invariably among the top 3 Linux desktop distributions (on distrowatch [2]).

If anything, stats probably don't accurately capture how ubiquitous JS is.

[1] https://github.com/linuxmint/cinnamon

Will it be ported to Gutter and Cinnamon? There's a feature request open from 2022 but no answer https://github.com/linuxmint/cinnamon/issues/11141

I agree that there is a balance between customization and "cleanness" in design and implementation.

However, I think the GNOME 3 and 4 designers went too far and alienated many users:

https://www.zdnet.com/article/linus-torvalds-finds-gnome-3-4...

https://medium.com/@fulalas/gnome-42-the-nonsense-continues-...

https://www.reddit.com/r/linux/comments/wte7tr/gnomes_design...

https://linuxreviews.org/GNOME_Developers_have_Made_Their_Mo...

https://www.osnews.com/story/133955/gnome-to-prevent-theming...

When a designer's "coherent vision" eclipses the needs of the software's users then users get frustrated and either fork the project or go to another project. MATE (https://mate-desktop.org/), Cinnamon (https://github.com/linuxmint/Cinnamon), and Unity (https://unityd.org/) exist largely because of how far the GNOME 3 designers went and how they were not willing to compromise their "coherent vision":

https://bbs.archlinux.org/viewtopic.php?id=121162

https://blog.linuxmint.com/?p=1910

https://web.archive.org/web/20101129161856/http://www.pcworl...

I'm not sure what the devs want to see in a case like this, but I'd try to report it either on the LinuxMint-Forums or on the cinnamon issue tracker on github.

And I read Cinnamon being not yet out with a Wayland session as meaning that it’s in the works, but according to the Cinnamon team, “We still don't have any specific plans for implementing Wayland support…and we're not in a hurry to do so” (https://github.com/linuxmint/cinnamon/issues/10787)

Mind you, it's much easier to crash a Wayland compositor than an X11 window manager because so much more has to be done in the compositor process; Cinnamon devs mentioned this flaw as a major reason they won't support Wayland yet, because if a panel widget crashes, it will also crash the entire desktop.

I tried a few searches through open cinnamon issues but nothing really stood out yet OTOH, I know some of the recent changes to Nemo/Cinnamon had caused issues which I've run into myself in F37 (such as the new themes, some Nemo drag-and-drop issues, and another issue with Nemo's input focus when clicking the toolbar button to a new folder while you are renaming a file) so still plausible this could be a Cinnamon-specific bug.

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