I've mentioned this a few times but never publicly announced it, so consider this the announcement.
I've also ported Owl, my Cocoa Wayland compositor, from OS X to the Hurd using GNUstep.
Here's a screenshot of weston-terminal and weston-flower, running on Owl on GNUstep on Hurd, with X forwarded from a QEMU VM via SSH.
Here's another pretty screenshot for you'all
I've made a mock-up to illustrate my ideas about the next-gen terminal experience!
• the pathbar
• username, hostname and git branch displayed in the UI, shrinking the shell prompt back to just a $
• commands as cards
• syntax highlighting, including graying out the output a bit to differentiate it from commands themselves
• autocompletion (displayed in a native widget)
• built-in error handling options
• the time each command took (on the right)
I never did the #introductions thing, so here goes!
I live in Moscow, 🇷🇺 & currently study at CMC MSU.
I work at SmartDec where I write a cool static analyzer for Java & Kotlin. I'm also a tech editor at tproger.ru
I'm on the Darling team; we hack on macOS internals to make apps & programs targeting Darwin run on Linux/Android.
What comes to mind are these two blog posts from this year:
some horror stories there - about Rust, Go, and Python.
and I remember @neauoire describing the absurd bandwidth usage by Rust's cargo downloading trees of dependencies.
@aday blogged about some of the platform work we've been doing lately.
tl;dr: GNOME apps are going to look so dope in a few months, it's kind of ridiculous :P
The on-screen keyboard in #Windows11 is so much better than it was in 10 that I now rarely feel the need to flip over & use the physical keyboard for entering small pieces of text, such as search queries or short instant messages. Previously I'd use the physical keyboard if I had it attached; now I only reach for it when typing several sentences of text (or code).
The OSK is still nowhere as good as Gboard is on Android though :|
To be clear: I don't necessarily agree, but it's very nice to see someone appreciate our work & love what we love
"But my secret second wish, is that the whole UI side of SerenityOS could be ported in its entirety to Linux. Finally, for the first time in decades, a pragmatic kernel with a pragmatic user interface. I would happily ditch GNOME, KDE, Sway, i3, Wayland, Pulseaudio, pipewire, Freetype2, Network Manager and the other myriad of components of the current Linux UI stack for something designed with passion and a coherent vision."
Overhead on the 🍊 site
Dear #Clang developers, this ‘ToolChains/Linux.cpp’ file is a textbook example of what not do do:
I've been working on a little demo app for the rust portals library ashpd and I finally released it on Flathub.
Source code is at https://github.com/bilelmoussaoui/ashpd/tree/master/ashpd-demo
Also please don't use this post to hate on GNOME.
GNOME is good, even if they sometimes make choices that I disagree with.
That's because processes exist on a deeper level, no matter what starts and manages them. Sure, some integration with systemd *when it's available* is nice (such as: showing what unit or machine a process belongs to, and letting you stop a unit instead of killing a process).
Well, the same goes for network interfaces.
P. S. What I'm saying is emphatically *not* that NM does nothing useful and that I'd expect everything to work the same without it.
Let's switch topics for a second: we can all agree systemd does some useful things (even if we disagree on whether it does them right), and I think everyone would be surprised to see generic process manager app not work without systemd (& telling you to contact Debian).
What kind of sorcery is this? 🦀
The compiler sees I'm transmuting a literal zero, knows there's a reference inside Context, and emits a warning. Mind absolutely blown.
(Yes, I'm intentionally creating a broken Context; I just needed to check what some code compiles to.)
As cool as NetworkManager may be, there of course are many different solutions for configuring and bringing up your network interfaces, and they vary from system to system (does NM even support the BSDs?).
The actual state of network interfaces — which interfaces there are, which are assigned an address, and so on — is independent from which tool was used to configure them, and is available from the kernel.
Reminder that this is the sad state of affairs:
GNOME refuses to see network interfaces unless they are configured by NetworkManager (here, I've used systemd-networkd), as if they don't exist. The Settings app says "Oops, something has gone wrong. Please contact your software vendor.", but at least gives you a clue for figuring out what is it that it doesn't like.
And the upstream response has been: "unless we expect it to replace NetworkManager eventually, we are not going to add support".
Rust, objc, Kotlin, C, Python
Linux, GNOME; Android
Wayland; Plan 9
Microkernels, the Hurd
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!