Windows 11 is little more than a reskin of windows 10, and they still fucked it up.

Rounded corners are mandatory (Why? I really preferred squared ones). But developers can choose to have their windows square. Why only the developers? Let the user decide how a windows looks like!

And don’t get me started on the start menu. It was a complete massacre. Tiles are gone (am I the only one that liked them?). Instead, now we pin apps to the start menu. Fine I guess, except for the fact that half of the fucking menu is taken up by fucking recomendations. If I remove every single recommendation, instead of having my space back for more pinned programs I get this message: “oh you like this precious white space? If you turned on some recommendations it would show something”. No, i don’t want recommendations, I want my start menu space back. Which btw in windows 10 used to be resizable to whatever size I wanted.

Oh and lets not forget about the volume mixer. Which some genius decided that it was better to keep it 10 clicks away from the user in the settings, instead of conveniently at one click in the taskbar. Which they also made the sound settings their own special taskbar element, instead of another taskbar program. So now if I want to replace their shitty sound settings with the ones I like (trumpet btw), now I would have 2 sound settings in the taskbar, while in win10 I only had 1.

And whose Idea was to join the sound settings and internet settings in the same taskbar button visually? Which is also not the same button functionally. You see, if you press the left side of the button it opens the sound settings, but the right side opens the internet settings. How much do Microsoft UI people get paid?

I guess we got dark notepad, that’s nice.

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.

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.

The lava lamps are not true random though. For something to be truly random, it must be non-deterministic (no seed at all). The only way for a computer to accomplish this is to read from a source of true randomness in nature. The lava lamps are random enough, but not truly random.

At the moment, the only source thought of being non-deterministic is quantum mechanics.

So if you make a computer generate random numbers out of the randomness of quantum mechanics, you would have truly random numbers.

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.

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.

That is because when you’re a beginner, you read everywhere that you should be using anaconda and jupyter notebooks. I know because I did so. Neither of them lasted more than a week on my computer though.

Anything that’s not an integer or a range doesn’t belong inside []. Much more readable to use zip, map, filter, etc. And more powerful.

EDIT: that was meant for indexing lists. Strings inside [] for indexing ducts are fine.

I haven’t used npm. But pip is horrible. Some times I’ve used a well-known library that only works on linux, but there is no mention of it whatsoever, and it installs without problem. The error only happens at run-time (not even when importing!) and says nothing about platform-dependency. I only learned that it was a linux-only library because I happened to try running it on a Linux machine to see if it worked.

Many times you have to set up your environment a specific way (environment variables, PATH, install dependencies outside of pip) for it to work, and there’s no mention of it anywhere. Sometimes you install the library with pip, sometimes with apt, and there is no way to know which one. And sometimes the library is both in apt and pip, but the pip one does nothing.

Furthermore, good luck importing a library. You might have installed it with “pip install my-library” but to import it you have to do “import MyAwesomeLibrary3”. And pip won’t tell you about that.

The mistake was choosing a language, and afterwards searching for a use to the language you just learned.

I don’t think changing a profession’s terms to “prevent stupid jokes” is a smart move.

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.

At this rate, the US government won’t even consider it as an option! Rust is practically a hippie language.

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.

This is the talk that convinced me that C is the only language more cult-like than rust.

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.