quick-lint-js VS MilkyTracker

You were write. Fucking sleeper shill https://github.com/quick-lint/quick-lint-js/blob/master/tools/ci-analytics/github_api.go

pretty insane this issue queue...not that most open source is lucrative but putting low ball price tags on it like this is...not my style let's just say https://github.com/quick-lint/quick-lint-js/issues

My allocator is 258 SLOC.

quick-lint-js (my project) is written in C++. It:

generator: https://github.com/quick-lint/quick-lint-js/blob/7dacde3aacc95110b1ed3a56d8e6fa812aa624c0/tools/generate-lex-unicode/index.js table: https://github.com/quick-lint/quick-lint-js/blob/7dacde3aacc95110b1ed3a56d8e6fa812aa624c0/src/lex-unicode.cpp lookup: https://github.com/quick-lint/quick-lint-js/blob/7dacde3aacc95110b1ed3a56d8e6fa812aa624c0/src/lex.cpp#L89-L109

use /u/strager's quick-lint, its better.

There are a couple of trackers available for linux, Milky is even open source https://github.com/milkytracker/MilkyTracker

I agree that you could reduce the lines of code by modernizing, and get more reliable code (the current codebase has cases of UB that they neglected pull requests to fix for a year and counting, see https://github.com/milkytracker/MilkyTracker/pull/255 and https://github.com/milkytracker/MilkyTracker/pull/256). But MilkyTracker is uniquely fast in compiling, I think because of avoiding STL and heavyweight headers. My hope is that in the future we can have container niceties and lightning-fast compilation (perhaps modules over headers, concepts over SFINAE, or using STL alternative containers designed to be lightweight like EASTL or Corrade, or jumping ship from C++ entirely to Zig or Nim or so).

Take a look at https://github.com/milkytracker/MilkyTracker. It's C with classes, has lots of UB, but sadly they didn't care about me trying to fix it.

Assuming you have Windows, try this one, it has a simple executable inside that allows you to run it.