Maybe they meant of the box. You have to add additional repos to get non-free drivers installed on Debian or install them manually.
Maybe they meant of the box. You have to add additional repos to get non-free drivers installed on Debian or install them manually.
I’ve been using Linux as my main driver for a couple of years now but I didn’t know the list of reserved file name characters is so short.
I didn’t believe ‘*’ is allowed. That alone is so error-prone, it’s insane. Backslash is allowed too - how do you escape that? Sometimes I think they giggled while writing the specs.
deleted by creator
Different mindset. A user doesn’t want to find bugs but get shit done.
And we absolutely wanted to shoot the tester who gave us this use case.
Why? Because he tested well and broke the software? A user changing their mind during a guided activity absolutely is a valid use case.
Well, it’s a life, I guess…
Yeah, the people at Pixar have no clue how to use a computer. Lol
Do you really expect their artists to be IT experts? You seem to be stuck in the early 90s mindset when “knowing how to use a computer” covered all disciplines.
It’s actually quite similar. Non-fungible since only OP has the private key but easy to steal by just downloading the image (and cropping the key if you want).
But it can also be a matter of (inexperienced) devs just deciding, fuck it, I won’t try to merge it, I’ll just copy my changes elsewhere and throw away the repo.
Pretty sure that’s actually it. Git has a learning curve and, for example, some naive rebase not working out as intended can be scary if you don’t know what you’re doing.
It works well - for a Windows subsystem. It is well-integrated but also separate which can be annoying sometimes.
For example, you might code in Python in VSC against a WSL folder but make a script to eventually run in Windows. You need to install and update Python twice then - a Linux and a Windows version (obvious, but can be annoying).
WSL is also really slow, especially for filesystem heavy stuff. You know how on Linux programs sometimes run faster via Wine/Proton than on Windows itself? Yeah, this is the other way around.
It was earlier, when they released Windows 7 and it was the first (and only) release, management gave development a largely free hand and they could bring down some technical debt.
But apparently that didn’t work out for Microsoft and now we get one dystopian news after another.
Isn’t the POSIX incompatibility a major roadblock when scripting?
It must be a really deeply integrated part of the Windows kernel because it has never been able to show progress properly.
Back in the days of floppy disks it always felt that actual copying started when the progress showed 100%.
Makes sense. It’s like having your personal undergrad hobby coder. It may get something right here and there but for professional coding it’s still worse than the gold standard (googling Stackoverflow).
Pendatry. Very widespread in tech.
Onfuscators probably use it though, so no spec ever will be able to get rid of this crap.
BASIC. At least VB.
Debian 2.x (don’t remember exactly) was my first attempt. But I don’t actually count that because after annoying driver troubles (networking and mouse) and having to recompile the kernel multiple times I unfortunately lost interest.
Tried again with Debian 8 on my laptop and stuck with it until I moved 100% Linux just a couple of years ago thanks to Valve/Proton.
I sometimes update out of habit almost immediately after I updated. That’s always a little disappointing.
Thanks, that’s good to know. I wasn’t up-to-date since I currently don’t run a Debian machine.