felipehummel

That's the best and succinct description of using ChatGPT for this kind of things: it's a floor raiser, not a ceiling raiser.

That's no true at all. The syntax is pretty similar with few key differences. The idea is for dotty to become Scala 3.0. But, in the meantime, the next Scala 2.* versions will pave the way for 3.0. Meaning to avoid too many breaking changes in 3.0.

The above has been said repeatedly by Martin Odersky (creator of Scala) and the folks on the Scala compiler team in talks and discussions.

You may try out using Scala as script language like this: "scala myScript.scala". The first startup times are slower, and even after that it may be slower than Python/Ruby but it still may be sufficient for your use case.

Using "sbt ~run" (re-runs your program automatically at every file change) may also be an option.

Although named arguments are good, you won't use it in all function calls.

Can you elaborate on this: "and to handle all cases..".

From my brazilian perspective it's very strange to read this. In Brazil, vacation is mandatory by law. Any employee has 30 days of vacation by year. But the moment the employee goes on vacation and how he does it (30 days straight, 15-15 days, 20-10...) is still discussed previously with the employer.

I'm not judging which one is better, just acknowledging the culture difference.

Not really a natural law, but medicine from time to time finds out that working too much or sleeping less or not having time for pleasure/fun/family hurts your health.

You can actually make it automatically convert in both directions with just an import. But it is good practice to do it explicitly. In my opinion, for a typesafe language, this is a good way to do it.

I think "distributed" in this context is about multiple machines/servers. Not multiple plataforms.

A few suggestions: you could remove this kind of idiom: .map( result = { ... }) In the blocking commands example the snippet resembles the Javascript callback hell when it could be simpler to read: https://gist.github.com/felipehummel/6187248

Also, even simplifying it, it still seems overcomplicated. The returning type: Future[Try[Option[(String, ByteString)]]] is too much. Can't you remove the Try or the Option? Futures can already hold either a Sucess or Failure, so isn't the Try redundant?

Chrome in OS X here and it all seems fine.

Comparing Pattern matching to "ifs and elses" shows that, saddly, he didn't really understand its power.

Also, his opinion on Options seems to forget its advantage that the compiler won't let you use a "nullable" object without proper care. It is the main thing about it.

From the talk, it seems that he was new to Scala, didn't properly understand its concepts, wrote a bunch of spaguetti code and then blamed the language.

I didn't understand what it is supposed to do.

It hasn't been a real problem for me. But I cant say the same for every kind of program developed in Scala. I'm not saying that it is not a problem and I dont recognize it. Its just that, for me, the problem is much smaller than some people here seem to think.

Maybe I've waited too long too many times for gcc to compile C/C++ that when I went to Scala I thought waiting some seconds to compile is okay =P

How many times you do full recompile during a day? I'm curious because in my workflow I rarely do full recompile.

Just use sbt ~compile. It will compile every time a file changes (only what is needed) . I've been using Scala full time for a year now, and I've never been bothered by compiling time.

One simple example of Scala power is the greatness of the Future pattern (scala, akka, finagle/twitter and other implementations).

You can still have the exact same Futures functionality in Java, but they will be so much more verbose and annoying to use that it ends up not being a good idea.

Scala compilation is indeed slow (although I think C++ is worse). But I always have a "sbt ~compile" running, compiling every file as they change. So the compilation time is pretty much irrelevant to me. While using eclipse, I guess, you'd get the same speed too.

The "much harder to read" varies greatly between codebases. Most "sane" codebases are 90% (random percentage) as easy to read as Java. Just collection initialization, transformations, simple pattern-matching, method invocations... Some times there is an ugly nested flatMaps/maps/filters. But in my experience, in general, they're more the exception than the rule.

Can you elaborate on how you merge clusters? Many times a clusters will be just single-doc clusters, how to check if you need to merge two single-doc clusters? (it seems like the same process that was done in the first place to create the clusters: doc x doc similarity)

saturdaysaint said GUI.

Siri has pretty much no interface. The AI/data part of the problem is much, much harder.

I also would really like to read more about successful use of Scala in various companies. Twitter uses it, but is it happy with Scala?

After I discovered this feature/shortcut I started not caring anymore about Unity bugs. Navigating applications this way is much faster than alt+tabbing. Another useful shortcut is alt+` (backtick). It cycles through open windows of the same application. If you have 10 PDFs open, you can cycle through them with alt+`.

I also believe it is nonsense to overuse symbols for methods. I think even Martin Odersky agrees (I've read somewhere).

I guess this is something that will settle down eventually. And programmers will stop using so much random symbols instead of English.

For the specific case of Lists, I don't think is that much trouble. It is the most important class of the language. You better get used to it anyway.

I know. I've seen it. Can you point to some unreadable code? Preferably one that does not fall into the 'operator overload ing abuse' category?

Best summary on this whole discussion.

I really want to see all this thrash/unreadable Scala code that everyone is talking about. I haven't done any great projects on Scala, only smaller ones. With a few exceptions (of operator overload and implicits abusing) I've read many Scala sources and after you pass the "functional programming WTF moments" you come to understand pretty much everything.

What this 1 year old child can accomplish using the iPad? I'm really curious. Would it be different with any other large touch screen interface?

Do it like stackoverflow. Search submitted urls/articles and show in the article submission interface. Preferably ajax-y so as user types url and/or title it already sees if he is posting something repeated.