Eww: ElKowars wacky widgets(github.com) |
Eww: ElKowars wacky widgets(github.com) |
I haven’t used Janet much other than going through the beginning of this book here, but here’s the link to a good book and the Rust bindings of you want to check it out.
A really good (and free!) book on Janet: https://janet.guide/
And the Rust bindings: https://docs.rs/janetrs/latest/janetrs/
[1] http://mikehadlow.blogspot.com/2012/05/configuration-complex...
The features and the visual results are impressive. I wrote 400 lines of configuration and about ten scripts for it but in the end the instability chilled me.
Sometimes tooltips refuse to display, windows open in duplicate or refuse to close, the logs indicate json errors without any apparent reasons or consequences.
I will come back to see the progress in a few months.
Since then I tried i3status-rust, there are less possibilities visually but the same interactive features and its really fast stable.
0: https://old.reddit.com/r/unixporn/comments/wlscxa/fvwm_an_es...
Being written using GTK and thus also styled in GTK CSS makes a big impact here, of course
From the website[1]
(Edit: The reason I say it's 'unfortunately' named is that not everyone has the privilege to load pages containing terms like 'porn' without the risk of trouble in their workplace, country, or otherwise. I have no problem with the name personally, and it's a fantastic sub and Discord.)
You could call your project bacon soaked in milk but it might needlessly deter Muslims and Jews.
Everyone has the option of not browsing HN at work.
- The original goal of eww was to be two-dimensional polybar with support for full visuals and CSS, rather than just colored text. This means that my target audience, at least initially, was also more the polybar crowd than the awesomeWM crowd. Eww aims to be usable without really needing to know how to program, and aims to provide declarative UI description language that reduces complexity of state management and logic as much as possible. This is, arguably, a goal I've at least somewhat reached -- primarily given the fact that eww DID grow quite fast, and did enable lots of people to do more interesting UI designs than other projects (such as AwesomeWM) did. "Widgets for everyone" is a tagline I don't wanna leave, and thus requiring users to do full-on scripting is not something I'd wanna do easily.
- if you remove yuck and it's state management architecture from eww, you'll be left with quite little. Thus, there would at that point be little added value over existing GTK wrappers. The thing that makes eww appealing (at least IMO) is that it does simplify lots of the most commonly needed things down to a very simple state and UI structure, and provides a great iteration-cycle with great error messages. This would be very hard to keep when turning it into a regular, more imperative library
If we cater to a specific set of people, it will be a discrimination against all others.
I think the most tolerant solution is to let people control their own bubbles of what they want to see.