MacBook, defective by design banner

title:
Put the knife down and take a green herb, dude.


descrip:

One feller's views on the state of everyday computer science & its application (and now, OTHER STUFF) who isn't rich enough to shell out for www.myfreakinfirst-andlast-name.com

Using 89% of the same design the blog had in 2001.

FOR ENTERTAINMENT PURPOSES ONLY!!!
Back-up your data and, when you bike, always wear white.
x

MarkUpDown is the best Markdown editor for professionals on Windows 10.

It includes two-pane live preview, in-app uploads to imgur for image hosting, and MultiMarkdown table support.

Features you won't find anywhere else include...

You've wasted more than $15 of your time looking for a great Markdown editor.

Stop looking. MarkUpDown is the app you're looking for.

Learn more or head over to the 'Store now!

Sunday, July 18, 2010

I've seen [admittedly, I've seen a report claiming to be quoting] the Consumer Report blog on the iPhone saying that they aren't impressed with the sunset on Apple's free case offer for iPhone 4 purchases as part of Antennagate.

The reasoning behind Apple's free bumper deadline seems to be pretty clear. If 70% of iPhone 4 buyers pre-"scandal" grab cases, Apple's going to change the design of the iPhone and save a few bucks by adding some insulation, if they haven't already. If 5% do, they're going to go back to selling the iPhone exactly like it is. The free case shindig is more of a PR stunt and large scale survey than anything else.


Honestly, I've got no idea what the hubbub is about. Don't hold your iPod with your left hand in the "deathgrip" when you're on the phone. It's not like everyone who has an iPhone doesn't end up buying a case anyhow, and I bet many would rather use a case that's not the $29 bumper special.

Best design for a phone? No. But the iPhone isn't just a phone. Can't be a jack of all trades and not cut a few corners.

I just wonder how Apple let this turn into such a PR mess. If they knew about the antenna compromises earlier on, as rumors say (and their fancy smancy antenna page would imply) they did, they could have leaked the defect to prepare an already overly forgiving market of Apple-lytes or, better yet, had a reply ready rather than waiting weeks and allowing analysts to start randomly pricing out the costs of the R-word in the b-as-in-billions. That's the real failing here.

That said, I can't wait for the new iPod touch. Mine fell out of my pocket at the Little Caesars, we'll say, and even though my number and email are laser-etched on the back, it appears to have disappeared for good. I'm not really surprised, but it sure would be nice to get a call at some point. I'm hoping if I buy the new one with a camera, a rumor I'm assuming is true, it'll help make the old one reappear (though I realize more likely is that it hits the Goodwill with a cracked screen in two years before that call comes). A phone-less iPhone really is still pretty danged cool.

Which makes me wonder... does the death grip kill 3G in general? What, were all the iPhone testers left-handed?

Labels:


posted by ruffin at 7/18/2010 11:23:00 AM
0 comments
Sunday, July 04, 2010

As Anandtech's review of the iPhone 4 shows, there are downsides to believing your own hype.

The fact that Apple didn't have the foresight to coat the stainless steel antenna band with even a fraction of an ounce worth of non-conductive material either tells us that Apple doesn't care or that it simply doesn't test thoroughly enough. The latter is a message we've seen a few times before with OS X issues, the iPhone 4 simply reinforces it.


There's a certain nearsightedness that corresponds to such ivory tower engineering. As I read somewhere earlier today, it's as if Apple tested the iPhone's reception by hanging it magically in the air... makes sense if the FCC's requirements of putting the antenna out of your head's way is your design goal. Not so much if you want humans to use it.

posted by ruffin at 7/04/2010 01:05:00 AM
0 comments
Saturday, July 03, 2010

I've often complained that one often has to spend a cool grand more on Mac hardware than similar Windows hardware. It's often more like $500-700 now, but the Mac Tax is still there, especially in games. You'd have to wait months after a Windows release to purchase some subset of Windows games for the price of that game when it was released. That is, you had to buy long in the tooth games on Mac for the price of new games on the PC, and you had nearly zero access to the used market.

Well, that's also been the case for iTunes and the iPhone. Gizmodo updates us on the iPhone 4 Mac Tax.

In other words, Apple will reach back in time 9 years to make the iPhone compatible on PCs but only 3 to make it compatible with their own computers. So much for the advantages of a closed infrastructure!


