DacoTaco

typical hehe
governments are often more strict in rules than normal people, and those rules often prevent other rules from being enforced hehe
it shouldnt be though, they should set the bar with their own buildings :)

I agree. I often discuss this with friends and the argument of "our electricity network cant supply all that power" (which is true) is one i often counter with adding more solar panels, even to apartments.

My brother, who lives in germany, has told me about this before and i love the idea so much. Its so simple to implement and has no downsides whatsoever. The person renting the appartment buys the solar panel and if they leave they can easily take it with them.

And yet, i can not for the life of me get my land lord convinced to allow me to do this too despite it needing no permanent changes to the apartment... Solar panels rules are too strict here too, and i love that germany just embraced them like its nothing

I think you have things wrong. Any other languages can have libraries be distributed as some format that would allow applications to use it, be it linux/gcc and .a files ( which are actually archives with elf/object files of the code ), or a full on library like .so/.dll.
Rust can only do .o/.dll and only have it expose like a c library afaik. Even .net has improved on the .dll and includes all its language features in it. Rust has none of that. Its not true that libraries not rebuilding are only for closed source. Its also ease of use/access and less problem prone. What if i build my library using a different version of the compiler than you and your application? I could have no problems building my library, while you cant build your application because the library i made gets rebuild and errors.
These errors happen and are all because there is no stable interface/abi and all other languages have overcome this.

Also, by default, nothing in c is rebuild unless it needs to. Thats why the intermediate .o ( elf object ) files exist, so it only has to do the relinking and not recompile and thats why .a archive/libraries in c work, because it doesnt recompile. Unless you meant the fact rust can rebuild part of a file, without recompiling it completely?

I think you dont fully understand how c compilers ( gcc specifically ) work when using multi file projects ( and not just doing gcc input.c -o output.exe ) just how i dont fully know how the rust compiler works. Also, anything using IL will always have an abi, because how else will it jump from code to IL code, so its obvious that rust to wasm will have to abide by that haha. Be it c wasm, c# wasm or rust wasm calling one another. Wasm is wasm, and you only need an exposed interface to call or include the other wasm ( c#/blazor having NativeFileReference in the csproj )

Again, i like the idea of rust, but it has a long way to go to be viable atm. And it has many pitfalls to avoid so it doesnt become the hot mess that is any framework based on node.js

I know that exists, but whats the point of that? You loose all advantages of rust when you use the library then because it cant predict application state with the library code. There is a reason all those rust libraries are compiled locally when you compile a rust application. Its a major lacking point for rust, and as long as it lacks that its dead in the water for big projects.
Again, i like strong type stuff and i like the ideas of rust but it is not grown up enough for me

What is this abi and standard calling methods you speak off? Are you a rust-non-believer or some shit! Rewrite it all in rust, no questions asked!

( i too like the ideas of rust, but without a decent abi or not constantly changing interface, its useless to me. I dont want to rebuild all code, including libraries every time i update 1 library in my application )

Saaaaame. But sometimes even strongly typed stuff wont break on compilation time

Its funny cause its true. I often design tests to be "if a case/enum value is added this test will explode and tell them to add code here"

Their source code repo contains a copy of libogc for wii/gc builds because they were annoyed at us. And i do mean a copy. Not a reference, or a sub-module, a full on copy that they build before building the wii/gc executable.

Their own issue, as long as we dont get reports of their broken shit...

Then there are the multiple times they cloned emu repos and butchered them into cores. Or the fact they force the core interface on emulators making them bad.

Retroarch is a nice project from a far, but the closer you look, the more you see huge ass cracks in the project, held down with duct-tape

Plus he has a following of people who like his take on being open and to the point. It feels like a breeze of fresh air sometimes.

N

As a european who has been to the uk, i agree