Sergey Bugaev

@bugaevc@floss.social
1.2K Followers
275 Following
3.9K Posts

I hack on GTK / GNOME, GNU Hurd / glibc, wl-clipboard, Darling, SerenityOS / Ladybird, Owl, etc.

I like Rust and dislike Docker.

GitHubhttps://github.com/bugaevc
Pixelfedhttps://pixelfed.social/bugaevc
TZMSK / UTC+03
LINGUASru en eo

@david_chisnall @dvandal @strlcat @davidgerard@circumstances.run I have poured most hours of my last 10 years of life into listening to users and pushing things forward on Wayland even if I personally wouldn't need the feature. I really saddens me that someone would think that Wayland developers don't care.

We do care, but we only have a finite amount of time in our volunteer life. Yes, we don't copy-paste solutions from X11: we try to fully understand the problem space and do better. This does mean that coming to us with technical solutions rather than use-cases tends to be met with "please, explain why you need to do this?".

I don't really know what you mean when you say that we silence criticism. I've read enough in the past years to guarantee that it's not silenced. I appreciate constructive criticism better than rants, rants tend to demoralize me.

I am also saddened about the conspiracy that big corp deprecates X11 against the community's will. There is no single company with a monopoly here, please take a bit of time to look at Wayland developers' employers. Personally, I'm ex-SourceHut and now just a volunteer (my day job is unrelated: SNCF Réseau).

I've never said that X11 was deprecated, and I always tell people to use whatever works best for them. The only reason why X11 has less activity nowadays is because X11 lacks volunteers. (We severely lack volunteers on the Wayland side too.)

People, distros, communities move away from X11 if/when they collectively decide that they should. Nobody's pulling the strings here.

@dvandal @strlcat @davidgerard

Wayland and systemd are both symptoms of the same behaviour, as was PulseAudio:

  • Observe that an existing system has flaws.
  • Don't engage with users to identify use cases.
  • Throw up some half-finished code (with incomplete or nonexistent backwards compatibility) that solves some of the problems of the old system but doesn't address all of its use cases and introduces more problems for other people.
  • Declare that the old thing is deprecated and everyone needs to move to the new thing.
  • Create a load of work in the rest of the ecosystem that other people have to do.
  • Silence all criticism by pointing out that the old thing was imperfect.

And that's the kind of thing that you can only get away with if you're able to act as a monopoly, by employing maintainers at key points across the ecosystem.

The biggest problem with Microsoft was not that their monopoly allowed them to be evil, it was that it allowed them to be stupid. A lot of things in the MS ecosystem are actually bad for Microsoft, but they're pushed out because no one inside MS cares enough to do the right thing and no one outside is able to fix the problems. I, personally, don't want the F/OSS OS ecosystem to end up like that.

"step one is gaining access to the journal on her laptop where she records her innermost thoughts"

🙃 it never occurred to me to log my thoughts using logger(1) or systemd-cat(1), but it makes sense, doesn't it? this way, you can cross-correlate your innermost thoughts with system events such as hard drive read failures, services crashing, and DNS returning bogus results (logger "it's always DNS!")

WIP new Tuba post editor looking hot 🔥

Kudos to @GeopJr for making it happen!

https://github.com/GeopJr/Tuba/pull/623

I had a go at implementing my own static site generator last night, for the hell of it. It was a lot more fun than I expected.

Admittedly it's cobbled together from a lot of pre-existing libraries (axum, pulldown_cmark, tera, etc.) but I was surprised at how easy it was to get something perfectly functional working (just ~400 lines).

It's been years since I properly dug into 'core' web technology, and I'm happy to report that crafting things out of HTML and CSS is just as fun as it always was.

An AmperSand, from the southernmost beach/shore of East Lothian - I'm not sure it actually has a name, but maybe Dunglass Beach? - this afternoon.

I always make these below the line of high tide, and it was particularly pleasing to walk past later and watch the sea in the process of reclaiming it.

#BeachArt #Lettering #AmperSand

Two RFCs have finished FCP, so in the near future you'll be able to have attribute & derive macros that are declarative (i.e. not proc macros).

Thanks @josh for writing these up. Looking forward to RFC 3714, which will render many proc macros obsolete.

https://github.com/rust-lang/rfcs/pull/3697
https://github.com/rust-lang/rfcs/pull/3698

#Rust #RustLang #programming

Declarative `macro_rules!` attribute macros by joshtriplett · Pull Request #3697 · rust-lang/rfcs

Many crates provide attribute macros. Today, this requires defining proc macros, in a separate crate, typically with several additional dependencies adding substantial compilation time, and typical...

GitHub
Unix Errno would be a great Star Wars character name
I love the ios26 random wallpaper from my photos. Every hour it picks an interesting crop and does cool type for the time display. Honestly impressive and a bit of joy every time I grab my phone.

it lives!  JVM in Bash

for now it only has ~5 opcodes implemented, and one virtual method (println). So this is literally the minimal amount of Stuff to get a hello world working

next up, conditionals?

×
🎉 Filmbook is now available on Flathub! 📷

Your film tracking app just got easier to install! You can now get Filmbook directly from Flathub:
https://flathub.org/apps/page.codeberg.bjawebos.Filmbook

Built with Rust & GTK4/libadwaita, Filmbook helps analog photographers keep track of their film usage with a smooth, modern interface that works great on desktop Linux and even Linux phones like the Librem 5 and Pinephone Pro!

Calling all analog photographers: I need your creative input! What features are you missing? What would make your film photography workflow even smoother? Your ideas will help shape the future of Filmbook.

Share your thoughts and join our community:
https://codeberg.org/bjawebos/filmbook

#filmphotography #analogphotography #flathub #linux #opensource #rustlang #gtk #filmbook #community #librem5 #pinephone
@bjawebos maximally non-creative question - for which usecases it is ever needed? 😯
@torf The use case is initially very personal. I have a Linux cell phone and never have a pen and paper with me. I also have a lot of analog cameras and not all of them have a holder on the back where I can put the film carton in. The situation for me was that I often had cameras where I was no longer sure whether there was film in them and if so, which one. I tried using a pen and a piece of paper, but that didn't work for me at all. Now I can enter everything in the Filmbook app and always have an overview. So far it's working very well because I always have my Linux phone with me. Maybe other people feel the same way.
@bjawebos Are there any binaries for Macs for a not-very-techie user?
@carusb Unfortunately, I don't have plans for Mac binaries in the near future. There are two main challenges: I don't have access to Mac hardware for testing, and GTK4 apps don't provide the native macOS look and feel that Mac users typically expect - they maintain their Linux/GNOME appearance instead.
While it's technically possible to run GTK4 applications on macOS (and Windows), without proper testing devices I can't ensure a good user experience. Since Filmbook is open source (AGPL-3), anyone is welcome to attempt a Mac port, and I'd be happy to support such efforts!
For now, the app works great on Linux systems and is available through Flathub for easy installation. If there's significant demand from Mac users, I might reconsider in the future.

@bjawebos Thanks for the very reasonable explanation, Björn! For me at the moment it would be of marginal benefit, if any; I only have film loaded in 2 cameras at the mo, and the MX has the box tab in its slot. The other is a mju II.

I do have a Notes file of films this year, including MMYY𝛼cccBW film lens filter location dev, eg "2505CPMXBW Pan F 50 M35-2 yellow Ken[ilworth] HC-110 E", if that's any help. Those go into folder names and then to C1Pro Albums, then metadata tags.

@carusb That is definitely a help. It's also exciting how different the processes are for every photographer.