Hey @FridaTveit, I do not agree with this description. I would prefer instead what James Gosling would say: The Java programming language is a general-purpose concurrent class-based object-oriented programming language, specifically designed to have as few implementation dependencies as possible. It lets application developers "write once, run anywhere".

Hi @michaelspets :) Like I said, I'm very happy to receive different suggestions for the blurb, thanks for offering your help! :)

As it is though, we've already had a complaint about the sentence "specifically designed to have as few implementation dependencies as possible." (see issue #406). Also bear in mind that the first thing the users will read after this blurb is ABOUT.md which starts with:

Java is a general-purpose computer programming language that is:

• Concurrent
• Class-Based
• Object-Oriented

But I guess whatever we write it will probably be repeated somewhere in ABOUT.md. Later in ABOUT.md it mentions low-level features and being simple as well. So repetition might be unavoidable/not a problem?

Also from what I can tell this is taken word for word from Wikipedia. I think @kytrinyx wanted us not to directly quote something like Wikipedia but instead use our own phrasing to make it more understandable, but I may have got that wrong?

What do you think @exercism/java?

I think the implementation dependencies line is confusing, especially for newcomers. The "write once, run anywhere" portability is probably something worth calling out, however. I'd be in favor of adapting that and including it in the blurb somehow.

I tried to incorporate the portability in the blurb. What do you think @stkent, @michaelspets? :)

It is very nice @FridaTveit.

Perfect mashup!

LGTM!

I think @kytrinyx wanted us not to directly quote something like Wikipedia but instead use our own phrasing to make it more understandable

Sorry I'm so late to this.

Yes—I don't want us to quote Wikipedia or other sources directly, unless it's a really great colloquial, friendly quote, and then only if we have it in the ABOUT with proper attribution. The blurb is not the place for this.

Thanks @FridaTveit for taking the lead on getting this done, and thank you @michaelspets for your input. It's only by actually raising the issue that we can discuss these things and figure out what works for our situation.