As with any good (and especially "currency"), it's only worth 1 USD as long as somebody (including the issuing company) is willing to give you 1 USD for it. Even if it is "linked", "pegged" or called something else.
I generally share your skepticism, but didn‘t DeepSeek prove that one does not need a „competitive advantage“ in hardware? And if that does not hold for HW, it likely also doesn't hold for energy.
The competitive advantage of DeepSeek IMO were the engineers. Some pretty hard-core optimizations went out of their lab, and this is what I think is a major differentiator between success and failure. You can have all the HW you can wish for but if you don't have the right set of people you're not gonna make it. Many companies think that they have the right set of people but they don't.
If they do, who says they get to keep them? Hell, even if they do get to keep them, who says they're the still the right set of people in 5 years?
Mistral seems clearly sensible to keep around for some powerful and wealthy people, and I have no problem seeing why. They might not even all be Europeans.
Probably it’s not about gaining a competitive advantage but more about bringing down the costs to run frontier models in the EU to a level where it’s a viable enough option to bring down the risk of relying on the US and china entirely.
The underlying system API is a u16. Do you propose that this library should add logic to clamp the value between 0 and 255? What would be the point in that?
"NVIDIA began implementing SPARK in its security strategy in 2019 on select pieces of firmware. They began training additional personnel in SPARK and eventually developed an in-house training program.
Several NVIDIA teams are now using SPARK for a wide range of applications that include image authentication and integrity checks for the overall GPU firmware image, BootROM and secure monitor firmware, and formally verified components of an isolation kernel for an embedded operating system, to name just a few."[0]
> NVIDIA is working with AdaCore to implement Ada and SPARK programming languages into certain firmware elements to reduce this potential error. In this webinar you will learn how the combination of NVIDIA hardware with Ada and SPARK delivers robustness and security, improving efficiency and safety in the development pipeline.
I disagree with their politics, I'm concerned by the multiple privacy incidents, and I generally refuse to support them until they refocus on Firefox instead of all the other stuff they're doing.
If they worked only on Firefox, I'd have nothing against them. As it stands, I can't even donate to Firefox if I want to.
Love the image of the monitor showing Battle Chess! As a side note to all like-minded people that love old DOS games, check out the library of DOS games on archive.org: https://archive.org/details/softwarelibrary_msdos_games
I‘m curious: How does Zyn integrate with non-Zyn-style projects? I.e. I have CMake/whatever project X that just tries to find dependencies and lists them in some readme to be manually installed by the user (I think that applies to most C/C++ projects out there).
And now, I am listing X as a dependency in Zyn. How does it deal with this situation?
Zyn can integrate with non-Zyn-style projects (like CMake or Make-based ones), but it treats them as opaque third-party dependencies and handles them externally. Here's how it works:
Cloning: When you list a Git-based dependency like https://github.com/user/X in your zyn.toml, Zyn clones it into .zyn/deps.
Build Detection: Zyn looks for known build systems (CMakeLists.txt, Makefile, etc.) in the dependency. If found, Zyn runs the appropriate commands (cmake, make, etc.) to build the project.
Dependency Isolation: Zyn does not parse or resolve the internal dependency graph of project X. If X needs other libraries (Y, Z, etc.), you must also list those manually in your own zyn.toml. This gives you full control and reproducibility.
Header and Library Exposure: After building, Zyn makes the compiled .a/.so/.lib and headers available to your main project automatically by linking them via -I and -L flags.
Example:
Let’s say project X depends on Y and Z, but doesn’t use Zyn itself and just mentions this in a README. You’d do:
[dependencies]
X = "https://github.com/user/X"
Y = "https://github.com/user/Y"
Z = "https://github.com/user/Z"
Zyn will fetch and build all of them. It doesn’t care that X has no zyn.toml.
