Sergey Bugaev @bugaevc@mastodon.technology

I've mentioned this a few times but never publicly announced it, so consider this the announcement.

Yes, I have ported #Wayland (along with a few Weston clients and wl-clipboard) to the #Hurd (that's what I wrote the epoll server for!)

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 did it!!!!

TL;DR: I have ported #Wayland to #Darwin and written my own Wayland compositor using Cocoa 😎

0/5

I've made a mock-up to illustrate my ideas about the next-gen terminal experience!

Featuring:
• 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'm a software developer who loves to hack on stuff. Some of my interests: #Linux, #Rust, #Kotlin, #Android, #Python, #objc, pure #C, #Darwin, #Wayland, #GNOME, & there's more.

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.

Apparently there's very little info online about D'OLE internals

"nxorb" is about as much as I can find after days of googling

Just used bpftrace to debug an issue with my system for the first time

Admittedly, I could've used good ol' strace for this particular use case, but I figured I'd use this as an opportunity to get more familiar with bpftrace

#SerenityOS #unixporn

Ah, the wonderful world of Unix, where you can get unexpectedly killed for writing into your own stderr

Oh, and the moment you get killed is controlled by some other, possibly less privileged process

What could possibly go wrong...

Tired: GNOME on a tablet
Wired: GNOME on a phone
Inspired: GNOME on a smartwatch

"smelling_salts - Wake futures using an epoll thread without depending on an executor / runtime."

that's... not how this works

A sane thing is to have your CI (or your local build system) detect if there were any warnings (whether compiler warnings at build time or logged warnings at runtime) and notify you (but not fail your build either).

Using Werror is much like aborting your app when you wanted to log a warning.

Warnings are for when something is not quite right. Aborts are for when something has gone so terribly wrong that it makes no sense to continue (like a fundamental assumption or invariant was violated).

Do you want to know if your program logs any warnings? Surely! But do you want to just crash it in case of any warnings, in hope that that will make the user report the warning to you? No!