News for hackers. Stuff that matters.
Re:Scala: Where it came from, Where it's going by eklavya on Tuesday March 17, 2015 @02:32PM (#9220185)
> It's crazy that in these slides he says "I wanted a hipster language" -- most languages use [] for arrays so I used (). WHY!!!!? Just to be different? No actual real advantage? That's a terrible reason and a great way to make it hard for new people to adopt your language.

func<Future<List<Option<String>>>> vs func[Future[List[Option[String]]]]

Which one is easier on your eyes?

Re:Scala: Where it came from, Where it's going by trhway on Tuesday March 17, 2015 @03:52PM (#9220850)
>>func<Future<List<Option<String>>>> vs func[Future[List[Option[String]]]]

>Which one is easier on your eyes?

i don't get the joke here. Or are you seriously implying that one is in someway better than the other? (i'm curious as i've been in the industry for more than two decades, so my eyes just filter that crap automatically anyway)

Re:Scala: Where it came from, Where it's going by jghn on Tuesday March 17, 2015 @07:22PM (#9222347)
Granted I'm biased as I'm primarily a scala dev these days but I've always preferred the square brackets over the angle brackets. At least for me it is actually more readable.
Re:Scala: Where it came from, Where it's going by seanmcdirmid on Tuesday March 17, 2015 @10:41PM (#9223279)
Angle brackets aren't even very readable, couple that with the fact that they are also OPERARTORS and you are looking at some major complexity in your parser to distinguish between bracket usage and operator usage (possible, but requires looking ahead, worse syntax errors).
Re:Scala: Where it came from, Where it's going by frowaway001 on Wednesday March 18, 2015 @01:48AM (#9223830)
Or just terrible syntax choices like in Java or Rust.
Re:Scala: Where it came from, Where it's going by eklavya on Tuesday March 17, 2015 @04:20PM (#9221114)
I am seriously implying that one is easier on the eyes than other.
Re:Scala: Where it came from, Where it's going by imh on Wednesday March 18, 2015 @02:05AM (#9223880)
That's really not a fair comparison here. With a monospaced font, it's much more comparable:

  func<Future<List<Option<String>>>>
  func[Future[List[Option[String]]]]
Re:Scala: Where it came from, Where it's going by outworlder on Tuesday March 17, 2015 @04:01PM (#9220941)
Or, maybe, perhaps:

func(Future(List(Option(String))))

Re:Scala: Where it came from, Where it's going by smenko on Tuesday March 17, 2015 @06:45PM (#9222164)
Err, no... One is a type construction, the other is function application. It sure helps if these are different...
Re:Scala: Where it came from, Where it's going by platz on Tuesday March 17, 2015 @10:03PM (#9223139)
Conceivably, it could be application of a type constructor to type arguments, where parens control precedence, not application:

    Func (Future (List (Option String)))