As others have said, this is ridiculous. Many people start programming when they're quite young. I was proficient in BASIC (not that it's something to brag about:-) ) when I was 7, and Java before I was 12.
Secondly, abstract is not required to understand at least some programming languages. If somebody suggested teaching them the Lambda Calculus, I'd be a bit worried, but something like C/BASIC/etc. is sufficiently procedural to make things easy. Don't confuse procedural languages with algebra just because both involve variables, because the concepts are actually very different in different languages. (I'm unsure whether Lisp/Scheme would be "too abstract" for people. I don't think functional programming would be the problem; if anything, it'd be the syntax (not the parenthesis.))
Thirdly, you divide people into "12-13" year-olds and "13-14" year olds. Leaving aside that people 13 years old fall into both classes, one year of age difference is very little basis on which to delay teaching people programming.
Finally, and most importantly, you mention that those ages are where abstract thought develops "on average". Other people in this thread who have supported you have again cited average cases. NotesSensei is not going to be teaching a school-wide programming class. NotesSensei is going to be teaching programming to people who have joined a computer club. There's a big difference there.
As for precisely what to each them, I wouldn't recommend VBScript or, therefore, KPL. I also would not recommend Java; while I think Java is a nice programming language and has many decent uses, I don't think it'd be a language that kids would like to learn as there first language. There's way too much figurative red tape to wade through to get anything done. The same probably applies to greenfoot. I would probably recommend Python.
initrd's are also useful if you want to use fancy disk formats (RAID/LVM/EVMS/etc.) Some desktop users will want to use an initrd.
The point of an initrds (now, at least) is to pull out the work of finding the root filesystem from the kernel and get it into userspace, which is much easier to maintain. Eventually, even "regular" root devices/filesystems will be mounted by an initrd, and the kernel will be that much smaller and more maintainable.
(I'm using "initrd" as a synonym for "initramfs", even though they're not actually synonymous.)
As this post's sibling has pointed out, ash, the minimalist shell component of BusyBox, is what the article's author intended to use.
Furthermore, the proc filesystem, like most (all?) virtual filesystems, doesn't care what the device name is. Most people use "none", for clarity, but/proc should work just as well.
Random junk works well enough if you're sure (and rightly so) that you'll remember your passwords and if you're sure the service won't decide to change them. That has happened to me, and resulted in switching cell phone providers because my account with the old provider was therefore no longer accessible. (Their service left something to be desired anyway.)
Other people have hinted at this, but nobody has said it directly: Windows installations can be copied trivially (dd, cp, etc.) if the old drive is removed when the system is first booted from the new drive. If you do that, Windows will (on that first boot), readjust all its internal cruft. After that, you can reconnect the old drive, which will then appear as a non-C: drive.
Keep in mind, however, that the sysadmin is also going to be installing all the software, and telling the higher-ups exactly how to configure encryption. To paraphrase an ancestor post: "If you don't trust your sysadmin, who do you trust?"
I would suggest using Thunderbird to download all the mail from AOL's IMAP servers, burning a copy to CD (just in case), and then redirecting/bouncing/remailing/etc. every message to the gmail account.
I once had a Linksys BEFSR11 (1-port Cable/DSL router) with a very weird problem-- TCP connections didn't work. UDP worked fine, ICMP worked fine, but not TCP.
I tried 3 different firmware versions over a period over 2 years. By the end of it all, I was pretty sure I had a paperweight, so I called Linksys tech to confirm.
The first thing they asked me was what OS I was using. Since I had tested it with 4 different computers collectively running Windows 2000, Linux, OS X 10.2, and OS X 10.3, I told them I had tested it with multiple computers and multiple OSs. They kept asking, I finally told them OS X. The same thing happened with ISPs (I've tried our LAN, Speakeasy, and Adelphia.) I finally told them Speakeasy. It kept going on.... TCP settings, etc.
I asked to speak to their supervisor, they hung up.
I called back, and told them exactly what was wrong-- TCP connections weren't working, but other IP types were, that I had tried it with multiple computers, OSs, ISPs, etc. They started asking about my TCP settings...
I called back, and immediately asked for a supervisor. I asked her if she knew the difference between TCP and UDP. She said she did, so I told her the situation, and she agreed the box was fried.
When you download a work, reproduction necessarily occurs. When you provide a work on a server for people to download, distribution occurs.
This is the core problem in your argument. If you're planning on giving what you download to somebody else, you're redistributing it, and it is illegal. Otherwise, the copy you make when downloading is (by definition) for personal use, and thus exempt. It's in copyright law.
All documents should be XML (or some other data discription language.) CSS's sucessor should be used to assign elements presentation. Possibly by converting them to other element trees.
The XML should be psuedo-standardized, so browsers would be able to recognize TV-Listing-ML/Search-Result-ML and present it in an alternate form, if you wanted, with headers and footers added (to make advertisers happy, unfortonately necessary for a new Web protocol to suceed.)
Ya want to know what I would have done? (Don't answer that.)
I would have used annoyed and stern tone, and told him, "Alright then. What's your name? [Write it down.]] I want to cancel my account; and I don't want to bother calling you again. I have no intention of paying anymore, so here's what you'll need to do: you'll need to write my name and account information down on a Post-it note, and when the database comes up again, put the cancelation through for me."
If he told me I needed to be on the phone, I'd say tell them (that they already have my phone number on file || what my phone number is) and to call me sometime. When [insert times I'm not likely to be sleeping.]
That'd show them!
Re:Why it wasn't put in already
on
Hacking Quartz
·
· Score: 1
I wrote a comment in reply to two posts, this was the second. The reply is in another thread, please post comments there.
The relevant text of the comment was:
This is a task-oriented job-- each server is a task. I use virtual desktops-- [stickies, notes, etc] [chat, email,/.] [perl code I'm writing-- a few vims, a test window, a few man-pages] [something for school (though not now)-- HTML editor, Safari window, Preview of the PDF version] [[repeat last two for a while]] [DVD] etc.
I switch desktops when I switch projects; when I start working on my perl code again, I switch to it. "Arbitrary" new windows don't need to be assigned; they appear on my perl desktop; that's where I am. If I start a new project, I switch to a blank desktop, and then start working on it.
Expose can be useful for the average Mac user (not Aunt Tille, who won't use >2 windows anyways), but fails for the geek-- the person who does 8 things at once, uses mainly 4-5 programs [terminal, web browser, chat [sometimes in a terminal; I use imcom often], occasional other apps]
Apple's demos make Expose look like more than it is-- they chose (intentionally or not) scenarios that make it's F7 functionality shine; but my Javadocs, vim terminal, and compile/run terminal group together better than my vim terminal, compile/run terminal, email terminal, chat terminal, network copy, mplayer terminal,...
All spelling errors are the fault of data integrity erors betweeen hear and slashdot.
---
I should also comment that you don't have to memorize 11 ctrl-keys; just click the desktop you want to switch to in the pager on your screen. Select it from a menu-extra. Or use a keystroke, of your choice.
Virtual desktops are powerful; you may not need them. They're not difficult, (like you seem to think), but use what works for you. (For me, that's using Expose inside one of 11 virtual desktops, though I rarely use more than 6 of them.)
Re:Why it wasn't put in already
on
Hacking Quartz
·
· Score: 1
This post is a reply to two other comments, foo and bar
It's true; he cannot find a window he wants with a specific event (key or mouseclick): with Expose, you need to activate it and then pick a window. Moreover, everything is shown at once, and it is difficult to locate the window in question. Terminal windows are difficult to tell apart, to top it off.
This is a task-oriented job-- each server is a task. I use virtual desktops-- [stickies, notes, etc] [chat, email,/.] [perl code I'm writing-- a few vims, a test window, a few man-pages] [something for school (though not now)-- HTML editor, Safari window, Preview of the PDF version] [[repeat last two for a while]] [DVD] etc.
I switch desktops when I switch projects; when I start working on my perl code again, I switch to it. "Arbitrary" new windows don't need to be assigned; they appear on my perl desktop; that's where I am. If I start a new project, I switch to a blank desktop, and then start working on it.
Expose can be useful for the average Mac user (not Aunt Tille, who won't use >2 windows anyways), but fails for the geek-- the person who does 8 things at once, uses mainly 4-5 programs [terminal, web browser, chat [sometimes in a terminal; I use imcom often], occasional other apps]
Apple's demos make Expose look like more than it is-- they chose (intentionally or not) scenarios that make it's F7 functionality shine; but my Javadocs, vim terminal, and compile/run terminal group together better than my vim terminal, compile/run terminal, email terminal, chat terminal, network copy, mplayer terminal,...
All spelling errors are the fault of data integrity erors betweeen hear and slashdot.
That prints "unphooey". (Yes, there are still unresolved issues having to do with visibility of @_. I'm ignoring that question for the moment. (But note that if we make @_ lexically scoped, those anonymous subroutines can act like closures... (Gee, is this sounding a little Lispish? (Never mind.)))) from perlsub(1)
Slashdot Mirror
BBN's page for quantum crypto
Batik also renders fonts improperly in some situations.
As others have said, this is ridiculous. Many people start programming when they're quite young. I was proficient in BASIC (not that it's something to brag about :-) ) when I was 7, and Java before I was 12.
Secondly, abstract is not required to understand at least some programming languages. If somebody suggested teaching them the Lambda Calculus, I'd be a bit worried, but something like C/BASIC/etc. is sufficiently procedural to make things easy. Don't confuse procedural languages with algebra just because both involve variables, because the concepts are actually very different in different languages. (I'm unsure whether Lisp/Scheme would be "too abstract" for people. I don't think functional programming would be the problem; if anything, it'd be the syntax (not the parenthesis.))
Thirdly, you divide people into "12-13" year-olds and "13-14" year olds. Leaving aside that people 13 years old fall into both classes, one year of age difference is very little basis on which to delay teaching people programming.
Finally, and most importantly, you mention that those ages are where abstract thought develops "on average". Other people in this thread who have supported you have again cited average cases. NotesSensei is not going to be teaching a school-wide programming class. NotesSensei is going to be teaching programming to people who have joined a computer club. There's a big difference there.
As for precisely what to each them, I wouldn't recommend VBScript or, therefore, KPL. I also would not recommend Java; while I think Java is a nice programming language and has many decent uses, I don't think it'd be a language that kids would like to learn as there first language. There's way too much figurative red tape to wade through to get anything done. The same probably applies to greenfoot. I would probably recommend Python.
initrd's are also useful if you want to use fancy disk formats (RAID/LVM/EVMS/etc.) Some desktop users will want to use an initrd.
The point of an initrds (now, at least) is to pull out the work of finding the root filesystem from the kernel and get it into userspace, which is much easier to maintain. Eventually, even "regular" root devices/filesystems will be mounted by an initrd, and the kernel will be that much smaller and more maintainable.
(I'm using "initrd" as a synonym for "initramfs", even though they're not actually synonymous.)
As this post's sibling has pointed out, ash, the minimalist shell component of BusyBox, is what the article's author intended to use.
/proc should work just as well.
Furthermore, the proc filesystem, like most (all?) virtual filesystems, doesn't care what the device name is. Most people use "none", for clarity, but
Random junk works well enough if you're sure (and rightly so) that you'll remember your passwords and if you're sure the service won't decide to change them. That has happened to me, and resulted in switching cell phone providers because my account with the old provider was therefore no longer accessible. (Their service left something to be desired anyway.)
Other people have hinted at this, but nobody has said it directly: Windows installations can be copied trivially (dd, cp, etc.) if the old drive is removed when the system is first booted from the new drive. If you do that, Windows will (on that first boot), readjust all its internal cruft. After that, you can reconnect the old drive, which will then appear as a non-C: drive.
Amen.
Keep in mind, however, that the sysadmin is also going to be installing all the software, and telling the higher-ups exactly how to configure encryption. To paraphrase an ancestor post: "If you don't trust your sysadmin, who do you trust?"
First post!
Nah, only weekly ones.
Is there anything particularly wrong with getting a few UNIX boxen (for redundancy) with accurate clocks and setting their times manually?
You can't upload email through POP.
I would suggest using Thunderbird to download all the mail from AOL's IMAP servers, burning a copy to CD (just in case), and then redirecting/bouncing/remailing/etc. every message to the gmail account.
I once had a Linksys BEFSR11 (1-port Cable/DSL router) with a very weird problem-- TCP connections didn't work. UDP worked fine, ICMP worked fine, but not TCP.
I tried 3 different firmware versions over a period over 2 years. By the end of it all, I was pretty sure I had a paperweight, so I called Linksys tech to confirm.
The first thing they asked me was what OS I was using. Since I had tested it with 4 different computers collectively running Windows 2000, Linux, OS X 10.2, and OS X 10.3, I told them I had tested it with multiple computers and multiple OSs. They kept asking, I finally told them OS X. The same thing happened with ISPs (I've tried our LAN, Speakeasy, and Adelphia.) I finally told them Speakeasy. It kept going on.... TCP settings, etc.
I asked to speak to their supervisor, they hung up.
I called back, and told them exactly what was wrong-- TCP connections weren't working, but other IP types were, that I had tried it with multiple computers, OSs, ISPs, etc. They started asking about my TCP settings...
I called back, and immediately asked for a supervisor. I asked her if she knew the difference between TCP and UDP. She said she did, so I told her the situation, and she agreed the box was fried.
For others reading here in the discussion, see my reply to his other comment.
For others reading here in the discussion, see my reply to his other comment.
This is the core problem in your argument. If you're planning on giving what you download to somebody else, you're redistributing it, and it is illegal. Otherwise, the copy you make when downloading is (by definition) for personal use, and thus exempt. It's in copyright law.
Don't you mean base?
All documents should be XML (or some other data discription language.) CSS's sucessor should be used to assign elements presentation. Possibly by converting them to other element trees.
The XML should be psuedo-standardized, so browsers would be able to recognize TV-Listing-ML/Search-Result-ML and present it in an alternate form, if you wanted, with headers and footers added (to make advertisers happy, unfortonately necessary for a new Web protocol to suceed.)
Ya want to know what I would have done? (Don't answer that.)
I would have used annoyed and stern tone, and told him, "Alright then. What's your name? [Write it down.]] I want to cancel my account; and I don't want to bother calling you again. I have no intention of paying anymore, so here's what you'll need to do: you'll need to write my name and account information down on a Post-it note, and when the database comes up again, put the cancelation through for me."
If he told me I needed to be on the phone, I'd say tell them (that they already have my phone number on file || what my phone number is) and to call me sometime. When [insert times I'm not likely to be sleeping.]
That'd show them!
I wrote a comment in reply to two posts, this was the second.
/.] [perl code I'm writing-- a few vims, a test window, a few man-pages] [something for school (though not now)-- HTML editor, Safari window, Preview of the PDF version] [[repeat last two for a while]] [DVD] etc.
...
The reply is in another thread, please post comments there.
The relevant text of the comment was:
This is a task-oriented job-- each server is a task. I use virtual desktops-- [stickies, notes, etc] [chat, email,
I switch desktops when I switch projects; when I start working on my perl code again, I switch to it. "Arbitrary" new windows don't need to be assigned; they appear on my perl desktop; that's where I am. If I start a new project, I switch to a blank desktop, and then start working on it.
Expose can be useful for the average Mac user (not Aunt Tille, who won't use >2 windows anyways), but fails for the geek-- the person who does 8 things at once, uses mainly 4-5 programs [terminal, web browser, chat [sometimes in a terminal; I use imcom often], occasional other apps]
Apple's demos make Expose look like more than it is-- they chose (intentionally or not) scenarios that make it's F7 functionality shine; but my Javadocs, vim terminal, and compile/run terminal group together better than my vim terminal, compile/run terminal, email terminal, chat terminal, network copy, mplayer terminal,
All spelling errors are the fault of data integrity erors betweeen hear and slashdot.
---
I should also comment that you don't have to memorize 11 ctrl-keys; just click the desktop you want to switch to in the pager on your screen. Select it from a menu-extra. Or use a keystroke, of your choice.
Virtual desktops are powerful; you may not need them. They're not difficult, (like you seem to think), but use what works for you. (For me, that's using Expose inside one of 11 virtual desktops, though I rarely use more than 6 of them.)
This post is a reply to two other comments, foo and bar
/.] [perl code I'm writing-- a few vims, a test window, a few man-pages] [something for school (though not now)-- HTML editor, Safari window, Preview of the PDF version] [[repeat last two for a while]] [DVD] etc.
...
It's true; he cannot find a window he wants with a specific event (key or mouseclick): with Expose, you need to activate it and then pick a window. Moreover, everything is shown at once, and it is difficult to locate the window in question. Terminal windows are difficult to tell apart, to top it off.
This is a task-oriented job-- each server is a task. I use virtual desktops-- [stickies, notes, etc] [chat, email,
I switch desktops when I switch projects; when I start working on my perl code again, I switch to it. "Arbitrary" new windows don't need to be assigned; they appear on my perl desktop; that's where I am. If I start a new project, I switch to a blank desktop, and then start working on it.
Expose can be useful for the average Mac user (not Aunt Tille, who won't use >2 windows anyways), but fails for the geek-- the person who does 8 things at once, uses mainly 4-5 programs [terminal, web browser, chat [sometimes in a terminal; I use imcom often], occasional other apps]
Apple's demos make Expose look like more than it is-- they chose (intentionally or not) scenarios that make it's F7 functionality shine; but my Javadocs, vim terminal, and compile/run terminal group together better than my vim terminal, compile/run terminal, email terminal, chat terminal, network copy, mplayer terminal,
All spelling errors are the fault of data integrity erors betweeen hear and slashdot.
That prints "unphooey". (Yes, there are still unresolved issues having to do with visibility of @_. I'm ignoring that question for the moment. (But note that if we make @_ lexically scoped, those anonymous subroutines can act like closures... (Gee, is this sounding a little Lispish? (Never mind.))))
from perlsub(1)
Couldn't resist.
Northrup Grumman?
Well, my start page is nil (not to be confused with about:blank). My home page, of course, is /.