runT1ME

40 ms·

361.
by runT1ME 12y ago
>Haskell introduced typeclasses. Go and Rust popularize them (as interfaces and traits, respectively, the latter also influenced by C++ STL's concepts). This is a really ironic thing to say considering Go doesn't have generics,
362.
by runT1ME 12y ago
Why would anyone in the top (let's say, 5%) of tech be interested in working for IBM when it seems this is how it treats its employees?
363.
by runT1ME 12y ago
> controlling how things are executed/computed. No...see...you understand a monad. That is not the same thing as groking "Monads" in the abstract sense. For instance, I don't think the State monad really has anythi
364.
by runT1ME 12y ago
Isomorphic means there exists an 'isomorphism' or an invertible function between two things that aren't the same. So an Array and a List could be Isomorphic, but a Set and a List could not be. You could have (I think?) an iso
365.
by runT1ME 12y ago
Awodey's does not have answers to the exercises, so it makes it hard to find out if I'm getting close or just scribbling things down...
366.
by runT1ME 12y ago
Does anyone else see the missing piece to this post mortem? An infinite loop made its way onto a majority(? all?) of production servers, and the immediate response is more or less 'we shouldn't have deployed to as many customers,
367.
by runT1ME 12y ago
Have you read the canonical Functional Programming in Scala? It goes over all of that and more in immense detail. http://www.amazon.com/Functional-Programming-Scala-Paul-Chiu...
368.
by runT1ME 12y ago
Scala does everything C# does and a lot more. I'm a big C# fan but we're doing new development in scala and even porting some of our C# code over.
369.
by runT1ME 12y ago
This is FUD. You often don't need trampolines and there are better solutions than trampolines.
370.
by runT1ME 12y ago
Scala's biggest advantage over other languages for me in terms of reducing bugs, complexity, and pleasantness have been higher kinded types. Given that F# is lacking in this, and they don't have plans to add it, I can't even
371.
by runT1ME 12y ago
I appreciate the response, but I don't follow the argument. >All of these incompatible forks need to down-integrate the change and work around the little tweaks they've added. You have a mess. Is that really better than havin
372.
by runT1ME 12y ago
>When you have a number of interdependent modules, then every change request and new feature has to go through that module's owner. If it's not their top priority (and it won't be), then getting your work done suddenly has
373.
by runT1ME 12y ago
Our organization (big C# codebase, newer apps in scala) has doubled down on extremely functional C# (using the NICTA XShapx library which has a lot of overlap with this one). It's been a tremendous help. C#'s linq comprehension
374.
by runT1ME 12y ago
>What this means in practice is that companies that use open source extensively in their operation, become slower and slower to innovate as they are carrying the weight of a thousand different systems of checks on code quality and robust
375.
by runT1ME 12y ago
It sort of seems like you've spent a lot of effort to re-invent a less good version of scala? Why not Scala?
376.
by runT1ME 12y ago
Do you know about Scala?
377.
by runT1ME 12y ago
>I don't think Scala usage will grow much more now that Java 8 is released Do you think the main reason people use Scala is because of lambdas and type inference?
378.
by runT1ME 12y ago
F# is a remarkably less powerful language than scala. Along with the cost of Visual Studio + windows licenses, the Scala/open source ecosystem is just a better choice.
379.
by runT1ME 12y ago
>C# seems to look more like Scala with every release It does, but then that begs the question of "why use c# at all?". C# is still missing (along with F#) scala's most powerful features, and I prefer the JVM and openness
380.
by runT1ME 12y ago
I should have added that despite me not liking the std lib collections library, it's still stands above all other collection libs I've used in other languages. The problem is that the std. lib collections tries to unify mutable&#x
381.
by runT1ME 12y ago
The collections library itself is probably one of the worst things about scala. I've ranted on the mailing list before, but it's overuse of inheritance rather than a type class based approach kills reasoning and modularity. Subty
382.
by runT1ME 12y ago
As someone involved in the scala community (and scalaz) community, I'd say about 60% of the companies I talk to at the various meetups use at the very least #scalaz. I was pleasantly surprised.
383.
by runT1ME 12y ago
OCaml?
384.
by runT1ME 12y ago
Neat reply, thanks. In regards to #2, this sounds like the ST monad, are they comparable at all? What makes OCaml easier to debug with GDB opposed to haskell specifically? I don't have experience doing either, but that's a curiou
385.
by runT1ME 12y ago
C# is missing good type inference, implicit conversions, implicit parameters, higher kinded types (huge loss), lightweight method syntax, currying, pattern matching...
386.
by runT1ME 12y ago
You seem completely ignorant of the things you're attempting to talk about. Scala doesn't have "hundreds' of features, nor is the language specification thousands of pages. It's just an outright fabrication to say
387.
by runT1ME 12y ago
>I can understand some of the things FP gets you I really don't think you do understand, as an example in the last thread we ran into each other you completely missed the fact that Futures allow concurrency for free since you&#x27
388.
by runT1ME 12y ago
I'm not sure if .NET has a bad rap at all, rather I believe the onus is on the .NET developer to show it was a better choice than the alternatives that are more mature and flexible from a licensing standpoint. I consult as a software e
389.
by runT1ME 12y ago
Seriously, just use scala Futures. Here's one of many super easy ways to do parallel computations in scala: val list = getItemsToProcess() //List[SomeObj] list.map(so => Future { processorHeavyMethod(obj) }) &#x2F
390.
by runT1ME 12y ago
Functional Programming in Scala. It's not a book about scala, it just so happens to use scala as the language to teach you how to program functionally. I've read other books that purport to do the same, they end up showing a ligh

More ›