Slashdot Mirror

>> Dumb fucking neckbeards.
> Ah! Smart abstinent prepubescents!

Nah, he's just bitter he can't grow a beard like all the important computer scientists can ;-)

http://www.codethinked.com/the-programmer-dress-code
http://www.codethinked.com/The-Programmer-Dress-Code---Part-Deux
http://entertainment.slashdot.org/story/08/04/29/181249/facial-hair-and-computer-languages

>> Dumb fucking neckbeards.
> Ah! Smart abstinent prepubescents!

Nah, he's just bitter he can't grow a beard like all the important computer scientists can ;-)

http://www.codethinked.com/the-programmer-dress-code
http://www.codethinked.com/The-Programmer-Dress-Code---Part-Deux
http://entertainment.slashdot.org/story/08/04/29/181249/facial-hair-and-computer-languages

the unsafe delegates

As I understand correctly, C# delegates are only signature-safe. So the delegates are "safe" as Pythons functions if they follow the method signature. But from a strongly typed language I expect "safe" to mean "type-safe" not "signature-safe". So for example you have the following code:

// C# delegate void Fire(double, double);
...
public Fire fire;

// Java
interface MissleLauncher { void fire(double, double); }
interface FireIgnator { void fire(double, double); }
...
public FireIgnator ignator;

In C# code, fire can mean different things in different contexts. You can assign fire everything, it just have to meet the method signature. But for ignator you can assign only a FireIgnator.

Not sure what's clumsy about it

It's just so many { and } in C# (4 levels of braces):

namespace foo {
class Foo {
public int Xx {
get { }
set { }
}
}
}

Other language have solved that problem in a more elegant way, for example Groovy:

class Foo {
def xxx // automatic setter and getter
def getXxx() { } // override the getter
void setXxx(def foo) { } // override the setter
}
...
Foo foo = new Foo()
foo.xxx = "new value"
println foo.xxx

That there are other issues with C# that I dislike. For example:

• the IXxxx for interfaces. I mean really, what is the point? You shouldn't care less if it's an interface or not, since it's OOP, which means that you should not known which specific implementation you are programming to.
• the 100s (exaggerated a little) of keywords, also see Ten C# Keywords That You Shouldn’t Be Using
• the distinction between class/struct. Optimization should happen without that the programmer should care about. The VM should be intelligent enough to notice when a class it's just value holding record and optimize it. Also see C# Optimization Secrets

• Unless you know more about the C# language than I do, it is typically best to avoid structs entirely. If you use structs, you must be careful to not pass the struct as a parameter to methods often, or performance will degrade to worse than using a class type. The reason for this is that structs are copied in their entirety on each function call or return value.

• namespaces, #region, ref, out, arrays/jagged arrays (why two incompatible array types?)

Now compare him with everyone else - they've all got face hair:
http://www.codethinked.com/post/2007/12/06/The-Programmer-Dress-Code.aspx Edsger Dijkstra (come on ...), Alan Kay (oop), Bjarne Stroustrup (c++), Brian Kernighan (unix, c), Dennis Ritchie (c), Ken Thompson (unix), John McCarthy (lisp), Richard Stallman (gnu), Steve Wozniak (apple), Larry Wall (perl), Alan Cox (linux kernel), James Gosling (java), Grady Booch (uml), "Maddog" Jon Hall (linux intl), Manuel Blum (cryptography), Robin Milner (ml), Philip Wadler (haskell, xquery), Jaron Lanier (virtual reality), Niklaus Wirth (Euler, Algol W, Pascal, Modula, Modula-2, Oberon), C.A.R. Hoare (quicksort), Robert Tarjan (splay trees), Dan Bricklin (visicalc), Phil Katz (pkzip), Jon Postel (rfc), Larry Ellson (oracle).

Now compare him with everyone else - they've all got face hair:
http://www.codethinked.com/post/2007/12/06/The-Programmer-Dress-Code.aspx Edsger Dijkstra (come on ...), Alan Kay (oop), Bjarne Stroustrup (c++), Brian Kernighan (unix, c), Dennis Ritchie (c), Ken Thompson (unix), John McCarthy (lisp), Richard Stallman (gnu), Steve Wozniak (apple), Larry Wall (perl), Alan Cox (linux kernel), James Gosling (java), Grady Booch (uml), "Maddog" Jon Hall (linux intl), Manuel Blum (cryptography), Robin Milner (ml), Philip Wadler (haskell, xquery), Jaron Lanier (virtual reality), Niklaus Wirth (Euler, Algol W, Pascal, Modula, Modula-2, Oberon), C.A.R. Hoare (quicksort), Robert Tarjan (splay trees), Dan Bricklin (visicalc), Phil Katz (pkzip), Jon Postel (rfc), Larry Ellson (oracle).

Yes, and you'll growa beard.

Growing a beard seems to be important to becoming a famous programmer.

These are examples of what is known as the progammer's dress code:

first
second

I think Woz has the essence of it.

These are examples of what is known as the progammer's dress code:

first
second

I think Woz has the essence of it.

Whatever you do, don't mess with this guy and his beard of respectable size.

If you ever feel overly nerdy when using Linux, just give the men behind the OS a thought and you'll feel much better!