What’s up with all these posts lately talking as if C was the chain breaker that will let you achieve a higher spiritual level for your soul or some shit. This is at least the second I’ve seen this week.

It’s a programming language. If you want to use it, use it. There is no illuminati pulling in the strings to prevent you from learning this holy language.

That being said, like all programming languages, it’s a tool, with its upsides and downsides. Depending on the project it might be the best choice or the worst. But with the advancement in language design, there’s very little upsides compared to more modern languages, taking into account its big downsides.

Ah, a C programmer.

It’s a one line function in an example. It’s a getter.

Lmao, and they say dynamic typing is supposed to speed up the developer.

This is literally a getter function. How is a getter awful code? It’s the simplest function there is. The only function simpler than that is returning the input itself.

Python doesn’t check the types of function headers though. They’re only hints for the programmer.

For rust I use iced, as it meets all my needs and is a delight to work in. I don’t think it’s good for making graphs though. For graphs I heard that people like matplotlib (in python), which you can also use inside PyQt apps. I’ve tried using matplotlib and did not enjoy the experience at all, but I don’t know of any alternatives.

To be fair, in that article mentions the way to get rust from C. Sure, there is not a compiler written in C, but C is down there in the list of compilers needed for rust, so “just” need to compile some other compilers in the middle.

The bedrock of modern civilizations is expensive to develop, buggy and unergonomic though.

If you make C run, you probably (I’m not sure, would have to verify) can make rust run. And if there isn’t yet, there will probably soon be a C compiler written in rust, so you can choose to bootstrap from wherever you prefer.

C’s ABI will probably last longer than C, since there is not a stable rust ABI though.

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.

I believe the game was 10 days old when they shut it down. There are no concord fans. You can’t have fans in 10 days.

My guess is that they knew it was going to be a shit game, but realized too deep in the development phase. So they just released it as soon as possible and didn’t waste more money on it (marketing). My guess is that the released it instead of cancel just in case they were wrong and people actually liked it.

They are not created by people. They are created by programs.

It is a supply and demand curve.

The supply is incredibly small for a world-famous artist compared to their demand. If the reason some people can’t buy a ticket because there are no tickets left, there’s room to increase the price of the ticket and sell the exact same amount of tickets. If resellers can just buy all your tickets and sell them for 10x the price, then you can 10x the price of tickets and sell the same amount.

The problem is that you can’t just use the profits from selling Taylor swift tickets to make another Taylor swift so you can increase the supply of Taylor swift.

There are only 3 ways they can increase their Taylor swift profits: 1. Make concerts in bigger venues so they can sell more tickets. 2. Increase the ticket prices. 3. Increase the amount of Taylor swift concerts.

1. And 3. Have upper bound limits. Specially 3. Because what incentive do multi-millionaire artists to work more? If I were so wealthy, I’d strive to work less, not more.

The easiest option is 2. why wouldn’t they do it?

Sure, if I was a music fan it’d suck, but the truth is that they are corporations, and they are legally required to increase the shareholders’ value.

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.

To be fair, mechanic items, and especially electronic ones were far more repairable back then.

You could see, desolder and solder components without issue. Nowadays most of the electronics are inside chips, and only the components that need to be physically big (like those responsible for the power supply) are human sized. Sure, there are some small SMD that can be manually diagnosed and replaced, but even then you often need a lot of skill and equipment.

The good thing about Box::leak() is that it returns a raw *mut pointer. So you need unsafe{} to dereference it. Might as well: let my_ref = &mut unsafe{*ptr}; while you are at it, so you have a perfectly normal rust reference, so the function signatures don’t need any change.

The problem with Rc is that it would also require a RefCell most of the time. So the whole thing would be filled with Rc<RefCell<T>>. With the required .borrow_mut(). It would both do a pain to do and undo.

And of course I want to undo it, because RC is a shitty GC.