Hacker Newsnew | past | comments | ask | show | jobs | submit | xiaohanyu's commentslogin

One of the main reasons why books cannot update as software is because there is no GitHub or even Git thing for books crafting.


What is picgo?


I think github has some API for this right?

Does gitmore just call GitHub API or counts by commits manually?


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.


Maybe webp is a better target than png?


No, because their domain is png /s

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.


It's not. JPG, I could live with but please not webp.


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.


Because it's impossible to use in other tools. Only browsers get it. But I agree about lossy images for text.


Definitely should be WebP.


Interesting journey of vibe coding a non-trivial project.

Any more details about why this project is unmaintainable?


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.


I just watched a video https://www.youtube.com/watch?v=eIoohUmYpGI which I think summarize your points here, recommend it to you as well.


The best demo for music programming language demo I can found is: https://www.youtube.com/watch?v=yY1FSsUV-8c&t=374s, The concert programmer.


https://yamlresume.dev

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.

To release soon: HTML output.

Demo: https://asciinema.org/a/759578


One thing that LaTeX still win is CJK support, typst is still very young and lacks professional support for non-latin languages: https://blog.ppresume.com/posts/on-typesetting-engines#concl...

I admit that typst is quite promising and given enough time, its adoption will increase quite a lot.


Actually I am planning to integrate AI to generate this kind of YAML first and then convert it to PDF.

The idea:

1. apply strict schema validation to YAML so AI won't generate wrong/invalid data 2. write prompt to AI help people generate a sample YAMLResume 3. adopt AI to parse existing PDF or images and convert it to YAMLResume format


Well I'm just suggesting first because most people already have a resume and it will be tedious for them to convert it to yaml.


yep agree


Typst is a pretty good alternative to LaTeX and I agree all pros in your comment, with only one major deal breaker now: its CJK support is not mature enough and not producation-ready yet.

I wrote a post half year ago explained the details for my decision between LaTeX and Typst: https://blog.ppresume.com/posts/on-typesetting-engines#typst


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: