ghostlyInc
Show HN: A local WebP/AVIF converter because I was tired of slow browser tools
https://ghostlyinc.com/en-us/tools/pixel-press/
Every time I needed to convert images, I had to upload them somewhere. Slow, annoying, and not great for privacy.So I built a simple Windows tool that does everything locally.Drag & drop foldersBatch convert to WebP & AVIFNo uploads, no cloudFast and minimal UIWould love feedback.
Show HN: Pixel Press – Fast Image Converter for Windows (WebP / AVIF)
Hi HN,I built a small Windows tool called Pixel Press for fast image conversion.It focuses on modern formats like WebP and AVIF and supports batch conversion with simple drag & drop. The goal was to make image optimization for websites quick and simple.Main features: - Batch image conversion - WebP and AVIF support - Drag & drop workflow - Runs locally (no cloud)Demo...
How to optimize images for websites (WebP, AVIF, responsive images)
I tried running it in WSL, but my usual workflow is still centered around Windows tooling, so it adds a bit of friction to the inner dev loop.
Maybe moving more of the build pipeline into WSL would actually be the cleaner approach long term.
Linux just makes them visible much earlier.
I'll definitely take another look at the System.IO helpers you mentioned to avoid some of that.
Are there any other common pitfalls you’ve seen when running .NET apps on Linux that are easy to overlook?
I can run it in WSL, but since my development happens on Windows I have to copy the build output into the WSL environment and run it there. I automated it a bit, but it still adds noticeable overhead and slows down the feedback loop.
So I usually only test there when I suspect a Linux-specific issue (case sensitivity, paths, permissions, etc.).
Ask HN: Developing .NET on Windows but deploying to Linux – common issues?
I develop a Blazor Server app on Windows but deploy it to Linux servers (mostly for cost reasons).Quite often everything works locally but fails on Linux. In many cases it turns out to be things like case-sensitive paths or filesystem differences.I'm curious how others handle this workflow.Do you also develop on Windows and deploy to Linux? What kinds of issues did you encounter?
But you're right that in day-to-day professional environments they aren't used nearly as much. So it might also just be the model over-generalizing a small stylistic pattern it saw frequently in certain parts of the corpus.
Words like “goblin”, “gremlin”, “yak shaving”, etc. are common in engineering culture to describe hidden bugs or messy systems. If those appear often in the training corpus or get positively reinforced during alignment tuning, the model may overuse them as narrative shortcuts.
It's basically a mild style artifact of the training distribution, not something intentionally programmed.
Things like generating boilerplate, quick test scaffolding or documentation lookups. Each one is small, but they compound during the day.
That’s probably why it’s hard to capture in traditional studies.
Curious: has anyone seen studies measuring task-level productivity instead of overall output?
If a title resonates ("coding at 60 again") people often upvote before even reading the post.
That alone can create these huge spikes.
Doctors who can code have a huge advantage because they understand the real workflow problems in hospitals and clinics.
Some of the best medical software I've seen was built by people who first experienced the pain themselves.
If you enjoy building products, health tech startups or medical tooling could be a very natural path.