"It takes two" has marvelous story and definitely is not violent

Just discovered it yesterday. Had an awesome time playing it with my wife. Can only recommend

Browser tab problem is not about the web or the browser, it is about users' habits and discipline. If you suffer from this "problem" invest time in learning shortcuts for bookmark, typing to search history in the address bar, saving things in proper place for later reading and, above all, concentrate on one thing for more than 5 minutes.

At the end of the day, it's a browser, not a boot camp. If user re-education worked designing software (and most other things) would be a lot easier.

This mindset/rant does not work in the real world. When a large enterprise company tried it, (Apple), they were widely mocked for blaming users for “holding it wrong”.

It is not up to developers to determine how users use their tools. The best you can do is hint and nudge, but it is not your decision at the end of the day.

I don’t think it’s solvable if users don’t themselves close or group/categorize the stuff they’re opening. Any automation/heuristic is prone to not do what the user wants, because the tool can’t really judge why the user opened any given page, and thus can’t make an informed decision in how to handle it. I can think of new (mostly power-)user features to support the user in organizing opened pages, but I have a hard time imagining an I-don’t-want-to-deal-with-this user feature that would universally “just work”. (Of course, I may be wrong.)

The closest I can think of is to have sortable list views of open pages that you can sort by open date, last updated, possibly content type (e.g. has video), and/or group by site or by “opened from” (navigation history graph). Again, this is moving into power user territory.

this sounds like a good candidate for issue report. Would you mind collecting performance snapshot and sending it to JetBrains?

Yet it indeed makes full use of resharper:

"instead of reimplementing ReSharper’s features on the IntellIJ Platform, which runs on the JVM, we’re using ReSharper in a headless mode, out of process, and communicating with it via a very fast custom binary protocol. "

Kotlin doc has short feature comparison with scala: http://kotlinlang.org/docs/reference/comparison-to-scala.htm...

In general, "If you are happy with Scala, you probably don't need Kotlin."

Which is kind of funny, because they are still playing catch-up with Scala.

(That's perfectly fine on its own, but doing the usual Scala-bashing at the same time as copying most of the language varbatim doesn't make the Kotlin team look any better.)

They've stated their decision not to copy certain features such as rampant operator overloading. Is this what you mean by "Scala-bashing"?

No. Scala has neither operator overloading nor any kind of rampant form of it.

In Scala you can define stuff like <*/+-> to mean anything you want. Are you perhaps arguing over my choice of words to describe this phenomena?

Yes. It's neither an operator nor are you overloading anything.

The whole point is that everything is just a bog-standard method and infix notation is a orthogonal notion, separate from a method's name.