Thank you for the clarification. Very cool project!

I’m not really an OS guy, so forgive me if this question has an obvious answer. When a thread migrates, it keeps its stack and register, thus any data contained within this can be used in the destination process (correct me if I’m wrong). Thus sending a message could be as simple as migrating a thread and having that thread copy data from its registers or stack memory to the current process’s memory space. However, how does the thread find process-specific addresses and handles (e.g. a mutex)? For example, I’m picturing a scenario where you are implementing an MPI library and want to use thread migration to send (small) messages from one local process to another. The thread orchestrating the send simply loads the data from memory and migrates, but how will it know where to store the data to? Would there need to be a data structure stored in a fix offset in memory that contains the destination address of the receiving process?

deleted by creator

It’s also the basis for a popular hardwaregeneration language, chisel. No clue why they chose it

OK, but being a victim doesn’t make you immune to this categorization. A victim of sexual abuse who rapes someone is still a rapist. Someone who was persecuted for their race who then persecutes others for their race is still a racist. Victims don’t get a “Get Out of Jail” card.

I don’t think engineers need encouragement to be cynical. More often engineers need to lighten up.

But then that’s not evolution?

Think that sounds far-fetched? Evolution figured it out with single-cell organisms 2 billion years ago, and they haven’t faltered since.

The “brain” that is in these robots is incredibly simple and does not have the capability to learn. While it feels like tech is breaking boundaries every day, having any serious amount of computational power that simulates learning at this small of a scale is incredibly far off. The fear mongering is not necessary.

I mean, I like Longlegs, even though a lot of people were upset by the 3rd act. I think this movie is outside of that “guilty pleasure” area. The Monkey knows what it is and does it well.

Biggest con of KDE + Krohnkite (to me) is no text-based config. I really have no desire to pour through the GUI to set up all my keybinds. I’ve tried this setup before, and honestly I mostly like it. However anytime I want to change something I just hate having to click through a menu with my mouse. The search bar helps, but often you’ll spend a lot of time guessing what the devs decided to name a setting. I went back to Sway and have no regrets. Though I’ll admit I wish there was something that was basically Sway with the benefits you mentioned here.

OK, but not everyone produces technical debt at the same rate and not everyone takes responsibility for what they produce, so the point is still relevant.

I don’t really see how what you detailed in your summary connects to your thesis. How are things like more registers and less cycles for branches related to using RISC over CISC? It reads more like the microarchitecture of the MIPS is better rather than the approach of the ISA.

The IEEE standard actually does not dictate a rounding policy

I guess your battery isn’t overheating?

I personally recommend Multi Launcher, which is KISS with just a few more features that stay out of your way if you don’t want them

The amount of CPU time compiling code is usually negligible compared to CPU time at runtime. Your comparison only really works if you are comparing against something like Rust, where less bugs are introduced due to certain guarantees by the language.

Regarding “language constructs” it really depends on what you mean. For example using numpy in python is kind of cheating because numpy is implemented in C. However using something like the algorithm libraries in Rust woulf be considered fair game since they are likely written in Rust itself.

kitty. The ssh kitten is enough reason to use it. I work ob a lot of different systems that require OTP. Using the ssh kitten I can type the OTP once and can spawn new terminals that ssh and cd to the remote direvtory without logging in again. Obviosly the tabs and window panes are are a must too. There’s tons of other useful features that I like, like using hints to select nunbers, filenames, urls, etc in the terminal output.

Not sure I understand your comment on multithreading. pthreads are not very hard to use, and you have stuff like OpenMP if you want some abstraction. What about C is not ideal for multithreading?

Every time I’ve looked into it, most advice I’ve gotten was that it’s not a good idea.

Thanks for the details! I have done MPI work in the past, so I was curious how an MPI implementation and iceoryx2 might be similar/different regarding local IPC transfers. It’d be interesting to do a detailed review of the two to see if they can benefit from each other.