Totally fair! I know semicolons aren’t for everyone — W++ leans into a mix of familiar C-style syntax with some Python-style simplicity, but it’s definitely not a perfect fit for all tastes.
Appreciate the kind words regardless — and who knows, maybe I’ll experiment with optional semicolons in a future version.
For me, having semi colon be a non-configurable default is a non starter. Languages like Go or C take it too far. I prefer a typescript like language where semi colons are configurable through a config file or tool.
Typescript itself is a non starter because of non-configurable "brackets around if conditions" behavior. I pretty much write any language I wanna use these days depending on the task. Use the right tool for the right job. I do generally target perl 5.8 as a backend though. Seemed simpler and most widely supported backend across all systems I came across. Has been super stable since '02.
Use legaleese to fight legaleese, just write in the ToS itself only the blockchain version is applicable. If they want to move off they at least have to update the blockchain version to remove the blockchain requirement for applicability.
They could of course just do that, so there is no benefit from it being in block chain compared with anywhere else.
The only advantage block chain provides is you don't have to trust anyone.
Eg you don't have to trust GitHub to not delete or modify the repo themselves, but they weren't any part of the problem here.
Blockchain history cannot be manipulated unlike in git. This was meant as a joke though. There’s other ways to achieve this besides blockchain. the internet archive way back machine can pull up the TOS on a certain date.
