HNHacker News
TopNewBestAskShowJobs

asdasf

1,190 karma · joined July 18, 2013

submissionscomments
asdasf··on In Defense of Scala. Response to “I Don’t Like Scala”
Odd that you cite Larry Wall given that he thinks haskell is one of the most important languages for any programmer to learn. I always find it weird that people try to use someone famous to support their opinion when that famous person disagrees. Perl lacks a type system because that was what made the most sense for perl. That doesn't mean it makes the most sense period.

>every thought I don't have to think about static types is a thought I can instead think about something I actually care about.

Static types do not add something to think about. You already have to think about what things are. Static types just let the compiler ensure that you didn't make any mistakes. Passing a user object into a function that wants a string isn't suddenly useful because there is no type system giving you an error.

asdasf··on In Defense of Scala. Response to “I Don’t Like Scala”
>whereas in Ruby, Grooy et al you just do something like: complex_object.to_json

So, just like you would in a statically typed language like scala or haskell?

asdasf··on In Defense of Scala. Response to “I Don’t Like Scala”
>I can't back up my absurd claim with an actual argument, so go google some strawmen for me

Really? How does this kind of shit not get downvoted to oblivion?

asdasf··on In Defense of Scala. Response to “I Don’t Like Scala”
>Edward Kmett is a Haskell evangelist

Really? Could you point me to some of his evangelizing? Or did you mean "he uses haskell and is quite happy with it"? Because that isn't the same thing.

>inconsistencies that the average programmer will never even realize exist.

Do you honestly believe that? http://www.youtube.com/watch?v=TS1lpKBMkgg

>Scala that only when you leave it's confines do you realize, shit, I miss

But the very point Edward makes is that you don't give up those things when you leave scala. You only give up those things if you leave scala for something worse. You could leave for something better, keep all those things, and get tons of important things that you also won't realize you are missing until you get used to them and then try to live without them.

asdasf··on In Defense of Scala. Response to “I Don’t Like Scala”
>I think the general POV the OP is trying to convey is that Scalaz is an incomprehensible cluster fuck of symbols to everyone but those in the know

Right, I get that there are lots of scala people who are very anti-intellectual and are vehemently opposed to learning anything. But what I don't get is how "if I don't learn this stuff, I don't understand it" is "snobbism" on the part of people providing the library you didn't learn.

>and historically the response to beginner questions has been something along the lines of, "go read this paper" a la Haskell.

I have not seen that response in either scalaz or haskell. It sounds an awful lot like the common strawman used to dismiss haskell as "academic" from people who have never bothered to try it. Practical experience with haskell in particular has been that people are ridiculously accommodating and helpful.

asdasf··on Where should I start learning Assembly?
You have to know assembly to be able to understand what you are looking at. Yes, you need to know more than just assembly, but you absolutely need to know assembly.
asdasf··on In Defense of Scala. Response to “I Don’t Like Scala”
That's a pretty terrible defense of scala. Sounds more like a "I hate some random scala projects for made up reasons". How does scalaz have "colossal snobbism" exactly? Because it contains stuff you haven't learned?
asdasf··on Why do dynamic languages make it more difficult to maintain large codebases?
I don't think so. We are talking about haskell after all, not haskell + experimental ghc extensions. And which popular extensions break type inference anyways?
asdasf··on Why do dynamic languages make it more difficult to maintain large codebases?
Who does that? Dynamic type systems don't actually exist, it is simply a lack of a static type system. Nobody argues about dynamic type systems, they argue about whether or not to have a static type system.
asdasf··on Why do dynamic languages make it more difficult to maintain large codebases?
No. Discussing what static type systems do means discussing what static type systems do. Not pretending static type systems can't do anything java doesn't do. We don't judge dynamic typing by how shitty PHP is for the same reason. Dynamic typing is not what made PHP shitty, it just happens to be both dynamically typed and shitty.
asdasf··on Why do dynamic languages make it more difficult to maintain large codebases?
That is an argument against particular languages that happen to be statically typed. That is not an argument against static typing, which requires nothing of the sort.
asdasf··on Why do dynamic languages make it more difficult to maintain large codebases?
The compiler can already infer all the types anyways, you don't need to declare types. It is considered good practice (and -Wall warns for it) to provide types for top level definitions, as they are usually important enough to warrant this form of machine checked documentation.

note: Yes I know the compiler can't actually infer all types all the time, but the exceptions are obvious and require type information in dynamically typed languages too (ie. convert a string to an int: you have to tell it you want an int, you can't just say "convert this string" and have it guess what you want it converted to).

asdasf··on Why do dynamic languages make it more difficult to maintain large codebases?
Maybe 100K LOC in a static language is more difficult to maintain than 100K LOC in a dynamically typed language, but what if the same functionality requires 500K LOC in the dynamically typed language?
asdasf··on Why do dynamic languages make it more difficult to maintain large codebases?
How very dishonest of you. It actually boils down to "a bunch of common languages do it right, so use one of those instead of java".
asdasf··on Why do dynamic languages make it more difficult to maintain large codebases?
>in which I make the rather obvious point that all the scaffolding you have to erect in statically typed languages

You mean "in which I pose the rather obvious strawman". What scaffolding? What is this mysterious "extra stuff" people give vague names like "scaffolding" to that I've never encountered despite programming in a statically typed language all the time?

