windicss VS Quasar Framework

why not use Windi CSS or Tailwind css?

Windi CSS, in contrast to Tachyons, is a very fresh framework. Started in the late December of 2020, it’s already gained a lot of attention and currently sits at respectable 1.5K GitHub stars.

No mention of Windi CSS? Didn't it inspire this?

However I decided it was time to question my own biases. I installed Tailwind Intellisense for VS Code and started up a test project with a starter that included Tailwind (actually it uses Windi, which is a Tailwind compiler). I then started making a basic site, forcing myself to use the utility classes for (most) all of the styling.

For more details, please check windicss

You can check the README of windicss (https://github.com/voorjaar/windicss). Compared with postcss, it runs faster, can be built in real time and does not require plugins such as autoprefixer and purgecss to increase the complexity of configuration. And windicss extends the utilities and variants of tailwindcss. For example, you can directly use p-1.3rem or bg-hex-fff just like atomic css. And we also have a compilation mode, which can combine a line of classes into one to increase the readability of html.

Imagine writing your app once and having it work on web, mobile, and even desktop. That's Quasar for you. It's not just about UI; it's about creating a universal app. With its Material Design components, Quasar lets you customize your app's look while ensuring it performs beautifully across devices.

I have a bit of an obsession with finding the fastest way to launch apps. My goal is to be able to create fully functional MVP's and proofs of concept in less than a day. That means being able to spin up a backend and then implement a frontend as efficiently as possible. For the backend, PocketBase has been my favorite lately. On the frontend I am still trying to find a winner. I like Quasar (VueJS + Capacitor) which is fantastic for web apps, but falls a bit short for mobile apps. I've been eyeing React Native lately especially since Expo offers a ton of great plugins like Location and also supports remote updates.

Cool, could also check out a unified App platform framework:

https://quasar.dev/

Cheers =3

In general... it is often a skill issue with labor pools, as firms accepted Java/JavaScript is almost universally known by juniors.

Apps are in user space, and are often disposable-code after 18 months in most cases. Projects like https://quasar.dev/ offer iPhone/Android/iOS/MacOS/Win11 single code base auto-generated App publishing options, but most people never hear of it given a MacOS build host is required for coverage.

The talk pokes fun at the Ivory tower phenomena, and how small-firm logical assumptions halt-and-catch-fire at scale. =3

https://en.wikipedia.org/wiki/Ivory_tower

In general, people must make a choice between portability, and the breadth of optimizations.

For multi-platform builds, there are single code-base frameworks available:

https://quasar.dev/

For MacOS, Linux Gtk, and Windows native builds there are mature free libraries that allow both FOSS and commercial static linking:

https://wxwidgets.org/

Game engines are designed to solve a single set of use-cases for optimization, and portability is usually terrible outside the current windows release.

Best of luck, =3

Quasar. The enterprise-ready cross-platform Vue framework.

I like this for simple mobile projects:

https://quasar.dev/

In some cases, going with an SVG icon pack etc. can save a bit of space. =3

In the previous article we set up the skeleton of the application with the Quasar framework based on VueJS

It is OK, people wouldn't know what is missing if they never saw the alternative.

"It's hard to even parse this sentence"

Try to cross-compile something on modern MacOS, and handle the DRM signing on another platform. For example, you are still going to need an active Apple Developer account to run https://quasar.dev for MacOS/iOS targets, or users are going to incur a bit of hassle running your code.

It is ok, most people have trouble understanding each other at first. =3