Hackaday3D Printed Clock Just Taps It In
https://fed.brid.gy/r/https://hackaday.com/2026/03/21/3d-printed-clock-just-taps-it-in/
3D Printed Clock Just Taps It In https://hackaday.com/2026/03/21/3d-printed-clock-just-taps-it-in/
#Clockhacks #Clock #ESP32 #Golf #Putting #Servo #Time
#Clockhacks #Clock #ESP32 #Golf #Putting #Servo #Time
UndeadLeechWhile working on #servo recently, I came to the realization how much Rust isolates itself from other languages, just by not providing a C interface by default.
We can't write a browser engine for every programming language. While using Servo is a breeze in Rust, using it with any other language seems problematic.
The Linux Kernel managed to adopt Rust, I wrote a Rust WebKit browser, but I'm not sure what the future holds for Servo when it's time for Rust to say goodbye.
Blort™ 🐀Ⓥ🥋☣️Ah yes. I think you're right about the tires. Happy I was wrong! :)
Looking forward to when Kumo is available with Servo from the Flathub repos. Even if it's buggy as all hell, I just want a relatively easily installed option to help test/use/bug report a servo browser to help Servo move forward!
Happy you're doing this work!
Is this a recent change? I just tried installing Kumo from Flathub, and I don't see any option to change browser engine anywhere. The gif you embedded in your post doesn't seem to be showing for me, so if it shows where to enable this, I still haven't been able to see it.
PS Isn't Kumo a big car tire brand? I ,ean, I get that it's a different field, but it seems it could be an issue down the road...
Marco AllegrettiWEFT OS — Post 3 is up: Why Servo, and why now?
If your shell is a web document, the engine isn’t a “dependency” — it becomes a foundation, with a governance model and an upstream workload attached.
I wrote about the Chromium/WebKit/Servo trade, and what “Servo gaps” actually mean for an OS shell.
https://marcoallegretti.me/blog/why-servo-and-why-now/
#weft #servo #rust #wayland
If your shell is a web document, the engine isn’t a “dependency” — it becomes a foundation, with a governance model and an upstream workload attached.
I wrote about the Chromium/WebKit/Servo trade, and what “Servo gaps” actually mean for an OS shell.
https://marcoallegretti.me/blog/why-servo-and-why-now/
#weft #servo #rust #wayland
A little preview of the multi-engine behavior in Kumo:
To quickly try out a website in a different engine, you can just reload it in WebKit/Servo through the context menu.
Kumo will remember which engine was last used for a domain and use that engine for all new tabs for that domain going forward. That way if you're interested in a new browser engine, you can transition one website at a time, rather than requiring a complete browser change.
It seems like many things have improved in #servo since I've last checked it out. Performance isn't perfect, but it does still manage to reach 60-70 FPS while screen recording on a Fairphone 5 (~90 without).
Plenty of work left to do before I can ship it as an alternative engine, but I think this time it might make it upstream rather than sitting in a branch for another year.
January in Servo: preloads, better forms, details styling, and more!
Val Packett 🧉I guess #Servo is now the only serious browser engine taking a stand against slop, even mentioning ethical issues? (Despite one bronze sponsor listed on the homepage being "somethingsomething AI" heh)
We really need to get servo-gtk to a more serious state where epiphany could use it…