3 ms·
250k lines of code in one commit is reason enough to disregard the project entirely, IMO. Vibe code if one wants, but that is just madness...
by tfrancisl 3mo ago
250k lines of code in one commit is reason enough to disregard the project entirely, IMO. Vibe code if one wants, but that is just madness...
- ninininino 3mo agoIt's pretty obvious that the author didn't write a single commit during development, they just squashed their commits into a single commit at the end.
- tfrancisl 3mo agoWhether they did that or had an LLM one shot it, I dont really care. Commit history is pretty important if you ever want to try fixing bugs or improving features in the future.
- deleted 3mo ago[deleted]
- Uptrenda 3mo agoThis seems kind of like a laughable and shallow reason for you to disregard my entire project. >book too large >didn't read >0/10, heh Most of that code is from: (1) simulating all of asyncio (not a main feature) (2) monkey patching (not a main feature) (3) synthetic program suite (dynamically built sample projects) (4) entirety of the asyncio test suite in the test dir (5) and other tests The actual code surface for the run time is very small. The parent comment just ran a blind measure over the whole repo.