Talk:Good Technology

From APIDesign

(Difference between revisions)
Jump to: navigation, search
(Comment provided by aboguylod - via ArticleComments extension)
Current revision (10:30, 30 April 2013) (edit) (undo)
(Comment provided by Tim Boudreau - via ArticleComments extension)
 
Line 15: Line 15:
--[http://79.170.40.42/3a9ar.com/pligg/story.php?title=read-all-about-the-penis-advantage
--[http://79.170.40.42/3a9ar.com/pligg/story.php?title=read-all-about-the-penis-advantage
aboguylod] 20:14, 7 January 2012 (CET)
aboguylod] 20:14, 7 January 2012 (CET)
 +
</div>
 +
== Tim Boudreau said ... ==
 +
 +
<div class='commentBlock'>
 +
These days, my definition of a "good technology" is one which lets me get rid of at least two other technologies - or something which aligns the model of the software to the underlying technology so much better that entire categories of problem disappear. Something that makes you realize that the creators of a technology you've been using for years fundamentally misunderstood the nature of the problem they were solving. Like, say, NginX vs. Apache or callback-based I/O code versus threaded I/O code.
 +
 +
--Tim Boudreau 12:30, 30 April 2013 (CEST)
</div>
</div>

Current revision

Comments on Good Technology <comments />


aboguylod said ...

Tim Boudreau said ...

These days, my definition of a "good technology" is one which lets me get rid of at least two other technologies - or something which aligns the model of the software to the underlying technology so much better that entire categories of problem disappear. Something that makes you realize that the creators of a technology you've been using for years fundamentally misunderstood the nature of the problem they were solving. Like, say, NginX vs. Apache or callback-based I/O code versus threaded I/O code.

--Tim Boudreau 12:30, 30 April 2013 (CEST)

Personal tools
buy