Sorry, but, please, can we stop this? Schizophrenia is not a "Hi I'm me. 'And I am me too!'" kind of deal. At all. Period. It's not Multiple Personality Disorder, in fact it usually doesn't involve anything like what any media portrayal has ever been. It's more of an intrusive pattern. You know who you are, but there are people whispering, singing, yelling, in your ears - outside your window - in the bathroom - anywhere around you. Telling you to do things? Maybe. Probably not. More like being annoying. But one turns into two turns into many turns into noise and chatter and intense periods of thoughts you can't escape, you can't focus on, and you can't stop. It's incredibly debilitating, but more often than not you have no problem understanding it's not "you" that's in those voices and thoughts - the real problem is understanding that those voices and thoughts are indeed coming FROM you.
The idea that schizophrenia is akin to what you see in Sybil or the media in general is usually wrong. I've yet to see any good reporting on the topic, but people throw it around plenty. "Oh, the market was up, the market was down: it's being schizophrenic." No, if the market was "schizophrenic" it would have trouble concentrating and possibly hallucinate while being extremely paranoid. At times. For the most part it would keep to itself and try to read or at least talk to someone else because it's going through something terribly difficult that no one takes the time to understand.
Interesting, sure, but CSS3 isn't finished, no one adopts it completely, and not supporting IE isn't a doable thing in any corporate environment unless it's an Open Source company. Even then, part of your goal is conversion, so you have to at least be able to reach the people using IE in the first place, right?
Replying late, because I like your post. However, you generally need one iPhone (preferably older but running the latest OS - say, iPhone 4, iOS 7), and an iPad. We've added an "iPad Mini" because whatever...not really sure why. Even if we needed to test the last two gens of each, it's still just iPhone 5x and iPad/Mini. But Android. I hate. HATE testing for Android. It's the worst. QA guy uses Motorola Blah running 3.1, QA department tests against random 7" tablet, Galaxy Note, we have another few coworkers with phones ranging from 2.x to 4.x, and not one device ever produces the same output as the other. One doesn't support the 'click' event (I shit you not), one doesn't like 3D transforms, the other has a problem with z-indexes which only showed between two particular point releases (but he'll never see a fix thanks to the carrier), etc etc etc.
I wish I was just trolling Android, trying to bash, and being all "LOL APPLE YAY," and truth-be-told I'd love it if Android was a good platform, but from a web developer perspective I hate it with all my heart. I'm implementing polyfills for modern browsers, and it's only last year (2013) that manufacturers and carriers started considering Chrome for Android as a default over the stock browser. That's a great step, but it's late in the game. Very, very late. I'd have been on Android since day one (and I've run from 1.x on my Nook to 4.x on my HP TouchPad) if I didn't have to wrestle it to the ground at work.
We learned, years ago, how to deal with IE6-Safari-Chrome-FF. We were never prepared for the hellish landscape that was Android.
Even when you want to network x, you have to manually setup a bunch of configuration on both machines to get it to work, it doesn't work by magic, or autoconfiguration, cause nobody cares enough to do it, evidently, cause even now you have to manually do this, 20 years later.....what a bullshit system....
That's weird, because I have ElementaryOS running on my server at home, and from my workplace Mac or my home-use Ubuntu ThinkPad, I can:
ssh -X -C [host] -l [user]
and I'm good to go. Start firing up xterm, pgadmin, chrome, or anything else on the server just fine, even from work. Sure, chrome gets sluggish over that distance, but it's not really something I'd use often. Other programs though run perfectly fine and are useable considering it's a home-based cable hookup running whoknowswhere out to my office.
The client I do work for has thankfully been very forgiving of what can and can't be done on a mobile device, despite their strict brand guidelines and anal eye (eww) for detail. They've also been somewhat willing to increase budget for fully responsive sites, even if it means 3 more months and a complete overhaul of the codebase. We've done several projects for them with a complete rewrite in mind.
Mmmhmmmm...we had a contractor that did a lot of sorting and rendering of content with Javascript. I went in to fix a mostly unrelated bug, and ended up rewriting it with PHP in a few minutes and removing any need for post-render rendering.
Sure, unless your layout has fixed-width paragraphs. I can pinch and zoom all I want, but if the text doesn't flow with the zoom, then I have to scroll right and read some, scroll left and read some, repeat.
We just wrapped up an annual overview of our sites and properties, and a whopping 65% of our traffic is from mobile this year (not sure if that's tying in tablets, however). They devices in hands are eating up the devices on desks, in our case, but it's hard to say if that's because it's more popular or because we spent time designing to make sure our customers ended up on decent mobile experiences.
Bingo. this is why we employ GOOD designers who follow a design through from wireframe to SASS and then support it for the life of the product. They work hard to learn and incorporate new technologies like SASS, Bootstrap, the Flex model, and others. They write good CSS so the developers can focus on functionality - backend connections making things work, and minimal frontend work to get what the client wants (uggghhhh "infinite scroll!")
And certainly not something you'd ever do, since you haven't tried? I find my "smart" phone does plenty of things I'd rather not do on my desktop - simple games, getting a quick look at/. or stackoverflow (and forwarding pages for later reading to my InstaPaper account), listening to music, making calls or videocalls. Smart phones do plenty of things well, but reading long blocks of text is not one of them.
There are also plenty of good ways around:hover - if you MUST have it, make the:hover state do something useful on a mobile browser. Is it a menu? Make the menu open on:hover if you're finding yourself on a mobile device. Is it a link that just gets an underline? Tag it with some class so that jQuery (or whathaveyou) just knows to go ahead and "click" the link. Watch out for some Android stock browsers though, they tossed out.click() on elements and you have to polyfill:(:hover doesn't have to be removed when you go mobile or responsive, but it should be accounted for in a way that doesn't make the user want to never come back.
That is the best website I've ever seen, and every designer at my job will see it. Bonus awesome for the use of the citation attribute in the blockquote - bam.
Chrome has begun to do more with UA-related stuff. Changing the UA now also implements "bugs" from other browsers. Example: IE7 I think had a weird problem with how I accessed a particular property, and Chrome reported it to me when I set the UA. Desktop at least auto-checks the dimensions for your "viewport," not sure if mobile does too - again, YMMV.
Mostly those assumptions have to with advertisements.
Bingo. I disable ads on desktop, but that feature is missing on mobile. Not only that, but I often find myself accidentally tapping an ad that hasn't loaded (why no width/height tags???).
At the verrrrry bottom is a "switch to full site" or something, but it only lasts so long, and oddly isn't tied to your account settings...
It's such a tough nut though - without a competent design and dev team behind a responsive effort, you can very easily wind up in a bad situation. And where do you draw the line? The Flex model works great on browsers that support it, but then you have to hack around those that don't? So you don't use it, but what do you use? Whether it's a "shame.css" file (also know as "ie7.css ie8.css..."), a separate "mobile" site, or some wacky mix of UA detection and responsive, we're still hacking around things that should be fixed and out of the way. But then Big Client still runs IE FREAKING 8 IN THE COMPANY. In the FIELD. IN THEIR STORES. So, you make the damn thing work on IE8, and usually choke on it so much that you just pull out the icon fonts, backtrack on some HTML5 goodness, get special SASS plugins to convert your RGBA colors into PNGs...and client is happy. And then they open it in mobile and wonder why you never redesigned the separate mobile site - not like you were too busy cursing that they'd never caught up in 2013.
Another problem with the sliding door, which should be even more obvious, is that the majority of consumers will simply not trust Manufacturer because Manufacturer can't "promise" a safe, non-hackable camera. Of course, no one can promise that, but the addition of "privacy cover" implies that there is likely someone out there who can and will use your camera without your permission. While this may be TRUE, the average consumer will certainly see it as a failing of ASUS/Apple/Samsung/etc and not a failing of the government to protect from this (instead of partake in it).
Not to mention that acid reflux can make a "score" higher, as well as too many carbohydrates. Glass of wine and a bunch of bread? Your BAC will read much higher than it might otherwise. Burp up something nasty? It'll read higher. Often times, you're asked to hold your breath and then blow REALLY HARD. One story I heard, they asked the person pulled to blow harder and harder until finally they said "That it's! That's what we're looking for!" So, he blew hard enough to cause the reader to read high enough to arrest.
I like this, except for the Android part. The myriad offerings on the Play store that would fool a parent are too many - not trying to start a war (or participate in it), but for the older folks who just don't "get" computing, I'd suggest forking the extra bit for an Apple tablet of some sort.
1) Any photos, bookmarks, etc that you want to keep: have a copy of it on a backup DVD
LOL I'm sorry but I'm really laughing out loud over here. Backup to DVD? I've written (and rewritten) the instructions to copy a CD for my mom many many times over the last several years. I don't know what it is about "Open - Click Copy CD - Wait" that makes things difficult...asking her, or my dad, to burn backup DVDs is just asking for it.
Slashdot Mirror
UGH.
Sorry, but, please, can we stop this? Schizophrenia is not a "Hi I'm me. 'And I am me too!'" kind of deal. At all. Period. It's not Multiple Personality Disorder, in fact it usually doesn't involve anything like what any media portrayal has ever been. It's more of an intrusive pattern. You know who you are, but there are people whispering, singing, yelling, in your ears - outside your window - in the bathroom - anywhere around you. Telling you to do things? Maybe. Probably not. More like being annoying. But one turns into two turns into many turns into noise and chatter and intense periods of thoughts you can't escape, you can't focus on, and you can't stop. It's incredibly debilitating, but more often than not you have no problem understanding it's not "you" that's in those voices and thoughts - the real problem is understanding that those voices and thoughts are indeed coming FROM you.
The idea that schizophrenia is akin to what you see in Sybil or the media in general is usually wrong. I've yet to see any good reporting on the topic, but people throw it around plenty. "Oh, the market was up, the market was down: it's being schizophrenic." No, if the market was "schizophrenic" it would have trouble concentrating and possibly hallucinate while being extremely paranoid. At times. For the most part it would keep to itself and try to read or at least talk to someone else because it's going through something terribly difficult that no one takes the time to understand.
Interesting, sure, but CSS3 isn't finished, no one adopts it completely, and not supporting IE isn't a doable thing in any corporate environment unless it's an Open Source company. Even then, part of your goal is conversion, so you have to at least be able to reach the people using IE in the first place, right?
Replying late, because I like your post. However, you generally need one iPhone (preferably older but running the latest OS - say, iPhone 4, iOS 7), and an iPad. We've added an "iPad Mini" because whatever...not really sure why. Even if we needed to test the last two gens of each, it's still just iPhone 5x and iPad/Mini. But Android. I hate. HATE testing for Android. It's the worst. QA guy uses Motorola Blah running 3.1, QA department tests against random 7" tablet, Galaxy Note, we have another few coworkers with phones ranging from 2.x to 4.x, and not one device ever produces the same output as the other. One doesn't support the 'click' event (I shit you not), one doesn't like 3D transforms, the other has a problem with z-indexes which only showed between two particular point releases (but he'll never see a fix thanks to the carrier), etc etc etc.
I wish I was just trolling Android, trying to bash, and being all "LOL APPLE YAY," and truth-be-told I'd love it if Android was a good platform, but from a web developer perspective I hate it with all my heart. I'm implementing polyfills for modern browsers, and it's only last year (2013) that manufacturers and carriers started considering Chrome for Android as a default over the stock browser. That's a great step, but it's late in the game. Very, very late. I'd have been on Android since day one (and I've run from 1.x on my Nook to 4.x on my HP TouchPad) if I didn't have to wrestle it to the ground at work.
We learned, years ago, how to deal with IE6-Safari-Chrome-FF. We were never prepared for the hellish landscape that was Android.
Yay!
Baahhh. I liked it up until
Even when you want to network x, you have to manually setup a bunch of configuration on both machines to get it to work, it doesn't work by magic, or autoconfiguration, cause nobody cares enough to do it, evidently, cause even now you have to manually do this, 20 years later.....what a bullshit system....
That's weird, because I have ElementaryOS running on my server at home, and from my workplace Mac or my home-use Ubuntu ThinkPad, I can:
ssh -X -C [host] -l [user]
and I'm good to go. Start firing up xterm, pgadmin, chrome, or anything else on the server just fine, even from work. Sure, chrome gets sluggish over that distance, but it's not really something I'd use often. Other programs though run perfectly fine and are useable considering it's a home-based cable hookup running whoknowswhere out to my office.
They said that the keys weren't on the "compromised" systems
* sorry, complete rewrite of front-end. Usually the back-end can stay in place for the most part.
The client I do work for has thankfully been very forgiving of what can and can't be done on a mobile device, despite their strict brand guidelines and anal eye (eww) for detail. They've also been somewhat willing to increase budget for fully responsive sites, even if it means 3 more months and a complete overhaul of the codebase. We've done several projects for them with a complete rewrite in mind.
Mmmhmmmm...we had a contractor that did a lot of sorting and rendering of content with Javascript. I went in to fix a mostly unrelated bug, and ended up rewriting it with PHP in a few minutes and removing any need for post-render rendering.
That ticks me off, almost as much as "There's an app for [Some Web Site] for your device! Go to the App Store now?!? Yes/No]"
Bonus pissed off if No takes you to the homepage.
Sure, unless your layout has fixed-width paragraphs. I can pinch and zoom all I want, but if the text doesn't flow with the zoom, then I have to scroll right and read some, scroll left and read some, repeat.
We just wrapped up an annual overview of our sites and properties, and a whopping 65% of our traffic is from mobile this year (not sure if that's tying in tablets, however). They devices in hands are eating up the devices on desks, in our case, but it's hard to say if that's because it's more popular or because we spent time designing to make sure our customers ended up on decent mobile experiences.
So, generally? Developers suck
Bingo. this is why we employ GOOD designers who follow a design through from wireframe to SASS and then support it for the life of the product. They work hard to learn and incorporate new technologies like SASS, Bootstrap, the Flex model, and others. They write good CSS so the developers can focus on functionality - backend connections making things work, and minimal frontend work to get what the client wants (uggghhhh "infinite scroll!")
And certainly not something you'd ever do, since you haven't tried? I find my "smart" phone does plenty of things I'd rather not do on my desktop - simple games, getting a quick look at /. or stackoverflow (and forwarding pages for later reading to my InstaPaper account), listening to music, making calls or videocalls. Smart phones do plenty of things well, but reading long blocks of text is not one of them.
There are also plenty of good ways around :hover - if you MUST have it, make the :hover state do something useful on a mobile browser. Is it a menu? Make the menu open on :hover if you're finding yourself on a mobile device. Is it a link that just gets an underline? Tag it with some class so that jQuery (or whathaveyou) just knows to go ahead and "click" the link. Watch out for some Android stock browsers though, they tossed out .click() on elements and you have to polyfill :( :hover doesn't have to be removed when you go mobile or responsive, but it should be accounted for in a way that doesn't make the user want to never come back.
That is the best website I've ever seen, and every designer at my job will see it. Bonus awesome for the use of the citation attribute in the blockquote - bam.
Chrome has begun to do more with UA-related stuff. Changing the UA now also implements "bugs" from other browsers. Example: IE7 I think had a weird problem with how I accessed a particular property, and Chrome reported it to me when I set the UA. Desktop at least auto-checks the dimensions for your "viewport," not sure if mobile does too - again, YMMV.
Mostly those assumptions have to with advertisements.
Bingo. I disable ads on desktop, but that feature is missing on mobile. Not only that, but I often find myself accidentally tapping an ad that hasn't loaded (why no width/height tags???).
At the verrrrry bottom is a "switch to full site" or something, but it only lasts so long, and oddly isn't tied to your account settings...
Oh, and let's not forget that many corporate machines There run Windows policies that force IE 8 into 7 compatibility mode...
It's such a tough nut though - without a competent design and dev team behind a responsive effort, you can very easily wind up in a bad situation. And where do you draw the line? The Flex model works great on browsers that support it, but then you have to hack around those that don't? So you don't use it, but what do you use? Whether it's a "shame.css" file (also know as "ie7.css ie8.css ..."), a separate "mobile" site, or some wacky mix of UA detection and responsive, we're still hacking around things that should be fixed and out of the way. But then Big Client still runs IE FREAKING 8 IN THE COMPANY. In the FIELD. IN THEIR STORES. So, you make the damn thing work on IE8, and usually choke on it so much that you just pull out the icon fonts, backtrack on some HTML5 goodness, get special SASS plugins to convert your RGBA colors into PNGs...and client is happy. And then they open it in mobile and wonder why you never redesigned the separate mobile site - not like you were too busy cursing that they'd never caught up in 2013.
True story, from a "tech leader" no less.
Another problem with the sliding door, which should be even more obvious, is that the majority of consumers will simply not trust Manufacturer because Manufacturer can't "promise" a safe, non-hackable camera. Of course, no one can promise that, but the addition of "privacy cover" implies that there is likely someone out there who can and will use your camera without your permission. While this may be TRUE, the average consumer will certainly see it as a failing of ASUS/Apple/Samsung/etc and not a failing of the government to protect from this (instead of partake in it).
Not to mention that acid reflux can make a "score" higher, as well as too many carbohydrates. Glass of wine and a bunch of bread? Your BAC will read much higher than it might otherwise. Burp up something nasty? It'll read higher. Often times, you're asked to hold your breath and then blow REALLY HARD. One story I heard, they asked the person pulled to blow harder and harder until finally they said "That it's! That's what we're looking for!" So, he blew hard enough to cause the reader to read high enough to arrest.
I like this, except for the Android part. The myriad offerings on the Play store that would fool a parent are too many - not trying to start a war (or participate in it), but for the older folks who just don't "get" computing, I'd suggest forking the extra bit for an Apple tablet of some sort.
1) Any photos, bookmarks, etc that you want to keep: have a copy of it on a backup DVD
LOL I'm sorry but I'm really laughing out loud over here. Backup to DVD? I've written (and rewritten) the instructions to copy a CD for my mom many many times over the last several years. I don't know what it is about "Open - Click Copy CD - Wait" that makes things difficult...asking her, or my dad, to burn backup DVDs is just asking for it.
For shame. I wish I had mod points to mod this down. Shameful, /.. Normally racism is is pushed down but I guess no one said "nigger"