Comments on: Technology Bias Can Be a Strength or a Weakness http://accidentaltechnologist.com/technology/technology-bias-can-be-a-strength-or-a-weakness/ Musings about Technology, Software Design and Development Wed, 16 May 2012 17:59:00 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Rob Bazinet http://accidentaltechnologist.com/technology/technology-bias-can-be-a-strength-or-a-weakness/#comment-2149 Rob Bazinet Thu, 27 Sep 2007 07:21:00 +0000 http://localhost/~rbazinet/?p=148#comment-2149 Wow, it took you a lot less time to respond than I expected. My point is the use of attacks as a way to knock down a technology. Your post attacks right from the beginning and even though you make points the context of the post is lost by the attack. I didn't miss your points and I won't refute them. Your post was a great example of exactly the point of my post. So to summarize, regardless of your technical merit the point of the post is lost by the attacks. I don't have anything against your or your taste for Ruby, Rails or any other technology. If you don't Rails then great. Wow, it took you a lot less time to respond than I expected.
My point is the use of attacks as a way to knock down a technology. Your post attacks right from the beginning and even though you make points the context of the post is lost by the attack. I didn’t miss your points and I won’t refute them. Your post was a great example of exactly the point of my post.
So to summarize, regardless of your technical merit the point of the post is lost by the attacks. I don’t have anything against your or your taste for Ruby, Rails or any other technology. If you don’t Rails then great.

]]> By: Rob Bazinet http://accidentaltechnologist.com/technology/technology-bias-can-be-a-strength-or-a-weakness/#comment-140 Rob Bazinet Thu, 27 Sep 2007 07:21:00 +0000 http://localhost/~rbazinet/?p=148#comment-140 <p>Wow, it took you a lot less time to respond than I expected.</p> <p>My point is the use of attacks as a way to knock down a technology. Your post attacks right from the beginning and even though you make points the context of the post is lost by the attack. I didn't miss your points and I won't refute them. Your post was a great example of exactly the point of my post.</p> <p>So to summarize, regardless of your technical merit the point of the post is lost by the attacks. I don't have anything against your or your taste for Ruby, Rails or any other technology. If you don't Rails then great.</p> Wow, it took you a lot less time to respond than I expected.

My point is the use of attacks as a way to knock down a technology. Your post attacks right from the beginning and even though you make points the context of the post is lost by the attack. I didn’t miss your points and I won’t refute them. Your post was a great example of exactly the point of my post.

