baptist child abuser thinks he knows jack about shit pt. 2
Timeline
Post
Remote status
Context
6
@f0x Dare I ask, what?
@manfromhuh nicecrew user misunderstood a child going through shock of leading to the near drowning of his younger sister as him not caring (timeline for a childs shock-period for traumatic events is ~1-2 years, on top of the years of processing one will have to do afterwards.) So he threw his young son in a pond and watched him struggle to swim while staring at him and refusing to help as a "lesson" because he is retarded and wants to tell me polygamy isn't a sin, and neither is killing children and animals.
@f0x @manfromhuh holy fuck
@pwm @f0x @manfromhuh I still really don't understand how people like this can even look at themselves, much less EXPLAIN what they're doing to other people as if they think it's OK.
what's fucked up is it has this twisted moralizing dimension to it "you're not sad enough so I'm gonna MAKE you sad!"
what's fucked up is it has this twisted moralizing dimension to it "you're not sad enough so I'm gonna MAKE you sad!"
Replies
3
@manfromhuh @pwm @f0x the idea is that spatial layouts are faster when you already know what you're looking for, so in theory they'll be faster for repetitive workflows. Large targets, the contour of the interface is easier to read and navigate through etc.
the problem is that only works for small sets of interface elements. It's REALLY not good when you need to find a logical place in the layout to shoehorn in every single thing your program can do, a lot of which not everybody is even gonna use. that's another huge problem with this approach, like 60-90% of the features that take up ribbon real estate most casual users AREN'T EVER GOING TO NEED. so it's just dead space that's extremely visually complicated and distracting that you find yourself scanning futilely over and over again while you page through the different sections looking for the little pictogram you need.
building UIs has pretty much become my career at this point, I've done a lot of reading and thinking about them.
the problem is that only works for small sets of interface elements. It's REALLY not good when you need to find a logical place in the layout to shoehorn in every single thing your program can do, a lot of which not everybody is even gonna use. that's another huge problem with this approach, like 60-90% of the features that take up ribbon real estate most casual users AREN'T EVER GOING TO NEED. so it's just dead space that's extremely visually complicated and distracting that you find yourself scanning futilely over and over again while you page through the different sections looking for the little pictogram you need.
building UIs has pretty much become my career at this point, I've done a lot of reading and thinking about them.
@bajax @f0x @manfromhuh I can't think of anything I would rather do less than ui
I will ALWAYS outsource that shit
I will ALWAYS outsource that shit