packages VS NectarJS

I will be happy for any feedback! The Stylify is still a new Library and there is a lot of space for improvement 🙂.

Hi all!I have made a guide on how to switch from Styled Components CSS-in-JS to Stylify Utility-First CSS.Stylify is a library that uses CSS-like selectors to generate optimized utility-first CSS based on what you write.I would be happy for any feedback if it is understandable :).Thanks in advance for any response!

Say goodbye to CSS-in-JS and Runtime scripts for injecting and compiling CSS and hello to lightning-fast coding with Stylify Utility-First CSS. As a React frontend engineer, you know the importance of efficient, streamlined solutions that don't sacrifice style or functionality. And that's exactly what Stylify offers.

const compilerConfig = { // CSS variables are note enabled by default in Stylify replaceVariablesByCssVariables: true, // https://stylifycss.com/docs/stylify/compiler#variables variabels: { textFontSize: '12px', textColor: '#000', // Tries to match a screen, can be sm, md, lg... minw400px: { textFontSize: '18px' }, // For a @media (prefer-color-scheme: dark) dark: { textColor: '#fff' }, // When screen is not found, // it falls back to a custom selector // in this case element with the ".dark" class // which will very probably be the root (html el) '.dark': { textColor: '#fff' }, } };

Apart from the colors module, there is a typography.module.css. You might want to remove it as well and rewrite these classes into Stylify CSS components using Stylify dynamic components syntax.

Stylify + SvelteKit. Style your SvelteKit website faster with Stylify. Don't study selectors and syntax. Use pure CSS syntax and get generated CSS with advanced optimization for production.

const { Bundler } = require('@stylify/bundler'); const isDev = process.argv[process.argv.length - 1] === '--w'; const bundler = new Bundler({ watchFiles: isDev, // Optional compiler: { mangleSelectors: !isDev, // https://stylifycss.com/docs/stylify/compiler#variables variables: {}, // https://stylifycss.com/docs/stylify/compiler#macros macros: {}, // https://stylifycss.com/docs/stylify/compiler#components components: {}, // ... } }); // This bundles all CSS into one file // You can configure the Bundler to bundle CSS for each page separately // See bundler link below bundler.bundle([ { files: ['./app/**/*.tsx'], outputFile: './app/styles/stylify.css' }, ]);

I have made a Stylify CSS that uses CSS-like selectors to generate optimized utility-first CSS. It can be integrated into various tools: Next, Vue, Angular, Next, Nuxt.

The first google result for "JS to binary" was this: https://github.com/NerdLang/nerd, you might try to give it a spin. However these kinds of solutions come with a lot of caveats as of how to handle stdio, memory, and many other things that other languages, such as C and Go, handle natively as part of their stdlib...

for anyone else interested in approaches to this here's another abandoned attempt to transpile js to c https://github.com/NectarJS/nectarjs

The question is just whether there's sufficient purpose and value for that. https://github.com/NectarJS/nectarjs

Rails/Ruby performance has improved:

https://medium.com/retention-science/ruby-is-still-a-diamond...

Alhough, compiling Javascript to binary makes code even faster https://nectar.js.org , although I wish that project would get more love with bugfixes https://github.com/NectarJS/nectarjs/issues

Technically speaking, this is bollocks. You can compile javascript to machine code for Windows, Mac, and Linux if you so choose, there is even a compiler for arduino, which quite obviously does not and cannot run a javascript interpreter. The point is that, in our modern world, there is no such thing as a scripting language. Virtually any language can be compiled to bytecode to run in the Java JVM, and many (even surprising ones like javascript) can be compiled AOT to native machine code.

Object pascal to JS? Why not just write JS directly? Can you leverage Lazarus? For JS to WASM, there's NectarJs https://github.com/NectarJS/nectarjs but docs appear to be nonexistent :(