HNHacker News
TopNewBestAskShowJobs

archgrove

2,454 karma · joined March 31, 2009

Adam Wright (http://www.archgrove.co.uk)
submissionscomments
archgrove··on Steve Jobs, circa 2020: "Thoughts on country roads"
Regardless of Job's other comments, the "Flash crashes Macs" isn't FUD by any definition. The SWF plugin is just a pretty bad bit of software. If you don't believe me, check the Firefox crash analysis for today: http://people.mozilla.com/crash_analysis/20100502/20100502_F.... The Flash plugin is the greatest cause of crashes for them on the Mac, and it's pretty damn high on Windows as well.

The claim by the Adobe CEO that Mac flash crashes are "to do with the Apple operating system" is complete and total nonsense (there's nothing in OS X that would cause Flash to be crashy, and the data supports the fact that it's bad on Windows as well).

archgrove··on Jobs on Flash: Hypocrisy So Thick You Could Cut it with a Knife
The author openly conceeds the points that consumers will actually care about - performance, security, and proprietary nature. It's hard to claim that it's a "marketing trick to pull the wool over the eyes of consumers" when you agree with large tracts of the author's argument.

Their main point, that he's somehow a hypocrite because Apple haven't used the latest tech for everything, entirely misses the point he's making - Putting a 3rd party layer between your platform and developers can cause a lag in new features being used. He then states he's mostly worried that Adobe would have really amplified this lag, as "Adobe has been painfully slow to adopt enhancements to Apple’s platforms". He doesn't say it's bad that they've been this slow, just that they are this slow. If it takes them 10 years to adopt Cocoa, why would anything in iPhone 4.0 turn up in Flash till 2015? His claim is that middleware lag is a bad thing is not weakened by iTunes for Windows being crappy - if anything, it's strengthened.

He makes his position very clear - "we sell more devices because we have the best apps", and feels they get the best apps without middleware. There's nothing inconsistent with this position, whilst still taking advantage of other platforms lack of restrictions. I'm not even going to deal with the authors claim that h.264 is as proprietary as Flash: A standard that was developed by a committee, in the open, with many implementations and a licensing scheme for anyone, versus a commercial closed product developed by a single company and no competitive implementations? Sure, there's no difference at all there.

archgrove··on :-moz-any() CSS selector grouping
This doesn't seem to be linked to any upcoming or finalised W3C/WHATWG standard. It certainly looks like a nice idea, but isn't this arbitrary introduction of non-standard features exactly what we hated IE3-6 for? Prefixing it with "moz-" doesn't really make it less propriatory (we can easily have imagined all the IE* 'extensions' having an ie- prefix). If IE9 came out with a load of new CSS selectors and syntax that nobody had heard of, there'd be uproar in large sections of the technorati.

This kind of experimentation is certainly useful. However, with the vendor- prefixes leaking into real world sites, we seem to need a real playground for experimental new CSS/HTML features that ensures they don't get used in production. Alas, I'm not sure what the best route to this would be.

archgrove··on @twitterapi's countdown to Basic Auth removal
OK, having researched, I presume you're refering to the XAuth stuff http://dev.twitter.com/pages/auth#browser-less-apps.

How the frell is this any better than Basic auth for most users? I can only see that 1) I don't have to store their password on my client and 2) it won't be sent across the network plaintext.

This is useless. End users have no idea that I'm actually doing 1), and 2) has never been a problem (HTTPS supports Basic auth fine for transport encryption).

archgrove··on @twitterapi's countdown to Basic Auth removal
And importing a new library into my codebase is a non-trivial activity. I need to vet it, ensure it will be supported and updated, and that well, it actually works. It makes Twitter implementation from "pretty much trivial in any language/device under the sun" into "Pain in the ass".

I don't mind supporting new APIs when they offer a solution to a real problem. As I've asked in my other comment, how many people have really lost their credentials via basic auth?

Edit: I can't seem to reply to steveklabnik's post below, so I do it inline by emphasising importing a new library is a non-trivial activity. I'm afraid that mass importing of external code into my projects is not something I undertake lightly; unless it's a platform supported (or very widely used) library, it requires a reasonable amount of vetting to ensure that it a) Works b) Does't break anything else c) will continue to work in the future.

