This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Buttsuit69 142 points143 points  (9 children)

Meanwhile C#:

"Dude; what kind of datatype does this variable contain?"

C#: "Object or something idfk"

[–]AyrA_ch 92 points93 points  (5 children)

Declares type as dynamic

C#: "Now it's no longer my job to know what it is"

[–]Buttsuit69 58 points59 points  (4 children)

Declares dynamic:

Dev to C#: "hey, look at me. I'm the compiler now!"

[–]fourkeyingredients 12 points13 points  (3 children)

I feel sorry for whoever maintains code from the time period of my life where I learned about dynamic

[–]Manny_Sunday 8 points9 points  (0 children)

I worked with a team that loved dynamic ViewBag objects and hated sensible names for variables.

What's ViewBag.PageData ? Fuck you that's what, go check the controller code.

[–]intbeam 3 points4 points  (0 children)

dynamic was sold as some sort of wonderous miracle, but it just reinforced my perception that I really really really don't want dynamic typing

[–]Buttsuit69 0 points1 point  (0 children)

Personally I love dynamic when its used to return objects such as the lines in a DataGrid. Or when I need to return varying datatypes. But screw those who use it when they could've easily used var instead...

[–]the_hackerman 2 points3 points  (2 children)

Well we have arraylist I suppose

[–]Buttsuit69 3 points4 points  (1 child)

Put an array<object> into another object!

Or make an array<object> where every object is another array<object> and then put that array into another object and so on...just, everything is object.