Thanks! The project started because I needed to replace Xinha (https://xinha.webfactional.com/) in the admin panel of a gaming news site I've been running since the early 2000s. Xinha served me well for years, but it was no longer actively maintained and had accumulated a lot of legacy baggage. I wanted something lightweight that just worked without pulling in a framework or a tree of dependencies.
Development time: the core editor took a few weeks of focused work, but I've been iterating on features for a couple of months now (slash commands, markdown mode, table editing, etc.).
Regarding Tiptap: it's a great project and I have a lot of respect for it. They're solving a different problem though. Tiptap is built on top of ProseMirror, which gives you a proper document model, collaborative editing, and a very composable extension architecture. If you're building something like Notion or a collaborative SaaS editor, that's absolutely the right choice.
The trade-off is complexity and size. Tiptap pulls in ProseMirror and its own packages, easily 200KB+ of dependencies before you even add extensions. You need a bundler, a build step, and you install features one by one as separate packages.
Zero WYSIWYG comes from the opposite direction. It's a single JS file and a single CSS file, about 120KB total, zero dependencies. You drop a `<script>` tag in your page, call `init()`, and you immediately get it working.
It's really aimed at a different use case: traditional server-rendered sites (PHP, Django, Rails...) where you just need a reliable textarea replacement in your admin panel without introducing a build pipeline or a framework dependency. That's the world I come from, and that's the itch it scratches.
"If you are looking for that one trick that lets you get ahead and jumpstart your career, my advice to you is: Don’t choose the path of least resistance. When training a muscle, you only get stronger with resistance. The same is true for learning any new skill. It is when you struggle with a specific problem or concept that you tend to remember."
As with anything, there's also too much of a good thing though.
In my own career I switched role to get more time on a area where I felt I needed more growth an practice. Turns out I never got really very good at it, and basically was just in a role I wasn't great at for 6 years. It was miserable. My lesson is "if you know you are bad at something, don't make it load-bearer in your life or career".
There's a reason that one of the big corporate skills books is Strength Finder - because fundamentally playing to your weaknesses isn't a good play, its that you need to consistently challenge yourself to keep building whatever muscle you choose to do. You don't want to build strength by lifting 10,000 pounds all at once, but by increasing your load every day.
In most professions barely anyone is doing the continual education or paying attention to the "scene" for that profession, if you do that alone you're probably already in the top 10%.
Gitmore uses github api and AI generates insights/ custom newsletters for users.
You can also connect Gitmore's AI into slack and ask it questions directly from your workspace.
I thought webp would be better for this and checked again just to be sure, and yes, it would be better for this. WebP is quite well supported, albeit not as well supported as png, and it can have significantly smaller file sizes for the same lossless image as png.
Why? I assume the intention is to show these images on a webpage somewhere. WebP is well-supported by browsers and can store lossless images at better compression ratios than PNG, so why not use it? I don't think using a lossy format like JPEG makes much sense. JPEG is a fine format for photos, but for HTML content rendered as an image I assume most people would want a lossless format so you don't get artifacts.
I'm sure everyone has their own tolerance for what is and isn't maintainable :). For me, not knowing what code exists, where it is, how it fits together, and stuffing it all in one main file feels like a recipe for trouble down the road. Sure, I could probably tell the LLM to split the main file into modules and ask it to refactor code etc.
However, from personal experience I'm a lot more efficient when I use LLMs to help with tedious, boilerplate-like code writing but I remain in control over structuring the project so it's maintainable by more than machines only.
I use LLMs every day to write tests for example, it's a massive time saving and I wouldn't want to write tests manually ever again.
A open source Node.js lib that allows people to create and version control resumes using YAML.
Support LaTeX/PDF/Markdown outputs in one shot with professional typesetting.
Support English/Chinese/Norwegian/French languages out of the box.
With clang style, real time error reporting.
For no reason facebook blocked my account long time ago.
Can't figure out how to recover at all.
No response and no way to appeal.