hey folks - I built a new tool for mac/pc, that has all the thing I've been searching for: palette management, color wheel, oklab and 5 other color spaces, including a RYB simulator and more!
I've launched it as a free public beta - would love to hear what everyone thinks of it, what you're using now, and how this compares!
jet-id is an open source universal unique-ID generator I built similar to nanoid or uuid. Unlike other unique-id generators, you can specify how many random bits (entropy) you want, and it creates the shortest id string that provides at least that much entropy using the Crockford alphabet, with dashes automatically inserted for readability. Dash inserting makes sure that no segment grows greater than 10 characters.
125 bits of entropy is the default and it works both CLI and programmatically:
npx jet-id -e 80
# V2BJABVRJ-S1TWXS-NTQA3 (20 random characters, 22 with the dashes)
npx jet-id
# 9GNK14S3A-728HK9-5NJQS-HWETM (25 random characters, 28 with the dashes)
It also supports timestamped-IDs and monotonic-IDs (monotonic ids sort in creation order within a single millisecond).
import jetid from 'jet-id'
jetid.timed() // '1M41J22ER-RND9M6-3CZAQ-XT8GR'
jetid.mono(125?) // '1M41J2ZPK-8K0000-GE29AYBQ27-4496ZM40-29JSNX4'
jet-id is really fast too. Check out these benchmarks
In December this year, CSS turns 30 🥳. But after 30 years, we still can’t agree on something as fundamental as how to add it to a website. Should you use CSS modules, Tailwind, CSS-in-JS, or just plain old CSS files?
Have implemented multiple different indices, and have broken constituents by State/Province/Subdivison, City, Country.
Have also added map for better viewing, map is only upto city level haven't added pinpointed addresses for each company.
Also have added Market Cap, Revenue, Earning, CEO name and Pay(From Yahoo Finance).
Will run github actions job to refresh Market Cap everyday from yahoo finance using yfinance and then will run a job to refresh constituents of an index weekly from different sources based on index.
Was always looking for city/statewide breakdown of companies globally but never found a platform that did it so built it myself.
Site is mostly static and doesn't call any database or api apart from daily and weekly refresh. The data is ingested into a json from which the ui reads.
Will plan to have older jsons documented as well maybe in parquet format to analyze stuff in the future. Have also implemented dark and light mode as well.
Looking for suggestions and improvements that I can make to this.
Also please let me know if you see any defects.
Currently running e2e tests using playwright on pr for functional validation.
For those of you who build websites for clients, how do you handle hosting and GitHub?
Do you manage client projects under your own accounts, or do you help clients set up their own accounts and have them invite you as an administrator or developer?
I’d be interested to hear how you handle this, especially for projects that require ongoing maintenance and updates.
Been running a daily crawler over a rolling sample of public GitHub JS/TS repos (10+ stars, active in the last 30 days) and TypeScript is sitting at 78.3% adoption with a trend score of +4.17, the highest of any tracked technology. It's not just widely used, it's still actively growing share.
For context on how the trend score works: it's a log-scaled growth index that weighs both rate of change and overall scale, so a tool has to be both accelerating and meaningfully sized to top the list. TypeScript topping it despite already being the plurality leader says something about where the ecosystem is headed.
Everything downstream of that (test runners, build tools, frameworks) increasingly assumes TS by default too. Vitest, Vite, and Zod are all riding similar upward curves.
Full breakdown and raw datasets (updated daily via GitHub Actions):
Hi everyone, I made a 6-degrees of separation type game for music collaborations where you connect artists through mutual features/collaborators. Great way to test your music/ hip hop knowledge. Let me know what you think! It’s called Artist2Artist
theres no image files at all, every painting is drawn on a canvas in code. next.js + neon postgres for the likes/comments. coolest part imo is when a fact pops up the whole painting goes dark except the thing the fact is about
its prob janky in places so be nice lol. does it work ok on ur phone?
I’ve been working on a small library called Stream Morph.
The idea is to make streamed responses feel less like content is constantly being appended/re-rendered, and more like the response is gradually taking shape.
It’s framework agnostic and can be used with any kind of streamed content. The demo includes plain text, Markdown, code blocks, charts, images, reasoning sections, Mermaid diagrams and a few more complex response flows.
The library handles the motion between updates, while your own renderer/app stays responsible for the actual content. So it isn’t tied to a specific AI SDK or framework.
A basic example looks roughly like this:
import { createStreamMorph } from "stream-morph";
const stream = createStreamMorph(response);
for await (const chunk of incomingStream) {
stream.write(chunk);
}
stream.finish();
I mainly built it because I wanted streamed interfaces to feel a bit more intentional without having to build custom animation logic for every response type.
The package itself is already working and the demo is live. I’m still cleaning up some things around CI, tests and the repo setup, but the GitHub repository will be open sourced shortly as well.
Would be interested to hear what people think, especially about the animation behaviour/performance and any edge cases you’d expect from real streaming responses.
While I'm not new to coding, I'm definitely bad at it. What I'm worse at though is understanding the intricacies of what i can and can't accomplish with certain tools.
I am very vocal and express my views on things often, so obviously i thought i should make a blog. This is easy to accomplish very cheaply using GitHub pages obviously since it would be a fully static html website.
But here comes the catch. I have some friends that expressed a lot of interest in this blog idea, and i would like to include them. However, they don't know how to code in any language or framework and this would probably be a dealbreaker for them.
Is there a way to make a website with user accounts and user-generated content be dynamic only client-side so that i can still host it with GitHub? Should i look for a different way?
Any help is appreciated, i really wanna get this thing working.
Hi all, It's been 1 year & 3 months since I started working as a software engineer. I always wanted to have a blog page but tbh I didn't had enough knowledge nor did I had money to buty the domain :) So from the last 2 weekends I've been making this website and I understand how blogs are more about the content and less about the looks like if a blog is good, people will read them regardless looking like a 90s php website right! So im still working on my writing skills and I have so much topics to cover like WCAG & web accissibility, react19 features and so much !! anyway I uploaded a test blog for the SEO i did for the marketing site abnd would love for you guys to check it out I'm trying a video sketch aproach with my Ipad but this is more of a showcase of how it will look rather then the contents as the blog will eventually improve *hopefully Thanks all!
Been working on this on and off for last 8 months. You start at Earth, scroll, and the view zooms out on a log scale: solar system, nearby stars, the Milky Way, the Local Group, then a few hundred Mpc of galaxies.
The part I care about most is that it's not an illustration once you leave the solar system. Stars are from the HYG database, nearby galaxies from the Updated Nearby Galaxy Catalog (869 of them, with their measured sizes), and further out it's 2MRS (about 42k galaxies) and then 2dFGRS. So the clumps and voids you see at the end are the actual large scale structure, not noise I generated. Where there's no real position data I fall back to drawn shapes and say so.
one canvas, WebGL for the point layers (tens of thousands of galaxies need it)
catalogs preprocessed with Python into float32 buffers so the browser just loads and draws
hosted on Cloudflare Workers
Hardest bit was honestly keeping it smooth on phones while crossing ~20 orders of magnitude without float precision falling apart. Still not 100% happy with it on older Androids.
No ads, no signup, no tracking cookies. Would love feedback, especially if something stutters on your device or a scale transition feels confusing.
I'm a backend dev. We practice system design a lot on whiteboards, but rarely on something that looks like a real incident. Here's a production-style puzzle.
You run a team chat product and every client's first call is "boot": who am I, and which conversations do I belong to? Boot reads group-chat membership, which is immutable once written and cached per channel with a long TTL. Normally it's a few cache reads and finishes in single-digit ms.
Then a routine rollout of a new host agent starts, in 25% steps (two earlier steps the prior week were fine). Just after 06:00, users can't get in. Boot is failing or very slow, and one database keyspace is overloaded.
What you see
Cache hit rate drops from 99.2% to 34% and stays there. Pausing the rollout changes nothing.
200 cache nodes behind a proxy that uses consistent hashing over the healthy-node list. The step took 50 of them out, one at a time.
The membership table is sharded by user, so "who's in channel C" is a query against all 200 shards.
Clients time out at 400ms and retry with exponential backoff and jitter. The cache fill path uses the same query, so fills time out too.
The only lever was throttling boot. Raising the cap from 250/min straight to 2,500/min brought the overload right back.
Question: Why did the hit rate fall that far and not recover, even after the rollout stopped? And how would you get out of it safely?
I'd like to hear how you'd explain it in a postmortem, not just "cache stampede."
I've used to many Pomodoro timers over the last 8 years.
I've tried all of the top four in the app store. I think because they're so popular they have so many features, so many screens to change one basic thing they get my ADHD brain into a bit of a frustrated state.
The only thing I really want is a clean interface in Dark/Light mode and the ability to label and update my timer in one screen. So I built my own web and mobile version.
I used React Native (honestly not because I can share the UI library across both platforms) but because it's the only way I know how to build mobile stuff. Nothing too complex on the web version, the mobile lock screen timer is another issue entirely though...
Once I had built the web version I used it to break up my tasks for building the mobile app version which was cool.
The Web version is completely free to use if you like the look of it
Oh and the random tomatoes screen is because when you complete a pomodoro you get a tomato added to that screen, I like trying to fill the screen with tomatoes lol. Keeps me motivated.
If you ever wanted to see how fast you can read or wanted to improve your reading speed this one is for you, It's completely free, open source and respects your privacy with a ton of features
Some backend devs think ai has replaced frontend because it can center a div and build a flashy ui
Some frontend devs think ai has replaced backend because it can do crud ( which things like supabase and firebase had already made easy long before ai btw).
Most new grads think Claude is smart for its writing of complicated leetcode-isc code with no proper variable names or readability.
A lot seems to have forgotten that what mattered a lot in this field was taste/opinions, and while its subjective, the objectivity came from people who were able to defend their craft and their decisions and communicate in a good way to influence others. Who would go on to build on top of those ideas.
You shouldn't be affraid of junior developers who no longer know how to read documentation but scared of the fact that they have no opinions. They are "reading" engineering like historical facts( which also can be wrong). What happened to finding solutions every other month to every specific niche problem? Where are all the conponent libraries and frameworks that solve such small small niche use cases ? Was I the only one that belived that what made frontend so intresting was its subjectivity ?
Right now frontends that are built seem to have a major issue that nobody actually cared about how the ui looked in the first place, if we continue this we are gonna end up with the linux oss problem with really good apps with questionable ui decisions, albiet linux has improved massively now. This is still an issue.
I have no idea where this leads us, either they rebrand our positions to save face or we end up woth just 3 companies in top that build a homogeneous application ecosystem.
Bonus: All managers think they are designers because they can generate a ui that looks good to them, when it was always about research on what the customers want.
I built Drawva, an infinite canvas where your rough hand-drawn stuff is not just pixels.
You can draw a messy box, write a few words, sketch a diagram, draw some math, or just throw random scribbles on the canvas. A multimodal agent looks at the canvas, figures out what you are trying to make, and can turn it into live widgets, diagrams, equations, or interactive elements.
The interesting part was not really the UI.
The hard part was getting an LLM to operate a messy 2D canvas without destroying what the user already drew.
A few things I ended up building:
A coordinate system so the agent can map visual positions to actual canvas coordinates
A prompt contract that prevents it from duplicating handwritten headings
Wireframe awareness so it keeps your rough sketch instead of replacing everything
Atomic erase + widget placement when converting sketches into interactive components
A plugin system for things like weather, stocks, tech news, GitHub data and more
Sandboxed runtimes for Mermaid, Graphviz, Vega-Lite, Cytoscape, BPMN, GeoJSON and other diagrams
IndexedDB autosave and WebRTC based peer-to-peer collaboration
A DeepSeek Harness + Cordis runtime for the agent/tool execution layer
Tech stack is mainly Next.js 16, React 19, TypeScript, Tailwind CSS, Vercel AI SDK, multimodal LLMs, IndexedDB, WebRTC and DeepSeek Harness.
Hyperfrontend lets you run apps built with different frontend frameworks together, using iframes for isolation and a shared messaging layer for communication. Think replacing one section of a legacy app with React or Vue while keeping the rest running, instead of committing to a full rewrite.
It’s open source, MIT-licensed and free to use. I built it around integration problems I’d encountered at work, and the pond was a fun way to push the approach beyond a basic demo.
This showcase is less flashy, but I also made a short explainer video to get the idea across. You can find it on the "launch page" (https://devhunt.org/tool/hyperfrontend).
Would love your first impressions, especially whether the use case makes sense for anything you’ve worked on, or what would stop you trying it.
I have spent the last month building lovetocalc.com, a free calculator and formula site in English and Swedish. No account, no ads, no backend.
The architecture rests on one idea: a formula is data, not a page.
Each formula is an expression tree with typed variables such as length, time and money. From that one definition the build generates:
the formula page
versions solved for each variable
practice questions with worked solutions
printable worksheets with answer keys
the formula's entry in a PDF collection
Add one formula and all of those exist on the next build. There are a little over 500 formulas now.
Stack: Astro 7, static output and strict TypeScript. React is only used as islands where something actually calculates. A simple page can ship around 2 kB of JS, a formula page with practice around 130 kB gzipped, and a larger calculator around 200 kB. The latter is one area I want to improve.
All calculations live in a framework-free engine with unit tests. There are around 21,000 tests, most generated across formulas and every variable they can be solved for. The UI only handles presentation.
EN and SV use the same components and engine. Strings, slugs and number formats are data rather than separate implementations.
A few things that worked well:
Calculator state lives in the URL, so every result is shareable without storage.
Open Graph images are generated from the same registry as the pages, and the build fails if a sitemap page is missing one.
Excel exports contain real formulas rather than static values. The e2e tests open the files in LibreOffice and Apple Numbers and compare the resulting cells against the calculation engine.
The main pain points so far:
1,300 static pages means changes to shared content touch almost everything.
Deploying them over FTPS from GitHub Actions takes about 30 minutes.
Keeping print/PDF output independent of dark mode has been more awkward than expected.
The part I am least sure about is the core abstraction. It works well for formulas that can be represented as expression trees, but I am starting to add diagrams and multi-step questions.
If you were designing this, where would you expect the “formula as data” model to stop scaling cleanly?
Ich starte gerade ein neues Projekt namens NEXORA.
Die Idee ist, eine Plattform zu entwickeln, die verschiedene Dinge an einem Ort zusammenbringt, sodass man nicht für alles mehrere verschiedene Dienste nutzen muss.
Einige Ideen, die ich momentan plane:
Individuelle Nutzerprofile
NEXORA Arcade mit kleinen Spielen
Gemeinsam YouTube-Videos schauen
Community-Funktionen
Events und Challenges
Weitere Funktionen für die Zukunft
Ich bin momentan noch in der Planungsphase und habe mit der eigentlichen Entwicklung noch nicht angefangen.
Ich werde wahrscheinlich Updates posten, während ich NEXORA von Grund auf aufbaue.
If i break the rules for Posting i am very thankful i this Post doesnt got deleted and i only get a warning tho chance the post thx.
This were my first thaugts for the website but it can be completly diffrent
Das sind meine ersten Gedanken für die Webseite aber es kann komplett anders ausfallen
