Not as many OSes for PPC as x86, but there are still a number of them that will run on Mac hardware: OS X (of course), a number of Linux distros including SUSE, Gentoo, Debian, YellowDog, among others. Then there's NetBSD (also of course), and OpenBSD. There are folks working on porting FreeBSD as well.
Whether you buy a nice higher color temp incandescent bulb that is labeled 'full spectrum', or you get the cheapest incandescent bulb you can find, you will find that they are both full spectrum. The issue that causes typical fluorescents to only emit light in certain color bands does not affect incandescents. The bulbs labeled 'full spectrum' incandescents are just incandescents with a coating to give them a higher color temp, which just helps to confuse the meaning of the term. I do agree that higher color temp light is nicer.
That is kind of weird. The resaon that spectrum matters with fluorescents is that when you are hitting phosphors with electrons you get a very specific band of light that is emitted. That is why you need to mix up the phosphors used in the bulb to try to get an even looking white.
AFAIK, when you run a current through a filament in an incandescent bulb the spectrum emitted is continuous, so you are going to be getting the full spectrum by default with a standard incandescent.
From the page you referred to they are really just using a fancy filter to adjust the already full color spectrum to make the light cooler. It looks like they are really just trying to take advantage of the general misunderstanding of the term 'full spectrum.'
Full spectrum refers to fluorescents. Most cheap fluorescents have light that spectrally has a few peaks on visible wavelengths, and minimal or no light on others, though the light sill looks white to the eye. Full spectrum fluorescents have a mix of phosphors in them so that light from across the spectrum is emitted by the bulb to some degree - though there are still some peaks and lows nothing is skipped altogether.
Color temperature and 'full spectrum' are not really the same thing. A lot of cheap fluorescents have a low color temp around 2700 that looks yellowish, but you can buy fluorescents that have a higher color temp. Depending on what you like 3500-4100 bulbs are out there that will put out light that looks 'whiter', though if you go high you get a bluish look about 4500.
Bookpool has it for less than Amazon, BN, or booksamillion. They have free shipping if your order is $40 or more, so this may or may not be a better deal.
Your views on game rooms are as false as your assertions about Dean's approval ratings: http://www.gallup.com/subscription/?m=f& c_id=13764
In no workplace I have been where there was a game room was there ever any noticible negative impact on productivity. The bottom line is this: happy workers are more productive. A game room is a small investment, and in some places it will pay off in increased productivity. If people hang out in the game room all day rather than doing working, you have much more serious problems in your workplace than the fact that you have a game room.
The coffee was so hot that it was literally burning people's mouths. They had recieved repeat complaints that their coffee was causing injuries, and did nothing. The main reason why why the suit award was so large was because McDs knew that they were injuring people by serving 400 degree coffee and did nothing about it.
PowerSchool is a WebObjects application. How can you be deploying it on OS 9? I have deployed WO apps on NT/2k, Solaris, HPUX, and OS X - 9 deployment is impossible AFAIK. Or are you referring to the client? I have not used it but I thought, being a web application, that it was browser based.
I installed mkLinux on a 5300 many years ago. It was a pain. I wound up using SCSI disk mode and basically using the powerbook as a target hard drive. But then fstab gets confused thinking that the internal drive is SCSI, so you have to mount it after the install and fix fstab. It ran dog-slow, and I could never get a driver for the PCMCIA ethernet card I had. That was years ago. It looks like there is a project here: http://nubus-pmac.sourceforge.net/ that would be better suited to get a more modern Linux installed.
It is easy to rip on an article with the sort of vacuous criticisms you fired off, but you really did not address a single real issue in the article. First off, you make it sound like he is advocating JS, which in reading the article is clearly not the case.
Secondly, covering your criticisms:
When he said that working with anonymous structures or structures by reference can be ugly, you interpreted 'ugly' as 'looks like.' But the ugliness in 'my $count = keys %{ $self->{groups}[HACKERS] };' is ugly in more than just looks.
The poster above already pointed out your gross oversimplifications regarding Java.
Finally, your point that "there are much worse things to complain about languages, besides syntax, and inappropriate usage," is correct, and the article itself does just that.
In short, your analysis is overly simplistic, and full of fluff.
æ is the latinization used when transliterating the Greek alpha-iota. So Greek alpha iota theta espilon rho, got transliterated to æther. æ often evolved into just 'e' over time giving us ether. So it is sorta Greek.
Interestingly fat binaries for OpenStep could be built for 68k, x86, Sparc, and HPPA-RISC, so they would have a head start getting Cocoa ported over to Sun hardware.
No. This is not guesswork. A window is inherently a much more heavyweight entity than a view inside a window, and will necessarily consume more RAM. Take a look at the cocoa docs for all the components of a NSWindow. Assuming that the tabs are subclassed NSView, take a look at what is involved there. Beyond that, windows are double buffered, have border transparencies/shadows and other RAM-hogging aspects not associated with a view. In OS X, more windows inherently means more RAM. If a window with three tabs ate as much RAM as three separate windows in Safari, that would indicate extremely crappy coding, and I guarantee you I would not use the browser based on that fact.
You may not like tabbed browsing, and if not, all is well for you as you have more browsers to pick from, but tabbed browser windows are far from a horrible idea. In fact I think it is one of the few really great UI ideas I have seen in the browser world in a long time.
Just because Windows started the MDI thing long ago does not make tabbed browsing awful. The fact is that Windows simply had a really horrible implemetation of MDI. Windows inside of windows - eeew. Tabs are intutive, easy to use, and most implementations are well though out. They improve performance, and help to organize content that otherwise can get out of control. I used to hate having tons of browser windows open, and having to cascade them just so, so that I could go back and forth between the slew of pages I need to have open at work - now I use Chimera and am much happier.
I realize that folks have various issues with them, some contrived, some genuine, but they do solve a usability problem I have suffered under for years better than any other solution I have seen yet. If you do not like them, great for you, you need not use them. For me, I can't live without them, and I will never use a browser that does not support tabs unless something better comes along that solves the same problem as elegantly.
From: pinkerton@netscape.com (Mike Pinkerton) Date: Tue Jan 21, 2003 10:46:55 AM US/Central To: CHimera Subject: [Chimera] Sigh Reply-To: chimera@mozdev.org
Let me put this to bed once and for all: I'm not stopping work on chimera.
Yes, I'm frustrated and sick of being kicked around by apple. That's why I muttered that i was "torn". I never said I was stopping work or that chimera was dying. I can't speak for Simon or bryner or any of the other members of the team, but they're not stopping either.
I appreciate the support and all the emails. We're making a damn good product here, and we're doing it because we want to, win, lose, or draw.
-- Mike Pinkerton Mac Browser Weenie pinkerton@netscape.com http://people.netscape.com/pinkerton
_______________________________________________ Chimera mailing list Chimera@mozdev.org http://www.mozdev.org/ma ilman/listinfo/chimera
One person's featureful browser is another's bloatware. Note how often people bitch about Mozilla as 'bloated.' Software design is all about tradeoffs, no feature is completely free, and Chimera has the best set of tradeoffs for me (except for putting the bookmarks in a sidebar - I hate that). You might not see some features you want and call Chimera 'dumb,' but there is a fair chance that the gains of adding the feature vs. the bloat added by it were weighed. Also Chimera has a lot of features with no UI in prefs.js.
It is funny that the example you chose (the close button) is one of the reasons I like Chimera over Moz. The space where tabs go is already space limited and I was really annoyed when the close button showed up in Mozilla. When a lot of tabs are open that limited space is precious - adding a UI widget for an action where you already could either hit Cmd-W, or use a contextual menu did not seem like a good trade to me, and I am happy to see Chimera agrees more with my sensibilities. And it is clear that there are still a lot of feature yet to be implemented in Chimera, and features to implement, since it is only a.6 release.
Finally it is really funny to see someone call a browser 'dumb' when that person cast their opinions in concrete at version number.3.
Apple can have some bone-headed stubbornness that makes them say moronic things like this, and never ever ever admit their error. Having external parties control Chimera will save it from the worst Apple-isms like a universally reviled Metal UI, tabs because some dimwit UI "expert" says they are bad, etc, while still keeping the better parts of Apple's OS design.
As far as cp goes, most files will copy fine, but if you work with files that have resource forks (fewer and fewer as time goes by) then install the Dev Tools and use CpMac and MvMac, which handle resource forks properly. Or use 'ditto -rsrc' which handles forks as well.
As far as the alias thing goes, 1) it is not too hard to avoid aliases and 2) they are designed to be convenient to your average user. By default there are not many in the system, so provided you make symlinks rather than aliases all is well. Having used OS X since Public Beta, I have yet to have had a real problem with the alias/symlink thing. *NIX tools do not like aliases, so I always use symlinks instead, no big deal.
Aliases point to a file in an intuitive way to a non-technical person - if you move or rename the file it keeps pointing to the file - if you replace it, then it points to the replacement, simple for grandma to get.
As for breaking aliases, you are in error saying that renaming your HD will do this. When I managed Mac labs, users used to rename various HDs in labs fairly often, which I would name back. There were no ill effects on any aliases. I have done full and partial restores from backups using Retrospect with no unexpected effects on aliases, sounds like you were using a crappy backup tool.
Re:Apple Laptop Keyboards Unsuitable for Unix User
on
More Switching Stories
·
· Score: 1
You make no sense. You say that you cannot remap the control key on a powerbook, and then refer to software that does exactly that. You then berate Apple for catering to their traditional customers. What company in their right mind would not cater to their traditional customer base? Let me just say that you come off as a tad paranoid about Apple ignoring UNIX folk, and oddly obsessed on the placement of a modifier key (especially one you know you can change the mapping of via software). Apple has a few markets they are working on entering, especially Hi Ed, and Scientific that are UNIX strongholds, and from what I can tell they are working on strengthening them. Not including a three button mouse, and leaving the keyboard unchanged from it's layout of the past fifteen years does not mean that Apple is ignoring all customers who are UNIX sorts.
BTW - on a PowerBook is is a lot easier to work with a single button and use mod keys for the other two keys. I have now done it for years and find that I actually prefer the single button approach to my two-button ThinkPad. It works better with my thumb placement. My fingers of my left hand are always over the modifier keys on the PowerBook anyway, since that's where my hand rests - it works perfectly.
While it is not a complete C++ solution, Apple has been persistently working on improving ObjC++ support. With ObjC++ all your GUI code still has to be in ObjC, but your business logic can stay in C++. Since GUI code is platform specific anyway having to use some ObjC should not be that objectionable to non-zealots. Every release it has better support, so obviously Apple knows that this is a priority with some customers. Plus Carbon is still around. If the Pepper guy didn't want to write reentrant code, well, that is a bummer, but the more reentrant code in the world, the better thread support will be, and the faster Mac OS X will be.
Slashdot Mirror
Not as many OSes for PPC as x86, but there are still a number of them that will run on Mac hardware:
OS X (of course), a number of Linux distros including SUSE, Gentoo, Debian, YellowDog, among others. Then there's NetBSD (also of course), and OpenBSD. There are folks working on porting FreeBSD as well.
Whether you buy a nice higher color temp incandescent bulb that is labeled 'full spectrum', or you get the cheapest incandescent bulb you can find, you will find that they are both full spectrum. The issue that causes typical fluorescents to only emit light in certain color bands does not affect incandescents. The bulbs labeled 'full spectrum' incandescents are just incandescents with a coating to give them a higher color temp, which just helps to confuse the meaning of the term. I do agree that higher color temp light is nicer.
That is kind of weird. The resaon that spectrum matters with fluorescents is that when you are hitting phosphors with electrons you get a very specific band of light that is emitted. That is why you need to mix up the phosphors used in the bulb to try to get an even looking white.
AFAIK, when you run a current through a filament in an incandescent bulb the spectrum emitted is continuous, so you are going to be getting the full spectrum by default with a standard incandescent.
From the page you referred to they are really just using a fancy filter to adjust the already full color spectrum to make the light cooler. It looks like they are really just trying to take advantage of the general misunderstanding of the term 'full spectrum.'
I forgot to add that the color of a bulb, white vs. yellow is 'color temperature' and is not related to whether a bulb is full spectrum.
Full spectrum refers to fluorescents. Most cheap fluorescents have light that spectrally has a few peaks on visible wavelengths, and minimal or no light on others, though the light sill looks white to the eye. Full spectrum fluorescents have a mix of phosphors in them so that light from across the spectrum is emitted by the bulb to some degree - though there are still some peaks and lows nothing is skipped altogether.
Color temperature and 'full spectrum' are not really the same thing. A lot of cheap fluorescents have a low color temp around 2700 that looks yellowish, but you can buy fluorescents that have a higher color temp. Depending on what you like 3500-4100 bulbs are out there that will put out light that looks 'whiter', though if you go high you get a bluish look about 4500.
Bookpool has it for less than Amazon, BN, or booksamillion. They have free shipping if your order is $40 or more, so this may or may not be a better deal.
Your views on game rooms are as false as your assertions about Dean's approval ratings:& c_id=13764
http://www.gallup.com/subscription/?m=f
In no workplace I have been where there was a game room was there ever any noticible negative impact on productivity. The bottom line is this: happy workers are more productive. A game room is a small investment, and in some places it will pay off in increased productivity. If people hang out in the game room all day rather than doing working, you have much more serious problems in your workplace than the fact that you have a game room.
there was a firewall that sensed and deleted duplicate slashdot stories...
The coffee was so hot that it was literally burning people's mouths. They had recieved repeat complaints that their coffee was causing injuries, and did nothing. The main reason why why the suit award was so large was because McDs knew that they were injuring people by serving 400 degree coffee and did nothing about it.
PowerSchool is a WebObjects application. How can you be deploying it on OS 9? I have deployed WO apps on NT/2k, Solaris, HPUX, and OS X - 9 deployment is impossible AFAIK. Or are you referring to the client? I have not used it but I thought, being a web application, that it was browser based.
I installed mkLinux on a 5300 many years ago. It was a pain. I wound up using SCSI disk mode and basically using the powerbook as a target hard drive. But then fstab gets confused thinking that the internal drive is SCSI, so you have to mount it after the install and fix fstab. It ran dog-slow, and I could never get a driver for the PCMCIA ethernet card I had. That was years ago. It looks like there is a project here: http://nubus-pmac.sourceforge.net/ that would be better suited to get a more modern Linux installed.
It is easy to rip on an article with the sort of vacuous criticisms you fired off, but you really did not address a single real issue in the article. First off, you make it sound like he is advocating JS, which in reading the article is clearly not the case.
Secondly, covering your criticisms:
When he said that working with anonymous structures or structures by reference can be ugly, you interpreted 'ugly' as 'looks like.' But the ugliness in 'my $count = keys %{ $self->{groups}[HACKERS] };' is ugly in more than just looks.
The poster above already pointed out your gross oversimplifications regarding Java.
Finally, your point that "there are much worse things to complain about languages, besides syntax, and inappropriate usage," is correct, and the article itself does just that.
In short, your analysis is overly simplistic, and full of fluff.
æ is the latinization used when transliterating the Greek alpha-iota. So Greek alpha iota theta espilon rho, got transliterated to æther. æ often evolved into just 'e' over time giving us ether. So it is sorta Greek.
Interestingly fat binaries for OpenStep could be built for 68k, x86, Sparc, and HPPA-RISC, so they would have a head start getting Cocoa ported over to Sun hardware.
No. This is not guesswork. A window is inherently a much more heavyweight entity than a view inside a window, and will necessarily consume more RAM. Take a look at the cocoa docs for all the components of a NSWindow. Assuming that the tabs are subclassed NSView, take a look at what is involved there. Beyond that, windows are double buffered, have border transparencies/shadows and other RAM-hogging aspects not associated with a view. In OS X, more windows inherently means more RAM. If a window with three tabs ate as much RAM as three separate windows in Safari, that would indicate extremely crappy coding, and I guarantee you I would not use the browser based on that fact.
You may not like tabbed browsing, and if not, all is well for you as you have more browsers to pick from, but tabbed browser windows are far from a horrible idea. In fact I think it is one of the few really great UI ideas I have seen in the browser world in a long time.
Just because Windows started the MDI thing long ago does not make tabbed browsing awful. The fact is that Windows simply had a really horrible implemetation of MDI. Windows inside of windows - eeew. Tabs are intutive, easy to use, and most implementations are well though out. They improve performance, and help to organize content that otherwise can get out of control. I used to hate having tons of browser windows open, and having to cascade them just so, so that I could go back and forth between the slew of pages I need to have open at work - now I use Chimera and am much happier.
I realize that folks have various issues with them, some contrived, some genuine, but they do solve a usability problem I have suffered under for years better than any other solution I have seen yet. If you do not like them, great for you, you need not use them. For me, I can't live without them, and I will never use a browser that does not support tabs unless something better comes along that solves the same problem as elegantly.
The quote is "Linux is only free if your time has no value," it is indeed on his site in the themes.org interview here:
http://www.jwz.org/doc/linux.html
From: pinkerton@netscape.com (Mike Pinkerton)
a ilman/listinfo/chimera
Date: Tue Jan 21, 2003 10:46:55 AM US/Central
To: CHimera
Subject: [Chimera] Sigh
Reply-To: chimera@mozdev.org
Let me put this to bed once and for all: I'm not stopping work on chimera.
Yes, I'm frustrated and sick of being kicked around by apple. That's why I muttered that i was "torn". I never said I was stopping work or that chimera was dying. I can't speak for Simon or bryner or any of the other members of the team, but they're not stopping either.
I appreciate the support and all the emails. We're making a damn good product here, and we're doing it because we want to, win, lose, or draw.
--
Mike Pinkerton
Mac Browser Weenie
pinkerton@netscape.com http://people.netscape.com/pinkerton
_______________________________________________
Chimera mailing list
Chimera@mozdev.org
http://www.mozdev.org/m
One person's featureful browser is another's bloatware. Note how often people bitch about Mozilla as 'bloated.' Software design is all about tradeoffs, no feature is completely free, and Chimera has the best set of tradeoffs for me (except for putting the bookmarks in a sidebar - I hate that). You might not see some features you want and call Chimera 'dumb,' but there is a fair chance that the gains of adding the feature vs. the bloat added by it were weighed. Also Chimera has a lot of features with no UI in prefs.js.
.6 release.
.3.
It is funny that the example you chose (the close button) is one of the reasons I like Chimera over Moz. The space where tabs go is already space limited and I was really annoyed when the close button showed up in Mozilla. When a lot of tabs are open that limited space is precious - adding a UI widget for an action where you already could either hit Cmd-W, or use a contextual menu did not seem like a good trade to me, and I am happy to see Chimera agrees more with my sensibilities. And it is clear that there are still a lot of feature yet to be implemented in Chimera, and features to implement, since it is only a
Finally it is really funny to see someone call a browser 'dumb' when that person cast their opinions in concrete at version number
Apple can have some bone-headed stubbornness that makes them say moronic things like this, and never ever ever admit their error. Having external parties control Chimera will save it from the worst Apple-isms like a universally reviled Metal UI, tabs because some dimwit UI "expert" says they are bad, etc, while still keeping the better parts of Apple's OS design.
man osascript
As far as cp goes, most files will copy fine, but if you work with files that have resource forks (fewer and fewer as time goes by) then install the Dev Tools and use CpMac and MvMac, which handle resource forks properly. Or use 'ditto -rsrc' which handles forks as well.
As far as the alias thing goes, 1) it is not too hard to avoid aliases and 2) they are designed to be convenient to your average user. By default there are not many in the system, so provided you make symlinks rather than aliases all is well. Having used OS X since Public Beta, I have yet to have had a real problem with the alias/symlink thing. *NIX tools do not like aliases, so I always use symlinks instead, no big deal.
Aliases point to a file in an intuitive way to a non-technical person - if you move or rename the file it keeps pointing to the file - if you replace it, then it points to the replacement, simple for grandma to get.
As for breaking aliases, you are in error saying that renaming your HD will do this. When I managed Mac labs, users used to rename various HDs in labs fairly often, which I would name back. There were no ill effects on any aliases. I have done full and partial restores from backups using Retrospect with no unexpected effects on aliases, sounds like you were using a crappy backup tool.
You make no sense. You say that you cannot remap the control key on a powerbook, and then refer to software that does exactly that. You then berate Apple for catering to their traditional customers. What company in their right mind would not cater to their traditional customer base? Let me just say that you come off as a tad paranoid about Apple ignoring UNIX folk, and oddly obsessed on the placement of a modifier key (especially one you know you can change the mapping of via software). Apple has a few markets they are working on entering, especially Hi Ed, and Scientific that are UNIX strongholds, and from what I can tell they are working on strengthening them. Not including a three button mouse, and leaving the keyboard unchanged from it's layout of the past fifteen years does not mean that Apple is ignoring all customers who are UNIX sorts.
BTW - on a PowerBook is is a lot easier to work with a single button and use mod keys for the other two keys. I have now done it for years and find that I actually prefer the single button approach to my two-button ThinkPad. It works better with my thumb placement. My fingers of my left hand are always over the modifier keys on the PowerBook anyway, since that's where my hand rests - it works perfectly.
While it is not a complete C++ solution, Apple has been persistently working on improving ObjC++ support. With ObjC++ all your GUI code still has to be in ObjC, but your business logic can stay in C++. Since GUI code is platform specific anyway having to use some ObjC should not be that objectionable to non-zealots. Every release it has better support, so obviously Apple knows that this is a priority with some customers. Plus Carbon is still around. If the Pepper guy didn't want to write reentrant code, well, that is a bummer, but the more reentrant code in the world, the better thread support will be, and the faster Mac OS X will be.