HNHacker News
TopNewBestAskShowJobs

happy_dino

145 karma · joined February 10, 2013

submissionscomments
happy_dino··on Go 1.1 beta 1 Released
Sadly, the mailing list debates often don't contain much more than linking to this article and repeating unsubstantiated claims.

The points brought up in the comment section below the article were not answered at all.

Russ Cox: “I would be happy to learn about implementations that somehow manage to avoid all three of these bad outcomes [...]”

First comment: “How about C# implementation? It lets you use primitive types.”

Second comment: “The massive gaping hole in your list of approaches is .NET: reified generics, but in a reference-type oriented language. [...]”

Third comment: “http://msdn.microsoft.com/en-us/library/ms379564(VS.80).aspx talks about the .Net Generic implementation in a bit more detail.”

Russ Cox: ⁎crickets⁎

happy_dino··on Go 1.1 beta 1 Released
I'm wondering how long it will take until people will either stop linking to blatantly false articles or start reading more than the first 5 paragraphs of it.
happy_dino··on Go 1.1 beta 1 Released
I think that asks for some further explanation, considering that Go even ships with hard-coded, built-in “generic” data-structures and the topic comes up pretty much every other week on the mailing list.
happy_dino··on Java Infinite Streams
Having gained experience with both, I can happily declare Java 8 to be finally more complex than Scala.
happy_dino··on Fjord – F# programming language for the JVM
Have a look at http://oss.readytalk.com/avian/.
happy_dino··on Fjord – F# programming language for the JVM
Support for tail calls pretty much depends on the actual runtime implementation.

If it is important to you (it certainly is to me), use an implementation which supports proper tail calls.

I'm doing it and I have never looked back.

happy_dino··on ‘Functional Programming Principles in Scala’ starts today
I wouldn't say that. Not typed, not really functional and mutability everywhere.
happy_dino··on ‘Functional Programming Principles in Scala’ starts today
Sure, except in talent and thought leaders.
happy_dino··on ‘Functional Programming Principles in Scala’ starts today
Even if you know both “paradigms”, Scala's incredibly well-done fusion of those concepts is what makes the language interesting, imho.

You can learn FP and OOP everywhere, but which language combines FP and OOP in such a seamless a way Scala does?

happy_dino··on 6 Months with C#
> Now you're just making things up.

http://skillsmatter.com/podcast/home/expert-panel-discussion...

happy_dino··on 6 Months with C#
> F# actually have significant percentages of uptake because they're actually supported by Microsoft. Scala, Clojure, etc.... are just miniscule blips on the radar in comparison.

I think that's pretty much wrong.

Despite Microsoft shipping F# support in their main IDE, pretty much no one uses it. Can you name one popular library which switched from C# to F#?

Compare that to e. g. Scala: Huge amount of adoption compared to F#, despite _not_ shipping with any IDE by default. One of the most popular Java web frameworks switched from Java to Scala recently.

Even the F# “elite” is aware of it and complaining about how Scala has a a lot higher adoption (and a larger ecosystem and more developers, libraries, conferences, user groups, support, ...), so I'm a bit surprised by your statement.

happy_dino··on Writing Web Applications in Go
I'd say this is largely a non-problem. If you already know F#, then Scala is a much simpler, more consistent language. In a way, Scala seems to be a refined, better designed version of F#.

For instance, F# has support for functional and object-oriented programming, but most people I spoke to recommend just ignoring the object parts. That's certainly my impression, too. Compared to Scala, F# didn't manage to combine FP and OOP into a single, coherent approach. You have more or less ML's type system with the object stuff bolted on.

Another example would be that F# has tons of features where a single one could suffice. Consider the Unit of Measurement stuff, the various forms of (computation) expressions and type providers. Scala can do all of that and a lot more with "just" macros.

> It's nice that I can abbreviate some common constructs

Not sure what you mean with that.

> How do I look up these operators when they could come from anywhere (global, first operand, second operand, implicit conversion, etc.)

Not really. There are no operators, everything is a method invocation. The method is either defined on the type of the left, or added by an conversion from that type. That's it.

> How do I know when parentheses, dots, curly braces, are mandatory or optional?

Method calls with one argument can leave out dot and parentheses. If a method has a side effect, you define and call it with parentheses, otherwise you leave them out.

> There are too many implicit things going on, how do I know which meaning of _ (underscore) is meant here?

People love to make up scary examples, but I have never seen any actual misuse of implicits in real code. The meaning of the underscore doesn't change, it is always the same: "There exists something, but I don't care to give it a name."

