[eluser]Nick_MyShuitings[/eluser]
@toopay,
You are correct in you default definition of scalability. My reference to the term was not in depth, nor did I seek to define it. When new programmers (the same ones who usually ask questions here that 5 minutes of google will resolve for you), think "scalability", they are thinking JMeter, seige, ab load tests, and they wonder why their results drop so drastically after adding the ORM or DB abstraction layer. They are thinking of the clause in their contract with the client that says some bullshit like XYX concurrent users with an average of XYZ seconds / page load.
You bring up the (IMO valid) argument that we would be better off calling that performance, and then proceed to define a (IMO better) definition of what scalability truly entails. I agree with you completely... but I've been programming for years now, and PM for almost as long... a lot of the guys in this forum can't even figure out a foreach... so I summarized my post in a way that experience programmers might find offensive/over simplified, in which case "sorry"
