True. I didn't do something similar because: 1) I have no place to work on cars. 2) I wanted something reliable. I wouldn't have confidence in the car you described as a daily driver (if _I_ built it that is). Now maybe if you built it, it might be reliable. 3) I am being perverse. I LIKE driving the underdog. (when the underdog is as fast as the SRT-4). 4) I got a new car loan for the SRT-4.
Cada loco tiene su tema. I've done this math too. I got more than I could with a Jap car. The trans, differential etc is usually the weak point in building up a japanese car. Try running more than 10 lbs of boost in a Civic and see what happens. You'll not be driving it for long. The cool thing about the Dodge SRT-4 is that the car was built to be hot-rodded. The tranmission is heavy duty and has a torque biasing differential already in the driveline. By the time you replace the transmission and the differential and retrofit a turbocharger etc, you'll likely spend more than just buying the Neon. Plus, the SRT-4 can run 15-20 lbs of boost with no work needing to be done to the engine's bottom end. Also, the stock clutch is already upgraded. SRT-4 only needs a new clutch if you go to the Mopar stage 3 setup (or similar). In other words the stock drive train is good up to about 300 HP. Take a Civic Si for example, (I love the Civic Si) and try getting 350 HP out of it. You can do it maybe, but not run it very far unless you upgrade the *entire* drive train. The SRT-4 is perfectly happy with 350 - 400 HP and you can order one that way from the factory! (They'll ship Stage 3 motors in a crate though cause its not "approved" for street use - must assemble).
And what exactly makes it a "bad imitation of a rice burner"? Its not an imitation of anything! So go build your rice burner and I'll see you on the track!:-)
Power to weight Baby! Under 3000 lbs. 230 HP (at the wheels!). But the Porsche engine isn't that much more powerful (if any at all). See my post below.
Shitbox? Hmmm, my feelings are hurt! I guess I have to go out and humiliate a few Porsches and Mustangs on my way home! Horsepower isn't that much different between Boxter S and SRT-4. Most SRT-4's dyno out to about 227 - 235 *at the wheels*. They're rated by Dodge as 230 hp. So the engine HP (measured at the engine) will be close to the Boxter S numbers, which IIRC is 258. FYI: With Mopar's stage 3 kit, an SRT-4 makes about 365 hp on pump gas and just shy of 400 on 100 octane! Yikes! Now THATS a fast shitbox! I submit that the SRT-4 is about the most fun you can have (behind the wheel) for 22 kilodollars.:-p
"...it's like buying a new Porsche and ripping out the engine and putting a Dodge Neon engine in it."
Not arguing your point about the usefulness of Winders on a MacTel machine, but my Dodge SRT-4 (essentially a Neon) will whip the crap out of a Porsche Boxter (and LOTS of other more prestigious cars). Putting a Neon engine in a Porsche ISN'T necessarily a bad idea!:-p
Putting Winders on a MacBook... I wish there was a VMware solution for this. I don't want to have to permanently install Windows on ANYTHING anymore. The only OS I want my macs booting is OS X.
VMware are you listening?
Re:Open Appserver and Progress 4GL
on
JSF vs ASP.net
·
· Score: 1
"...and a rich client for in-house power use."
This is exactly the scheme we're using in house. We'll deploy various frontends (some TBD) based on client needs and bandwidth. On our company LAN, we'll use fat clients (better for serious data entry IMHO), and all will access the same body of business logic on our Progress Open Appserver (great product).
Rant: I really wish Progress Software Corporation had better advertising and promotion. They've had a great DB and rich development environment for years. Now they have kick-ass middleware (SonicMQ etc). They've been around (and proftable) for over 25 years, and nobody under 40 ever heard of them.
-=W=-
Open Appserver and Progress 4GL
on
JSF vs ASP.net
·
· Score: 1
Is this really 'just a front end'? If your project is really just a front end to an existing body of business logic, it doesn't really matter that much. Front end coding will be the easy part. Going through your server or appserver business logic and tweaking it for your new interface will be where the work is. In a well designed web front end there should be as little business logic as possible. This way the front-end coding is reduced and replacing your web interface down the road with another front end becomes easier. Laugh if you want, but I'd probably code the appserver-side logic in the Progress 4GL running on Open Appserver and then use a Webspeed front end if the requirements were low, if not maybe write the web interface with Visual *.Net or whatever the team was comfortable with. IMNSHO, the middle tier is where your big decisions should be. That way you're not permanently tied to any particular front end.
"I'm really confused by the mindset of those that disable all the features of their OS (like Dashboard and Spotlight), unless you have an old system. Is that it? Is it that you don't like your computer doing all these things? Or is it that you think that a whiz-bang feature has to be something you want to use all the time, or not at all?"
My G5 iMac only has 1.5 GB of RAM.:-(
I found that after a while I just used my browser to get the info I needed because its right there, usually with a bunch of tabs open, all the time. Hitting F12 to look at a cooler clock than the one in the titlebar... well after a while it just didn't seem worth it for me in my particular working environment.
At this point in time, I don't know *anyone* who uses Dashboard or any Konfabulator-like widget. I wonder what the profile is of the average heavy user of Dashboard/Konfabulator? All my friends/acquaintances/co-workers are either senior Windows admin types or Linux/UNIX admins or programmers. (I write UNIX server-side and Windows client-side software).
I guess there are some people who are fairly passionate about this kind of desktop accessory (I was a serious Sidekick user back in the day) and I didn't mean to ruffle any feathers. If Dashboard makes you happy, I'm tickled pink.:-)
Other than Yahoo execs? I'm a Mac user, and while I thought Dashboard was pretty kewl at first, my enthusiasm quicky waned. Now I've disabled it. Most of the funchtionality of it was already available on various web pages, and I can close the browser down and reclaim resources. With Dashboard, those widgets are consuming memory and other resources even when Dashboard isn't showing. Will Yahoo's version act the same way? Maybe a Konfabulator user can weigh in on this. Mod this down as a troll, but I just can't care about Yahoo's version of Apple's version of Konfabulator. Big waste of resources.
I was in a similar situation. If your boss is smart enough to write code, he is probably smart enough to see reason. You just have to have "proof" that you guys need to be using versioning etc. The problem lies in figuring out what consitutes "proof" for him. I suggest pointing out that he better have a damn good reason to go against industry best practices. During a previous stint (about 5 years) of consulting I found that using busswords like "Best Practices" when explaining this stuff to people really works. He probably won't understand at first but nobody wants to look like a dummy to his peers.
Another good angle: The first principle of sales is: "The fear of loss is greater than the desire for gain." Show him what he could lose if your outfit doesn't use industry standard tools. This is probably the most reliable method to sell anything. There's also lots of studies that show projects using versioning are more productive that teams that don't use it even when versioning is implemented in the middle of a project with an aggressive deadline. Steve McConnell's book _The_Software_Project_Survival_Guide http://www.amazon.com/gp/product/1572316217/103-20 95419-7389469?v=glance&n=283155 from M$ Press has lots of usefull strategies and factoids. He also addresses the human factor in software projects. Good stuff.
He may also just not want to go through the learning curve associated with new tools. FWIW, that was part of the problem here. Using web based tools helped with user (and boss) acceptance around these parts. We're using a help desk application to track all sorts of IT trouble tickets as well as defects: http://www.otrs.org/ OTRS (Open Ticket Request System) is an open source web based application written in PERL. So far we've had a good experience with it.
We've also implemented Subversion and Viewcvs. Both OTRS and Subversion/Viewcvs are running on a PC class box running SuSE 9.3. We're also using Very Quick Wiki: http://veryquickwiki.croninsolutions.com/ as a easy (and quick!) way to share the progress of out software projects with the company's users. This was one of the easiest sells of all. I just installed it (very easy to install, drag and drop, uses Tomcat as server) and started using it. I sent out some project updates with a URL instead of the full text. Just pointed my users and boss toward the wiki page for the project. Now he's using it to keep notes about changes to be implemented in our enterprise systems.
Using the SuSE distro made all of this easier as all the servers (OTRS as well) are included, but your favorite distro will work just as well. We use SuSE because the last 4 or 5 versions have been well "groomed." The uptime on the box has been fantastic! Better in fact than our HP 9000's.:-p
This story is currently nominated for "Worst Slashdot Story of 2005" and unless a Katrina-scale woofer of a story comes along in the next month, this little slice of junior-high blather will easily take the prize. I wonder if Hemos actually _read_ this story before posting it? (Hemos: did you write this? Or just post it?) As many others have pointed out, the first sentence doesn't even parse in English! I might be wrong, but I'm assuming that Hemos' native language is English because most of the not-english-as-first-language-having folks I've met can express themselves MUCH better than Americans who grew up with English. Not meaning to flame Americans (I'm from Mississippi after all...) but the state of written communication in the USA seems to be declining proportionally to the rise in blogging.
I started downloading the new release about 5 minutes before this story left the mysterious future... when it did, my download speed went down to 2.8 KB/s.
I other news: My boss is getting serious about rolling out Linux desktops here. He asked me today for a "prototype" for his desk. Crossover Office is gonna be a big part of our company's desktop transition. We only have about 150 - 200 desktop users, and our M$ tithe is still about 40 or 50 kilodollars per year. Getting off the upgrade treadmill is going to be sooo cool!
It seems that the prefered beginners languages here on/. are (in no particular order) are Python, BASIC, and ANSI C. All are IMNSHO, good choices for a beginner. A few have mentioned Ruby, which is a very approachable language. But the best advice I've seen here so far is "Find an itch you want scratched". That is, find yourself an interesting project, and code it. Decide which platform its gonna run on, pick one of the above mentioned languages and do it! The only way to learn to code is to code! Oh yeah, it helps to read code. Reading source is a huge help to see how others solved problems.
One problem with this discussion is that you never said what platform you use or want to write for. This lack of information about what you want to do is really common. Almost _every_ one of these "Ask/." articles leave out information that respondents need to adequately answer the darned question! At any rate, if you're a M$ kinda user, I think you should get ahold of VB 6 or VB.net and start with that. Lots of books etc available to make getting started easy. If you're a Linux/UNIX sorta person, then the ANSI C recommendations really start to make more sense.
I think the bottom line is this: If you just want to learn some more about programming "in general", then you probably won't learn much. If you have some sort of persistent interest in solving some problem or other, or you want to make your life easier by automating something, then just code it!/* this post is really disorganized. i'm in the middle of debugging a headless batch process on HP-UX, so this post is only getting spare clock cycles */
What is the intellectual property angle here? In TFA, Mr. Smith refers Google as "failing to respect his intellectual property rights." But the real issue is a trademark dispute. Isn't there a difference between ip and trademark disputes?
IANAL, etc, but it sounds like this isn't going to go well for "Independent International Investment Research". I understand that Smith has some obligation to protect his trademark, but I'll bet their market doesn't care and wouldn't confuse the two services. G-Mail just doesn't have any public profile at all.
Your assertion that the Bible has changed is somewhat incorrect. The source documents for the English translation of the Bible have not changed. There have been many translations, which sometimes are different from one another. This is the nature of translations. Translations are man-made documents. Other than the adding of vowel pointing to the Torah, the Hebrew scriptures are remarkable in the _lack_ of change over the last couple of thousand years. The greek and aramaic sources for the New Testament are amazing in the fact that they agree with each other so closely. Take all the thousands of source docs for the Gospels and you will have only a dozen or so differences between them. Very cool considering the hand-copied nature of books back then. To summarize: Translations aren't the same as the source documents! The Bible _wasn't_ written in English and there aren't any "divinely inspired" translations! And please don't bring up the KJV. Its OK considering the limited sources they had to work with, but there are much more accurate translations than the KJV! If you can't read Greek, Hebrew and Aramaic (and Latin so you can check out the Septuagent) you can't read the Bible! You're just reading TRANSLATIONS. As far as you assertion that Yahweh needed to correct himself... hmmmph. He didn't change the message because he made a mistake. He changed the contract He made with humans, because _we're_ not perfect.
OK I don't know much about CMS's but wouldn't it act differently? Possibly different feature sets and look and feel? How would/. readers feel if suddenly the site wasn't running slashcode? (OK, some might rejoice...) But it would look and act differently if it were running another CMS wouldn't it?
This is really a cheesy article even for zdnet uk. There are egregious mispellings in the first paragraph and the (first) link for page two is broken. Perhaps the mispellings are meant to be funny. They are not. The article is not redeemed by it's content. As many other posters have pointed out: this article isn't funny. With so many really well-done articles published every week, why subject/. readers to this reeking pile of shite?
The USA doesn't have the biggest army in the world. China probably has the biggest army in the world. Our military isn't really all that big compared to times past. We may have _one_ of the best trained army in the world. The USA spends a great deal more money on training than any other country (in total dollars spent on training). Averaged out per soldier, we are still spending more than any large army per soldier. Some smaller European armies may spend more per soldier than we do. We also have some of the very best Spec Ops warriors in the world. I think (but haven't verified) that we have more Spec Ops warriors than any other country.
As far as "shooting our own side" goes, that is a big problem in any war and for any army. The old saying "friendly fire ain't" comes to mind.
What really counts though is the fact that we can field an army anywhere in the world _faster_ than anybody else. Its the ability to put ordnance (or armed soldiers) on the ground anywhere and do it _right_now_ that makes the US's military without equal on this planet.
Slashdot Mirror
True. I didn't do something similar because:
1) I have no place to work on cars.
2) I wanted something reliable. I wouldn't have confidence in the car you described as a daily driver (if _I_ built it that is). Now maybe if you built it, it might be reliable.
3) I am being perverse. I LIKE driving the underdog. (when the underdog is as fast as the SRT-4).
4) I got a new car loan for the SRT-4.
Cada loco tiene su tema. I've done this math too. I got more than I could with a Jap car. The trans, differential etc is usually the weak point in building up a japanese car. Try running more than 10 lbs of boost in a Civic and see what happens. You'll not be driving it for long. The cool thing about the Dodge SRT-4 is that the car was built to be hot-rodded. The tranmission is heavy duty and has a torque biasing differential already in the driveline. By the time you replace the transmission and the differential and retrofit a turbocharger etc, you'll likely spend more than just buying the Neon. Plus, the SRT-4 can run 15-20 lbs of boost with no work needing to be done to the engine's bottom end. Also, the stock clutch is already upgraded. SRT-4 only needs a new clutch if you go to the Mopar stage 3 setup (or similar). In other words the stock drive train is good up to about 300 HP. Take a Civic Si for example, (I love the Civic Si) and try getting 350 HP out of it. You can do it maybe, but not run it very far unless you upgrade the *entire* drive train. The SRT-4 is perfectly happy with 350 - 400 HP and you can order one that way from the factory! (They'll ship Stage 3 motors in a crate though cause its not "approved" for street use - must assemble).
:-)
And what exactly makes it a "bad imitation of a rice burner"? Its not an imitation of anything! So go build your rice burner and I'll see you on the track!
Power to weight Baby! Under 3000 lbs. 230 HP (at the wheels!). But the Porsche engine isn't that much more powerful (if any at all). See my post below.
Shitbox? Hmmm, my feelings are hurt! I guess I have to go out and humiliate a few Porsches and Mustangs on my way home! :-p
Horsepower isn't that much different between Boxter S and SRT-4. Most SRT-4's dyno out to about 227 - 235 *at the wheels*. They're rated by Dodge as 230 hp. So the engine HP (measured at the engine) will be close to the Boxter S numbers, which IIRC is 258. FYI: With Mopar's stage 3 kit, an SRT-4 makes about 365 hp on pump gas and just shy of 400 on 100 octane! Yikes! Now THATS a fast shitbox! I submit that the SRT-4 is about the most fun you can have (behind the wheel) for 22 kilodollars.
"...it's like buying a new Porsche and ripping out the engine and putting a Dodge Neon engine in it."
:-p
Not arguing your point about the usefulness of Winders on a MacTel machine, but my Dodge SRT-4
(essentially a Neon) will whip the crap out of a Porsche Boxter (and LOTS of other more prestigious cars). Putting a Neon engine in a Porsche ISN'T necessarily a bad idea!
Putting Winders on a MacBook... I wish there was a VMware solution for this. I don't want to have to permanently install Windows on ANYTHING anymore. The only OS I want my macs booting is OS X.
VMware are you listening?
"...and a rich client for in-house power use."
This is exactly the scheme we're using in house. We'll deploy various frontends (some TBD) based on client needs and bandwidth. On our company LAN, we'll use fat clients (better for serious data entry IMHO), and all will access the same body of business logic on our Progress Open Appserver (great product).
Rant: I really wish Progress Software Corporation had better advertising and promotion. They've had a great DB and rich development environment for years. Now they have kick-ass middleware (SonicMQ etc). They've been around (and proftable) for over 25 years, and nobody under 40 ever heard of them.
-=W=-
Is this really 'just a front end'? If your project is really just a front end to an existing body of business logic, it doesn't really matter that much. Front end coding will be the easy part. Going through your server or appserver business logic and tweaking it for your new interface will be where the work is. In a well designed web front end there should be as little business logic as possible. This way the front-end coding is reduced and replacing your web interface down the road with another front end becomes easier.
Laugh if you want, but I'd probably code the appserver-side logic in the Progress 4GL running on Open Appserver and then use a Webspeed front end if the requirements were low, if not maybe write the web interface with Visual *.Net or whatever the team was comfortable with. IMNSHO, the middle tier is where your big decisions should be. That way you're not permanently tied to any particular front end.
"I'm really confused by the mindset of those that disable all the features of their OS (like Dashboard and Spotlight), unless you have an old system. Is that it? Is it that you don't like your computer doing all these things? Or is it that you think that a whiz-bang feature has to be something you want to use all the time, or not at all?"
:-(
:-)
My G5 iMac only has 1.5 GB of RAM.
I found that after a while I just used my browser to get the info I needed because its right there, usually with a bunch of tabs open, all the time. Hitting F12 to look at a cooler clock than the one in the titlebar... well after a while it just didn't seem worth it for me in my particular working environment.
At this point in time, I don't know *anyone* who uses Dashboard or any Konfabulator-like widget. I wonder what the profile is of the average heavy user of Dashboard/Konfabulator? All my friends/acquaintances/co-workers are either senior Windows admin types or Linux/UNIX admins or programmers. (I write UNIX server-side and Windows client-side software).
I guess there are some people who are fairly passionate about this kind of desktop accessory (I was a serious Sidekick user back in the day) and I didn't mean to ruffle any feathers. If Dashboard makes you happy, I'm tickled pink.
Other than Yahoo execs? I'm a Mac user, and while I thought Dashboard was pretty kewl at first, my enthusiasm quicky waned. Now I've disabled it. Most of the funchtionality of it was already available on various web pages, and I can close the browser down and reclaim resources. With Dashboard, those widgets are consuming memory and other resources even when Dashboard isn't showing. Will Yahoo's version act the same way? Maybe a Konfabulator user can weigh in on this.
Mod this down as a troll, but I just can't care about Yahoo's version of Apple's version of Konfabulator. Big waste of resources.
I was in a similar situation. If your boss is smart enough to write code, he is probably smart enough to see reason. You just have to have "proof" that you guys need to be using versioning etc. The problem lies in figuring out what consitutes "proof" for him. I suggest pointing out that he better have a damn good reason to go against industry best practices. During a previous stint (about 5 years) of consulting I found that using busswords like "Best Practices" when explaining this stuff to people really works. He probably won't understand at first but nobody wants to look like a dummy to his peers.
0 95419-7389469?v=glance&n=283155
:-p
Another good angle: The first principle of sales is: "The fear of loss is greater than the desire for gain." Show him what he could lose if your outfit doesn't use industry standard tools. This is probably the most reliable method to sell anything. There's also lots of studies that show projects using versioning are more productive that teams that don't use it even when versioning is implemented in the middle of a project with an aggressive deadline. Steve McConnell's book _The_Software_Project_Survival_Guide
http://www.amazon.com/gp/product/1572316217/103-2
from M$ Press has lots of usefull strategies and factoids. He also addresses the human factor in software projects. Good stuff.
He may also just not want to go through the learning curve associated with new tools. FWIW, that was part of the problem here. Using web based tools helped with user (and boss) acceptance around these parts. We're using a help desk application to track all sorts of IT trouble tickets as well as defects:
http://www.otrs.org/
OTRS (Open Ticket Request System) is an open source web based application written in PERL. So far we've had a good experience with it.
We've also implemented Subversion and Viewcvs. Both OTRS and Subversion/Viewcvs are running on a PC class box running SuSE 9.3. We're also using Very Quick Wiki:
http://veryquickwiki.croninsolutions.com/
as a easy (and quick!) way to share the progress of out software projects with the company's users. This was one of the easiest sells of all. I just installed it (very easy to install, drag and drop, uses Tomcat as server) and started using it. I sent out some project updates with a URL instead of the full text. Just pointed my users and boss toward the wiki page for the project. Now he's using it to keep notes about changes to be implemented in our enterprise systems.
Using the SuSE distro made all of this easier as all the servers (OTRS as well) are included, but your favorite distro will work just as well. We use SuSE because the last 4 or 5 versions have been well "groomed." The uptime on the box has been fantastic! Better in fact than our HP 9000's.
HTH
"Worst /. Story of 2005"
This story is currently nominated for "Worst Slashdot Story of 2005" and unless a Katrina-scale woofer of a story comes along in the next month, this little slice of junior-high blather will easily take the prize. I wonder if Hemos actually _read_ this story before posting it? (Hemos: did you write this? Or just post it?) As many others have pointed out, the first sentence doesn't even parse in English! I might be wrong, but I'm assuming that Hemos' native language is English because most of the not-english-as-first-language-having folks I've met can express themselves MUCH better than Americans who grew up with English. Not meaning to flame Americans (I'm from Mississippi after all...) but the state of written communication in the USA seems to be declining proportionally to the rise in blogging.
>Every time a new security hole is discovered, system administrators using Xen have to manually backport a fix from the latest kernel.
Yeah, its problems like that with Xen that keep our shop on VMware.
http://www.novell.com/products/linuxprofessional/c omparative.html
I started downloading the new release about 5 minutes before this story left the mysterious future... when it did, my download speed went down to 2.8 KB/s.
I other news: My boss is getting serious about rolling out Linux desktops here. He asked me today for a "prototype" for his desk. Crossover Office is gonna be a big part of our company's desktop transition.
We only have about 150 - 200 desktop users, and our M$ tithe is still about 40 or 50 kilodollars per year. Getting off the upgrade treadmill is going to be sooo cool!
It seems that the prefered beginners languages here on /. are (in no particular order) are Python, BASIC, and ANSI C. All are IMNSHO, good choices for a beginner. A few have mentioned Ruby, which is a very approachable language. But the best advice I've seen here so far is "Find an itch you want scratched". That is, find yourself an interesting project, and code it. Decide which platform its gonna run on, pick one of the above mentioned languages and do it! The only way to learn to code is to code! Oh yeah, it helps to read code. Reading source is a huge help to see how others solved problems.
/." articles leave out information that respondents need to adequately answer the darned question! At any rate, if you're a M$ kinda user, I think you should get ahold of VB 6 or VB.net and start with that. Lots of books etc available to make getting started easy. If you're a Linux/UNIX sorta person, then the ANSI C recommendations really start to make more sense.
/* this post is really disorganized. i'm in the middle of debugging a headless batch process on HP-UX, so this post is only getting spare clock cycles */
One problem with this discussion is that you never said what platform you use or want to write for. This lack of information about what you want to do is really common. Almost _every_ one of these "Ask
I think the bottom line is this: If you just want to learn some more about programming "in general", then you probably won't learn much. If you have some sort of persistent interest in solving some problem or other, or you want to make your life easier by automating something, then just code it!
What is the intellectual property angle here? In TFA, Mr. Smith refers Google as "failing to respect his intellectual property rights." But the real issue is a trademark dispute. Isn't there a difference between ip and trademark disputes?
IANAL, etc, but it sounds like this isn't going to go well for "Independent International Investment Research". I understand that Smith has some obligation to protect his trademark, but I'll bet their market doesn't care and wouldn't confuse the two services. G-Mail just doesn't have any public profile at all.
Your assertion that the Bible has changed is somewhat incorrect. The source documents for the English translation of the Bible have not changed. There have been many translations, which sometimes are different from one another. This is the nature of translations. Translations are man-made documents.
Other than the adding of vowel pointing to the Torah, the Hebrew scriptures are remarkable in the _lack_ of change over the last couple of thousand years. The greek and aramaic sources for the New Testament are amazing in the fact that they agree with each other so closely. Take all the thousands of source docs for the Gospels and you will have only a dozen or so differences between them. Very cool considering the hand-copied nature of books back then.
To summarize: Translations aren't the same as the source documents! The Bible _wasn't_ written in English and there aren't any "divinely inspired" translations! And please don't bring up the KJV. Its OK considering the limited sources they had to work with, but there are much more accurate translations than the KJV!
If you can't read Greek, Hebrew and Aramaic (and Latin so you can check out the Septuagent) you can't read the Bible! You're just reading TRANSLATIONS.
As far as you assertion that Yahweh needed to correct himself... hmmmph. He didn't change the message because he made a mistake. He changed the contract He made with humans, because _we're_ not perfect.
You mean like OSX and Spotlight?
why not pick up the USD 499 Mac Mini? Mine is working just fine as a small server.
OK I don't know much about CMS's but wouldn't it act differently? Possibly different feature sets and look and feel? How would /. readers feel if suddenly the site wasn't running slashcode? (OK, some might rejoice...) But it would look and act differently if it were running another CMS wouldn't it?
Wouldn't changing to another CMS possibly cause you to lose readership? Seems like just upgrading the server is the way to go.
Looks like I made an "s" out of myself! :-P
This is really a cheesy article even for zdnet uk. There are egregious mispellings in the first paragraph and the (first) link for page two is broken. /. readers to this reeking pile of shite?
Perhaps the mispellings are meant to be funny. They are not. The article is not redeemed by it's content. As many other posters have pointed out: this article isn't funny. With so many really well-done articles published every week, why subject
Wow, that was the bestest post I've ever read! :-)
You might have the bigest army in the world...
The USA doesn't have the biggest army in the world. China probably has the biggest army in the world. Our military isn't really all that big compared to times past. We may have _one_ of the best trained army in the world. The USA spends a great deal more money on training than any other country (in total dollars spent on training). Averaged out per soldier, we are still spending more than any large army per soldier. Some smaller European armies may spend more per soldier than we do. We also have some of the very best Spec Ops warriors in the world. I think (but haven't verified) that we have more Spec Ops warriors than any other country.
As far as "shooting our own side" goes, that is a big problem in any war and for any army. The old saying "friendly fire ain't" comes to mind.
What really counts though is the fact that we can field an army anywhere in the world _faster_ than anybody else. Its the ability to put ordnance (or armed soldiers) on the ground anywhere and do it _right_now_ that makes the US's military without equal on this planet.