Monday, January 23, 2017
Saturday, January 21, 2017
Thursday, January 19, 2017
Monday, January 16, 2017
Sony's blu-ray player eternally on-going train wreck of pure badness makes me wish they would get hammered with a class action law suit for shipping broken shyte products, or that all consumers everywhere would grow a backbone and boycott all things sony. I know I will.
Sure, the whole blu-ray thing is a complete and utter end-user usability debacle from start to finish, but somehow Sony goes that extra mile and introduces extra bugs like having the box stop responding to the (perfectly good, working) remote control while it is playing even regular DVDs.
Anybody involved with blu-ray should go out of business immediately, if you ask me. But with extra special love in it for Sony. The company who offers live chat customer service, makes you jump through hoops, and then tells you on we're closed ha ha. (BofA did that to me recently as well. If I were dictator, bad UX would be a severely punishable offense.)
Sure, the whole blu-ray thing is a complete and utter end-user usability debacle from start to finish, but somehow Sony goes that extra mile and introduces extra bugs like having the box stop responding to the (perfectly good, working) remote control while it is playing even regular DVDs.
Anybody involved with blu-ray should go out of business immediately, if you ask me. But with extra special love in it for Sony. The company who offers live chat customer service, makes you jump through hoops, and then tells you on we're closed ha ha. (BofA did that to me recently as well. If I were dictator, bad UX would be a severely punishable offense.)
Saturday, January 14, 2017
Wednesday, January 11, 2017
Webapps are a lie, at least when it comes to basic usability and user experience. I mean sure I guess my favorite feature of bloody Google Groups (in Firefox, but whatever!) is how their compose UI just screwed me and lost my message when I accidentally hit the 'back' shortcut on my keyboard, and going 'forward' doesn't restore my message text.
Tuesday, January 10, 2017
JavaScript is horrible. Just, horrible. I mean, if you ask me.
There are things which purport to address some of JavaScript's problems in various ways. Take Facebook Flow: advanced typing for JavaScript. Yeah, well, no, kind of a fail there from my experience. I am not trying to say it is easy to do, not at all. I am just saying that I feel like all these things (Flow, Typescript, PureScript, whatever) are way overhyped vs. what their actual UX is like, at least right now. I wish there were better ways for developers of such project to know themselves, and then to represent to potential users thereof, exactly how far things work, and where they start to fall apart.
And I wonder if there's really much ability to save something that starts out as a dynamically typed language. (Especially one that has as many screwy layers of abstraction heaped upon it, each attempting to fix fundamentally missing/broken things about the original language ecosystem, and all versions since. All the versions of ES specs. All the ways to use Babel. All the different competing approaches to modules. Etc.) I mean things like Haskell and Ocaml have enough trouble, and they were designed from the ground up to be nicely typed, by people who really cared about it. Oh god I'm so depressed.
What really explodes my mind in a meta depressing way is that somehow, apparently, for whatever group-think brain-washed stone-dumb reasons, this is never sufficiently called out. The Emperor's computer has no clothes!
There are things which purport to address some of JavaScript's problems in various ways. Take Facebook Flow: advanced typing for JavaScript. Yeah, well, no, kind of a fail there from my experience. I am not trying to say it is easy to do, not at all. I am just saying that I feel like all these things (Flow, Typescript, PureScript, whatever) are way overhyped vs. what their actual UX is like, at least right now. I wish there were better ways for developers of such project to know themselves, and then to represent to potential users thereof, exactly how far things work, and where they start to fall apart.
And I wonder if there's really much ability to save something that starts out as a dynamically typed language. (Especially one that has as many screwy layers of abstraction heaped upon it, each attempting to fix fundamentally missing/broken things about the original language ecosystem, and all versions since. All the versions of ES specs. All the ways to use Babel. All the different competing approaches to modules. Etc.) I mean things like Haskell and Ocaml have enough trouble, and they were designed from the ground up to be nicely typed, by people who really cared about it. Oh god I'm so depressed.
What really explodes my mind in a meta depressing way is that somehow, apparently, for whatever group-think brain-washed stone-dumb reasons, this is never sufficiently called out. The Emperor's computer has no clothes!
Friday, January 6, 2017
Things a good programming language should do, even if they are Hard, and which your own favorite language surely fails to do some of:
- help clone things.
- help do equality/comparison testing.
- have 'where' as well as 'let'.
- have something like newtype deriving.
- help automatically clean up resources other than memory.
- have as many things be 'first class' as possible.
- support reflection/introspection/mirroring.
- support named parameters, optional parameters, and partial application.
- do varags in a way that doesn't suck.
- not use case sensitivity for anything too important.
- lean toward being as close to statement-free as possible.
Tuesday, January 3, 2017
I keep wanting to like and use F#.
I keep seeing F# be leaky layers of abstraction epic fails.
I keep giving up and going running back home to momma / java / javascript now.
I keep seeing F# be leaky layers of abstraction epic fails.
I keep giving up and going running back home to momma / java / javascript now.
Monday, January 2, 2017
How it came to be that the space bar is used for more than one thing in a browser I dunno, but it sure does kill me. Mostly I just want it to be a space bar. Secondarily I want it to scroll the page. Anything else is just plain dumb wrong, like having it open/close a widget I just clicked on on a page.
There is no justice in the world when it comes to UX. (There's also not really any fundamental justice in the world at all, of course, and that's a much more deeply disturbing sad thing about human nature, but it doesn't seem like I can do anything about that.) If there were any justice in the world when it came to UX, Nintendo would have gone out of business as soon as they released the Wii or the 3DS.
The world of home a/v receivers is a wonderfully rich horrible hateful bad evil dumb broken idiotic backwards dumbass UX.
- The UI of all receivers is, apparently, like dog barf. And no I don't really want to have to dedicate my cell phone to fixing their UI problems so "having an app" doesn't satisfy me.
- Simple things like remembering that I had "night mode" audio compression on.
- Advanced features like auto diagnostics that show me what part of the audio/video path is failing. Both in terms of standard crap like HDMI handshake failures, and in terms of long-term out-of-warranty internal hardware failure.
- The front panel is just pathetic. It should be a full on bitmapped graphic display.
- Physically I haven't really seen a receiver that isn't sorta just gross or lame. They are neither something that is cool enough from a technonerd perspective, nor attractive enough from a tasteful home decor perspective.
- The rear panel hookups are always a nightmare once you've ever installed things. Just physically being able to get back and change things.
- Rear panels are often not designed well e.g. on Denons it looks like often the component/composite video input is not physically lined up with the matching audio. So that's a bloody nightmare if you are hanging over the back of the equipment trying to read the labels upside down.
- Anybody who uses an intense blue LED (this includes things like Panasonic M43 cameras' "iA" button) deserves to be taken out and shot. If you ask me.
- The fundamental problem in my mind is that a lot of receiver UX fails to make the abstractions make sense. Instead of manually digging through menus and manually mapping inputs and outputs, the UI should more automatically help map things; should also show things visually e.g. (strawperson idea) show a vertically scrolling list of inputs on the left, and a vertically scrolling list of outputs on the right and let you match them up.
Sunday, January 1, 2017
There doesn't seem to me to be enough economic punishment in our socioeconomic system for bad UX. For example, Barnes & Noble's web site doesn't tell me explicitly if something is/not available at the local store. I apparently have to infer it from the totality of what is displayed as the details e.g. it says I can have it sent to me by Thursday or whatever so I guess it is not in stock locally. Not that it even shows me if it knows what my local store is. Or would let me find out if the item is in stock at any other store locations around me. Just utterly nuts.
Subscribe to:
Posts (Atom)