![]() ![]() That is, more of then than not, not the case. to rewrite the whole thing based on solid, powerful technology and tools. The whole "prototype" idea assumes once you grow out of the "prototype" phase you have the time, money, manpower, etc. Maybe something like reassigning the IP to a trust, with the trust having an obligation to sue anyone and everyone who tries to create derivative works of the code they've been handed?) (Going further, it'd be interesting to create some sort of quagmire of a software license, specifically for prototypeware, such that you'd be forced to rewrite all the prototype code instead of reusing even a hair of it in production. Stick SQLite in for the database, munge HTML and Javascript together, whatever-it's literally going to slap away the hand of anyone who tries to use it on a production workload, so why not? If an enforceable mechanism like that existed, I'd be a lot more confident in mocking things up. It'd force the migration to something better just as if it were a Big Customer with Enterprise Compliance Demands. But there'd be no way to just slide the limit upward or otherwise tarry. It would warn anyone monitoring it well in advance of hitting such a limit, of course. ![]() I've often dreamed of a specific type of software built and released as "prototypeware", where any app created using it will have certain built-in scaling limits-and going past them will irrevocably force the app into a read-only mode. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |