On Sat, Feb 2, 2013 at 2:09 PM, Paul Glavich <subscripti...@theglavs.com>wrote:
> At the risk of being argumentative, we asked for this. Maybe not you or me > specifically, but the community at large has. I agree the number of > technologies at play, particularly in this space is large but it makes it > all the more **interesting** to make those architectural choices. In some > ways, less choice is better as the number of possibilities and combinations > are less, thus decisions are more constrained and easier to get to.**** > > ** ** > > However, the flexibility afforded to us now is great. The better > technologies will rise, the lesser ones either improved, integrated or > discarded and this is our task. In a properly architected system, the risk > of choice of a communications technology can be mitigated. However, we are > also human and can introduce dependencies where in hindsight, this was a > bad thing. We live and learn. It goes back to the “circle of dev life” > previously mentioned. Never believe the hype. Accept it for what it is, > experience it, come to an informed decision based on that, and your > educated judgement. Remember, .Net remoting is still there J**** > > ** > By that token, so is DCOM. (bitter laughter) -- Meski http://courteous.ly/aAOZcv "Going to Starbucks for coffee is like going to prison for sex. Sure, you'll get it, but it's going to be rough" - Adam Hills
