As far as I know, critical systems like reactor control software is mathematically proven first and verified after implementation. I don’t think you can go beyond that.
The property grid control is still the greatest general purpose UI of all time. Define your classes with some attributes and it just works. It was all downhill from there with web and mobile.
The reason was the coders' mindset who entered the job market after 2000, maybe up to 2010, that the ability to code (to use a programming language) is the ultimate development of homo sapiens. With that solved by AI, we can safely start going back to simple, sane concepts like low-code and no-code, property sheets and drag & drop user interfaces.
Because I learned on this, it made learning everything else that much harder. Even today I wish there was something as functional, basic, and intuitive, even though I well.understand the reasons for doing things different ways.
It's about prioritizing candidates for the costly initial audition, and breaking symmetry for the introduction, something particularly useful for people who can't just approach other at random in a social setting.
Dear Google, please don't turn off your old generally available Pro-class model before your new Pro-class model is generally available (previous discussion https://news.ycombinator.com/item?id=49668196 )
Yup, tried all variations of that. There's the advantage that you can use a lower hallucination OCR specific model for the pre-processing, at least for clean text. But for something hard like handwritten forms, applying VLM with context is less error prone than preprocessing to text.
Also - and this is bizarre - the token cost of doing that is higher, not lower, at least in Gemini world, and by a large margin. That's very counterintuitive, but a page encoded as image tokens can be smaller than same page as text, and is not meaningfully lossy on documents that are just typed text because the models are well trained on those.
We sure did. It's a great writer, better in a harness, will process lots large context, but complex reasoning with convoluted rules and low hallucination tolerance? That's still larger model territory.
Completely free flow typing is risky in terms of interpretability, but type narrowing - var a : supertype; if (a is subtype) { // a is known to be subtype }, or type case, saves boilerplate in any OOP language.
seems to respect reduce motion just fine! the animation, while extremely lovely, also does seem to be quite taxing on my GPU (~60% usage on M1 Max with Zen/Firefox, on a 1440p widescreen, which is admittedly quite a lot of space to render animation)
love the website though, i hope i one day will be able to make something that elegant!
Every technical topic involves AI now. Even if it's about why the ancient Greeks didn't turn their steam engines to industrial use - the AI's should be researching the details. We might as well ask which topics involve humans or use language.