Linked by Eugenia Loli on Wed 23rd Jan 2008 22:07 UTC
With Linux on the desktop going from a slow crawl to verging on an explosion, many have toiled with the question: How do we make this happen faster? A well-known Austin-based Linux Advocate thinks he has the answer.
Permalink for comment 297644
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 fran on 05/18/13 1:38 UTC
Google 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.
Linked by Thom Holwerda on 05/16/13 13:17 UTC
"Android and iOS, the number one and number two ranked smartphone operating systems worldwide, combined for 92.3% of all smartphone shipments during the first quarter of 2013 as Windows Phone crept past BlackBerry for 3rd place. According to the International Data Corporation Worldwide Quarterly Mobile Phone Tracker, Android smartphone vendors and Apple shipped a total of 199.5 million units worldwide during 1Q13, up 59.1% from the 125.4 million units shipped during 1Q12." Windows Phone doubles from a few to twice few, iOS loser market share as its growth is slower than that of the overall market. BlackBerry continues slide into irrelevance.
Linked by Thom Holwerda on 05/16/13 12:06 UTC
"According to the latest research from our Wireless Smartphone Strategies service, global Android smartphone profits reached US$5 billion in total during the first quarter of 2013. Samsung dominated and captured an impressive 95 percent share of all Android smartphone profits." Wow.
Linked by Thom Holwerda on 05/15/13 23:03 UTC
"During its Keynote today, Google announced new features coming to its flagship search function - you know, that thing we all started using Google for. VP Amit Singhal spent some time discussing what Google's search functionality will eventually morph into. Google's strategy is summarized by three words: answer, converse, and anticipate. Singhal explained that many of the pieces of these upcoming changes can already be seen in products that Google has recently introduced - namely, Google Knowledge Graph and Google Now, with perhaps a splash of Google Glass, too." I hold on to my hat every time Google changes Search. It's such a vital product in my daily life.
Linked by Thom Holwerda on 05/15/13 21:46 UTC
"Wired has obtained a copy of a cease and desist letter sent by Google to Microsoft today, demanding Microsoft immediately remove the YouTube app from its Windows Phone Store and disable existing copies on consumers' devices by May 22. The YouTube app for Windows Phone - developed by Microsoft not Google - strips out ads and allows downloading, both violations of YouTube's terms of service." Incredibly petty. Just come up with a solution, you bunch of kids.More News »
Sponsored Links
Member since:
2005-11-02
To suggest that BSD code can be 'closed off' so that people can no longer access the source code is disingenious in the extreme. "
BSD code can be used as the basis of closed software, hiding changes, improvements, regressions and problems of all kinds. The closed software can then be pushed by its backers and succeed over the open software, for a variety of reasons including (possibly) that it might be better. This cannot (legally) happen with GPL'd software.
GPL'd software is good for mandating a future in which code-visible-and-editable is the norm. BSD code is nice, but it does not mandate this. Because it does not *force* code visibility it implicitly supports code hiding, even though it is itself open.
Suppose a company takes some BSD'd code and incorporates it into their product, makes sales, makes a profit, but does not contribute money or patches back to the original application. Society is harmed by a closed application existing, society is harmed by the company's customers choosing the closed application instead of the open application from which it was in whole or in part derived, and society is harmed by improvements not flowing to all users.
It is not sufficient that existing and future users of the BSD'd version continue to use it and be free. The code has been closed off to the detriment of society.
If said application had been GPL'd instead then the company would be faced with reimplementing the functionality in a probable inferior way, or they would be required to publish their changes. Even if they chose to roll their own society would still be served by its probable inferiority driving customers to options which *were* based on the GPL'd code.
This argument is always raised whenever the BSD license's drawbacks are discussed. Nothing can stop you from using the last free version the day after the fork, and nothing is likely to stop you at any time. That's not the point I was making and I think it is as disingenuous for you to suggest that it was as it is for me to suggest that BSD code can be closed off.
I know you do. I have this conversation often with my BSD-fan friends; we continue to fail to understand each other on this point. It's an ongoing problem. I run in to the same problem debating socialism vs. libertarianism for many of the same reasons, regardless of which side I choose.
We can argue all day about whether the greatest freedom for the greatest number will be achieved by limiting some freedoms today; I expect we wont agree. We can debate the fine semantic points concerning just who it is whose freedom is being abridged; I suspect we wont agree on that, either. I'd just as soon not start... people seem to like voting me down for saying things which offend their ideals.