Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
Get HideMyAss! VPN, PC Mag's Top 10 VPNs of 2016 for 55% off for a Limited Time ×

Comment But... why? (Score 2) 430

One of the hallmark problems of design-by-committee is that they extend languages for the sake of doing fun things, not because people need it.

While everyone needs containers (like vector/hashmap), nobody needs a simple graphics library. There is practically no hardware out there that doesn't have some sort of hardware accelerated graphics and simple operations just make no sense there.

So, my question really is why they are doing this? I'm betting the answer is not one where they have actual usecases in mind.

Submission + - Intel's Knights Landing - a 72 core, 3 teraflop beast (

asliarun writes: David Kanter of Realworldtech recently posted his take on Intel's upcoming Knights Landing chip. The technical specs are startling massive and shows Intel's new found focus on throughput processing (and possibly graphics). 72 Silvermont cores with beefy FP and vector units, mesh fabric with tile based architecture, DDR4 support with a 384bit memory controller, QPI connectivity instead of PCIe, and 16GB on-package eDRAM (yes, 16GB!). All this should ensure throughput of 3 teraflops/s double precision. Many of the architectural elements would also be the same as Intel's future CPU chips — so this is also a peek into Intel's vision of the future. Will Intel use this as a platform to compete with nVidia and AMD/ATI graphics? Or will this be another Larrabee? Or just an exotic HPC product like Knights Corner?

Submission + - Microsoft, We Need to Talk About Visual Studio (

jones_supa writes: 'I really hope Microsoft employees (from the Visual Studio team) or the management read this post', begins Matias at Yosoygames blog. He is assured that latest revisions of Visual Studio are failing to satisfy the video game industry. One by one: horrible compilation performance, excruciatingly slow IntelliSense, unusually high RAM consumption, no native 64-bit version, high latency text editor input. Matias's benchmarks show that GCC is almost 3x faster than MSVS2013 C++ compiler (Clang is fastest), even when not using precompiled headers. IntelliSense's 'Go to Definition' is too slow, he continues. 'Often it takes noticeable time (between 750ms and 2 seconds probably) while VC 2008 was nearly instantaneous (except for a few cases).' The VS2013 IDE uses 3 times more RAM than Visual C++ 2008, and its compiler uses 2 to 3 times as much RAM. 64-bit version would also be needed, as some components of the toolchain run out of their 3GB memory space. As the icing of the cake, the editor input occasionally lags behind. For his purposes, it's hard to switch, as Visual Studio is the default and standard compiler for the Windows platform. As a workaround, Matias uses the aging Visual Studio 2008 and makes some positive remarks about Qt Creator.

Comment Re:Not just (Score 2) 179

The Qt part left a bit of a bad taste in my mouth, so I did some research of my own.

The first thing to notice is that a normal Qt application has no attack surface, there is no need for any part of the application to use elevated privileges. So what was his point? The presenter went with the assumption that some applications can be started as a normal user but get root rights by being installed as suid-root.

I don't understand why he would attack that idea. Having a GUI app started by any user run as root is not good security policy. Having your app run as root and linking it to multi-megabytes of library that is not hardened for such a case is just plain silly.

The answer of the Qt guys makes a lot of sense, the library is not meant to be run with different privileges as the user that started it. He should have gotten the point when the Qt security experts made the point clear with the plugins. If I can start an app as root from my normal user, and I can specify which styling-plugin to run, I essentially can tell it to run my code. As root.

So, I'm fully satisfied with the answer that Qt is not wrong, it doesn't have an attack surface unless the app using it is doing something stupid.

His security report is akin to blaming the vim authors that it is a security concern if you install it as suid-root. Its blaming the wrong person for introducing the attack surface.

ps. his quoted Qt code never occurs in any of the Qt5 codebase as far as I can find.

Comment Re:Symbian is (not) a goner (Score 1) 423

The GP was a bit vague, I understood it differently from how you read it. From my point of view, it makes a lot of sense.

The point that I think makes a lot of sense it that Symbian is not dead because you can run Qt based applications on it. You can develop on your Windows/Linux box and deploy it on your Symbian device. You can also deploy the same app on a Meego device, if you want. Without rewriting it.

Saying an OS is dead in my mind means its not available anymore, or that there are no applications for it. The first is obviously false as there are still 100million devices with it with more coming from various vendors. The applications can be written using Qt (google for "Qt Quick") and as such the applications market is probably just going to get bigger, not smaller.

Symbian is not a goner just yet. But many will agree its going to be replaced eventually with things like Meego. Naturally, this is why developers should choose Qt as they can develop for both the current and the next generation at the same time.

Comment Re:Labelling. (Score 1) 423

most distributions dropped KDE 3 support.

They did, and they did that because their users screamed at them. Which is entirely silly to listen to, I mean, would your car dealer remove the doors if you really loudly asked for it? Hmm, maybe they would.

I'm just saying that the distros did this *against* the wishes of KDE.

Comment Re:KDE 4.0 once again... (Score 1, Insightful) 165

Huh. Sorry, that's complete bullshit. While everyone knows that a .0 version may have bugs, it's also expected that a .0 version *will* be ready for prime time. If it's not, it should have an alpha or beta moniker.

I appreciate your opinion, and I even understand your point of view. Do you understand that releasing software may be something that is not just for your benefit? There are integrators, developers and others that need this release. And you should try it, you might even like it. Depending on how many features you actually use from an office suite.

Comment Re:KDE 4.0 once again... (Score 1) 165

Not sure where you got the impression that a .0 version is a final "please use this for your mission critical work". That has never been true and nobody every claimed it to be the case. Remember Windows 3.0 ? I don't. I do remember 3.1

Anyway; this is a *platform* release. Distro's, integrators and developers can now get this and use it. There will be users that like it, but TFA is being brutally honest that its not for end users.
I don't understand why you seem to be upset.


Submission + - KOffice 2.0.0 platform release is out

zander writes: "Today the KOffice team released their platform release with version 2.0.0; the name seems to point to both the fact that this is the first in a series and meant for integrators and developers more than for end users but the name platform is also a reference that this version runs on all major operating systems.

KOffice 2 is a much more flexible application suite than KOffice 1 ever was. The integration between the components is much stronger, with the revolutionary Flake Shapes as the central concept. For instance, KWord can embed bitmap graphics, Krita can embed vector graphics and Karbon can embed charts. This flexibility does not only give KOffice unprecedented integration, but also allows new applications to be created very easily. Such applications can e.g. target special user groups like kids or certain professions."

Comment Re:Qt Looks Like Shit (Score 1) 230

Its not so much that many must find Oxygen pretty, its much more that people that don't are not whining about it like the original poster did. They just use another style that looks better to them. Frankly; saying that a theming toolkit looks ugly is kind of silly. Especially since there is a native Windows look&feel as well as a native MacOSX l&f which, well, look native.

Slashdot Top Deals

It is impossible to enjoy idling thoroughly unless one has plenty of work to do. -- Jerome Klapka Jerome