Can the index size exceed the RAM size (e.g., via memory mapping), or are index size and document number limited by RAM size?
It would be good to mention those limitations in the README.
Show HN: I wrote a full text search engine in Go
51–56 of 56 posts
Re: Show HN: I wrote a full text search engine in Go
#52AI slop.
Re: Show HN: I wrote a full text search engine in Go
#53You are avoiding the questions whether this was vibe coded or not. I see that almost every single project of yours was vibe coded down to the readmes. Why hide this?
Re: Show HN: I wrote a full text search engine in Go
#54This is good for someone playing around with Go and data structures with vibe coding, but I just hope HN doesn't get flooded with vibe coded toy projects.
Re: Show HN: I wrote a full text search engine in Go
#55Earlier quoted context omitted.
I like it, I comment exactly like you do. Comments are free, storage is plentiful, why not add comments everywhere?!
Time and risk of comments/docs becoming outdated and doing more harm than good. I'm impartial in this discussion but that's usually how the counter argument goes.
The counter argument is bunk, you change the comments when you change the code. It’s not hard. If you forget, them a reviewer will notice. If not, then you aren’t focusing enough attention on the finer details of a project, to your detriment.
Personally, I find that a lot of good, accurate comments and documentation helps me to trust a code base more because I can see that the devs cared and focused on the finer details rather than just tossing code over a fence at me.
Re: Show HN: I wrote a full text search engine in Go
#56Yep, coding is dead now everything is pure ai slop