sraybell
HTML5 will be the death of Flash and Silverlight as we know these products today. That doesn't mean the product by name won't exist (think jQuery-esque like platforms for HTML5), it will just change forms.
That's my guess anyways.
Why are people afraid of words?
Also, there are a lot of bold assertions made without any actual, measurable success. This whole list is "because I said so". In other words, "citation needed".
I have no interest in taking it further. This isn't Facebook.
They may not care about their privacy, but I do. The rights of others are also my rights. It's not theirs to squander away so easily.
FYI, I'm 27.
Maybe this is part of the macro problem of communicating to management that isn't necessarily technical (which is a problem in and of itself, because management at some level SHOULD be technical. I've found that if management isn't techy enough when their direct reports are highly technical, you get performance measurement disparity).
This invites all the same problems. There are management styles in play at some groups that seem to think that number of anything is a good measure. It's quantity over quality. If your next release has a "big feature", but a concise implementation, they may wonder why you only generated 20 code files instead of 200. And you're right back to square one again.
This may only apply to certain solutions, too. You mentioned python. I'm curious to see if the same could be applied to C#, or Java. Further, I've found that in some projects, we have Enums.cs, for instance, that contain all our enumeration types in that given Namespace or Pacakge (C# and Java respectively). Maybe they should get their own code file? Maybe not?
I think before you implement a system like this, you have to implement a good design structure. Otherwise, you have no solid adherence. You could easily bloat the count, or undercut it, as necessary.
Ultimately, we need a way to measure performance objectively, without meaningless numbers. I don't have a good solution, and I really don't know if I like yours or not. Hrm.
Thanks for the post, though! Will give me something to chew on while I run my scripts... :-)
That's just my opinion, though.
Look, with some portion of dynamic being usefel everywhere and with the growing demand thereof, it was prudent to add these features. Heck, optionals and named were hotly contested features since 1.0 due to introducing mechanisms that were ultimately not important at the time. It introduces complexity, etc.
Maybe C# should give him a pony, too.
There were many other trumpeted features in C# as well as the framework as a whole.
Thanks!