You're only partially right. Axioms are statements that (1) can't be proven, and (2) you assume are true, and everything is built upon them. However, there are other, non-axiomatic, statements in any formal system that cannot be proven either true or false. That's what the parent was talking about (hence the mention of the Godel's incompleteness theorem). BTW, if you're a CS major, you've encountered this in the form of the Halting Problem:)
While people would figure out what you mean, I think what you wrote is not entirely correct: you should have used quotes. E.g.:
Is "fruit" an adjective or a noun?
(of course, you could argue that I, in turn, should've quoted the whole sentence itself... But I'm at an English keyboard that doesn't have proper open-quotes and closed-quotes, so I didn't bother)
Anyway, I'm not sure what the English grammar says about requiring quotes in cases like this, but I'm pretty sure my native grammar (Russian) would require them.
Well, sticking with your analogy--your drill isn't as likely to get compromised and start drilling holes in other people's walls; Windows is (granted, they're saying the security updates will be treated differently, but I'm not sure this will last forever). Secondly, if your cheap knock-off drill has a defect, this defect was almost certainly introduced by the knock-off maker. Not so for Windows--your copy is identicaly to mine and everyone else's, so the said defect was there from the get-go.
You know, the best part was, I've never seen a bash forkbomb before, and stupidly decided to give this a try:-P (I had no idea that ":" was a valid bash command, and so figured that maybe it'll come up with a particularly amusing error message... was I ever wrong:)))
Because some places require you to write comments (even when they are really not necessary) and enforce it with a style checker. One way to shut up the said checker is to generate comments of this sort. Sad, but true:)
Technically, the idea is not new -- Rene Magritte has a series of paintings of this sort. One, for instance, depicts an easel standing in front of a window. The painting on the easel is "transparent" in exactly the same sense. For those who are interested, search for "The Human Condition" (or something like "Le Condition Humaine", if you pardon my French:)
I'm not sure this is entirely accurate. When I immigrated to the US, I lived in New York City which also has a completely swamped INS branch. But when I applied for citizenship, I dealt with the branch that was close to my university--which was in a different part of the state--and as a result went through the process in a much shorter period of time than my parents (who got theirs earlier in NY). Note that in both cases the INS branches were in the same state, but in different cities. The difference in efficiency was striking (probably due to a much lower volume of work in the area of my university).
I heard this recently with regards to a different film, but it seems so fitting that I hope you forgive a little adaptation:
Two sheep are standing outside of a movie theatre, munching on a VHS tape of The Hitchiker's Guide. Sheep 1: "Hmmm... tastes pretty good!" Sheep 2(dismissively): "Nah, I liked the book better."
Actually, just remembered a few excellent sites, 1. http://www.geocities.com/mike_mccracker/ "Dansm's Guitar page". This used to live at a couple of different addresses before, but looks like this is the current link. Lots of useful infom especially if you are starting out. 2. http://www.wholenote.com/ check out the "lessons" link. This has lessons on all kinds of sunjects, for all levels.
If you're just starting, most web/computer tools won't be of too much help for a while (IMHO). Instead, try to get a friend to show you some chords/tunes, as well as the basic layout of the guitar. If you are even moderately serious about learning, getting a good teacher will help a lot too. I'd also suggest hanging out in alt.guitar.beginner, it's a pretty nice newsgroup where lots of questions can be answered. Also, from what I've seen, the "guitar for dummies" book is actually quite good and will get you through the basics in a sane order.
After you get acquainted with the instrument a bit, check out www.olga.net, a sizeable archive of guitar tablatures (assuming you don't mind learning to read tab -- it's easy, though it's not a substitute for real music notation in the long run).
One program I'd suggest (non-free, unfortunately) is Guitar Pro. It's a tablature editor that can play the tablature, and there are quite a few tunes available in its format--so you can see the tab and hear the tune played. Pretty nice if you use tabs.
The parent is not quite as insightful as people apparently think. Consider the fact that the distances one typically covers in the States are quite a bit greater than almost anywhere in Europe or the UK. Most areas are not that densely populated, and thus do not have many -- or frequently serviced -- transportation options. As a result of this, public transport is not nearly as well-developed or as efficient as the equivalents in other countries. It's not terribly convenient to use public transport to go anywhere unless you can stay within city limits all the time. That happens to be much less feasible in the states than in Europe.
Here're a couple of examples to illustrate my points.
1. I have to commute about 12 miles (~19km) to work every day. Time by bus+subway+bus: 1 hour Time by car: 20-40 minutes, depending on traffic. Multiply by 2 (commute back home) -- the difference is between 40 and 80 minutes per day, an hour on average.
2. I have to drive about 220 miles (~350km) to see my parents who live in another city every month. Time by public transportation: bus + subway+intercity bus+subway = 10 min + 20 min + 4 hrs + 1 hr = 5.5 hours. By car, the trip takes 4 hours door-to-door.
Again, multiply by 2 for the way back, and we have about a 3 hour difference. Seeing as I typically go late Friday night or early Sat. morning, and come back on Sunday, 3 additional hours of time that I can spend with my family makes quite a difference. So does not having to be aggravated by crappy buses;)
I hope this somewhat illustrates my point. And just to make things clear, I'm not talking about some tiny towns in the middle of nowhere--the above trips concern Boston and New York.
Gee, and nobody even complained at the red flag waved in their face--that the sole reference listed in the article is "Understanding IPv6" by Microsoft Press:-P
Could slashdot readership have become more mature? Though if I had to guess, I'd say anyone has yet to RTFA:) (by Occam's Razor:)))
well, the difference here is type safety. e.g., the compiler ensures that the "begin" and "end" are of the same type (I), and that when something of type I ("it", in the example in the post) is dereferenced, you get something of type V.
with void*, you are on your own, and if you pass incorrect pointers to your function, you won't find out until the program crashes or produces very strange data.
e.g., let's say you have an array of doubles called a, and an array of chars called z. and you'd like to find the value 3.14 in the former. In your code you make a typo that looks something like this: int index = find( a, z+length_of_a, 3.14)
with the generic find function, the compiler will catch the error (the find might have to be written out as find). if find were written using void *'s instead, you'd not know anything was wrong at runtime.
>because simply put, they control most of the >recognizable music in the world. It's RIAA, not RIAW... There's plenty of music being made outside of the states, and I doubt RIAA controls every import. Though who knows...
I wonder if it is possible to somehow make music with Silbo Gomero. I assume regular whistling-along would become impossible or at least more difficult--but then again, people speaking pitch-based langugages can sing, so maybe it's possible with Silbo as well:)
That said, I wish they had more details about the language in the article... Though here's what I found so far: Wikipedia entry, and another link mentioned there.
My apologies:) I actually considered writing it the correct way, then thought it looked wrong, and lo and behold, made the mistake.
I guess that's what I get for not having read a word of Spanish for 6-7 years. But I have 'El Hobbit' awaiting its turn on my bookshelf. Maybe if this winter turns out really cold...:)
I was very surprised at what I heard when I opened the trailer--the song that goes through the whole thing is set to the melody of Joaquin Rodrigo's 'Concierto del Aranguez', one of the very few classical concertos for guitar. Interesting to hear the piece arranged for voice and hand drums:)
See, the problem with the 'approve' scheme (at least the simple, naive version that comes to mind) is that instead of being flooded with annoying messages you will get flooded with no-less-annoying and no-less-intrusive requests for approval/authorization, still creating a DOS-like situation due to the low SNR...
I've always found that I was much more motivated to do the work, and learned more from the process, if I had the ability to work with someone else--whether the policy allowed it or not.
Working alone is prone to getting stuck at one place and not being able to move on, whereas when you work with a partner (or partners), there's a potential for a different perspective, which almost always helps. I found that I learned a lot simply from hearing a different take on the problem (usually, after getting stuck in solving it:) as opposed to spending hours agonyzing over a stumbling point and possibly not really advancing from it, thus learning very little from the assignment. Furthermore, many people learn a lot by just discussing the problem, as it forces them to think along paths their brains would not take if they were left to themselves; many things fall into their place and sink in much better in this fashion (for example, how many of you have come up with an answer to a tough question while explaining your question to a friend?). And let's be realistic, in the real world, many things are done collaboratively and are beyond any single person.
A number of my CS classes at Cornell had a very simple policy, which has worked remarkably well (and I've seen this both as a student and a TA). The policy was, roughly:
1. You are allowed to discuss the problem with others
2. You have to give credit to the people you discussed the problem with (write down their names on your assignment)
3. Everyone has to do their own writeup
This policy had the benefits of letting people bounce ideas off of each other, to learn from others, to pick up things they wouldn't otherwise pick up. At the same time, requiring everyone to do their own writeup ensured that the people understood the solutions well enough to be able to formulate them well on paper--not an easy task if you're just trying to blindly copy parts of a solution without understanding it.
What I saw with that policy in place was that people tended to form stable study groups, the overall results were pretty good (yet sometimes people in the same study group might have rather different explanations of the same things!), and also, in the rare cases of cheating, the cheating was relatively obvious and easy to spot.
Slashdot Mirror
You're only partially right. Axioms are statements that (1) can't be proven, and (2) you assume are true, and everything is built upon them. However, there are other, non-axiomatic, statements in any formal system that cannot be proven either true or false. That's what the parent was talking about (hence the mention of the Godel's incompleteness theorem). :)
BTW, if you're a CS major, you've encountered this in the form of the Halting Problem
While people would figure out what you mean, I think what you wrote is not entirely correct: you should have used quotes. E.g.:
Is "fruit" an adjective or a noun?
(of course, you could argue that I, in turn, should've quoted the whole sentence itself... But I'm at an English keyboard that doesn't have proper open-quotes and closed-quotes, so I didn't bother)
Anyway, I'm not sure what the English grammar says about requiring quotes in cases like this, but I'm pretty sure my native grammar (Russian) would require them.
... while providing the same level of security ...
:)
as IE??? That's how I read it at first
Well, sticking with your analogy--your drill isn't as likely to get compromised and start drilling holes in other people's walls; Windows is (granted, they're saying the security updates will be treated differently, but I'm not sure this will last forever).
Secondly, if your cheap knock-off drill has a defect, this defect was almost certainly introduced by the knock-off maker. Not so for Windows--your copy is identicaly to mine and everyone else's, so the said defect was there from the get-go.
You youngsters never learn your place, do you?
You know, the best part was, I've never seen a bash forkbomb before, and stupidly decided to give this a try :-P :)))
(I had no idea that ":" was a valid bash command, and so figured that maybe it'll come up with a particularly amusing error message... was I ever wrong
Because some places require you to write comments (even when they are really not necessary) and enforce it with a style checker. :)
One way to shut up the said checker is to generate comments of this sort. Sad, but true
Technically, the idea is not new -- Rene Magritte has a series of paintings of this sort. One, for instance, depicts an easel standing in front of a window. The painting on the easel is "transparent" in exactly the same sense. :)
For those who are interested, search for "The Human Condition" (or something like "Le Condition Humaine", if you pardon my French
I'm not sure this is entirely accurate. When I immigrated to the US, I lived in New York City which also has a completely swamped INS branch. But when I applied for citizenship, I dealt with the branch that was close to my university--which was in a different part of the state--and as a result went through the process in a much shorter period of time than my parents (who got theirs earlier in NY). Note that in both cases the INS branches were in the same state, but in different cities. The difference in efficiency was striking (probably due to a much lower volume of work in the area of my university).
Two sheep are standing outside of a movie theatre,
:)
munching on a VHS tape of The Hitchiker's Guide.
Sheep 1: "Hmmm... tastes pretty good!"
Sheep 2 (dismissively): "Nah, I liked the book better."
Actually, just remembered a few excellent sites,s Guitar page". This used to live at a couple of different addresses before, but looks like this is the current link. Lots of useful infom especially if you are starting out.
1. http://www.geocities.com/mike_mccracker/
"Dansm'
2. http://www.wholenote.com/
check out the "lessons" link. This has lessons on all kinds of sunjects, for all levels.
If you're just starting, most web/computer tools won't be of too much help for a while (IMHO). Instead, try to get a friend to show you some chords/tunes, as well as the basic layout of the guitar. If you are even moderately serious about learning, getting a good teacher will help a lot too. I'd also suggest hanging out in alt.guitar.beginner, it's a pretty nice newsgroup where lots of questions can be answered. Also, from what I've seen, the "guitar for dummies" book is actually quite good and will get you through the basics in a sane order.
:)
After you get acquainted with the instrument a bit, check out www.olga.net, a sizeable archive of guitar tablatures (assuming you don't mind learning to read tab -- it's easy, though it's not a substitute for real music notation in the long run).
One program I'd suggest (non-free, unfortunately) is Guitar Pro. It's a tablature editor that can play the tablature, and there are quite a few tunes available in its format--so you can see the tab and hear the tune played. Pretty nice if you use tabs.
HTH
The parent is not quite as insightful as people apparently think.
;)
Consider the fact that the distances one typically covers in the States are quite a bit greater than almost anywhere in Europe or the UK. Most areas are not that densely populated, and thus do not have many -- or frequently serviced -- transportation options. As a result of this, public transport is not nearly as well-developed or as efficient as the equivalents in other countries. It's not terribly convenient to use public transport to go anywhere unless you can stay within city limits all the time. That happens to be much less feasible in the states than in Europe.
Here're a couple of examples to illustrate my points.
1. I have to commute about 12 miles (~19km) to work every day. Time by bus+subway+bus: 1 hour
Time by car: 20-40 minutes, depending on traffic.
Multiply by 2 (commute back home) -- the difference is between 40 and 80 minutes per day, an hour on average.
2. I have to drive about 220 miles (~350km) to see my parents who live in another city every month.
Time by public transportation:
bus + subway+intercity bus+subway = 10 min + 20 min + 4 hrs + 1 hr = 5.5 hours.
By car, the trip takes 4 hours door-to-door.
Again, multiply by 2 for the way back, and we have about a 3 hour difference. Seeing as I typically go late Friday night or early Sat. morning, and come back on Sunday, 3 additional hours of time that I can spend with my family makes quite a difference. So does not having to be aggravated by crappy buses
I hope this somewhat illustrates my point. And just to make things clear, I'm not talking about some tiny towns in the middle of nowhere--the above trips concern Boston and New York.
GTK? Qt? Motif? :-P
Talk about a code monkey...
Er, that would be Star Office.
I think their powerpoint equivalent is called Impress, so that's the "i" in "sxi"
Gee, and nobody even complained at the red flag waved in their face--that the sole reference listed in the article is "Understanding IPv6" by Microsoft Press :-P
:) (by Occam's Razor :)))
Could slashdot readership have become more mature?
Though if I had to guess, I'd say anyone has yet to RTFA
Here on Slashdot, we can't even get to 3 properly:
;)
1. Write a witty post
2. ???
3. Profit!!!
well, the difference here is type safety.
:)
e.g., the compiler ensures that the "begin" and "end" are of the same type (I), and that when something of type I ("it", in the example in the post) is dereferenced, you get something of type V.
with void*, you are on your own, and if you pass incorrect pointers to your function, you won't find out until the program crashes or produces very strange data.
e.g., let's say you have an array of doubles called a, and an array of chars called z. and you'd like to find the value 3.14 in the former.
In your code you make a typo that looks something like this:
int index = find( a, z+length_of_a, 3.14)
with the generic find function, the compiler will catch the error (the find might have to be written out as find).
if find were written using void *'s instead, you'd not know anything was wrong at runtime.
HTH
>because simply put, they control most of the
:)
>recognizable music in the world.
It's RIAA, not RIAW... There's plenty of music being made outside of the states, and I doubt RIAA controls every import. Though who knows...
just nitpicking
polar regions ;)
I wonder if it is possible to somehow make music with Silbo Gomero. I assume regular whistling-along would become impossible or at least more difficult--but then again, people speaking pitch-based langugages can sing, so maybe it's possible with Silbo as well :)
That said, I wish they had more details about the language in the article... Though here's what I found so far:
Wikipedia entry, and another link mentioned there.
My apologies :) I actually considered writing it the correct way, then thought it looked wrong, and lo and behold, made the mistake.
:)
I guess that's what I get for not having read a word of Spanish for 6-7 years. But I have 'El Hobbit' awaiting its turn on my bookshelf. Maybe if this winter turns out really cold...
I was very surprised at what I heard when I opened the trailer--the song that goes through the whole thing is set to the melody of Joaquin Rodrigo's 'Concierto del Aranguez', one of the very few classical concertos for guitar. Interesting to hear the piece arranged for voice and hand drums :)
See, the problem with the 'approve' scheme (at least the simple, naive version that comes to mind) is that instead of being flooded with annoying messages you will get flooded with no-less-annoying and no-less-intrusive requests for approval/authorization, still creating a DOS-like situation due to the low SNR...
So that won't necessarily ease the problem.
I've always found that I was much more motivated to do the work, and learned more from the process, if I had the ability to work with someone else--whether the policy allowed it or not.
Working alone is prone to getting stuck at one place and not being able to move on, whereas when you work with a partner (or partners), there's a potential for a different perspective, which almost always helps. I found that I learned a lot simply from hearing a different take on the problem (usually, after getting stuck in solving it :) as opposed to spending hours agonyzing over a stumbling point and possibly not really advancing from it, thus learning very little from the assignment. Furthermore, many people learn a lot by just discussing the problem, as it forces them to think along paths their brains would not take if they were left to themselves; many things fall into their place and sink in much better in this fashion (for example, how many of you have come up with an answer to a tough question while explaining your question to a friend?). And let's be realistic, in the real world, many things are done collaboratively and are beyond any single person.
A number of my CS classes at Cornell had a very simple policy, which has worked remarkably well (and I've seen this both as a student and a TA). The policy was, roughly:
1. You are allowed to discuss the problem with others
2. You have to give credit to the people you discussed the problem with (write down their names on your assignment)
3. Everyone has to do their own writeup
This policy had the benefits of letting people bounce ideas off of each other, to learn from others, to pick up things they wouldn't otherwise pick up. At the same time, requiring everyone to do their own writeup ensured that the people understood the solutions well enough to be able to formulate them well on paper--not an easy task if you're just trying to blindly copy parts of a solution without understanding it.
What I saw with that policy in place was that people tended to form stable study groups, the overall results were pretty good (yet sometimes people in the same study group might have rather different explanations of the same things!), and also, in the rare cases of cheating, the cheating was relatively obvious and easy to spot.