Odds on there being any open source drivers for this SoC? ImgTec is known for being hostile towards open source in general and delivering shit-grade binary-blob drivers that perform poorly and are rife with compatibility issues.
You're doing a wonderful job of talking up New Hampshire as a place to run when you're tired of being sane.
AN ACT adding an exemption from immunization for conscientious beliefs.
So instead of having to admit that their opt-out is based on irrationality, they can opt out "just because." Brilliant. Do you have a lot of anti-vaxxers up there?
Exclusion During Outbreak of Disease. During an outbreak of a communicable disease for which immunization is required under RSA 141-C:20-a, [children] students exempted under RSA 141-C:20-c shall not attend the school or child care agency threatened by the communicable disease.
But muh liberties! How can I be free if I'm not free to spread disease!
Utilization of the kernel continues to grow, but a great many devices are utilizing Android and even more are locked down. And few of those uses result in improvements to the kernel, Android, or anything outside that tiny bubble.
Because none of what you said is correct. EME is a secondary plug-in API that focuses on video DRM black boxes. The browsers won't be decrypting anything. Even an open source browser could implement the interfaces, only problem is the DCE modules probably won't be available on any true Linux systems - only on shit blessed by Google or some other DRM-happy company.
We could ask them to keep that shit out of the browser and build their own client. But Microsoft, Apple, and Google are all too happy to cater to abusive media conglomerates.
And EME is Encrypted *MEDIA* Extensions. It works on the HTML media tag, for encrypting audio and video, not HTML. It has nothing to do with HTML, nothing to do with copying and pasting or saving text or documents.
For now. The demand will inevitably be made for it to cover everything.
there is a huge amount of demand in the real world from users and content providers.
Yup, those same content providers who buy congressmen and manipulate our laws entirely in their favor and abuse the DMCA with no repercussions.
If it's going to happen anyhow, shouldn't it at least be standardized?
It isn't standardized. It still requires proprietary, arbitrary blobs and works on all of two OSes.
Sailfish is not a "vastly different OS" like Android is. It is very much a standard Linux distribution. This likely will be as well, since that's much easier to maintain than a disaster like Android.
I'm going to give Valve the benefit of the doubt, but not you.
Cooperating system
Steam is not a one-way content broadcast channel, it’s a collaborative many-to-many entertainment platform, in which each participant is a multiplier of the experience for everyone else. With SteamOS, “openness” means that the hardware industry can iterate in the living room at a much faster pace than they’ve been able to. Content creators can connect directly to their customers. Users can alter or replace any part of the software or hardware they want. Gamers are empowered to join in the creation of the games they love. SteamOS will continue to evolve, but will remain an environment designed to foster these kinds of innovation.
So obviously you're doing the kneejerk thing instead of reading things. If the platform were going to be locked down, the bolded bit above would be impossible.
And you've set your entire argument up in a biased fashion too.
GPL: the positive feedback loop is damped by the unattractiveness of the license to many potential contributors, particularly GPLv3. Fewer participants equals less resources spent developing the project.
A claim which is possible but largely lacking in evidence.
BSD: the claimed negative feedback loop almost doesn't exist.
Additionally unfounded. Given that BSD sources can be downloaded, modified, and their changes never see the light of day the loss of information is virtually guaranteed. Not to say it doesn't happen with the GPL, but it's actually a legal risk to allow it to happen.
Because the reason they're using open source in the first place is to reduce their own workload, and maintaining a private fork of a public codebase turns out to be a lot of work.
And yet there are plenty of vendors who would do just that if it suited their purposes. Your argument for staying upstream is entirely logical, but then, many corporations are not run in a logical fashion.
Basically the only time this actually happens in the BSD-licensed world is when someone decides
Would you ever know?
GPL zealots
Nothing worse than responding to a reasonable post with an invective.
In reality, productive sharing is always an outcome of shared interests between all the parties involved, not the license.)
But only so far as it suits their business interests. The GPLv3 was created to further advance its goals which have always been to ensure the software is free and that the recipient of the software is never encumbered by whomever they receive it from.
Having a single point of failure disrupt something as essential as Linux kernel development doesn't instill confidence in the business world.
No it doesn't. The business world that utilizes Linux is never running on the bleeding edge, and silly non-events like this don't shake anyone's confidence.
Real end users "use" the system and care more about usability than access to the source code.
Ah, so you get to define who a "Real end user" is I take it?
Most of them would not know how to write any code let alone audit it.
Which is beside the point, really.
The end user's "freedom" is actually limited when nerds argue over licensing terms and are unable to include some software because of it.
Nonsense. You just don't like that the argument doesn't go 100% your way and others disagree.
The GPL is actually a form of slavery that you agree to enter into in order be able to modify the code.
I see we're back to hyperbole. No, you can modify the code all you see fit. You simply can't redistribute without complying with the GPL. Which isn't slavery by a long shot.
The price that the GPL imposes is too high a price.
For you maybe, but you're already acting unreasonably.
So does a mildly successful OSS project called Android
That Android is OSS is almost completely immaterial because even if it wasn't, the handset vendors would get the sources regardless.
maybe Canonical is tired of trying to get everyone on board and just decided "We'll go our own way and when you finally figure out it was the right one feel free to catch up".
And maybe they just think they know better than everyone else. But I suspect that Mir would not have happened if not for Wayland.
Android did the first true fork of the Linux kernel that I've heard of and probably ruffled some feathers there but they got it out the door, shipping and working
And the net result is that the kernel is a constantly moving target that causes a large part of the delay in getting new versions of Android on older handsets. I'd hardly argue that Android of all things is an example of why doing things in an open way is bad, given how rapidly most Android devices are left to wither on the vine. I'd hate for desktops and laptops to be left to wither in a similar fashion.
Actually it's telling, mostly about Canonical's outward attitude. They created all of these solutions, but none of them were widely adopted. Few people use Launchpad, bzr, Upstart, etc. Perhaps it's related to Canonical's seeming desire to develop internally and release when they see fit, rather than develop in the open and take community input?
And Wayland is out there. It was already being tested on devices when Mir was announced. Of course, no one knew Mir was coming because Canonical likes to work behind closed doors, the larger Linux world be damned.
Why not? If no one uses it anymore, it's dead code that simply increases complexity. And once you start removing those dead bits, you can't call it X11 anymore. So you fix it to better fit the most common use cases and the easiest way to do that now is by rewriting it. Particularly when that code was written against a 30 year old standard that has been receiving workarounds to account for new hardware for years.
Slashdot Mirror
Odds on there being any open source drivers for this SoC? ImgTec is known for being hostile towards open source in general and delivering shit-grade binary-blob drivers that perform poorly and are rife with compatibility issues.
You're doing a wonderful job of talking up New Hampshire as a place to run when you're tired of being sane.
So instead of having to admit that their opt-out is based on irrationality, they can opt out "just because." Brilliant. Do you have a lot of anti-vaxxers up there?
But muh liberties! How can I be free if I'm not free to spread disease!
Utilization of the kernel continues to grow, but a great many devices are utilizing Android and even more are locked down. And few of those uses result in improvements to the kernel, Android, or anything outside that tiny bubble.
I know, doesn't that suck? It's also impossible to change! They're forever stuck operating in that mode and no one knows why...
No joke! Too bad you can't, you know, dynamically swap between interfaces or something. But for some reason it's impossible...
Because none of what you said is correct. EME is a secondary plug-in API that focuses on video DRM black boxes. The browsers won't be decrypting anything. Even an open source browser could implement the interfaces, only problem is the DCE modules probably won't be available on any true Linux systems - only on shit blessed by Google or some other DRM-happy company.
So the USSR/CCP? Where it's not atheism that is the problem but the state ideology?
None of the stack is open. You're still interfacing with a plug-in, only with an all-new and untested API.
We could ask them to keep that shit out of the browser and build their own client. But Microsoft, Apple, and Google are all too happy to cater to abusive media conglomerates.
For now. The demand will inevitably be made for it to cover everything.
Yup, those same content providers who buy congressmen and manipulate our laws entirely in their favor and abuse the DMCA with no repercussions.
It isn't standardized. It still requires proprietary, arbitrary blobs and works on all of two OSes.
Because what we really need is anarchy, right? No way that could end badly.
Wayland is not GNOME-centric. Why do people go around saying stupid shit?
That doesn't make it not a disaster. That just makes it common.
Sailfish is not a "vastly different OS" like Android is. It is very much a standard Linux distribution. This likely will be as well, since that's much easier to maintain than a disaster like Android.
I'm going to give Valve the benefit of the doubt, but not you.
So obviously you're doing the kneejerk thing instead of reading things. If the platform were going to be locked down, the bolded bit above would be impossible.
Given the stated support for remote streaming of media, you might not need XBMC. And there's no word on the base platform, yet.
And you've set your entire argument up in a biased fashion too.
A claim which is possible but largely lacking in evidence.
Additionally unfounded. Given that BSD sources can be downloaded, modified, and their changes never see the light of day the loss of information is virtually guaranteed. Not to say it doesn't happen with the GPL, but it's actually a legal risk to allow it to happen.
And yet there are plenty of vendors who would do just that if it suited their purposes. Your argument for staying upstream is entirely logical, but then, many corporations are not run in a logical fashion.
Would you ever know?
Nothing worse than responding to a reasonable post with an invective.
But only so far as it suits their business interests. The GPLv3 was created to further advance its goals which have always been to ensure the software is free and that the recipient of the software is never encumbered by whomever they receive it from.
An example that is mostly immaterial given that the biggest driver of Android adoption has been the fact that Google has been behind the effort.
X is mostly well tested very mature tech and it seems to work fine, and provide MORE not less capability than Wayland.
X11/Xorg is very well tested but largely misses the point on current platforms, if it's not outright causing problems and forcing workarounds.
Amusingly, the 3rd party firmware on my router has more in common with desktop Linux than any 3rd party Android firmware.
Yes, but not a good one. Eric Cantor and Mitch McConell have yet to do anything useful or intelligent.
No it doesn't. The business world that utilizes Linux is never running on the bleeding edge, and silly non-events like this don't shake anyone's confidence.
Ah, so you get to define who a "Real end user" is I take it?
Which is beside the point, really.
Nonsense. You just don't like that the argument doesn't go 100% your way and others disagree.
I see we're back to hyperbole. No, you can modify the code all you see fit. You simply can't redistribute without complying with the GPL. Which isn't slavery by a long shot.
For you maybe, but you're already acting unreasonably.
That Android is OSS is almost completely immaterial because even if it wasn't, the handset vendors would get the sources regardless.
And maybe they just think they know better than everyone else. But I suspect that Mir would not have happened if not for Wayland.
And the net result is that the kernel is a constantly moving target that causes a large part of the delay in getting new versions of Android on older handsets. I'd hardly argue that Android of all things is an example of why doing things in an open way is bad, given how rapidly most Android devices are left to wither on the vine. I'd hate for desktops and laptops to be left to wither in a similar fashion.
Actually it's telling, mostly about Canonical's outward attitude. They created all of these solutions, but none of them were widely adopted. Few people use Launchpad, bzr, Upstart, etc. Perhaps it's related to Canonical's seeming desire to develop internally and release when they see fit, rather than develop in the open and take community input?
And Wayland is out there. It was already being tested on devices when Mir was announced. Of course, no one knew Mir was coming because Canonical likes to work behind closed doors, the larger Linux world be damned.
Why not? If no one uses it anymore, it's dead code that simply increases complexity. And once you start removing those dead bits, you can't call it X11 anymore. So you fix it to better fit the most common use cases and the easiest way to do that now is by rewriting it. Particularly when that code was written against a 30 year old standard that has been receiving workarounds to account for new hardware for years.