Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

A Vote!

Name: Anonymous 2013-11-29 5:55

I saw we ban the following programming languages:


Javascript
Ruby


from this board for the purpose of being too shitty.

Name: Anonymous 2013-11-29 9:34

I agree.

Name: Anonymous 2013-11-29 17:40

I concur, but why stop there?

Name: Anonymous 2013-11-29 20:44

Let's ban PHP as well. It's an objectively bad language which is completely replaceable.

Sepples can't be banned because it doesn't have a popular replacement that isn't slow as balls.
Perl can't be banned because it's okay for some sysadmin (and doing so would leave us with fucking bash, or rather, bashit).

Name: Anonymous 2013-11-29 23:04

Why do people like dynamic typing?

What is the justification for dynamic types?
Please, convert me, /anus/-sama

Name: Anonymous 2013-11-30 1:35

>>5
You save some keystrokes by not having to write the types.

Those are all the advantages I can think of.

Name: Anonymous 2013-11-30 1:47

>>6

Consider int atoi (const char * str);
It returns 0 on error. Of course, it also returns 0 when that's the correct number to return. And so we have no real way of knowing if the function failed. With dynamic typing, we can have the function return "error", nil or some equivalent value. Of course, there are work around to this problem, like checking the type of the string before hand, but you can't deny that there are advantages like this to dynamic typing.

Also I'm against dynamic typing.

Name: Anonymous 2013-11-30 2:30

>>7
You'll know 0 is the correct number and not an error signal because you passed the string "0" to it.

Name: Anonymous 2013-11-30 2:44

>>4
[Sepples] doesn't have a replacement that isn't slow as balls.
What about D?

Name: Anonymous 2013-11-30 3:14

>>8
Uhhh no, I passed a character array and I have no fucking clue what was in it.

If you're saying I should have checked if it was "0", I would also have to check for 0E0, +0E0, 0E+0, etc.

Name: Anonymous 2013-11-30 7:48

>>7
Maybe it returns a Maybe Int?

Name: Anonymous 2013-11-30 15:22

>>9
I forgot about it.

Ban Sepples.

Name: Anonymous 2013-11-30 16:37

>>11
That's just a functional abstraction around returning two values, one of which is an error code.

Name: Anonymous 2013-11-30 16:46

First they came for Javashit. And I did not speak up because I was not a subhuman web developer.
Next they came for Ruby. And I said ``Hey guys, you need any help?''

Name: Anonymous 2013-11-30 20:06

>>14
Excellent post, I love you.

Name: Anonymous 2013-11-30 23:14

>>13
No sir, that's a concrete type motherfucker.

Name: Anonymous 2013-12-02 3:48

>>16
Maybe may be concrete, but away from an abstract standing, in the abstract machine (that is to say the concrete) it may be represented as (errcode, ret).

Name: Anonymous 2013-12-02 5:40

>>1
for the purpose of being too [b][i]shitty[/i][/b]
It really should be ``for the reason of being too shitty''.

Name: Anonymous 2013-12-02 8:04

I'm working on an authentication protocol similar to CHAP but using openpgp digital signatures and implementing it on a chrome extension using openpgpjs/sjcl
i am fucking tired about using passwords or pseudo-decentralized protocols like oauth.

passwords are only useful for encryption, period

Name: Anonymous 2013-12-03 2:44

>>5

the standard argument is that a static type system necessarily rejects some programs that would be otherwise run normally. and that type systems are never "good enough," since working with dynamic types is better than working with a shitty type system

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List