Replace Sunshine with Super Mario Eclipse. It has the original shine sprites, huge quality of life improvements, and an insane amount of new content.
Replace Sunshine with Super Mario Eclipse. It has the original shine sprites, huge quality of life improvements, and an insane amount of new content.
It’s not the Chromium team. Google could have added JPEG XL to Android, but that’s been stalled for nearly two years with zero explanation as for why.
The whole thing smells of managerial interference somewhere.
Interestingly, the reference implementation libjxl appears to be a Google project. They’re all over the patents file and CLA.
If Mozilla isn’t merely being hopeful about having the same team create a Rust implementation, that might actually mean there’s internal interest within Google. Assuming they pull it off, the bullshit reason for refusing to add JPEG XL to Chromium might finally stop being a blocker.
Google created the original reference implementation, libjxl. It’s not stupid that they would prefer a Rust rewrite be created by the same team.
We really don’t need more than #3 for a reason to stay far away from Telegram. Security through obscurity is not security, and neither is rolling your own crypto.
The “P” stands for “Private”
But think of the profit improvements!
It would have if I actually had the PSID 🥲
It was an expensive lesson to take photos of my new drives and store the PSID and serial numbers in KeePass.
When using Opal (hardware encryption), it locks down the drive. Not even a secure erase would wipe/release the damn thing.
I had this happen to me with a hardware-encrypted bitlocker drive. I was forced to buy a new SSD, actually.
If you can find the download for GitHub Enterprise, Ruby Concealer is little more than an XOR cipher. Make of that what you will.
You can self-host GitHub. It takes around 32 GB of memory, however.
The “++” in C++ stands for extra verbose.
They do, but then go on to contradict themselves:
On a platform level, we believe GTK should stop forcing a single stylesheet on all apps by default. Instead of apps having to opt out of this by hardcoding a stylesheet, they should use the platform stylesheet unless they opt in to something else. We realize this is a complicated issue, but assuming every app works with every stylesheet is a bad default.
Emphasis theirs. They are explicitly saying that their belief is for applications to use the [original GNOME] platform stylesheet by default, and making the ability to reskin an application opt-in by the application [developer]. I agree that a one size fits all stylesheet is bad, but the solution should be to provide more granular selectors at the toolkit level to allow themes to fix what they break, not force defaults onto everyone.
The fact that https://stopthemingmy.app/ isn’t a joke…
App Icons are the identity of an app. Changing an app’s icon denies the developer the possibility to control their brand.
FOSS is built around the principle of software being free, as in freedom. If you want to restrict how a user interacts with your software for the sake of a corporate identity, fuck right off and go to an Apple platform. We won’t miss you.
Appstream Screenshots (the screenshots used in GNOME Software or Flathub) are not very useful if they look nothing like the real app does once you install it.
Oh no, how tragic. Your application doesn’t look like your screenshots when running on my customized system. You know what would be more tragic? Your application sticking out like a sore thumb.
User Help and Documentation are similarly useless if UI elements on your system are different from the ones described in the documentation.
I’m really struggling to understand their perspective here. Is their documentation really that bad, to the point where it would be impossible to follow if the background color is wrong or if the buttons look like slightly-different buttons?
The only reasonable complaints they had are with broken styling or icon sets replacing icons in a way that changes their meaning. The rest of this is just straight up stupid.
Look at Mac or Windows users.
Mac, maybe. Windows? No. Not by a long shot. I have the pleasure of using Windows 11 for work, and it’s just as bad as the fragmentation between Linux applications using GTK vs those using Qt—except it’s all made by one single corporation.
Microsoft just can’t commit to a design language. You have modernized applications made with WinSDK using WinUI, and then you have the “classic” applications made with the Win32 API. And, their designs could not be more diametrically opposed. WinUI applications are crammed full of blank space and animations, whereas Win32 applications look like “and the kitchen sink” Windows XP programs with a coat of paint slapped on top. You have system legacy applications that came straight out of Windows NT and use the same L&F since Windows 8, full of stacking popup models and design decisions made to work around limitations, you have a couple of “modern” applications that use the “my first time making a Flash game” Metro design language of Windows 8, a few more applications that use squared-edge and small border design from Windows 10, and then, finally, the Windows 11 design.
That’s four entire generations of designs crammed into a single operating system, and unless you only use it to browse the web, you are going to see all of them at some point. Fuck, the modern Settings application still opens the control panel for some things.
And again, that is just Microsoft’s programs. How about third-party software? You have some programs still using Win32 because they’re built on the bones of your ancestors, other programs using Win32 because WinUI 3 only has official support for C++ or C#, some programs in Qt for cross-platform support, even more programs using Electron because it’s more cost-effective to churn out HTML that looks like Windows than to maintain multiple frontends, and even programs that use Unity or Unreal Engine as a goddamn GUI toolkit.
Seriously, fuck that. Linux might be mostly split across two GUI frameworks and proprietary pity-offerings that only exist because the company was already using Electron, but at least it’s consistent within them.
This assumes front-end development.
From a (dev)ops perspective, if I had a vendor hand me a tarball instead of proper documentation, I’d look very far away from their company. It isn’t a matter of if shit goes wrong, but when. And when that shit goes wrong, having comprehensive documentation about the architecture and configuration is going to be a lot more useful than having to piece it together yourself in the middle of an outage.
For your sake, I hope your employment was agile as well. Those jobs sound like they were dumpster fires waiting to happen.
Because people are technologically inept and buy into the propaganda that kernel-level anticheat is more effective than the alternative solutions.