because explicitly declaring types can be redundant, if the compiler knows a lot of the times you should also know
also because some types are extremely cursed: see std views/ranges
because explicitly declaring types can be redundant, if the compiler knows a lot of the times you should also know
also because some types are extremely cursed: see std views/ranges
imagine being a conservative. the jokes write themselves
Surprised at how much my parents hated on me for slacking when now as an adult all I wish I could do was slack more.
WSL, if not then msys2/git bash at bare minimum
Poweshell 7 is okay if you have access to it but regular day to day shell scripting is like as 10x more verbose with powershell than bash
I just use WSL at work, extremely fortunate to be able to despite IT locking down everything as much as possible
I specifically said this advice because dual booting windows with Linux is a terrible idea.
Although you are right, if you USB read/write is slow it will be a sluggish experience.
I use like less than a tbsp of coffee creamer for coffee.
The flavour is so artificial that any more will make me feel sick. It just tastes like soap.
Many coffee creamers also taste terrible, I'm very surprised at the popularity of them overall.
I get a specific kind that I can bear and I put a very small amount and it works for me. I don't like milk. Black coffee is okay but I do like it with creamer more.
You should just test run it from a bootable usb.
Install steam. Mount your NTFS drive which contains your windows games. If you have sims on steam use steam. If not take a look at lutris before doing any of the above.
Your experiment ends when you've tested all games you want to play.
Now: You cannot use NTFS (windows) drive for games, although you did it in the experiment long extended usage is discouraged.
So you will need to find a way to transfer your games to a different formatted drive. (ext4, btrfs for example)
If you don't need that advice you will eventually run into frustrating issues.
"grug try watch patiently as cut points emerge from code and slowly refactor, with code base taking shape over time along with experience. no hard/ fast rule for this: grug know cut point when grug see cut point, just take time to build skill in seeing, patience
sometimes grug go too early and get abstractions wrong, so grug bias towards waiting
big brain developers often not like this at all and invent many abstractions start of project
grug tempted to reach for club and yell “big brain no maintain code! big brain move on next architecture committee leave code for grug deal with!”
Honestly, if they want to go full enterprise at least use the javabeanfactoryfactoryfactory pattern
This is a reminder that it's okay to enjoy garbage and accept that it is garbage. You don't need validation from strangers. you don't have to convince strangers that what you consume is only the most peak content possible.
I have nothing to add except: man's really wrote like 7 classes to just have 1 function each
actually what they say is "I live here meow"