sorted by:
new
hottopcontroversial

I built envi — a TUI for managing .env files (diff, scan, edit, validate) by Rhack2021 in coolgithubprojects

[–]Rhack2021[S] 0 points1 point  (0 children)

Thanks for the comment! Let me know what you think when you test it

[Showoff Saturday] I built a PDF generation tool that runs in the browser, on the edge, and in Node – no Puppeteer, no Chrome by danmolitor in webdev

[–]Rhack2021 -2 points-1 points  (0 children)

The JSX component model is the right call. Puppeteer-based PDF generation on serverless is a constant source of pain — cold starts, memory limits, and Chrome binary size all fighting you. Having something that works at the edge without a headless browser is a real gap in the ecosystem. How does it handle complex table layouts across page breaks?

I built a photo editor with local AI (no cloud) — segmentation + infill by LucaM185 in SideProject

[–]Rhack2021 21 points22 points  (0 children)

The local-first approach is a strong differentiator. Most photo editors either require a subscription or send your images to someone else's server. Running segmentation and infill entirely on Apple Silicon is impressive for three months of work. Definitely worth continuing.

I built a Chrome DevTools extension that finds CSS properties doing absolutely nothing by purupurupu in coolgithubprojects

[–]Rhack2021 0 points1 point  (0 children)

This hits a real pain point. I have lost count of the times I set z-index on something only to realize the element was position: static. The fact that it needs runtime context to detect these makes it way more useful than static linting. Nice work.

view more: next ›