2,535 karma · joined September 24, 2010
This is rubbish. What matters is how many packets of data go through the network. It is packets which are the unit of transfer and which are handled by intermediate nodes. The difference between say 2340 and 2290 bytes is of no material consequence whatsoever, it may cause one less packet to be sent but probably won't. To think it does have a consequence is to demonstrate a complete lack of understanding of what happens in the network and in endpoints. None of these '50 byte savings' accumulate anywhere in any meaningful or measurable sense whatsoever. So no, it doesn't "add up" to anything.
And if you're going to downvote me explain why I am wrong and how the benefit of these mythical 'savings' can be demonstrated.
Secondly, America's power and influence is fading, slowly admittedly, but fading nonetheless. Like here in the UK your turn will come when you realise what it is like to be yesterday's bully boy. Ours came with the break up of Empire, yours may come when the world calls in your debts or builds walls to isolate your corrupt financial structures.
America was once admired and respected. Now it is increasingly like some blundering fat tourist in a brothel, people pretend to be nice to you because they want your money. But really, nobody is your friend.
I'm old enough to have read Computer Lib ('74) when it came out, I have a first edition which I imported into the UK by sending some sort of international money order to a US bookshop. For some reason I also have a second edition.
Applications should enforce correct application behaviour regardless of user behaviour. Databases should maintain database integrity regardless of application bahaviour.
If this requires duplicated effort then so be it.
And my point is that some very smart people work in marketing. People who think they can avoid being influenced are delusional.
There are two sets of attributes, the first (commonly called "skill" but perhaps better called "technique") describes how well you can carry out the "motor" activities of your job. The other, and more important in critical circumstances, is "judgement".
To describe it by analogy with driving, in the beginning you concentrate on developing experience in operating the vehicle, eventually this becomes more or less automatic. People call this skill and they are wrong, it is a set of learnt reflexes. More important is judgement, knowing how to maintain road awareness, knowing when and how to overtake, when to speed up and when to slow down etc, etc. NB when people talk about the dangers of drinking and driving it is impaired judgement they are mostly talking about (although there is some impaired skill such as poor reaction times which stops them getting out of problems their degraded judgement has got them into).
Judgement comes with experience and follows skill acquisition. With surgeons you would hope they know how to make a cut (they have technique). What you really want is someone who knows where and what to cut (they have judgement).
And yes, all of this applies to programming and systems design.
You are being intellectually dishonest by adopting an artificially contrarian position and trying to pretend he was saying we had to choose one or the other just, it seems, for the sake of having a contrarian position.
You are wrong, but despite having an idiotic opinion you're not an idiot, tempting as it is to think that. You are just someone who thinks that just because they can form a banal opinion that means the opinion has any worth. It doesn't.