Since first running into TrackingPoint at CES 2013, we’ve kept tabs on the Austin-based company and its Linux-powered rifles, which it collectively calls "Precision Guided Firearms," or PGFs. We got to spend a few hours on the range with TrackingPoint’s first round of near-production bolt-action weapons last March, when my photojournalist buddy Steven Michael nailed a target at 1,008 yards—about 0.91 kilometers—on his first try, in spite of never having fired a rifle before.
But big, heavy, bolt-action rifles were only the beginning, with the underlying idea being that the company would scale its weapons both up and also down in size. And, last month, we day tripped back out to the Best of the West range just outside of Austin in Liberty Hill to lay hands on TrackingPoint’s newest set of PGFs, the TP AR 556 and TP AR 762. Unlike the big XS-series long rifles we fired last time, these newest PGFs are semiautomatic carbines—the type of weapon that the media usually (and incorrectly) refers to as "assault rifles."
This screenshot shows the QML/JS KDevelop plugin working as usual, highlighting declarations and uses, finding types, and displaying nice tool-tips. The code-completion also works even if it is not visible on the screenshot. What is interesting is the look of KDevelop: do you see the flatter theme? The colors that are a bit different than usual? This difference is appearance comes from the fact that this is not the usual KDevelop, this is KDevelop 5, based on Qt5 and on the shiny new KDE Frameworks 5.
It’s been exactly ten years since the launch of OpenStreetMap, the largest crowd-sourced mapping project on the Internet. The project was founded by Steve Coast when he was still a student.
It took a few years for the idea of OpenStreetMap to catch on, but today, it’s among the most heavily used sources for mapping data and the project is still going strong, with new and improved data added to it every day by volunteers as well as businesses that see the value in an open project like this.
To celebrate the project’s birthday, I sat down with Coast, who now works at Telenav, to talk about OpenStreetMap’s earliest days and its future. Here is a (lightly edited) transcript of the interview.
Just about two weeks ago, I got a Flame and have decided to use it as my primary phone and put away my Nexus 5. I’m running Firefox OS Nightly on it and so far have not run into any bugs so critical that I have needed to go back to Android.
I have however found some bugs and have some thoughts on things that need improvement to make the Firefox OS experience even better.
Android Circuit: An Early Moto 360 Review, The Chinese Rulers Of Android, And The Galaxy Tab Nook 4 Is ComingSubmitted by Rianne Schestowitz on Sunday 10th of August 2014 07:09:52 PM Filed under
Taking a look back at the week in news across the Android world, this week’s Android Circuit highlights a number of stories, including the first impressions and images of the Moto 360 smartwatch, the Meta M1 breaks cover, more news on a potential antitrust investigation of Android in the EU, China’s dominance of the Chinese Android market, Samsung and Apple drop some patent cases, and the Tab 4 Nook has a launch date.
Android Circuit is here to remind you of a few of the very many things that have happened around Android over the last seven days.
I few weeks ago I announced I was joining Linaro. I work there as Director of Core Development Group. I moved from Prague to Cambridge (the original), that is, from continental to oceanic climate. From dry, cold in winter and hot in summer to wet, soft in summer and above zero most of the winter. In theory an improvement, you might think. Well, depending on much it rains. I will tell you better in spring.
A few days ago The Mukt published and interview where I explained a little what is Linaro and what do I do as Core Development Director.
Being merged into the mainline kernel code-base for Linux 3.17 was the big DRM feature pull that included enhancements to the Intel and AMD Radeon graphics drivers (among the other smaller DRM/KMS drivers), but missing from action was the open-source NVIDIA driver. The Nouveau driver changes were delayed by some last-minute bug-hunting but now a separate pull request was issued to land the Nouveau driver updates for Linux 3.17.
We're now around the half-way point of the Linux 3.17 merge window with at least another week expected before the 3.17-rc1 release depending upon Linus Torvalds' travel around LinuxCon and the Kernel Summit in Chicago. While we're only half-way through the merge window, there's already enough new functionality to warrant a summary article for those that haven't been keeping up with all the Linux 3.17 coverage.
With Linux comes choice. Along with that choice, comes debate. Which desktop is the best? Which offers the most user-friendly experience? The questions are not only never-ending, but date back over a decade where the “war” between KDE, GNOME, and every other desktop was given voice. I would, contend, however, that there is a desktop for every kind of user to be found within the Linux landscape. To that end, I want to take some of the most popular desktops and match them to end users.
Wednesday is the day we've been waiting for when hopefully the lid will be lifted on OpenGL 5 by the Khronos Group.
On 13 August is when the Khronos Group will be announced the next-generation OpenGL at SIGGRAPH in Vancouver. Given that it's going to be going head-to-head with DirectX 12, AMD's Mantle API, and to some extent Apple's Metal, we (and others) assume this is most likely where they're going to make the jump to OpenGL 5.0 rather than OpenGL 4.5 for the next-gen functionality.
Also note that only Python 3 is supported. It doesn't make sense to support legacy Python versions like 2, especially when developers need to do a port anyway from PyKDE4 to PyKDE5.
Another important reason is that it costs more time and effort to support more configurations. It is no secret to anyone who has followed PyKDE4 development and support just a little bit, will have noticed that my time for KDE is very limited. The situation isn't likely to improve, in fact in a couple months it should get worse if all goes to plan. I see that some people have stepped in to fill the void and fix some of the build and installation problems they have encountered (hi Luca!). This is great and I encourage people to get involved where possible. The hardest part is getting a working dev environment set up, deep C++ knowledge isn't really needed (I certainly don't have deep C++ knowledge!).