SilentEditor

Thanks for the in depth reply. This did clear a few things I guess I overlooked the first time. Great work!

Okay I will check them out! Thank you for the reply

This is a clever way to make a dry, high-stakes topic actually approachable, and the game framing makes equity tradeoffs much easier to internalize.

How did you decide where to simplify versus stay financially accurate, and were there any startup-equity edge cases you intentionally left out because they made the game less intuitive? :)

Cool project!

The Vim modal model feels almsot native for spreadsheets, and splitting the formula engine into a TUI-free core was prolly a great architectural choice.

How are you thinking about recalculation, dependency tracking, and undo/redo as the sheet grows, especially once multi-cell edits and larger CSVs start stressing the core?

This could be very useful, I cant seem to find any documentation though, am I just blind? :P

Damn this is some legit information. I've looked around for some more recent information regarding modding and shelling, any tips other than the ones listed below?

Thx

This is a really good framing honestly. Spec-first tools are useful, but milestone-first feels way better for actually learning and not getting lost after step 2.

I like that you keep things verifiable at each step too, thats the part most AI coding tools skip and then people think theyre progressing when theyre just generating code.

how do you decide milestone size so its not too tiny but also not overwhelming? do you track failed attempts/retries as part of progress, or only completed milestones? Also are you planning a mode where users can switch between learning path and spec mode in the same project? I think that could be very strong.

Thats super helpful, thanks for the details. Makes sense now that PSNT is more of a transport/runtime format for the PS2 constraints than a quality hack.

Very cool that it supports bitnet too even if results are rough right now, feels like theres a lot of room to tune there over time. when you do fix tok/sec, are you planning to post per-stage timings too (tokenizer, weight stream, matmul, samppling)? would be awesome to see where the biggest bottleneck is on real hw

Love this project. The CD streaming trick is such a smart constraint hack, and honestly the best part is you trained the model for the hardware instead of forcing a desktop recipe onto PS2.

Curious about 2 things if you can share:

whats your per-token latency on real hardware how much quality loss came from PSNT quantization vs fp16 baseline Either way this is peak hacker energy, shipping on actual hardware makes it 10x cooler.

This is incredibly interesting, will follow.

Cool tool and great idea. However I find a few UX bugs initially as I'm browsing around.

- The document, when loaded, is not centered in the screen, a little bit annoying. - The landing page is not SUPER intuitive, I don't really know what to do or how to start doing anything, maybe a SMALL tutorial? - When I land on the page I get presented with dark mode, as soon as I select a tool and get redirected the theme changes to light mode.

Great tool and most of them work good too!

I will browse a bit more and let you know what I find :)

Wow nice tool! Unfortunately I'm not able to contribute for any of the listed supports. Good luck with finding supporters though, looking forward to follow this.

I built Silent Editor to see if a fully browser-side stack could handle the PDF editing workflow that people currently do by uploading files to cloud services or paying for Adobe. Loading a PDF, editing text in place, adding signatures, merging pages, exporting a clean result. All without the document ever leaving your machine.

All the technology already exists: PDF.js for parsing and rendering (same engine Firefox uses), pdf-lib for assembling output files, Canvas API for pixel-level work, Tesseract.js compiled to WebAssembly for OCR. The problem is making these pieces work together smoothly enough that it actually feels like a real editor and not a hack.

Most of the system is deterministic plumbing. Rendering pages to canvas, extracting text span coordinates, managing overlay state for highlights and signatures, remapping annotations when pages get reordered or deleted. The part where things get tricky is everything visual: matching the original font when you replace text, sampling the actual ink color from rendered pixels so your edits don't look obviously different, and producing an export that's either compact with selectable text (Vector mode) or pixel-perfect faithful to what you see on screen (Visual Perfect mode).

The privacy model is enforced architecturally, not by policy. Production builds ship with a Content Security Policy and a runtime network guard that block outbound requests carrying document data. The only things that touch the network are billing metadata through Stripe and page analytics through Cloudflare. Neither carries any document content. There's a CI suite that fails the build if any of this regresses.

It's already handling real editing workflows: text replacement with font trait detection, electronic signatures with date stamps, page insert/delete/duplicate/reorder/merge, shape annotations, OCR for scanned documents, and both export paths. But font matching is still imperfect for uncommon typefaces, color sampling from the canvas can miss on edge cases, and Visual Perfect export produces larger files than I'd like.

I'd especially welcome criticism on: is the free tier boundary (daily export cap, Visual Perfect gated to premium) reasonable, or does it feel like it cripples the product? And for people who actually handle sensitive documents regularly, does "runs in your browser, no upload" actually change your behavior, or do you just not think about it?

This is a really cool idea. Might be too technically advanced for me to comment on but I really like this, really cool simulation tool. Good job!

Big fan of the concept. Just need to distribute it well enough for it to start working by itself! Great design too, cosy UX vibes! :) Good luck

This is really interesting to follow. Good luck with this, great idea!

This is a really good idea. Image all the game devs that hate writing actual code but sits on some seriously good ideas. This will help so many to get the initial MVP thats needed to see if a game idea is viable.

Good work! Interesting to follow.

I'm not really well read in the topic but the tool seems like it could solve a lot of unecessary struggle that usually comes when setting up several different tools to integrate in the same environment. However I really enjoy the site and the UX work. Beautiful!

Oh yeah! I was also really confused at first haha.

Interesting to follow this. Strong implementation and the presenatation is just beautiful! Good job.