It really all depends on the particulars of the application, but in many cases they are totally correct that putting the logic in the application can be much more scalable. Often these are not all or nothing type arguments. It may be that you need a mix of traditional SQL for some stuff with business rules and all that jazz, another SQL setup for hosting certain types of dynamic data and then a NoSQL setup for the unstructured data. There is no one solution for all troubles, that's just the way it is.

AC is 100% correct provided we're dealing with a local Access database and not Access fronting a SQL Server - in the latter case, all of the queries and what not take place on the SQL Server and not on the client. The latter case is not uncommon with Internal Applications that started off as an Access application and were later converted to run on SQL Server.

Actually a number of the older embedded platforms I've programmed for DID in fact use gcc+patches, usually with proprietary stuff added all around. I believe for most of the microcontrollers supported by Keil, the compiler is based on GCC (often the older 2.x series.)

While the GPLv3 was the reason Apple suddenly invested in clang (which just happens to ride on llvm), it has little effect on any companies that do what they should do.

The US - still the best place to live and the whole "debt" issue is really not a huge deal.

It has been my experience that they don't believe that people have real names like Hunter, Yearly, color name, Happy, and lots of other common English words. - if there's a question, they should ask for proof and give you x amount of time before they just disable the account.

Are thinking of Matthew Boulton or perhaps misspelling Michael Bolton?