Live data from Hacker News

Negotiations Failed: How Oracle Killed Java EE

headcrashing.wordpress.com

511–520 of 526 posts

Re: Negotiations Failed: How Oracle Killed Java EE

#511

Earlier quoted context omitted.

Windows based EC2 instances represent maybe 10 % of all EC2 instances.

https://aws.amazon.com/windows/ We run nearly 2x more Windows Server instances than the next largest cloud provider, according to an IDC report.

Interesting point of reference, but doesn't prove or disprove the parent comment

Re: Negotiations Failed: How Oracle Killed Java EE

#512
post #509

Earlier quoted context omitted.

javascript is named javascript for marketing purposes. your example is an almost stereotypical misunderstanding by people unfamiliar with java.

Those marketing purposes are exactly what dtech is referring to.

marketing purposes being a non-technical thing, which isn't a very meaningful support to saying something like js/webassembly are replacing the jvm.

Re: Negotiations Failed: How Oracle Killed Java EE

#513
post #499

Earlier quoted context omitted.

Just because I responded to all posts doesn't mean I am able to remember everything. It is also foolish to have senior devs focus on selling themselves as Language X dev, without any other skill to offer. I would rather have a VB 6 guy on the team that can do proper software architecture design, speaks fluently two European languages across our customer sites and is able weight what really matters across the delivery…

So what are the chances that someone who is doing VB6 in 2019 and is talking about he has been maintaining a legacy combination VB6 app that interfaces with C++/ATL DCOM objects is keeping up with the latest advances in architecture, development practices, etc. compared to someone who does a show a history of transistioning as technology changes?

In the world of enterprise consulting, a great one.

Because again, that person has more than one hat to wear, instead of being stuck in coding silo.

Re: Negotiations Failed: How Oracle Killed Java EE

#514
post #500

Earlier quoted context omitted.

Might be, but some customers do pay to keep it alive.

That’s fine. But from an employees standpoint who should always be focused on what’s in their own best interest from a career standpoint, there is no way that it could be argued that it is best to stick with those technologies long term. The chances are that either (the hypothetical) you would either want to leave the company that is still focused on those technologies or the company would leave you long before your…

From employees stand point they should learn to diversify their skills beyond programming languages, enterprises that just want typing coders outsource their projects.

The only ones onsite have more to offer than programming language knowlege, like domain business, architecture design, foreign languages.

Employees that want to stay employable should focus on being T-shaped ones.

Re: Negotiations Failed: How Oracle Killed Java EE

#515
post #502

Earlier quoted context omitted.

Developers that focus in only being good in tech, without any additional skill won't go far. The days of pure coding jobs are over.

Even with being a reformed former team lead, Devops and plenty of AWS infrastructure and development experience and looking for a change to add on Docker and k8s, It still crazy not to have the table stakes of knowing the latest tech.

Plenty of customers still run stuff on premises without any desire to put their precious data on someone's else computer.

Docker and k8s are the NoSQL of 2019.

Re: Negotiations Failed: How Oracle Killed Java EE

#516
post #513

Earlier quoted context omitted.

So what are the chances that someone who is doing VB6 in 2019 and is talking about he has been maintaining a legacy combination VB6 app that interfaces with C++/ATL DCOM objects is keeping up with the latest advances in architecture, development practices, etc. compared to someone who does a show a history of transistioning as technology changes?

In the world of enterprise consulting, a great one. Because again, that person has more than one hat to wear, instead of being stuck in coding silo.

As I said, having experience with modern technology is just “table stakes” to get your foot in the door if you want to stay at least partially hands on.

With the few unsolicited offers I’ve gotten to work for consulting companies just through my network - the travel requirements just won’t work for me right now - I kinda of know the requirements that most consulting companies are looking for.

Few of them are looking to do desktop Windows applications. Yeah some are looking for ways to run legacy Windows applications “in the cloud”, but most are looking for a way to convert them to the web and I haven’t come across any that actually want to start new greenfield desktop applications or for that matter .Net framework applications. Sadly, most aren’t even looking at .Net Core. Hopefully that will change.

