Cassette is a GUI application framework written in C11, with a UI inspired by the cassette-futurism aesthetic. Built for modern POSIX systems, it’s made out of three libraries: CGUI, CCFG and COBJ. Cassette is free and open-source software, licensed under the LGPL-3.0.
↫ Cassette GitHub page
Upon first reading this description, you might wonder what a “cassette-futurism aesthetic” really is, but once you take a look at the screenshots of what Cassette can do, you immediately understand what it means. It’s still in the alpha stage and there’s lot still to do, but what it has now is already something quite unique I don’t think the major toolkits really cater to or can even pull off.
There’s an example application that’s focused on showing some system stats, and that’s exactly the kind of stuff this seems a great fit for: good-looking, small widget-like applications showing glanceable information.
On the main page of OSnews, the title of this post isn’t visible or clickable.
It’s a bug that only happens when the article starts with a *blockquote*.
@thom-holwerda : you should fix your WP template.
I’m so annoyed with it that I decided to fix it with a small little tweak: insert something before the blockquote.
Just run this in the browser console to fix it:
jQuery(‘.front-view-content.full-post > blockquote:first-child’).parent().prepend(‘ ‘)
See the code here : https://gist.github.com/dungsaga/786b365fd32bb625960661c7d2bd993f
there’s a better fix from https://mstdn.social/@[email protected]/113971810490442290
Just tweak the CSS styles for the titles:
jQuery(‘.front-view-content.full-post’).css(‘clear’,’both’)
if you have a web extension that can customize websites (such as Stylus, Stylish, uBlockOrigin …), you can also fix it by adding attribute “clear:both” for .front-view-content.full-post
or .front-view-content.full-post > blockquote
We have over-engineered so many layers of caching that even though it was fixed promptly, getting all of the caches (Cloudflare, host CDN, WP, performance plugins, ISP, local browser) cleared was… surprisingly difficult.
Adam Scheinberg,
Too many platforms succumb to a bloat problem, this ends up being fixed by adding more hardware & cache resources. Older websites tended to not need server side caching because the code that generated the website was already performant. Relying on cache to solve performance problems can incur problems.
1) It requires more hardware & expense.
2) Some platforms (I’m thinking magento in particular here) are so slow that populating the initial page cache is problematic and if users navigate to pages that aren’t cached they experience major performance problems.
3) When content/resources are updated, caches will end up distributing old content.
The best way by far to solve #3 is to add url parameters that derive from the content, such as a version or timestamp. This way all pages that use a resource can disseminate information about whether the resource has changed. However most platforms don’t do this and instead rely on caches to timeout or users to clear caches and refresh the page, which ends up creating more traffic and delay.
Using developer tools, I notice this CSS file is uncached. Was this done on purpose? It has a version number, meaning that adjusting the version number every time it’s changed would inform the browser to request a new resources, thereby bypassing every single cache standing in the way of updates.
http://www.osnews.com/wp-includes/css/admin-bar.min.css?ver=6.7.1
Of course it would be nice if wordpress just handled it automatically so that all resources could update the moment files are touched. I’m a big fan of making computers do the work.
how fresh it looks.
A desktop environment with this would be super cool.