Regardless of budget, I have found the following setup has afforded me all the comfort upsides of mobility and console gaming, with none of the performance downsides.

1. Build a standard desktop gaming pc to your budget, setting aside ~$150, give or take.

2. Make sure it’s wired into your network and not using wifi. Setup Steam on it as usual.

3a. (Console experience) Buy a Google TV with Chromecast, or whatever it’s called now. Install Steam Link app on it and connect it to your gaming pc. Get a Bluetooth compatible Xbox controller, connect it to the chromecast. Enjoy a console experience with your gaming pc. If you have the chromecast on a wired ethernet lime you’ll have maybe 1ms of input lag, very playable.

3b. (Laptop experience), buy a dirt cheap laptop, install steam on it, use Steam Streaming fu ctionaloty to stream from gaming pc to laptop. If you plug the laptop into ethernet you should have sub 1ms input lag.

This let’s you get all the horsepower of a gaming pc, at gaming pc hardware prices, but the portability of a laptop and/or couch gaming comfort of a console.

And since it’s all centralized to your 1 “server” machine, of you make changes in setup A (ie change am in game setting or etc), it’ll persist even if you swap over.

IE if I change my settings or preferences on the console, I’ll persist that over on my laptop and won’t have to change it again.

Furthermore no network save game synching needed, no waiting for a game to download a second time, no need to update the fane multiple times, etc.

It’s all centralized to your own core machine and everything else is just a thin client.

PS: this works with the Steam Deck too, you can stream from gaming pc to steam deck and use it as a thin client 👍

Dunno why ppl are down voting you, this is 100% the way.

Architecture as code is amazing, being able to completely wipe your server, re-install fresh, and turn it on and it goes right back to how it was is awesome.

GitOps version controlled architecture is easy to maintain, easy to rollback, and easy to modify.

I use k8s for my entire homelab, it has some initial learning curve but once you “get it” and have working configs on github, it becomes so trivial to add more stuff to it, scale it up, etc.

Yeah in fact you’re giving the llm additional data to train on what poisoned data looks like so it can avoid it better, as they can clear see the before vs after

Lasse is the original maintainer of XZ, they have been placed back in their position as sole maintainer.

“Jia Tan” was the person who slipped the backdoor into XZ and is now banned.

Lasse has already fixed abd removed the backdoor.

XZ itself is critical software everyone uses (its one of the main compression/decompression programs used on linux)

but the best way to avoid getting them is still to just avoiding stupid shit.

This is fine and dandy on a personal pc, but in a work environment you are now being actively targeted by malicious actors if your company is a good target.

Constantly.

So once you are in that zone you do need some fast acting reactive tools that keep watch for viruses.

Nowadays it’s less of an issue with docker and whatnot.

Just set the image to refresh every night at midnight and if they tried to make manual changes it’ll just revert back to its original state at midnight.

Customers don’t really get direct access to deployed code now, it’s buried under like 4 layers of abstraction on most CDNs now.

Simply deploying to azure already smears multiple layers of access control and RBAC overtop that it’s hard enough for me, the dev, to answer the question if “what is actually deployed atm?”, let alone for the customer to get in their and meddle.

For casual users I typically recommend using Cinnamon Desktop, it’s the most Windows-esque UI and will be the easiest for them to pick up and use.

I roll with Cinnamon on Ubuntu and it’s been extremely painless, very simple to get stuff do and shit just works.

Prolly for the best, WotC seems hell bent on destroying every IP goldmine they can, good to not strap yourself to a sinking ship.

Would’ve liked to see some kind of endgame for baldurs gate but oh well.

I feel like this is more “how we feel we get perceived by others” moreso.

I try and perceive all the members of my team as, well, my team. I heavily appreciate everyone busting their assess off and contributions.

However, there are folks on each layer that do actually treat others like this and I think we can all agree those people suuuuck.

In Canada the Cert and the Degree are separate.

You typically through getting your degree also become certified, but the key is while your degree lasts forever, the Cert has to be maintained and renewed.

Cert has a lifetime and expires and you have to keep it up to date.

In Alberta for example the regulatory authority is APEGA: https://alis.alberta.ca/occinfo/certifications-in-alberta/engineer/

I think even technically the license is also a separate piece of paperwork.

Degree: you completed school at some point

Cert: up to date on current practices, must be maintained, requires the degree

License: you are legally allowed to practice in the province/country and have registered. Requires degree+cert

What if they are actually a software engineer, with a cert? >_>;

I have worked with actual cert’d engineers on web projects, lol

This by a long shot, I agree.

What CLI tools do you find have install problems on Powershell?

Everything I’ve used can be installed “headless”, often using winget now.

But powershell just sucks and windows file system is cumbersome, so limux is still better.

So far any use case I’ve solved with just SSH.

What specifically do you need to rdp in for?

Honestly I never use right ctrl for anything, having a dedicated hockey to get ai prompting for coding sounds actually fine and I don’t mind its location.

I expect we will start to see it get integration with ms office sooner than later as well.

What I would be really interested in, is how does it play out in reversed scenarios.

How do inexperienced women react to a singular man commenting in a competitive area that is female dominated, do you see the sane sorr of vitriol from lower performing women, vs welcoming behavior from better performing women?

My understanding is “immutable” is a bit of a misnomer and avoids the “point” of using these distros.

“Layered Distros” is a better terminology, where you can imagine the OS as multiple layers, and you can swap 1 layer out for another without modifying the others and still have a functional operational machine.

Now some of those layers have to be immutable ones at runtime for this concept to work, so thats where that part of the name comes from, but thats an implicit result from the actual point/use case of these distros, not the selling point.

So you can swap versions/releases of your OS very cleanly at boot, without modifying userland, and it will continue to function just the same. This lets you do stuff at the admin level like broadly releases a version update merely by having users just reboot their machines, and next time they boot up their machine will now be running on the new OS layer, with their local “user” layer being unchanged.