I'll agree to 100 as long as that includes DBA's, sysadmins, code librarians, QA testers, and project managers in addition to the actual system architects and/or programmers.
A man on a business trip is in Florida and decides to give his wife back home in Oregon an "I love you honey" call. During the conversation he off-handedly mentions the time of day. His wife replies, "Hey, that's the same time that it is here!"
It's entire structure is *derived* from printer tags and most are useless. Apps that don't know what they are sending or receiving shouldn't be doing it in the first place. And in fact they don't. The whole semantic web concept is total BS and is in fact a total failure.
No b2b apps really need it as they are all custom built and the apps cloned from them already know the semantics of the data or they wouldn't have bothered to clone from them in the first place. XML is just added after the fact. It is useless cruft.
Why do you think everyone hates it? It's as bad as C++ which requires full knowledge of the application specific templates to be of any use. Kill them both.
No it is not weird. XML is weird because it contains and is based on printer control cruft. Lots of printer control cruft. An unnecessary tag is a tag is a tag is a fucking tag.
Why do you think everybody hates it? Why do you think there are plans afoot (like the subject of this article) to get by without it?
XML sucks because it is based on a printer control spec. It's as simple and as ugly as that.
Yes. I'm lucky LISP can parse XML since they are really only just a special case of S-Expressions. Once out of that horrid mess of printer tags it was much more straightforward to validate them and insert them in all their complexity into a nicely normalized relational database.
Really. Non of that totally unnecessary tag BS inherited from a printer definition spec (of all absurd things.) And key/value pairs are a hell of a lot easier to insert into a database in addition to being easier to read.
Slashdot Mirror
I'll agree to 100 as long as that includes DBA's, sysadmins, code librarians, QA testers, and project managers in addition to the actual system architects and/or programmers.
Cuz' we buy lots of BMW's.
Since when did liberals do anything else except tear down Western Civilization?
If you are going to use indentation you shouldn't need all those parentheses.
"- Writing a line of code is done as a last resort when all attempts to avoid it have failed."
Yes, God forbid that we automate some clerk's job out of existence.
"If you create a programming language through which to solve the needs of your scenario, then the article simply makes no sense at all any more."
Which you can do most easily in LISP.
Mod this up.
"Typically no two software engineers agree on a solution."
Smart ones do in design sessions.
HTML5, XML and javascript don't break out of the client-server paradigm, they implement it, one hopes in a RESTful manner.
Same with SQL. It was originally supposed to be a query language for end users. Everyone had learned about Venn diagrams in school, right?
A riddle for you then:
A man on a business trip is in Florida and decides to give his wife back home in Oregon an "I love you honey" call. During the conversation he off-handedly mentions the time of day. His wife replies, "Hey, that's the same time that it is here!"
How is that possible?
You think it is actually tidy underneath there?
http://www.nytimes.com/interac...
Any company that has 200 devs working on the same codebase is in trouble. They just don't know it yet.
Every programmer is a trial and error programmer.
The sneer is affectionate because every engineer has sometimes kludged things together.
And they all converge towards LISP.
OMG, it's another sign of global warming!!!
They are directly competing now that RedBox has a streaming plan.
The Apple Stores sell an external SuperDrive for $79.
Red Box is waaaaaaay cheaper than Netflix and you can get BluRay discs too!
It's entire structure is *derived* from printer tags and most are useless. Apps that don't know what they are sending or receiving shouldn't be doing it in the first place. And in fact they don't. The whole semantic web concept is total BS and is in fact a total failure.
No b2b apps really need it as they are all custom built and the apps cloned from them already know the semantics of the data or they wouldn't have bothered to clone from them in the first place. XML is just added after the fact. It is useless cruft.
Why do you think everyone hates it? It's as bad as C++ which requires full knowledge of the application specific templates to be of any use. Kill them both.
No it is not weird. XML is weird because it contains and is based on printer control cruft. Lots of printer control cruft. An unnecessary tag is a tag is a tag is a fucking tag.
Why do you think everybody hates it? Why do you think there are plans afoot (like the subject of this article) to get by without it?
XML sucks because it is based on a printer control spec. It's as simple and as ugly as that.
Yes. I'm lucky LISP can parse XML since they are really only just a special case of S-Expressions. Once out of that horrid mess of printer tags it was much more straightforward to validate them and insert them in all their complexity into a nicely normalized relational database.
Really. Non of that totally unnecessary tag BS inherited from a printer definition spec (of all absurd things.) And key/value pairs are a hell of a lot easier to insert into a database in addition to being easier to read.
for clearing that up for us.