I’m one of those that use PowerShell on linux.
You can use tmux, vim, sed, awk or whatever binary you want from PowerShell. Those are binaries, not shell commands.
You can use pipes, redirects, stdin and stdout in PowerShell too.
I personally don’t regularly use any object oriented features. But whenever I search how to do something that I don’t know what to do, a clear object-oriented result is much easier to understand than a random string of characters for awk and sed.
Just ask your ISP for more upload speed (and pay for it). It’s a thing you can do.
Don’t need sudo or anything pre installed for vscode either. It will send the server to the machine via SSH and then run it automagically.
You can do that with vscode too. And probably many IDEs.
The only real reason for which you would need to use vim in such cases is if the target computer can’t run the vscode server, which I’ve never encountered yet.
Iirc Ubuntu names their home files “Downloads”, “Documents”, and so on. Same with windows (there are a lot of uppercase letters in windows files). I’ve had issues with Cargo.toml before. And not just cargo, many config files use case to signal priority (so if both Makefile and makefile exist, Makefile will be used (or other way around)). Downloaded files are a gamble. Files created by user input (so for example if I wanted my user to be “Calcopiritus”, my home would be “/home/Calcopiritus”.
Uppercase letters might not be common in filenames, but they are not nonexistent.
They are not created by people. They are created by programs.
I can make MY files all lowercase, but 99.999% of files on my computer are not created by me. And some of them have capital letters.
When you say "canse insensitive file*, do you mean lowercase files? Or is there an option?
Idk why we talking about mouses. When I’m on Linux, most of the time it’s through ssh.
This is the first time I’ve seen uppercase denoting scope. Usually it is done with a “_” or “__” prefix.
Casing styles usually mean different identifier types.
snake_case or pascalCase for functions and variables, CamelCase for types, UPPER_SNAKE_CASE for constants, and so on.
If we want to apply this to file systems, you could argue something like: CamelCase for directories, snake_case for files, pascalCase for symlinks, UPPER_SNAKE_CASE for hidden files.
I’m with windows on this one. Case insensitive is much more ergonomics with the only sacrifice represented by this meme. And a little bit of performance of course. But the ergonomics are worth it imo.
This is perfectly fine to do under GPL as well. I don’t see the problem.
There are companies that sell Linux distros on a DVD or USB drive.
Hardware doesn’t need to be too weird. Back when I bought my laptop, it was a kinda recent model so most of its features didn’t work in Ubuntu (I say Ubuntu because it’s the distro that worked best. Tried many others and they had even worse support). After a year or so it worked mostly, except some things.
To this day, 4 years later, the display brightness control still doesn’t work correctly.
I don’t think hiding the problems do any good. The Linux desktop/laptop experience is not good, specially for non-programmers. It’s usable, but not good.
This meme has the logos of the OSs from around 2007. Back then there weren’t many Linux non-IT users.
I’m not a java programmer, but I think the equivalent to str would be char[]. However the ergonomics of rust for str isn’t there for char[], so java devs probably use String everywhere.
Python is the slowest (widely used) language there is. It’s not hard to be faster.
Not saying I’d do it, just throwing one more option out there.
It’s easier to park when there’s another car already parked, for reference.
You don’t need to have wired across the room. You can put them through the wall like every other cable. If the wire tubes are not full, it isn’t very complicated. I put my Ethernet wires in the wall.
A program being written in rust itself doesn’t guarantee anything, but it tells you what you’ll probably find:
Many of those are highly positive to the end consumer.