Skip to main content
Post a Comment

Power User View

I am a VBA programmer for Excel and Access on Windows, and my technical background includes stints as desktop/server support, project management, and departmental IT management, but all with Windows. Several years ago, before the switch ads, I purchased an iMac with OS X, partially for aesthetics and partially for novelty; I upgraded it to 1Gb RAM a few months ago. Counter to the hype, I would often hang my iMac, and although the software availability is greater for PC's, I've found Mac software much more appealing. Obviously I am not a gamer. My technical background means I have the knowledge required to secure a wireless network, setup firewalls, and avoid viruses/phishing, so my biggest issue with my iMac is speed in everyday use.

Generally, the Mac versus Windows debates hovers around several issues, e.g., ease of use, speed/power, installed base, total cost of ownership. There are others, but the reason that Intel in Mac matters is primarily power. The move to Intel reduces one of the largest single complaints about Mac's, that they are slow. Recent tests tend to show Windows outperforming Apple's PC's, even for vaunted design applications, and now with Intel processors inside, that criticism is muted. I think kudos should also be given for the ease at which they've ported/recompiled OS X on Intel. Since the base OS is UNIX, it might translate into easier upgrade paths for Mac OS X users, besides the increased power Mac users will enjoy. It has simply made a great product better.

Comments

Post a Comment

Popular posts from this blog

Behave: The Biology of Humans at Our Best and Worst by Robert M. Sapolsky My rating: 5 of 5 stars I finished reading this crying. It is a work of neurobiology, social science, anthropology, and history, but ultimately it is a work of great humanity, suggesting ways that humans, our groups, our systems, and our societies can be made better. View all my reviews
Post a Comment
Read more

A Journey — if You Dare — Into the Minds of Silicon Valley Programmers

My responses in a NY Times comment section for the book, Coders: The Making of a New Tribe and the Remaking of the World by Clive Thompson : #1 - Link Although I've been a software developer for 15 years, and for longer alternating between a project manager, team lead, or analyst, mostly in finance, and now with a cancer center, I found it funny that you blame the people doing the coding for not seeing the harm it could cause. First, most scientific advancement has dark elements, and it is usually not the science but how it is used and sold by business people that is the problem. This leads to the second problem, in that it is not coding that is in itself problematic, but specifically how technology is harnessed to sell. It is normal and desirable to track users, to log actions, to collect telemetry, so as to monitor systems, respond to errors, and to develop new features, but that normal engineering practice has been used to surveil users for the purpose of selling. Blaming
Post a Comment
Read more

Don't learn to code. Learn to think.

A response to  Don't learn to code. Learn to think. : Below is is my usual response when I see an article stating that everyone should learn to code:  Rather than programming, it is more important to impart the thinking of computer science (CS) than a specific implementation. Programming can be an end point for some students, but it is likely that programming itself will be increasingly automated, so that one needs more the general concepts common in CS. Even then, programming itself is to some degree a grunt task that one progresses beyond:  The following are typical components of a CS degree: algorithms & flowcharting systems thinking logical systems and set theory object-orientation & patterns probability, statistics, mathematics All of the above can be useful in an increasingly automated and data-driven world.
1 comment
Read more