Part of this is due to the combination of hardware and software in one company. This forced upgrade is precisely why, if Apple ever gained the marketshare that Windows has, the government would almost have to step in to ensure the power to force upgrades isn't abused.

Let me explain. Microsoft has to make sure companies that deploy on its dominant OS rest easy that their apps won't break when their user base moves from, say, XP to Vista or Windows 7. Enough change from the last OS, and guess who gets left in the cold? It's not the user and their favorite apps; it's the OS. People will keep using XP, and they can keep using XP precisely because MS doesn't control hardware. Windows has to work on computers that meet a certain standard, and hardware makers, like Dell, can keep putting out new hardware that works with XP. You can't strongarm a move quite as easily as Apple can.

Visual Basic 6, a language Microsoft ended "mainstream" support for five years ago, still works on Windows 7. Now, Apple does do something similar. They couldn't have Microsoft Office break in OS X, so they kept Rosetta active to make sure their biggest third-part software providers kept running. Same with Photoshop and Carbon. Apple bent over backwards for each major software interest on their OS. Microsoft has lots more people interested, and the degree to which their tools continue to produce apps that work on older OSes has to stay very broad. Microsoft's position requires their culture, one that helps developers.

Now maybe if Apple had more share, they too would have to kowtow to developers a little more diligently. I don't think that this is part of the Apple mentality, however. They've broken Java compatibility, the one spot I'm most familiar with, over and over, and have given and stolen back API calls from within Java with impunity. Look also to their attitude with Flash (and Java, etc) on iOS. It's their way or the highway. Heck, look at the move from OS 9 to OS X or PowerPC to Intel! They completely obsoleted an entire chip architecture. That's Apple's culture. Want to use a camcorder with a Firewireless MacBook? Buy a new, USB camcorder, Jobs writes. No, really. That's his answer.

This is a long way of saying the reason the iPhone syncs back 9 years on Windows and 3 on OS X is entirely Microsoft's fault. The tools and software libraries used to make iTunes on Windows work on XP. That's a Microsoft decision. If Apple wanted, they could introduce artificial walls to make iPhone 4 Windows 7 or Vista only, but it's be artificial. More importantly, in a world with options in software, hardware [if not OS], lots of users will simply not use an iPhone. More to the point, Apple's arranged it so that people without the income or interest in upgrading something that works fine already in a few years aren't in their target market. Your barely Outlook literate aunt isn't buying an iPhone. Jobs doesn't want her to. But Windows will support her, and when she does replace the 10 year-old computer, it'll likely be another, well, whatever. eMachine?

I've always been impressed with Microsoft's coding tools. Occasionally they get overly happy with embracing and extending, but as long as you're writing on Windows for Windows, you'll be hard pressed to find a better, more fully fleshed out set of objects than MS's. Microsoft's coding tools encourage backwards compatibility as a rule. They've got too many developers and too many hardware choices not to take this open-minded approach, ironic as that sounds when said about MS. It's a cultural thing.

Let's sum: Jobs makes cool; Microsoft makes tools. If a coding library breaks or is too tough to support on Apple, Jobs will tell you that's just too bad. Buy a new Mac.

Labels: , , ,


posted by ruffin at 7/03/2010 11:44:00 AM
0 comments

Support freedom
All posts can be accessed here:


Just the last year o' posts:

URLs I want to remember:
* Atari 2600 programming on your Mac
* joel on software (tip pt)
* Professional links: resume, github, paltry StackOverflow * Regular Expression Introduction (copy)
* The hex editor whose name I forget
* JSONLint to pretty-ify JSON
* Using CommonDialog in VB 6 * Free zip utils
* git repo mapped drive setup * Regex Tester
* Read the bits about the zone * Find column in sql server db by name
* Giant ASCII Textifier in Stick Figures (in Ivrit) * Quick intro to Javascript
* Don't [over-]sweat "micro-optimization" * Parsing str's in VB6
* .ToString("yyyy-MM-dd HH:mm:ss.fff", CultureInfo.InvariantCulture); (src) * Break on a Lenovo T430: Fn+Alt+B
email if ya gotta, RSS if ya wanna RSS, (?_?), ¢, & ? if you're keypadless


Powered by Blogger etree.org Curmudgeon Gamer badge
The postings on this site are [usually] my own and do not necessarily reflect the views of any employer, past or present, or other entity.