My question remains: Why? What is the insanely pressing need to move to OAuth when users don't really seem to care and I can't find any evidence that it's been a real security problem? I completely agree that it's nicer in theory, but as mentioned in my other post, I don't actually see that it's any more secure. Unless I'm being highly dense, it would fall to a completely trivial quazi-social engineering hack in almost all end user cases.

archgrove··on @twitterapi's countdown to Basic Auth removal
Edit: OK, I was wrong, as I'd hoped - you don't need a web browser. The rest of my post stands unchanged as, regardless of my interpretation, it kills the Twitter support I just wrote in less than an hour into one of my apps, and renders it a multi-hour (if not day) redevelopment. I'll probably just kill the feature.

This seems like a silly move: What was previously a very easy to target platform is now much less easy. Was there a glut of user credential theft from the basic authentication API that's caused this? Or is it the architectural purists winning out over engineering pragmatism?

I'm not convinced that, on most devices, it will actually add any security anyway. Consider iPhone application "EvilTwitter". User enables Twitter support. I, evil developer, present a fake Twitter OAuth page. This looks identical to the Twitter login page, carefully configured to hide most of the Safari interface (as 99% of iPhone Safari embedders do). The user enters their details, I steal them, the present a "Woops, wrong password" error. I redirect them to the real OAuth verification page. From here on, my application works fine - the user just assumes they mistyped their details the first time (as mobile device users do, well, continuously).

archgrove··on What ? Adobe Flash for iPhone OS is an open platform ?
I see your point, but I stand by the choice - any process that actually has an group of people sit there and review your app by hand could only have been seen as "open" by very naive individuals.
archgrove··on What ? Adobe Flash for iPhone OS is an open platform ?
Direct quote from Mike Chambers: "Because this is Flash, it is rather trivial to port games created with Flash that target the iPhone to target other operating systems, such as Android."

Which pretty much sums up the entire reason for 3.3.1. Did they serious expect that, going in with this offering, they'd get no pushback from Apple? It's been abundantly clear from day one that the iPhone store is a closed platform, subject to the business ideals of Apple (i.e. make Apple more money). Any sane iPhone developer knew this going in, and really doesn't care (or they'd never have started).

I suspect the correct way to view the iPhone store is not "A horribly closed environment compared to e.g. Windows/the Web", but "A largely open market compared to the PS3/Wii etc". Closed platforms have existed for eons without the world ending, and they'll continue to exist in the future. The real novelty with the iPhone is it sits in the middle - neither open nor closed. People are freaking out trying to shoehorn it into one camp or the other, when it's just not possible.

archgrove··on Ubuntu Is A Poor Standard Bearer For Linux
Well, even if I did set it all up for them, the point is that it will happily break itself without doing anything other than the recommended updates.
archgrove··on Reboxing iPad
I think EPSN (and porn :) are basically just video. Porn is normally at the cutting edge of tech, so I expect <video> there soon enough and I'd guess EPSN would get it once enough of their users start moaning. So, in the long term, this once again just leaves "games" - something the iOS isn't really suffering a shortage of.

I didn't believe it even 6 months ago, but given how many sites I use are now rolling out <video>, I'm coming around to the idea that Flash could be largely irrelevant within a year or two. The only holdout that might cause problems will be the landing page/"entire site as flash" 'designer' nonsense. How quickly those transition to HTML 5 (or a sane end user experience) will be interesting to watch.

archgrove··on Reboxing iPad
Fair enough, though I wonder if you really need to buy it to realise that you don't have a use for it. I suppose a trial run is reasonable, in case it has some magic use you don't consider till you have it.

I'm still though, to this day, boggled by the commenters who seem to think that a Flashless browser is crippled. What sites do these people use all day whereby the Internet is entirely useless without Flash? I see it only on an occasional Flash Game and video sites who have not yet rolled out HTML5 (a number dwindling month on month). Once a particular TV catchup service I use deploys <video>, I'll literally see Flash once a week.

Is there some usage pattern for the web that I'm unaware of, wherein people require Flash continuously?

archgrove··on [dead]
Good lord. I need some kind of super-flag to hammer this kind of idiotic, vitriolic, nonsense into the nearest incinerator. Though by the tone of it someone already missed the incinerator, hit the author, and caused serious brain trauma.