asdasf··on Richard Stallman - Re: clang vs free software
You are just repeating the same old red herring. Actually free software does not restrict anyone's freedom. I understand GNU/communists are insane, it is not a problem of understanding, but one of dishonesty. Pretending public domain software (actually free) restricts "end users" freedom is a lie.
asdasf··on How Real is ‘Her’? Artificial Intelligence Experts Weigh In
You have to consider everything he says through the lens of "Stephen Wolfram is crazy".
asdasf··on Ask HN: cheap ways to host your own email server?
apt-get install postfix openldap dovecot

I really don't know what the deal is with email, but since the mid 90s there's been this weird thing where everyone wants to follow some kind of step by step guide. But it is just simple software like anything else. If you can setup a webserver or a database server or anything else you can setup a mail server.

asdasf··on Ask HN: cheap ways to host your own email server?
If you are going to say "that's not true at all" you need to present an argument for why I am wrong. You posted something completely irrelevant, and a couple of exploits. There are security vulnerabilities found in all kinds of software, so what?
asdasf··on Ask HN: cheap ways to host your own email server?
Where do people get these misguided notions about email? You don't need dkim or spf at all, few people check either, and they are just to prevent backscatter. Running your own mail server is trivially easy.
asdasf··on Richard Stallman - Re: clang vs free software
>The people who campaign for GPL software authors to change their license seem to assume that the authors of the software naively chose the GPL, as opposed to choosing it for its particular spirit.

Many do. Any many of them realize they didn't actually want the GPL, they just picked the license they had heard of the most. I don't see what this has to do with the discussion of gcc being limited technically because the GPL is not enough to sufficiently hinder people from writing proprietary tools.

>That's really important distinction that people don't realize about the GPL - it's designed to protect the rights of the END USERS

That is an artificial distinction created to try to justify the newspeak meaning of "freedom" where it is defined to mean "imposes restrictions". Developers are users.

asdasf··on React: Finally, a great server/client web stack
If you have to pose a really terrible strawman to argue for client side templates, you are basically conceding the argument. It is even worse given that moving it to the client doesn't change anything you complained about.
asdasf··on Facebook may lose 80% of users by 2017, say Princeton researchers
>Nonetheless, we can fairly argue that both hypotheses lack a firm grounding in the evidence.

Then make that argument. Because just saying "I don't like it" over and over is not making any such argument.

asdasf··on Clang and FSF's strategy
>Well, strictly speaking, neither one of us can be sure what would happen

We could certainly look at the hundreds of projects setting precedent to determine that you are almost certainly wrong.

>Is it “FUD” if I still really believe it?

Yes. If you are posting something to create fear, uncertainty and doubt, then it is FUD. Even if you are sincerely crazy, it doesn't make your FUD not be FUD.

>but I have the feeling of Google, Apple, and the rest of the permissive license promulgators

Google are not "permissive license promulgators". And you wouldn't be having this conversation if not for actually free software, like freebsd, apache, bind, etc. The people who made the internet are the "permissive license promulgators". Show some fucking respect.

>And one fine day they will turn off the freedom and turn it all proprietary

And see a therapist. You are paranoid and delusional.

asdasf··on Clang and FSF's strategy
The apple employees working on it are the minority, that is the point. If apple decided to have their employees work on a closed source fork, they would have less than 25% of the current developers of LLVM/clang working on their compiler. LLVM/clang would still have the other 75%+.
asdasf··on Clang and FSF's strategy
Why would you post an outright lie like that? Anyone can read the discussion and see multiple mailing list postings from RMS himself confirming the "conspiracy theory" is in fact reality. Quite an odd concept of debunking.
asdasf··on Clang and FSF's strategy
The open one would stagnate because it has over 3 times as many developers, writing over 3 times as much code? You seriously think that?
asdasf··on Clang and FSF's strategy
No, it is not still true. It was never true. It is pure FUD. Apple has absolutely no way to "close the development" of llvm. Why do GPL zealots still post such crappy FUD even when MIT/BSD/apache/ISC licensed projects make up a massive portion of the infrastructure of the net, and no magical closing has ever managed to cause any problems at all?
asdasf··on Clang and FSF's strategy
https://lists.gnu.org/archive/html/emacs-devel/2012-12/msg00...

RMS says "freedom" is worth sacrificing functionality for. GCC is a monolithic mess of shit that is virtually impossible to debug, and produces incorrect code very frequently. Being forced into a terrible architecture where everything is smushed into everything else just to prevent people from being able to use gcc as a front end and something else as a backend is absolutely a case of making the code worse for the sake of trying to further a political agenda.

asdasf··on Clang and FSF's strategy
You are the one conflating the technical and political. This has little to do with licenses. GCC is written poorly on purpose in order to make it difficult to work with gcc. They do not want gcc to be used as a typical unix tool, doing some task and then having the output piped to some other tool to do some other task. They want you to have to directly extend gcc to add whatever functionality you want, this way you would have to make your functionality GPL. The consequence of this moronic decision is that gcc is an absolute nightmare to work on, is full of bugs that are very hard to isolate, and is being abandoned by everyone sane in favor of clang.
← PreviousPage 2 of 20Next →