Either you're using a sign bit, or you are missing a finger. 10 bits gets you a range of 0-1023 or 1-1024.
Chromebooks aren't exactly fast or high-res. Unless you buy the Pixel, but then you might as well buy a real laptop. I wouldn't stick an employee with a slow half-top and expect them to be productive.
Most schools (and corporations, even) with private networks require you to re-register your adapter when your MAC changes. So it wouldn't really work.
That's what I'm saying. Cheers!
That happened to me with a 10' $5 cable from Monoprice. Out of desperation after I broke it the other day, I bought a 3' $5 cable from the bargain bin in the cell phone accessories department at a big store that I usually don't go to... last resort, I know, but it couldn't wait until the next day. And the $5 cable works like the OEM cable.
UI design is good when it enables you to be efficient at a task and it does that. I agree there. However I think his point is more of a UX point. How do you learn other than just hitting things to see what they do? There's no manual, no alternative noob mode with text, no hover-for-tooltip, and no help file. Users shouldn't have to enlist the aid of another user.
User thoughts might include: Is this going to break something? Can I undo it? I'd better not touch it. How do you Google an icon? (You don't.) Why is that there? Where is the menu? Where is the list of things I can do here? I don't want to break anything. It's scary/frustrating because I don't know how to use it, but there is no guidance.
Eventually, you get enough of these negative/confusing emotions and the thought "Ah well, back to iPhone" forms. I've seen it firsthand with several people who tried to switch because they kept having thoughts like that during the whole return period on their Androids.
So you see, it's a fairly basic UX misstep that could be avoided with some sort of hint. It's really unfortunate that it happens all over the Android ecosystem because I like it and want to see it succeed... but they're really shooting themselves in the foot still.
It's when you get two Cheetos that fused together during manufacturing.
You jest, but I'm sure I've rolled my face around on my keyboard and produced a Perl script that does that.
Yup, especially restaurant menus, which are *always* in PDF. It's frustrating when you're on mobile and just want to see the menu before you commit a large party with diverse dietary restrictions to going somewhere.
It's like your sig says.
Trolling is a art.
Go ahead, try to sing "Jumpin' Jack Flash" accurately without looking at a lyrics sheet.
I dare you.
or "Louie Louie"
The good: Visually impressive. The sound was excellent. 3D was tastefully done and not gimmicky. Special effects didn't seem to overreach and I wasn't sitting there irritated by a lens flare overload. Good cameo for Stan Lee. The extra scene at the end of the credits (like in every Marvel movie) left some interesting loose ends.
The bad: It seems like they cut out some minor parts of the plot and various explanations/reveals for things so they could fit more action into the time allotted. At multiple points during the movie, I thought to myself, "What is this and why didn't they introduce it?" Maybe it's a movie for people more familiar with Thor's comic book history.
I bet they will put some of the things I wanted in an extended director's cut later. So I'll probably watch for that in the stores in a few months.
Summary: It was a pretty interesting fantasy/action movie, and is very appealing to the senses. Don't leave until ALL the credits are over. The fact that I *wanted* additional exposition is good. I am just a little bit dissatisfied. Worth it for a matinee showing at least.
Sweet, ANOTHER "standard".
Did we really need it?
And how do you propose to know if any particular compiler or library is or isn't compromised?
Promotion in that position? What's that look like?
I hereby promote you to the rank of "Corporal Chair-napper over by the nukes"...