Not related to your question at all, but:
I don’t recommend editing the source code from cargo’s files. Instead, the correct way to modify a dependency would be making a fork and using it as a gift dependency (or path dependency, which is even easier).
Dear imgui absolutely exists on rust. Which is the same dear imgui as C/C++. If you want a rust option though, there’s egui, which is basically Rusty’s version of dear imgui.
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.
At this rate, the US government won’t even consider it as an option! Rust is practically a hippie language.
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 the talk that convinced me that C is the only language more cult-like than rust.
HTML is hard to parse because it allows mistakes.
I don’t know the answer to your question. But if it was me, I’d run the HTML parser until it encounters an error, manually fix the error, then try to parse again. Until it parses correctly.
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.
Instead of checking if debug assertions are disabled, you should use debug assertions, it would make the code much neater.
If you wanna eliminate the borrow checker this way, I guess you could use raw pointers instead of references, and have debug assertions to check if those pointers are null. At that point you’d have a mix of C and Rust. The memory would be completely unsafe (you’d have to allocate mostly on the heap, and drop it manually), but you’d have rusts’s type system. You’d also lose a lot of ergonomics though.
EDIT: just to be clear. I think completely disabling the borrow checker this way is absolutely nuts. Maybe you could have some raw pointers in troublesome locations (where RC/RefCell would have too big of a performance impact for a 144fps game). But most of the code should be borrow checked, since the borrow checker only gets in your way sometimes. It’s not like lifetimes go away with the borrow checker, you still have to think about lifetimes if you manually manage your memory.
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.
What I do to parse strings (pseudo code since I’m on mobile, don’t copy-paste):
delimited(
",
many0(alt(
any_character_except_quote_or_slash,
pair('\', escaped_char)
)),
"
)
Where any_except_quote_or_slash and escaped_char are defined somewhere else, the rest of the parsers are by nom.
You may want to wrap pair with a map and many0 with recognize.
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.
Java I don’t know enough of to say. I never use dependencies in java because I can’t be bothered to learn Gradle/maven/eclipse/whatever.
Python I completely disagree. First, I believe all (non-python) libraries are distributed as binaries, no local compilation at all. Which makes the issue of the content not matching GitHub even worse.
Secondly, python is used as a glue language. Most of the time, it’s just a way to interact with bindings to a C library. There’s no big project that uses only the standard library.
Lastly, in python, whatever you want to import doesn’t always match the pip install command. In your code you might say “import MyAwesome69”, but the command to install it is “pip install awesome lib”. Any malicious actor would just need to publish a python library called “myawesome69” and it would get many people trying to install “awesomelib”. You have to know the magic words to install each library. And projects rarely tell you how to install dependencies. Requirements.txt is a joke (if you want to automatically create it, it puts every single installed library on your machine/venv, not just the ones used in your project), but you’ll be grateful if the project you want to run provides one. Also, nobody distributes python programs as executables, which means everyone who wants to run it must know the magic words, not just the developers. Moreover, not all dependencies are available through pip. The install instructions might say “install awesomelib”, but when you “pip install awesomelib” you pull a malicious library instead of installing the actual awesomelib available via “sudo apt install awesomelib”
I don’t usually use libraries in my python scripts, but that’s because I use it as a scripting language, they rarely reach 300 loc. If you want to use tl make an actual program. You’re gonna pull a lot of dependencies.
C++, like java, I can’t speak of, because installing a library was such a pain in windows without Visual Studio that I was never able to. Might explain why they don’t use many libraries.
This entire post is so ignorant it can be summed up in a one paragraph analogy:
“Why do everyone love screwdrivers so much? I drove in nails perfectly with my hammer, but the screwdrivers are so bad at it! Who even designed them? What a horrible design!”