Viewing profile — zoomerang

Haskell functions return side-effects using the IO type, with the boilerplate plumbing being hidden with monads and do-notation. "main" in Haskell by default has a return type of "…

Typescript is really starting to look quite compelling. If we could have null-safety and ADTs I'd be using it in a heartbeat.

Really, the only reason Javascripts future looks very bright is because it has a monopoly - it's the only language that runs in the browser. Javascript is a great language for what…

I can remember this switch back in the day, but for some reason my memory has failed me. I could have sworn the original was in Haskell, not Lisp. Selective memory I guess.

As somebody with more experience with Haskell and Scala than Clojure - how to Transducers differ from Functors in Haskell? On the surface they seem very similar.

Out of curiosity, what's difficult about that mutable array implementation? I'm a relative Haskell novice, but was able to write some mutable array code with only a cursory read th…

First up - I'll preface my reply below with a big disclaimer that I'm a relative notice with Haskell, so these are purely my opinions at this point in my learning curve. > What's "…

No specific reason really. I didn't think about it at the time, that's just how I typed it. Probably because C is a single letter, and thus potentially needs some differentiation f…

> that is altar upon which you sacrifice the abilitity I see statements like this all the time from people that either fundamentally misunderstand Haskell, and use to have the same…

Well yes and no. GHC does a pretty good job of warning you when you're missing a potential option in a pattern match, and it's generally pretty easy to write code that avoids parti…

> The idea that compile-time checks is much better than runtime checks is also not obvious (Java's and other commercial languages nonsense about type safety aside - Java is no more…

Not really. The point of Haskell is not to avoid having side effects. The point of Haskell is to allow code to be referentially transparent - this makes it both easier to reason ab…

Out of curiosity, have you tried F#? It's a substantially nicer language than Javascript, and there's a lot of problem domains that are far easier solved in it. People wouldn't use…

"Quick" - sure. HTML5 lets you spin up UIs fairly quickly. "Powerful" - I'm not so sure. Generally I find native toolkits, while requiring a bit more effort up front, generally yie…

For simple apps, HTML5 works fairly well. But you quickly run into problems. My company has been working on a cross mobile application in HTML5 using Cordova. It was quick to proto…

Yes. Java can be compiled to native machine code via GCJ, and can expose a normal C++ Api. Whether you'd want to do this or not is another story. C# and Xamarin would be a far bett…

> JavaScript is the only language that let's you target every platform Ironically, the three languages you listed - Java, C#, and Objective-C are all available on all major platfor…

"Shitty" may not be the right word, since C#'s type system works fairly well for its problem domain. The point is that the type systems found in C# and Java are conservative and in…

> generic is really useful Container types are the most obvious. Lists, Arrays, Dictionaries, Vectors, Stacks. You'd be hard pressed to find code that doesn't use a container type …

> Am I the only one agrees with the author that generics probably do more harm than good It's really the same debate as 'Dynamic' vs 'Static' languages, since without generics your…

The problem with raw SQL queries is that they don't compose. Using an ORM, I can do two things. 1. Pass around query objects, and build queries derived from others. I can also comb…

I went into FP from the perspective of a Python/Javascript/Groovy zealot, considered FP to be a silly academic thing with no real world applications. Took me about a week to be pro…

Having substantial experience running a startup on Scala (Not OCaml, but many of the same aspects apply) I'm going to throw my 2c in. > There is not a strong community behind OCaml…

Monadic futures are a fairly effective solution to the problem. No callback hell, just a clean linear flow of imperative looking non-blocking code that runs concurrently but still …

I can't wait for somebody to hack this and make every Tesla on the planet start honking at the same time. (Presuming there's a 3G hookup of some kind going on here)