You can upload flv's but youtube will re-encode them if the average bitrate is higher than a certain, very low threshold (something like 350kbps total) and you won't get a high quality encode.
Funny you mention that. I've installed Hardy on my father's new HP laptop just a week ago. The installation was fast. The installer finished without a hitch and everything worked out of the box with shiny compiz effects on top. It took me 3 hours to install the OS, install three 3rd party apps (skype, codecs, flash) and do a backup.
Bringing the original Vista installation to a usable state took the rest of the day. That included:
removing a f***-load of trial crapware
hunting down 3rd party apps (firefox, AV, FoxIT, 7-zip, etc)
hunting down HP updates because "HP Update" has been broken for months now
defragment & backup
If I had not done all that my father would get lost in there in a second. Hopefully he'll need Vista only as a fall-back because he plans to use that laptop for docs, web, mail and an occasional chess game.
Trying to block legitimate speech because it's not approved by the "authorities" would fall so flat on its face in court it'd be an embarrasment to any politician that passed it.
The difference between a dude who stands in his hot tub to work on the filter pump and the guy who spills soda on the reactor control panel [wikipedia.org], is that hot tub boy only kills himself and at most a few of his friends.
We know how to design a reactor which can fail safely and deactivates without constant and precise supervision. We also know how to safely handle coolant leaks. I agree that the major problem is in the wetware but we could potentially minimize it's job to the design and the hitting the off button. Once we have the design the off button should be a no-brainier.
I'd say that 411 fatal electrocutions by 110V AC in a whole year can be considered freak accidents. Especially when you consider the total number of users.
I agree that nothing is safe in life. When I write "safe" I thought "safe enough not to explode in my face when running with or without supervision". Small difference, I know.
If his rant is indicative about the future direction of science, we're all doomed. I wouldn't be too concerned about that. I'd be more concerned about the reason behind this quote:
"All models are wrong, and increasingly you can succeed without them." I sincerely hope there's some merit behind it. If there isn't any then Google would have to revise this guy's job position.
Pragmas were meant to be OS and compiler specific. If your OS or compiler doesn't provide a standard then it's the language is not at fault.
* Macros after-thought and not type safe
Macros weren't meant to be type safe. You should use templates if you need type safety.
* No 24, and 32 bit (unicode) chars
What about std::wstring and cwchar?
* Still has float / double crap, instead of being properly deprecated and f32, f64, f80 used instead
* Still has short / long crap, instead of being properly deprecated, and i8, i16, i32, i64, i128, u8, etc...
It can be made safe with enough money in R&D. Just compare the old reactor designs with the recent ones, like breeders. The argument that nuclear energy can't be called safe reminds me of the old electricity argument with AC vs DC. It CAN be made safe, it just needs engineering.
That voluntary opt-in functionality is already on every piece of hardware.
It's called an off button. If a big sign doesn't convince you to use it, then I don't see why would you use an automatic feature which you have to explicitly turn on.
A feature like that is an additional attack vector and it is bound to be misused. A working implementation could also give funny ideas to the police, like adding a 3rd mandatory mode saying "fuck your settings, turn off NOW".
I'm curious if Via will pull that one off with the same idle power drain as the Atom. If yes, then couldn't you actually get better battery life with the Nano? If it will perform better per-watt than the Atom, then you could get stuff done faster and save on the power drawn by other components.
You could prevent that with shaping based on volume.
A token bucket tied to a given link would ensure a high burst speed for any protocol and deteriorate after a short period of constant heavy traffic. You'd have to properly set it up so a user won't be able to get more speed than he's allowed to, with short bursts.
Don't bother clicking through for the videos. All three only show how they dropped the laptops on the floor. Whooping three shots per laptop: falling on the floor on the spine, base from 29 inches and in a bag from 60 inches. Nothing interesting.
Just go with the print version if you want to read it.
Unstable like hell. Do not use it if you're not planning to help with development. It brought down the whole X server when, for example, the swfdec plug-in crashed (which was often). Basically it felt like any crashing application could crash X along with it. I tried it on a laptop with a X3100.
You should consider a fork as damage control. If this project wasn't Open Source then the whole project could be in danger of withering away. If this project would not be OS then all effort put into could be lost. This saves the work that would be spent on duplicating rewriting the project in case a developer goes completely nuts.
In this case, a fork isn't so damaging. Pidgin uses a separate library as a back-end so both forks have an easy way to maintain full compatibility.
Either way, you need to accept the harsh reality that any ISP that offers broadband service (1+ Mbps) without transfer caps will go out of business within 2 years. You should tell that to almost every European ISP currently in business or they'll be in really serious trouble!
Slashdot Mirror
I dunno, it just seems we're a bit heavy on the science experiments and little to slow on the Yankee Ingenuity these days.
That's coming from a guy with a homepage on "WaveBlankets".
You can upload flv's but youtube will re-encode them if the average bitrate is higher than a certain, very low threshold (something like 350kbps total) and you won't get a high quality encode.
Apology accepted.
PS. I didn't know anyone else here was happy with it.
PPS. No, really I am.
Funny you mention that. I've installed Hardy on my father's new HP laptop just a week ago. The installation was fast. The installer finished without a hitch and everything worked out of the box with shiny compiz effects on top. It took me 3 hours to install the OS, install three 3rd party apps (skype, codecs, flash) and do a backup.
Bringing the original Vista installation to a usable state took the rest of the day. That included:
If I had not done all that my father would get lost in there in a second. Hopefully he'll need Vista only as a fall-back because he plans to use that laptop for docs, web, mail and an occasional chess game.
Trying to block legitimate speech because it's not approved by the "authorities" would fall so flat on its face in court it'd be an embarrasment to any politician that passed it.
You must be new here. I'd like to welcome you to the wonderful world of the Digital Millenium Copyright Act.
A 32" LCD may need more power than a 32" CRT but my 19" LCD monitor runs on 30W compared to 120W my old 19" CRT had used (TCO'99).
It's not that simple(tm).
The difference between a dude who stands in his hot tub to work on the filter pump and the guy who spills soda on the reactor control panel [wikipedia.org], is that hot tub boy only kills himself and at most a few of his friends.
We know how to design a reactor which can fail safely and deactivates without constant and precise supervision. We also know how to safely handle coolant leaks. I agree that the major problem is in the wetware but we could potentially minimize it's job to the design and the hitting the off button. Once we have the design the off button should be a no-brainier.I'd say that 411 fatal electrocutions by 110V AC in a whole year can be considered freak accidents. Especially when you consider the total number of users. I agree that nothing is safe in life. When I write "safe" I thought "safe enough not to explode in my face when running with or without supervision". Small difference, I know.
* No standardized pragmas
Pragmas were meant to be OS and compiler specific. If your OS or compiler doesn't provide a standard then it's the language is not at fault.* Macros after-thought and not type safe
Macros weren't meant to be type safe. You should use templates if you need type safety.* No 24, and 32 bit (unicode) chars
What about std::wstring and cwchar?* Still has float / double crap, instead of being properly deprecated and f32, f64, f80 used instead * Still has short / long crap, instead of being properly deprecated, and i8, i16, i32, i64, i128, u8, etc...
Use cstdint and cfloat* No distinction between typedefs and aliases * Inconsistent left-to-right declarations
I don't have much experience with those in C++ so maybe someone else should elaborate. Could you provide examples where these two would be a problem?* Compilers still limited to ASCII source
This is true but hard-coding unicode strings is considered a no-no.* No binary constant prefix (even octal has one?!)
This is true.* No standard way to assign NaN, +Inf, -Inf to floating point constants at compile time
Standard since C99.It can be made safe with enough money in R&D. Just compare the old reactor designs with the recent ones, like breeders. The argument that nuclear energy can't be called safe reminds me of the old electricity argument with AC vs DC. It CAN be made safe, it just needs engineering.
One can't be proved or disproved but the other can be (eventually).
That voluntary opt-in functionality is already on every piece of hardware.
It's called an off button.
If a big sign doesn't convince you to use it, then I don't see why would you use an automatic feature which you have to explicitly turn on.
A feature like that is an additional attack vector and it is bound to be misused. A working implementation could also give funny ideas to the police, like adding a 3rd mandatory mode saying "fuck your settings, turn off NOW".
"Nature doesn't like singularities" That's a quote I often heard form my physics professor. We're physically bound to hit a wall.
I'm curious if Via will pull that one off with the same idle power drain as the Atom. If yes, then couldn't you actually get better battery life with the Nano? If it will perform better per-watt than the Atom, then you could get stuff done faster and save on the power drawn by other components.
You could prevent that with shaping based on volume. A token bucket tied to a given link would ensure a high burst speed for any protocol and deteriorate after a short period of constant heavy traffic. You'd have to properly set it up so a user won't be able to get more speed than he's allowed to, with short bursts.
I would too but the last time I did it, my BSD died.
Don't bother clicking through for the videos. All three only show how they dropped the laptops on the floor. Whooping three shots per laptop: falling on the floor on the spine, base from 29 inches and in a bag from 60 inches. Nothing interesting. Just go with the print version if you want to read it.
Unstable like hell. Do not use it if you're not planning to help with development. It brought down the whole X server when, for example, the swfdec plug-in crashed (which was often). Basically it felt like any crashing application could crash X along with it. I tried it on a laptop with a X3100.
By the visible hand of government regulation.
My first impression of the headline was: "Why the hell would Microsoft do a Fedora conference?"
You should consider a fork as damage control. If this project wasn't Open Source then the whole project could be in danger of withering away. If this project would not be OS then all effort put into could be lost. This saves the work that would be spent on duplicating rewriting the project in case a developer goes completely nuts. In this case, a fork isn't so damaging. Pidgin uses a separate library as a back-end so both forks have an easy way to maintain full compatibility.
What about energy density?
Or let them add an opt-in compatibility flag which will tell GCC to clear that flag manually and be done with it.