cinnamon VS execa

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.

I’m partial to Sindre Sorhus’ execa, this document outlines the differences:

https://github.com/sindresorhus/execa/blob/main/docs/scripts...

Yeah, or over https://github.com/sindresorhus/execa?

And given the existence of those npm packages, is there any aspect of Bun Shell that required it to be built into the Bun runtime instead of published to npm?

For something which works across all JS runtimes (Deno, Node) and achieves basically the same, check out the popular JS library Execa[1]. Works like a charm!

[1]: https://github.com/sindresorhus/execa

To simplify the process of running the commands, I will use execa - abstraction library on top of Node.js child_process methods.

Hello, this is an interesting problem. At https://stacktape.com (where we're creating a developer-friendly abstraction of AWS), we're recommending 2 options: - use a "deployment script" (basically a custom-resource lambda function that runs during the CloudFormation deployment). You can install prisma into it, and then execute the migration command from the lambda function using something like execa, if you're using Javascript/Typescript. You can easily do this with Stacktape anytime. - use a bastion (EC2) instance (deployed to the the VPC where your RDS db is). The cheapest instances cost ~4.5$/month, so it shoudln't be too costly. You can also securely connect to it using EC2 instance connect, that leverages IAM to grant permissions to connect to it. (this is something we're currently implementing as Stacktape, and will be ready in ~2 weeks).

For FE, it’s usually Cypress or Playwright; for BE, it’s to run a server and start sending requests; for CLI, I like the tool called execa.

Since version 6 execa is pure ES module. An attempt to import a package into NestJS project results in an error:

Essentially when I run this from my shell I get a listing of keymaps configured for vim. However, when I run it from a program without a PTY or TTY (e.g., via Rust's Command or Node's execa) I get an exit code of 0 and no output.