10 years ago they had been saying 10 years already.
We seem to have come to the root of the problem. When they say, "at least 10 years" and establish a minimum bound, you hear "10 years" and take it is a maximum.
R&D people do not promise to turn new technologies into products inside of a fixed time period. And when the say "at least 10 years" they're establishing a precision of a decade. It isn't a prediction at all, but if you wanted to translate it into one it would be something like "10-30 years" not "within 10 years."
Graphene has a lot of strength in a sheet, but it is soft and floppy. A graphene bullet would just be a carbon bullet. A graphene-coated bullet would be similar to a teflon coated bullet, but not as good and a lot more expensive.
I think you're confusing "products" or "implementations" with "technologies." The only "technologies" that went quickly from discovery to a product were the bag clip and the slap-chop. Everything else took decades, you just didn't learn about it so you don't know about it. You hear the pre-release hype on the boob tube and then six months later you see the ad for the product. Z0MG they build stuffs so fast nowz!
10 years ago they were saying at least 10 years. Most of the big sexy breakthroughs have been in the last few years, and almost all of those are fairly fundamental and not at all close to being products. There are already high quality flexible display prototypes being shown at Japanese conventions. Right now I don't think anybody needs a flexible screen badly enough to pay the "prototype-adopter" prices. Give it a couple more years and they'll have something ready for "early" adopters.
After being forced to write papers in cursive as a child, you get to college... banned. Just straight out banned. You can hand print, or computer print.
Really? Wow. You do all your exams on computer? None of them are handwritten, not even the maths and physics exams?
Hand print or computer print. You've got some work to do before you worry about the exams! Hand print. The verb for hand printing is "print," too.
That is really the funniest part. After being forced to write papers in cursive as a child, you get to college... banned. Just straight out banned. You can hand print, or computer print.
The same thing would happen in a professional setting. If somebody submits a report in cursive, they can plan some time to rewrite it in print so everybody can read it.
I have buckets of pens and piles of notepads all over my desk and around my office.
I'll tell you though, I've never once grabbed a pad to jot a note and done it is cursive. Never once. I spent my early years suffering through the lessons; I could probably still write that way if I wanted. Writing quickly, it would be a total mess and impossible to read later. It made sense in a past where it was important to conserve ink and paper. When you're racing against your ink drying from exposure to air, you're better off not even lifting the quill. But by the time the ink was being manufactured into a pen, that time was past. Long before I was born!
Cursive is just an old alternate script, from an age where anything professional was hand lettered calligraphy. It is not useful as a backup skill for recording information on paper. That can be done with a pen and normal print script.
You haven't spent much time scribling on napkins. Cursive will tear the napkin and cause it to totally fall apart. You have to stick to print so when it tears it is in an isolated spot. Cursive, the napkin will be weakened continuously where you've written, and once a tear starts it keeps tearing - right through the writing!
As long as the kids are learning to print by hand, they will be fine. Cursive is now a specialized skill for caligraphers.
He talks right in that email about making it a "dependency" but about the need for support on non-linux platforms. That just clarifies that systemd doesn't want gnome to actually depend on systemd, just to have it is a build dependency and to have the features still work if it isn't there.
Now, gee, why is it that you dug out the reference, but didn't bother pointing out that it acquits systemd's author? He clearly is against gnome actually requiring systemd in the sense that people are accusing.
And yeah, any developer should realize what a PITA traditional locale support is on *nix. A solution for that is needed. Fix the problems that systemd is going solve for gnome, and it won't need to get the solutions from systemd.
Also note that it doesn't mean you'll need systemd installed to use gnome. You'll only need the modular part that has the APIs that gnome uses. Whiners should consider spending some time learning how to build packages for their favorite distro, and they can do something productive. Systemd is already modular, but the distro packages are less so. So spend some time setting up a build system that divides it up. That will save people not running the init system from needing those parts of the code to be installed.
That isn't caused by systemd, that is caused by gnome sucking. Something that has been getting worse every year since Gtk3. Maybe they were lazy? It is like a voodoo spell, "gnome gnome gnome dependency!!!!" with no specific technical analysis of a problem.
You know... all that code that I don't know what it does because I don't understand the problem it solves! Surely if I don't know it can't be useful, right? Who are you to have features I don't understand?!/s
You have heard of heavy manufacturing? It is a thing. It is not my thing. It is also not a toy.
It is who funded and participated in development. So if you think the Japanese heavy manufacturing industry is a bubble, yes, that is bizarro world indeed.:P
Complete nonsense, most of the libraries are in C, and writing C is a regular part of a Ruby programmer's job.
If all you do is Rails, and not Ruby generally, then of course you won't be touching C. If you're the person writing the libraries that the Rails people will use, then you're using C frequently, even if it is only to write Ruby bindings for things. It is really more often about interfacing than speed. C is the general purpose interface language.
Using the Ruby C API you can write individual methods in C, and others in Ruby. The fact that you can re-open classes at any time means that isn't even a discrete feature, it is just the natural way things work.
As to which parts might get rewritten... the parts that were bottlenecks according to the benchmarks or profiler, and nothing else.
You're just wrong. It is not a point of bitcoin to make pseudo-anonymous transactions. That is just basic idiocy. Check the features, it is not something offered. It puts your purchase in public, and it discloses it to future recipients of the coin. It is in fact how it avoids using a central authority; instead it provides transparency. It is the exact opposite of anonymity. How do you tie your shoelaces in the morning?
Very few trees fall over from heavy rain. The vast majority of the treefall is wind and ice. That is just something obvious if you've been involved in the industry, or even read the numbers of customers affected by outages. It is just not the normal end that a tree has, and so it doesn't happen to a lot of customers. It shouldn't be more than one street for a couple blocks, and their power will be restored within a couple hours. And there are so few of those happening, that the response time will stay low.
Whereas wind and ice will cause more widespread outages that will strain response time, and that represents the vast majority of total downtime anywhere in the NW.
Slashdot Mirror
10 years ago they had been saying 10 years already.
We seem to have come to the root of the problem. When they say, "at least 10 years" and establish a minimum bound, you hear "10 years" and take it is a maximum.
R&D people do not promise to turn new technologies into products inside of a fixed time period. And when the say "at least 10 years" they're establishing a precision of a decade. It isn't a prediction at all, but if you wanted to translate it into one it would be something like "10-30 years" not "within 10 years."
Graphene has a lot of strength in a sheet, but it is soft and floppy. A graphene bullet would just be a carbon bullet. A graphene-coated bullet would be similar to a teflon coated bullet, but not as good and a lot more expensive.
it's theoretically correct
No, the precision disagrees and so it is neither theoretically or actually correct.
I think you're confusing "products" or "implementations" with "technologies." The only "technologies" that went quickly from discovery to a product were the bag clip and the slap-chop. Everything else took decades, you just didn't learn about it so you don't know about it. You hear the pre-release hype on the boob tube and then six months later you see the ad for the product. Z0MG they build stuffs so fast nowz!
10 years ago they were saying at least 10 years. Most of the big sexy breakthroughs have been in the last few years, and almost all of those are fairly fundamental and not at all close to being products. There are already high quality flexible display prototypes being shown at Japanese conventions. Right now I don't think anybody needs a flexible screen badly enough to pay the "prototype-adopter" prices. Give it a couple more years and they'll have something ready for "early" adopters.
After being forced to write papers in cursive as a child, you get to college... banned. Just straight out banned. You can hand print, or computer print.
Really? Wow. You do all your exams on computer? None of them are handwritten, not even the maths and physics exams?
Hand print or computer print. You've got some work to do before you worry about the exams! Hand print. The verb for hand printing is "print," too.
That is really the funniest part. After being forced to write papers in cursive as a child, you get to college... banned. Just straight out banned. You can hand print, or computer print.
The same thing would happen in a professional setting. If somebody submits a report in cursive, they can plan some time to rewrite it in print so everybody can read it.
I have buckets of pens and piles of notepads all over my desk and around my office.
I'll tell you though, I've never once grabbed a pad to jot a note and done it is cursive. Never once. I spent my early years suffering through the lessons; I could probably still write that way if I wanted. Writing quickly, it would be a total mess and impossible to read later. It made sense in a past where it was important to conserve ink and paper. When you're racing against your ink drying from exposure to air, you're better off not even lifting the quill. But by the time the ink was being manufactured into a pen, that time was past. Long before I was born!
Cursive is just an old alternate script, from an age where anything professional was hand lettered calligraphy. It is not useful as a backup skill for recording information on paper. That can be done with a pen and normal print script.
You haven't spent much time scribling on napkins. Cursive will tear the napkin and cause it to totally fall apart. You have to stick to print so when it tears it is in an isolated spot. Cursive, the napkin will be weakened continuously where you've written, and once a tear starts it keeps tearing - right through the writing!
As long as the kids are learning to print by hand, they will be fine. Cursive is now a specialized skill for caligraphers.
He talks right in that email about making it a "dependency" but about the need for support on non-linux platforms. That just clarifies that systemd doesn't want gnome to actually depend on systemd, just to have it is a build dependency and to have the features still work if it isn't there.
Now, gee, why is it that you dug out the reference, but didn't bother pointing out that it acquits systemd's author? He clearly is against gnome actually requiring systemd in the sense that people are accusing.
And yeah, any developer should realize what a PITA traditional locale support is on *nix. A solution for that is needed. Fix the problems that systemd is going solve for gnome, and it won't need to get the solutions from systemd.
Also note that it doesn't mean you'll need systemd installed to use gnome. You'll only need the modular part that has the APIs that gnome uses. Whiners should consider spending some time learning how to build packages for their favorite distro, and they can do something productive. Systemd is already modular, but the distro packages are less so. So spend some time setting up a build system that divides it up. That will save people not running the init system from needing those parts of the code to be installed.
That isn't caused by systemd, that is caused by gnome sucking. Something that has been getting worse every year since Gtk3. Maybe they were lazy? It is like a voodoo spell, "gnome gnome gnome dependency!!!!" with no specific technical analysis of a problem.
That seems backwards. Based on this claim, systemd reduces the coupling between Linux and GNU tools, and allows each part to be replaced more easily.
Dev-oo-an could be a village by a moor in England, I'm sure of it. Except you'd probably pronounce it Dev-oo-er.
Devuan, based on a Norman word for whiner. Who would doubt it?
You know... all that code that I don't know what it does because I don't understand the problem it solves! Surely if I don't know it can't be useful, right? Who are you to have features I don't understand?! /s
systemd is modular, that is in the list of debunked myths.
Haters hate more loudly than users use, that is all.
Haters might shut up and go to their new clubhouse, that could be a significant change.
If RedHat now = "The Man" then I think we can finally declare, Linux has won. Linux has taken over the world. Long Live Linus!
http://img.photobucket.com/alb...
They do look a lot alike.
If you know about the history of regex in Ruby, that one stands out as a complaint from 2005 or so recycled as FUD.
I'll give you a hint: Ruby doesn't use its own regex library...
You have heard of heavy manufacturing? It is a thing. It is not my thing. It is also not a toy.
It is who funded and participated in development. So if you think the Japanese heavy manufacturing industry is a bubble, yes, that is bizarro world indeed. :P
Complete nonsense, most of the libraries are in C, and writing C is a regular part of a Ruby programmer's job.
If all you do is Rails, and not Ruby generally, then of course you won't be touching C. If you're the person writing the libraries that the Rails people will use, then you're using C frequently, even if it is only to write Ruby bindings for things. It is really more often about interfacing than speed. C is the general purpose interface language.
Using the Ruby C API you can write individual methods in C, and others in Ruby. The fact that you can re-open classes at any time means that isn't even a discrete feature, it is just the natural way things work.
As to which parts might get rewritten... the parts that were bottlenecks according to the benchmarks or profiler, and nothing else.
You're just wrong. It is not a point of bitcoin to make pseudo-anonymous transactions. That is just basic idiocy. Check the features, it is not something offered. It puts your purchase in public, and it discloses it to future recipients of the coin. It is in fact how it avoids using a central authority; instead it provides transparency. It is the exact opposite of anonymity. How do you tie your shoelaces in the morning?
Disco was "temporarily popular" in the mainstream from 73 to 79. So again methinks you don't understand what fad means.
That doesn't even contradict me! lolololololol
Very few trees fall over from heavy rain. The vast majority of the treefall is wind and ice. That is just something obvious if you've been involved in the industry, or even read the numbers of customers affected by outages. It is just not the normal end that a tree has, and so it doesn't happen to a lot of customers. It shouldn't be more than one street for a couple blocks, and their power will be restored within a couple hours. And there are so few of those happening, that the response time will stay low.
Whereas wind and ice will cause more widespread outages that will strain response time, and that represents the vast majority of total downtime anywhere in the NW.