HNHacker News
TopNewBestAskShowJobs

kapowaz

237 karma · joined February 6, 2012

submissionscomments
kapowaz··on Apple rejecting applications which use Dropbox
Ethics are objective now? I personally think it's a dodgy move on Apple's part, but I think the knee-jerk reaction is over the top, particularly given how Apple's policies on in-app-purchase are still quite nascent.

It's easy to castigate this as a monopolistic move intended to benefit iCloud, but the reality is that Dropbox and iCloud aren't directly competing services. Really this is about how third-parties offer purchasable services from within iOS. There is a trade-off to be made between what offers the best user experience and what is practical for third-parties though, so I have to imagine Apple will eventually be more flexible.

kapowaz··on Apple rejecting applications which use Dropbox
I'm surprised it took this long for an extremist, reactionary post like this to reach the top of the comments.

Remember: Apple couldn't possibly be a large corporation whose objectives and principles occasionally conflict in a way which causes collateral damage to their users or developers. They only care about squeezing out the competition through any means necessary.

kapowaz··on Google HTML/CSS Style Guide
> Avoid qualifying ID and class names with type selectors. Unless necessary (for example with helper classes), do not use element names in conjunction with IDs or classes.

I've never heard a decent explanation for why, with this one. Unless you're intentionally creating a rule which is broad in scope, adding the element name helps document a rule, giving somebody who is unfamiliar with this CSS some context on how the rule is used. Other than saving a scant few bytes here and there, I can't see what the benefit is.

kapowaz··on The War On RSS
You're implying that the user interface and metadata of a site like twitter has no development or maintenance cost?
kapowaz··on The Real Cost of Used Games
Richard doesn't do himself any favours in how he goes about persuading the reader of his point. Judging by a lot of the comments here on HN a most people read the opening couple of paragraphs then drew their own conclusions, which may or may not have been on the money.

