Thank you for this, kevin42. So many great games around the 2000s. If Tim Sweeney could open UE1, a lot of games could benefit from it like Quake being open sourced did.
> consider the cost of maintaining an OSS ClickHouse cluster
I mean... it is pretty straightforward. 40~60 line Terraform, Ansible with templates for the proper configs that get exported from Terraform so you can write the IPs so they can see each other, and you are done.
Would you prefer for it to be dictated by the power-hungry suits running companies and giving themselves multi-million dollar bonuses after mass layoffs?
I'm not sure why you think those are mutually exclusive. If anything, I think pulling out the middlemen—the actual interviewers—gives upper management more direct influence on hiring (assuming the models are tuned at their direction).
This is sort of a category error... re2c is a lexer generator, and YAML and Python are recursive/nested formats.
You can definitely use re2c to lex them, including indentation, but it's not the whole solution. You need a parser too.
I use it for everything possible in https://www.oilshell.org, and it's amazing. It really reduces the amount of fiddly C code you need to parse languages, and it drops in anywhere.
Parser generators usually have some downside, but there's not much downside to the lexer generators IMO. It just saves you work. And the regex syntax is better than Perl/Python because literals are consistently quoted.
Re2c only performs the tokenizing part, not the parsing part. Re2c should be able to run a regex to recognize N spaces and produces a n-space token. It will be up to the parser to use that to get the indentation of a statement.
Because std::string is pretty much the worst way how one would implement a string type. Sometimes it's better to not have a feature than to have a broken feature.
Thank you for this, kevin42. So many great games around the 2000s. If Tim Sweeney could open UE1, a lot of games could benefit from it like Quake being open sourced did.