Because of an offhand comment during a Q & A about possibly filtering some ads, the logical conclusion is that Apple is going to censor political and advocacy adverts. Well, perhaps. Then the logical conclusion of that is that the government will, in some kind of bizarre revenge strategy, spring into action with anti-trust lawsuits against Apple (for what is not made clear), whilst the Pope calls for a holy war against all things Steve hath made? The conclusion of the chain is that this might take down all of Apple?

Freedom of expression doesn't guarantee that a network has to carry your expression, and there are plenty of advert vendors who filter their content aggressively (many print magazines, children's outlets etc). This does not cause the implosion of the underlying company, nor a jihad directing users to march on the corporate HQ.

I would seriously suggest that the author, who spent $500 for a device he hates and maintains a weblog all about hating this device, would find a better use of his time and money in therapy.

archgrove··on Ubuntu Is A Poor Standard Bearer For Linux
The specifics of the post may be written in a troll-like style, but the key points are quite valid - I've had very similar experiences with Ubuntu. Running an "apt-get dist-upgrade" update last October entirely hosed support for my (pretty damn common) network card - transferring at anything above about 5Mb/s would lock the network driver. I had to manually discover this, and hand-correct the hosing until they finally shipped a kernel > 2.6.30.

The machine is an entirely standard, off the shelf, Atom based PC. Taking the "Could I give this to a non-IT expert" test, it failed entirely. I'm not saying that this couldn't happen on a non-Linux system, but a) I've never had it happen to Mac or Windows b) Trawling support forums and kernel bug lists to discover the cause isn't good enough for end users and c) Waiting 4 months for a non-hacky fix sucks. As it stands, I could never seriously recommend Ubuntu to a non-tech savvy friend.

I suppose this is just anecdata, but I'm certainly not alone (another friend can tell you a similar story about sound cards, for example).

archgrove··on New iPhone Agreement Bans Flash-to-iPhone Compiler & Others
I can think of only two (tenuously) justifiable reasons for this.

1 - Perhaps, during the beta, they want code written in C (and derivatives) to aid in debugging framework bugs. Rather than "My App doesn't WORK!!!!! (Using MonoTouch Vxxyy)", they can get a repro using a stack they know and control top to bottom. In this case, I can see it as justified.

2 - If it's specifically to target cross-compilers as a business decision, to ensure that iPhone only gets "exclusives", then I suppose it's their prerogative. It will probably backfire long-term, as their market share isn't that dominant. "Browser, Palm, Android + all else" or "iPhone" makes the iPhone a secondary port target versus a first class platform.

If it's any other reason, it is ridiculous. It makes me seriously question my upcoming Mac Pro & iPad purchases. Even though I currently develop for Mac and iPhone using only Obj-C, I can't build a development strategy around a schizophrenic "partner". What's next - documentation not written in Pages? Failure to use Steve's favourite colour in the background? It's getting... bizarre.

archgrove··on The iPad Literally Breaks Every Use Case I Had For It
Well, the browser has tabs (at least, the iPhone Mobile Safari does, so it's no stretch to think this does as well). The lack of a camera is, I agree, silly.

Rather than rebut the rest of his "points" directly, I'll focus on "multitasking". Frankly, the iPhone and iPad do multitask, in the ways that are important to (most) people. Multitasking in an end user product really means "I can do more than one thing at once", not "The computer runs many processes". The iPhone OS currently accomplishes exactly this, via saved state.

In any well behaved iPhone app, if you quit, the state of the UI and your data is persisted, so that when you return, it's like you never left. The UI for this multitasking is a bit clunky - hit "Home" then pick the app - but for most people, this works fine. There are only two situations when this doesn't - when the app does something interesting in the background, and when the "stack" of application interactions collapses - if I click a mailto: link to open Mail, quitting that doesn't return me to Safari - I have to go there again manually.

The two cases of "Does something interesting in the background" that really people want are audio streaming and notification of some event, and they're real problems. However, Apple's persistently said they're trying to protect the user experience (stability, battery life etc) by denying background apps. I've no reason to believe this isn't the case (I'm mean really, what are they gaining except geek ire by restricting this?). The audio case is annoying and needs a solution - the notification case is slightly better since push was rolled out.

Outside of these cases, the iPhone multitasks well enough for 99% of the world. His reading case, catching up on the news etc all are handled - you just have a slightly painful app switch process (i.e. you press two buttons rather than just one). The only case that isn't is background movies/music from 3rd party apps - and really, the only sensible case out of that is music (Do you really watch a movie and browse at the same time on a 10" screen?). Regardless, I suspect the point will be moot soon enough - OS 4.0 seems very likely to bring some notion of background processes.

