“My source is that I MADE IT THE FUCK UP”

• President of the USA (probably in a videogame)

What’s so bad about the Rust compiler? I know it’s slow, but given all the analysis it’s doing, it makes sense. And, from my own experience, setting correct optimization levels for dependencies along with a good linker makes incremental builds plenty fast.

I have been toying with the idea of forking Servo to make a scriptable keyboard-driven browser, like Nyxt but with something else instead of Lisp.

Probably too huge of a project for one hooman though.

deleted by creator

Despite whatever your lead/manager says, there is always an option to nuke it from low orbit and start over.

As a programmer, I concur. I sit on my arse all day pushing keys , anybody can do that.

Hey what if my software is paid, but you can purchase it for N money or more, with an input field?

Because that I’ve seen a lot, and it sounds suspiciously like what you’re describing, yet completely normal.

Edited for grammar

A genuinely cool and somewhat lean alternative to Electron!

It’s not that native UIs are lagging behind, there is a whole set of reasons.

TL;DR: browsers, as opposed to desktop apps, are stardartized - because they were originally designed to display and deliver text documents. We were never supposed to build complex application UIs on a web stack.

First, there is no standard way of making native UI on a desktop. Every OS uses it’s own solution, while Linux offers several different ones. Browsers rely on a set of open standards developed specifically for the web, and even there not everything works exactly the same.

Second, browsers are designed to draw a very specific kind of UI through a very specific rendering mode - they run an immutable hierarchy of elements through layouting and painting engines. It works great for documents, but it becomes extremely unweildy for most other things, which is why we have an entire zoo of different UI implementations (crutches, most of them) for browsers.

On the desktop we often make a choice of what UI technology would fit best our purpose. For a game engine I would use an immediate-mode UI solution like ImGUI, for the ease of prototyping, integration and fast iterations.

For consumer software I might choose between something like QT or GTK for robust functionality, reliable performance, acessibility and community support. Mobile platforms come with their own native UI solutions.

For data-intensive UIs and heavy editors (e.g. CAD, video and music production, games) I might need to designan entirely new rendering pipeline to comply with users requirements for ergonomics, speed, latency etc.

It is also easy to notice that as a team or employer, it is often much easier to hire someone for web stack, than for native development. Simply put, more people can effectively code in JS, so we get more JS and tech like Electron enables that.

If you are interested in a single solution that will get you nice results in general, no matter the platform - you might see some success with projects like Flutter or OrbTK.

UI rendering in general is a deep and very rewarding rabbit hole. If you are in the mood, this article by Raph Levien gives a good overview of existing architectures: https://raphlinus.github.io/rust/gui/2022/05/07/ui-architecture.html

What do you mean, “people like you”?

I genuinely like this about you now

Does everyone have this one friend, who instead of typing out one message, splits their thoughts into 6-32 smaller messages sent in quick succession?

Also, I wish there was a way to throttle or debounce notifications on my phone.

I set three alarms 7 minutes apart. 7 minutes is enough for a quick snooze without frustration, but not long enough to actually fall asleep.

Also, I used to use smartwatch with a phase-aware alarm clock, highly recommend.

Ok real talk here for a minute. If, by any chance, some dufus has put a lightbulb in their month and need help removing it, grab a sturdy cloth towel, pass it into their mouth through the corners and gently wrap the glass part of the lightbulb in the cloth. When you’re done, all corners of the cloth should be hanging outside persons mouth. Their teeth should not touch the glass directly - only through the cloth. This way when the glass breaks, all the pieces will be contained I the cloth for an easy and, if you are careful, harmless removal.

The safest way to crack the bulb once you’ve wrapped it in cloth is to GENTLY tap the bottom jaw - imagine a 4 year-old landing an uppercut. The glass is very thin and cracks easily, - no need for much force.

Of course, better not get into such a situation in the first place. Stay safe, folks!

Oh I love these!