Software Fashion 477
fedor writes "Software fashions come and go, but they always claim a few victims on the way. Where there's fashion, you'll find that rather weak willed person who is the Stupid Fashion Victim (or the SFV for short).
This great article from Software Reality is all about fashion in software. Do you all remember WAP? In a couple of years some of the current 'technologies' will be gone too. The article mentions VB.NET, struts and XP as current fashion..."
WAP fashionable? (Score:2)
Text only? Feeble baud rates? Unable to read standard sites? Pur-lease...
Re:WAP fashionable? (Score:5, Interesting)
There's lots of useful content that can fit within WAPs limitations, and it's a snap to do. I blame the low acceptance on content creators who are not taking the tiny bit of time needed to make WML versions of their sites.
Until the content is there, it can't become very popular in the mainstream.
Re:WAP fashionable? (Score:2)
If only Verizon would get some decent data plans and bluetooth
Re:WAP fashionable? (Score:3, Interesting)
Re:WAP fashionable? (Score:3, Funny)
Yikes! I can't imagine that screen size is useful unless you're into midget sex.
I get better resolution out of the memories of pr0n in my head than you probably get on that damn phone.
Besides, who's holding the phone for you while you're...umm...
Re:WAP fashionable? (Score:2)
It's nice to see it die.
I wonder... (Score:5, Funny)
YIKES!!! (Score:2, Funny)
Whats next? A front page story post with the goatse guy?
Re:YIKES!!! (Score:2, Funny)
Re:YIKES!!! (Score:5, Funny)
Whats next? A front page story post with the goatse guy?
I've been submitting those, but for some reason, they keep getting rejected.
Re:YIKES!!! (Score:3, Funny)
Re:YIKES!!! (Score:3, Funny)
Re:YIKES!!! (Score:3, Funny)
Or, she could climb in goatse guy.
Re:YIKES!!! (Score:5, Funny)
Or, she could climb in goatse guy.
If she did both at the same time, you'd have a wicked MC Escher drawing.
LOL, Struts is right on target. (Score:3, Insightful)
Rick
Re:LOL, Struts is right on target. (Score:5, Informative)
I will definitely agree that the learning curve for struts is quite steep and the number of files involved per user action is high (1 form bean, 1 action, 1 jsp, 1 xml config file, 1 property file, possibly 1 xml validation file) but there are some IDEs which help out in some cases. The problems are incredibly similar to most MVC frameworks. Using modular design leads to more complex code, its a fact of life.
Struts is certainly not the end all and be all but its better for medium to large projects than the alternatives I've looked at (caveat: I have not investigated JSF which someone mentioned)
Re:LOL, Struts is right on target. (Score:4, Interesting)
Now I'll admit that there are some areas of
Re:LOL, Struts is right on target. (Score:4, Insightful)
If modularization begets complexity, you ain't doin' it right.
Modularization should simplify, in that each module encapsulates and abstracts a well-definined function. It may add volume to your code, but should render it easier to work with.
Re:LOL, Struts is right on target. (Score:3, Insightful)
The whole _problem_ is that software projects are becoming more and more complex each year, and thus more likely to fail if tackled in the wrong fashion. (Even if they don't fail the first time around, they fail when someone has to maintain them. Whenever a whole enterprise system gets scrapped and r
Soapbox (Score:3, Funny)
Victim? (Score:3, Funny)
That's my mother you insensitive clod.
Re:Interesting? (Score:5, Insightful)
Re:Interesting? (Score:2)
They hold up the models.
Let's vote for the greatest forgotten... (Score:2, Troll)
My vote is the
Runner-up: The adventure games a'la Sierra's.
Re:Let's vote for the greatest forgotten... (Score:4, Interesting)
On the other hand one must ask whether programming in C# really is better than doing RAD in C++ Builder or even (ugh) Delphi.
Also, while it may be a "fad" at the moment, we should remember that Java was as well for a long time. Yet Java definitely made it past the fad moment. With C# this is even more likely since it seems like Microsoft will be making Windows more and more dependent upon .NET whether we like it or not. Thus calling it a "fad" seems difficult, despite all the exaggerated hype.
Re:Let's vote for the greatest forgotten... (Score:2)
Re:Let's vote for the greatest forgotten... (Score:2, Insightful)
I suggest you get off the bandwagon and do a little of your own thinking...
p.s. Stop making me defend Microsoft, you insensative clods!
Linux fashion. (Score:2, Insightful)
First it was Slackware, then Debian and now Gentoo. Now that Debian has lost around 90% of its market share it is being left out to dry with its anceint packages and deprecated
Whats next? Ive recently seen a rise in Mandrake cooker users, as they provide the ultimate in ease of use combined with the power.
Re:Linux fashion. (Score:2)
Re:Linux fashion. (Score:3, Insightful)
I'd liken Red Hat to a business suit; not really practical for rolling your sleeves up and getting dirty, but still required by staid corporate types everywhere. Odd how that tallies with its prime marketplace... ;)
Re:Linux fashion. (should be titled flamebait) (Score:3, Interesting)
I am actually not sure why Gentoo is so popular right now.. I use it, but I have kind of specific reasons for using it (four-node openmosix cluster of boxes that need to be identical and so upgrades are cron'd to go off at the same time)..
For the average user not really needing to sit and fiddle around with make.conf and funky masked ebuilds I would not recommend it, Mandrake is nice for home systems where you have a ton of stuff plugged into the box and need something quick that just plain
Re:Linux fashion. (Score:2)
"Use the source Luke...."
Re:Linux fashion. (Score:3, Interesting)
The Debian package format is not deprecated, when I first started using it APT was far superior to RPM, although RPM has gained ground since then.
If you don't want "ancient" packages upgrade to testing or unstable
Microsoft Bob will never go out of fashion. (Score:3, Funny)
Re:Microsoft Bob will never go out of fashion. (Score:2)
Re:Microsoft Bob will never go out of fashion. (Score:2)
I was a beta tester for Windows 95, and remember folks calling it "Bob Pro"....
Re:Microsoft Bob will never go out of fashion. (Score:3, Funny)
I was a beta tester for 3.11. Then I upgraded to being a beta tester for Windows 95. After that came NT, then 98, then 2000. I'm happy beta testing 2000, and have no inclination toward joining the XP beta test group...
The one i hate most (Score:4, Insightful)
Re:The one i hate most (Score:2, Insightful)
Most movements like this or XP have their points. It's just that the good is almost overwhelmed by the "let's do it just because." People get caught up in the title rather than the content. This is exactly what leads to the dreaded "checklist bloat" of most p
Re:The one i hate most (Score:3, Insightful)
I have not seen an IDE which makes it as painless to deduce a variables type quickly as hungarian notation (once you learn what "sz" "lp", "pI" and so on stands for). When scanning through new code this helps a lot, even if it's not done 100% consistently. Not even tooltips (as VS.NET and several other IDEs has) are quick enough.
I do think such an IDE (or editor, really) could be constructed, perhaps u
Re:The one i hate most (Score:3, Funny)
I'm not sure about "sz", but an "lp" is what I used to put on my parent's stereo, and a "pI" is what you hire when your wife starts wearing six inch stilletto heels when she goes to visit her "friend".
Re:The one i hate most (Score:3, Insightful)
Hungarian Notation is just file extensions in source code -- it will surprise nobody that both terrible creations were midwifed at the same place. It's a bad idea who's time never came. Now that we've moved out of the '70s and have development tools more sophisticated than vi and grep, it's not merely archaic but rather positively prehistoric. Don't fish Hungarian Notation out of history's
Re:The one i hate most (Score:3, Insightful)
Even Charles Simonyi, who started the whole Hungarian Notation thing, didn't propose that it should be used everywhere, for every variable name. This is, as the parent post suggests, a classic case of a valid idea being used in inappropriate contexts just for the sake of fashion. Unfortunately it (or worse still bastardised versions of it) has become so entrenched it is followed more like it is religion than fashion. Some developers can't be talked out of it with any reasoning - they just tell me it has to
Re:The one i hate most (Score:4, Funny)
But, I pointed out, in Perl a variable's type depends on context.
"Huh?" He asked.
"Ok, I read in a number as a string. Then I use it as a number. Then I format it using a regexp. Then I print it as a string. What is it, a number, or a string?
"Use two variables, one integer with an "i" prefix and one string with an "str" prefix." he said.
"Well, now that you're using double the memory to perform the same task, let's consider. How will this scale when we've got thousands, or tens of thousands, of hits?" (this was going to be a CGI app). I crossed my arms and waited.
"Doesn't matter. Use Hungarian Notation. It'll make it easier to read your code."
"But it's fucking stupid."
"No it's not! DO IT!" (and so on, ad infinitum).
I called a friend of mine, who had taught me a lot of my Perl knowledge, and I asked him, point blank, what he thought of all this.
"Your sysadmin's a re-re." He said.
"A what?" I asked.
"A re-re. A retard. Freshen your resume."
And, so I did...
Re:The one i hate most (Score:3, Funny)
The first time I saw Hungarian notation, I didn't know what it was. I wondered why anyone would name variables svStrVar or have type HWND. My initial reaction was that it looked like it was written in Hungarian or something. (Not that I know Hungarian...)
I laughed rather hard when I found out what the name of that notation was.
.NET = Fashion (Score:3, Insightful)
This is why OSS is so great. Most of the time, it's not about the money; it's about the product. Therefore, it's not about getting sales, it's about getting users.
Re:.NET = Fashion (Score:4, Interesting)
But the point is the frameworks. Finally Microsoft have solved the 'framework that sucks' problem by
Dave
Re:.NET = Fashion (Score:3, Insightful)
I believe that in a year or two, when the next "new thing" is introduced, you'll be going, "Yeah, whatever. Who's going to swap from C# to this?"
Shrink-wrap apps (Score:3, Insightful)
Re:.NET = Fashion (Score:3, Interesting)
If you think Java's popularity is a result of it's technical merits, you are dead wrong. It's popular because it was marketed as an anti-bug silver bullet to the powers that be, a bullet that is far enough from C to be bug resistant, and close enough to C that it doesn't require much retraining. I don't think it delievers on
Re:.NET = Fashion (Score:3, Insightful)
Sounds like you don't really know what you are talking about. If you are implying Smalltalk and Python are supersets of Java (as it exists currently), you are just ignorant. Each of 3 languages (or platform, if you wish), has their specific strengths, but claiming Java is inferior of 3 is ridiculous. It may be that when f
What about CORBA? (Score:5, Insightful)
But missed CORBA! Surely it belongs in the Technology X != Silver Bullet category. As far as I'm concerned, CORBA best solves the "this project has too many resources" problem.
But then again, I'm probably just another SFV :-)
Re:What about CORBA? (Score:4, Interesting)
Disclaimer: I'm clearly bigotted [fnorb.org]
However, if you believe CORBA was going to be a silver bullet, then you were mistaken. I've never heard anyone say such a thing. But then, I stay away from marketing people.
As far as I'm concerned, CORBA best solves the "this project has too many resources" problem
I think you actually discovered that "distributed systems are difficult".
What you need is a component infrastructure that builds on CORBA to make the slice of the generic distributed system problem that most people are (currently) interested in a simple problem. Luckily it exists, and it is called J2EE
As for me, J2EE *doesn't* address the kind of problems I'm interested in, so the *only* option is CORBA. (And please, don't talk to me about web services or SOAP
UML (Score:5, Funny)
Re:UML (Score:2, Insightful)
I think their point on patterns is equally valid for UML, or TechnologyX in fact...
UML usage is often seen as an end in itself. Robin (intrepid co-author of this article) was once asked during a job interview: "What's your favourite UML Diagram?" What's the correct response to that? "Oh, Use Case Diagrams every time! Yeah, I use it for everything!"
However I think "Robin" should have read Joel On Software's Guerrilla Guide to Interviewing [joelonsoftware.com] for the 'correct' respons
Everything, including tools, in moderation! (Score:5, Insightful)
If UML and Patterns is making your engineers less intelligible, then they are doing something wrong. It is possible that those tools are not appropriate for your problem space. It is also possible that they need to drop the elements of the model that aren't working for them.
Design Patterns is an incredibly useful tool, especially in the OO world. But as was noted in the article, there is a danger of designing everything as a pattern. Being able to say "I use a Service Locator to look up the remote resources" or "I use this Abstract Factory to get the proper xml parser" is incredibly useful. But it has a tendancy to be overdone.
Everything, including tools, in moderation!
Re: Everything, including tools, in moderation! (Score:3, Interesting)
Design patterns and UML were designed as practical tools, not dogma. If they help you do what you were doing anyway (and they often do), then great: use 'em. But if they don't, then don't. They're there to serve you, not the other way around.
UML is simply a way of describing objects and their relationships; not a way to create those things, just a way to communicate them afterwards. Similarly, design patterns are simply practical examples that have worked for people before; reusing them may
Re: Everything, including tools, in moderation! (Score:4, Interesting)
This is true, but note that the UML/patterns/OO newbie is in no position to determine that. One common mistake is to read the book, discard the parts you don't think is necessary, and then proceed with your design work. The rules that you chose to ignore were put there by pretty smart people, and there's a good chance they were put there for a good reason. When the design finally fails because you were missing something, the egotistical designer then blames the method.
The point is, I think the parent post was suggesting that the programmers in question may simply have broken the rules, and not actually found some instance where the methods really apply poorly. It's ego-boosting to think that what you do is unique and beyond the reach of old stuffy rules, but the truth is that most of us are doing things that have been done before.
This isn't to say that those cases don't exist, but that they're probably rarer than you think, especially if your team of programmers is trying it out for the first time, especially if you don't have a senior engineer already experienced in the method guiding your team. For the first time, at least, the instructions should be followed to the letter and strictly enforced. They should be dogma until you've at least went through a complete product life cycle with them.
What you suggest we've already tried for decades. The result is prevasively poor documentation and fragile designs.
Re:Everything, including tools, in moderation! (Score:2)
I read this on your info page...
Hmm - Enterprise billing software? Australia? Auditor? Could the system go by the name "Power"? Feel free to email me or send me Lotus NotesReading UML (Score:3, Insightful)
I would like very much to have a tool like UML to explain my designs -- I am a very visual/graphical type person. The trouble is that UML has so many kinds of lines, arrow heads, and connector icons that I can't m
Re:"Required" email (Score:4, Insightful)
For absolutely no gain? Yes. There are better ways, such as putting any needed documentation into the source code itself. That way not only are they more accessible when reading the code but they're easier to change and harder to forget about.
Check out doxygen (at sourceforge) for a pretty cool system.
A classic Slashdot post, linked (Score:2)
This perfectly fits a classic reposting of a classic Slashdot post.. let me think, I believe the year was 2001...
REPOST:A classic /. posting on languages as fasion [slashdot.org]
Hmmm... (Score:5, Funny)
Illegal division by zero at line 1.
Memes (Score:5, Interesting)
Richard Dawkins in his book "The selfish gene" introduced a concept of a meme. Meme is a replicator, just like gene, except that it represents an idea. It is copied by us, humans, either verbally or in writing, software, paintings, etc., and so on. Susan Blackmore in her book "The meme machine" expands on the idea.
Now, what does it have to with "Software Fashions". Both Dawkins and Blackmore present well-thought out argument that memes are subject to similar forces as genes. As a consequence, just like in a genetic world you can have outbreaks of viruses, in memetic environment there are outbursts of ideas. Some of them are as much use as a flu virus, and until our minds develop resistance to it, they will spread. Once memetic vaccine has been developed they die out.
Blaming software fashions on SFV is just like blaming flu outbreak on a SVV (stupid virus victim). Note that memetic fashions are common and not restricted to software. From bell-bottoms, through furbies to whatever the latest craze we have now.
Re:Memes (Score:2)
Re:Memes (Score:3, Funny)
I'll be glad when memetics is out of fashion. I'm sick of hearing about it.
Nothing against you personally, but memetic arguments always seem to come off as 1. pretentious 2. absolving oneself of personal responsability 3. a "I have a hammer so everything is a nail" approach. In this case, the hammer is genetics, evolution, and an overblown analogy.
Now, if memetics proves to be a viral idea, does that invalidate memetics or prove it? Quite a paradox, eh? I suppose it's entirely possible for memet
Re:Memes (Score:5, Funny)
Re:Memes (Score:3, Informative)
Blaming software fashions on SFV is just like blaming flu outbreak on a SVV (stupid virus victim).
Not so. The "stupid" part of SFV means something like "susceptible to memetic infection". So in making an analogy with biological viruses, you'll need to change "stupid" to something which connotes susceptibility to viral invasion [bbc.co.uk] (such as sleep deprivation [iowastatedaily.com], old age [mcw.edu] or stress [bbc.co.uk]).
More ignorant flamebait... (Score:5, Insightful)
From the article:
That alone should tell you that the author has no clue as to what they are talking about. I am most definately not a VB.NET fan, but that statement is just false and shows a huge lack of understanding of the .NET Framework.
Re:More ignorant flamebait... (Score:5, Insightful)
They're talking out their asses on the libraries. CLS-compliant is CLS-compliant. But they're dead-on right about VB.NET. I'm pretty sure that Microsoft "upgraded" VB by starting with C#, changing the syntax to match Basic, then dumbing it down with over-verbose keywords for new language features and a lack of "intrinsic" keywords for unsigned integer types. All this for a language so different from previous versions of VB, it needs a non-trivial conversion anyway.
Hmm, instead of making the language easier to use, they just made it different. Syntactic aspartame?
Re:More ignorant flamebait... (Score:3, Interesting)
Right, the author obviously doesn't understand
Having coded in VB6, VB.Net, C++ and C#, I have noticed that VB editors highlight what I think represents the "language" of the future...
(Prepare for Troll or Flamebait mod - Now!)
Intellisense.
As a language, I like C# better than VB.Net, but the line completion and type lookup under VB.Net make it easier to work with. Fewer typos and faster coding are the result. This is obviously tricky to do in languages where whitespace is insignificant, though. I have
Re:More ignorant flamebait... (Score:3, Interesting)
lots of valid points (Score:2, Interesting)
Rational Unified Process has contained roadmaps for XP process variants for over a year. RUPs primary purpose in life now is to keep consultants employed, although there's a ton of good stuff in there. Sorting it from the three tons of crap is why you need a consultant.
VB.net appears to have been largely abandoned by IT, and Microsoft's not far behind. That's good, since it
Some good points, but... (Score:3, Interesting)
Robin [...]was once asked during a job interview: "What's your favourite design pattern?" What's the correct response to that?
I don't think that's such a stupid question, as long as it's interpreted correctly. A good design pattern, like a good algorithm, is likeable in its own right, because of it's elegance and the way it breaks down a complicated problem. Maybe the interviewer wanted to know if Robin was really passionate about programming.
VB.Net is really just syntactic sugar on top of C#. C# offers more and better libraries.
What libraries do C# offer that are not accessible from VB.NET? As far as I know, all C# libraries (at least those in the standard framework) are CLS compliant, and thus accessible from any CLR language.
Because programmers didn't test that much, XP stipulates that tests must be written before the code. In other words, just because something has a weakness you shouldn't do the opposite in an extreme form.
That's just crazy talk. Automated regression tests isn't intended to relieve those lazy programmers, in XP they're the de-facto definition of what the system is designed to. Not to mention that test-first design often leads to better design, in particular wrt coupling between classes and components.
Better yet... (Score:2)
Warning! Above links not work-safe! (Score:2)
Missing the biggest stupid software fashion (Score:5, Insightful)
Unfortunately, unlike other stupid fads applied to software such as TQM, ISO9000, RUP, etc., outsourcing does real economic damage to the victims, (as opposed to just the psychological damage represented by trying to work around the others).
Fashion? Yeah sure. (Score:3, Insightful)
WAP dying out (Score:2)
What the article should really state here is that the WAP technology is dying, but not the idea (browsing the web - walled garden or not).
More evolving and changing than going the way of the Dodo. Although, granted, that's not quite so catchy as "WAP is dead!"
Great - more loaded questions for husbands (Score:2)
Does this tarball make me look fat?
Another fashion (Score:2)
What's wrong with XP? (Score:2)
Relevance to, well, everything (Score:5, Funny)
Fortunately, we here in the business world don't have the same 'fashion trends' problem you software blokes seem to suffer.
The very worst fashion... (Score:5, Interesting)
The very worst fashion has to be EJBs.
EJBs complicate development. Where a single class would previously have worked just fine, EJB requires up to seven (!) classes to define things like the Remote Interface, Remote Home Interface, etc. And where a simple constructor would previously have served, EJB requires a long JNDI call. Not to mention, there are zillions of arbitrary coding restrictions that must be memorized and followed for EJB to work properly.
Furthermore, EJBs drastically impair performance. The "shopping cart" demo that comes with a major commercial app server brings my 1GHz 512M machine to its knees. Such a program could otherwise execute quickly on a 286 8MHz, a machine less than 1/1000th as powerful as the one running the EJB. I regularly encounter shops that have huge farms of commodity boxes to run very trivial EJBs that would otherwise execute on a single box just fine.
And EJBs do not scale any better than 2-tiered systems. 2-tiered systems allow you to horizontally scale the business logic by adding commodity machines to the second tier. Adding another tier does not help this at all.
...For this crippling blow to development, you get to pay Bea $40k/developer. Snake oil! Very expensive snake oil!
Software development resembles a foot race between you and your competitors, and using EJB resembles paying a surgeon exorbitant sums to cut off your left leg before the race. It costs craploads of money, it cripples progress, and it hurts!
Re:The very worst fashion... (Score:3, Insightful)
Misuse of EJBs complicate development. When they're used just for the sake of fashion (as often seems to be the case), a perfectly good solution (for something) can be applied to entirely the wrong problem, resulting in a mess. The parent post makes two good points about the danger of fashion (another way of saying following blindly without thinking?); one of these points is perhaps made inadvertantly. Firstly, the results are bad. Secondly, it can make it look as if the subjec
Woah! (Score:2, Funny)
You mean my micro-horse was just a waste of money?
anyways, here is a cool page [sito.org] I found.I nominate XML (Score:4, Insightful)
XML is a fad because the whole concept of universal interchange of data is getting locked down by the big vendors. Theoretically, yes, data in XML is portable, but, so are well documented binary structures and CSV.
To have real interoperability, you have to know how the software uses the data. To get that, you must have open source. Microsoft knows this, and that's why they are pushing XML as the "nirvana" of interoperability.
I'd invite anyone who argues against the above to look at an XMLized Word document...
Re:I nominate XML (Score:3, Insightful)
<record id="35">
<name>Joe Blo</name>
<shoe-size>12</shoe-size>
<favorite-number>10</favorite-number>
</record>
means, while the following:
35,"Joe Blo",12,10
is just a blob of useless data.
I.e. XML helps ME in MY PROGRAMS today. It's not the nirvana of anything, but I sure as hell don't want to switch to CSV.
Favorite quote (Score:3, Insightful)
Well, that sentance pretty much sums up what wrong with the computer industry, doesn't it?
My personal vote for industry flavors of the week (Score:4, Interesting)
Flavors of the week, past & present:
DRM: Right now every big software company is considering it, and many of them will stop using it when they realize just how much it pisses off their customers, and how little it does to reduce piracy.
Push content: How many of you still have a push client on your systems? /me listens for responses, hears nothing but chirping crickets.
.NET is also a flavor of the week that will be yesterday's news once Microsoft force-upgrades their customers to the next flavor of the week.
Cameras in every gadget, starting with cell-phones. Most people don't care enough to use them, don't want to have to check themselves in the mirror every time their phone rings, and have little use for them outside the normal uses that a dedicated camera is usually used for. In the end, it's an expensive gimmick.
Virtual reality. Visions of William Gibson's matrix have danced in the heads of thousands of developers and marketers, but that's not going to happen in real life. The problem is that VR interfaces are far less intuitive than the good old fashioned screen full of windows with a keyboard & mouse. Can you imagine donning VR goggles & gloves to write a letter or buy airline tickets? It's just plain easier & faster to do it the way we do it today.
As silver bullet supply decreases... (Score:2)
Zounds! Let's get rid of all those cockamaney silver bullets, and we'll have giant robots to ride in. Cool!!!
Re:In a few years... (Score:4, Funny)
Makes you wonder if there is some hidden insight in calling the Linux version 'Mono'.
Re:I'm so unfashionable, it hurts... (Score:2)
A few seconds of Google found me this:
http://www.multicians.org/raf-tbl-definition.ht m l
Is that what you're talking about? Looks a bit like Prolog, only with some interesting semantic variations on that theme.
In general, I like the idea of highly dynamic languages that provide deep access to the structures of the encompassing system. For example, coding on MUSHes has always been insanely fun, and some of the most intere
Re:I'm so unfashionable, it hurts... (Score:2)
Not what. Who?
cLive ;-)
Re:I'm so unfashionable, it hurts... (Score:2)
It's not so much that I have a problem with... uh... TBL's current research interest, as it is that I just think it's kind of... obvious. The namespace issues are the really hard part, so in the end it just comes down to a lot of grunt work in getting those squared away.
Of course, since we ARE talking about fads here, you're probably right.
Re:I'm so unfashionable, it hurts... (Score:2)
It's not so much that I have a problem with... uh... TBL's current research interest, as it is that I just think it's kind of... obvious. The namespace issues are the really hard part, so in the end it just comes down to a lot of grunt work in getting those squared away.
I'd really like to know who you're talking about. Any help? I've recently become a bit of a language nut myself.
Re:XHTML (Score:5, Interesting)
See, the hacker part of me demands that anyone who has a web page learn HTML: it's not that hard, and it's like having a driver's license -- it's a lowest common denominator of skill. I believe that if every dork with a GeoCities site actually knew HTML instead of exporting from MS Word, the Web would be a better place. So, from that perspective, XHTML is something I support -- though I support it from the sense of replacing HTML (which should die in the eternal fires of Hell) entirely. Making people learn XML would be nice, but it's too complex a thing to make "required reading" for GeoCities weenies.
That said, you are obviously correct in that XML is the way the world should be. In fact, I did some web pages in straight-up well-formed XML coupled with CSS stylesheets, and it worked just fine. The only problems are that with current browsers, you can't use inline embedded images (Mozilla and IE don't support this) or hyperlinks (basically XPath, which IE doesn't support.) So, it looks like the Promised Land is withheld from us, which forces us to use XHTML for a while yet.
So, as you can see, I am wishy-washy on whether I like XHTML, or if I do whether I like it better than XML.
Of course, now I feel like I just did an in-depth evaluation of whether N*Sync or Britney will be more successful in the long run.
Re:A few software fashions that are doing too well (Score:2)
Re:Come on SOAP...Come on SOAP!! (Score:2, Interesting)
Re:Collections. (Score:3, Interesting)
The poster might be referring to the fact that the routines tend to provide Objects instead of strongly-typed objects, which leads to so much casting that I do frequently end up writing specialized collections classes just to avoid the cast. JDK 1.5 (when and if) should have a new collections framework designed