chw42

QUOTE (Buehrle>Wood @ Jun 30, 2014 -> 04:49 PM) Neuer incredible game. Saving Germany single handily right now He's one of the few goalies that will go way out of the box to disrupt plays. That's a lot of confidence.

Germany has ramped up the pace, but are still goal-less. Looks like we're going extra-time on this one.

QUOTE (Y2HH @ Jun 29, 2014 -> 07:41 PM) This highlights exactly what I've been saying... Google maps on iOS (original release) was better than what was present on Android, but don't take that for me saying I love it...I don't, it's still just ok design. I'd prefer apple maps UI with googles data set if I had a choice. People don't use Google maps on iOS because of its design, as it's often slow, clunky, and busy (yes, even today), they use it for its accuracy and extremely populated data set. Which goes back to my point from the start...even Googles updated "holo" designs aren't great, they're simply better than the absolute crap that preceded it. So, I again say, I welcome the changes coming in android l. I don't really understand why you can't just accept that, as far as I'm concerned -- and in my opinion -- up until now, googles UI design is meh. It's fine that you have that opinion, I just believe that it's absolutely wrong.

QUOTE (bmags @ Jun 29, 2014 -> 06:47 PM) I feel like we've been told Costa Rica will be outmatched every game before they win. I'm not betting against them anymore (figuratively) Greece is not a good team. Had Duarte not gotten that stupid second yellow, they would have won easily.

QUOTE (zenryan @ Jun 29, 2014 -> 06:00 PM) CR was dead out there and Greece still couldnt do anything for 30 minutes. I dont see how Costa Rica will be able to survive the Dutch. CR isnt going to have much left. Navas had an incredible game. Greece had two golden chances to score that he blocked, albeit somewhat inadvertently.

QUOTE (Y2HH @ Jun 29, 2014 -> 07:52 AM) To be more clear, in this conversation when I talk about "framework", I mean the basic design language and parameters in how applications and UI's are built, for example, in Android L, they're calling it "Material Design", so in this case I wasn't talking about ART or Dalvik, which are both runtimes. I *never* said Android 1.x to 4.x was similar *performance* wise, I said Google went through a number of revamps and project butters to make Android "run better", not to mention SOC design is much better these days which alone would make it run better. Specifically, I was talking about the framework itself, which was still largely the same in the way apps were designed, the clunky/boring square shapes, borders, the drab color schemes, etc. I'll reference that before 4.4, ALL of Google's apps on iOS were superior to their own apps on Android, INCLUDING the first release of Google Maps on iOS that made Android's look like complete crap. The whole look and feel of Android, INCLUDING the current 4.4, was and is just "blah"...was it better than 1.x and 2.x? Yes. But it was still using Windows 3.x, which while still better than DOS...it it was still lacking. The good news is, I think Google took this seriously enough to rework it's ENTIRE design philosophy in Android L, so now they can stop slapping brighter lipstick on that same old pig and move in a better direction with a better looking model. Since I'm not yet out of cliches or unrelated references to OS's and how they look, Google spent years trying to make Android 1.x-4.x look like Kate Upton by slapping makeup on some average looking girl...who would never look like Kate Upton no matter how much makeup and airbrushing they used... You do realize that Google apps on iOS also used Holo design right...? This was especially evident before iOS 7. Maps was updated first on iOS because Apple Maps replaced the old Maps app, Google gave it priority. Android got the updated version a few months later and it looked more or less the same. You're literally bashing something that you liked on iOS.

QUOTE (BigHurt3515 @ Jun 29, 2014 -> 12:17 AM) My bold prediction is Wade and Melo come to Chicago. Rose-FA PG Wade-Butler Melo-McDermott Gibson-Mirotic Noah-FA C Finals here we come No thanks on D-Wade.

QUOTE (lostfan @ Jun 28, 2014 -> 10:21 PM) @blasondamadrid: R.Madrid (1). Mirotic jugó el jueves su último partido con la camiseta del Madrid. Operación NBA en marcha. La próxima semana viaja a EEUU. non-fluent Spanish speaker translation: Mirotic has played his last game for Madrid, and he heads to the USA next week. @blasondamadrid: Real Madrid (2). Como contó Fernando Ruiz (@fernan_ruiz), Mirotic tenía tomada la decisión hace semanas. El club recibirá 2,5 millones. Mirotic had decided this weeks ago. Madrid gets 2.5 million. There are more tweets, but the gist of it is that Mirotic is ready to go to the NBA right now, and he will come pretty much no matter what the Bulls are paying. Wow nice.

