premium-concern

This is more of a split between techniques for programming-in-the-small vs. programming-in-the-large.

All languages have this. You could write more or less the same list for Swift or Java with minimal changes.

Again, do you have any actual experience with this, or is this just your assumption? Because I have never seen this issue in the wild.

I have never seen this.

> Swift syntax is more intuitive and readable than Scala

Example?

> The problem with Scala is not that it has all the features of Swift, it's that it has way more.

Please have a serious look at Swift. I don't think this claim stands up to any kind of scrutiny.

Swift is more like C++ than anything else in terms of features, Kotlin has roughly the same amount of features as Scala but more special-cased ones. Kotlin solves one problem well, and only that one: If you want to write Java, but want it to be a bit less verbose, then Kotlin is perfect.

Even if it did, it wouldn't matter, because people would vote those politicians that tried this shit and their party out of office.

Even government budgets have to adhere to some standardized schemes of reporting. See also rating firms.

Otherwise even the US would have a balanced budget and no debts. (Ignoring the fact that the US is the main force behind trying to change the account rules to make them look less bad.)

Given the size of the deposits, and the ROIs of available low-risk investments, does the difference really matter?

Skip a single CappuFrappeGingerPumpkinLatte (or what people buy in cafes in SF) and you just got more money than any investment on the deposit can ever make.

> However there are also co-operatives that invest your deposit and actually pass on the interest to you when you move out (these apartments are rare though).

This is not optional. It is required by law. Interest from deposits belong to the renter.

Consider two functions (excuse my Scala):

  scala> val str: Function[String, String] = s => if (s.length > 3) s else null
  str: java.util.function.Function[String,String] = $$Lambda$1369/859456754@2c668c2a

  scala> val num: Function[String, Integer] = s => if (s == null) -1 else s.length
  num: java.util.function.Function[String,Integer] = $$Lambda$1376/1887041776@121cf6f4

With Optional, you receive different results depending on whether you call map twice, or combine the functions first:

  scala> Optional.of("Foo").map[String](str).map[Integer](num)
  res12: java.util.Optional[Integer] = Optional.empty

  scala> Optional.of("Foo").map[Integer](str.andThen(num))
  res15: java.util.Optional[Integer] = Optional[-1]

This is incorrect. (They decided to disallow null as Optional's value for whatever insane reason.)

It also leads to all sort of weird usability issues: The old "`someMap.get(...)` returned null ... now does that mean the entry doesn't exist, or the entry exists and it is null?"

In fact they are currently working on special hacks to Java 10's Generics, because they realized that important collection classes don't work well with specialization, and even their new Optional can't save them. (Not directly related, but a good example how design mistakes combine and cause even more pain down the road.)

Yawn.

Java is the platform with NPEs and null checks everywhere. If that's your definition of practical, sure, go ahead.

In Germany:

- Rent increase limits

- Larger changes need landlord's approval (changing walls and stuff). A lot of smaller stuff can be done on your own and doesn't require asking the landlords. (Many landlords are happy if you want to paint the walls etc., though.)

- Only smaller apartments (often intended for students) come usually with furniture

- The deposit has to be put on a special, locked bank account. The money can only been withdrawn if both sides tell the bank in writing that the rent contract is over

- Depends on the size of the pet

Which includes leased company cars. So yes, people don't finance their cars.

> political brinkmanship and finger-pointing

The difference is that parties that try to pull that in Germany not only loose elections, but are punished so hard by voters that they can't even get over the necessary 5% requirement in the next election.

Have a look what happened to the FDP after they pushed through lower taxes for hotels.

Optional#map is implemented incorrectly.

   someOptional.map(a).map(b) NOT EQUAL TO someOptional.map(a.andThen(b)

No. Java messing things up as usual, doesn't have any broader impact on the usefulness of the concept.

Error handling with null is wrong and broken, regardless of whether the null is "typed" or not.

null might have some very limited other uses, but they will never compete with those structures designed for error handling, because they do something fundamentally different.

Yep. "Don't buy things if you can't pay for then." sounds reasonable, but some other countries seem to disagree.

Not surprised that those countries suffer from government shutdowns over how much the debt ceiling is raised.

That's an extremely weak argument. Java's Optional is broken and should never be used.

Or you use Scala and Scala.js and just get things done.

That's what "rent" means.

Did you even bother to read the article before commenting?

There is nothing a client can do when the server is compromised.

I stopped taking this seriously after "the documentation is really good".

Not sure whether this is your real opinion or you are just making fun of people who say that.

I think this assumes that Oracle

- can ship something in time

- and that it will be generally available for developers (looking at how hard Oracle pushes their Java department to invent commercial features they can sell, I'm not sure about that)

Looking at it, I assume that this will go the way of GWT ... not starting from "how can we make Java a good citizen in this new ecosystem?", but "here we have 100% of Java, the JDK and the JVM ... how can we compile this with full fidelity into X?".

Is there anything this adds over Scala-native, which seems to be much further ahead already?

Scala has value types, and on native all the current restrictions from the JVM are dropped.

Additionally, you can also explicitly allocate things on the stack.

You can also allocate continuous memory.

The amount of code bloat is offset by optimizing a medium-sized picture.

You don't need Autowite for that. That's pretty much basic functionality of Scala.js.

That's kind of nonsense. Kotlin adds some syntax sugar to Java, but it's not related to Scala in any reasonable way.

The difference is that Scala is a vastly better, designed language. It's not something like Typescript which tries to salvage JavaScript without being able to fix the worst parts.

Scala also has much better, more mature tooling and IDE support.

The build system is also amazing, not the mess cobbled together in JavaScript that is changing every second week.

In addition to that you have stable, existing and mature libraries which work on multiple platforms, achieving _real_ cross platform support. (Not this "if you make JavaScript run outside of the browser..." nonsense.)

Plus, the quality of libraries is so much higher because they aren't written by JS kids with a maximum attention span of 5 minutes.

Not sure what you are talking about regarding SBT. SBT does incremental builds, it's one of the few that even do this interactively. It is also built on parallel-by-default execution: The task engine runs everything that can be computed in parallel except when you request sequential processing. (Some old code-bases with broken tests for instance.)

My experience with Google software is that its usually not as good as Google employees think it is. See Go, Dart, GWT, Android, Google Groups, Angular. I think this can be partially contributed to the sect-like structure of the company where everything created at Google is the best thing ever, while everything invented in the rest of the world is discarded or ignored. See this hilarious reply from Googlers to a feature that many people take for granted, but Googlers are completely unaware of: https://github.com/bazelbuild/bazel/issues/1394

Bazel is yet another thing where Googlers think they have invented the best thing ever, and then have to realize that the world around them, which they tried to ignore so hard, has moved on since 1970, making their "really great, special tool" neither great nor special.

Not sure if there is a "leading" one ... Lightbend, EPFL, IBM, Verizon, GoldmanSachs, SAP, Twitter, ...