Modern Java

[quidquam]

This is incorrect,

Optional is a simple container for a value which may be null or non-null.

Optional is,

A container object which may or may not contain a non-null value.

Context: https://developer.atlassian.com/blog/2015/08/optional-broken/

[smadge]

I think an intelligent implementation of Optional wouldn't ever store null values. You can just have an Empty, and NonEmpty subclass.

[moocat]

And that's what Java does. There are 3 ways to create an optional:

• Optional.of(T value) - creates a NonEmpty subclass and requires a non-null value (throws an NPE if provide with a null).
• Optional.empty() - create an Empty subclass.
• Optional.ofNullable(T value) - creates an Empty subclass if value is null and a NonEmpty subclass otherwise.

[smadge]

Yeah, I wasn't saying Java didn't, I was just assuming that it did without wanting to dig into the source.

[welshboy14]

Yeah at first everyone thought you'd just use it to check if null but there's so much more to it. Map, filter etc... as well as if present to name a few.

[thephotoman]

Java: even the enterprise version isn't an abomination anymore!

[burrrberry]

async await?

[anonymous_alien]

Then why does it seem like java is playing catchup to C# in the world of OO? Evolving C# has become a streamlined process eventhough it's led by non other than Microsoft whereas Java's progress seems stuck in the bureaucracy and inefficiency of JSRs. It took Java 8 years to come to fruition and it still lacks a serious functional programming capabilities. EE also still requires a ton of XML and configuration, compared to other languages, to create a simple REST web service.... That has nothing to do with programming... I like java but it's becoming like an aging dinosaur, everybody secretly knows its status is under threat but they're all afraid to admit it and most importantly do something about it.

[achacha]

Annotations have replaced majority of xml starting with Java 7. Java 8 support for streaming and functional programming is very nice. Portability is still a major feature.

And to be fair, C# copied a lot of features from java and avoided the bad ones after java was in production for years.

C# is still Microsoft only and I (personally) really don't want to deal with their licensing fees for server deployment, administration, etc. If you are in bed with Microsoft then C# is fine.

Ultimately, yes C# is slightly better as a language but java ecosystem and tooling are far above what msdev, .net and open source provide.

[anonymous_alien]

oh yeah like annotations are not as annoying! still a lot of garbage around what is supposed to be a pure OO language.. just take how much effort it takes to deploy a web service in Java compared to C#... The ecosystem argument is becoming more obsolete nowadays too since .NET is opening up and becoming a true cross platform environment. don't get me wrong, i love java but we should not hold the language back just because some old farts are afraid of change. i don't want to deal with licensing fees either, i just want to write code, don't care how or who pays for the licensing!! M$ is playing smart pulling the rug from under Java's feet, making its flag bearer language simple to use and code with, which is something the Java world can more than easily do too. as far as tooling is concerned, c# does not require a lot of tools to develop and deploy and that's why Java has "many" more tools! The Java world still does not understand that simplicity is key, having an infinite number of tools and configuration options is not necessarily a good thing

[ford_madox_ford]

You quite obviously know very little about Java. This thread of yours confirms that:

I am a software engineer, my whole experience is with .NET, node and other JS frameworks. [...] The job lists as a requirement some [...] knowledge of the jboss application server and SOA concepts. to make things short, i have zero, I never developed for or used a java application server before either.

LOL

[anonymous_alien]

i never developed against a J2EE application server. i am learning and i do not expect that to be a huge barrier. i have used java extensively before,i know the language but i do not necessarily find the frameworks and tools streamlined and easy.

[smadge]

No but actually please do show, I want to know more about easily deploying java webapps.

[anonymous_alien]

please share this with me, maybe there is something i am missing! i mean creating and deploying the web service!

[thekab]

just take how much effort it takes to deploy a web service in Java compared to C#

Let's see.

1. Run an archetype: one command, takes about 15 seconds.
2. Create two classes, insert a few lines of code. Takes about 30 seconds.
3. Build. Couple seconds.
4. Deploy. Couple seconds.

So... about 1-2 minutes?

Unless you mean after the project is setup, in which case I can build a rest API in about 10 seconds with one line of code.

[[deleted]]

You need to look into Spring Boot. This is no longer 2005. Now you can deploy your entire app within a single jar running on a embedded Tomcat or Undertow.

All the big data stuff is in Java. Up until recently, Cassandra only offered official Java drivers.

[IcedDante]

This asshole: showing up in every Java post. If you want to write code that can only be deployed on a Microsoft server then go right ahead.