I hope that helps a bit!

happy_dino··on The comeback of static typing
I wouldn't call something "fully statically typed" when most abstractions can only be implemented by casting from and to the top type.

There is a reason why no one wants to use Java 1.4 anymore.

Go's "static typing" is next to useless.

happy_dino··on Google I/O 2013
> and Scala doesn't seem like an option

Care to explain why?

happy_dino··on The Play Framework at LinkedIn
It's funny that you keep picking blatantly wrong examples.

    scala> def ==(a: Any) = false
    <console>:7: error: overriding method == in class Any of type (x$1: Any)Boolean;
     method == cannot override final member
           def ==(a: Any) = false
               ^
Maybe you should actually use the language for a few minutes before commenting? :-)
happy_dino··on The Play Framework at LinkedIn
In general, that's nonsense.

There are certainly languages which are comparatively close, so that it is hard to tell, and where different weightings can lead to different results. That doesn't mean it is like this for every comparison.

For instance, the comparison between Java and Scala certainly doesn't belong to this group, just like comparing PHP with many other languages also leads to a clear outcome.

But honestly, I don't care. There are also people claiming that there is no "objective superiority" in cases like "evolution vs. intelligent design", "6000yo universe vs. billions of years", "software patents vs. no software patents", "no contraception/abortion vs. women's rights".

Right reaction is to laugh and move on.

happy_dino··on The Play Framework at LinkedIn
You don't like someone's experience and claim that people who agree are basically paid by Typesafe? Great way to debate.

FYI: I don't work at Typesafe, and I share his experience.

One great thing about Scala is that one can immediately tell whether someone has actually used it by looking at the complaints.

Things like "OMG _!!!", "Null, Nothing, None ... sooooo confusing", "Perl", "C++" give it away immediately. I wonder why people are not more upfront and honest about not having spent more than 5 minutes with Scala. It's totally OK, no one can learn everything.

happy_dino··on The Play Framework at LinkedIn
Irony. That's Java.
happy_dino··on The Play Framework at LinkedIn
> Scala has way more language features than Java

I wouldn't say that. I think the main difference is that Scala spent its language design budget on more useful things compared to Java. Have a look at C# if you want to see a language with tons of features.

> What I mean is, how much do you know about what a particular piece of code does when looking at it in isolation? How much additional context do you need to figure out what it does? How many possibilities are there?

From experience, that amount of code is considerably smaller than Java because I can be pretty sure that some piece of Scala code usually won't mutate stuff all over the place.

happy_dino··on The Play Framework at LinkedIn
> Java comes with cheap programmers, some of the best tools in the world, reliability, and speed.

You realize that none of your points are actually related to the language itself?

Yes, Scala's syntax is ugly, just look at this cryptic operator soup: int[][]_00_[][]=null;

happy_dino··on The Play Framework at LinkedIn
Just like a CPU, the design of the language was informed by the experience gained and the lessons learned when analysing/building its predecessors.

The analogy is perfectly fine imho.

happy_dino··on The Play Framework at LinkedIn
And what's your actual point now, except trying to disagree?
happy_dino··on The Play Framework at LinkedIn
I really can't imagine how that is supposed to be even remotely controversial. That's probably as controversial as saying that a $200-CPU built in 2013 is faster than a CPU in 1993.

Isn't that just repeating the “all languages are equal”-myth?

happy_dino··on Why I Like Go
> Indeed, you can end up with an indeterminate state.

No. I think that claim is hysterically funny considering that Go developers almost never check all FOUR states of Go's style of error handling.

The problem Go is solving here wouldn't even exist if they had designed/used a better language in the first place.

Maybe Go people should stop drinking so much Kool-aid, because they sound like all these Node.js-ninja-rock-star kids who think that they revolutionize asynchronous programming while they reinvent threads, badly.

happy_dino··on A New Java Library for Amazing Productivity
Interesting article which asks the right questions.

These days, nobody should need to use Java to reap the JVM platform's benefits.

happy_dino··on Why I Like Go
> However having a language that combines this Scala feature with Go's exception-free error handling, would be awesome and a true solution that would make software run more reliable and with less crashes.

Do you realize that this is actually the case? Every Library/API I have seen in Scala until now uses the appropriate abstractions like Option/Either/Try/Validation/... and restrict exceptions to the most exceptional faults.

But anyway, if I had to choose between Go's horribly broken approach of returning multiple values and exceptions, I'll choose exceptions every day. Exceptions are ugly, but at least they are not blatantly wrong like using tuples for error codes.

← PreviousPage 5 of 5