Painful watching.

[Jem]

Here's someone who utterly misunderstands Scala. The WTF ratio in this talk is high.

https://vimeo.com/64716826

From 8:40 to 15:20.

Enjoy!

[Tony Morris]

> --
> You received this message because you are subscribed to the Google
> Groups "Melbourne Scala User Group" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to scala-melb+...@googlegroups.com.
> To post to this group, send an email to scala...@googlegroups.com.
> Visit this group at http://groups.google.com/group/scala-melb?hl=en-GB.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
Yeah we discussed this on twitter recently. Not all light bulbs are bright.

--
Tony Morris
http://tmorris.net/

[Korny Sietsma]

Wow.  The stupid, it burns.  I didn't make it all the way to 15:20 - after he started *again* dismissing pattern matching as a bad idea, I gave up.

- Korny

--

You received this message because you are subscribed to the Google Groups "Melbourne Scala User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-melb+...@googlegroups.com.
To post to this group, send an email to scala...@googlegroups.com.
Visit this group at http://groups.google.com/group/scala-melb?hl=en-GB.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

Kornelis Sietsma  korny at my surname dot com http://korny.info

.fnord { display: none !important; }

[Travis Dixon]

Feels a bit like preaching to the choir by posting it here, but...

The question on Go's dependency management was pretty amusing.  

Turns out Scala is bad because you can't use libraries compiled across language versions, but the fact that Go doesn't allow you to lock your dependency down to a particular version is just "the new way you share libraries these days"

When a CEO, (no matter how large or small his company) gets up on stage, says "I spent 6 months in this language" repeats "I just didn't understand it" a bunch of times along with "I just didn't want to spend a day or two to get it working", and therefore doesn't like it... 

well... 

I guess I don't regard it as the opinion of a software engineer.

I will tend to agree though, that if you decide to introduce Scala on a short project, leave no time for ramp up and education on the new concepts it introduces, but try to use them anyway, then yeah I reckon you might have trouble.

[Tony Morris]

I observe that you're occasionally a little more generous in describing what is actual :)

-- 
Tony Morris
http://tmorris.net/

[Jonathan Merritt]

I think my main complaint is the lack of depth.  I'm not exactly a Scala or FP power-user, and I too wondered about the reasons for using Option in Scala APIs.  However, I rapidly found blog posts comparing Option with the equivalent null checks, pointing out that the "null checks" couldn't be omitted accidentally if Option were used.  That was enough to make me interested.

Jonathan Merritt.

[Ben Hutchison]

On Sun, Apr 28, 2013 at 8:25 PM, Jonathan Merritt <j.s.m...@gmail.com> wrote:

I think my main complaint is the lack of depth.  I'm not exactly a Scala or FP power-user, and I too wondered about the reasons for using Option in Scala APIs.  However, I rapidly found blog posts comparing Option with the equivalent null checks, pointing out that the "null checks" couldn't be omitted accidentally if Option were used.  That was enough to make me interested.

During "phase 1" of my Option learning, I thought Option was just a way of representing null more explicitly; nicer, but I didn't see a whole lot of value.

In "phase 2", I realised it is a value incorporating some uncertainty, and that's damn useful as is. There's often no need to unwrap the option except right out on the boundary:

def parseFloat(s: String): Option[Float]

def squareRoot(f: Float): Option[Float]

val optRoot = parseFloat("foobar").flatMap(squareRoot)

//There's a null check in there we totally eliminated

-Ben

PS watched about 2 minutes of the video, halfway through, got the gist. Happened to land on a place where the speaker was saying "theres a ton of things I dont know about Scala" but then he went on to bag it anyway. Are these the kinds of advocates Go needs to build credibility, I wonder?

[Korny Sietsma]

One of the things I really liked about Options back when I was doing Scala, was *not* using them.  If I had something not wrapped in an Option, I knew it could never be null, which was wonderful.  The few places where I did have Options I could use flatMap or case or other things to unpack them as needed, but the real benefit was all the pointless null checks (or NullPointerExceptions) I didn't have to care about everywhere else.

- Korny

--

You received this message because you are subscribed to the Google Groups "Melbourne Scala User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-melb+...@googlegroups.com.
To post to this group, send an email to scala...@googlegroups.com.
Visit this group at http://groups.google.com/group/scala-melb?hl=en-GB.
For more options, visit https://groups.google.com/groups/opt_out.