There's that lovely genx spirit, do nothing and surely things will get better!
Maybe another post about drinking from the garden hose will help, or complain about how the kids are getting participation trophies despite the practice going back a hundred years.
The Fine Repo linked above makes it clear that this particular software runs only on TV-type devices. SponsorBlock does appear to be available on iOS in multiple ways (see https://github.com/ajayyy/SponsorBlock/wiki/iOS), which is something I was not aware of.
The comment I replied to assumed that you were using these tools on a laptop or desktop machine, because you didn’t otherwise specify what platform you were running on, and you didn’t reference a web page showing the specific tools you were using.
I will consider whether or not I want to use Safari with an extension for this feature on iOS. I am mostly happy to avoid regular advertisements using my YouTube Premium account, and most sponsor sections don’t bother me. But I have been curious about trying SponsorBlock or similar tools, so this might be the easiest way for me to do that.
JSON often means data is crossing a boundary, and JSON has `null`. So if you have a PATCH endpoint that accepts a partial object, how do you determine what was actually set in the request vs what go has initialized to an empty value.
I don’t think there was a single canonical solution, but pointers to everything was a pretty common one. Everything in the AWS SDK was a `string` or a `float64` or similar—it was exceedingly annoying, not least of all because it basically forced tons of unnecessary allocations.
It'll be a new app, but it does provide a drop-in replacement for konsolepart (along with also having a QML module API for embeds into Qt Quick-based app, closing a gap Konsole currently leaves open). I'm sure it'll be some time before it would be ready to replace Konsole as default, also because conversations like that take some time and are a community process.
Oh Konsole while great (efficient and feature-rich) is showing its age and has a bit of a widget bloat and an unwieldy configuration system. For that reason I switched to Kitty a couple of years ago when I was transitioning to neovim I'm have not looked back since.
This looks like a great opportunity for the KDE project to rethink its terminal application for the modern age. Text-based config would be amazing though not sure how it'll fit into KDE Frameworks etc.
Plus one on this one.
I have chezmoi apply my konsole settings onto every new machine and sync the settings between machines as I modify them over time.
There's a pattern though, they companies at the front of the Ai hype train love to brag about their eyes and brain free coding practices. Reap what you sow I suppose
Maybe another post about drinking from the garden hose will help, or complain about how the kids are getting participation trophies despite the practice going back a hundred years.
reply