Where the design community meets.
When you design something @2x and it's width is 95px what does it become?
Let me explain: 95 / 2 = fuck your designs.
Just do @1x. Only thing that actually needs to be exported @2x is images assets that can't be SVGs. Just zoom the fuck in when building crap in PSD.
Or, make your life easier, design in a vector based tool!
@2x is a pain in the ass for developers because not all values can be evenly divided by 2 so don't do it.
There isn't ever a reason to design at 3x. Who cares what screen you're designing for, if its written in code, it'll scale.
Simple, use even amounts when designing (they can all be divided by 2). It's really not hard. And once again, this topic doesn't need swearing. You'll be more convincing if you're nice. :)
"Simple, use even amounts when designing"
Seriously.. You are just making things difficult for the sake of having an argument.
Sorry, but I don't see that as difficult. And I'm not arguing for the sake of arguing. I'm just not seeing compelling reasons to be convinced to work at 1x. You're free to have a different opinion though :)
Option 1: Be conscious of whether you are using an even or an odd number for every single thing you create
Option 2: Don't worry about it, because you're designing @1x
If you can't understand how you're being difficult, then it's sort of pointless having a conversation about it. You're free to stay in the dark ages of design :)
Im not being anymore "difficult" than everyone here who clearly seemed to have made up their mind, despite what I see as reasons to design at 2x. But your comment is funny to me, because I see 1x design as being the old school approach. :)
This is starting to reek of /r/iamverysmart
Whether you see designing @1x as being the old school approach is kind of irrelevant, since you are just not coming off as someone who has any authority to say so.
And I never said that designing at 2x doesn't have issues (in fact I point some out in my article), but designing at 1x has issues too. You can work at either resolution as long as you know what the issues are. Both have pros and cons.
Ask your developers who implement how they feel about @2x. That is the only reason you need.
I am a developer too. There's no problem implementing my designs.
Well then aren't you something! You should write a book about this topic since you're so positive it's the best way to do it!
You'd be more convincing if you weren't condescending and assumed your way was the right or only way :)
So trying to support my opinion is being condescending? What about all of you who disagree? Are you all condescending? I'll change my opinion when I see a convincing argument against it.
Your inability to hold someone else's opinion as a possibility while immediately refuting it is the condescension, dude.
The fact that you've hit every comment with "nope not this way" or "nope done that already this is the best" makes you the biggest dick in this thread (even bigger than me calling you one).
Here's something you should say aloud daily (or at least the amount of times you refute someone else's thought)
It is the mark of an educated mind to be able to entertain a thought without accepting it. - Aristotle
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.