UltimaDB, a high performance full-featured MVCC transactional embedded database, with special focus for use on SMR clusters.
UDB has full transactions, selectable persistence (in-memory, eventual, strict) and consistency (SI, SSI). A lot of time was spent on performance.
Written in Rust, with 8k line of code and 15k lines of tests, 96% coverage.
Formal verification with Lean 4 is in progress (see /formal), also consistency checking with elle/jepsen is in progress.
It uses phase change (solid to liquid) to store heat at about 200 kJ/kg. Compare this to heating water in a boiler from 10c to 60c - stores 209 kJ/kg.
So we already have an effective way to store heat which can work for decades without servicing and is also cheap to produce (in terms of money and energy consumption).
Is supported on more platforms, has more developers, more jobs, more OSS projects, is more widely used (Tiobe 2024). Performance was historically better, but c# caught up.
LLMs are learning in a very similar way humans are learning. So if humans can read a text (or view a video), learn from it and then use the knowledge to produce something, so can LLMs?
Copyright laws have quite strict rules on what constitutes a copy, and this was tested in courts many times. This rules also apply to works produced by LLMs.
You must be using a dynamic language with a heavy framework? Rails maybe?
I code in Go mainly (also Java and Rust) and never experienced what you describe: simple addition of a field to a struct does nothing if not used in code. And the use is simply checked by compiler.
However, I did work alongside a Rails team which had major gripes with this. They called it brittle tests: whenever they made a simple change (like adding a field), half of their tests would fail. This really lowered devs' confidence in their codebase and slowed the changes to a halt.
If you are concerned by this proposals, then you should check out current CAs trusted by your browser - all those CAs can issue rogue certificates trusted by your browser, that can be used in MITM attack.
For example, CAs present in Firefox, that might give you pause: Beijing Certificate Authority, China Financial CA, Guang Dong CA
The CA system in browsers is inherently broken and it allows state actors to MITM you and see all your traffic if they:
1. have ability to capture IP traffic (requires cooperation with ISP)
2. have ability to generate rogue certificate via cooperation with CA
The problem is that at that point liquid hydrogen already spent 70% of the energy stored in it (80% efficiency of electrolysis * 40% liquefying efficiency) .
UDB has full transactions, selectable persistence (in-memory, eventual, strict) and consistency (SI, SSI). A lot of time was spent on performance.
Written in Rust, with 8k line of code and 15k lines of tests, 96% coverage. Formal verification with Lean 4 is in progress (see /formal), also consistency checking with elle/jepsen is in progress.