One thing that I've noticed about Mac users is that many of them are in the business of creating content (graphics, music, writing, etc.)
This is the perfect market to test this pay-to-play scheme.. these users understand the costs of creating content and that someone's making a living doing it.
If this scheme doesn't work with Mac users, it won't work with a larger audience...
This paper describes a sampling mechanism. If you take a look at the graphs, they are gathering the IP sequence numbers over a long period of time (60 to 75 minutes.)
I fail to see how this can scale. Will a cable ISP with 10,000 customers really want to spend a year to check for compliance?
The article also states that Intranet traffic can also screw up the results. A simple background process that pings other machines on the network at random intervals should be enough to screw up the sampling mechanism.
In the real world, development teams are made of of people from places where they don't learn English as a first language.
Looking around my current team, I see people from China, India, Norway, Japan, Germany, Malaysia, Iran. All are very competent developers, but many of them have writing skills that suck.
Personally, I would prefer to look at their code rather than some tortured syntax that is pretending to be the English language.
I agree completely. The Java implementation on OS X is incredible.
For kicks, I installed Tomcat on a 400 mhz iMac one day. Took about 10 minutes and the performance was better than an 800 mhz Win2K server.
Haven't played with an Xserve yet, but dual processor model must kick some serious butt.
Hopefully, BEA and IBM will wise up soon so we can start putting app server environments on these boxes. My guess is that Weblogic or Websphere on an Xserve would be pretty sweet.
Another note: a Mac makes an excellent admin tool. With RDC and XDarwin, I use my iBook to manage a whole range of Windows and Unix servers. It's small, portable and wireless.
And the looks you get from people when they realize that you're administering a Solaris machine: priceless!
True, production databases should be inside one or more firewalls.
But what about users who have demos or other software that needs SQL Server to run on their laptop? They often run SQL Server outside of the firewall.. and they can bring the worm back to the intranet.
I hadn't thought about using the address space as a way of communicating between nodes. It certainly puts a new and interesting twist on larger systems...
Still, I don't see 64-bit systems working their way into the lower end of the market anytime soon. I distribute my work across many machines. It's cheap and easy to have lots of servers...
I have my doubts about the success of 64-bit chips, too (sounds like we both started messing around with 8080's and 4040's:-)
The only thing that I see the 64-bit architecture getting you is more addressable memory (2^64 vs. 2^32). Most large scale systems these days are highly distributed; you throw lots of CPUs at the problem. You don't throw a large memory space at the problem.
You don't need a 64-bit processor to for the instruction size. RISC uses less, not more.
Of course, there are advantages to parallelization of the instruction pipeline, but multi-processor systems or vector processing units (Altivec rocks) are better at this.
I remember being involved in an early port on a 64-bit DEC Alpha. It was a pain in the butt and the performance gain wasn't enough to justify the expense.
-ch
Now that's a nice IDEA...
on
Java IDEs?
·
· Score: 1
As I sit here cursing JBuilder, I look forward to the end of the current project so I can try out IDEA
The problem is actually quite simple to describe. Designing good user interfaces takes as much time and dedication as it does to design good plumbing (eg. the kernel, OS, shell).
It's also difficult for someone who is working in one discipline (ie. the kernel) to understand/accept the rigors of working in another discipline (ie. UI design)
A good UI takes years of research and design. It's not a matter of making the windows look pretty. It's making them work pretty.
Slashdot Mirror
One thing that I've noticed about Mac users is that many of them are in the business of creating content (graphics, music, writing, etc.)
.. these users understand the costs of creating content and that someone's making a living doing it.
This is the perfect market to test this pay-to-play scheme
If this scheme doesn't work with Mac users, it won't work with a larger audience...
This paper describes a sampling mechanism. If you take a look at the graphs, they are gathering the IP sequence numbers over a long period of time (60 to 75 minutes.)
I fail to see how this can scale. Will a cable ISP with 10,000 customers really want to spend a year to check for compliance?
The article also states that Intranet traffic can also screw up the results. A simple background process that pings other machines on the network at random intervals should be enough to screw up the sampling mechanism.
Just like Clippy used to help me write letters.
"I looks like you're trying to break into the system. Would you like some help?"
In the real world, development teams are made of of people from places where they don't learn English as a first language.
Looking around my current team, I see people from China, India, Norway, Japan, Germany, Malaysia, Iran. All are very competent developers, but many of them have writing skills that suck.
Personally, I would prefer to look at their code rather than some tortured syntax that is pretending to be the English language.
Mod the parent up! These are the good guys.
I agree completely. The Java implementation on OS X is incredible.
For kicks, I installed Tomcat on a 400 mhz iMac one day. Took about 10 minutes and the performance was better than an 800 mhz Win2K server.
Haven't played with an Xserve yet, but dual processor model must kick some serious butt.
Hopefully, BEA and IBM will wise up soon so we can start putting app server environments on these boxes. My guess is that Weblogic or Websphere on an Xserve would be pretty sweet.
Another note: a Mac makes an excellent admin tool. With RDC and XDarwin, I use my iBook to manage a whole range of Windows and Unix servers. It's small, portable and wireless.
And the looks you get from people when they realize that you're administering a Solaris machine: priceless!
that the world's second photo was of a naked woman.
No, they waited until they had 3D technology
A 747 in the backyard is pretty cool, but I'd much rather have the fighter jet with a beer holder.
How long do you think it will take before someone comes out with a kit that makes it easy to draw the black circle around the outside rim of the CD?
Something like those "easy CD labeling" thingys.
-ch
True, production databases should be inside one or more firewalls.
.. and they can bring the worm back to the intranet.
But what about users who have demos or other software that needs SQL Server to run on their laptop? They often run SQL Server outside of the firewall
Code Red got inside firewalls this way...
-ch
I hadn't thought about using the address space as a way of communicating between nodes. It certainly puts a new and interesting twist on larger systems...
Still, I don't see 64-bit systems working their way into the lower end of the market anytime soon. I distribute my work across many machines. It's cheap and easy to have lots of servers...
-ch
I have my doubts about the success of 64-bit chips, too (sounds like we both started messing around with 8080's and 4040's :-)
The only thing that I see the 64-bit architecture getting you is more addressable memory (2^64 vs. 2^32). Most large scale systems these days are highly distributed; you throw lots of CPUs at the problem. You don't throw a large memory space at the problem.
You don't need a 64-bit processor to for the instruction size. RISC uses less, not more.
Of course, there are advantages to parallelization of the instruction pipeline, but multi-processor systems or vector processing units (Altivec rocks) are better at this.
I remember being involved in an early port on a 64-bit DEC Alpha. It was a pain in the butt and the performance gain wasn't enough to justify the expense.
-ch
As I sit here cursing JBuilder, I look forward to the end of the current project so I can try out IDEA
For the designer, the web is full of compromises. How would you rank these conflicting goals in order of importance?
A) Usability
B) Entertainment
C) Robustness
D) Speed
E) Beauty
F) Accessibility
It's also difficult for someone who is working in one discipline (ie. the kernel) to understand/accept the rigors of working in another discipline (ie. UI design)
A good UI takes years of research and design. It's not a matter of making the windows look pretty. It's making them work pretty.