Does that mean that if it's okay for other people to ignore proprietary copyright, then people can also freely ignore the GPL and make and distribute derivative works of GPL products without source code?
No, that's not what he said. Don't worry, others have deliberately misconstrued what he has said on the topic in the past. Also, he's talking about music which doesn't have the "proprietary" vs. "free" distinction (the only way to have proprietary music is to never, ever share it.)
I don't believe that Stallman said anything about the copyrights themselves. His point was, again, about the implied (false) moral weight behind declaring "sharing" as being wrong (something opposite to what we're taught as children.) He then proceeds to point out fairly common failings of the music industry as a whole and the laws surrounding copyright, and basically makes the point that there are systematic flaws in the way we compensate artists and that the status quo basically feeds the machine that tries to shove crap like SOPA/PIPA down our throats.
I wouldn't mind more Raspberry Pi articles if you could actually buy it and use it, but you can't.
You can. It's just backordered to hell and gone now.
By the time the next available shipment arrives and those that have pre-ordered it receive their Pi, there will be something better.
I ordered in March, my preorder arrived in June. So ~3 months, with delays. Of course, the delay might have increased significantly since due to demand.
I think we might find a way to put the "waste" to use long before we have to worry about such long-term data storage.
By and large we already have it. All the stuff that will require 10K years to "cool" is spent reactor fuel, which if the politicians would pull their heads out of their asses would stick in a breeder reactor and burn for more power, then take what comes out of there (weapons grade plutonium) and stick it in the center of a military base for the next century while they cut it up for probe RTGs that get launched into space.
I honestly can't think of what else they'd need to store for tens of thousands (or even millions) of years. Even Chernobyl will have cooled significantly in only a hundred years or so.
Your dystopian perspective is... not refreshing. Sorry. Might as well kill yourself now and get it over with.
What's the point of moving thousands of people around? For every person in one place, there is a another person in just like them in any place that you would send them to.
Because companies don't benefit from having to place duplicates of their staff, whatever the role, all over the place. They'll put people in specific regions to manage them, but chances are your core staff will be in a handful of locations if not fewer. And sometimes they need to go there.
Walk to any corner and there's a McDonalds, a Bank of America, a Chevron gas station, and a Starbucks. Travel a thousand miles in any direction and you're on a corner with a McDonalds, a Bank of America, a Chevron gas station, and a Starbucks. What's the point of travel?
It could happen at any time. The exemption was purely because of arguments made by the EFF. At some point the solicitor general could disagree and suddenly jailbreaking tools could be rendered illegal and punishable under the DMCA.
And believe me, they really, really want them to be illegal.
building what people want according to how they use their devices does not add up to a conspiracy to prevent them from creating unmanaged content.
It'd sure seem less conspiracy-like if the way they were building these things wasn't rife with DRM that can't be turned off. But the entire ARM-based mobile world is basically centered around non-optional, inflexible lock down.
And a subset of that is being shoved into the PC space. Who knows how many iterations it'll be until it's pushed fully.
Where are the higher level frameworks in QT? Perhaps they are in Mer, but I could find no reference for that, which indicates there's not much Mer there.
All of the mobile-specific stuff is going into Qt Mobility. Anything missing will undoubtedly need to be added, I suspect that the team in question is aware of that.
Mobile programming these days is a LOT more than just being able to draw or do simple animations or being able to hit SQLLite.
No shit. Do keep in mind that this is the same team that developed the N9, I'm pretty sure they're aware of what deficiencies exist in the available APIs.
That would imply I ever had any "empty implications", whatever the hell that means.
Your frequent "proclamations" or unsupported statements for or against things that, unless prompted, you never give reference to or back up. It's a very general thing that you have a habit of doing here on Slashdot.
Is that something like when you are not a mobile developer and you cast aspirations of those who are when they try to tell you how things really work?
No, I just find it highly annoying when people think others are supposed to just blindly believe what they say.
Yes, if they actually wanted to have meaning in the market instead of chasing their tails. Instead the prediction of their demise is sadly all too certain to make.
And jumping on board with a platform that is being shoveled out the door by HP, with no future development in sight, is a smart move to make? Who knows, they may adopt some of what's in webOS, maybe merge it into Qt. We don't have visibility into much more than what's been pointed out today. Odd that, given the sparse info, you're already making proclamations of their doom.
They could have folded some aspects of MeeGo into the underlying WebOS infrastructure, but Qt 5 is ANCIENT compared to modern mobile OS's. They will get nowhere with this little vanity project, which makes me sad indeed given the effort they will undoubtedly sink into it. I despise wasted potential.
Then go back to your iOS development and let everyone else try to ensure there are more options than just Apple/Google, and maybe enjoy a niche. Not everyone needs to take on the two beasts out of the gate or serve every possible customer, they just need to be profitable.
The N9's Harmattan is basically Maemo 6, only without GTK and the "Aegis" security system in place. It was "MeeGo-compatible" due to sharing a number of platform APIs and including Qt, but not MeeGo due to lacking some APIs MeeGo had as well as being DEB based and not RPM based.
there's just no way to get MeeGo up to speed compared to Android, iOS and WP7 at this point API wise
Since you're so familiar with the details, care explaining how? Some detail, if you would. I'm curious as to how Qt 5 and the rest of Mer (the MeeGo-type core Linux platform they're using) is deficient, API wise.
Or is this yet another empty implication?
They should have started with an OS that was not too far behind and also had a strong core following - WebOS.
So they should have gone with an OS they were totally unfamiliar with, rather than one they were familiar with... why?
They don't need to make a device targeted at Linux hackers. They can add those capabilities on whatever device they make. What they need to do is take the territory that Nokia lost when they abandoned Symbian, and deliver on support in ways that Android vendors fail utterly at. If they can do that, catering to us nerds is something they'll do anyway because they'll want that capability themselves.
I think they chose not to market it directly to the public for other reasons. It was rejected by the carriers as being too flimsy, but I haven't heard anything about that despite knowing a lot of people with N950s who use them on a daily basis in lieu of their N900s.
Moot point though. The problem there was the hinge. It was still thinner and larger.
The N900's only real stellar point is the slide mechanism for the keyboard. Mine's probably been opened and closed more than a thousand times in the last 2.5 years and it's still rock solid.
The rest could be readily re-done, possibly thinner and better (see the N950.)
No worries, I doubt there will be a product named MeeGo. In fact, it isn't even using MeeGo, but Mer, which spun off from MeeGo when it became obvious that Nokia was going to walk away and Intel was off to pursue other things.
Jolla will probably name it something else exclusive to them. All that matters is by going with Mer (or as they've been saying, MeeGo) you know one thing: Qt.
Really? Where are the sources? I know the limaproject is trying to implement one, but I have yet to see an open source driver that does anything more than bare-bones 2D support, let alone actual 3D.
Except it isn' 'Microsoft's secure-boot solution', it is the Trusted Computing Groups secure-boot solution. Microsoft is a 'promote'r of TCG, but so is AMD, Intel, Cisco, IBM, HP, Fujitsu, Juniper, Infineon, Wave, and Lenovo.
Microsoft has been a hard-driver behind ALL of this.
Move down into the 'Contributor' category and you add dozens more companies, including Red Hat, Accenture, AMI, Dell, Freescale, Toyota, Hitachi, General Dynamics, Sony, Seagate, Western Digital, etc.
And you'll find that promoters have way, way more say than most Contributors, once you get inside these groups.
Surely you don't think that all those companies are interested in Trusted Computing just because Microsoft is insisting on it, do you?
Generally they're all assholes when it comes to restricting users. Microsoft just happens to be an 800lb gorilla.
Secure boot is just one little link in the chain of Trusted Computing.
Indeed, a chain secured by a lock you won't have the key to.
It is the first test that FOSS is facing with regard to the upcoming changes in computing. There will be many more to follow. If FOSS wants to remain relevant in the coming age where owners demand tighter control over their data they are going to have to figure out how to adapt.
FOSS is explicitly being excluded in these situations. All of these "solutions" require some 3rd party to be trusted and for the entire platform to be geared to work AGAINST the user, who is treated like the enemy rather than the party to be protected.
Now, there is nothing that is incompatible with the ideas of 'open source' and the ideas of 'trusted computing'.
Of course not, but that would imply that 'trusted computing' put the user in a 'trusted position.' The vast majority of current applications do not. The user is completely untrusted and given a little sandbox to piddle around in.
There is absolutely no technical reason that Red Hat, or SuSe, or Ubuntu, can't provide a 100% FOSS solution that is trusted. The only thing that could hold them back is putting ideology first.
Or the fact that a FOSS solution that is trusted is pretty much 100% antithetical to the concept behind FOSS, especially when you've effectively TiVOized everything by locking it up and not giving the user the key.
Going about the approach of pushing hardware that doesn't exist doesn't get you anywhere, especially when a behemoth like Microsoft can snap their fingers and have all the OEMs stand at attention.
The proper way to pursue this would be through the courts, and leveraging Microsoft's history against them.
The problem, again, is not UEFI but secure boot. The two are not inextricably linked.
It doesn't seem much different than the DRM problem in that way.
You'll have an uphill battle. Apple is transparently convincing people that DRM is good.
chaining
Can't happen. If any point has a flaw then the key gets revoked. From the UEFI platform down to the kernel needs to be "trusted" to betray the user, and the kernel must be secured against local exploits that allow bypassing of the chain.
it appears that the FSF is feeling hurt because Ubuntu is switching to another open source bootloader that doesn't use the GPL.
No, they're concerned that Ubuntu is giving up a GPL bootloader because they're choosing to adopt Microsoft's secure-boot solution, which effectively puts all such systems under Microsoft's control and makes it infinitely harder for "unapproved" software to run on the systems (which, if Microsoft's attitude is any indication, would include virtually all Free Software.)
companies have the right to secure their computers.
So my computer belongs to Microsoft? Dell? Asus?
Perhaps you missed the bit where ALL systems with the Windows 8 logo were going to be forced into this locked state by default. It's not just a corporate security feature, it's being rammed down ALL of our throats.
And it's always been on the thin edge of the razor. Microsoft has readily yanked their chains by changing the file formats and protocols, keeping them perpetually behind in terms of compatibility.
As for Novell, compatibility providing a few years of bounty is meaningless when the source of that bounty turns around and uses their monopoly to effectively drive you from the market. All you've done is made them more powerful.
Perfect, isn't it? Leverage your monopoly in the desktop space to push the APIs you use on your tablets, and then reserve the tablet space for yourself!
Please. Can you even come up with a scenario that would mirror this?
I've heard nothing nearly as insane come out of any other party, let alone the democrats. The GOP, nationwide, currently has monopolies not just on crazy, but stupid as well.
Slashdot Mirror
No, that's not what he said. Don't worry, others have deliberately misconstrued what he has said on the topic in the past. Also, he's talking about music which doesn't have the "proprietary" vs. "free" distinction (the only way to have proprietary music is to never, ever share it.)
I don't believe that Stallman said anything about the copyrights themselves. His point was, again, about the implied (false) moral weight behind declaring "sharing" as being wrong (something opposite to what we're taught as children.) He then proceeds to point out fairly common failings of the music industry as a whole and the laws surrounding copyright, and basically makes the point that there are systematic flaws in the way we compensate artists and that the status quo basically feeds the machine that tries to shove crap like SOPA/PIPA down our throats.
You can. It's just backordered to hell and gone now.
I ordered in March, my preorder arrived in June. So ~3 months, with delays. Of course, the delay might have increased significantly since due to demand.
By and large we already have it. All the stuff that will require 10K years to "cool" is spent reactor fuel, which if the politicians would pull their heads out of their asses would stick in a breeder reactor and burn for more power, then take what comes out of there (weapons grade plutonium) and stick it in the center of a military base for the next century while they cut it up for probe RTGs that get launched into space.
I honestly can't think of what else they'd need to store for tens of thousands (or even millions) of years. Even Chernobyl will have cooled significantly in only a hundred years or so.
Your dystopian perspective is... not refreshing. Sorry. Might as well kill yourself now and get it over with.
Because companies don't benefit from having to place duplicates of their staff, whatever the role, all over the place. They'll put people in specific regions to manage them, but chances are your core staff will be in a handful of locations if not fewer. And sometimes they need to go there.
I take it you don't actually travel.
It could happen at any time. The exemption was purely because of arguments made by the EFF. At some point the solicitor general could disagree and suddenly jailbreaking tools could be rendered illegal and punishable under the DMCA.
And believe me, they really, really want them to be illegal.
It'd sure seem less conspiracy-like if the way they were building these things wasn't rife with DRM that can't be turned off. But the entire ARM-based mobile world is basically centered around non-optional, inflexible lock down.
And a subset of that is being shoved into the PC space. Who knows how many iterations it'll be until it's pushed fully.
All of the mobile-specific stuff is going into Qt Mobility. Anything missing will undoubtedly need to be added, I suspect that the team in question is aware of that.
No shit. Do keep in mind that this is the same team that developed the N9, I'm pretty sure they're aware of what deficiencies exist in the available APIs.
Your frequent "proclamations" or unsupported statements for or against things that, unless prompted, you never give reference to or back up. It's a very general thing that you have a habit of doing here on Slashdot.
No, I just find it highly annoying when people think others are supposed to just blindly believe what they say.
And jumping on board with a platform that is being shoveled out the door by HP, with no future development in sight, is a smart move to make? Who knows, they may adopt some of what's in webOS, maybe merge it into Qt. We don't have visibility into much more than what's been pointed out today. Odd that, given the sparse info, you're already making proclamations of their doom.
Then go back to your iOS development and let everyone else try to ensure there are more options than just Apple/Google, and maybe enjoy a niche. Not everyone needs to take on the two beasts out of the gate or serve every possible customer, they just need to be profitable.
The N9's Harmattan is basically Maemo 6, only without GTK and the "Aegis" security system in place. It was "MeeGo-compatible" due to sharing a number of platform APIs and including Qt, but not MeeGo due to lacking some APIs MeeGo had as well as being DEB based and not RPM based.
Since you're so familiar with the details, care explaining how? Some detail, if you would. I'm curious as to how Qt 5 and the rest of Mer (the MeeGo-type core Linux platform they're using) is deficient, API wise.
Or is this yet another empty implication?
So they should have gone with an OS they were totally unfamiliar with, rather than one they were familiar with... why?
They don't need to make a device targeted at Linux hackers. They can add those capabilities on whatever device they make. What they need to do is take the territory that Nokia lost when they abandoned Symbian, and deliver on support in ways that Android vendors fail utterly at. If they can do that, catering to us nerds is something they'll do anyway because they'll want that capability themselves.
I think they chose not to market it directly to the public for other reasons. It was rejected by the carriers as being too flimsy, but I haven't heard anything about that despite knowing a lot of people with N950s who use them on a daily basis in lieu of their N900s.
Moot point though. The problem there was the hinge. It was still thinner and larger.
There's only a few actual connections.
Intel: Moblin -> MeeGo -> (huge disconnect, much package shedding) -> Mer
Nokia: Maemo -> Harmattan
Samsung: Tizen
The N900's only real stellar point is the slide mechanism for the keyboard. Mine's probably been opened and closed more than a thousand times in the last 2.5 years and it's still rock solid.
The rest could be readily re-done, possibly thinner and better (see the N950.)
No worries, I doubt there will be a product named MeeGo. In fact, it isn't even using MeeGo, but Mer, which spun off from MeeGo when it became obvious that Nokia was going to walk away and Intel was off to pursue other things.
Jolla will probably name it something else exclusive to them. All that matters is by going with Mer (or as they've been saying, MeeGo) you know one thing: Qt.
Really? Where are the sources? I know the limaproject is trying to implement one, but I have yet to see an open source driver that does anything more than bare-bones 2D support, let alone actual 3D.
Microsoft has been a hard-driver behind ALL of this.
And you'll find that promoters have way, way more say than most Contributors, once you get inside these groups.
Generally they're all assholes when it comes to restricting users. Microsoft just happens to be an 800lb gorilla.
Indeed, a chain secured by a lock you won't have the key to.
FOSS is explicitly being excluded in these situations. All of these "solutions" require some 3rd party to be trusted and for the entire platform to be geared to work AGAINST the user, who is treated like the enemy rather than the party to be protected.
Of course not, but that would imply that 'trusted computing' put the user in a 'trusted position.' The vast majority of current applications do not. The user is completely untrusted and given a little sandbox to piddle around in.
Or the fact that a FOSS solution that is trusted is pretty much 100% antithetical to the concept behind FOSS, especially when you've effectively TiVOized everything by locking it up and not giving the user the key.
Going about the approach of pushing hardware that doesn't exist doesn't get you anywhere, especially when a behemoth like Microsoft can snap their fingers and have all the OEMs stand at attention.
The proper way to pursue this would be through the courts, and leveraging Microsoft's history against them.
The problem, again, is not UEFI but secure boot. The two are not inextricably linked.
You'll have an uphill battle. Apple is transparently convincing people that DRM is good.
Can't happen. If any point has a flaw then the key gets revoked. From the UEFI platform down to the kernel needs to be "trusted" to betray the user, and the kernel must be secured against local exploits that allow bypassing of the chain.
Yeah, they're only concerned that these corporations will leverage their power ("freedom") to deny you the same. They'll be free to ensure you aren't.
No, they're concerned that Ubuntu is giving up a GPL bootloader because they're choosing to adopt Microsoft's secure-boot solution, which effectively puts all such systems under Microsoft's control and makes it infinitely harder for "unapproved" software to run on the systems (which, if Microsoft's attitude is any indication, would include virtually all Free Software.)
So my computer belongs to Microsoft? Dell? Asus?
Perhaps you missed the bit where ALL systems with the Windows 8 logo were going to be forced into this locked state by default. It's not just a corporate security feature, it's being rammed down ALL of our throats.
And it's always been on the thin edge of the razor. Microsoft has readily yanked their chains by changing the file formats and protocols, keeping them perpetually behind in terms of compatibility.
As for Novell, compatibility providing a few years of bounty is meaningless when the source of that bounty turns around and uses their monopoly to effectively drive you from the market. All you've done is made them more powerful.
So eventually all of them?
None?
Nor is pushing hardware that doesn't exist.
Perfect, isn't it? Leverage your monopoly in the desktop space to push the APIs you use on your tablets, and then reserve the tablet space for yourself!
Only with the added burden of no software flexibility and way more DRM + lock down.
Please. Can you even come up with a scenario that would mirror this?
I've heard nothing nearly as insane come out of any other party, let alone the democrats. The GOP, nationwide, currently has monopolies not just on crazy, but stupid as well.