1
Call Before You Dig
(lemmy.blahaj.zone)
Thank you Ted, that's the joke.
systemdeez nuts!
As long as the repair shop is reputable it's not too hard. I was looking at options on iFixit when I first heard this update was coming down the pipeline. I guess I am lucky that mine was already a refurbished unit when I bought it so it looks like the battery has already been replaced.
https://www.ifixit.com/Guide/Google+Pixel+6a+Battery+Replacement/152516
I replaced a few batteries myself before in a Nexus 6 and a Pixel 4a. The guides really help as does having the right tools. It's also helpful that iFixit offers genuine battery replacements.
https://www.ifixit.com/products/google-pixel-6a-battery-genuine?variant=39912699330663
This Desire Path Fact brought to you by Barqs.
Also, they can still offer the olde versions of the file for download.
Except in a lot of cases they really don't.
But if they keep it updated for modern systems that means as time goes on the files they are offering to install... won't work on old hardware because they've been updated to the modern era.
Sure if you grab a file from them and never get a newer, more maintained version, it will play on exactly the hardware and software you had when you bought it... But if you lost the install file somehow and went to grab a new copy five years later the updated ones may no longer run on your old hardware
They keep a bunch of 32-bit libraries for backwards compatibility with older games that they launch. You can find numerous discussions about this in the Steam forums as well as on sites like Hackernews.
If you want, I can give it to you from a Valve employee:
https://github.com/ValveSoftware/steam-for-linux/issues/179#issuecomment-267790879
We will not drop support for the many games that have shipped on Steam with only 32-bit builds, so Steam will continue to deploy a 32-bit execution environment. To that end, it will continue to need some basic 32-bit support from the host distribution (a 32-bit glibc, ELF loader, and OpenGL driver library).
Whether the Steam client graphical interface component itself gets ported to 64-bit is a different question altogether, and is largely irrelevant as the need for the 32-bit execution environment would still be there because of the many 32-bit games to support.
Maybe do some cursory research before talking out of your ass.
I need DOS Box
It's Valve's responsibility that Microsoft stripped DOS support from their OS in Windows 10?
Starting with Windows 10, the ability to create a MS-DOS startup disk has been removed, and so either a virtual machine running MS-DOS or an older version (in a virtual machine or dual boot) must be used to format a floppy disk, or an image must be obtained from an external source.
GoG also famously uses a model where GoG does not care what OS you’re using.
I could have sworn their model was keeping old games updated to work functionally on newer hardware.
https://www.gog.com/en/gog-preservation-program
The GOG Preservation Program ensures classic games remain playable on modern systems, even after their developers stopped supporting them. By maintaining these iconic titles, GOG helps you protect and relive the memories that shaped you, DRM-free and with dedicated tech support.
The entire back-end has changed.
Literally. People miss the fact that Steam is still a 32-bit app just to support older games. The rest of the world has moved onto 64-bit operating systems and applications. It's shocking they still support 32-bit in 2025. So the argument that they aren't supporting older titles is a little misleading because that's the whole reason they still run a 32-bit client.
Most operating systems are no longer even offered in a 32-bit variant, 64-bit only.
I haven't had a device with 32-bit hardware in almost 15 years. The last device I can even think of that was still 32-bit within the last 15 years was a Google Nexus 6 in 2014. All the Pixel line have been 64-bit.
Steam is literally one of the last 32-bit holdouts. Everything else has moved on. Even Discord dropped 32-bit support last year.
EDIT: Also, for reference, since Windows 98 is heavily mentioned in the arguments, those operating systems included 16-bit code. We're talking about dropping 32-bit code, 16-bit code is deader than a doornail. Windows 3.11 was the first introduction of 32-bit code. Windows XP seems to be where they dropped all 16-bit code in 2001. We're talking over 30 years of hardware changes.
All versions of MS-DOS and the below versions of Windows had 16 bit code:
MS-DOS (all versions)
Windows 1.x/2.x/3.x (all versions)
Windows 4.x or 9x (Windows 95/98/Millennium Edition) (all versions)
I don't necessarily agree with all of Kaldaien's points, but I can't say they aren't well argued. Their opinions are valid if you're willing to accept and consider their perspective.
I personally don't see the point playing games on the original hardware, and I think keeping them updated for modern systems is a good thing, but I can see why someone might disagree and prefer running them in a VM on a traditional operating system, especially in terms of keeping the original way the game ran intact. I also disagree about the value of Microsoft's game rental service, but I also see the value in saying "if I don't actually own my games anyway, why not take it to it's logical conclusion of just renting them."
As I said, their points are well argued, even if I don't necessarily agree on them.
view more: next ›
SnotFlickerman
joined 2 years ago
They were the only phones I would reasonably buy due to their ability to be customizable... Yeah this pretty much puts a nail in the coffin of using a Pixel in my book as well.