That's not striking back. That's further incriminating oneself. It's a common reaction under suspicion: talk more. Even a first year law student, would Mr. Wise have been smart enough to have one standing beside him, would be advising his client to "shut up shut up SHUT UP!"
Fortunately for J Spence, Mr. Wise does not, in fact, appear to have been smart enough to engage counsel. This is all evidence quite favorable for the plaintiff. It's now cached on hard drives all over the world.
Please to note: 1) I am well aware of the difference between industrial hemp and ganja. 2) I am in favor of marijuana legalization. 3) I am an atheist.
I think it should be legal just because I like getting high.
If they had a clue, they would grow 10000 acres of canabis which;
A) grows 10000x faster than trees B) makes 10x more pulp per acre C) uses 100x less water. D) stick it to the govt.
I think you forgot your "...profit" clause, except here it would say D) Use a bunch of arguments of dubious value to misdirect attention from the fact that what you really want is to get stoned ...Profit!
See, I always thought that same thing! Then I started working in a large corporation. Now I understand what being brutally honest in a place like, say, Bosnia must have been like.
I got out. If you're smart and just keep your lips shut, maybe you will too.
What's wrong with taking a 4x4 shopping? I have successfully migrated my various family members in far-flung states to Firefox, people who call IE "the Internet." Either install it during a visit, or, if need be, talk them through it over the phone. If they don't want extra features, they don't have to use them. Once they're comfortable, though, casually suggest they try, say, tabs. Then eventually they're installing their own extensions! If they're not part of the solution, you know, their part of our problem. So you have to do a little free tech support. Big deal. Consider the opportunity here to create a user base for open source software in the general public. This is beautiful opportunity to wow them with better software. Don't squander it.
I ran across a used copy of this book in The Strand and have to say it has taken its place next to The Cookbook on the shelf of Truly Useful Books. All the "advanced" php books I had found before this one either had a three or four page spread on objects and classes or (in the case of one awful Wrox book) scads of code with little useful description of the considerations that went into its architecture. If you're coming to php from a non-coding background, you'll find that most books seem to stop just before the discussion gets truly interesting (and useful). No, I don't already know how to make use of inheritance, and telling me that it involves extending a class without describing why I would want to do that and how to design classes so it can be done intelligently and powerfully is pretty useless.
This book deals with those advanced topics in substantial depth. Want to know what strategies should be considered in deciding how far to abstract database classes? Want an in depth discussion of preformance caching? Care to contemplate the values of various distributed architectures? Interested in Zend engine internals? From coding style clear through application benchmarking, this book covers it, and it covers it thoroughly and engagingly.
Oh, great. Now it's not enough to look down on Windows users. We have to have Linux users and Linux "desktop users," whatever those are. We know this, though: they're not as savvy as us real Linux users.
That looked tiring. And wasn't it annoying that in the midst of all that, they had to move the data over from the ball machine to the screen on those lucite "floppies?" Forget wifi, in the future, they don't even have ethernet anymore.
What I want to know is: What do you have against toys? Scared by a clown as a child?
Even on the big, bad interweb, sometimes one doesn't feel like writing "production" "code." Sometimes one may just want to make amusing and useful applications that need to manage fair amounts of data. And then one might want to share them with others.
Sheesh. People here can get so serious about computers. Coding is such a manly art!
So first he doesn't get specific enough, but then he gets too specific? Solly, Cholly, but you're going to have to make up your mind what exactly it is you want!
I dunno, it really seems the industry is neither served nor effectively critiqued yet in this medum. The "fun," informative shows weren't either and the "incisive" was a few weeks late and a shade dumbed down. I can't bear the thought of just, like, watching it. Did anyone here really do that?
Nevertheless, I'll feel a bit sad if it's gone. Well, just a tiny bit. It wasn't hurting anyone, after all.
Why settle for second best?
on
Core CSS (2nd ed.)
·
· Score: 3, Informative
I haven't read this CSS book, but I've read a few, and the best ones always seem to have the same author. I can't imagine how one could be more clear and complete than Eric Meyer's Definitive Guide. He's also published a useful reference to CSS 2.0.
And it won't look the least bit suspicious when the host is connected to several other hosts, transferring encrypted data at full-speed 24 hours a day.
No, it won't, as long as everything else is encrypted. I used to make this argument regarding email, when asked why I insisted on encrypting everything. Granted, I send more unencrypted mail nowadays, having given up to some extent. But I use more and more encrypted http connections. It's not overoptimistic to think that https might become the norm. Nor is it technically such a big hurdle.
Slashdot Mirror
That's not striking back. That's further incriminating oneself. It's a common reaction under suspicion: talk more. Even a first year law student, would Mr. Wise have been smart enough to have one standing beside him, would be advising his client to "shut up shut up SHUT UP!"
Fortunately for J Spence, Mr. Wise does not, in fact, appear to have been smart enough to engage counsel. This is all evidence quite favorable for the plaintiff. It's now cached on hard drives all over the world.
What an idiot.
He can't charge for any binary that incorporates GPL source without making the source available. I thought that was obvious.
I'm glad I just downloaded the latest on Saturday! Always a minute late and a nickel shy...until now, motherfuckers!
In your face, um,... enigmatic forces who've been keeping me down.
Now as long as they don't hack any new functionality in, I'll be sittin' pretty.
Please to note:
1) I am well aware of the difference between industrial hemp and ganja.
2) I am in favor of marijuana legalization.
3) I am an atheist.
I think it should be legal just because I like getting high.
I stand by my sneer.
If they had a clue, they would grow 10000 acres of canabis which;
...Profit!
A) grows 10000x faster than trees
B) makes 10x more pulp per acre
C) uses 100x less water.
D) stick it to the govt.
I think you forgot your "...profit" clause, except here it would say
D) Use a bunch of arguments of dubious value to misdirect attention from the fact that what you really want is to get stoned
See, I always thought that same thing! Then I started working in a large corporation. Now I understand what being brutally honest in a place like, say, Bosnia must have been like.
I got out. If you're smart and just keep your lips shut, maybe you will too.
What's wrong with taking a 4x4 shopping? I have successfully migrated my various family members in far-flung states to Firefox, people who call IE "the Internet." Either install it during a visit, or, if need be, talk them through it over the phone. If they don't want extra features, they don't have to use them. Once they're comfortable, though, casually suggest they try, say, tabs. Then eventually they're installing their own extensions! If they're not part of the solution, you know, their part of our problem. So you have to do a little free tech support. Big deal. Consider the opportunity here to create a user base for open source software in the general public. This is beautiful opportunity to wow them with better software. Don't squander it.
This is true even with 1.4. I was really astounded by this software. You're right; it appears native.
I ran across a used copy of this book in The Strand and have to say it has taken its place next to The Cookbook on the shelf of Truly Useful Books. All the "advanced" php books I had found before this one either had a three or four page spread on objects and classes or (in the case of one awful Wrox book) scads of code with little useful description of the considerations that went into its architecture. If you're coming to php from a non-coding background, you'll find that most books seem to stop just before the discussion gets truly interesting (and useful). No, I don't already know how to make use of inheritance, and telling me that it involves extending a class without describing why I would want to do that and how to design classes so it can be done intelligently and powerfully is pretty useless.
This book deals with those advanced topics in substantial depth. Want to know what strategies should be considered in deciding how far to abstract database classes? Want an in depth discussion of preformance caching? Care to contemplate the values of various distributed architectures? Interested in Zend engine internals? From coding style clear through application benchmarking, this book covers it, and it covers it thoroughly and engagingly.
Oh, ok.
Sorry.
Oh, great. Now it's not enough to look down on Windows users. We have to have Linux users and Linux "desktop users," whatever those are. We know this, though: they're not as savvy as us real Linux users.
Sheesh!
OK, try this: open that same page in firefox and konqueror at the same time and I think you'll see there's a substantial ...
Oh, wait.
Never mind.
Did I mention I love firefox?
That looked tiring. And wasn't it annoying that in the midst of all that, they had to move the data over from the ball machine to the screen on those lucite "floppies?" Forget wifi, in the future, they don't even have ethernet anymore.
What I want to know is: What do you have against toys? Scared by a clown as a child?
Even on the big, bad interweb, sometimes one doesn't feel like writing "production" "code." Sometimes one may just want to make amusing and useful applications that need to manage fair amounts of data. And then one might want to share them with others.
Sheesh. People here can get so serious about computers. Coding is such a manly art!
The alpaca (Lama pacos) is featured on the front of the rather new (2003) O'Reilly book, Learning Perl Objects, References & Modules .
"The woman I was just talking to told me my password started with an 'X' as in 'Zebra'. What should I type?"
...as in Xerox."
"You should type 'Z'
People replying to my sig annoy me. That's why I change it all the time.
May I suggest a more effective method?
So first he doesn't get specific enough, but then he gets too specific? Solly, Cholly, but you're going to have to make up your mind what exactly it is you want!
I dunno, it really seems the industry is neither served nor effectively critiqued yet in this medum. The "fun," informative shows weren't either and the "incisive" was a few weeks late and a shade dumbed down. I can't bear the thought of just, like, watching it. Did anyone here really do that?
Nevertheless, I'll feel a bit sad if it's gone. Well, just a tiny bit. It wasn't hurting anyone, after all.
I haven't read this CSS book, but I've read a few, and the best ones always seem to have the same author. I can't imagine how one could be more clear and complete than Eric Meyer's Definitive Guide. He's also published a useful reference to CSS 2.0.
flying mongoose
What is that, some kind of web browser?
You, sir, have hit the nail on the head.
I couldn't put my fingers on exactly what it was that was missing!
And it won't look the least bit suspicious when the host is connected to several other hosts, transferring encrypted data at full-speed 24 hours a day.
No, it won't, as long as everything else is encrypted. I used to make this argument regarding email, when asked why I insisted on encrypting everything. Granted, I send more unencrypted mail nowadays, having given up to some extent. But I use more and more encrypted http connections. It's not overoptimistic to think that https might become the norm. Nor is it technically such a big hurdle.