The important take-away point for me (which I've never seen expressed before) is that so long as publishers are fearful of the pre-owned market, they will spend (waste?) development resources on features whose sole purpose is to further retention and disincentivise reselling games. Some of those features will be fun, but they will potentially alienate some gamers who feel they're no longer getting good value in their game. Witness how the First-Person Shooter genre has transitioned from story-based campaigns with a small multiplayer component into a far more multiplayer-centric experience, with a short single-player campaign which a lot of gamers simply ignore. Similar things have happened in other genres too.

Where I find myself disagreeing with Richard is that because GameStop have ‘used the nuclear option’ already, publishers and console manufacturers should do the same; when your customers are the collateral in this exchange, they won't thank you for it. We're also in a period of upheaval with videogame retail (I don't know how well GameStop is doing, but certainly in the UK high street videogame retailers are dying). Maybe in a few more years’ time the problem will solve itself, with the majority of customers choosing to buy direct from online retailers; the tactics that GameStop employs that have such a dramatic effect can't be employed when you're selling second-hand games through Amazon.

I can't think of a good interim solution off the top of my head, maybe there ought to be more stringent laws to prevent retailers from pushing used stock over new stock, or that they're prohibited from selling used stock at more than a certain percentage of the cost of new. These ideas probably have holes, but I'd rather see something along these lines pushed than see consumers be punished for somebody else's war.

kapowaz··on OMGPOP CEO tweets: "Shay Pierce was the weakest employee on the team"
I'm not sure how many folks who read Hacker News work in videogame development, but for any who are, I'd like to propose something simple: refuse to work for Zynga. Extend this boycott to any videogames company that behaves in this contemptuous and insulting manner towards the people who actually generate the real worth in the company.

Sentiment towards the likes of EA and Sony are at an all-time low for their consumer-hostile behaviour, and I think the market is ripe for being shaken up. We've already seen in recent weeks that the games-playing public are prepared to reach into their wallets even in the middle of an economic downturn and help fund videogame projects through Kickstarter.

If the people who make videogames refuse to be treated like disposable commodities by obnoxious pricks like Dan Porter by boycotting working for them, then eventually these organisations will have to change their ways, or risk being replaced by companies who will treat their staff with respect and humility.

kapowaz··on It’s Not the File Size That’s Killing iPad Magazines
I've pretty much ignored the entire concept of iPad magazines (via Newsstand) until I got my iPad III. Right now I'm trying out the free 7 day trial of The Guardian, and I'm impressed. It's £9.99/month, so I'm still debating if it's worth it, but after 4 days I'm leaning towards yes.

Why? Well, in contradiction of the original article's charges, it does innovate and provide more than just a static page by page experience. You can navigate in a page-by-page sense, but it also groups subjects, provides links to other articles, and has a top level navigation. The front page [https://img.skitch.com/20120321-jg1fn7y9u4ktw7ktx229uygnja.p...] does a great job of highlighting interesting subjects that day, and where an article has a video it can be played inline.

In many ways it's basically a heavily device-oriented website, but it has the advantage that all the content is downloaded automatically each day (without me having to remember to download it whilst on wifi before I head onto the tube). Also, unlike many of the magazines on Newsstand, it actually embeds their gorgeous Guardian Egyptian Text typeface [https://img.skitch.com/20120321-1xb6ybrcyem76rw29569tf9kp5.p...], so even though most of the graphics aren't retina-resolution yet, the text is still beautiful to read.

Contrast this experience with Edge magazine. I've been reading this in print since 1995, and it's always been a high-production quality publication. I'd expect the iPad experience to match, but it doesn't even come close. Apparently one of the oft-mentioned magazines which simply bundles up a bunch of JPEGs, I could probably get past that were it not for the horrible way it loads each page, first apparently using a low-resolution image resized to fit, then gradually drawing in the full-resolution image in tiles [https://img.skitch.com/20120321-kam5qxxn3rens7a1x534jgyidh.p...]. This happens with every single page transition, even with pages you've already visited, meaning that switching between two pages of a gatefold article is an incredibly irritating process. Also, as it's a resized image, the text isn't especially clear, particularly when you compare to the high standard The Guardian sets.

The way I look at it, if old-world print publications want to survive the transition to digital, then they can't expect to get away with the latter, but instead should be striving towards the former. Make a good product and people will buy it. Try and push rubbish and when you finally discover you have to stop the physical presses, the virtual product won't stand up to scrutiny.

kapowaz··on Icon Fonts are Awesome
I am worried by this trend towards using a custom typeface to store icons. Firstly, whilst it looks great in the giant preview pages linked to on HN, these icons often look terrible at smaller sizes / without anti-aliasing. Secondly, whilst they're undoubtedly efficient when you're going to use a lot of them in various sizes, I question whether that's still true compared to an optimised PNG sprite (which coincidentally can solve the first problem too).
kapowaz··on Mozilla is looking for help for its browser-agnostic Web documentation
I'll volunteer to write something about vendor prefixes.
kapowaz··on Designers read this and developers will love you
I would love for this hypothetical tool to exist, but the problem doesn't lie with the tool, but that you're talking about essentially different workflows. Designers tend to use the tools that they're most familiar with, that give them what they need. Usually that means Illustrator + Photoshop (or sometimes, Fireworks).

I've given thought in the past to a hypothetical tool that I'd love to see that does a lot of what Photoshop does. It would use a nested plaintext file structure, letting it work with a version control tool (imagine being able to diff two PSDs and know that all that changed was a label value, or a single layer being removed, rather than it being a completely opaque binary change?). It would effectively provide direct access to the advanced features of CSS, only with a nicer UI. It could be built to allow testing responsive layouts all within a single document. All this and more. It'd be great.

But designers wouldn't want to use it. It wouldn't be grounded in their essentially visual workflow. Sure, you could have intermediaries translate documents between the visual and the quasi-layout-based, but that's even more work than just having designers adopt better practices. What's more, these practices don't just benefit developers: it'll make life easier for designers too! That's what makes it such a no-brainer. Sure, some lazy or precious designers might object to being told how to do their job (nobody appreciates being told they're doing things wrong), but if you introduce these practices gently I'm sure they'll pay off.

kapowaz··on Designers read this and developers will love you
In a nutshell a layer comp is a saved state for your layers. It can include any/all of: visibility, position and layer style. A combination of these should let you create alternative views for practically any sets of states provided the original layers give you what you need.

For example, a navigation interface, complete with hover and selected states can be all done with the same text and icons (say) if you have a vector shape layer for icons, and then apply separate appearances for each interaction state.

The example you give can be done as simply as toggling the visibility of a layer you don't want to see, and moving other elements up to fill the void appropriately, then saving this as a separate comp.

kapowaz··on Show HN: I decided to document and share my high-level CSS best practices
> This document is a personal one

Then they're implicitly not ‘best practices’.

> We’re not Facebook, but we are big.

Then it's possibly appropriate. I remain unconvinced even in large projects but I do think CSS is lacking some important features that would make this kind of practice redundant; the kind of things that LESS and SASS provide, like variables and mixins.

> Heavily location selectors hinder flexibility; components should not rely too heavily on where they live, they should be movable as easily as possible.

This again makes presumptions about what kind of site you're building. If you're aiming for heavily modular, reusable components where you'll be repeating markup patterns throughout, it may be more appropriate. Nonetheless, the example you cited looked like a small, common pattern that is easily self-contained enough to be reused in this way.

> IDs will only ever hinder a CSS developer; they offer zero benefit (where CSS is concerned) over a class, thus why would you ever bother using them?

Specificity is an important part of the cascade, and a tool in your box. Being able to target an element with a higher priority than another without needlessly complicating the selector is a feature I wouldn't voluntarily give up just because of some nebulous claim of harm they might cause. Another reason is the same one I don't agree with stripping off element names; they are self-documenting and give developers clear, unavoidable signposts about the nature of the elements they're targeting.

> I’ve just finished the rebuild a massive front-end, the project as a whole took over a year. Number of IE stylesheets: 0. It can be done.

Every project is different. Some will accept layout degradation in older browsers. Some won't. Some will demand extravagant layout effects that require extra time and effort to get working well in IE6-8. To suggest that IE-specific stylesheets are something you should be striving to omit is to needlessly burden developers with (potentially) unreachable goals.

That's the crux of my problem with these ‘best practices’ — developers who've yet to spend a lot of time thinking about how to structure their CSS well could come across these and head off in all manner of wrongheaded directions. Maybe that's why there aren't any universally agreed-upon CSS best practices beyond more simple techniques; the general rule I take with me is ‘YMMV’.

kapowaz··on Show HN: I decided to document and share my high-level CSS best practices
> For each level of markup nesting, try and indent your CSS to match.

Nope.

> Also write vendor prefixed CSS so that colons all line up

Nope.

> When building a new component write markup before CSS

Yes!

> Instead of building dozens of unique components, try and spot repeated design patterns abstract them; build these skeletons as base ‘objects’ and then peg classes onto these to extend their styling for more unique circumstances.

This is a bone of contention amongst front-end developers. If you're Facebook, and you have a deep and wide site architecture that would otherwise result in masses of duplication, this makes sense (although arguably using CSS preprocessors like LESS or SASS would make even more sense), but these rules do not make sense for small to medium sized sites. If anything, they encourage a thin layer of abstraction on what would otherwise be entirely presentational markup. You were on to something when you said start with your markup: classify your marked up elements by giving them IDs and classes according to what they are and what they do, and then declare rules for how things of that type want to look.

> All components should be left totally free of widths; your components should always remain fluid and their widths should be governed by a grid system.

Nope. Again, grid systems are something that should be used on a case-by-case basis, according to the nature of the site you're building.

> Heavily location-based selectors are bad for a number of reasons.

Nope. What you're arguing against is a rule that has a high degree of specificity. Naturally there is a sane limit to how specific a selector should be (if you want to avoid specificity wars) but `.sidebar h3 span` is not too specific a rule.

> An over-qualified selector is one like div.promo

Alternatively you might call this a self-documenting selector. If you're going to apply a class to multiple types of element and you want them to all inherit the same rules then sure, don't apply an element name too — otherwise you're adding classes which communicate zero information to a developer unfamiliar with the markup structure.

> Do not use IDs in CSS at all.

NOPE NOPE NOPE NOPE NOPE. Understand specificity rules. Write good selectors. Don't outright ban IDs just because you're not careful enough to write clean CSS.

> As a general rule, all layout and box-model rules can and will work without an IE stylesheet if you refactor and rework your CSS.

Hahahahahahahahahhaa.

I'll echo comments from others here; these are not ‘best-practices’ — they're just a set of arbitrary rules that you might find work for you, but you might find they don't. I'd argue that if you enforce these vigorously, your projects are succeeding in spite of these rules, not because of them.

kapowaz··on Blizzard Lays Off 600, Including About 60 Developers
Are you saying these people voluntarily built tools that effectively made themselves obsolete?
kapowaz··on The cause for all your Mac OS X mouse annoyances
I've long disliked the acceleration ‘feel’ of Mac OS X, and have worked around it with acceleration-curve adjustments etc., but I find the explanation provided highly doubtful. Why? Well, for one: various games circumvent OS X’s own mouse speed/acceleration settings, and when they do so instantly reproduce the ‘feel’ from Windows. The same is true when emulating Windows through virtualisation software. If this was a hardware lag issue, then surely both of these would be affected too? And even were it a hardware issue, it shows that you can remedy it in software.

I'd long believed that the problem would never be addressed, and then a couple of months ago I used a new Apple Magic Mouse with Lion; the acceleration and speed was so good out of the box that I didn't install USB Overdrive as part of my new Mac setup routine for the first time in over 5 years. Could it be that it's a driver issue, or just different devices have different acceleration characteristics? Perhaps, but whatever the case might be, I'm far less inclined to attribute it to input lag.

← PreviousPage 3 of 3