HNHacker News
TopNewBestAskShowJobs

archgrove

2,454 karma · joined March 31, 2009

Adam Wright (http://www.archgrove.co.uk)
submissionscomments
archgrove··on [dead]
Because, of course, those fries will be serving themselves. I'd say checkout staff and customer assistants are one of the few jobs that couldn't be mechanised/outsourced in the (reasonable) future.
archgrove··on Google shows off Android 3.0, the 'Entirely for Tablet' Honeycomb (video)
One can't really tell from a promotional video, but the main thing that stands out to me is the improved home screen over iPad. It's too "technical" to be mass market in this version; viz. "Books \n 3x3" type stuff - my parents won't know what 3x3 means, even after explanation. Even I'm only guessing is the size the widget takes on the home screen. However, assuming they fix that, it's rather an improvement on Apple's iOS SpringBoard, which is looking rather dated (alongside their notification system). Here's to competition accelerating an upgrade in iOS 5!

The rest of the applications, one can't really tell in short clip. A lot of them - mail, video chat etc - seem very similar to what one would find elsewhere, except with the Honeycomb chrome (take it or leave it, as personal preference dictates). In others, I worry they've gone for eye candy over usability. For example, in "Books", the circular scroll is all very well, but I can't see any way of telling how far through your collection you are, nor where the book you want might be. Of course, the is prerelease promo, so it might be obvious in the real thing. What most people don't seem to get is that Apple tend to use eye candy only when it's useful - not just to look like something in Minority Report. Even they don't get it right all the time (I'm looking at you, Time Machine animation!). Eye candy is really cool for promotional videos, but when you're trying to use the application for the 4562nd time you really hope that it's added just to enhance usability, rather than impress CES visitors.

archgrove··on Android vs iOS: A Developer's Perspective
I totally agree with some of the points: iOS should really receive the same garbage collector that OS X has had for years, and the provisioning certificate nonsense is, well, nonsense. iOS really does need a side loading mechanism. That you need a Mac to develop on is, I suppose, a negative - you can get going with Android on almost anything.

However, I can't say I've ever had any problem with Apple's documentation: It's clear, well written, generally entirely correct. I must confess, I've never spent "weeks devising and performing increasingly peculiar experiments to figure out how to get iOS to do what [I] want", any more than on any platform. If he's complaining that iOS has private APIs then, well, I'm quite sure Android does as well - private just means "not guaranteed to exist in the same form on an upcoming release". If he's claiming that Android's "openness" allows him to see deep inside the OS to make design decisions, rather than relying on the documentation, then I'd suggest that's a mad development strategy (unless one likes rewriting when new OS releases come out).

The point about the simulator seems to be that Android's is so bad, you have to use the phone. I can't really see that as a plus, as one could do exactly the same thing on iPhone, except that iOS has a working simulation environment for when you want it.

The remaining points, about the initial user experience and development environment are entirely subjective, so one can't really comment either way. His point that developing for Android seems to be "easier" than iPhone runs contrary to my experiences, but what one man finds easy, another might find hard.

archgrove··on Oracle and Apple Announce OpenJDK Project for Mac OS X
Almost as important is the announcement that the current Apple JDK, 1.6, will still ship in Lion. Given the release cycle of Java 7, that's a big relief to Java users and given the HN crowd, budding Android developers. Moreover, it seems to quash the (ridiculous) rumours that OS X Lion will end up being some locked down antithesis of previous versions of OS X.
archgrove··on Oracle and Apple Announce OpenJDK Project for Mac OS X
Your point (c) is the most important, in my opinion. I work in computing theory research at a major UK university, and well over 50% of the desktops I see used are Macs, and about 80% of the laptops. Many of our undergraduates also use Macs. A working Java implementation is quite important for this area - both for Apple, to ensure we keep buying them and Oracle, to stop people just saying "Well, we don't use that much Java anymore, let's just drop it".
archgrove··on An umbrella designed using aerodynamic theory to withstand 100km/h winds
I have one of these. It certainly is much better at resisting the strong winds England can blow than a classic umbrella (which lasts about 15 minutes around here).

Unfortunately, it has two other problems that hamper any recommendation. The first is, as another commenter mentioned, it won't stay closed when collapsed without a fiddly velcro tie. You have to wrap it around the entire umbrella body, which is keen to spring open whilst you struggle with it. With cold, wet fingers this can be tricky.

The second problem is the build quality. Whilst generally OK, within 6 months mine had developed two flaws. It won't stay fully extended, as one of the little clips that pops out on the telescopic handle failed. It thus loves to collapse down to a size suitable for a toddler at any opportunity. The second is one of the canopy support structs popped out and bent, so it doesn't quite hold rigid.

It's a pity that what is otherwise an excellent design is hampered by one poor choice, and some shoddy construction. I don't know if the flaws on mine are isolated, but if that were the case, I'd have expected one flaw at most - not two orthogonal failures. Moreover, given the price, I scoured their website to find support and customer services when it broke. I had no luck whatsoever in finding after sales service, and couldn't return it to the store (it was a gift).

archgrove··on Stack Overflow just became a top-500 site.
Yup! Not sure exactly when, but certainly on the radar.
archgrove··on Stack Overflow just became a top-500 site.
I chose it. Any app that downloads data from the web needs to be careful with age ratings - Stack Exchange has more than programming questions - it has, e.g. video games, with perhaps more age restricted material. I chose 12+ as a compromise between Apple's desire to have age approprate labelling, and restricting likely users.
archgrove··on Stack Overflow just became a top-500 site.
It would be interesting to find out how many users they're getting from their semi recently launched API (http://stackapps.com). I know my iPhone Stack Exchange client http://sixtoeightapp.com has over a thousand downloads, and won't be counted by Quantcast. Whilst it's more of a complementary access point, other apps on Stack Apps might suffice as the sole access point for passive users (i.e. those who just want answers, as the API is read only currently).
archgrove··on On a New Road : James Gosling on Apple and Java
I agree - it's not, at the moment, an ideal end user situation. Even though the build process was reasonably easy, a fair few GUI programs won't run (though mostly every command line app seems to work fine). Most importantly for my test, Eclipse was OK.

The main point of the test was to see how close the system was to being even usable. Considering Apple have maintained the OS X Java for a decade, I expected there to be no alternative that was even vaguely close to running "Hello World", let alone running something as complex as Eclipse. Instead, it worked pretty damn well, and (modulo licensing), I suspect even I could package up the results into a DMG that 95% of people could use to, i.e., build Android apps. More than that, consider the worst case scenario for OS X Java...

1) Apple don't ship anything with 10.7; 2) Oracle don't ship anything, nor do IBM; 3) Getting old versions of Apple Java running is impossible

