gnome-shell-extension-caffeine VS b-decoded

Für Gnome gibt es das unter dem Namen "caffeine" https://github.com/eonpatapon/gnome-shell-extension-caffeine. Sehr hilfreich um den Laptop während des Kompilierens wach zu halten

Make a Store from where people can install and upload extensions to, and the extensions should be mostly divided into 2 categories: functionality adding extension which has nothing to do with UI (like Caffeine Gnome extension) and miscellaneous extensions (which changes the UI as well as add some functionality, Like Cosmic Workspaces Gnome Extension). This store should also host widgets preferably created using EWW (because it is also written in Rust and would fit quite well in Cosmic DE ecosystem.....or it can be forked to match the design language of Cosmic DE, thus maintaining design consistency even in the widgets).

eonpatapon/gnome-shell-extension-caffeine

or the more easier ways

https://github.com/eonpatapon/gnome-shell-extension-caffeine

Just use b

I use b

I used to believe this but i don't anymore.

From https://github.com/tlack/b-decoded

Arthur is famous for his very dense programming style. Most C programmers would scream when seeing this code.

In his view (and others in the terse scene), it is much better to have everything in your application readable on the screen at once than to have great names for things or a lot of white space to comfort the first timer reader.

To them, once you've sufficiently studied that screen or two of code, you can understand all of it at the same time. If it's spread out over thousands of files, it's very difficult to understand all of it, which leads to bugs, unnecessary abstraction, and the need for advanced tooling just to work with your own project's code.

He wants to see the code "all at once" so he can understand all of its behavior without paging around and shifting his focus to another tab, window, etc. To get there he makes a lot of tradeoffs in terms of the code formatting and naming conventions. He also, in b, creates a dense set of interlocking macros and abstractions that can make the code very hard to follow.

Critics and the uninitiated say that his code is like old school modem line noise: random punctuation intermixed with bits of understandable code. I would suggest that he's actually quite careful with the abstractions he chooses and they are actually not always the most dense, highly compressed code structures available to him. He chooses wisely and his code rewards deep study.

Interview with Arthur Whitney: https://queue.acm.org/detail.cfm?id=1531242

Here's some links relating to this style of code that you may find useful:

https://docs.google.com/document/d/1W83ME5JecI2hd5hAUqQ1BVF3...

https://github.com/tlack/b-decoded

https://chat.stackexchange.com/rooms/90748/conversation/ngn-...

They're not 1.5 paragraphs per line, but enough to give a taste of the implementation style.

I could write a whole compiler in that time.

Here is a link: https://github.com/tlack/b-decoded