The geek anti-iPad ire really confuses me. What did we expect, other than what we got? It was never going to run OS X - the user experience would have been awful without major changes that broke all 3rd party OS X apps (and then, what's the point?). The hardware, modulo camera, seems entirely reasonable at a price that's damn good - who realistically expected anything more from an affordable tablet machine at this point in technology? The "walled garden" is a real issue, but I think we have, as a group, gained far more than we've lost with the App store. All these people saying "I could never have been a tinkerer with an iPad" - poppycock. Download the SDK for free, develop all you want. Pay a nominal fee to deploy to 100 other devices without ever giving Apple a look at your app. Or hell, just jailbreak it if the limits of the SDK are so onerous.

Alternatively, just don't buy it. Having chosen this please, stop filling up HN/Reddit/The Internet with "The iPad doesn't raise the dead, make me a billionaire and cure cancer, so all my dreams are shattered and Apple is awful".

archgrove··on [dead]
Um. OK. It's a holding page for another "Stealth startup" doing search. Come back to me when you've actually got a product or got some important, non shill people I trust excited.

Stealth Startup is, in my dictionary, largely congruous with "No product"

archgrove··on The Muggle Coder
Good for you - this is the way it should (and for most sane people, does) work. You ignore the tools until you understand what they're automating. One day, you'll get bored of writing boilerplate and trying to design the best UI by compile/run/repeat, and you'll go back to the tools for their appropriate uses.

It's always a benefit to understand exactly what's going on under the hood but I've seen some people take it too far, making this initial "I'm going to understand it properly" benefit into a curmudgeonly handicap^1. "I'm hardcore, I write all my UIs by hand! Those new fangled IDEs with their magic autocomplete - I keep my documentation on 430 sheets of fanfold printout! When I was young, we wrote all our code by hand using ed in Sanskrit, printed it out and hand soldered into hardware using tools we made by smelting our own iron!".

They're often right, to a degree - they can still write reasonable programs, and they'll likely have fewer defects than a person who just blindly uses tools. However, they often can't work in teams or adapt rapidly to new developments, and development change times are orders of magnitude above those who both understand the tools and when to use them.

1 - I'm not accusing the author of this problem, but the general tone does set a few alarm bells ringing...

archgrove··on Gravity versus electromagnetism ...
It's a nice example. Another one I like is "It takes the whole earth to attract this small iron object, but only this small magnet to overcome that pull"
archgrove··on Twitter URLs and Limitations
If I were writing a popular URL shortener, the most useful thing I could add would be short (2 character) prefix to the random link, indicating the target type (e.g. video is foo.bla/vd12345). This fixes a pet peeve of mine, when I follow an Mobile Safari link to Youtube on an EDGE network, causing an application shift. Also, 95% of videos on the web these days are better rendered in text, and I just want to ignore them.
archgrove··on The “Good” Student
I'm going to assume the actual statement "Good students are good at everything" is a quote that is, at best, rather out of context. It's patent garbage; I often take classes (and advise others to take classes) in things I know I'm no good at, either to advance from "Useless" to "OK", or just because it's something I enjoy. My art skills are truly awful and I'll never get top marks, but it wouldn't stop my taking an elective, because I'd like to be better and enjoy the area.

People who constantly get top marks in everything are, to me, suspicious. Mostly anyone who's smart can pick a syllabus they'll ace - but will they gain anything from it? Now, if they're getting constantly low marks, or random mark disparities in seemingly related areas, that might be a legitimate concern, but to blanket it as "Good students are good at everything" is just bizarre.

archgrove··on Tell HN: StackOverflow is just terrific
I've tried this approach; taking the time to give a detailed answer with reasoning behind my choices and explanations for areas that might be unclear. Two things happen:

1 - The fast, but "good enough" answer wins out for the short term 10+ votes (and "Accepted status), then the question falls into the mire, occasionally floating to the surface via a Google search, where I might get one or two votes.

2 - My answer is accepted, enough that noone else bothers to partake in the question, and it falls off the radar having received maybe 1 or 2 votes.

In terms of getting good answers into the system, I guess things are working as intended. In terms of creating an engaging experience for the questioner and answerer, this seems sub-optimal.

← PreviousPage 7 of 7