by schiaparelli » Mon May 12, 2014 8:53 am
—i'm sort of in "design school" (taking some but not all of the traditional design major curriculum here, but i still have a desk in studio). the professors run the gamut from pragmatically humble to snobby aesthetes. i guess i came into design from this very applied low-key understanding of design as making nice posters and whatnot. i'm happy that my school is expanding my horizons to consider things like…designing for greater social problems, designing for reform, &c. there's this interesting tension between d-schools that do the craft vs. the philosophy vs. a bit of both.
relevant terminology: big-D versus little-d design (big-D design is usually "design that can change the world", "design thinking to solve wicked problems in society", little-d design is posters, tea kettles, t-shirts, logos kinda thing), "design thinking" which is what about half of my classes seem to push—this holistic way of viewing design in everyday life and seeing the world as a designed environment (e.g. considering things like processes and sequences of actions and community dynamics as things that can be designed).
there's an interesting article that's been making its way around the internet called "", and it kind of addresses how design has come into vogue and how current design culture may (from the author's perspective) fail to really solve problems. i think it's a great read.
x x x
the shift key in iOS 7 is the absolute worst. i always think it's on when it's not, and then i turn it off when i want it on because i got so horribly confused…trying to figure out exactly what's wrong. i think in older versions of iOS 7/in general with keyboard design you expect all keys to be the same color, and previously if you hit the shift key it would change bg color to show it was on. now what they seem to have done is make the main keys a white bg and everything else grey to use some kind of visual prominence thing to isolate keys people will use most often (characters + space + dictation) but it's confusing because the convention we expect is different bg = toggled shift. i think?
x x x
—fair warning, i'm a very typography-centric person, but the typography-centric perspective provides to me the clearest difference between using macs vs. PCs for (largely graphic) design, at least.
apple and microsoft employ different type rendering engines in their operating systems. , but i'll summarize it briefly:
OS X prefers to render type so that it's true to the design of it, so small details will remain intact and more faithfully depicted. the downside is that type renders a bit blurry and delicate (due to how the subpixel antialiasing operates, to fool you into seeing certain shapes when there isn't enough pixel density to perfectly display a shape's contours).
windows prefers to render type so that it is sharp, clear, and readable, so legibility is hindered as little as possible. the downside is that the type renders a bit jaggedy and with less character (because less subpixel antialiasing is used).
windows has made available a slightly better rendering system in the past few years called cleartype, but i think it still requires users to explicitly enable it.
there's also some interesting history/drama about how apple at the beginning paid a lot of money to license nice, professional, widely respected typefaces from type foundries (helvetica, hoefler text) whereas microsoft felt too cheap to pay some licensing fees so instead commissioned knockoffs (arial is a knockoff of helvetica—most people would say an inferior knockoff). and to this day OS X has a better set of typefaces than windows, although microsoft has also done some nice things in commissioning really lovely web typefaces (e.g. georgia, verdana, and the C typefaces that were the only good thing to come out of windows vista—calibri, constantina, consolas, &c).
aside from that i can't really think of clear reasons, except that some people say that OS X is better designed and has a better overall eye to design, and designers prefer to work with pretty things.