You are viewing a single comment's thread.

view the rest of the comments →

0
0

[–] 16442934? ago 

Yes, that is what productive means. Writing software to solve a problem, rather than writing software to get a pay check. If you want to do anything embedded, low level or resource constrained you need to know C and/or asm. In order to interface with most libraries which are written in C and expose a C API, you need to know C to wrap it in another language, like haskell. For anything else use haskell. Examples:

I want to buy a cheap embedded board and have it automatically open my chicken coop door in the morning

This is productive, and embedded. You have no choice but C or asm. So learn them.

I want to write a database app to keep track of breeding my chickens and the resulting quality

This is productive and not embedded. Learn haskell.

I want to live in a closet in San Fagcisco and do all the work for low pay while diversity hires get all the credit

This is not productive. Learn a soy language.

If you just want to be a wagecuck, learn whatever the most popular thing is at the time and place you want to wagecuck in, because the goal is not software it is money, so it doesn't matter how shitty the software you work on is all that matters is your chances of getting hired.

0
0

[–] 16442938? ago 

I'm not just here to shit on you for telling everyone to use haskell and nothing else. I was considering it today; my xmonad config is pathetic because I don't know the language. I was thinking about wasting an hour making it better, but I had to go back to working on webdev for my job. I'll eventually learn haskell properly, but it's been six years and I haven't bothered to do it, even when I attempted to while unemployed. But you're pretending like runtime efficiency and "no errors ever" marketing of haskell outweighs the ease of use, simple syntax, and wealth of libraries I'd get by using anything else instead. Just stop doing that, and we'll agree on most things here.

0
0

[–] 16442946? ago 

I didn't say haskell was easy to learn, I said it is the best high level language to learn to do productive computing. Haskell has a very simple syntax, and tons of libraries, many of which are completely beyond anything available in shit languages. There is no parsec or pipes for python. But haskell is difficult to learn, and it is made even more so because you got jewed. Kikes taught you a broken language as your first language, and this instilled in you expectations that haskell violates. This makes it even harder to learn, because you have to unlearn what you already learned. It sucks I know, I went through that too. It is unfortunate that technology is so heavily corrupted by (((billionaire corporate interests))), but they want you using lowest common denominator shit so you can be easily replaced with pajeets, and they hope to replace those pajeets with someone even dumber if they can get gorillas or niggers to be able to work a keyboard.

Note that I am also not saying haskell is the only language that doesn't suck, but there's no reason to learn something like sml over haskell, and the languages that are above haskell like idris are still works in progress. But if idris displaces haskell you'll have no problem learning it if you know haskell. And the other likely option is haskell ends up with full dependent types before idris is ready, and then everyone just sticks to haskell anyways.

0
0

[–] 16442940? ago 

runtime efficiency being that it is compiled and implying nothing else.