If they sold it a $400 they'd be at a loss, at $300 they would crash the desktop market. People would by it for general desktop use. Similar how so many PS2 were bought just because it was the cheapest DVD player and didn't buy games.
Hell, there was a supercomputers built with PS3 clusters. Maybe that explains why the Steam Machine only has a 1Gbps nic...
I'm most surprised that they removed SMART tooling. My primary pool is still spinning rust for the foreseeable further. And I just retired a drive based on SMART testing and TrueNAS's alerting.
I had issues with my 8bitdo controllers right trigger acting stuck (would keep running). Seems like a bug with the Linux version. Changed compatability to Proton Experimental and everything runs great now.
Man, I remember lusting over getting a WD Raptor back in the day. They were so much more expensive and lower data density it I couldn't justify for my low budget.
As was already said, 160 was pretty common, think increments of 20 or 40 is what i remember. Raptor drives had kinda odd size increments compared to other consumer drives. Looks like it would be 36Gb circa 2003.
I once got some retired scsi drives. Man 10,000rpm drives were loud and hot...
Thank you! This project make so much more sense when put in context of Google+. Their landing page is so buzzwordy my eyes just glazed over and just couldn't see what it's actually trying to achieve.
Makes me wonder if there is self hosted project like Google Wave... and if that is a good idea...
Talos... are you running kubernetes for your laptop you mad lad? Also, not aware that the coreboot is ready yet for any of the non-chromebook machines. (Edit: meant coreboot for Framework laptops)
Is that method different from using the hot keys to swap layouts?
Depends on your desktop environment and if you are using Wayland. If you use the hot keys, probably try those first since using the terminal can mess those up. It's a bit of a hammer, but I typically manage keyboard layouts only using the terminal.
Like can I tell it to always use that mapping for that game or do I need to remember to run it each time I play the game and then set it back after I'm done (or automate that)?
Hmm, I've never had the need, but I would start by changing the game command in your launcher (Steam, Lutis, etc.)
I use gamemode to automate things like changing my RGB light patterns when running a game, maybe there is a per-game thing you could do..
Hey, long-time Dvorak user here, almost as long as a Linux user.
When I start playing a new game, I usally just go with defaults. Some games (like all Valve games) do a good job of using keyscan codes for bindings and mapping them to the layout. If that's not the case the game is likely to be incorretly using the keyscan codes, or just using the OS's key events. If that's the case, I will just force qwerty with setxkbmap us and restart the game. After a few hours, I try to rebind keys for dvorak. Persoally, I like to change keyboardings to use Tribe's ESDF layout instead of WASD anyway.
If you are using wayland for your display, setxkbmap is great since most games run in Xwayland mode, so native apps will still be in Dvorak.
I don't really need to type much in games anyway now, so I don't mind keeping with qwerty bindings. I play Starcraft 2 this way.
The worst experience I can recall is Natural Selection 2, which its game engine refused to bind non-alphanumeric keys like ',' 😵💫.. But that was playing with Windows, would probably work with Linux if the game was still alive.
Seems more like an article the Sun would publish 🤣