You presume that newer is "better." Many use old computers whose companies have died out, because in many ways they were better. The more skilled you are, the less computer you need.
He just needs to be aware of the legal issues behind those newer systems like KDE. He doesn't have to use them if he has no use for them.
Sorry, pedantic moron, but "Internet Explorer" does not give me such problems. Perhaps it does not use the "same plug-in mechanism" to run the "pdf file" with "Acrobat Reader."
I remember now why I have to hit people hard when they're wrong on Fascdot. This is what I get when trying to phrase things nicely.
Closures with nested function definitely work. Don't use lambda's -- they're an admitted failed experiment.
I don't agree here. Closures do not work, and will not for the forseeable future. They need to be faked. Nested scope has little to do with anything -- "lexical scope" aka Scheme's "environment model" are what's needed.
The function attribute method of faking closures isn't so bad, I use it. It would of course be nicer to have a cleaner language, but it's sufficient.
- Python advertises its support for first-class functions, but I can't seem to get closures to work.
The reason for this has nothing to do with lambda, and everything to do with not supporting Scheme's environment model. There are two ways to fake closures: OOP Function attributes
For one thing, you're assuming getting computers trades off with water or reading. This seems false; the goals can coexist.
Second, information technology might help people communicate better and share info. They could share ideas on living more sustainably; get together and build businesses.
No way, this post is good stuff. It was good you were questioned, because this article was illuminating. I remember working in an academic environment, and people kept thinking that admins were masters of their domain, and it was illogical that things could go wrong. And they probably were masters, but the domain happened to be a buggy place.
In fact, all domains are no doubt buggy to some extent, unless you're willing to learn and oversee the quality.
Why should I want their respect? The engineers I met at college were all fairly boring individuals who were usually in it for a stable well-paying job.
I'd rather the respect of artists.
Unfortunately that's my strategy, and it doesn't seem to be working. I wonder what kind of cartel props up those prices. I would be very surprised if $50 is a sweet spot for every game.
I wonder if it has to do with the graphics arms race. But don't graphics people have some level of reusable libraries they can sell each other?
Most of them make no sense. To an intelligent being.
That's the point. GM Dvorak studies "irrational" positions and moves, which are incredibly subtle and questionable, but turn out to be strong (even if they're not understood).
The "Remis-Tod," the draw-death, seems to be more likely.
I never once saw a memory-leak problem that wasn't due to a programming error.
I don't know what to say to that. Of course memory leaks are caused by programmer errors.
But I do see your point, I'm not too concerned with memory use that's only constant factors higher than other systems. However, some classes of customer are.
JBuilder is very fast and stable on my 700 MHz OS X iBook - much faster MS Word.
I didn't mention OS X performance. The Mac Look 'n Feel tries to use native widgets whenever possible, and it's gotten better after every OS update. So you're to be envied.
HOWEVER, Java is built into MacOS X. I'm not sure if I could work around compatibility breaks by bundling the JRE, as I do with Windows.
The numerical performance of my own Java app is very close to C++, and multi-threading is really impressive.
I've heard that too about numerical performance. And luckily, with the new nonblocking i/o, there won't be too many situations where I have to spawn a lot of threads. (Apparently multithreading is variable depending on the native platform, though I've never stressed it enough to know.)
One of these days I'll need hands-on experience with SWT. But I hope Mozilla's XUL is really useful, and so I'd probably use that earlier. (I'm not an early adopter... more medium... so either one will take a while.)
And BTW, you've ignored the the backwards compatibility problems, versioning, etc. All these things were mentioned in the memo too.
There's one strange thing in the memo though... if you check out the README packaged with Java, you can distribute the version you want with your apps, provided you keep certain files in your distro. So either my lawyers have been overlooking something illegal, or something is nuts.
It's on Solaris only that Sun advises not to use Java for software projects. As far as I can judge from the memo (and yes, I did read it completely), they *are* developing software in Java for other platforms and will continue to do so.
It seems like we didn't read the same memo. The backwards compatibility problems, versioning, etc were not intrinsic to Solaris. And anyone who programs Java on Windows notices bad performance there too.
It was a very diplomatic letter. Sun's comparative advantage does not lie with Windows, so I don't think it makes much sense for the memo's author to make a big deal of it.
Nothing about Java itself being inherently problematic, just issues with certain implementation.
Anyone who programs much in Java knows that these problems exist across all implementations. Look at the Bug Parade; memory consumption is out of whack. And since it's not truly opensource, people just can't fix up the problems themselves -- Sun is to bureaucratic to ever let that happen.
Still, it's a well-documented and pleasant platform otherwise.
My wife writes Java GUIs and actually has never ever had any of the problems that they are referring to in this memo. The GUIs she writes runs fine, and they are very complex GUIs, things that do tasks such as controlling telephone switches.
I have written complex GUIs, which actually overwrite the paint() methods of Components, and Swing is slow on Windows and Unix. Also, I've used Swing apps, and guess what, they're slow memory hogs too.
Inevitably someone proclaims that Swing runs fast if you program well enough. (I'm not referring to you but to Sun's party line.) BULLSHIT. It's slow. It trades memory for speed, and still isn't that speedy. Run Jext or Borland JBuilder and you'll see what I mean.
Now,/I/ may personally like it for many uses, where control outweighs performance. But it's malicious for Sun to claim it fit for mainstream desktop apps.
Slashdot Mirror
You presume that newer is "better." Many use old computers whose companies have died out, because in many ways they were better. The more skilled you are, the less computer you need.
He just needs to be aware of the legal issues behind those newer systems like KDE. He doesn't have to use them if he has no use for them.
I remember now why I have to hit people hard when they're wrong on Fascdot. This is what I get when trying to phrase things nicely.
Thanks! I was looking for Woodcock's Z specification book and was tempted to buy it at Amazon.
Moz does the same.
.. and yet another way: IBM article
Let me qualify that: Guido called it "nested lexical scope."
The function attribute method of faking closures isn't so bad, I use it. It would of course be nicer to have a cleaner language, but it's sufficient.
OOP
Function attributes
For one thing, you're assuming getting computers trades off with water or reading. This seems false; the goals can coexist.
Second, information technology might help people communicate better and share info. They could share ideas on living more sustainably; get together and build businesses.
Well, fix your broken resume.asp link on your webpage.
No way, this post is good stuff. It was good you were questioned, because this article was illuminating. I remember working in an academic environment, and people kept thinking that admins were masters of their domain, and it was illogical that things could go wrong. And they probably were masters, but the domain happened to be a buggy place.
In fact, all domains are no doubt buggy to some extent, unless you're willing to learn and oversee the quality.
Why should I want their respect? The engineers I met at college were all fairly boring individuals who were usually in it for a stable well-paying job. I'd rather the respect of artists.
Unfortunately that's my strategy, and it doesn't seem to be working. I wonder what kind of cartel props up those prices. I would be very surprised if $50 is a sweet spot for every game.
I wonder if it has to do with the graphics arms race. But don't graphics people have some level of reusable libraries they can sell each other?
The "Remis-Tod," the draw-death, seems to be more likely.
I never once saw a memory-leak problem that wasn't due to a programming error.
I don't know what to say to that. Of course memory leaks are caused by programmer errors.
But I do see your point, I'm not too concerned with memory use that's only constant factors higher than other systems. However, some classes of customer are.
JBuilder is very fast and stable on my 700 MHz OS X iBook - much faster MS Word.
I didn't mention OS X performance. The Mac Look 'n Feel tries to use native widgets whenever possible, and it's gotten better after every OS update. So you're to be envied.
HOWEVER, Java is built into MacOS X. I'm not sure if I could work around compatibility breaks by bundling the JRE, as I do with Windows.
The numerical performance of my own Java app is very close to C++, and multi-threading is really impressive.
I've heard that too about numerical performance. And luckily, with the new nonblocking i/o, there won't be too many situations where I have to spawn a lot of threads. (Apparently multithreading is variable depending on the native platform, though I've never stressed it enough to know.)
Then use SWT.
True, but Sun don't like that.
One of these days I'll need hands-on experience with SWT. But I hope Mozilla's XUL is really useful, and so I'd probably use that earlier. (I'm not an early adopter... more medium... so either one will take a while.)
And BTW, you've ignored the the backwards compatibility problems, versioning, etc. All these things were mentioned in the memo too.
There's one strange thing in the memo though... if you check out the README packaged with Java, you can distribute the version you want with your apps, provided you keep certain files in your distro. So either my lawyers have been overlooking something illegal, or something is nuts.
Oh you pussy dong.
I was about to refute your point, but I find I like being called that. Thanks!
It's on Solaris only that Sun advises not to use Java for software projects. As far as I can judge from the memo (and yes, I did read it completely), they *are* developing software in Java for other platforms and will continue to do so.
It seems like we didn't read the same memo. The backwards compatibility problems, versioning, etc were not intrinsic to Solaris. And anyone who programs Java on Windows notices bad performance there too.
It was a very diplomatic letter. Sun's comparative advantage does not lie with Windows, so I don't think it makes much sense for the memo's author to make a big deal of it.
Nothing about Java itself being inherently problematic, just issues with certain implementation.
Anyone who programs much in Java knows that these problems exist across all implementations. Look at the Bug Parade; memory consumption is out of whack. And since it's not truly opensource, people just can't fix up the problems themselves -- Sun is to bureaucratic to ever let that happen.
Still, it's a well-documented and pleasant platform otherwise.
My wife writes Java GUIs and actually has never ever had any of the problems that they are referring to in this memo. The GUIs she writes runs fine, and they are very complex GUIs, things that do tasks such as controlling telephone switches.
/I/ may personally like it for many uses, where control outweighs performance. But it's malicious for Sun to claim it fit for mainstream desktop apps.
I have written complex GUIs, which actually overwrite the paint() methods of Components, and Swing is slow on Windows and Unix. Also, I've used Swing apps, and guess what, they're slow memory hogs too.
Inevitably someone proclaims that Swing runs fast if you program well enough. (I'm not referring to you but to Sun's party line.) BULLSHIT. It's slow. It trades memory for speed, and still isn't that speedy. Run Jext or Borland JBuilder and you'll see what I mean.
Now,
Funny how the insightful comment was moderated down.