To improve determinism, define a system instruction with explicit rules for your specific use case.
"Please be deterministic".
HN user
Freelance web developer & open-sourcerer.
Currently building `nuqs`, a type-safe search params state manager for Next.js - https://nuqs.dev
- Homepage: https://francoisbest.com - Bluesky: https://bsky.app/profile/francoisbest.com - GitHub: https://github.com/franky47
To improve determinism, define a system instruction with explicit rules for your specific use case.
"Please be deterministic".
The Peek mode is insanely good, it reminds me of those exploded views of buildings and "how things work" children books.
The model seems to be having a hard time with the marble floor in the quire (low resolution), is this because of its reflection?
The live translation demo reminds me of the Babel Fish in The Hitchhiker's Guide to the Galaxy. This could be very valuable to have in your headphones while travelling.
Not super impressed by the model constantly interrupting the user in the other demos though.
Might want to set `overscroll-behavior: contain;` on those scroll areas, having the whole page move up and down (or worse, navigating Back when scrolling left) isn't great UX.
https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/P...
"You forgot to say please"
I once made the mistake to reply one of those threads with a public email address, it's now an incubator for AI-generated spam. And not just slop text: now we're getting full vibe-coded HTML UI..
Example: https://bsky.app/profile/francoisbest.com/post/3mhq6znfcxk2d
The whole point of shadcn/ui is that it’s customisable (that’s why the components are copied into your app as opposed to installed from a central npm package).
This is made easier with the /create UI: https://ui.shadcn.com/create
People use it like a design system, but it’s more like a design system for design systems.
Do you not risk having a client app that falls out of sync with the server’s API endpoints?
Loved the headings btw.
I’d love to see someone try.
Though using AI to build the devtools we used for signal analysis would have been helpful.
I used to do that exact job 10 years ago (without AI, obviously). I figure that career would be very different now.
There was something exciting about sleuthing out how those old machines worked: we used a black box approach, sending in test samples, recording the output, and comparing against the digital algorithm’s output. Trial and error, slowly building a sense of what sort of filter or harmonics could bend a waveform one way or another.
I feel like some of this is going to be lost to prompting, the same way hand-tool woodworking has been lost to power tools.
Especially when the "content" is a blatant AI summary:
Duffer’s advice highlights a conflict between technological advances and creators' goals. Features like the ones he mentioned are designed to appeal to casual viewers by making images appear sharper or more colorful, but they alter the original look of the content. By asking fans to turn these features off, he is stressing the importance of preserving the director’s vision.
Disappointing they didn't have their research facility in Cheyenne Mountain.
This is hilarious, thank you!
How did it match my facial hair in the XKCD, since HN is text-only? :mind-blown:
That’s what CI is for.
Refined GitHub [1] still does (for things like PR approvals & automations), and it feels odd indeed. Still worth adding on top of the stock UI.
Sad, I wrote my first ever programs on Arduino, learned C++ through it, and did my first OSS contribution by creating the Arduino MIDI Library, ~16 years ago.
I wouldn't be where I am if it wasn't for Arduino. Thank you to the OSH community for making these boards open to all back then.
I gave my kids (5 and 2) two Volcas (Beats & Keys) to play with. The Keys is a bit too advanced (too easy to get no sound at all, or something that sounds horrible), but the Beats is a wonderful machine for kids, as it's virtually impossible to make it sound bad. Also great to teach them rhythm.
Except you hit limits when trying to share that URL. Eg: try pasting a URL longer than 4096 bytes in Signal or WhatsApp, and they don't render it as clickable.
Thanks for mentioning it! (I'm the author)
Thanks for the feedback, Vercel domain uses nuqs [1] (I'm the author) for URL state, and I agree flooding the browser history is a bad experience.
Is there a way to update the URL (ie: keeping it reactive in the address bar) without creating those history entries, or to ask the browser to squash the last entry it created into the previous one?
[1] https://nuqs.dev
Cursed alphabetical sorting of numbers:
8 5 4 9 1 7 6 3 2 0
Can you guess what it is?
The reaction (removing the package) is also similar to an inexperienced developer when confronted to their first vulnerability report.
Assuming good intentions (debugging) rather than malice was at play, communication is key: drop the malicious version of the package, publish a fix, and communicate on public channels (blog post, here on HN, social media) about the incident.
A proper timeline (not that AI slop in the OP article) also helps bring back trust.
It has a (albeit experimental) flag for transforming enums, namespaces and other runtime-impacting aspects of TypeScript, if that’s what you were referring to?
https://nodejs.org/api/cli.html#--experimental-transform-typ...
You can run TypeScript natively in Node.js 24, actions based on that runtime don’t need a build step.
And ruin a good 90’s film & series’ SEO in the process.
One thing I was thinking of was sort of a "delayed" mode to updating my own dependencies.
You can do this with npm (since version 6.9.0).
To only get registry deps that are over a week old:
$ npm install --before="$(date -v -7d)"
Source: Darcy Clarke - https://bsky.app/profile/darcyclarke.me/post/3lyxir2yu6k2sWhat’s a good (ie: opinionated) code formatter and unit test framework for C++ these days?
I just had a PR on an old C++ project, and spending 8 years in the web ecosystem have raised the bar around tooling expectations.
Rust is particularly sweet to work with in that regard.
Anthony Fu’s epoch versioning scheme (to differentiate breaking change majors from "marketing" majors) could yield easy winners here, at least on the raw version number alone (not the number of sequential versions released):
I don't know if it's intended (and if so, hat tip to the designer), but the logo is not aligned: the arrows should form an X in negative space, but the horizontal distance between the left & right arrows is smaller than the vertical distance between the top & bottom ones.
The Theremin mode in the reply was also very good!