And very delicious! I love the pasta shape in my mouth haha

Oh god yes! Every time im in germany i will stop at an ice creamshop for this!

I have terrible friends haha

Tried that on the last install i had to do. Doesnt always anymore. Task manager was hidden by the setup a few times when i did that :(

I ended up using rufus to patch iso pre-extraction hehe :)

Thats interresting, thanks! Stuff for me to look into!
I also think halfway through the conversation i might have given the impression i was talking about pointers, while it was not my intention to do so. That said, the readonly/mutable reference thing is very interresting!
Ill look into what rust does/has that is like the following psuedocode :

DataBaseUser variable1 = GetDataBaseUser(20);
userService.Users.Add(variable1);
variable1 = null; // or free?
[end of function scope here, reference to heap now in list ]

That sounds odd. That also means that a mapper, command, service,... can never return a class object or entity. Most of the programming world is based on oop o.O
Keep in mind im not talking about the usage of pointers, but reference typed variables.

Thanks for the response. Ive heard of rust's compiler being very smart and checking a ton of stuff. Its good thing it does, but i feel like there are things that can cause this issues rust cant catch. Cant put my finger on it.
What would rust do if you have a class A create something on the heap, and it passes this variable ( by ref ? ) to class B, which saves the value into a private variable in class B. Class A gets out of scope, and would be cleaned up. What it put on the heap would be cleaned up, but class B still has a reference(?) to the value on the heap, no? How would rust handle such a case?

Serious question, how would using rust avoid this? Rust still has reference types in the background, right? Still has a way to put stuff on the heap too? Those are the only 2 requirements for reusing memory bugs

I agree. When i got my framework 16 it just felt like suddenly i had freedom in my hands, a breath of fresh air. It was amazing in the first week learning all the hooks and crannies of their mad design and open schematics.

Youre right, but with framework the motherboard isnt hard connected to the connectors/ports of the laptop. Or any hardware really.

Yes!
They have released multiple new mainboards for the framework 13 which upgraded the cpu. This is a new mainboard with the latest intel cpus. They have always allowed everyone to just buy the board so they can upgrade their existing framework 13's, thats their whole stick : modularity.
This time they also have a new screen panel and battery you could get to upgrade your system.

Also obviously new systems can be bought with the new hardware from the get go too.

I have a framework 16 that my boss got for me. Im a trial to see if we can save money by going framework instead of dell for the laptops developers use as things like the ports on the side, batteries and mainboards are easily replaced and upgraded. No need to waste +2600 euro every 3 years per laptop either if we can just swap the mainboard. They didnt want to finance the gpu, but when the laptop is mine after 3 years i will probably get the gpu for it :)
(In a framework 16 a gpu can be plugged in or replaced. Framework 13's always use integrated gpu )

Even google's ai overview agrees its the truth there!