Don’t get me wrong, until I chopped everything off of my resume I did before 2008, I did get a few recruiters who were looking for those older technologies, but why would I waste my time gaining experience in older technogies when there is a ridiculous amount of money to be made as a “digital transformation consultant” or by knowing cloud infrastructure and how to architect on top of it (pretty good at it), and the entire Docker ecosystem (learning it)

Re: Negotiations Failed: How Oracle Killed Java EE

#517
post #476

Earlier quoted context omitted.

This may be true but conventional wisdom against using anything GC'ed for real-time applications (like HFT or aerospace stuff) is going to mean even if go's gc is good enough, using any gc'ed language for these apps is going to be extremely rare for years if not decades. Seems far more likely that rust will chisel away at that market than golang or any other gc'ed language.

Many HFT firms have used Java for ages. If you know what you’re doing you can avoid GC. Also, not everything needs to be realtime.

For arbitrage that must happen really fast, FPGAs is the way to go, and for complex code that needs to be rewritten often and quickly, Java is probably a better fit than C++.

Re: Negotiations Failed: How Oracle Killed Java EE

#518

Earlier quoted context omitted.

> webassembly [is] eating JVM's cake It's hard for me to take all the "Java is dying" threads seriously when they don't even seem to understand where Java plays. Webassembly ? Really? That's a client-side tech, and 99.999% of Java devs ceded the browser battleground pre-9/11. Java's bread and butter is EAI, ETL, and server-side business application development. Particularly with pieces requiring heavily distributed d…

You're right that Java is entrenched in a lot of the enterprise space, but I think you're being quick to dismiss entrants that have gained steam in the last few years. For example, Go is becoming the default in Kubernetes applications. It's eating tech companies that became large in the last few years like Lyft and Uber. It'll spread to other large tech companies like Amazon or IBM with ease. It will possibly get pic…

Go is a good language for developing middleware and automation tools, but it's not, at any rate, a replacement for Object-Oriented languages. Java, C#, Python, Ruby etc are much more suited to business-oriented apps, data science and so on.

There are many uggly things on Go language that can be considered nice features for system programming. Even though, if you go too much on the low-level (such as for operating system, drivers or embedded devices) it's still a issue to use go instead of a more hardcore systems language such as C++ or C. It is, at most, a niche language today. And probably will stay this way unless it goes into a major redesign.

Better to talk about Rust or Kotlin, which are languages that have much more potential and can be a real threat to the dominant languages/platforms today. But right now, they are too unknown to be taken in consideration just as many other good languages that never came to be.

Re: Negotiations Failed: How Oracle Killed Java EE

#519

Earlier quoted context omitted.

> Some of these people who compare Java to Cobol have no idea....at this point Java is so widely used in the enterprise that it’s foolhardy to think that Java will disappear anytime soon. Isn't that PART of the Java to Cobol comparison? Someone making that comparison wouldn't be saying that Java will disappear anytime soon.

COBOL is a valid comparison in terms of its space occupied and the verbosity the language is. The difference is cobol is really mainframe era and java is mini / unix era. Its client side except via phone is largely gone. But like cobol still in mainframe apps, so would be java. We do not see that gone as mini/unix not dying. The windows server running java is an area I am not sure and not much encountered. But window…

Client-side is gone on most languages. While there's still native mobile apps (and some rare desktop apps), the only language available on the client-side for the web is javascript or languages that can be transpiled to javascript. Flash, cold fusion and other stuff are gone. It's not a "Java is dead" thing.

Re: Negotiations Failed: How Oracle Killed Java EE

#520
post #398

Earlier quoted context omitted.

Yes. The Java ecosystem is far larger than Oracle. Java can absolutely thrive if Oracle were to cease to exist tomorrow, or if everyone else[1] decides to move to a fork. 1. https://news.ycombinator.com/item?id=19827875

Again, where are those contributors? Companies that just repackage Oracle's work don't count.

> Again, where are those contributors?

Current contributions are besides the point, when Netscape open-sourced their browser, the Mozilla Foundation didn't even exist prior to that moment. Java without Oracle is viable - I dare say a "Java Foundation" would be an improvement in terms of community involvement, and there are candidate companies with vested interests (and excellent engineers) to join one should it ever come into existence.

Oracle has a history of not being great at dealing with the wider open source community, not just related to Java: look at how it handled Open Office.

Post reply on HN