towerful
Americans confused at what month “27” is
Enshittification is about increasing monetisation of a previously free/cheap product.
Adobe moving from a lifetime purchase to a subscription service: enshittification.
Adobe not supporting old GPUs: not enshittification.
Twitter locking rate limits behind subscription: enshittification.
Twitter rebranding to X: not enshittification.
Raspberry Pi prioritising business customers making SKUs rare and enabling scalpers: enshittification.
Raspberry Pi moving to a new version of Debian making many tutorials outdated: not enshittification
Ensittificstion is the process of a platform good for users becoming good for business customers, becoming good for investors/shareholders.
Whilst it is a cool phrase, and an interesting observation, enshittification doesn’t apply to everything that has a core change.
Enshittification would be mandatory ads in-game, some sort of P2W mechanic.
Requiring better hardware is not enshittification.
CS has always needed a GPU.
CS:go required anything DX9 compatible with 256mb VRAM. Which would be an NVidia 6600, a midrange GPU from 2004 - around the time CS Source was released.
CS2 minimum spec is a GTX650. Which is a mid range GPU from 2012, around the time cs:go was released.
Something of a pattern there…
If CPUs didn’t have integrated GPUs, this whole “cs is CPU dependent” thing wouldn’t apply, because you would STILL need a GPU.
It’s just that intel bundled a barely passable GPU alongside the CPU.
TBH, I think you are missing you’re argument.
You should be arguing that there is no way to play cs:go now that cs2 has released. Meaning a potential hardware upgrade requirement.
That is a bummer. That’s pretty shit.
But it is NOT enshittification.
That does not claw back value/money from customers to valve or its investors.
Unless you can show me, beyond reasonable doubt, that Valve is making money from giving away CS2 for free to anyone that has purchased cs:go through the requirement of a hardware upgrade.
Until then, this is not enshittification.
Is it shitty? Sure.
I guess the obvious one is “holding spacebar for control key”
The server was now too full of data to do anything,
This reminds me of something that I always mean to do but totally forget to.
Allocate 1gb of space for a blank/dummy file on every VM I run.
When you run into a VM that locks up due to disk space, delete (or resize) the file, get to work fixing the VM, then put the empty file back
I am going through this right now, but without the drugs.
Mid 30s, waking up to realise my life is a mess, working on getting a diagnosis for ADHD and possibly bipolar, and getting help with depression.
I am now fixing my life.
The biggest thing that is helping me is talking about it. Asking for help is important, but just sharing your experiences is also important.
It was a friend that shared his experiences with me that has put me on this journey of recovery.
Never any problem solving, or offering solutions or fixes. Just sharing and talking.
Anyway…
When I’m doing software dev stuff, I always feel out of my depth. I’m reading interesting articles from people way smarter than I am. I’m reading codebases that are a delight to read through and leave me in awe.
And I turn to my projects and work, and feel like a fraud. It’s all “standing on the shoulders of giants”, following tutorials just to get things to compile, locking myself out of VMs or network switches from dumb mistakes.
But I also work in live events, so still technical and a lot of smart people. But when there is a problem, or a unique problem to solve, I’m just like “yeh, the problem is here because…” or “why not just do this…”.
And these moments make me realise that perhaps I am not a fraud or an idiot. I just have different experience than my peers both in software development and live events. And there is some overlap.
I think a huge part of it is: everyone is making everything up all the time.
Some people have made something up before, so they can draw on that experience.
It’s always worth spending a little time introspecting some of your progress.
Spending less time googling issues, and realising you can figure stuff out (make stuff up) for yourself? Huge win.
Remembering correct syntax? Huge win.
Writing code that only has 1 or 2 bugs? Huge win.
Recognising that a problem is best solved using whatever pattern/library/etc? Huge win.
Imposter syndrome is real.
Dunning-kruger is also real.
And then the imposter syndrome makes you think you are in the dunning-kruger zone, and makes everything worse.
Recognizing the progress and successes helps