"It's a bit much to believe she has the worst memory ever, but only when it comes to things which are potentially damaging to her criminally and politically."
Actually, Narcissistic Personality Disorder combined with trauma-induced schizophrenia would produce *exactly* this effect.
Sounds about right, but what trauma did Trump experience?:-)
Actually, yes. Mixing tabs and spaces to make a single indent level (e.g., 0x09 0x20 0x20 0x20 0x20 0x09 0x20 0x20 0x20 0x20) is about the most braindead, stupid, foolish, retarded, dumb thing you could ever do in a text file. It ruins things for everyone.
Emacs auto-indenting doesn't do it that way. It uses tabs then spaces. So (by default) an indent of 4 would be (4 spaces), an indent of 10 would be (1 tab + 2 spaces) an indent of 17 would be (2 tabs + 1 space)... People (including myself) have been using this indent behavior in Emacs for about 30 years w/o problems. You don't seem to be speaking from a point of experience here, as I am. Code formatted this way displays correctly in Vi, and other editors, regardless of the tab-width setting. In addition, the actual indent levels are language dependent and the Emacs mode styles are completely configurable.
That is truly the worst of both worlds. If you're going to use tabs, then tabs should be used for indenting (i.e. the block-level of the code) and spaces for formatting after the appropriate indent has been achieved, and the two should not mix.
Also, to follow up, Emacs has language-specific mode styles and knows how to indent code properly. It just uses a mix of tabs and spaces to achieve that indenting. All of this is configurable, but I always use the default style settings. Many of the posts for this article mention editors doing smart indenting rather than people just using tabs/spaces willy-nilly.
Bzzzzzt. Combining tabs and spaces to make up a single indent level is BRAIN DEAD.
Actually no. Indenting w/just tabs is brain dead and indenting w/just spaces is counter-productive. Your low UID aside, I'll stack my 30 years of experience using Emacs like that against that any day.
As long as the indenting method is consistent, there's generally no problem regardless of the displayed tab-width -- which people should just fucking leave at 8 spaces and don't use so many of them. (People that indent using only tabs should simply be killed.) In addition, I've been doing this since 1985 and neither I or my co-workers have *ever* had any problem with my code. To the contrary, code that has been edited (usually) in vi, indented using just tabs, but with a smaller tab-width is much more problematic and ugly (and requires either tweaking the editor to display correctly or simply re-indenting the code properly).
My 30 years of experience, millions of lines of code generated and edited, in about 20 languages, on just about everything from PCs to Cray computers (using and administrating) stands pretty solidly.
I use Emacs with a function bound to the Return Key that performs a and the re-indent function indents with tabs and spaces as appropriate -- meaning 10 spaces would be indented using 1 tab and 2 spaces.
(defun smart-newline ()
"(reindent-then-newline-and-indent) if in a mode listed in smart-newline-modes. Otherwise just (newline)."
(interactive)
(if (memq major-mode smart-newline-modes)
(reindent-then-newline-and-indent)
(newline)))
Even an infinitesimal propulsion could get a micro-probe up to near light speed...
It could probably get anything up to near light speed given enough time... And keeping a micro-probe from getting destroyed by a particle of dust, while moving at near light speed, is whole other problem.
... inside a locked box that requires a 10-digit code + retinal scan + penis imprint, stored at the bottom of a lake, filled with sharks, wearing lasers.
Someone once made it to the lock-box, but... I just didn't have to feed the sharks that day.
I even have a sign posted: Do not look at sharks with remaining good eye.
The portends to be based on 1980's experiences,...
Not mine. From 1985-87, while still in school, I worked on developing automatic-programming code on a Xerox 1108 (Dandelion) in InterLISP-D. And ported Franz LISP from 4.3 BSD on a VAX 785 to SunOS on a Sun-3 (I believe). After graduating, I later went to work at NASA Langley in 1988 as a sysadmin for their Convex and Cray (2 and YMP) systems.
I watched most (maybe all) of the first season of "Halt and Catch Fire" and was pretty bored. Never went back.
Although... my micro-programming / assembly class was on IBM/Intel PCs because the IBM 360 had actually caught fire the previous semester. Don't know if it halted first.
"I was just a college student a couple of years ago and now I am working on an actual space mission, how cool is that," said Karan Vaish, 23, who is helping the team to design the lunar rover.
Neil Armstrong was 38 when he walked on the Moon, 24 years before you were born -- after being a Navy pilot, graduating from Purdue, being a test pilot and being in the astronaut program for 11 years. You graduated from school and are playing with robots. Granted, they're "space robots" and that is pretty cool, but keep a little perspective.
That aside. Why is it news that younger people work on things too? Someone has to take over and do things. Young graduates with excellent training and skills seems appropriately normal. Hopefully the youngsters will learn from both the achievements and mistakes of their predecessors - you know, all the older folks that did it first.
I am terrified of the prospect. As some point, I should start living a more risky lifestyle, since 3 out of 4 of my grandparents lived well into their '90s. Maybe I can kill myself in my early '90s through a skydiving accident or something.
Don't worry. It doesn't always work out that way. My wife's parents both lived until they were in their 90s -- father died of Parkinson's and mother died of Alzheimer's'' (both within a fairly short time after becoming debilitated), but Sue died at 61 of a brain tumor (just 7 weeks after diagnosis). I was 42 at the time, now 53. Both of my parents are still alive and healthy in their 70s. I don't know what's in store for me going forward, but at least I'm not afraid of death - because Sue is there somewhere (even if that's nowhere).
Please be sure not to "talk back" while testing this beta operating system!
I thought Canonical stopped listening to user feedback years ago anyway.
They listen, the problem is just that they think they know better.... I just wish they would get back to that and start working with the community again.
Ya. Good thing that doesn't happen elsewhere... (cough) systemd (cough)
Slashdot Mirror
If you're voting for this woman, you're every bit the partisan idiot she was counting on you to be.
And... if you're voting for Trump, you're just an idiot. So where does that leave us?
"It's a bit much to believe she has the worst memory ever, but only when it comes to things which are potentially damaging to her criminally and politically."
Actually, Narcissistic Personality Disorder combined with trauma-induced schizophrenia would produce *exactly* this effect.
Sounds about right, but what trauma did Trump experience? :-)
Well I don't even have a smartphone, so that makes me TEN TIMES as humble as you!
Ya, but do you, or your feature phone, even lift?
It's just another attempt by Microsoft to make us all see Windows 10 through rose-colored glass(es).
Actually, yes. Mixing tabs and spaces to make a single indent level (e.g., 0x09 0x20 0x20 0x20 0x20 0x09 0x20 0x20 0x20 0x20) is about the most braindead, stupid, foolish, retarded, dumb thing you could ever do in a text file. It ruins things for everyone.
Emacs auto-indenting doesn't do it that way. It uses tabs then spaces. So (by default) an indent of 4 would be (4 spaces), an indent of 10 would be (1 tab + 2 spaces) an indent of 17 would be (2 tabs + 1 space) ... People (including myself) have been using this indent behavior in Emacs for about 30 years w/o problems. You don't seem to be speaking from a point of experience here, as I am. Code formatted this way displays correctly in Vi, and other editors, regardless of the tab-width setting. In addition, the actual indent levels are language dependent and the Emacs mode styles are completely configurable.
That is truly the worst of both worlds. If you're going to use tabs, then tabs should be used for indenting (i.e. the block-level of the code) and spaces for formatting after the appropriate indent has been achieved, and the two should not mix.
Also, to follow up, Emacs has language-specific mode styles and knows how to indent code properly. It just uses a mix of tabs and spaces to achieve that indenting. All of this is configurable, but I always use the default style settings. Many of the posts for this article mention editors doing smart indenting rather than people just using tabs/spaces willy-nilly.
Bzzzzzt. Combining tabs and spaces to make up a single indent level is BRAIN DEAD.
Actually no. Indenting w/just tabs is brain dead and indenting w/just spaces is counter-productive. Your low UID aside, I'll stack my 30 years of experience using Emacs like that against that any day.
As long as the indenting method is consistent, there's generally no problem regardless of the displayed tab-width -- which people should just fucking leave at 8 spaces and don't use so many of them. (People that indent using only tabs should simply be killed.) In addition, I've been doing this since 1985 and neither I or my co-workers have *ever* had any problem with my code. To the contrary, code that has been edited (usually) in vi, indented using just tabs, but with a smaller tab-width is much more problematic and ugly (and requires either tweaking the editor to display correctly or simply re-indenting the code properly).
My 30 years of experience, millions of lines of code generated and edited, in about 20 languages, on just about everything from PCs to Cray computers (using and administrating) stands pretty solidly.
I use Emacs with a function bound to the Return Key that performs a and the re-indent function indents with tabs and spaces as appropriate -- meaning 10 spaces would be indented using 1 tab and 2 spaces.
(defun smart-newline ()
"(reindent-then-newline-and-indent) if in a mode listed in smart-newline-modes. Otherwise just (newline)."
(interactive)
(if (memq major-mode smart-newline-modes)
(reindent-then-newline-and-indent)
(newline)))
that space debris has created more space debris that will create more space debris that ...
When objects traveling 16000mph collide what do you expect?
If they're both going the same direction, then not much... rubbing is racing.
In addition to the speaker, the Wave features a microphone array for Cortana support.
You spoiled it.
Samuel L. Jackson will probably play him in the inevitable biopic.
Privatization - better, cheaper, faster... more bang for the buck.
Even an infinitesimal propulsion could get a micro-probe up to near light speed ...
It could probably get anything up to near light speed given enough time... And keeping a micro-probe from getting destroyed by a particle of dust, while moving at near light speed, is whole other problem.
It never helps when the phone is smarter than the user.
It said it 'included' powdered cheese and canned tuna. It could of also had literally anything else.
They counted themselves lucky. The previous simulation included canned cheese and powered tuna.
Someone once made it to the lock-box, but... I just didn't have to feed the sharks that day.
I even have a sign posted: Do not look at sharks with remaining good eye.
Big deal. Your 6-digit id would seem to indicate that there are those older than you here on /.
You know that your userid is not tied to your age right? And not all people stick to one account for their whole lives.
Ya. It's a /. meme. But I guess you might be too young to know that -- having a 7-digit uid and all. :-)
The portends to be based on 1980's experiences, ...
Not mine. From 1985-87, while still in school, I worked on developing automatic-programming code on a Xerox 1108 (Dandelion) in InterLISP-D. And ported Franz LISP from 4.3 BSD on a VAX 785 to SunOS on a Sun-3 (I believe). After graduating, I later went to work at NASA Langley in 1988 as a sysadmin for their Convex and Cray (2 and YMP) systems.
I watched most (maybe all) of the first season of "Halt and Catch Fire" and was pretty bored. Never went back.
Although... my micro-programming / assembly class was on IBM/Intel PCs because the IBM 360 had actually caught fire the previous semester. Don't know if it halted first.
"I was just a college student a couple of years ago and now I am working on an actual space mission, how cool is that," said Karan Vaish, 23, who is helping the team to design the lunar rover.
Neil Armstrong was 38 when he walked on the Moon, 24 years before you were born -- after being a Navy pilot, graduating from Purdue, being a test pilot and being in the astronaut program for 11 years. You graduated from school and are playing with robots. Granted, they're "space robots" and that is pretty cool, but keep a little perspective.
That aside. Why is it news that younger people work on things too? Someone has to take over and do things. Young graduates with excellent training and skills seems appropriately normal. Hopefully the youngsters will learn from both the achievements and mistakes of their predecessors - you know, all the older folks that did it first.
I am terrified of the prospect. As some point, I should start living a more risky lifestyle, since 3 out of 4 of my grandparents lived well into their '90s. Maybe I can kill myself in my early '90s through a skydiving accident or something.
Don't worry. It doesn't always work out that way. My wife's parents both lived until they were in their 90s -- father died of Parkinson's and mother died of Alzheimer's'' (both within a fairly short time after becoming debilitated), but Sue died at 61 of a brain tumor (just 7 weeks after diagnosis). I was 42 at the time, now 53. Both of my parents are still alive and healthy in their 70s. I don't know what's in store for me going forward, but at least I'm not afraid of death - because Sue is there somewhere (even if that's nowhere).
I was born on December 30, 1870 and as soon as my birth certificate arrives in the mail I'll be able to prove it.
Big deal. Your 6-digit id would seem to indicate that there are those older than you here on /. - but not me :-)
Please be sure not to "talk back" while testing this beta operating system!
I thought Canonical stopped listening to user feedback years ago anyway.
They listen, the problem is just that they think they know better. ... I just wish they would get back to that and start working with the community again.
Ya. Good thing that doesn't happen elsewhere... (cough) systemd (cough)
Dubbed "Unlimited Freedom Premium" plan, ...
I thought you couldn't put a premium on Freedom -- especially "Unlimited" kind.