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.
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..
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).
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.
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 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?
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.
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