I want alpha, I want CMYK or whatever colourspace. I want exif or whatever metadata.
But more than anything I want it to support both lossy and lossless algorithms so we can finally see an end to people using jpg for everything, including hard contrast logos.
It would just take a checkbox on the save dialog with some wording to encourage lossless where appropriate.
Given that warning letters without significant supporting evidence can be considered damaging to the reputation of an individual, it would seem appropriate that if you are on the receiving end of a warning letter, you should sue the sender for libel.
If this happens enough, then it might results in changes to one of the DEA laws or libel laws, so it would be a win win type deal.
Nobody asked for the "awesome bar" or whatever the hell that is. If it improves productivity then fine
The address bar does auto complete from a number of sources such as history and bookmarks with a fall through to search if it isn't found. So yes they called it "awesome" making a gross error of naming judgement, but of course it improves productivity over the alternative of having four different searches.
We/did/ ask for this feature - at least implicitly - we just didn't need the dumbass name.
The goal for both Meego and Android should be to get their kernel customisations back into mainline.
They benefit everyone then, provided they are not customisations that only benefit the android stack.
As for using Dalvik.. doubtful. QT is the strategy and it goes beyond Meego, and is native.
"Stealing" is an odd term to use for open source. Sharing it is the point.
We don't need to worry too much about Nokia's involvement in MeeGo either - you can take your hat off. It is an open source linux distribution, and the more people / businesses that get involved, the lesser is Nokia's influence. My hope that this goes the way of other distributions, where corporations contribute but the distribution has its own life. Once MeeGo has reached a usability milestone we'll see xda port it to everything they can get their hands on, then demand will increase for handset manufacturers will be pressured in to providing open source (or at least blobs) drivers for their hardware. Then the tables will be reversed, asking not what handset/OS shall I buy, but what handset shall I buy, and which OS shall I install on it.
Android isn't anything like MeeGo or a linux distribution. It has its own stack - the commonality ends at the kernel (if they have even merged the custom kernel changes back in to mainline yet) The kernel is only a part of the equation - significant but a part.
If they want their CPU platform to only be thought of as useful for running Android java apps, then ok that is a possible decision. If I was AMD I would prefer something that has a bit more potential - which is what Meego provides. I am not surprised at their decision to want a proper gnu/linux stack, hence my post.
MeeGo is a linux distribution optimised for low power mobile devices.
No one would be surprised if the title read "AMD Joins Mobile Linux OS efforts" which is what is going on. It is an open source project, and the only real contender for mobile at the moment.
Of course AMD want to play in the mobile space and to do this they need an OS. Their alternative is to roll their own or form another equivalent partnership like MeeGo that aims to achieve the exact same thing.
Gentoo has a "java" use flag for openoffice - and presumably if this is turned off, openoffice will be built without java. And presumably libreoffice would be built without java if the same use flag was disabled. And presumably this removes any java, rather than what is already identified as optional.
So presumably java isn't a dependency unless you use a binary that has java enabled as one.
It is only a saving if there is no intention of doing FTTH ever. If there is, then just get on with it. It is far cheaper to do FTTH(now) than FTTN(now)+FTTH(later).
Does hadopi specify which copyright holders can request IPs from ISPs?
Because it seems to me that most people in France would have some sort of copyright on something they have produced, so irrespective of media files being torrented or whatever, they could all put requests through hadopi?
What about international copyright holders - can they put requests through hadopi?
Don't forget 150000 IP addresses a day won't canvas the entire population in a year or so unless you assume static IPs for everyone.
If your nation is so on the verge of rioting that some commentary on a website is all that is required as a trigger, further removal of civil liberties may not be the best course of action.
The point of the process is to find solutions that overcome the limitations of tabs while NOT BREAKING THE FUNCTIONALITY provided by tabs.
I do appreciate that/. commentary is for people to exhibit change resistance as often as possible, but sometimes I just don't find it as interesting as other times.
But by all means carry on everyone. I am sure it is just a phase I am going through.
Wikipedia will catch up with what we all actually mean by netbook, and it obviously isn't the definition linked.
And "moving parts" is only a preference or opinion - as long as portability and longevity are respected. It doesn't matter if the storage media spins as long as the portability and longevity aren't compromised to do it.
Clearly portability is limited by shock proof media, but not constrained by it.
Slashdot Mirror
I want a new image format.
I want alpha, I want CMYK or whatever colourspace. I want exif or whatever metadata.
But more than anything I want it to support both lossy and lossless algorithms so we can finally see an end to people using jpg for everything, including hard contrast logos.
It would just take a checkbox on the save dialog with some wording to encourage lossless where appropriate.
driving side choice, and coke formula.
The coke formula thing is my favorite. The rest of the world went - ok whatever, a new taste coke. They shrugged and moved on.
In the US, there was outrage, and the subsequent re-introduction of the old formula as coke classic.
Units, date formats, coke, etc will never change because changing stuff is clearly anti-american.
Britain also horrendous libel laws.
Given that warning letters without significant supporting evidence can be considered damaging to the reputation of an individual, it would seem appropriate that if you are on the receiving end of a warning letter, you should sue the sender for libel.
If this happens enough, then it might results in changes to one of the DEA laws or libel laws, so it would be a win win type deal.
Nobody asked for the "awesome bar" or whatever the hell that is. If it improves productivity then fine
The address bar does auto complete from a number of sources such as history and bookmarks with a fall through to search if it isn't found. So yes they called it "awesome" making a gross error of naming judgement, but of course it improves productivity over the alternative of having four different searches.
We /did/ ask for this feature - at least implicitly - we just didn't need the dumbass name.
It does confirm to standards, just not very many of them: http://people.mozilla.com/~prouget/ie9/
Of course this is a mozilla blog, but facts are checkable
The goal for both Meego and Android should be to get their kernel customisations back into mainline.
They benefit everyone then, provided they are not customisations that only benefit the android stack.
As for using Dalvik.. doubtful. QT is the strategy and it goes beyond Meego, and is native.
"Stealing" is an odd term to use for open source. Sharing it is the point.
We don't need to worry too much about Nokia's involvement in MeeGo either - you can take your hat off. It is an open source linux distribution, and the more people / businesses that get involved, the lesser is Nokia's influence. My hope that this goes the way of other distributions, where corporations contribute but the distribution has its own life. Once MeeGo has reached a usability milestone we'll see xda port it to everything they can get their hands on, then demand will increase for handset manufacturers will be pressured in to providing open source (or at least blobs) drivers for their hardware. Then the tables will be reversed, asking not what handset/OS shall I buy, but what handset shall I buy, and which OS shall I install on it.
And it will go the way of the PC
Android isn't anything like MeeGo or a linux distribution. It has its own stack - the commonality ends at the kernel (if they have even merged the custom kernel changes back in to mainline yet) The kernel is only a part of the equation - significant but a part.
If they want their CPU platform to only be thought of as useful for running Android java apps, then ok that is a possible decision. If I was AMD I would prefer something that has a bit more potential - which is what Meego provides. I am not surprised at their decision to want a proper gnu/linux stack, hence my post.
Yes, their upcoming "APU" series has low power variants.
MeeGo is a linux distribution optimised for low power mobile devices.
No one would be surprised if the title read "AMD Joins Mobile Linux OS efforts" which is what is going on. It is an open source project, and the only real contender for mobile at the moment.
Of course AMD want to play in the mobile space and to do this they need an OS. Their alternative is to roll their own or form another equivalent partnership like MeeGo that aims to achieve the exact same thing.
This is the only sensible move they could make.
Gentoo has a "java" use flag for openoffice - and presumably if this is turned off, openoffice will be built without java. And presumably libreoffice would be built without java if the same use flag was disabled. And presumably this removes any java, rather than what is already identified as optional.
So presumably java isn't a dependency unless you use a binary that has java enabled as one.
Presumably.
It is only a saving if there is no intention of doing FTTH ever. If there is, then just get on with it. It is far cheaper to do FTTH(now) than FTTN(now)+FTTH(later).
In reality, we might get something in products in 10 years.
And in general, predictions of "10 years" means anything from 10 years to infinity years. Much like fusion power is 10 years away, and always will be.
Does hadopi specify which copyright holders can request IPs from ISPs?
Because it seems to me that most people in France would have some sort of copyright on something they have produced, so irrespective of media files being torrented or whatever, they could all put requests through hadopi?
What about international copyright holders - can they put requests through hadopi?
Don't forget 150000 IP addresses a day won't canvas the entire population in a year or so unless you assume static IPs for everyone.
Never wear a jetpack and a backpack at the same time.
I have been using KDE 4 from 4.1 and it has been decreasingly sucky and increasingly stable since 4.2. And a far better experience than 3.5 imo.
So, if you found that you didn't like 4.4, 4.5 isn't worth your time.
If your nation is so on the verge of rioting that some commentary on a website is all that is required as a trigger, further removal of civil liberties may not be the best course of action.
Er no. I'd say that the standard should define which image formats should be supported *at a minimum*.
And which fonts.
And which video formats.
The point here is to try and get to a point where you publish something to the web and have some sort of hope that people will see it as intended.
"The remainder of this message cannot be displayed because your browser doesn't support video format spliggle, please try another browser"
So, what do you make an artificial atom out of?
Because:
That
Goes
Without
Saying
The point of the process is to find solutions that overcome the limitations of tabs while NOT BREAKING THE FUNCTIONALITY provided by tabs.
I do appreciate that /. commentary is for people to exhibit change resistance as often as possible, but sometimes I just don't find it as interesting as other times.
But by all means carry on everyone. I am sure it is just a phase I am going through.
In summary there are two short-sighted points of view in this commentary:
1) "I don't use many tabs, so there is no need to change tabs"
2) "I have hundreds of tabs open and don't have a problem, so there is no need to change tabs"
Guess what, no one gives a crap if tabs are fine for you. The reason why this is being explored is for those people who tabs do *not* work for.
I know, it is obvious now I have explained it, but don't feel embarrassed or anything.
Just enough to fund the committee that will take four years to discuss whether an Agency is necessary.
What is this feet and pounds crap? Are you working this out on a cave wall somewhere?
Please come outside.
Australia has always had caps and my conclusion is that this promotes rather than reduces sharing.
If you have a 10GB plan, and use 5GB toward the end of your month, you have 5GB unused but paid for.
Ensuring this is used up is "getting your moneys worth". So what are you going to download?
Seriously - Psion? Welcome to this century.
Wikipedia will catch up with what we all actually mean by netbook, and it obviously isn't the definition linked.
And "moving parts" is only a preference or opinion - as long as portability and longevity are respected. It doesn't matter if the storage media spins as long as the portability and longevity aren't compromised to do it.
Clearly portability is limited by shock proof media, but not constrained by it.
is feature-creep killing this new market?
The key definers for a "netbook" are weight, size and stamina - battery life. And of course some sort of mobile "net" capability.
As long as these are respected, then bring the features on - doesn't that go without saying?