The real deal y0

  • 0 Posts
  • 62 Comments
Joined 2 years ago
cake
Cake day: July 16th, 2023

help-circle


  • 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
















  • 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 )