My head hurts. There are 8 "cities" represented by letters A-H. Each city has 8 channels. The amoeba selected channel C1 (C is the first stop).. B8 (B is the last stop). Since the researchers didn't actually coax that path, how did their relative light pulses work? Did channels B1 through B8 all equally have the most light when compared to the light pulses in C1 through C8? If so, how do they determine that B should be the last stop? If not, if rather all the light impulses across all 64 channels ranged from weakest in C1 through strongest in C8, then that would just show the amoeba's mechanistic response to the light impulses. I'm missing something.
Unions are at all times and all situations a bad thing.
Of course it seems like the low skilled jobs are underpaid. If so, I'm guessing it's difficult to keep them filled. Good; the wages will go up naturally or the jobs will remain unfilled. That's the way a market should work and does work. Whenever unions take root, the industry and consumer suffers. Witness industries such as steel in US and Detroit auto. In the early days of the automobile, Detroit *was* Silicon Valley. Innovation flourished. Many prospered. The city thrived. Union and general collectivism in government took over. Now Detroit is hell on earth. As in literally; perhaps the world's worst 1st-world city in every way.
Economics is simple; there is no free lunch. If you see an opportunity higher on the food chain, pursue it. Almost all of us will find some opportunities out of reach. Do the best you can; extortion is not a virtue.
Application responsiveness is no doubt important, but not the most important thing. Most people don't care that an application takes 100ms longer here and there.
What's more important:
Time to market for new features.
Robust code that makes for stable applications.
After a couple weeks using C#, I was far more productive than with years in delphi. The FCL was just as good (not speaking of UI) as the VCL and the JCL together.
I think you can do more with a little less even in C# 1.0, but there's no doubt you can do more using 2.0 (with generics and, sparingly, anonymous methods).
And with such a massive user base, C# /.net has far surpassed delphi in terms of sample code, free libraries, etc.
Java came and Java went? Huh? Regardless, the cross platform aspect of Java isn't replicated in.net..net will probably last alot longer than Java has/will..net is too slow? For what? Are you writing real time applications? I've seen some amazing applications written in.net and they don't seem slow. The load time is surely slow, but even then there are methods available to minimize that.
I remember debugging paint operations. How is that not possible in BDS? Don't you simply need multiple monitors?
You're all crazy. The delphi compiler has always been fine, but the IDE sucked until BDS 2006. The archaic multiple window scheme in the old versions always drove me crazy; now everything slides in/out when I need it. The refactoring tools aren't as good as the current version of VS, but they still rock. I hate the pascal language with a passion, but this IDE makes it bearable.
As for not joining the.net revolution, you're not going to be able to avoid java or.net forever (.net the logical choice because it built on java's mistakes). That "massive Delphi and Windows API knowledge base" is EOL - sooner or later you must move on. Better sooner than later.
Slashdot Mirror
My head hurts. There are 8 "cities" represented by letters A-H. Each city has 8 channels. The amoeba selected channel C1 (C is the first stop) .. B8 (B is the last stop). Since the researchers didn't actually coax that path, how did their relative light pulses work? Did channels B1 through B8 all equally have the most light when compared to the light pulses in C1 through C8? If so, how do they determine that B should be the last stop? If not, if rather all the light impulses across all 64 channels ranged from weakest in C1 through strongest in C8, then that would just show the amoeba's mechanistic response to the light impulses. I'm missing something.
Unions are at all times and all situations a bad thing. Of course it seems like the low skilled jobs are underpaid. If so, I'm guessing it's difficult to keep them filled. Good; the wages will go up naturally or the jobs will remain unfilled. That's the way a market should work and does work. Whenever unions take root, the industry and consumer suffers. Witness industries such as steel in US and Detroit auto. In the early days of the automobile, Detroit *was* Silicon Valley. Innovation flourished. Many prospered. The city thrived. Union and general collectivism in government took over. Now Detroit is hell on earth. As in literally; perhaps the world's worst 1st-world city in every way. Economics is simple; there is no free lunch. If you see an opportunity higher on the food chain, pursue it. Almost all of us will find some opportunities out of reach. Do the best you can; extortion is not a virtue.
What's more important:
- Time to market for new features.
- Robust code that makes for stable applications.
After a couple weeks using C#, I was far more productive than with years in delphi. The FCL was just as good (not speaking of UI) as the VCL and the JCL together.I think you can do more with a little less even in C# 1.0, but there's no doubt you can do more using 2.0 (with generics and, sparingly, anonymous methods).
And with such a massive user base, C# /
Java came and Java went? Huh? Regardless, the cross platform aspect of Java isn't replicated in .net. .net will probably last alot longer than Java has/will. .net is too slow? For what? Are you writing real time applications? I've seen some amazing applications written in .net and they don't seem slow. The load time is surely slow, but even then there are methods available to minimize that.
I remember debugging paint operations. How is that not possible in BDS? Don't you simply need multiple monitors?
You're all crazy. The delphi compiler has always been fine, but the IDE sucked until BDS 2006. The archaic multiple window scheme in the old versions always drove me crazy; now everything slides in/out when I need it. The refactoring tools aren't as good as the current version of VS, but they still rock. I hate the pascal language with a passion, but this IDE makes it bearable. As for not joining the .net revolution, you're not going to be able to avoid java or .net forever (.net the logical choice because it built on java's mistakes). That "massive Delphi and Windows API knowledge base" is EOL - sooner or later you must move on. Better sooner than later.