I wonder if it could be argued that the imbalance of airtime represented in this situation corresponds to a significant corporate investment in those candidates that do appear in the debate. In reality it's a political advertisement for those candidates. They get to argue their moslty identical positions and the excluded candidates do not get to respond. Sounds like an ad to me. I wonder how much 90minutes of ad time goes for these days?
The biggest reason you see class abstractions in JS, is that people aren't able to think outside of an OO/Class hierarchy box.
codswallop. that's like saying that you see so many C programs because people aren't able to code in assembly. no. people stopped writing assembly and started writing more C for exactly the same reason that C was created in the first place - there's a better way to do it.
it may be the 'probably the most useful aspect', but it's still a leak of the implementation details of a half-baked feature.
how many of 'those C++ guys' are raving about how cool it is to mainpulate **this in your constructor? none. why not? because it's foolish and the language already provides rich abstractions for many of the sensible things you could do there, and more importantly prevents you from doing most of the idiotic things. same reason most of the 'compile-to-javascript' languages, as3, JIT engines, etc... either forgo the prototype chain entirely or de-emphasize it.
javascript doesn't, of course, do this. it says - look we're going to do half of the work for you, if you want something more you have to implement it yourself, here's the tools. watch your feet, though.
ugh, Crockford considered harmful. 1) it's not compatible with ES5. 2) it doesn't handle overridden methods/constructor 3) you can't efficiently & cleanly get private/protected members 4) it misses the point, just because you can do all these clever things with prototypes doesn't mean that you should.
exposing the mechanics of all this stuff to the programmer is a disaster - it results in reams of confused questions on stackoverflow, and tools that need to solve the halting problem.
does this mean it would be illegal for me to carry a book while riding my home-made 13-handled left-handed doobry-furkin (somewhat similar to a bicycle), unless I ask Congress first?
THREE.js is the worst example if this. the documentation is basically machine-generated API definitions with a "getFoo() - this method gets the foo" (sometimes) uselessly sprinkled therein. if you suggest that this could be improved, something that many people have tried, you will either told to: a) go look at the samples b) look at the (poorly commented) source code, work it out yourself c) write the f'ing docs yourself d) shut up e) really shut up, shortly before getting banned
seriously, who tells a n00b that they should be the ones writing the docs?
think what you will about the Mormons (I happen to agree with Linus), but I doubt the Finnish consulate is going to need any military protection, nobody's going to get dragged out and killed. the worst that will happen is a couple of over-entheusiastic, under-sexed, teen-aged adults will turn up at the door and ask them if they've heard the new message from God.
this isn't about altruistically teaching others a valuable skill. it's about vain programmers trying to show their non-programmer colleagues how hard it is to code in order to get more respect. how much more condescending can you get? different people have aptitudes for different skills. go teach some dis-interested people how to do the rubic's cube, or something.
Slashdot Mirror
Zx81 manual
BBC micro AUG
K&R
Petzold
SWIM agrees.
I wonder if it could be argued that the imbalance of airtime represented in this situation corresponds to a significant corporate investment in those candidates that do appear in the debate. In reality it's a political advertisement for those candidates. They get to argue their moslty identical positions and the excluded candidates do not get to respond. Sounds like an ad to me. I wonder how much 90minutes of ad time goes for these days?
I think you excellently summarized why this situation represents a complete failure to inform the electorate.
If you're giving them what they want then, by definition, you're not giving them anything they don't already know.
Wait. Did I miss something? I thought those wars were started to jack up oil prices and increase military spending.
The Apple Reality Distortion Field - now in a more visible purple color for your continence!
I think it's a hidden feature - the new camera is partially able to see through Somebody Else's Problem fields. Hence the pink/purple hue.
You're holding it wrong
Ok, I must be too young but I can't remember the last time MS closed some previously open-source framework.
Can you rmind me?
You miss the point, I think. When you remove the TypeScript annotations what makes you think the remaining JavaScript will be useful.
Isn't that exactly what the typescript compiler does?
Exactly. Thanks for clarifying my point.
The biggest reason you see class abstractions in JS, is that people aren't able to think outside of an OO/Class hierarchy box.
codswallop.
that's like saying that you see so many C programs because people aren't able to code in assembly.
no.
people stopped writing assembly and started writing more C for exactly the same reason that C was created in the first place - there's a better way to do it.
exactly. Javascript has leaky and dangerous abstractions that buy you nothing and only confuse - it's poorly designed.
and don't even get me started on semicolons.
i fail to see how any of that has anything to do with or is limited to prototype chains, except maybe performance where it can only hurt.
function programming techniques don't require prototype-based inheritance.
event driven callbacks, async, neither.
it may be the 'probably the most useful aspect', but it's still a leak of the implementation details of a half-baked feature.
how many of 'those C++ guys' are raving about how cool it is to mainpulate **this in your constructor? none. why not? because it's foolish and the language already provides rich abstractions for many of the sensible things you could do there, and more importantly prevents you from doing most of the idiotic things. same reason most of the 'compile-to-javascript' languages, as3, JIT engines, etc... either forgo the prototype chain entirely or de-emphasize it.
javascript doesn't, of course, do this. it says - look we're going to do half of the work for you, if you want something more you have to implement it yourself, here's the tools. watch your feet, though.
ugh, Crockford considered harmful.
1) it's not compatible with ES5.
2) it doesn't handle overridden methods/constructor
3) you can't efficiently & cleanly get private/protected members
4) it misses the point, just because you can do all these clever things with prototypes doesn't mean that you should.
exposing the mechanics of all this stuff to the programmer is a disaster - it results in reams of confused questions on stackoverflow, and tools that need to solve the halting problem.
if prototypical inheritance is so great, why does almost everyone write a class-like wrapper around it to make it useful?
nearly sane.
does this mean it would be illegal for me to carry a book while riding my home-made 13-handled left-handed doobry-furkin (somewhat similar to a bicycle), unless I ask Congress first?
what a load of horse hooey.
THREE.js is the worst example if this. the documentation is basically machine-generated API definitions with a "getFoo() - this method gets the foo" (sometimes) uselessly sprinkled therein. if you suggest that this could be improved, something that many people have tried, you will either told to:
a) go look at the samples
b) look at the (poorly commented) source code, work it out yourself
c) write the f'ing docs yourself
d) shut up
e) really shut up, shortly before getting banned
seriously, who tells a n00b that they should be the ones writing the docs?
I was an H1-B "slave". Now I pay significantly more taxes than the average US citizen.
think what you will about the Mormons (I happen to agree with Linus), but I doubt the Finnish consulate is going to need any military protection, nobody's going to get dragged out and killed. the worst that will happen is a couple of over-entheusiastic, under-sexed, teen-aged adults will turn up at the door and ask them if they've heard the new message from God.
get them to watch Primer. tell them that if they had had version control, they would have understood it.
the amount of salt water is irrelevant. it could be a bucket, it could be a parsec^3.
the only thing that's important is the rate of precipitation.
this isn't about altruistically teaching others a valuable skill. it's about vain programmers trying to show their non-programmer colleagues how hard it is to code in order to get more respect. how much more condescending can you get? different people have aptitudes for different skills. go teach some dis-interested people how to do the rubic's cube, or something.
do you think the marketing exec could pass the Turing test?