Linux seems like the opposite to me a slow marathon to achieve perfection. With pipewire, systemd and wayland there's less cruft than ever and you get the best out-of-the-box experience since it's inception.
Woah now, saying something positive about systemd will bring a bunch of crusty greybeards out of the woodwork who want their Linux to be as close to BSD4.4 as possible.
Jokes aside, I'm in agreement. Audio was still slightly buggy for me using a Elgato XLR USB interface, but it consistently worked with annoying workarounds. Linux is in a very good place for even normal consumers these days, I'm hoping Valve ends up making SteamOS a generalized gaming platform that will pull more market share away from Windows in that specific niche. I'm so ready.
I have the occasional annoyance like "VLC has choppy audio for a few seconds after I seek," and "Gnome has gone full douchebag with notifications for everything and removing all the settings."
Other than that, though, Ubuntu on any old laptop (expensive thinkpads are my favorite) is my go-to daily driver. Except at work where I'm learning to deal with a (new, shiny, powerful) Macbook that I will use to... connect to a Linux VM because that's the only way to work on our software. Seriously, a whole fleet of zillion dollar macbooks so we can all ssh into beefy VMs to build/test/deploy on Linux.
IT onboarding made a point that if you want to get a Windows laptop and wipe it for Linux, you need permission and a "good reason." How about "this is stupid just let me work on stuff." Of course it's about tech support and security, which is fair enough but I feel like they have it backwards. Support Linux and then require special permission for the $4000 ssh client...
After spending a couple of days with homebrew and building some things natively on aarch64, though, I might make a hobby out of moving stuff local. It really is a beautiful machine.
I rarely do. Working in the automotive industry (not Bosch, though) made me dislike cars even more than I did before, all the safety stuff (AUTOSAR, MISRA, ...) is theater.
I was writing a custom widget for iced (the Rust GUI library) and I was getting a panic due to some fancy logic I was trying to do. I guess the shortest description I can say is that it was a combination of what appeared to be a caching issue at first, but the real cause turned out to be some method shadowing where I was using a struct's method where I meant to use the trait's method.
I had made the specific operation generic (moving it out of the struct and into a trait) but forgot to delete it from the struct, so I was calling the incorrect function. Claude pinpointed the cache issue immediately when I just dumped two files into the context and asked it:
somewhere in my codebase I'm triggering a perform() on the editor but the next call on highlight() panics because `Line layout should be cached`
what am I missing? do I need to do something after perform() to re-cache the layout?
at first that seemed to fix the issue, but other errors persisted. so we kept debugging together until we found the root cause. either way I knew where to look thanks to its assistance
>Aurora is Amazon's own relational database. You can't run it yourself, only with Amazon. It can pretend to be either Postgres or MySQL. And it'll be cheaper and faster and have higher availability. But it won't be the exact same bits and bytes as your own Postgres, so there's some risks.
That doesn't ring true to me. From my understanding rds aurora mostly replaces the storage engines of these DBs and the frontent mostly follows upstream releases and is compatible with them.
You're spot on. GP is repeating the common misconception that "Aurora" is a distinct, from-the-ground-up relational database system which can "pretend" to be either MySQL or Postgres by reimplementing their protocols/front-end from scratch. But that isn't the case at all.
In reality, Aurora MySQL is clearly heavily based on the MySQL codebase, but with major changes specifically to InnoDB's persistence and MVCC layers. Aurora MySQL implements a physical replication system using shared storage, undo, and redo logging. The rest is otherwise compatible with MySQL because it is using a lot of MySQL code.
I haven't read up on Aurora Postgres, but I'd bet it's something similar being applied to the Postgres codebase.
It's entirely possible the custom storage components may share some common code between Aurora MySQL and Aurora Postgres, but a custom storage layer alone isn't a "relational database" which "pretends" to be other DBs. (In contrast, it appears that DSQL actually might be that – a custom system with a reimplementation of Postgres wire protocol.)
Not trying to knock Aurora btw, it's really interesting technology and is quite an achievement by Amazon. But the constant confusion about what Aurora even is creates some support burdens in the DB ecosystem.
reply