People need both. REST works well for CRUD operations that don't have complex side effects or constraints. What's often missing in this is intent. I just want to do "the thing" to this particular account or whatever.
Personally I like to very selectively add RPC actions on top of the base resource. Tacking an RPC action onto the resource URI allows you to encapsulate the intent of the user's action, handle all the updates required server side, and then return the updated representation.
> HiringSolved, a technology company that leverages artificial intelligence and machine learning to solve problems for talent acquisition practitioners...
I almost stopped reading at this opening sentence. We've got "leverage", the double base covering with "artificial intelligence and machines learning", and the coup de grâce, "talent aquisition practitioners."
I had the impression that it was a probing thing. Trying to figure out who in my friend list I'm interested in keeping up with. Annoying enough that I decided to uninstall the app.
This is such an important point. I'm living with a generic "group" feature in a SaaS app and it's a nightmare. It's been used by numerous clients for totally different things. These are the weeds that will choke your garden.
Perhaps a larger animal. Detachable coupling of course and some sort of programmatic control of the beast. The coupling would include devices which would increase the concentration of life giving material and turn back less desirable properties of the blood.
I would ride upon a great blood engorged elephant and take pity upon all the unwashed goat tethered masses.
I wish I could upvote this (and your other comments) 100 times. Amazing high quality machines will keep the design and dev community on Mac for years to come, churning out the apps that help to make the iPhone ecosystem work.
Bleeding power users to alternative systems creates vulnerability.
These arguments would be the same for Microsoft circa 2007. Why should Microsoft care if the designers, developers, and tastemakers hate their products? They've got so much lock-in that people will be forced to use their stuff forever. Wheee, we're invincible. We all know how this turned out.
I'm running up against low memory issues on my 16gb MBP lately. I absolutely cannot responsibly update my Apple product right now because of the 16gb limitation on the MBP. It does matter!
I'm getting ready to bite the bullet and go back to Linux desktop.
The only alternative that makes sense to me is to follow Peter Lynch's advice and buy what you know. Do this with money you can afford to lose.
When Apple released the original iPod I begged my Dad to buy me one and raved about it. Based on my excitement, he bought several thousand shares of aapl and still holds them. The gain on that single investment is greater than all the income he earned in his lifetime. You cannot expect to make these kinds of investments. Take a sliver of what you have and put it behind something you believe in. Put the rest in index funds.
Edit: I meant to tie this comment back to the original title about wealth disparity. Point being, my Dad has created generational wealth from a single lucky investment. It's just luck and a system that let's you keep your winnings.
Personally I like to very selectively add RPC actions on top of the base resource. Tacking an RPC action onto the resource URI allows you to encapsulate the intent of the user's action, handle all the updates required server side, and then return the updated representation.