I have acutally kicked this idea around 4 or 5 years ago of A "WSW" but more so in a sense that modularity would have been the groundworks for such a revolution.
Modularity. Modules, taking the scale of what cpus on the phones have to what the cpus in the late 90's till now had... interoperability... it is just not there yet. Infact it stagnated.
a lot has changed in the last months alone. there are several standards ready for IoT (ETSI M2M) [0], some are still being drafted (W3C Web of Things "WoT")[1].
Where I still see lot of room for improvement in standards is for totally radically new use-cases. Standardization guys are usually industry representatives from bigger companies who think about inter-op (and to a lesser extent use-cases). But many use-cases in IoT transcend or even threaten the business models of what the bigger players have built their power/dominance on (they prefer sustainability over disruption -- god I hate those buzzwords).
Therefore smaller innovators (individuals or garage start-ups) who have radical ideas such as building a decentralized business model (maybe using cryptocurrencies or blockchaining and not driven by harvesting user-data or advocate strong privacy) usually don't have the resources or time to put one of their staff into the slow-moving standardization bodies to make/defend their case.
Though the W3 is extremely open compared to others and even there are official members who vote behind closed doors, ... if enough contributors bring ideas in the open discussion groups, then these points too might get standardized.
The biggest problem though is standardizing security.
It is no coincidence that most IETF drafts especially older ones and official RFC's have under "Security" a note that says "to be done". Thinking ahead what might become a design problem later is hard and depends on how the standard later gets understood by the industry. But more important there aren't enough people who understand security in standards groups. That is not just a standards problem though and more of a disease of our industry. Just look at most web developers and have them explain how XSS/SQL-injection works ... or ask an Embedded engineer who is used to building non-connected appliances to think about remote exploitable buffer overflows after they connects the thing via a CoAP proxy to the WWW ... Yes you'd assume they know that in detail but reality is usually most have no idea - not because it's hard but because we are not incentivized by making it extra secure (security often is a useless feature unfortunately only indirectly affecting your financial bottom line (when sh1t hits the proverbial fan)).
Reminds me a job I had early on in life working under several intelligent people but unknowningly replacing 3.
Out of the 3 the 1st pushed me and encouraged me to move on when we debated who should stay, the 2nd was a surprise because I asked her why she was training me but sadly it was then I learned of her animosity toward me and her 30 years on payroll.
Which brings me to the last person I was replacing - the data scientist, the man that verfied my numbers and surely was verifying a lot of other things.
so having the guilt of the first two I happened to have a situation outside of my control land in my lap, I left the company immediately, positive they kept him onboard for atleast another 6 months to a year.
great experience nonetheless.
tldr: cost reduction hire, had to be vetted 1st - split before my conscience weighed too heavy.
Once upon a time writers actually took the time to investigate their "tools", like flying to Hawaii and sitting down with a psychologist in a small cafe and going over the numbers if you must.
Not everyone is in a New York state of mind. Once you Once Upon a time it speaks to narrowness.
1: email is hosted offsite, yet reliant on Google/Gmail to do in house work/intermail.
2: when you are reliant on an external source to solve a problem within your own house you are not prepared.
3: solution: reduce reliance or point of failure by either bringing it all in house and forwarding the remains or bring root to the source and source from root and use mask and forwarding.
I'm confused -- are you saying doing your own email hosting is the way to avoid getting stung by Gmail spam filters? Seems like an "out of the pot and into the fire" kind of situation.
confusion is the root of the problem, either remove the offending host and do it all in house or move yourself within the root of the problem and continue conducting business.
he could bounce off another provider/server so he can still maintain what he is doing now - he just has not explored any other solution except blaming. the arguement "it should just work" is not vaild if you are reliant on another service.
It's a great recruiting tool. Plus the possibilities of how it will scale for projects like robotics/fiber/wifi etc... who wouldnt want an inside track like that?
Modularity. Modules, taking the scale of what cpus on the phones have to what the cpus in the late 90's till now had... interoperability... it is just not there yet. Infact it stagnated.