From the JSF 2.3 release to the Amazon AWS outage, we're taking shots at easy targets
Watching both the tech industry as well as mainstream media oversimplify the February 2017 Amazon S3 outage story annoyed me greatly. The annoyance transitioned into keystrokes, producing two opinion pieces on the topic, one of which evaluated the impact the outage would have on the faith users put into their service providers, while the second tried to filter out the Amazon noise and move past the manner in which the media greatly oversimplified the problem. Both articles garnered some interesting feedback on TSS, social media, and the TechTarget’s family of Search sites which aggressively tweeted the stories:
Was the Amazon S3 outage a Chernobyl even for AWS?
Stop repeating this fake news story: An input error did not cause the Amazon S3 outage
We’re not picking on Amazon
Some have asserted that I’ve been picking on Amazon. The fact is, a number of recently published features on TheServerSide have been picking on everyone, so it’s not like we’ve been singling them out.
Everyone loves picking on JSF. TheServerSide put up a feature article last week asserting that web UI frameworks should not be part of the Java EE specification. Some suggested that the article was just another pot shot at JSF, but it wasn’t. Taking JSF out of the Java EE spec would actually be good for JSF, and the article articulates why. At TheServerSide, we’re JSF advocates, and I’m excited about the future of JSF. Taking a look at what’s new in JSF 2.3 makes me believe that many of the little frustrations that aggravated developers have been addressed, and the future is bright for the Java based, web component framework.
We must remove web UI frameworks like JSR-371 and JSF from Java EE
What’s new in JSF 2.3? CDI alignment and integration with client-side technologies top the list
From deprecated Java methods to RESTful web development
Oracle’s inability to prune deprecated methods out of Java SE also came under fire, with a callback to an interview we did with Rod Johnson about a hundred years ago discussing how Spring makes method deprecation something developers should take seriously.
When will Oracle start purging Java deprecated methods from the spec?
The over-hyped DevOps trend also became a target, as did RESTful web development with XML and JSON. We even took a shot at every single development stack and framework that competes with Java EE, which is indeed a tall glass of water.
DevOps and Agile: Riding the magical unicorns of software development
My RESTful calls read JSON but write XML. Does that make me a bad person?
Forget software conglomerations. Java EE is best-of-breed enough.
So perhaps we did pick on Amazon a little but, they weren’t the only victim of our scrutiny. If anyone was to suggest that Amazon was the only target TheServerSide’s opinion pieces were targeting, they’d be way off the mark.
You can follow Cameron McKenzie on Twitter: @cameronmcnz