Linked by Thom Holwerda on Wed 22nd Feb 2012 15:24 UTC, submitted by Ajeet
On my mark... Get set... Start not caring! Adobe has announced it plans to discontinue the stand-alone Flash Player for Linux, instead focussing all its effort on the version available through the Pepper API - which, besides Chrome, no one else is going to support.
Permalink for comment 508240
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
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:
2007-06-22
Since version 10.1 Flash uses CoreAnimation and a bunch of other OS X frameworks to implement part of its functionality like drawing. How does NPAPI (pepper or not) plays into it exactly? Citation for your claims please. Here's an article from a Flash engineer and it doesn't say anything about NPAPI (pepper or not): http://www.kaourantin.net/2010/02/core-animation.html
https://wiki.mozilla.org/index.php?title=NPAPI:Pepper&oldid=275848
Where exactly? This the last version before the page was blanked.
Actually, I would since Apple's WebKit engineers flat out refused to accept the necessary changes to support Dart just a few weeks ago. Google wanted to make WebKit language-agnostic and allow multiple concurrent scripting engines (currently only JavaScript is supported and only one engine at a time). Part of the reason for the refusal was the added code complexity and therefore maintenance burden. Another part was that Dart is not a web standard and WebKit's own mission statement says "[...] using standards-based technologies such as HTML, CSS, JavaScript and the DOM" and they want to avoid adding to the current fragmentation.
I'm not saying that Dart in WebKit might not happen at one later point if the decision of the engineers is overridden by higher management but currently the magic eight ball says "Unlikely".
Windows Vista/7 users had to endure a very non-native looking interface until just recently (Firefox 4) so it's not like OS X is the only one suffering from that, especially if you consider that most developers are apparently using Mac or Linux. It simply boils down to lack of manpower, especially since large parts of Firefox codebase is currently being rewritten.
Which is unfortunate and very short-sighted since Mozilla is the only organization which believably fights for an open web. Whatever organizational failures Mozilla displayed in the past (and there were far too many), at least they got their priorities straight.
I can't really argue against this. Even if taking into account that most of the remaining leaks are caused by extensions, Mozilla was far too lenient for far too long towards misbehaving extensions despite using them as a unique selling point for Firefox. Classical case of wanting to keep their cake and eat it. At long last they are tightening their rules for extensions to be hosted by Mozilla and started developing tools to help developers with finding leaks.
Edited 2012-02-23 14:03 UTC