- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
TRWTF is misspelling BorderColorSet as BorderColourSet
Admin
And now potentially ANY control have its border changed even if it is not a TextBox, RadioButtonList, DropDownList, CheckBox nor the newly added Button!! =D
Admin
But, but, but ...
The real reason for the function was to alias the
Control.Colorproperty to the correct spelling: Colour. Whilst an understandable and perhaps even honourable intention on the part of the dev, this sort of behaviour is the thing which colours a manager's cheeks, giving the code a flavour all its own. The dev should be cashiered most urgently, being told to waste no time putting his belongings in the boot before screeching his tyres right out of the car park and onto the motorway to redundancy.;)
Admin
WebForms is TRWTF
Admin
It's fashionable to bash it now that every front-end developer is a web developer. However I think it's really underrated for people who want to knock up a quick form filling app for departmental use (the type of thing you'd previously use access or Visual Basic for) without having to learn 2 different programming models and languages, or really understand how HTTP works at all.
I think the mistake MS made was in making this the main (and initially only mechanism) for developing web apps in ASP.NET.
Admin
I was afraid that the WTF would be, that assigning a property causes a client-server round-trip, but it seems like it wasn't that bad at least.
Admin
I have to disagree though. I worked in WebForms starting with .NET 1.1, and even then I knew it was an entirely inappropriate metaphor: trying to make web programming look like stateful applications in an inherently stateless environment. It also promoted far too much mixing of presentation and logic, and we’re still paying for the price for that today in complex applications that are difficult to change or modernize. I fully understand why Microsoft invented it, but I think it was the wrong approach.
Admin
I'm a personal fan how the developer thought it's really important to ToString() a string before using it in the switch statement. And I'm pretty sure they didn't even know why the reference type string works but not System.Type. Glorious.
Admin
ASP.Net WebForms was invented when server programmability on every platform was in its infancy, ASP was a hot mess of blended server-side code and client-side presentation layer, and desktop development was what 90+% of all Microsoft-stack developers knew.
Easy to forget how long it took for the split serside / clientside development paradigm to settle down. Arguably it still isn't settled. Had the Model View Controller idea been a couple years earlier that might have ruled the day instead of WebForms.
Admin
"Had the Model View Controller idea been a couple years earlier that might have ruled the day instead of WebForms."
You mean a few years earlier than 1979? https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller
Admin
I can understand wanting to use "colour" instead of "color" - what kills me is function names like "SendEmial" that I am never going to find without extra effort. Do I create and merge branches just to fix typos? Yes, frequently, for the sanity of those who inherit the codebase.
Admin
The real WTF is that after all this time there still is no better way to develop for web, without craptastic javascript, the hot mess that is CSS and the HTML ever moving standard. Nobody sane want's to touch that shit. And look, how the web went down the drain because of this. Instead of getting rid of that crap, we've now got framework after framework, you can't trust things to work or be supported after half a year, and idiots even try to drag that mess onto servers and local to clients. Such an epic waste of performance and memory.
Admin
Not everyone lives in the USA...
Admin
Actually "colour" is the real spelling. "Color" is the typo, originating from the wrong side of the big pond.
Admin
It's not a typo.
The term typo refers to an error caused by either a mistake made in honesty or perhaps a momentary lapse in judgment, concentration, attention or skill. All traits which are conspicuously absent in the population of dastardly settler colonials that fled and keep fleeing the shores of the civilized continent of Eurasia in an attempt to escape the lack of success in life caused by their own inadequacies which they, predictably enough, blame on their environment instead. As is the way of such people.
No, the many inaccuracies in spelling, terminology and speech in general exhibited by the inhabitants of the descendants of the american rebellion is in fact a conscious and malicious act of revolt against the English language and the European, and in particular British culture that it represents. Britain, it must be remembered, having been not just the direct opponent of their movement but also the dominant hegemonic superpower of the world at the time of the rebellion and thus the generic representative of the old world.
Thus the "american" language, if it can be called such, is a direct and overt mechanism by which the wayward colonials seek to create and continually reinforce their otherness from the old "civilized" world as part of their continual and permanent desire to prove to them self and anyone who would listen (pun intended) that their individual failures to succeed in their places of birth were caused in no part by their own individual inadequacies and failures but entirely by the world it self.
This coping process continues to this day and can most easily be observed in the various neo and paleo far-left movements dominating the modern political landscape of that nation as well as the entirety of the overly entitled Z and Alpha generations.
Continued in part 2.
/ The above post contains text that is not meant to be taken entirely seriously. Even if it is based on a moderate degree of truth to make you think. But the presentation style is for fun.
Admin
Part 2:
It should be noted that such actions when pertaining to language are neither new nor unique to the north american rebels. Indeed, the process of deliberate and aggressive language separation is one of the primary means of differentiation seen in newly created breakaway societies throughout human history.
One excellent example of this being the Balkans and in particular the territories formerly comprising the nation of Yugoslavia. That region which within living memory was dominated by a single unified language called Serbo-Croatian now hosts a number of languages (Serbian, Croatian, Bosnian, Macedonian versions of both and most recently Montenegrin) all of which, I have been lead to believe are rapidly becoming mutually unintelligible entirely through overt efforts of the people and their national governments.
This it is very ironic that in their ultimate act of spiteful rebellion against the "old" world the american colonials are in fact embracing one of its oldest and proudest traditions. That of talking differently in attempt to prove you are different.
/ The above post contains text that is not meant to be taken entirely seriously. Even if it is based on a moderate degree of truth to make you think. But the presentation style is for fun.
PS. For some reason I imagine this being read in the voice of Christopher Hitchens.
Admin
Ironically, a lot of American accents are more historically British sounding than the modern RP. But also, the extraneous "u"s in a lot of British spellings are things Middle English inherited from Middle French, so arguably, the Americans are being more British than the British by sneering at the continentals.
Wait, no, there's nothing more British than obstinately clinging to tradition for no reason other than being able to sneer at someone for not doing it.
Admin
What some people here don't seem to realize is that English, like many other languages, has various dialects, and like other language families, developed vast distances apart (most often with an ocean in-between.) British, Canadian, American, Australian, and others all evolved separately and have many differences from one another.
I submit that no one dialect can claim dominion over the "English" language as a broad whole, not even the English people given how much of a moving target of influences it had been over the past millennium making it probably one of the least stable of languages historically.