QUOTE (Y2HH @ Jun 28, 2014 -> 07:31 AM) Of course, people need to recognize that a lot of this is just opinion, but it's always been my opinion that something was missing from Android, it felt clunky even after it's repeated revamps and "project butters". As said, some of this stems from the over customization OEMs do with Android, but a lot of it comes from the framework Android is built upon, which is why a lot of Google's own applications on iOS were superior to their own Android counterparts. Of course, Google has done a lot of work on UI framework as of late, and it shows ... but I disagree with anyone that thinks their UI's were ever good, it's just an opinion, but I believe they were fair to poor designs, and I think the proof exists in that Google obviously agreed with me, hence their entire rework of the framework Android is based on. And it's not just limited to Android, their web UI's (aside from Chrome) also tend to be clunky, poorly laid out designs with what I call "option bombardment", just look at gmail on the web for reference (and again, Google KNOWS gmail's web UI is terrible). As I said before, it wasn't that Android's UI was terrible, it worked, but it was akin to using Windows 3.x ... it was better than DOS, but it still sucked. And replacing a UI just so it looks different isn't what I'm talking about, either. I don't think changing how a UI looks does anything, it's just slapping a fresh coat of lipstick on a pig (which is what Android was doing from v1.0 to 4.4), as the underlying framework was largely the same. Starting with Android L, however, the framework is changing along with the look, which is an example of GOOD UI replacement...not just change for the sake of change. The framework you're speaking of, ART, has been available since Android 4.4, which was released more than half a year ago. And that has almost nothing to do with UI. It has a lot more to do with UX. I think you're just throwing around the word "terrible" out there for no apparent reason. I'm not sure how the Gmail UI is terrible or how Holo UI is terrible. Just because Google thinks they can improve their interface doesn't mean they thought it was terrible. I also think you've never actually used Android if you think Android 1.0 and Android 4.4 are similar performance-wise. Most of what you said pretty much confirms that you haven't had a ton of experience using Android (understandable, since you're an Apple user).

QUOTE (Y2HH @ Jun 27, 2014 -> 08:20 PM) Not WAS, IS. And Google knows it, hence their major redesign of something that was just redesigned less than 2 years ago. It was 3 years ago, almost 4 if you take into account that Holo was created for Android 3.0. I feel like 3 years is more than appropriate for a re-design.

QUOTE (Y2HH @ Jun 27, 2014 -> 01:12 PM) I said they were part of the issue, but Google wasn't much better themselves. Google has always been pretty notoriously terrible at UI design. Google WAS poor at UI design. That hasn't been the case for like the last 2-3 years. Android used to look like absolute crap. There was a time when HTC Sense looked infinitely better than the stock Android skin. Then Matias Duarte came from Palm and re-designed the entire OS with 4.0. It wasn't perfect, but it was a huge improvement that rivaled iOS. I'd say that until iOS 7 came out, iOS looked outdated compared to Android 4.0+ with its skeuomorphic design since it came out in 2007 and didn't really change much until iOS 7 (6 years later). Design changes a lot in half a decade. I bet a lot of people thought Windows Vista looked nice when it came out in 07 after starring at the crayon drawing that was Windows XP. Not only did iOS get boring to look at, the design itself was old. Google does have issues centralizing its products and UI inconsistency does stem from that. However, pretty much every updated Google app followed the Holo design guidelines and put some small spins on it. After all, would you really want every app to look exactly the same? That'd be extremely boring. There was a lot of back and forth with where they should place the settings. Hamburger menu? Overflow button? I think they've finally moved over to putting settings in the hamburger menu, but now with Material design, I'm not sure what they're going to do. Google changes their mind a bit too much about UI design, but then again all you have to do is look at iOS and see what happens when you resist change for 5 years. The main issue with Android UI isn't that Google's design sucks, it's that app developers and OEMs s*** all over it by not following them. Apple will reject your app if it looks like you put it together in 5 minutes. Google doesn't care. I guess that's the problem with having a more or less open app store, but I'd rather keep it open than have Google reign supreme and watch over everything. The apps cobbled together in 5 minutes won't be downloaded and they won't be relevant. The bigger issue is that bigger developers like Twitter and Facebook don't care to follow the design guidelines. It took Facebook 3 years to put together an app that even resembled Holo design and I get a strong feeling that was because iOS 7 went with the flatter look. Should Google force these devs to follow their guidelines? Maybe they should or maybe they already do and it falls on deaf ears. Either way, I feel like Google's done a good job with design over the past 2-3 years, but since they're not enforcers of it (like Apple probably is), devs just don't bother to follow the guidelines.

QUOTE (Y2HH @ Jun 27, 2014 -> 12:26 PM) I did not particularly like later versions of Android despite being smoother/better than early versions. Android has always been lacking in uniformity and slickness, some of which was caused by 3rd parties such as Samsung or HTC re-skinning Android, and some of it was because Google was just all over the place on the design front, where programs often had settings in different locations, and it's overall feeling of lack of optimization. To be sure, there was nothing 'wrong' with later versions of Android, but to me, it was like using Windows. It worked, it did what it was supposed to do ... but it just wasn't very ... good, and if you wanted to make it good, it took a lot of customization and digging around. Ten years ago I would have been all over Android because of that ability to customize it into exactly what I wanted...I used to hack and tinker with everything, and it was great because it taught me the in's and out's of a device/operating system, and at that point in my life that was important to me. Even now I get the bug once in a while, but it fades quickly, and I just want whatever I'm using to work without hassle...and after a few days of making iOS or Android look unique, it gets old and I fall back to the, "Jesus, could you please just work when I try to do X, Y or Z, instead of me having to figure stuff out?" Android L, however, looks like it's approaching the uniform/optimized/fluid state I expect out of modern hardware/operating systems. So...you're saying Google's design guidelines were bad because third parties decided to ignore them and create terrible skins? I don't think that's a fair assessment.

QUOTE (Buehrle>Wood @ Jun 27, 2014 -> 11:46 AM) But the US made the knockout round as hosts. Only South Africa hasnt. Yeah I realized that and edited it. I was thinking of 98.

QUOTE (HickoryHuskers @ Jun 27, 2014 -> 10:56 AM) They were hosts in 2002 and every host gets to the knockout round. So yeah, there's been basically one WC ever where Asian teams have done much of anything. Except South Africa.

QUOTE (Y2HH @ Jun 26, 2014 -> 06:57 PM) Me either? I think Microsoft made a LOT of horrible decisions under Bamler, but purposefully trying to get people to stop using their products wasn't one of them. I believe Microsoft is in much better hands now. Aside from that, Android L *finally* looks like an OS I can take seriously, and no, I couldn't take previous versions seriously, as I personally believe they had horrendous UIs (and apparently Google agreed with me hence the change). Are you sure you're talking about Android 4.4 and not Android 2.3? Here's a comparison of what's visually different: http://www.androidbeat.com/2014/06/android...ual-comparison/ Android L does look nice. I tried out the preview yesterday. None of the Google Apps are updated yet, but the stock apps look decent. The animations a bit more fluid, which is nice. It's also using ART as the default runtime instead of Dalvik, which might be why.

QUOTE (HickoryHuskers @ Jun 27, 2014 -> 06:53 AM) If they're going to keep inviting Asia to the World Cup, they are going to need to give them a one man advantage for all 90 minutes every game. Maybe then they will do better than 0-9-3. That's what makes it even more remarkable that 3 CONCACAF teams advanced, since none of them got free points by being in a group with an Asian team. You can say that Mexico had a somewhat easy draw with Cameroon and Croatia, but they got a point off the hosts so they clearly earned their way through, and the US and Costa Rica survived absolutely loaded groups. Korea and Japan had success in past world cups. Both qualified for the knockout round in 2010 and 2002. They were just awful this time around.

QUOTE (zenryan @ Jun 26, 2014 -> 10:24 PM) is it a laser or a light from cameras? b/c that same green laser is at a lot of different games Pretty sure it was a fan with a green laser. http://www.theaustralian.com.au/sport/foot...d6322fa2e413342

QUOTE (Soxbadger @ Jun 26, 2014 -> 09:21 PM) So is randolph to cut the salary, or does that just further indicate McBuckets is being brought in to be Melo, not play with Melo. Probably the latter.

We got Anthony Randolph too.

QUOTE (Jake @ Jun 26, 2014 -> 09:12 PM) I'm not a huge fan of Shabazz, honestly. Seems like the typical undersized guard that goes off in college and is forgotten as a pro He's an undersized chucker.

s***, Napier's going to Miami.

Napier to Charlotte. Hopefully he's not getting traded to Miami. Napier will now play with Kemba. Cool.

QUOTE (bmags @ Jun 26, 2014 -> 08:57 PM) But is he white? Then he ben affleck. You white, then you Ben Affleck.

Don't know how to feel about McDermott. At least it gives them a bit more cap space.

Some asshole is pointing a laser at the Russian goalie...