Comments by "Brent Jacobs" (@br3nto) on "Stop Using Rust Use C++ | Prime Reacts" video.

5:10 The problem with MVPs is that they very easily and quickly become the production code. Once you get an MVP out, so do the requests for changes and improvements and additions. Before you know it, you have a full blown core system written in a scripting language. So do you choose what’s easiest or should you pick what you want to end up using?
116
@ what the difference between an MVP really? A prototype proves the concept… so in theory it is the minimum viable product. Usually though… there is an exisiting system in which the prototype must be delivered through and integrated with… so why bother proving the concept in anything but the actual system that will deliver the product… in which case the prototype is pretty much the MVP.
1
@ as an example… my team just spent the last 6 months rebuilding something that was prototyped 6 months earlier… but we couldn’t use anything from that prototype because it didn’t use real data, it didn’t use our system, it didn’t use the front end libraries we were using, sure it prototyped the product and looked cool… but it was a worthless prototype… it was just a gimmick
1