Part 2

Technology highlights from 2016: What was the biggest disappointment?

JAX Editorial Team
technology trends
Nostalgia Past image via Shutterstock

2017 is just around a corner, so it’s time to look back at this year’s highlights and see which technology trends might become important next year. We asked six people to share their biggest disappointments in the technology world in 2016.

Some say 2016 was a good year for technology, some cannot wait to welcome 2017. But no matter how this year was for you, one thing matters: there were lessons learned and battle scars gained. Before we turn the page and welcome 2017 with open arms, let’s have a look at what went wrong this year.

We asked six people to share their biggest disappointments in the technology world in 2016.

6 answers: In your view, what was the biggest disappointment in the technology world in 2016?

Lukas Eder: Java EE doesn’t fail to disappoint. I mean, how can we have an “enterprise version” of Java that still couldn’t really decide on a standard for JSON binding? By the time Java EE does have JSON binding, JSON will no longer be a thing, I suspect.

Not that I’m surprised, or personally disappointed. I prefer not to work on Java EE projects, which are usually quite overengineered.

Java EE doesn’t fail to disappoint

Steve Naidamast: As I have written in some of my previous articles, the biggest disappointment I have had with technology in recent years has been the growing erratic nature of the Microsoft development environments whereby anything and everything that is new appears to be taken up and provided in Visual Studio as additional techniques for development moving Microsoft away from its core development concepts.  Much of this has entailed the adoption of many JavaScript frameworks for web development, which has been encouraged by the continuing support for ASP.NET MVC.  

While the Java Community has worked with the MVC paradigm for many years as standard practice for its own web development, Microsoft had its paradigm in ASP.NET WebForms, which though not nearly as low-level as MVC has as its premise ease-of-use. WebForms has been refined into a very mature product and is still the most powerful way to develop database intensive web applications in reasonable time periods.  True, WebForms has its own set of issues but so does MVC.

Nicolai Parlog: For, like, the tenth year in a row — working conditions in the IT hardware industry (particularly in Asia) and required mining and resource processing (particularly in Africa).

A lot of engineering decisions are driven by hype.

Ivan Kusalic: Personally, I’m still disappointed that a lot of engineering decisions are driven by hype for certain technologies instead of understanding when they are applicable and what the benefits and downsides are. Basically, we as the industry are still trying to find the proverbial hammer to nail down all the problems. And while hammers are very usefully, sometimes you need a different tool as well.

Let me give you two examples:

1) A lot of people are still thinking in a very shallow way about microservices. It is not a silver bullet, but an architectural pattern that comes with pros and cons. What I find particularly interesting in this example is that, while being a reasonable final approach, they are often put into place way sooner than needed and unreasonable costs are paid along the way.

2) The Left-Pad Incident, I guess there isn’t much more that needs to be said here.

Jonas Helming: That would be either Project Jigsaw or Java Module System! Even though it isn’t possible anymore regarding the stage of development: I’d wish for Java 9 to implement some kind of “OSGi essential” – offering basic compatibility while dropping dynamics if needed. OSGi has been working for 15 years now; Jigsaw has been postponed again and again for five years.

Kai Spichale: MVC 1.0 has been deleted from the Roadmap of Java EE 8. The action based MVC framework would have been a complementary feature to JSF.

Have you taken our DevOps survey yet? Help us identify the latest trends in modern DevOps

Comments
comments powered by Disqus