4 ms·

"There are probably a lot of 9-5ers who could have that switch flipped and go from code monkey to craftsmen, but they are stuck doing WebForms and have never re

"There are probably a lot of 9-5ers who could have that switch flipped and go from code monkey to craftsmen, but they are stuck doing WebForms and have never really got bitten by the curiosity bug" That's disingenuous bullshit. Hackers start a lot earlier than "fresh out of college". Disinterested coders aren't lost souls led astray by the ways of .Net, they're disinterested coders; they'd write Ruby with just as little interest. "in the face of the stale joyless Microsoft platform." Thanks for making it worse. The .Net community does labor under the illness/weight of the 9-5 couldn't-care-less crowd, but to turn a community problem into a gross stereotype of the framework only serves to demonstrate your unfamiliarity with .Net. .Net is a rock solid, cool as hell and dynamic/evolving platform. .Net is steered with a much heavier hand than most frameworks, but it makes huge, deliberate moves of evolution (Linq, var/dynamic, PLinq, IronPython/IronRuby/F#, constantly-evolving-C#-syntax).

jcromartie 16y ago
LINQ to SQL was killed. IronRuby is terrible. Constantly evolving C# syntax is not inherently a good thing.
- contextfree 16y ago
  LINQ isn't the same as LINQ to SQL, which is an ORM written on top of the LINQ interfaces. Other ORMs like Entity Framework also use the LINQ interfaces.
- troygoode 16y ago
  As contextfree says, Linq2Sql is an ORM and Linq is really a set of a few technologies (expression trees, lambdas, anonymous types) originally created FOR Linq2Sql but now used all over the place. An example of non-L2S use of Linq to sort an array of objects: //array of dogs var dogs = new[]{ new Dog{Name = "Bowser", Age = 1, Gender = "M"}, new Dog{Name = "Yoshi", Age = 2, Gender = "M"}, new Dog{Name = "Molly", Age = 2, Gender = "F"} }; //get all male dogs ordered from oldest to youngest var dogs2 = dogs.Where(dog=> dog.Gender == "M").OrderByDescending(dog=> dog.Age); No database access involved.
- sofuture 16y ago
  C# is evolving, it's not just randomly, breaking-ly changing. It is a good thing.
Tamerlin 16y ago
I agree -- there are a lot of disinterested 9-5ers who are burned out by their environment, not the technology.

jcromartie 16y ago

LINQ to SQL was killed. IronRuby is terrible. Constantly evolving C# syntax is not inherently a good thing.

contextfree 16y ago
LINQ isn't the same as LINQ to SQL, which is an ORM written on top of the LINQ interfaces. Other ORMs like Entity Framework also use the LINQ interfaces.
troygoode 16y ago
As contextfree says, Linq2Sql is an ORM and Linq is really a set of a few technologies (expression trees, lambdas, anonymous types) originally created FOR Linq2Sql but now used all over the place. An example of non-L2S use of Linq to sort an array of objects: //array of dogs var dogs = new[]{ new Dog{Name = "Bowser", Age = 1, Gender = "M"}, new Dog{Name = "Yoshi", Age = 2, Gender = "M"}, new Dog{Name = "Molly", Age = 2, Gender = "F"} }; //get all male dogs ordered from oldest to youngest var dogs2 = dogs.Where(dog=> dog.Gender == "M").OrderByDescending(dog=> dog.Age); No database access involved.
sofuture 16y ago
C# is evolving, it's not just randomly, breaking-ly changing. It is a good thing.

Tamerlin 16y ago

I agree -- there are a lot of disinterested 9-5ers who are burned out by their environment, not the technology.