The term "scripting" language is almost meaningless now. So...what do you mean?
Both Java and Python are byte-compiled and run in a VM. The only difference is the separate compilation step for Java and this difference is only due to the nature of their respective type systems.
I agree. The guy is one hell of a technician and a shrewd business man.
Since I've just finished another in a long series of beers I'll even go so far as to say that he is a good "visionary". His concepts are cool. But his writing and directing are atrocious.
It's possible that ready access to the information requested would reveal more unseemly activity. That might be the reason for stonewalling on this particular subject matter.
I disagree that there's debate about the nature of the things listed above. I don't think that anyone is still saying there was no deceit in those cases. Exactly who knew, to what extent, and when are the only details in contention.
I do agree that to make as assertion this stupid must come from unbelievable arrogance. Then again the strategy of denial and ridicule has been succsesful in the past.
A solid knowledge of assembly, file formats, calling conventions, and other voodoo is the price of admission if you need to find out how something works and all you've got is a binary.
Especially if you're trying to slay one of those infernal "only shows up in a release build" bugs.
Re:Why BeOS failed, IMO.
on
Ten Years of BeOS
·
· Score: 3, Interesting
I agree. I was interested in playing around with BeOS so I looked at what dev tools/sdks were available.
IIRC, it was at least $50 (not counting using the gnu tools) and went a lot higher. $50 is nothing as far as the costs of dev tools are concerned, but I was irked.
As you said, if you're new and trying to make it you should be courting developers (and resellers), not acting indifferent to them or prematurely trying to use them as a revenue stream.
The distiction beteween weak and dynamic typing often gets lost during the firefight...
To put it succinctly:
Weak Typing: Lots of implicit conversion. Variables can automatically be treated as if they were some other type.
Dynamic Typing: Type checking is put off until run-time. Errors are often expressed via exceptions.
The Strong/Weak characteristics of a typing system are unrelated to it's Static/Dynamic charcteristics. You can have languages that are Strong/Static (e.g. C++), Strong/Dynamic (e.g. Python), Weak/Static (e.g. C), and Weak/Dynamic (e.g. Perl).
Why it's better than stable, it's Ultra-Stable (tm)!
From the brochure:
"Impervious to application faults, security breaches, and even normal usage! Here's one platform that even the most clueless user can't harm. If that's not compelling enough think of all you'll save on administration! Finally, true zero touch zero cost administration!"
Brought to you by Premier Executive Marketing Solutions, Inc. Ltd. LLC. OBE, CMH, IMHO, Esquire
Slashdot Mirror
The term "scripting" language is almost meaningless now. So...what do you mean?
Both Java and Python are byte-compiled and run in a VM. The only difference is the separate compilation step for Java and this difference is only due to the nature of their respective type systems.
The two previous replies pretty much cover it.
If you like, here's something I said about this a while back...but I think AC's list above better illustrates the point.
I'm not sure what the term "dynamic language" means anyway...
Generally, it refers the type system; i.e. the language is dynamically typed (as opposed to statically typed).
Not to be confused (though it often is) with weak typing.
Clothing Allowance.
I agree. The guy is one hell of a technician and a shrewd business man.
Since I've just finished another in a long series of beers I'll even go so far as to say that he is a good "visionary". His concepts are cool. But his writing and directing are atrocious.
Alec Guinness was always my favorite.
He did bring a certain amount of class that is now notably absent.
"This is the version you're looking for."
[waves hand Alec Guinness style]
It's possible that ready access to the information requested would reveal more unseemly activity. That might be the reason for stonewalling on this particular subject matter.
I disagree that there's debate about the nature of the things listed above. I don't think that anyone is still saying there was no deceit in those cases. Exactly who knew, to what extent, and when are the only details in contention.
I do agree that to make as assertion this stupid must come from unbelievable arrogance. Then again the strategy of denial and ridicule has been succsesful in the past.
- Lewinsky
- Lead up to Waco debacle
- Iran-Contra
- Watergate
- Gulf of Tonkin
- Tuskegee "Experiment"
After things like this, to name just a few, why is it surprising?Hehe...one would hope...although there are a lot of "if it compiles it must be ready" shops around.
A solid knowledge of assembly, file formats, calling conventions, and other voodoo is the price of admission if you need to find out how something works and all you've got is a binary.
Damn straight.
Especially if you're trying to slay one of those infernal "only shows up in a release build" bugs.
I agree. I was interested in playing around with BeOS so I looked at what dev tools/sdks were available.
IIRC, it was at least $50 (not counting using the gnu tools) and went a lot higher. $50 is nothing as far as the costs of dev tools are concerned, but I was irked.
As you said, if you're new and trying to make it you should be courting developers (and resellers), not acting indifferent to them or prematurely trying to use them as a revenue stream.
How would anyone know?
"Code Slingers, Inc. was denied a patent on it's revolutionary idle thread technology today.",
doesn't make a good press release.
So, just how long have you been waiting for an excuse (no matter how flimsy) to post that rant?
I ask because your tirade, although vigorous and interesting, is entirely unrelated to my post.
Since you seem to be articulate and well read I'm giving you the benefit of the doubt and assuming that you have some sort of agenda...
What is it exactly?
Correction: "curiosity".
Binary math was once thought to be a useless curiousity.
The distiction beteween weak and dynamic typing often gets lost during the firefight...
To put it succinctly:
Weak Typing: Lots of implicit conversion. Variables can automatically be treated as if they were some other type.
Dynamic Typing: Type checking is put off until run-time. Errors are often expressed via exceptions.
The Strong/Weak characteristics of a typing system are unrelated to it's Static/Dynamic charcteristics. You can have languages that are Strong/Static (e.g. C++), Strong/Dynamic (e.g. Python), Weak/Static (e.g. C), and Weak/Dynamic (e.g. Perl).
hehe...me too, the zip code is 60613 :)
Why it's better than stable, it's Ultra-Stable (tm)!
From the brochure:
"Impervious to application faults, security breaches, and even normal usage! Here's one platform that even the most clueless user can't harm. If that's not compelling enough think of all you'll save on administration! Finally, true zero touch zero cost administration!"
Brought to you by Premier Executive Marketing Solutions, Inc. Ltd. LLC. OBE, CMH, IMHO, Esquire
Oh, you seem to know each other already...
In that case it's a good thing they can be really small...and are getting smaller.
Slashdot and Fark "trading" articles is getting more and more noticeable. Maybe some sort of joint non-duplication accord is in order.
...in twenty years every other programming book I have will be in it's 123rd edition.
I didn't know you posted on Slashdot.