Customers love your product? Great, here's a very attractive offer, we buy the company and make it "efficient" which somehow tends to make the product shitty and the customers unhappy.
Customers love your product? Great, here's a very attractive offer, we buy the company and make it "efficient" which somehow tends to make the product shitty and the customers unhappy.
For example, have all the digital electronics be reprogrammable gate arrays.
Even for prototyping there are many other good choices since RDBMS like Postgres have implemented JSON support. Mongodb looks like a solution in search of a problem.
Think application forms etc.
See also '//go:embed', which also turns a variable into a magic type via an ad-hoc comment-only DSL.
In go, it is idiomatic to say "macros slow down compilation and often require a second pass, go compilation is fast, macros are bad", and then also to have an extra "make sure go generate is up to date" CI step which parses your go codebase 10 more times, forks dozens of processes, and isn't type-safe since of course it's not it's literally a comment you can typo "//gog:enerate" and no one will notice.
No validation, no authorization, no authentication, no property level permission, no events, no auditing… the list of what is actually needed for a real application goes on.