you're twisting my words, for cheap point scoring, but that's SP all over isn't it

I meant it's not much fun when you want to achieve something in an environment where you can't. You could easily hire a 3rd Gen programming language software engineer to use SP (if you can find one willing), but you wouldn't hire an SP clown to do a real man's job.
3rd Gen programming languages and 4th gen databases are all you need. for maximum flexibility. And they offer better tool support for software engineers long term. Software engineering is the development and
maintenance of software as an engineering process, it's not all about Rapid App Development, all RADs need taking further and refining for any real changing business, any business I've worked for would punch holes in a RAD in less than an hour, as an unconvincing façade "what happens if we want this, what happens if x,y,z happens?". When you get down into the devil of the detail and you get to an uh-oh moment when someone mentions a new requirement with far reaching impacts, i'd rather be in control of a 3rd Gen programming language than SP, because I know it can be sorted out.
and office365 is a load of rubbish in most situations, playing on buzz words like cloud infrastructure, selling the dream. In a simple one requirement business, on a budget based over a year it's cheaper than on-premises infrastructure, of course, if you just want cheaper and not bothered about backups, and someday transferring to on-premises infrastructure like most do. But businesses often need their own infrastructure in addition to cloud services if they have numerous systems and requirements, so just house it all on-premises from the start! It's more flexible and just as reliable, cloud does go wrong too. and in the real world when you get into some of the intricate requirements, and backup procedures, I've solved them every time with on-site infrastructure. too many restrictions in the 'cloud'. Backups; I'd rather have a backup here on-site that I can see, touch and test, than an exciting empty promise of a working backup out there in the 'cloud' behind some frontline technician, who when it all goes belly up, will just shrug his shoulders on the other end of a chat window and speel off "i'm really sorry about that, is there anything else I can help you with today my jolly good man? do you want fries with that?".
this
is the best advice for anyone reading not wanting a headache, and wanting a useful and long lasting business database, with any real requirements. It's about doing things properly. Buy cheap, buy twice.