64 bit architecture means far less efficient memory usage for applications that don't need it. This is why 32 bit chips are still being used in Macs, and this is unlikely to change before its more commonly necessary. By your logic, many embedded devices should move away from the ridiculously obsolete 4/8/16 bit chips they so often use. But they won't.
Its not so novel, but I'm sure there are plenty of schools, community centers, etc. around where you live that could always use spare hardware. A lot of the boxes these organizations receive are stripped down, and having extra sticks of RAM is very useful for them.
My grandmother uses a computer built from donated parts that a local group provides for the elderly, and she's now able to talk with her 4 generations of family over email (which is pretty well spread around the world now). There are probably tax breaks for you too, but in general donating unused hardware to those that will use it is a Good Thing.
Re:Discarding too many people
on
Defining Google
·
· Score: 1
While such people certainly are smart and possess insight and intuition, there's no correlation to being a good programmer.
This is true, but there is also little correlation between being a good programmer and being a talented and useful employee of a large innovative company.
Of the handful of people I know who bought the 14", the lower resolution was a positive deciding factor. It seems that for older people with poorer vision, having bigger pixels is just wonderful.
What's the use of more pixels if you can't see any of them?
In addition to the marketing aspects pointed out by other folks, let me remind you of the economics of marking these things.
Hard disks, such as those used in the iPod, have high fixed costs to produce. So while it may be possible to cram more bits in the same package as technology advances, its difficult to take an older, smaller disk and produce them cheaply. The single biggest cost in producing an iPod is the hard disk. QED, etc.
Also, given that iPods in all varieties have been selling like hotcakes from the start, why would Apple want to lower the price? Clearly lots of people are willing to pay the $300-$500...I know I was.
Apple has publicly admitted that the current development rate is not really there for the long term. Knowing how much cash they have on hand, I'd guess that they've been burning a tremendous amount of money to get OS X developed so quickly. Unless people start flocking to Apple hardware in droves, I'd guess we're about to see a return to normal (i.e. slow) development cycles for OS X.
This uses Zapfino with its alternate character shapes (which is included on OS X), and the embedded info in the PDF tells me it was created by printing to a file on OS X.
Couldn't say what was used to create it though, perhaps the creator will be so nice to share. It doesn't really look like the work of Illustrator to me, but I could be wrong on that. Whatever was used to create it, it looks like mostly just a lot of hard work and attention to detail (ex choosing alternate character shapes on some of the titling fonts).
My experience is that with users that would use a wireless mesh, Macs really do tend to dominate. These are often people who are working all the time outside of an office: grad students, graphic designers, musicians, etc. These tend to be Mac users anyway, but add in the long-ish history of Apple making laptops w/ built-in 802.11 cards, and its plausible that there are an awful lot of Powerbooks being used on these networks.
There is nothing surprising about certain platforms being popular in different, small subgroups of the population. Whether it be Solaris, Linux, OS X, or the mighty Amiga, there is likely going to be some niche, large or small, that finds the particular platform the best tool for the job.
This doesn't mean anything in terms in total market share though. For general purpose office computing, the niche leader is MS Windows. I don't see this changing in any dramatic way, despite the many cross-platform development options out there.
Though the power of a good reference book and a few tutorials is not to be underestimated, LaTeX is readable enough that you'll learn a lot just by downloading other people's source, and modifying it for your own use. Once you've got the basic syntax, it should be simple for you to build on different documents and styles.
Okay, I'll bite. Microsoft, for all its failings to innovate in its commercial projects, has been churning out interesting research for quite some time in its various labs:
Open your favorite text editor (or the plist editor included with the OS X dev tools), and have a go at:
~/Library/Preferences/com.apple.mail.plist
In this file, there is a key labeled "DeliveryAccounts". This is where all your SMTP account information is kept. You should be able to edit/delete any account from there.
There is a means of doing this through AppleScript as well, but I don't remember how that works, so I'll have to leave that as an exercise for the reader.
Also, I'm still looking for a snug case/sleeve for the PowerBook, if anyone has any suggestions. I'm looking for one that's thin and just big enough to include a mouse and a power supply. I'd also prefer zippers or buttons over velcro (since they tend to be quieter than velcro).
I highly recommend the iBook/Powerbook slip cases from InCase (they are sold through the Apple Store). They are largely neoprene, and work equally well as soft cases or sleeves. Two pockets -- one on each side -- just large enough for a mouse and AC adapter. Zippers on the main compartment, velcro on the pockets.
None of the Apple branded products on that page are new items. The oddball objects, like the CF interface and voice recorder, are made by 3rd parties, and are not new either.
Most of these products are simply Apple-ish enough to warrent being sold on Apple's web store (and their Brick+Morter stores as well).
These are some of the many reasons why Python is my language-of-choice, and why I don't program much in Java (my first programming language!). However, I should point out that what pops out is not super efficient C, but rather reasonably efficient compiled byte-code. Its nice, but python is rarely as fast as I'd sometimes like it to be.
I use some variant on this encoder from Hivelogic, where the whole address is encoded into javascript, which needs to be executed to decode any part of the name.
The downside is that javascript is necessary to read any portion of my email address, and it only works if spambots refuse to execute arbitrary javascript. But in a year of use, I haven't had any problems with it, and my primary email address is remarkably spam-free. Nothing the spam filters can't handle anyway.
In message forums, etc, I just don't use my email address, ever. My name is easily Googled if someone really wants to contact me.
Dockers makes cargo pants -- Mobile Pants -- built from hidden pockets. They look more or less like standard business khaki's, but have hidden cargo pockets in the outer seam.
If that doesn't work, buckle down and get a man purse. I got mine this past summer, and my notebooks, camera, ipod, palm pilot, headphones, and cell phone have never been easier to carry around. You will look better for it.
- if you code XHTML, then all XHTML compliant browsers should render the same.
-- if you code CSS, then all CSS compliant browsers should render the same.
-- if you code XYZ, then all XYZ compliant apps should do the same thing.
This assumes that there is no ambiguity in the standards. In the case of XHTML+CSS, there are plenty of vague/conflicting descriptions in the standard as to how something should render. Of the top of my head, here is a recent (and thorough) description of such a problem, from Dave Hyatt's Safari blog
Some would argue that in the long run, when your beautiful mess isn't rendering properly and its time to debug your HTML+CSS+PHP+who-knows-what, you may regret not knowing the intricacies of your code.
Having used Dreamweaver (and few other visual editors) in the past, I doubt its ability to create a working site that I could not create by hand. Sure it speeds a lot of things up a lot, but so does the HTML tag templates built into BBEdit
While Dreamweaver does offer a window for editing source directly, I would never call it adequate. Just because you can edit text does not mean its a substitute for a full blown text editor. (Does anyone know if Dreamweaver can use an external editor? I don't remember.)
The full version of BBEdit offers quite a lot over BBEdit Lite (which is not much more than a plain text editor). See BBEdit Feature List for a real list of features, but suffice to say BBEdit has enough to be a real coding environment (so long as auto-completion is not your bread and butter).
As for BBEdit vs. vim, they really are two very different pieces of software. vim is quite a lot more powerful, and is infinitely more configurable. However, I find BBEdit offers a much easier environment to work in. Forgetting a command never involves looking through a help file or manpage, and for light jobs its simple enough for my mother to use.
Also, BBEdit has always been the best text editor with a "Mac experience" (standard UI, file handing, etc). Without a cleaned up interface, vim and emacs are second class citizens in much of the Mac world, despite being much more powerful text editors. This alone was enough to make it a worthwhile pruchase for me (though I only paid the academic price).
The technology that Trinitron monitors use is called 'Aperture Grille' which, IIRC, consists of high-tension wires strung across a loom, of sorts. The two semi-noticable horizontal lines characterising Trinitron displays are actually the shadows from two horizontal wires used to space the vertical ones (or so I am led to believe). You don't notice them after a while, but occasionally they 'reappear'.
IIFC, the two horizontal wires are in place to keep the vertical wires from vibrating back and forth.
Slashdot Mirror
64 bit architecture means far less efficient memory usage for applications that don't need it. This is why 32 bit chips are still being used in Macs, and this is unlikely to change before its more commonly necessary. By your logic, many embedded devices should move away from the ridiculously obsolete 4/8/16 bit chips they so often use. But they won't.
Its not so novel, but I'm sure there are plenty of schools, community centers, etc. around where you live that could always use spare hardware. A lot of the boxes these organizations receive are stripped down, and having extra sticks of RAM is very useful for them.
My grandmother uses a computer built from donated parts that a local group provides for the elderly, and she's now able to talk with her 4 generations of family over email (which is pretty well spread around the world now). There are probably tax breaks for you too, but in general donating unused hardware to those that will use it is a Good Thing.
While such people certainly are smart and possess insight and intuition, there's no correlation to being a good programmer.
This is true, but there is also little correlation between being a good programmer and being a talented and useful employee of a large innovative company.
Of the handful of people I know who bought the 14", the lower resolution was a positive deciding factor. It seems that for older people with poorer vision, having bigger pixels is just wonderful.
What's the use of more pixels if you can't see any of them?
In addition to the marketing aspects pointed out by other folks, let me remind you of the economics of marking these things.
Hard disks, such as those used in the iPod, have high fixed costs to produce. So while it may be possible to cram more bits in the same package as technology advances, its difficult to take an older, smaller disk and produce them cheaply. The single biggest cost in producing an iPod is the hard disk. QED, etc.
Also, given that iPods in all varieties have been selling like hotcakes from the start, why would Apple want to lower the price? Clearly lots of people are willing to pay the $300-$500...I know I was.
Apple has publicly admitted that the current development rate is not really there for the long term. Knowing how much cash they have on hand, I'd guess that they've been burning a tremendous amount of money to get OS X developed so quickly. Unless people start flocking to Apple hardware in droves, I'd guess we're about to see a return to normal (i.e. slow) development cycles for OS X.
This uses Zapfino with its alternate character shapes (which is included on OS X), and the embedded info in the PDF tells me it was created by printing to a file on OS X.
Couldn't say what was used to create it though, perhaps the creator will be so nice to share. It doesn't really look like the work of Illustrator to me, but I could be wrong on that. Whatever was used to create it, it looks like mostly just a lot of hard work and attention to detail (ex choosing alternate character shapes on some of the titling fonts).
My experience is that with users that would use a wireless mesh, Macs really do tend to dominate. These are often people who are working all the time outside of an office: grad students, graphic designers, musicians, etc. These tend to be Mac users anyway, but add in the long-ish history of Apple making laptops w/ built-in 802.11 cards, and its plausible that there are an awful lot of Powerbooks being used on these networks.
There is nothing surprising about certain platforms being popular in different, small subgroups of the population. Whether it be Solaris, Linux, OS X, or the mighty Amiga, there is likely going to be some niche, large or small, that finds the particular platform the best tool for the job.
This doesn't mean anything in terms in total market share though. For general purpose office computing, the niche leader is MS Windows. I don't see this changing in any dramatic way, despite the many cross-platform development options out there.
You should also check out Basilisk II, though I've not had any luck getting it to run anything prior to System 7. It will run well on many platforms.
Though the power of a good reference book and a few tutorials is not to be underestimated, LaTeX is readable enough that you'll learn a lot just by downloading other people's source, and modifying it for your own use. Once you've got the basic syntax, it should be simple for you to build on different documents and styles.
Apple's wireless (bluetooth) keyboard. No mouse included.
s /A ppleStore.woa/70702/wo/ul2nAMdvPhM028BKE761R4igMn9 /1.3.0.5.10
http://store.apple.com/1-800-MY-APPLE/WebObject
I like the cut of your jib, sir.
-J
Okay, I'll bite. Microsoft, for all its failings to innovate in its commercial projects, has been churning out interesting research for quite some time in its various labs:
http://research.microsoft.com/research/topics/
Its a shame that so little of this work is making its way into products you can use, but them's the breaks.
Open your favorite text editor (or the plist editor included with the OS X dev tools), and have a go at:
~/Library/Preferences/com.apple.mail.plist
In this file, there is a key labeled "DeliveryAccounts". This is where all your SMTP account information is kept. You should be able to edit/delete any account from there.
There is a means of doing this through AppleScript as well, but I don't remember how that works, so I'll have to leave that as an exercise for the reader.
Also, I'm still looking for a snug case/sleeve for the PowerBook, if anyone has any suggestions. I'm looking for one that's thin and just big enough to include a mouse and a power supply. I'd also prefer zippers or buttons over velcro (since they tend to be quieter than velcro).
I highly recommend the iBook/Powerbook slip cases from InCase (they are sold through the Apple Store). They are largely neoprene, and work equally well as soft cases or sleeves. Two pockets -- one on each side -- just large enough for a mouse and AC adapter. Zippers on the main compartment, velcro on the pockets.
I am fooling spam engines using many of the techniques discussed in the /. article posted on this subject earlier this month.
/ 22 6221
http://ask.slashdot.org/article.pl?sid=03/10/02
Cheers,
J
None of the Apple branded products on that page are new items. The oddball objects, like the CF interface and voice recorder, are made by 3rd parties, and are not new either.
Most of these products are simply Apple-ish enough to warrent being sold on Apple's web store (and their Brick+Morter stores as well).
These are some of the many reasons why Python is my language-of-choice, and why I don't program much in Java (my first programming language!). However, I should point out that what pops out is not super efficient C, but rather reasonably efficient compiled byte-code. Its nice, but python is rarely as fast as I'd sometimes like it to be.
But that's a story for another day...
Cheers,
J
...these bitches...? You are an offensive fuck.
Cheers,
-J
I use some variant on this encoder from Hivelogic, where the whole address is encoded into javascript, which needs to be executed to decode any part of the name.
The downside is that javascript is necessary to read any portion of my email address, and it only works if spambots refuse to execute arbitrary javascript. But in a year of use, I haven't had any problems with it, and my primary email address is remarkably spam-free. Nothing the spam filters can't handle anyway.
In message forums, etc, I just don't use my email address, ever. My name is easily Googled if someone really wants to contact me.
Dockers makes cargo pants -- Mobile Pants -- built from hidden pockets. They look more or less like standard business khaki's, but have hidden cargo pockets in the outer seam.
If that doesn't work, buckle down and get a man purse. I got mine this past summer, and my notebooks, camera, ipod, palm pilot, headphones, and cell phone have never been easier to carry around. You will look better for it.
This assumes that there is no ambiguity in the standards. In the case of XHTML+CSS, there are plenty of vague/conflicting descriptions in the standard as to how something should render. Of the top of my head, here is a recent (and thorough) description of such a problem, from Dave Hyatt's Safari blog
Some would argue that in the long run, when your beautiful mess isn't rendering properly and its time to debug your HTML+CSS+PHP+who-knows-what, you may regret not knowing the intricacies of your code.
Having used Dreamweaver (and few other visual editors) in the past, I doubt its ability to create a working site that I could not create by hand. Sure it speeds a lot of things up a lot, but so does the HTML tag templates built into BBEdit
While Dreamweaver does offer a window for editing source directly, I would never call it adequate. Just because you can edit text does not mean its a substitute for a full blown text editor. (Does anyone know if Dreamweaver can use an external editor? I don't remember.)
The full version of BBEdit offers quite a lot over BBEdit Lite (which is not much more than a plain text editor). See BBEdit Feature List for a real list of features, but suffice to say BBEdit has enough to be a real coding environment (so long as auto-completion is not your bread and butter).
As for BBEdit vs. vim, they really are two very different pieces of software. vim is quite a lot more powerful, and is infinitely more configurable. However, I find BBEdit offers a much easier environment to work in. Forgetting a command never involves looking through a help file or manpage, and for light jobs its simple enough for my mother to use.
Also, BBEdit has always been the best text editor with a "Mac experience" (standard UI, file handing, etc). Without a cleaned up interface, vim and emacs are second class citizens in much of the Mac world, despite being much more powerful text editors. This alone was enough to make it a worthwhile pruchase for me (though I only paid the academic price).
IIFC, the two horizontal wires are in place to keep the vertical wires from vibrating back and forth.