They'll just instruct the ISPs to comply (meaning block any undecryptable traffic) or face mean men with guns.
Would that get us closer to Civil War? You bet.
Would that actually get us to Civil War? No, not as long as myspace, google, and facebook still work.
Port 443 would be blocked for all except online banks and those who comply with the government in other ways (think lots of logs and/or live monitoring of post-ssl traffic).
Any ISP personnel facing potential felony charges will think first of their families (as they should) and comply, at the expense of Joe Hacker.
"The reason you need that is because we don't want what happened to Unix to happen to Linux in terms of fragmentation."
What makes you think what happened to UNIX was bad? It's called evolution. Things change. If UNIX was all that, it would still be at the top of the food chain. It ain't. It couldn't perform.
Now, "UNIX The Philosophy" is alive and well, having transcended its earthly manifestation to become a mindset. It loaded itself into wetware. Pretty goo feat if you ask me.
Ultimately, let the best software win. The rest can go to bit-afterlife.
I'm gonna assume that with an id of 171285, you are no longer a teenager.
I can tell you that if you are attentive to what teenagers say, and engage them in meaningful conversation, they will often ask for advice. Then, it is important to give them frank, honest advice, backing it up with sound and logical explanations, with a story to two from experience that illustrates the advice given.
I'll take her absolutely seriously. It's a lot more important to listen to teenagers than 50 yo rambling farts. Teenagers are still discovering the world, can still be encouraged down the right path, and will impact the world a lot longer. Spending time listening to them, their fears, their ideas, their dreams, tells a lot more about the world we are going to live in than listening to someone born in 1958.
There are exceptions, of course, but generally this is my personal experience.
Disclaimer: I'm turning 40 this year, so I'm getting closer to ramblingfartness.
As a long-time wikipedia administrator (who're been fairly inactive of late because of my 3 year-old's constant request for my time--and rightly so) I readily understand the point you convey.
The other thing I think will become a problem is when Expert A writes an article on Subject X, then Expert B says, hey, Subject X is missing information Z, and Export A says no way, and Expert B can't write Subject X, but will write Subject AlmostX, and then you end up with two articles on Subject X. In wikipedia, the two articles would be merged. Knol is gonna have a big synthesis problem.
"Method or process of transferring kinetic energy gained by the rotational motion of a striking apparatus composed of a handle affixed to a mass of steel in rectangular shape thought an elliptical transverse cavity, said kinetic energy being applied to an elongated metal cylinder composed of a sharp-angled edge at one end and a flattened, thicker surface at the other hand, for the purpose of causing said metal cylinder to penetrate wood or other material. That the operator of the striking apparatus should fail to strike the elongated metal cylinder does not constitute an exception to this method or process."
That is why the developer needs to be "good", meaning:
-- Plugged in to online communities of people actively developing software. -- Able to distill the lessons learned from doing stuff and apply it to new stuff. -- Able to focus on the task at hand, relegating all the crap stuff to his manager. (That's what good managers do: take care of the crap the developer shouldn't have to) -- Able to do his own research (nothing says noob more than: "can anyone show me how to do this?") -- Able to work with text editors. We're talking web devs here. If you can't manually edit valid xhtml (and keep it valid), css, javascript, the server-side languages (there invariably end up being more than one), sql, and config / xml(bleh) files, you need to learn how to do it. -- Able to work with other coders (didn't say anyone else). It's harder than it sounds. But it's very important. -- Able to understand the fundamentals of the business.
Ultimately, being smart is important, but only coupled with an eagerness to learn new stuff, and an insatiable curiosity.
In my esperience, playing strategy games also helps. Great strategy gamers make great coders.
My wife being japanese (this pasty-white geek got an Asian chick.) I get plenty of that at home. (Not plenty of THAT, we're married after all) but plenty of Japanese-sounding words.
Slashdot Mirror
me too!
"Inform all the troops that communications have completely broken down."
They'll just instruct the ISPs to comply (meaning block any undecryptable traffic) or face mean men with guns.
Would that get us closer to Civil War? You bet.
Would that actually get us to Civil War? No, not as long as myspace, google, and facebook still work.
Port 443 would be blocked for all except online banks and those who comply with the government in other ways (think lots of logs and/or live monitoring of post-ssl traffic).
Any ISP personnel facing potential felony charges will think first of their families (as they should) and comply, at the expense of Joe Hacker.
"The reason you need that is because we don't want what happened to Unix to happen to Linux in terms of fragmentation."
What makes you think what happened to UNIX was bad? It's called evolution. Things change. If UNIX was all that, it would still be at the top of the food chain. It ain't. It couldn't perform.
Now, "UNIX The Philosophy" is alive and well, having transcended its earthly manifestation to become a mindset. It loaded itself into wetware. Pretty goo feat if you ask me.
Ultimately, let the best software win. The rest can go to bit-afterlife.
You can absolutely do that. A lot of sites do already. Just keep adhere to the lgpl and you're good.
I'm gonna assume that with an id of 171285, you are no longer a teenager.
I can tell you that if you are attentive to what teenagers say, and engage them in meaningful conversation, they will often ask for advice. Then, it is important to give them frank, honest advice, backing it up with sound and logical explanations, with a story to two from experience that illustrates the advice given.
This is what I meant by "involved guidance".
How on earth did you come to that conclusion from my post?
I recently became a parent, and I tell you, children are very smart and deserve our attentive ear and involved guidance.
I'll take her absolutely seriously. It's a lot more important to listen to teenagers than 50 yo rambling farts. Teenagers are still discovering the world, can still be encouraged down the right path, and will impact the world a lot longer. Spending time listening to them, their fears, their ideas, their dreams, tells a lot more about the world we are going to live in than listening to someone born in 1958.
There are exceptions, of course, but generally this is my personal experience.
Disclaimer: I'm turning 40 this year, so I'm getting closer to ramblingfartness.
...reinforced front bumper?
This is an Anonymous Coward. Please ignore.
As a long-time wikipedia administrator (who're been fairly inactive of late because of my 3 year-old's constant request for my time--and rightly so) I readily understand the point you convey.
The other thing I think will become a problem is when Expert A writes an article on Subject X, then Expert B says, hey, Subject X is missing information Z, and Export A says no way, and Expert B can't write Subject X, but will write Subject AlmostX, and then you end up with two articles on Subject X. In wikipedia, the two articles would be merged. Knol is gonna have a big synthesis problem.
First Post, because everybody went off to create their navel-knol.
One of the two things I said would be sad if I had to explain is that I was being facetious, that this is not a real patent.
No, that would be patent 5,987,808:
"Method or process of transferring kinetic energy gained by the rotational motion of a striking apparatus composed of a handle affixed to a mass of steel in rectangular shape thought an elliptical transverse cavity, said kinetic energy being applied to an elongated metal cylinder composed of a sharp-angled edge at one end and a flattened, thicker surface at the other hand, for the purpose of causing said metal cylinder to penetrate wood or other material. That the operator of the striking apparatus should fail to strike the elongated metal cylinder does not constitute an exception to this method or process."
Note: It would be sad if I had to explain twice.
Ah, I see. Ok.
I'm still not.
Reading body language is also really hard to do over the phone. You can get voice tone though.
If it's something important, meet face to face.
I'm not.
My troll was better than your troll.
Would someone be kind enough to rewrite the post in English?
That is why the developer needs to be "good", meaning:
-- Plugged in to online communities of people actively developing software.
-- Able to distill the lessons learned from doing stuff and apply it to new stuff.
-- Able to focus on the task at hand, relegating all the crap stuff to his manager. (That's what good managers do: take care of the crap the developer shouldn't have to)
-- Able to do his own research (nothing says noob more than: "can anyone show me how to do this?")
-- Able to work with text editors. We're talking web devs here. If you can't manually edit valid xhtml (and keep it valid), css, javascript, the server-side languages (there invariably end up being more than one), sql, and config / xml(bleh) files, you need to learn how to do it.
-- Able to work with other coders (didn't say anyone else). It's harder than it sounds. But it's very important.
-- Able to understand the fundamentals of the business.
Ultimately, being smart is important, but only coupled with an eagerness to learn new stuff, and an insatiable curiosity.
In my esperience, playing strategy games also helps. Great strategy gamers make great coders.
My wife being japanese (this pasty-white geek got an Asian chick.) I get plenty of that at home. (Not plenty of THAT, we're married after all) but plenty of Japanese-sounding words.
SourceForge, Inc. is a Japanese company? Who knew?
Don't.
To get Ruby on Rails "Just Right" requires a seasoned developer.
Same goes for javascript... And Python too.
Wait a minute. Wasn't this the point?
You can't just "pick up" something and be good at it instamagically.
Remember the lack of Silver Bullets when facing the blood-suckers in management.
Are you a Senior Agricultural Product Collection/Extraction Specialist too?