awesome-tagged-templates VS cinnamon

When zx first appeared, it was a tiny esm script that just proposed a new idea for how child_process.spawn API could be enhanced with string template literals.

The template combines HTML and JavaScript. To understand this approach, consider how PHP pages are generated. In PHP, code is embedded within the HTML. Similarly, this library leverages JavaScript template literals to achieve the same objective. From the definition: "Template literals are literals delimited with backtick (`) characters, allowing for multi-line strings, string interpolation with embedded expressions, and special constructs called tagged templates".

The numbers we are printing are monetary values so they are missing a decimal value and a currency symbol. One way we can do this is by using JavaScript template literals to append and prepend the pieces we are missing.

Tagged templates[0], the language feature that enables this, were introduced in ECMAScript 2015 apparently – arguably at least somewhat new in the lifespan of JavaScript. :)

Java is getting a similar feature with template processors[1]. It would be nice to have it in Python as well – i.e. not just f-strings, but something that (like tagged templates) allows a template function process the interpolated values to properly encode them for whatever language is appropriate (e.g. shell, SQL, HTML, etc.).

[0] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

[1] https://openjdk.org/jeps/459

References: Template literals (Template strings)

We are using a string template literal to create the tag and the ${} syntax to provide string interpolation, that is, substituting the values of href and altText into our string.

In TypeScript, a string literal type is a type that represents a specific set of string values. For example, the type "red" | "green" | "blue" represents the set of three string values "red", "green", and "blue". Template literal types allow you to perform operations on these string literal types using the same syntax as template literal strings in JavaScript.

The example also showcases the use of inline templates, employing JavaScript Template Literals. The JSON data obtained from the GET request is accessible through the "data" variable.

These are called "tagged templates": https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

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.