Then maybe the app should work as follows:
When "seller" is almost ready to leave, they announce (via the app) that they will 1) be vacating the spot in X minutes, and 2) disclose the precise location of the spot for $Y. In X minutes, if they have not vacated, they pay a fine for loitering (managed by the app).
The problem with choosing the best database (or technology in general) for each corner of each application is that before long you've got yourself a maintenance/support nightmare.
Better to stick with what you know, provided it's sufficient for the job at hand. Only when there's a compelling reason should you bring in something new.
For example, there aren't many use cases for which PostgreSQL isn't sufficient...
Great, so the one night a year that my wife and I actually get to go out, we can't go to a movie or a nice restaurant because our babysitter won't be able to contact us if there's a problem?
If you are a licensed Oracle site you have support 24/7/365...
Wrong. An Oracle license gets you squat. If you want support, you'll have to pay a yearly fee that's roughly one fourth of the astronomically high one time license fee.
I'm surprised that you're shocked that there might be people who find this surprising. People are often surprised by things which, if they just stood back and looked at the bigger picture, shouldn't be surprising at all.
But if anyone's shocked that I'm surprised, I wouldn't find that surprising --- I'd be astonished!
Slashdot Mirror
May of 2014, actually (the blog entry you linked to is dated May 6, 2014)
Then maybe the app should work as follows: When "seller" is almost ready to leave, they announce (via the app) that they will 1) be vacating the spot in X minutes, and 2) disclose the precise location of the spot for $Y. In X minutes, if they have not vacated, they pay a fine for loitering (managed by the app).
The problem with choosing the best database (or technology in general) for each corner of each application is that before long you've got yourself a maintenance/support nightmare. Better to stick with what you know, provided it's sufficient for the job at hand. Only when there's a compelling reason should you bring in something new. For example, there aren't many use cases for which PostgreSQL isn't sufficient...
I hope they pause every few minutes to show funny commercials. A star studded halftime show would be awesome too...
Great, so the one night a year that my wife and I actually get to go out, we can't go to a movie or a nice restaurant because our babysitter won't be able to contact us if there's a problem?
I saw the man looking at the planet with a telescope.
If you are a licensed Oracle site you have support 24/7/365...
Wrong. An Oracle license gets you squat. If you want support, you'll have to pay a yearly fee that's roughly one fourth of the astronomically high one time license fee.
http://www.oracle.com/corporate/pricing/pricelists.html
I'm surprised that you're shocked that there might be people who find this surprising. People are often surprised by things which, if they just stood back and looked at the bigger picture, shouldn't be surprising at all.
But if anyone's shocked that I'm surprised, I wouldn't find that surprising --- I'd be astonished!
And Regions login page isn't secure. It posts to a secure page, but the page containing the login form is an http: url.