Then, the real community experts have a nearly whole year of lead time (until Summer 2011, the earliest Lion ships) to convert what already limps along quite well into a decent Java SE SDK and runtime experience. This seems well within the grasp of them. Of course, if the community doesn't step up because it's not interested, then that rather makes the point that Java on OS X just isn't relevant any more.

archgrove··on On a New Road : James Gosling on Apple and Java
Not a lot. To assuage my fears, I just built OpenJDK's BSD port and ran Eclipse 3.6.1 on it without X11 (This from Snow Leopard 10.6.4). It wasn't hard, and could easily be packaged for general consumption.

The maintainer of the OpenJDK binary packages for OS X, SoyLatte, recently tweeted that "A community supported Java implementation for Mac OS X (including native AWT/Swing) is a totally tractable problem." (http://twitter.com/landonfuller). Even if Oracle doesn't step up, it seems the OS X Java community will probably handle it. Moreover, since Java has been languishing at Cupertino for years now (the length of time till Java 5 shipped, Java 6 32 bit), it's likely the community will handle it in a better way, with more frequent updates, than Apple ever did.

archgrove··on Google launching a Chrome OS tablet on Verizon, goes on sale November 26
In the comments, from the author...

> Lee Mathews said 10:50AM on 8-18-2010

> No, my source tells me it's Google hardware -- like the N1.

I'm assuming handset support in the US is the same as the EU, where for smart phones, you normally deal with the manufacturer, not the carrier ( i.e. If my iPhone or iPad breaks, I call Apple - not O2).

archgrove··on Google launching a Chrome OS tablet on Verizon, goes on sale November 26
Total evidence offered for YAGTR (Yet another Google tablet rumour): 0. Plus given that Google just got out of the phone handset to consumer business (because, frankly, they suck at any product that might require end user support), how likely are try to jump into another end user hardware sale/support setup?
archgrove··on IPhone to Droid-X: Lots to Like
You do realise that saying "I am now a 100% fuck-you Apple anti-fanboy" renders your entire post worthless? By the definition of fanboy you're saying your judgement is biased, your conclusions skewed, and your opinions suspect to the point that anyone who doesn't just want positive reenforcement of their existing ideas should ignore you.
archgrove··on DHH: Appstore is a warehouse of shit
This is so true. I've done some minor iPad consulting recently, but been asked for comments on several projects. I've found it only fair to prefix my replies with "I can't give you any guarantee that, having spent this money, you'll get anything. Apple uses a hidden list of rejection reasons, and enforces it capriciously". I rarely find companies going ahead with their developments.

Apple may be keeping some garbage out, but they're losing many good apps that probably would have been accepted, if the client had a hard and fast guidelines list to check against. They're also losing developer mindset. They are, in effect, FUDing their own developer base. It's a remarkable strategy, and I can't see how it's anything other than highly damaging.

I'm going through the App Review gauntlet now. My concerns at the end of the development, when doing the last checks against the few official things Apple will say regarding review (and against the web horror stories) were not "What would make a better app". They were:

- Will I get rejected for this icon? I think it's clear, but Apple might squint then claim it's too similar to their XYZ icon. I better change it to this other one, which is less good but at least entirely different

- As I fetch data from the Internet, and someone might post an offensive image before the moderators nuke it, I best set the Age Rating to 17+ (even though I've see an offensive image once in the system, and it lasted 5 minutes).

- I did say "Open in Safari" in my browser invoking popups, which my iPhone addicted users will find clearest. However, Apple randomly reject you for using their trademarks, so I better make it the less clear "Open in Browser"

and a dozen other quality reducing changes that are forced on me by the huge uncertainly about what's "allowed" and what will be understood by their team. In the three days it took me to change my "high quality" app (well, I think so :), I don't doubt the App Store admitted another 10 flashlights and 5 Fart apps.

I love the iPhone and iPad as a consumer. I like the technology as a developer (though I would prefer not to be 100% tied to Objective C). The "business" person and ethnical geek in me hates it with a passion. It's creating a horrible cognitive dissonance that I'm currently tempted to correct by going Android as soon as they have an a decent iPad clone.

archgrove··on Here's why you should not buy a Drobo
I've had my Drobo 18 months without a hiccup - It's not silent, but it's not noisy either. I've never had to contact customer support, so I can't really comment on that. I am marginally concerned by the fact that its death would mean I must have another Drobo to read the data, but this really isn't any different from most other hardware RAID controllers/NAS boxes, where the death of the card almost always means purchase of another identical card/driver combination to get your data back.

The point here is, Drobo/RAID/NAS are disk redundancy solutions - they cater for the fallibility of spinning magnetic platters, and never promise 100% reliability. Just like any solution, if you want to avoid data loss, you need to have an orthogonal backup system for when the other fails at a system level.

It sucks that he's had such problems with his Drobos, and it looks like the support he's got is subpar. This is not, however, the universal experience. Based on my experience, I'd be happy to recommend the Drobo to most people I know who want a simple and easy to setup solution for hard drive failures, with the big caveat that they still need at least one other backup solution.

archgrove··on Etude for iPad is out
That, I didn't realise. Great value :). Almost too great - I'd have paid for an upgrade!
archgrove··on Etude for iPad is out
It looks lovely, and I'll probably grab it (especially at that price). However, as an Etude for iPhone user, I have to say - you really need to get some more scores into the store. At the moment, months after launch, you still only have material from 21 composers. Everyone I've shown it to loves it, but it's a really hard sell with such a limited selection. I've no problem with paying for sheet music, and I'd probably pay more for the convenience of this format - it just needs to be there!
archgrove··on Will Steve Ballmer show up at the WWDC keynote?
Mostly, it's that the intellisense and interactive debugger systems are streets ahead. Intelisense is basically useless on XCode, and the debugger support is a thin UI layer around GDB (which, very often, just doesn't work. The number of times it'll tell me that a variable is out of scope when it's quite clearly right in front of its nose is insane).
archgrove··on Will Steve Ballmer show up at the WWDC keynote?
Hmm, I'm dubious. I can see XCode on Windows, as it increases the developer market share and primes people for a move to Mac. I don't know how they'd do it technically, though - most of the good bits of XCode are based on kernel level dtrace support.

I just can't see them wanting Visual Studio support. It is, pretty much, just better than XCode. Overnight, the superior development platform for an Apple device would be a Windows machine. Unless they're really planning on EOLing OS X and their non iP* businesses, why would they want the best developer environment to be hosted on a rival platform? Killing or abandoning OS X seems insane - desk/laptops still account for 50% of their income, and currently most OS X developers are also targeting iP* devices in parallel with their desktop work. Moreover, the iPhone halo effect is getting them more Mac sales and Mac developers. Whilst they're not hurting for iPhone apps, why give developers the incentive to stop buying Macs, buy Windows, kill off their OS X development, and throw out a hugely profitable segment of Apple's business to gamble on Android not eating their iPhone lunch?

I suspect this is just an analysts "blue sky" nonsense, or a confusion over e.g. development environments for Office 2011 Mac. For reference, this same guy claimed there would be no Mac updates in 2009, and that they'd release a small OLED laptop by the end of 2009. 0 for 2 so far, and I'm guessing 0 for 3.

archgrove··on Ask HN: Red Gate giving away iPad to developers who show up for interviews
Well, fair enough then; I'm presuming you're a RedGate employee. I'm then curious, how well are you doing persuading the "great software engineers" to interview away from their safe jobs with a £429 bit of kit?
archgrove··on Ask HN: Red Gate giving away iPad to developers who show up for interviews
I was up at the Cambridge university computing department the other day, and it became clear that this offer is really targeting the students there (it's advertised directly on their notice boards, for example).

The average quality of their graduates is pretty high, and as Red Gate are already in Cambridge, they need just a little kick to get the best people to come talk to them, rather than one of the investment banks (at the moment, only about half of the CS grads actually go and work in IT). It's not intended to get people to travel the globe to work for them, nor do they really want that hassle.

archgrove··on Antitrust inquiry into Apple over Section 3.3.1
How are Apple preventing you from buying the ever more popular Android phones? Or Web OS phones? You, a member of the market, buy the phone with the features you want. If you don't like Apple products, or the app store they provide, buy one of the many hundreds of alternative smartphones, many of which have large adoption.
archgrove··on Antitrust inquiry into Apple over Section 3.3.1
Your entire response seems to have missed my "allowed on phones that achieved any levels of success" qualifier. Name me any pre-iPhone development platform allowing development that had ever created a truly viable marketplace. There were a few faltering attempts with Windows Mobile and Symbian, but frankly, they were terrible. And yes, I am conflating development and the distribution channel, but this seems fine to me - if you develop, and noone ever runs it, did you develop anything?

Having seen [2], I think my point is even stronger - first class smartphone development really began with the iPhone (the App Store predates any other competitor). Of the third party services, only 4 predate the iPhone by more than a month or two (and of those, only 2 achieved even the level of success needed for a Wikipedia page).

archgrove··on Antitrust inquiry into Apple over Section 3.3.1
So Apple has a monopoly on the iPhone app store - no great surprise there. I may as well claim that Microsoft need to open the 360 marketplace to my personal ideals, because they have a monopoly on licensing XBox 360 games.

The Android app store certainly exists, and is doing quite well. The web is free for all platforms. Apple don't, by any realistic measure, have a monopoly on application sales for smartphones. They just couldn't - with only 25% of the smartphone market, and an app store that targets only that 25%, how can they have a monopoly on smartphone app publication? What they might have is a monopoly on the wealthy gadget consumer with large amounts of disposable income to spend on apps. I'm not, however, that Apple's clever demographic targeting, coupled with the inability of their competitors to eat into this market via fair competition, is reason to force them to change their business model.

archgrove··on Antitrust inquiry into Apple over Section 3.3.1
The specifics are different, no doubt - but the ethos is the same. Microsoft force you to use .Net (of some form) and their APIs because that fits their business model (i.e. ties you to the XBox). They're restricting me from using my platform portable pure C code, which is their choice. I obviously don't know, but suspect if large amounts of code started targeting XNA in a cross platform way, they'd come down on that too. I also don't know what the requirements of their commercial licence are (and unless you're an XBox developer, neither do you), but it's almost certainly more than just revenue sharing (they would never allow the publication of a "Crash a plane into the twin towers" game, for example). Moreover, I do know that Nintendo certain did (and I think still do) have strict policies on types of violence in games for their platforms.

Regardless, the general point stands. They're making choices based on what they think is best for their platform, and letting the market chose. This is how the free market is supposed to work. It breaks down when there are entrenched monopolies, or when other external factors prevent people from exercising their right to buy an alternative, or start a competitor - but that is demonstrably not the case here. So why not let the market decide?

archgrove··on Antitrust inquiry into Apple over Section 3.3.1
But they're nowhere near "distressingly close" to a monopoly - even picking the most Apple friendly metrics, they have only 25% of the smartphone market, with Android constantly closing the gap (and e.g. Blackberry actually ahead of them in some areas). The Wii, on the other hand, has around 50% of the current generation console market.

They seem to have a monopoly on marketplace hype, I won't doubt that. But to claim they've a monopoly on smartphones is just plain wrong.

archgrove··on Antitrust inquiry into Apple over Section 3.3.1
But "I expected it to be different" doesn't seem like a sound legal foundation for anti-trust action. In many ways, the iPhone has been the founding of "open" phone development. Prior to the iPhone, there was virtually no real development allowed on phones that achieved any levels of success (carriers had the platform locked down hard). Post iPhone, we've seen actual competition in this space - the entirely open Android strategy (though their App Store also has restrictions, they just apply them post-release rather than pre-release); the semi-closed iPhone and Nokia Ovi models, the web app model of all the platforms. People claiming that Apple has created a locked-down environment have very short memories - even the closed nature of the App Store via 3.3.1 would have been considered insanely open only 5 years ago.

Google have bet that unfettered platform mutability with (almost) totally free development is good for their business model. Great, and more power to them. Apple have bet that allowing a freeforall would cause their business model damage; OK, that's their call. Other platform holders are trying other strategies. The point being, the free market seems to be about allowing them to try these ideas, and fail if consumers don't like them. Whilst Apple are nowhere near a monopoly on smartphones (and they're frankly miles away from one), they should be free to adopt whatever model they think works best for them.

archgrove··on Antitrust inquiry into Apple over Section 3.3.1
Genuine question: How are the restrictions placed by Apple on what's allowed in the App Store any different then the restrictions placed by console owners on what's published for the XBox or PS3? For example, the XBox XNA community games system requires people to use .Net - there's no technical reason for this (the XBox is clearly capable of running native code). However, Microsoft/Sony/Nintendo still seem to be allowed to place pretty heavy licensing requirements on game publishers (so strict you can't actually know them without handing over a lot of cash).

I tend to agree with antitrust action most of the time, but it seems that platform owners should be able to have some say over their platform direction, if they honestly think that doing so is good for their business. Whilst they don't have a monopoly in the market, and there is plenty of choice for consumers, what benefit does the public get from forcing people trying the "Closed is better" business model to open up to direct competitors (who, depending on what you believe, might seriously damage the experience for end users)? If the market dislikes the closed system, it will fail. If it grows to be dominant, then sure - anti-trust seems reasonable. But whilst competition is thriving, it seems heavy handed to rule out certain business models.

archgrove··on Steve Jobs, circa 2020: "Thoughts on country roads"
The browser. Virtually nothing crashes the actual OS these days (be it Windows, OS X or Linux). I think I've had 1 or 2 complete OS crashes in the last 4 years.
← PreviousPage 6 of 7Next →