So to summarize, regardless of your technical merit the point of the post is lost by the attacks. I don’t have anything against your or your taste for Ruby, Rails or any other technology. If you don’t Rails then great.

]]> By: bwtaylor http://accidentaltechnologist.com/technology/technology-bias-can-be-a-strength-or-a-weakness/#comment-2148 bwtaylor Thu, 27 Sep 2007 00:55:00 +0000 http://localhost/~rbazinet/?p=148#comment-2148 You badly misrepresent the points in my <a href="http://blog.bwtaylor.com/java/ruby_meet_erlang" rel="nofollow">blog</a>. I posted a reply comment there. In short, my article was about hype and how it's ending for RoR. I am not an advocate of any language as a one-size-fits-all solution. I'm just tired of fanboy zealots, which RoR has too many of. I most certainly did not decide erlang was "the" technolgoy for me. I cited it for its "cultural impact" of taking over as the "hot" language. I did "attack the Rails community" because they deserve it. RoR people write blogs like "Java Sucks Ass" all the time. But contrary to your assertion that I did so "with little technical reasons", I listed 14 technical points about ruby in big bullets - I'm not quite sure how you missed them. Most of these points were NOT contested in the comments (you read all the way to the comments but missed the big bulleted list of 14 points ?!?!?). How could they be contested - they're true! If you care to take up the cause, I invite you to do so there. For the record, I got responses like: - "Very nice" from asd - "Spot on" from mb - "some are valid" from she (rubyist who argued to not to lump ruby in with the RoR crowd) - "agreed on this one" from herval on "No high quality app server" (from one of the few giving technical rebutals) - "some people in the Ruby community agree with you" from sam (who asked for and got citations for "ruby is slow") - "Based on my experience using Java, Ruby, and Erlang, I think your points are very accurate." from RobinB - "Having worked professionally with Ruby on Rails for 8 months, I tend to agree with your comments." from Nathan Youngman You badly misrepresent the points in my blog. I posted a reply comment there. In short, my article was about hype and how it’s ending for RoR. I am not an advocate of any language as a one-size-fits-all solution. I’m just tired of fanboy zealots, which RoR has too many of. I most certainly did not decide erlang was “the” technolgoy for me. I cited it for its “cultural impact” of taking over as the “hot” language.
I did “attack the Rails community” because they deserve it. RoR people write blogs like “Java Sucks Ass” all the time. But contrary to your assertion that I did so “with little technical reasons”, I listed 14 technical points about ruby in big bullets – I’m not quite sure how you missed them. Most of these points were NOT contested in the comments (you read all the way to the comments but missed the big bulleted list of 14 points ?!?!?). How could they be contested – they’re true! If you care to take up the cause, I invite you to do so there.
For the record, I got responses like:
- “Very nice” from asd
- “Spot on” from mb
- “some are valid” from she (rubyist who argued to not to lump ruby in with the RoR crowd)
- “agreed on this one” from herval on “No high quality app server” (from one of the few giving technical rebutals)
- “some people in the Ruby community agree with you” from sam (who asked for and got citations for “ruby is slow”)
- “Based on my experience using Java, Ruby, and Erlang, I think your points are very accurate.” from RobinB
- “Having worked professionally with Ruby on Rails for 8 months, I tend to agree with your comments.” from Nathan Youngman

]]> By: bwtaylor http://accidentaltechnologist.com/technology/technology-bias-can-be-a-strength-or-a-weakness/#comment-139 bwtaylor Thu, 27 Sep 2007 00:55:00 +0000 http://localhost/~rbazinet/?p=148#comment-139 <p>You badly misrepresent the points in my <a href="http://blog.bwtaylor.com/java/ruby_meet_erlang" rel="nofollow">blog</a>. I posted a reply comment there. In short, my article was about hype and how it's ending for RoR. I am not an advocate of any language as a one-size-fits-all solution. I'm just tired of fanboy zealots, which RoR has too many of. I most certainly did not decide erlang was "the" technolgoy for me. I cited it for its "cultural impact" of taking over as the "hot" language. </p> <p>I did "attack the Rails community" because they deserve it. RoR people write blogs like "Java Sucks Ass" all the time. But contrary to your assertion that I did so "with little technical reasons", I listed 14 technical points about ruby in big bullets - I'm not quite sure how you missed them. Most of these points were NOT contested in the comments (you read all the way to the comments but missed the big bulleted list of 14 points ?!?!?). How could they be contested - they're true! If you care to take up the cause, I invite you to do so there.</p> <p>For the record, I got responses like:</p> <p>- "Very nice" from asd</p> <p>- "Spot on" from mb</p> <p>- "some are valid" from she (rubyist who argued to not to lump ruby in with the RoR crowd)</p> <p>- "agreed on this one" from herval on "No high quality app server" (from one of the few giving technical rebutals)</p> <p>- "some people in the Ruby community agree with you" from sam (who asked for and got citations for "ruby is slow")</p> <p>- "Based on my experience using Java, Ruby, and Erlang, I think your points are very accurate." from RobinB</p> <p>- "Having worked professionally with Ruby on Rails for 8 months, I tend to agree with your comments." from Nathan Youngman</p> You badly misrepresent the points in my blog. I posted a reply comment there. In short, my article was about hype and how it’s ending for RoR. I am not an advocate of any language as a one-size-fits-all solution. I’m just tired of fanboy zealots, which RoR has too many of. I most certainly did not decide erlang was “the” technolgoy for me. I cited it for its “cultural impact” of taking over as the “hot” language.

I did “attack the Rails community” because they deserve it. RoR people write blogs like “Java Sucks Ass” all the time. But contrary to your assertion that I did so “with little technical reasons”, I listed 14 technical points about ruby in big bullets – I’m not quite sure how you missed them. Most of these points were NOT contested in the comments (you read all the way to the comments but missed the big bulleted list of 14 points ?!?!?). How could they be contested – they’re true! If you care to take up the cause, I invite you to do so there.

For the record, I got responses like:

- “Very nice” from asd

- “Spot on” from mb

- “some are valid” from she (rubyist who argued to not to lump ruby in with the RoR crowd)

- “agreed on this one” from herval on “No high quality app server” (from one of the few giving technical rebutals)

- “some people in the Ruby community agree with you” from sam (who asked for and got citations for “ruby is slow”)

- “Based on my experience using Java, Ruby, and Erlang, I think your points are very accurate.” from RobinB

- “Having worked professionally with Ruby on Rails for 8 months, I tend to agree with your comments.” from Nathan Youngman

]]>