The epic event-driven browser language for UI with functionality in one-liner CSS. Over 100 incredible CSS commands for DOM manipulation, ajax, reactive variables, single-page application routing, and lots more. Could CSS be the JavaScript framework of the future?
This is an issue to monitor the production of the new docs website, which is now underway, plus the change of name and repo to "Action CSS" and the new version number of "0.9". Why "0.9" and not "1.0"? Because, frankly, there aren't enough people using it yet, and I'm not convinced all the bugs have been found yet.
I've been focusing more recently on website dev with ACSS rather than new features, because the project suffers from a lack of real-world testers and I needed to up my certainty that the core does what it says it does.
There is a general psychosis in software development that unless there is a new release, the project has been abandoned. That is just bollocks. My desk lamp is over 20 years old, but I don't consider it to be a "legacy" desk lamp. It does the job well and optimumly, and doesn't require time-wasting upgrades every 6 months.
The core is now in a much more stable state where I'm not finding so many bugs, and at work we've recently successfully coded a full commercial flagship SPA using only HTML, CSS and ACSS, and not needed to use any raw JS or any other plugin or library (https://whiteline.co.uk - the installer's website). The prototype for that website did initially use GSAP, but I removed it for performance reasons. Two more very different public-facing websites will also be produced this year at my workplace. I don't know of a faster image-heavy, UI heavy, multi-page SPA, even on the opposite side of the planet (with no CDN or any particular focus on optimum image delivery). It's hosted in London England, and I tested it in New Zealand last week and it's still quicker than local New Zealand websites. That's good enough for me, so it's time for a upgrade for the project.
The new docs will include a lot more real-world hints and tips to solve situations. The current docs don't contain enough of those. And there are loads of performance tricks that I use when I code, and these aren't particularly well documented yet.
With the new release, there will also be tips on how to use intersection observer to speed things up. There is a new render-when-visible feature in the latest core branch for components, and I may add something similar into the language for general image delivery, because that needs to be manually setup in ACSS at the moment. I'm still ironing out the syntax for that because image delivery can trigger animations and sequences and there are a few things to consider. Rendering components and images with intersection observer, though, is the key to fast initial delivery of a large page.
As far as I know, only ACSS has "permanent dynamic event" functionality - ie. load the events once for a whole website and forget about them - they will kick in when needed. Because of this, you can get very flexible and simple about delivery of new HTML to the page, and that is such a key benefit to ACSS over other solutions that it needs to be highlighted more in the docs.
bob2517
commented
8 months ago
This is an issue to monitor the production of the new docs website, which is now underway, plus the change of name and repo to "Action CSS" and the new version number of "0.9". Why "0.9" and not "1.0"? Because, frankly, there aren't enough people using it yet, and I'm not convinced all the bugs have been found yet.
I've been focusing more recently on website dev with ACSS rather than new features, because the project suffers from a lack of real-world testers and I needed to up my certainty that the core does what it says it does.
There is a general psychosis in software development that unless there is a new release, the project has been abandoned. That is just bollocks. My desk lamp is over 20 years old, but I don't consider it to be a "legacy" desk lamp. It does the job well and optimumly, and doesn't require time-wasting upgrades every 6 months.
The core is now in a much more stable state where I'm not finding so many bugs, and at work we've recently successfully coded a full commercial flagship SPA using only HTML, CSS and ACSS, and not needed to use any raw JS or any other plugin or library (https://whiteline.co.uk - the installer's website). The prototype for that website did initially use GSAP, but I removed it for performance reasons. Two more very different public-facing websites will also be produced this year at my workplace. I don't know of a faster image-heavy, UI heavy, multi-page SPA, even on the opposite side of the planet (with no CDN or any particular focus on optimum image delivery). It's hosted in London England, and I tested it in New Zealand last week and it's still quicker than local New Zealand websites. That's good enough for me, so it's time for a upgrade for the project.
The new docs will include a lot more real-world hints and tips to solve situations. The current docs don't contain enough of those. And there are loads of performance tricks that I use when I code, and these aren't particularly well documented yet.
With the new release, there will also be tips on how to use intersection observer to speed things up. There is a new render-when-visible feature in the latest core branch for components, and I may add something similar into the language for general image delivery, because that needs to be manually setup in ACSS at the moment. I'm still ironing out the syntax for that because image delivery can trigger animations and sequences and there are a few things to consider. Rendering components and images with intersection observer, though, is the key to fast initial delivery of a large page.
As far as I know, only ACSS has "permanent dynamic event" functionality - ie. load the events once for a whole website and forget about them - they will kick in when needed. Because of this, you can get very flexible and simple about delivery of new HTML to the page, and that is such a key benefit to ACSS over other solutions that it needs to be highlighted more in the docs.