Linked by Thom Holwerda on Thu 15th Dec 2011 16:56 UTC
As it turns out, Google's idea of silently and automatically updating web browsers for security's sake is actually a pretty darn good idea - Chrome is pretty much always up-to-date. Microsoft agrees with this, and has announced it's going to automatically update Internet Explorer on Windows XP, Vista and 7.
Thread beginning with comment 500309
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Woah! - updateds already off
by jabbotts on Fri 16th Dec 2011 13:45
in reply to "RE[4]: Woah! - updateds already off"
Member since:2007-09-06
RE[6]: Woah! - updateds already off
by lucas_maximus on Fri 16th Dec 2011 14:13
in reply to "RE[5]: Woah! - updateds already off"
Member since:2009-08-18
It's the web developer's fault that IE6/7 can't render standards compliant HTML that renders properly in every other browser? Wow.. just... wow.
They can render standard compliant markup absolutely fine in the vast majority of cases. Yes you need a valid DOCTYPE declaration ...
http://www.quirksmode.org/css/quirksmode.html
A lot of times, complaints are made by web developers that would know a inline element from a block element.
IE (including 8) is stricter than other browsers, most web browsers let you get away with all sorts of things that are wrong.
But it doesn't seems to matter what someone says ... people have been told to believe "IE does everything wrong, and Firefox does it right".
RE[5]: Woah! - updateds already off
by muszek on Fri 16th Dec 2011 14:37
in reply to "RE[4]: Woah! - updateds already off"
Member since:2007-04-25
RE[6]: Woah! - updateds already off
by lucas_maximus on Mon 19th Dec 2011 15:28
in reply to "RE[5]: Woah! - updateds already off"
Member since:2009-08-18
The car analogy ... really?
Most of the rendering bugs are pretty easy to code around and are well documented by now.
All browsers have bugs, IE7 is 5 or 6 years old now? If I compared it to Firefox 1.5 or 2, I know that both these browsers have problems with things like inline-block just as IE7 does.
I'd rather know what those bugs are, then have something like Firefox that has new and interesting problems every 6 weeks.
Edited 2011-12-19 15:31 UTC
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
"This is my NeXTstation Turbo Color booting the Mac System 7.1 Operating System using a hardware add-on called 'Daydream'. The Daydream has a Mac ROM and a few custom ICs in it and hooked up to the NeXTs DSP port. Turns your NeXT into a full fledged 68k powered Mac." So cool.
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
"The NetBSD Project is pleased to announce NetBSD 6.1, the first feature update of the NetBSD 6 release branch. It represents a selected subset of fixes deemed important for security or stability reasons, as well as new features and enhancements. Please note that all fixes in the prior security/bugfix updates (NetBSD 6.0.1 and 6.0.2) are also in 6.1."
Linked by Thom Holwerda on 05/18/13 21:06 UTC
"At the end of a week in which Electronic Arts confirmed it wasn't developing a thing for the Wii U, one of the software engineers in EA Sports' Canada studio, in a series of since-deleted tweets, disparaged the console as 'crap' and suggested Nintendo should give up on hardware altogether. 'The Wii U is crap. Less powerful than an Xbox 360. Poor online/store. Weird tablet', tweeted Bob Summerwill, listed as a senior software engineer at EA Canada, in a reply to a tweet posting a link about EA's no-Wii U news. 'Nintendo are walking dead at this point'." The Wii U is turning into the 21st century's Virtual Boy.
Linked by Thom Holwerda on 05/18/13 7:37 UTC
"In NixOS, the entire operating system - the kernel, applications, system packages, configuration files, and so on - is built by the Nix package manager from a description in a purely functional build language. The fact that it's purely functional essentially means that building a new configuration cannot overwrite previous configurations. Most of the other features follow from this." Interesting approach. A Linux distribution, sure, but with some very refreshing ideas about system configuration.
Linked by fran on 05/18/13 1:38 UTC
Appfour added, among other features, C/C++ support to its new version of AIDE. From Android-IDE, "Now you can write parts of your app or your whole app in C/C++ on your device. AIDE supports the Standard Android NDK toolchain (GCC 4.6 + Bionic, STL, ...). No changes are necessary if you want to build an app developed on a PC with Eclipse. C/C++ development is fully integrated: Build errors appear in the error list and files can easily be navigated to with Go to file. The editor supports C/C++ syntax highlighting."
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Ars nails it: "The answer is that Google did announce what amounts to a fairly substantial Android update yesterday. They simply did it without adding to the update fragmentation problems that continue to plague the platform. By focusing on these changes and not the apparently-waiting-in-the-wings update to the core software, Google is showing us one of the ways in which it's trying to fix the update problem."
Linked by MOS6510 on 05/17/13 22:22 UTC
"It is good for programmers to understand what goes on inside a processor. The CPU is at the heart of our career. What goes on inside the CPU? How long does it take for one instruction to run? What does it mean when a new CPU has a 12-stage pipeline, or 18-stage pipeline, or even a 'deep' 31-stage pipeline? Programs generally treat the CPU as a black box. Instructions go into the box in order, instructions come out of the box in order, and some processing magic happens inside. As a programmer, it is useful to learn what happens inside the box. This is especially true if you will be working on tasks like program optimization. If you don't know what is going on inside the CPU, how can you optimize for it? This article is about what goes on inside the x86 processor's deep pipeline."
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
"It was the only moment I heard regret slip into Otellini's voice during the several hours of conversations I had with him. 'The lesson I took away from that was, while we like to speak with data around here, so many times in my career I've ended up making decisions with my gut, and I should have followed my gut,' he said. 'My gut told me to say yes.'" The world would've been a much different place - Apple would have been less dependant on Samsung for its chips, which probably would've meant less money for Samsung to develop its Galaxy business.
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Glass is getting some love at Google I/O as well. New applications have been released - Facebook, Twitter, Evernote, Elle, Tumblr, and CNN. Perhaps more interesting: the newly announced Google Glass Developer Kit will allow offline applications and direct hardware access - great for hacking and expanding Glass' potential. This kit will really allow hackers to put Glass through its paces.
Linked by Thom Holwerda on 05/16/13 17:04 UTC
"But Beck and Merrill decided that simply banning toxic players wasn't an acceptable solution for their game. Riot Games began experimenting with more constructive modes of player management through a formal player behavior initiative that actually conducts controlled experiments on its player base to see what helps reduce bad behavior. The results of that initiative have been shared at a lecture at the Massachusetts Institute of Technology and on panels at the Penny Arcade Expo East and the Game Developers Conference." Absolutely fascinating stuff. I'm a League of Legends player, and to be honest, the community isn't nearly as bad as some make it out to be. I'm happy Riot games has the guts to employ science to address the issue.More News »
Sponsored Links
Member since:
2009-08-18
Most problems with IE (especially past 7) is a result of sloppy web developers, some who don't understand why the browser has problems rendering pages when they put block elements within a inline element.
IE7 can be a PITA with absolute and relative positioning if you aren't careful, but static positioning it is largely fine.