the runLengthEncoding can be written like this: import Data.List (group) import Control.Arrow ((&&&)) encode :: (Eq a) => [a] -> [(Int, a)] encode = fmap (length &&& head) . group decode :: [(Int, a)] -> [a] decode = concatMap (uncurry replicate) Just one (two if you count the signature) line of code that does all that... when I saw this piece of code I became in love with this language.
The idea of "of that is horrible we don't look at it" is the fundamental mistake almost anyone does when trying to teach Haskell. If you can't sort out those error messages, then learning Haskell is way harder as you essentially then have a language which only says "wrong" when you make a mistake with no additional info.
I learned some Haskell last year and is one of the most amazings languages I've ever seen (like APL, but I've never been able to code a single line). It includes other wonderful things such as list comprehensions, where you define a list just writing the conditions that every element must satisfy to be include in it. y = [ x | con1, cond2, ... condN] For example, x is an element of list y if it's included in the list of intergers 1 to 50, and also x is odd: y = [ x | x
9:40 instead of spawning another generation of programmers that is told to find these error messages cryptic (which they are in some probably measurable, UI (user interface)-technical sense (we should start to realize that programming languages and compilers are software with hopefully *human usable* UIs just like anything else)), can't we just go to that compiler and output nice error messages? How much harder would it be to make it write the following: 'byLines' was given 'indent' which is a 'String -> String' when it expected a '[String] -> [String]' indent : *String -> String* byLines: (*[String] -> [String]*) -> String -> String in expression byLines *indent* at line ... (for the conservativists/backwards compatibility, we can still add the message in the current format after that) (by the way, what's with the Char [Char] business in the error message generated?)
Languages are generally wrote by very high end programmers who read those error messages trivially and forget at one point they were not high end programmers.
@Nolansan It knows what to keep and what to forget, it's magic. For example tail recursion is internally treated as a loop and just overwrites all the values on each iteration. It looks like a function that's calling itself forever but actually it uses a fixed amount of memory since it "knows" that all the intermediate values are not accessible from anywhere else.
As multicored processors are now standard and core counts will only be increasing with time, and also as software grows more complex, functional languages are becoming more popular because they're easier to maintain and much easier to program concurrently with. Concurrency is doing multiple things at once to make use of more computer cores.
Since there is no state change, you can share memory across multiple references without fear. Only changes require new memory, deep copy is unnecessary.
In my first impression Haskell looked criptic and weird. But I told myself "me shall learn dat". After reading some I went "wow that's amazing I luv it!" Now I'm trying to understand Monads - I think I'm going nuts.
Impressive, this actually made me interested in Haskell! Could the questions be added as subtitles? Makes it easier to figure out what is actually being answered :)
Code samples=great, Functional=great, Haskell should be used a lot more inside ChromeOS and Chrome as a better way for the internals to be architected and strictly controlled. Great presentation since Haskell content is ALWAYS desired, enjoyed, and overly welcome to me and for use at Google itself.
@cmatt85 I dunno. I work with Lisp professionally, and Lisp really lacks any of the guarantees that Haskell provides. Although Haskell is definitely derived from a lot of concepts created in Lisp, the resulting language is a different beast all together.
I am catching about half of what he is saying... I feel like he steamrolls over stuff far too quickly. This would work fine as an introduction, but none of the details or real explanations are there. Also, why is he laughing at the questions people ask?
the runLengthEncoding can be written like this:
import Data.List (group)
import Control.Arrow ((&&&))
encode :: (Eq a) => [a] -> [(Int, a)]
encode = fmap (length &&& head) . group
decode :: [(Int, a)] -> [a]
decode = concatMap (uncurry replicate)
Just one (two if you count the signature) line of code that does all that... when I saw this piece of code I became in love with this language.
The idea of "of that is horrible we don't look at it" is the fundamental mistake almost anyone does when trying to teach Haskell. If you can't sort out those error messages, then learning Haskell is way harder as you essentially then have a language which only says "wrong" when you make a mistake with no additional info.
I learned some Haskell last year and is one of the most amazings languages I've ever seen (like APL, but I've never been able to code a single line).
It includes other wonderful things such as list comprehensions, where you define a list just writing the conditions that every element must satisfy to be include in it.
y = [ x | con1, cond2, ... condN]
For example, x is an element of list y if it's included in the list of intergers 1 to 50, and also x is odd:
y = [ x | x
amazing language.
9:40 instead of spawning another generation of programmers that is told to find these error messages cryptic (which they are in some probably measurable, UI (user interface)-technical sense (we should start to realize that programming languages and compilers are software with hopefully *human usable* UIs just like anything else)), can't we just go to that compiler and output nice error messages?
How much harder would it be to make it write the following:
'byLines' was given 'indent' which is a 'String -> String' when it expected a '[String] -> [String]'
indent : *String -> String*
byLines: (*[String] -> [String]*) -> String -> String
in expression
byLines *indent*
at line ...
(for the conservativists/backwards compatibility, we can still add the message in the current format after that)
(by the way, what's with the Char [Char] business in the error message generated?)
Languages are generally wrote by very high end programmers who read those error messages trivially and forget at one point they were not high end programmers.
@Nolansan It knows what to keep and what to forget, it's magic. For example tail recursion is internally treated as a loop and just overwrites all the values on each iteration. It looks like a function that's calling itself forever but actually it uses a fixed amount of memory since it "knows" that all the intermediate values are not accessible from anywhere else.
This talk is useful in helping to understand Scala - similar ideas, different syntax
I had the same feeling when I first started programming in Haskell - The language is beautiful.
@noobyfromhell where did you learn it? i wish you'd say "an essay".
understand fp is cool, just curious that haskell has been invented for 24 years, has it always been popular? If just popular these few years, why?
As multicored processors are now standard and core counts will only be increasing with time, and also as software grows more complex, functional languages are becoming more popular because they're easier to maintain and much easier to program concurrently with. Concurrency is doing multiple things at once to make use of more computer cores.
@AshtonK1816 Thanks for the reply. I look forward to learning more about Haskell.
if there is no state change, after a program is running for a long time don't you just accumulate a ton of data and then run out of memory?
Since there is no state change, you can share memory across multiple references without fear. Only changes require new memory, deep copy is unnecessary.
In my first impression Haskell looked criptic and weird. But I told myself "me shall learn dat". After reading some I went "wow that's amazing I luv it!"
Now I'm trying to understand Monads - I think I'm going nuts.
Impressive, this actually made me interested in Haskell! Could the questions be added as subtitles? Makes it easier to figure out what is actually being answered :)
press 'c'
23.20, ghc does not catch it at compile time.
best talk ever
if you are fine with haskell, master the next step and use the coq programming language oder the agda programming language.
56:20 Now we can use Elm for web frontend in functional style :)
I dont understand a thing! I want to learn a functional programming language but it seems so hard!
Why we do not use python instead? What makes haskell/clojure special?
Code samples=great, Functional=great, Haskell should be used a lot more inside ChromeOS and Chrome as a better way for the internals to be architected and strictly controlled. Great presentation since Haskell content is ALWAYS desired, enjoyed, and overly welcome to me and for use at Google itself.
We hope all the replace Android APIs and Web browser control APIs to Haskell optimized.
The phrase "sounds like Lisp" makes me giggle.
It's funny watching a non-mathematician be awed by the concept of disjoint union.
@cmatt85 I dunno. I work with Lisp professionally, and Lisp really lacks any of the guarantees that Haskell provides. Although Haskell is definitely derived from a lot of concepts created in Lisp, the resulting language is a different beast all together.
Ugh, my head hurts. I think I'm gonna go take a nap.
I Wanna learn me a haskell for great good
Turns video on. Bleeds from eyes.
Programming in Haskell isn't normal, but on math it is.
in french it's actually amuse-gueule!
Amuse-gueule is a bit colloquial. Les deux se disent ;)
Hmmm, i can do that in Visual Basic.... i think.....
your profile pic matches your comment :D
This guy is win :D
So much of this sounds like lisp to me.
Without explicit guarantees and speed that come from static strong typing
Get a book, it's easier than you think (If you already can write programs). haskell.org/haskellwiki/Books
haskell is popular? there is only one haskell job available throughout the whole country.
I've been programming in Haskell for months now and I'm honestly disappointing in this talk. It's confusing even for me to follow.
6 people think java is the best programming language....
hahaha :D
I am catching about half of what he is saying... I feel like he steamrolls over stuff far too quickly. This would work fine as an introduction, but none of the details or real explanations are there. Also, why is he laughing at the questions people ask?