Sleaker

Gacha games being normalized didn't help this at all either. SMH at all my younger friends that got pulled into this trap.

Dell was selling new Intel core laptops at the $450-$550 range in 2006. Budget brands were offering similar deals/rebate sales pushing just below these. (Acer) I had purchased one of these.

20 years ago a $400 laptop could emulate most major psx games, and anything from n64 and prior.

A $1k laptop could dualbox WoW.. depending on the type of game you were playing consoles were not that much cheaper. Hardware prices in the mid oughts were getting very good.

The last company I worked for still had customers they were dragging forward to get upgrades from coax connexted green screen terminals to modern network thin clients. It wasnt on DOS, but very old unix OS, tape drives for backups, parallel for printers, serial for scanners. No USB. Lovely troubleshooting when you were dealing with 30+ year old hardware setups. There was only one company that would even servicenthe green screens if they failed, and you couldn't buy them anymore.

It was the believed area of emotion, passion and 'soul'. I think western/modern religion has morphed from the liver to the heart essentially.

This is something I've asked repeatedly at my job. Current team builds services for other developers to use, okay, do we also use it so we can go th ough all the same pain points as them? Why not?!

> And yes, that is literally why I don't support direct cash handouts to the homeless. You can feed them and house them, you can't throw money at them and expect a good outcome.

You maintain this despite all the research showing that this is the most effective way to help people?

The dolby/thx stuff for headphone s is done at the software level. It's just preset filters provided by synapse. There is no hardware dolby unless you get into the PCI audio card stuff, or audiophile dedicated sound board setups. Different USB DAC might impact noise levels. If you don't have noticeable audio artifacts then there's not really any reason to use another one.

Neither, the author is pointing out the desire of the enslaver, not the actual outcome. But I don't think their logic takes into account access to means to 'outsmart' the enslaver. It's trying to frame it as a single instance equation, not a societal one to try and show the underlying contradiction of desire.

At least, that's what I'm pulling from the quote, have not read the full context.

That would be poisoning the test with outside knowledge. Essentially boosting their skills with some expertise, exactly what was undesirable.

You are not wrong, just that was not the intent of what the person was trying to test for.

And this is -exactly- one of the reasons they didn't accept or continue with a sane proposal for more ergonomic error handling. I like go, but this was the one thing that I kept feeling like I was wasting so much time dealing with.

I don't think any form of automated adoption of orphaned packages will ever work, it's just too easy to introduce malicious code into an otherwise functional but no longer maintained source.

I get that premise, I guess I've just been around a lot of bad engineers that use these types of tools as crutches but can't actually articulate or diagnose problems well. They just regurgitate the syntax like it's a magic spell.

Maybe I just missed the boat on hashicorp and similar solutioning, but I find a lot of the solutions for working with multiple systems using an intermediary shared language, such as terraform, end up obfuscating the problems they intend to solve and result in people who deal with and support those systems on a daily basis having very little understanding of how to interact and troubleshoot the core infra that is being built up with those tools.

Yes, building those solutions requires a lot of expertise, but I've never found the tools to be worth engaging with over just using what the standard platform tools they abstract away were replacing. Then you add in the economic rug-pull scenarios that have happened when utilizing software like this and I wonder why everyone hops on the bandwagon so easily.

What is the company they're building trying to solve that system maintainers can't already do? Isn't this just rebuilding OS windowing?

I think the damage/risk here isn't explicitly about exfiltration, but could also just be damage/harm to the organization through re-writing content in documents.