Just registering the prediction.
# if >10 then was_created_by_agent = true
$ grep -oP '\p{Emoji}' vulns.md | wc -lJust registering the prediction.
# if >10 then was_created_by_agent = true
$ grep -oP '\p{Emoji}' vulns.md | wc -lFor a long time, I used PHP and JS/TS for web projects. Now I'm using Rust with Axum/Tokio/Tower/Hyper (web server), Leptos (SSR using "Islands" flag, which also allows WASM generation for front end; JSX-like syntax), and Diesel (ORM and query builder that expects you define your schema using raw SQL). (I also leapt from DB2, MySQL and MariaDB to PostgreSQL)
It's heaven.
I came back to it recently after the Leptos 0.7 release, though, and it’s MUCH smoother.
Still early days for a framework like this, but I think it’s got a lot of magic.
Maintaining and modernizing these critical systems is important work.
Biggest limiter is memory, where the need for it grows linearly with table index size. Postgres really really wants to keep the index pages hot in the OS cache. Gets very sad and weird if it can’t: will unpredictably resort to table scans sometimes.
We are running on AWS Aurora, on a db.r6i.12xlarge. Nowhere even close to maxed out on potential vertical scaling.
And when performance tanks, it’s hard to pin the root cause to a component.
Both of these could probably be fixed by tooling. Could be z as fun research project or maybe a company.
You enforce API contracts in a monolith (or any codebase, really) via an at-least-modest amount of typing and a compiler. You diagnose performance issues via any number of tools, prominently including metrics and profilers.
My context for this is a lot of years working with backend languages like Java, Rust, etc. though the same assurances and tooling are available for most every platform I’m aware of.
We at AirGradient see that very well that more and more companies force their users into the cloud and some monitors even refuse to show current air quality when not registered to the cloud. Imagine you would need to register your fever thermometer with an app in the cloud before you could measure your temperature...
Part of the problem is not only the investors in Matter but also VC funded smart home equipment manufacturers that are pressured to go down the recurring revenue business model.
At AirGradient [1] we want to demonstrate a counter example. Our fully certified air quality monitors are open source hardware and thus we provide the firmware code and they can be easily re-flashed with whatever software you like to use. With this openness a great community has emerged that maintains integrations to various systems like Home Assistant via ESPHome.
Frustrating that the best solution is still, “well, if that’s important to you, then set that up in your home lab or rent some extra (pet) VMs in the cloud.”