Who said it would? Not me, because I won't be using it. But I suspect a lot of readers are going to find the interruption of their focus to take away from the experience.
Oh come off it - you're not sending any page requests when you pull the plug, and if you're not running a public-facing server or transferring files in the background there shouldn't be anything connected anyway.
And those other machines are running anyway - over the course of a year, those retries will use less electricity than you save with one quickie shutdown.
My laptop battery is my built-in ups. And those "surge protectors" don't - and who cares about the "We'll pay up to 50,000 for equipment loss" - I just don't want to lose all my stuff. I'll play it save and unplug all the electronics, like the power company recommends.
You *do* hit save once in a while, don't you? The apps open with the last version that was saved to disk. What's so hard to understand about that?
Some go a bit extra - they alert you to the possibility of recovering the file first - but I like it when they just automatically open everything the way it was.
Also very handy when you're at a root console and you just want to go to bed - shut down, log in the next morning and you're back where you were.
In the Anti-Socialist Republic of Kanuckistan, book reads YOU!
Because you know that will be coming down the pike in a few years - "Let your book interact with you. Your web cam now takes a pic of you, pastes you into the scenes, has avatars of other readers, etc. Be really social!"
No thanks. I like to read to relax, read before I go to sleep, be able to put the book down and pick it up the next evening where I left off, without worrying that I might have offended someone by "ignoring" them, or have messages interrupt my reading, or not being able to take it into the bath.
I guess I should patent MY shutdown technique - goes back way before then. Make sure nothing important is going on (like a write operation), and just cut the power.
It still works great on modern OSes with a journaling file system - and the best part is that your whole desktop, including open apps and files, is restored next time you log in, and you only lose 2-5 seconds on reboot (which is less than the time you lose doing a clean shutdown), and you don't have to answer 3-4 dialogs asking if you want to save your session, etc.
Do that every time, and over the course of the year, you've saved 30 seconds x 250 days, oe 125 minutes - that's 2 HOURS of electricity. Be green - pull the plug:-)
Seriously, most of the time I shut down properly, but if I hear thunder close by, I just cut the power unless it's a laptop. Lightning doesn't have to be close enough to hear to induce surges in power lines, so I figure if I can hear it, it's already too close. I haven't lost any data doing this, but I *have* had to replace one cpu because of a power surge (and that was in the bad old days when you had to hand-solder them to the board).
Haven't you wondered why work hours are just like they are? (and so many other things...)
Work hours are the way they are for the employers' benefit, not yours. Look at how hard it is to get flex-time implemented anywhere, even though it's a proven productivity booster as well as lowering absenteeism.
This is because, despite our being "high tech", management STILL hasn't gotten a metric to measure productivity, so they substitute LOC and WAIC (lines of code and warm asses in chairs).
Look at kids. They don't want to come in when they're having fun. We FORCE them into a rigid schedule. Same thing when they're in school, so they sit there, many of them borde to death, and then we wonder why they don't learn. We do this because the only way we can "measure teacher effectiveness" is the number of hours spent on each class and the pass/fail rates (and the unions have sued to prevent the latter technique).
We're not machines - but we're doing a good imitation of making ourselves into bots.
Java is certainly not F/LOSS - it's VERY encumbered - why, even if you make something that ISN'T Java, you can get your a** sued.
So remember, never say that you want a "Cup of Java", or talk about the "Java Man" skeleton hoax, or the book "East of Java", of that your dad owned an "AMC Javalin", or "Javalin throwing".
Seriously though, I don't know what it is, but Ellison and Allen and Jobs and a few others of "a certain age" are going a bit wanky, thinking that they can close off stuff. For now, Jobs is having a modicum of success, but he's at least giving something to the people who buy his stuff - the others just want to build toll booths and collect the road taxes.
Oh well, they'll all be dead in 20 years or so... and old coots like Knuth, who would never dream of pulling this shite, will hopefully still be doing the code thing.
If I'm reading a book, it's because I WANT to be alone with the book and my imagination. The only communication I'm interested in is with the author's words.
We don't need, and we don't want, yet another "social platform."
And c is the son of assembler, and assembler is the son of people flipping switches on a panel, flipping switches on a panel is the son of jumping contacts on a punch-board, and jumping contact on a punchboard is the son of using an abacus, and using an abacus is the son of counting on your fingers, and counting on your fingers is the son of developing a concept called "more than 3" which in many cultures simply didn't exist, which is the son of putting the lie to the idea that we're somehow hard-wired for base 10, which is the parent of many other investigations into illogical thought, which leads us back to your statement. See how that works? It's tubular:-)
Isaac Newton had something to say about standing on the shoulders of others... every innovation owes something to somebody else. Think of how much you owe your mother, becuse the hand that rocks the cradle...
The original argument was that adobe hasn't created anything, just bought stuff. pdf proves this wrong.
They're probably the source of all those people who said "I tried linux, and switched back to Windows."
Stick with one of the other distros - they all have (much) lower dissatisfaction ratings. Heck, even Windows comes off better when you take into account market share.
Yes, your blood sugar tends to rise as you get older, but if it's so high that you can extract useful amounts of sugar on it, you should be taking meds.
The article says these are elderly diabetic patients. There's no reason for them to have higher blood sugar than anyone else - Banting and Best discovered insulin before most of them were even born.
I don't use operator overloading that much - mostly ++, --, + and -. They're a syntactic sugar that makes code pretty easy to understand, and it would be nice to have them in all languages.
There are definitely people who will never understand inheritance unless it involves a dead body and a will. And then there are those who think that everything has to be a derived class - they don't grok aggregation - what can you do? People are, for the most part, human.
We've know for a LONG time that teetotalers had higher rates of heart attacks than social drinkers. Abstention from alcohol is unnatural - even apes have been found to make home brew using fruits.
And where do you think the "milk from contented cows" came from? That silage at the end of the winter stinks of alcohol, it's been partially fermenting for months.
We agree on a lot of significant issues - and two of those are biggies- forcing everything into classes that they are hypocrites wrt operator overloading, etc. Unfortunately, since Oracle will sue you if you try to "extend" it in such a fashion... (even though it could in theory be kept compatible with the JVM...
And yes, I use gcc as a pre-processor when I write java. 1 #include as opposed to a ton of import statements (and the includes never use an import - they always use the fqn of the class, so no name clashes. This not only lets me have two or more classes with the same name (their dot.name will be different), but makes the emitted "intermediate source" more self-documenting.
Does this "prove" ubuntu is the crappiest distro? After all, the trend shows that more people complain about Ubuntu than everyone else combined. All it proves is you don't need Powerpoint to make you stupid, a few graphs can also do it.
Data points without context are not information - they're noise.
Mo - what's "amusing" is watching the Javanista continue to defend design mistakes that first Sun, and now Oracle, sontinue to cling to. For example there is no reason to have all graphics operations done in one thread - we solved that problem a few decades ago - the only problem was that at that time, computers didn't have enough memory. Times have changed, so has the hardware environment, but you wouldn't guess it looking at how stupidly Java manages it's paint events.
The oil isn't sitting there in foot-thick icebergs - otherwise they could just throw a hook on it and tow it to shore. I guess you missed all those pictures of the red oily foam.
now have that in contact with a couple atoms thick layer of crude and you now have combusted crude.
No, you don't. The surface area of the atoms in question respective to the enclosed volume and their mean free path before coming into contact with another atom guarantees that the "fire" is quenched immediately. It never even gets statted, You oxidize a few particles, that's all.
These kids are from MIT, they are most likely MUCH smarter than you,
I seriously doubt it. BTW, only 65% of MIT graduate students have had sex. Obviously either MIT attracts people who are butt-ugly and lack soft skills, or there's a severe shortage of beer (it doesn't take a rocket scientist to figure out how to open a bottle).
Thanks for the update. I notice that it also says that it supports pdf draw commands. Maybe that can be exploited to imitate some sort of flash proxy, for games, etc (obviously not going to be fast enough for video).
In iOS 3.2, the UIKit framework provides a set of functions for generating PDF content using native drawing code. These functions let you create a graphics context that targets a PDF file or PDF data object. You can then draw into this graphics context using the same UIKit and Core Graphics drawing routines you use when drawing to the screen. You can create any number of pages for the PDF, and when you are done, what you are left with is a PDF version of what you drew.
When I first attacked the problem, I had never written threaded c code before, and never written network code, nor had I used the c api with mysql. However, I knew that, given a few days, I'd get the hang of it - after all, it's all written with a certain logic behind it, so there are only a few ways it COULD work, and knowing the theory behind it all, it wasn't that hard.
I would say that those developers who would sink in such a problem could still be trusted with an improved Java, one that is more expressive. Give us multiple inheritance, structs and typedefs so we can make our own primitives, and (since Sun overloaded the math operators anyway so they work on both primitives and objects) operator overloading.
Sure, some programmers will screw it up, but most won't. And we won't have the inevitable code bloat from single inheritance and the need to wrap everything into the current Java model.
Is that too much to ask? Don't Java programmers deserve the best language possible? Wouldn't it be nice not to have me ranting about it?:-)
I'm not the enemy here. Sun messed up. Ever since Java first came out, I *wanted* it to succeed - but it's not done right. It suffers from a restrictive programming model, a too-rigid, artificially constrained class hierarchy, and the whole "lets bolt on some more sh*te in the next release so we have something else to talk about."
Will I use Java. Sure. Do I want it to be better? Of course. Do I think Oracle is right? Absolutely not. Java needs a fork - badly. And not dalvik. Dalvik doesn't attack the real issues - what was a great idea needs to be scrubbed down, stripped to its core, reinforced with new ways of doing things, and then make its way into the world as what it could have been.
Your comments point out one of the advantages of using c instead of c++ (or using c++ but not always creating objects to encapsulate code and data). Allocate a chunk of ram (enough for your data) in one shot, and whenever you need a new data structure, just stick it somewhere in there and point to the head. It makes for a much quicker "fake tree" than actually allocating objects to represent each node, and you don't ever have to free anything until you exit the program, then you just free that one memory structure. Need to grow it past your existing boundary? You can either use an array approach (allocate another chunk for another 100 data structs) or realloc (or realloc, and if it fails to grow the chunk because of fragmentation, then fall back to the array approach).
That's a lot quicker than the usual approach of creating objects for each node (and it makes it a lot quicker to do a search on un-indexed data)
All that being said, I think that people are missing the real point - Java can and should be improved. The original concept was good, but the implementation was always uninspiring. There were some design mistakes that "looked good at the time", but single inheritance was a serious blunder. Sun kept everything so "don't you dare fork this" that nobody came up with a proper mechanism for multiple inheritance. Just like it would be nice to have structs (so we can define our own "primitive data types" if we want and get the same performance advantage as with Java primitives), and, seeing as how Sun overloaded all the mathematical operators anyway (they work on both primitive types and objects, and + also works on strings), why can't we be trusted with the same ability? We're not dummies.
They could have called it Java++ or Java.NET or J# or JavaXT or JavaNG or Java 2.0 or Mocha or Avaj or Squirrel (squirrels like Oak), or whatever, and it would have been a much more flexible, expressive language. Then you wouldn't have me PMSing about it:-)
I *did* say "maybe". Adults should be able to function if they miss an occasional full night's sleep. This often improves with age. One of the reason older people don't get a good night's sleep is because they try too hard to get a full 8 hours when they don't need it, and as a result, the sleep they *do* get is pretty shallow.
though I personally do tend to get a great second wind around 9 p.m. It only tends to last a couple of hours, though, not deep into the night.
The body has a natural low around 2 am. If I;m on a roll, I'll walk the dogs to get through it, get some new ideas, get the blood circulating in the extremities (including the brain). By 3 am I'm pretty much back to normal, and the next thing I know, the sun is up, the birds are chirping, I've got the work I wanted to do done, and then some, and it's time to walk the dogs. I can then do a normal day, walk the dogs in the evening, go to bed around 11 pm, read for a bit, then get a solid 7-8 hours of sleep (you can call it either the sleep of the just or the sleep of the dead:-), and I'm good.
I've pretty much always been able to do that once or twice a week, except when there's been something physically wrong (like fighting off an infection). It's the 3 and 4-day stretches that kill. I once did 5 days - Sunday to Friday, with 2 hours sleep on Wednesday and 3 hours on Thursday. Finished by dawn Friday, showered, went to bed, and COULDN'T SLEEP! I had to go drive around for a couple of hours, and visit some friends, to "decompress." Mind you. everyone else who was involved was also beat, beat up, bushed, bagged, zonked, dead on their feet, falling asleep with their face in their eggs and bacon, etc. You can have some strange moments when you're that sleep-deprived. Like waiting for the stop-sign to turn green (pretty common, actually, and a good indicator that it's time to hit the hay if you have a chance).
Slashdot Mirror
Who said it would? Not me, because I won't be using it. But I suspect a lot of readers are going to find the interruption of their focus to take away from the experience.
And those other machines are running anyway - over the course of a year, those retries will use less electricity than you save with one quickie shutdown.
My laptop battery is my built-in ups. And those "surge protectors" don't - and who cares about the "We'll pay up to 50,000 for equipment loss" - I just don't want to lose all my stuff. I'll play it save and unplug all the electronics, like the power company recommends.
You *do* hit save once in a while, don't you? The apps open with the last version that was saved to disk. What's so hard to understand about that?
Some go a bit extra - they alert you to the possibility of recovering the file first - but I like it when they just automatically open everything the way it was.
Also very handy when you're at a root console and you just want to go to bed - shut down, log in the next morning and you're back where you were.
In the Anti-Socialist Republic of Kanuckistan, book reads YOU!
Because you know that will be coming down the pike in a few years - "Let your book interact with you. Your web cam now takes a pic of you, pastes you into the scenes, has avatars of other readers, etc. Be really social!"
No thanks. I like to read to relax, read before I go to sleep, be able to put the book down and pick it up the next evening where I left off, without worrying that I might have offended someone by "ignoring" them, or have messages interrupt my reading, or not being able to take it into the bath.
I guess I should patent MY shutdown technique - goes back way before then. Make sure nothing important is going on (like a write operation), and just cut the power.
It still works great on modern OSes with a journaling file system - and the best part is that your whole desktop, including open apps and files, is restored next time you log in, and you only lose 2-5 seconds on reboot (which is less than the time you lose doing a clean shutdown), and you don't have to answer 3-4 dialogs asking if you want to save your session, etc.
Do that every time, and over the course of the year, you've saved 30 seconds x 250 days, oe 125 minutes - that's 2 HOURS of electricity. Be green - pull the plug :-)
Seriously, most of the time I shut down properly, but if I hear thunder close by, I just cut the power unless it's a laptop. Lightning doesn't have to be close enough to hear to induce surges in power lines, so I figure if I can hear it, it's already too close. I haven't lost any data doing this, but I *have* had to replace one cpu because of a power surge (and that was in the bad old days when you had to hand-solder them to the board).
Pull the plug. A *real* OS can handle it.
Work hours are the way they are for the employers' benefit, not yours. Look at how hard it is to get flex-time implemented anywhere, even though it's a proven productivity booster as well as lowering absenteeism.
This is because, despite our being "high tech", management STILL hasn't gotten a metric to measure productivity, so they substitute LOC and WAIC (lines of code and warm asses in chairs).
Look at kids. They don't want to come in when they're having fun. We FORCE them into a rigid schedule. Same thing when they're in school, so they sit there, many of them borde to death, and then we wonder why they don't learn. We do this because the only way we can "measure teacher effectiveness" is the number of hours spent on each class and the pass/fail rates (and the unions have sued to prevent the latter technique).
We're not machines - but we're doing a good imitation of making ourselves into bots.
Java is certainly not F/LOSS - it's VERY encumbered - why, even if you make something that ISN'T Java, you can get your a** sued.
So remember, never say that you want a "Cup of Java", or talk about the "Java Man" skeleton hoax, or the book "East of Java", of that your dad owned an "AMC Javalin", or "Javalin throwing".
Seriously though, I don't know what it is, but Ellison and Allen and Jobs and a few others of "a certain age" are going a bit wanky, thinking that they can close off stuff. For now, Jobs is having a modicum of success, but he's at least giving something to the people who buy his stuff - the others just want to build toll booths and collect the road taxes.
Oh well, they'll all be dead in 20 years or so ... and old coots like Knuth, who would never dream of pulling this shite, will hopefully still be doing the code thing.
If I'm reading a book, it's because I WANT to be alone with the book and my imagination. The only communication I'm interested in is with the author's words.
We don't need, and we don't want, yet another "social platform."
And c is the son of assembler, and assembler is the son of people flipping switches on a panel, flipping switches on a panel is the son of jumping contacts on a punch-board, and jumping contact on a punchboard is the son of using an abacus, and using an abacus is the son of counting on your fingers, and counting on your fingers is the son of developing a concept called "more than 3" which in many cultures simply didn't exist, which is the son of putting the lie to the idea that we're somehow hard-wired for base 10, which is the parent of many other investigations into illogical thought, which leads us back to your statement. See how that works? It's tubular :-)
Isaac Newton had something to say about standing on the shoulders of others ... every innovation owes something to somebody else. Think of how much you owe your mother, becuse the hand that rocks the cradle ...
The original argument was that adobe hasn't created anything, just bought stuff. pdf proves this wrong.
None - including myself. linux doesn't necessarily mean Ubuntu, which is a good thing, because Ubuntu ranks #1 in terms of user dissatisfaction.
They're probably the source of all those people who said "I tried linux, and switched back to Windows."
Stick with one of the other distros - they all have (much) lower dissatisfaction ratings. Heck, even Windows comes off better when you take into account market share.
The article says these are elderly diabetic patients. There's no reason for them to have higher blood sugar than anyone else - Banting and Best discovered insulin before most of them were even born.
Sounds like either neglect or abuse to me.
I don't use operator overloading that much - mostly ++, --, + and -. They're a syntactic sugar that makes code pretty easy to understand, and it would be nice to have them in all languages.
There are definitely people who will never understand inheritance unless it involves a dead body and a will. And then there are those who think that everything has to be a derived class - they don't grok aggregation - what can you do? People are, for the most part, human.
As for reading a book or 20, I have over 1,000 in my personal library, all read - including a great assortment of computer books (many from O'Reilly).
Maybe you should learn to look a bit more deeply into things instead of being a dismissive little snot.
We've know for a LONG time that teetotalers had higher rates of heart attacks than social drinkers. Abstention from alcohol is unnatural - even apes have been found to make home brew using fruits. And where do you think the "milk from contented cows" came from? That silage at the end of the winter stinks of alcohol, it's been partially fermenting for months.
And yes, I use gcc as a pre-processor when I write java. 1 #include as opposed to a ton of import statements (and the includes never use an import - they always use the fqn of the class, so no name clashes. This not only lets me have two or more classes with the same name (their dot.name will be different), but makes the emitted "intermediate source" more self-documenting.
Data points without context are not information - they're noise.
It's WAY past time for a fork.
The oil isn't sitting there in foot-thick icebergs - otherwise they could just throw a hook on it and tow it to shore. I guess you missed all those pictures of the red oily foam.
No, you don't. The surface area of the atoms in question respective to the enclosed volume and their mean free path before coming into contact with another atom guarantees that the "fire" is quenched immediately. It never even gets statted, You oxidize a few particles, that's all.
I seriously doubt it. BTW, only 65% of MIT graduate students have had sex. Obviously either MIT attracts people who are butt-ugly and lack soft skills, or there's a severe shortage of beer (it doesn't take a rocket scientist to figure out how to open a bottle).
In iOS 3.2, the UIKit framework provides a set of functions for generating PDF content using native drawing code. These functions let you create a graphics context that targets a PDF file or PDF data object. You can then draw into this graphics context using the same UIKit and Core Graphics drawing routines you use when drawing to the screen. You can create any number of pages for the PDF, and when you are done, what you are left with is a PDF version of what you drew.
When I first attacked the problem, I had never written threaded c code before, and never written network code, nor had I used the c api with mysql. However, I knew that, given a few days, I'd get the hang of it - after all, it's all written with a certain logic behind it, so there are only a few ways it COULD work, and knowing the theory behind it all, it wasn't that hard.
I would say that those developers who would sink in such a problem could still be trusted with an improved Java, one that is more expressive. Give us multiple inheritance, structs and typedefs so we can make our own primitives, and (since Sun overloaded the math operators anyway so they work on both primitives and objects) operator overloading.
Sure, some programmers will screw it up, but most won't. And we won't have the inevitable code bloat from single inheritance and the need to wrap everything into the current Java model.
Is that too much to ask? Don't Java programmers deserve the best language possible? Wouldn't it be nice not to have me ranting about it? :-)
I'm not the enemy here. Sun messed up. Ever since Java first came out, I *wanted* it to succeed - but it's not done right. It suffers from a restrictive programming model, a too-rigid, artificially constrained class hierarchy, and the whole "lets bolt on some more sh*te in the next release so we have something else to talk about."
Will I use Java. Sure. Do I want it to be better? Of course. Do I think Oracle is right? Absolutely not. Java needs a fork - badly. And not dalvik. Dalvik doesn't attack the real issues - what was a great idea needs to be scrubbed down, stripped to its core, reinforced with new ways of doing things, and then make its way into the world as what it could have been.
Your comments point out one of the advantages of using c instead of c++ (or using c++ but not always creating objects to encapsulate code and data). Allocate a chunk of ram (enough for your data) in one shot, and whenever you need a new data structure, just stick it somewhere in there and point to the head. It makes for a much quicker "fake tree" than actually allocating objects to represent each node, and you don't ever have to free anything until you exit the program, then you just free that one memory structure. Need to grow it past your existing boundary? You can either use an array approach (allocate another chunk for another 100 data structs) or realloc (or realloc, and if it fails to grow the chunk because of fragmentation, then fall back to the array approach).
That's a lot quicker than the usual approach of creating objects for each node (and it makes it a lot quicker to do a search on un-indexed data)
All that being said, I think that people are missing the real point - Java can and should be improved. The original concept was good, but the implementation was always uninspiring. There were some design mistakes that "looked good at the time", but single inheritance was a serious blunder. Sun kept everything so "don't you dare fork this" that nobody came up with a proper mechanism for multiple inheritance. Just like it would be nice to have structs (so we can define our own "primitive data types" if we want and get the same performance advantage as with Java primitives), and, seeing as how Sun overloaded all the mathematical operators anyway (they work on both primitive types and objects, and + also works on strings), why can't we be trusted with the same ability? We're not dummies.
They could have called it Java++ or Java.NET or J# or JavaXT or JavaNG or Java 2.0 or Mocha or Avaj or Squirrel (squirrels like Oak), or whatever, and it would have been a much more flexible, expressive language. Then you wouldn't have me PMSing about it :-)
I *did* say "maybe". Adults should be able to function if they miss an occasional full night's sleep. This often improves with age. One of the reason older people don't get a good night's sleep is because they try too hard to get a full 8 hours when they don't need it, and as a result, the sleep they *do* get is pretty shallow.
The body has a natural low around 2 am. If I;m on a roll, I'll walk the dogs to get through it, get some new ideas, get the blood circulating in the extremities (including the brain). By 3 am I'm pretty much back to normal, and the next thing I know, the sun is up, the birds are chirping, I've got the work I wanted to do done, and then some, and it's time to walk the dogs. I can then do a normal day, walk the dogs in the evening, go to bed around 11 pm, read for a bit, then get a solid 7-8 hours of sleep (you can call it either the sleep of the just or the sleep of the dead :-), and I'm good.
I've pretty much always been able to do that once or twice a week, except when there's been something physically wrong (like fighting off an infection). It's the 3 and 4-day stretches that kill. I once did 5 days - Sunday to Friday, with 2 hours sleep on Wednesday and 3 hours on Thursday. Finished by dawn Friday, showered, went to bed, and COULDN'T SLEEP! I had to go drive around for a couple of hours, and visit some friends, to "decompress." Mind you. everyone else who was involved was also beat, beat up, bushed, bagged, zonked, dead on their feet, falling asleep with their face in their eggs and bacon, etc. You can have some strange moments when you're that sleep-deprived. Like waiting for the stop-sign to turn green (pretty common, actually, and a good indicator that it's time to hit the hay if you have a chance).
I can buy into that.