3 ms·
Written by a programmer who has a myopic view of how data is used. Data is not used by just one application in the real world over time; if your app that uses t
by bigtoga 18y ago
Written by a programmer who has a myopic view of how data is used. Data is not used by just one application in the real world over time; if your app that uses the stupid database becomes popular (or your startup becomes popular), you will now need many interfaces into that database - reporting, analysis, OLTP, maintenance. By putting it in a "persistence-aware programming environment" you're *&%$ing everyone else except you. Woohoo!
- Hexstream 18y agoWith a "persistence-aware programming environment" that uses a database as the backend, you have both. So I'm not sure if it's valid to argue PAPE VS DB...
- sah 18y agoThis problem applies to using any new or non-standard technology without abundant interfaces to a wide variety of tools. That's the downside. The advantage is that you get to use something better, and maybe it makes you more productive, and maybe it catches on and advances the state of the art. If everyone always used whatever interfaced best with the rest of the world, new technologies would be adopted much more slowly.
- yrashk 18y agoI was not arguing about "prohibiting" third-parties to connect to your database.