Look at those Huskell retards and laugh

However, this comes with the caveats of using WriterT [a], which is that it will leak space like crazy for a large assembly computation (even if you don't log anything!).

This is wrong.

*Main Control.Monad> take 2 . flip evalState 0 . execWriterT $ forever (byte 4)
[4,4]

Also, when complied with -O2 then

main = print . flip evalState 0 . execWriterT $ forever (byte 4)

appears to run in constant memory.

------------------------------------------

Huh. I guess that works because the whole stack is lazy. However, if you make the base State monad strict then WriterT leaks space:

>>> import Control.Monad.Trans.Writer
>>> import Control.Monad.Trans.State.Strict
>>> import Control.Monad.Trans.Class
>>> import Control.Monad
>>> runStateT (execWriterT (forever (lift (put 1)))) 0 -- Leaks space

JACKSON 5-3 GET.

JUST USE RUBY ALREADY!

>>3
Even though it is not lazy, it is OOP which is much worse than Haskell.

You could just get shit done F#.NET (might even get you a job, in finance even).

http://fsharp.org/use/linux/

Or keep using haskell because you read it was cool on Reddit or Hackernews or some shit.

>>5
The corporate idiot doesn't even get the point of the thread, which is that laziness is shit.

Also why would I want a job programming? Programming is not something that should be done for a job, and certainly not something that should be done in plebs langs like M$hitCF#VB.NET.

>>6
He also doesn't know that there are plenty of Haskell jobs out there.

Challenge: write an anaphoric macro in HASKELL.

>>7
Personally, I'd rather live and breathe Microsoft shit for the rest of my life than spend a week around Haskellers.

>>9
Feels bad to realize your own stupidity, huh?

>>6
F# isn't lazy (by default), have fun flipping burgers while writing shitty homoerotic code at home and not understanding why you have memory leaks.

And yeah I know Microsoft isn't cool where you're from. You know, that place where people love to look down on those who get shit done. Concealing their own inadequacy with a thin layer of bitter misguided elitism. Oh glorious patrician, teach me your ways of writing shit-tier useless programs that serve no other purpose than impressing similarly misguided fools. Let's write a Scheme!

>>7
sure, PLENTY of jobs, ... perhaps an unpaid internship at Galois?

>>11
Nice dubs

>>11
Just try Antibutthurtine, it's affordable, good-smelling ointment that will take away all the pain in your sphincter and return you the joys of life without butthurt.

>>13

Does it feels good on the butt?

>>14
Yes, it causes lots of le good feels on the btut.

More laughs from Haskell idiots:

Looking for a purely functional replacement for mutable vectors, but all are at least 100 times slower. Any alternative?

>>16
Hey guys, I lopped off my feet with an axe. But now it's difficult for me to walk. Any alternatives?

Metasepi Project needs donations on bitcoin.

Metasepi team meeting #19 ‒ October 19, 2014
ATS application on Arduino Uno
ATS2 internal overview ‒ September 14, 2014
First trying to read source code of ATS2 compiler.

Subprojects

Japan ATS User Group translates documents about ATS language into Japanese

Look how productive they are:

(UnderConstruction) ATS2 internal overview
Posted on September 14, 2014 / Tags: ats, internal, compiler
Table of contents

Call graph

Call graph

pats_main.dats:main
=> pats_filename.dats:the_prepathlst_push
=> pats_trans1_env.dats:the_trans1_env_initialize
=> pats_trans2_env.dats:the_trans2_env_initialize
=> pats_comarg.dats:comarglst_parse
=> pats_comarg.dats:process_ATSPKGRELOCROOT
=> pats_main.dats:process_cmdline
=> pats_main.dats:process_cmdline2

This is the entirety of what they understood in the ATS2 compiler. Now writing an operating system kernel in it should be a piece of cake... just bring those donations in.