Well, on the other hand, if they're supposed to be air-tight, I guess they're baby oil-tight, too.
But there's got to be something or another that doesn't react well with mineral oil, right?
I guess this means they save on fans, and the power to run fans. That's additional power and heat savings right there.
OK, I've got it: what about the CD/DVD drives? Or is it all network IPL in data centers? I'm racking my brains trying to think of something this would mess up.
Thanks for restating something I've been saying for a long time: If the Internet is a series of tubes, well, then, let it be a series of tubes already!
Build the tubes, then let private carriers (AT&T, Joe Bob Internet, etc.) pull their wires through.
No monopoly, and also no ugly wires on telephone poles that get homeowners' associations angry.
Why is that language designers feel they must come up with gratuitous differences to differentiate their babies?
I'm talking about where keywords are used in the same (or much the same) way, but they've come up with something different after spending some time with a thesaurus:
E.g., instead of Java "implements" for interfaces, you get "satisfies".
But contracts don't get invalidated even if they were totally electronic. It's like this: some people use pen/paper or typewriters to write works of fiction. And others to write business correspondence. The latter isn't invalidated because of the former.
Similarly, just because some people use email to shoot the breeze does not mean e-mail correspondence is invalid before the courts. That's the law since 2000 (ESIGN Act).
If you make an offer to someone (create a logo for me for $500), and he accepts, and creates the logo, you are obligated to pay $500. You made an offer, there was a back-and-forth (on email), and there was an agreement to exchange value (consideration). That's a contract.
FYI, Facebook has not been so stupid as to deny the contract. Last I read, they were going to take the tack that it doesn't mean what other people say it means.
ESIGN was passed to ensure that contracts or signatures "may not be denied legal effect, validity, or enforceability solely because it is in electronic form".
Note that UETA makes a distinction between electronic signatures vs. secure electronic signatures. But that doesn't mean the former is invalid.
I mention all this just so you (or anybody else) doesn't make business promises in email, and then think you can wave it off because "it's just e-mail".
In any case, the contract in this case wasn't electronic at all: It's a pen-and-paper signed contract with normal legal verbiage.
Plenty of people have been reading Slashdot for longer than the time when they were motivated to create an account. Hats off to your foresight to create an account early.
The thing with the confusion about equality vs. assignment operator is a valid concern, but the:= operator doesn't really appeal to me (initially).
Because the bugs associated with mistakenly using = vs. ==, I always put the constant value being compared on the left. That, of course, can't be assigned to, and the compiler will catch your error if you use =.
if (SOME_FLAG = this.x)//compiler flags this if (SOME_FLAG == this.x)
Same goes for other languages with this syntax (PHP, Javascript, C/C++).
Speaking of greed, the way that Zuckerberg is reputed to have treated Eduardo, his partner, and the one who put up all the initial investment money for Facebook is worse than the situation with the W twins.
He is reputed to have taken Eduardo's 30-some percent share down to 0 or so by issuing new stock to venture capitalists while keeping his and Sean Parker's percentages stable.
One phrase for dealing with startups: "non-dilutable shares"
>Benefits that an employee receives are given a value and will be taxed if they exceed certain numbers that are relative to all employees.
An interesting question is: what determines what benefits are "allowed"?
If the IRS had its way, giving free water to employees would be taxed, too (at maybe the rate for bottled water).
Before the rise of MS and Silicon Valley companies, businesses didn't give their employees free food & drink, pool tables, laundries, entertainment centers, daycare, petcare, and so forth.
So if some companies are giving all that stuff away, and some companies aren't (old-style corps), are "all employees" receiving the benefit so that it can be given taxfree?
in letting James "Father of Java" Gosling go to Google.
In a case where the judge is learning about Java, and where testimony may be taken on the history of Java, it can't help to have its creator on the other side.
For people who have worked with NoSQL (assuming you've worked extensively with SQL before):
1. For someone wanting to either scratch an itch, or come up with the Next Great Thing, would you recommend NoSQL-type solutions to do the standard save data coming in over the web, and later retrieve it, possibly rejigger and summarize it, and feed it back over the web when a user needs it thing?
2. Is NoSQL generally considered faster than SQL equivalents? At runtime or development time?
3. Is there a concept of DB design? Or is it just made up as you go? By doing additional.insert()'s?
I.e., you start off by.create(product). Then add fields:.addAttribute('name', 'Magic Rock').addAttribute('manuf', 'Rock Emporium')
Then you add in detail for the manufacturer table:.addAttribute('name', 'Rock Emporium').addAttribute('st', '123 Main St').addAttribute('state', 'NY')
Is that how it works?
4. And can you change field names later (ALTER TABLE)?
5. What about aggregate functions (MAX, GROUP BY, HAVING)?
I'm thinking about wading into the noSQL waters. Help me out:
If authors aren't normalized, does that basically mean you don't have a separate datastore (table, whatever) for authors? E.g., a publisher might want to keep track of author name, address, etc.
Here's another classic example: country codes vs. country names: (ca, Canada), (us, United States).
If you want to be able to use both, you'd would (classicly) store "ca" in your User table (for what country he lives in), and then have a separate Countries table that tells you what "ca" stands for.
How do you approach that in NoSQL (assuming you want to make use of both codes and full country names)?
Could I pick your brain since you have a bit of NoSQL experience?
How does indexing work in NoSQL? Are there EXPLAIN-type tools available? (EXPLAIN in MySQL tells you whether your query is using indexes or table scans, and can help you understand why your query is slow.)
I'm pretty flexible with SQL. Can you do just about any query you could with SQL? ("Find all customers who have bought at least $100 of stuff over the last year, but who haven't bought anything this year.")
One thing that annoys me is the disjunction between UPDATE and INSERT queries for the same set of fields:
INSERT INTO blah(uid, name, email) VALUES(12,'Goober','goob@example.com')
But if you want to change that to an UPDATE query, you have to move each of the fields around: UPDATE blah SET uid=12, name='Goober', email='goob@example.com'
This would have been better: UPDATE blah SET (uid, name, email) VALUES(12,'Goober','goob@example.com')
By the way, if you want to read hard-core fundamentalist, pro-relational stuff by DB guru CJ Date and others, DBDebunk is the place:
Slashdot Mirror
Backed by "what's a foreign key?"/"you don't need no steenkin ACID" MySQL and PHP, no less.
Well, on the other hand, if they're supposed to be air-tight, I guess they're baby oil-tight, too.
But there's got to be something or another that doesn't react well with mineral oil, right?
I guess this means they save on fans, and the power to run fans. That's additional power and heat savings right there.
OK, I've got it: what about the CD/DVD drives? Or is it all network IPL in data centers? I'm racking my brains trying to think of something this would mess up.
I can't believe governments are stupid enough to "sell" spectrum. Lease it instead, and keep leaseholders on a leash.
Thanks for restating something I've been saying for a long time: If the Internet is a series of tubes, well, then, let it be a series of tubes already!
Build the tubes, then let private carriers (AT&T, Joe Bob Internet, etc.) pull their wires through.
No monopoly, and also no ugly wires on telephone poles that get homeowners' associations angry.
Why is that language designers feel they must come up with gratuitous differences to differentiate their babies?
I'm talking about where keywords are used in the same (or much the same) way, but they've come up with something different after spending some time with a thesaurus:
E.g., instead of Java "implements" for interfaces, you get "satisfies".
abstract is replaced by "formal"
"actual" means "override"?
"public" -> "shared" : what's the value-add?
"var" -> "local" : var types much easier.
Well, I don't think you'll get warned about that in Javascript/PHP, so I just make it a general habit.
By the way, which compiler does that (asking, not accusing)? What's the switch for that in gcc?
Well, he has a signed contract.
But contracts don't get invalidated even if they were totally electronic. It's like this: some people use pen/paper or typewriters to write works of fiction. And others to write business correspondence. The latter isn't invalidated because of the former.
Similarly, just because some people use email to shoot the breeze does not mean e-mail correspondence is invalid before the courts. That's the law since 2000 (ESIGN Act).
If you make an offer to someone (create a logo for me for $500), and he accepts, and creates the logo, you are obligated to pay $500. You made an offer, there was a back-and-forth (on email), and there was an agreement to exchange value (consideration). That's a contract.
FYI, Facebook has not been so stupid as to deny the contract. Last I read, they were going to take the tack that it doesn't mean what other people say it means.
They also haven't denied the emails.
>Since when is something said in an email legally binding, especially in the corporate world?
Since the passage of the ESIGN act?
ESIGN was passed to ensure that contracts or signatures "may not be denied legal effect, validity, or enforceability solely because it is in electronic form".
Note that UETA makes a distinction between electronic signatures vs. secure electronic signatures. But that doesn't mean the former is invalid.
I mention all this just so you (or anybody else) doesn't make business promises in email, and then think you can wave it off because "it's just e-mail".
In any case, the contract in this case wasn't electronic at all: It's a pen-and-paper signed contract with normal legal verbiage.
Plenty of people have been reading Slashdot for longer than the time when they were motivated to create an account. Hats off to your foresight to create an account early.
The thing with the confusion about equality vs. assignment operator is a valid concern, but the := operator doesn't really appeal to me (initially).
Because the bugs associated with mistakenly using = vs. ==, I always put the constant value being compared on the left. That, of course, can't be assigned to, and the compiler will catch your error if you use =.
if (SOME_FLAG = this.x) //compiler flags this
if (SOME_FLAG == this.x)
Same goes for other languages with this syntax (PHP, Javascript, C/C++).
Speaking of greed, the way that Zuckerberg is reputed to have treated Eduardo, his partner, and the one who put up all the initial investment money for Facebook is worse than the situation with the W twins.
He is reputed to have taken Eduardo's 30-some percent share down to 0 or so by issuing new stock to venture capitalists while keeping his and Sean Parker's percentages stable.
One phrase for dealing with startups: "non-dilutable shares"
>Benefits that an employee receives are given a value and will be taxed if they exceed certain numbers that are relative to all employees.
An interesting question is: what determines what benefits are "allowed"?
If the IRS had its way, giving free water to employees would be taxed, too (at maybe the rate for bottled water).
Before the rise of MS and Silicon Valley companies, businesses didn't give their employees free food & drink, pool tables, laundries, entertainment centers, daycare, petcare, and so forth.
So if some companies are giving all that stuff away, and some companies aren't (old-style corps), are "all employees" receiving the benefit so that it can be given taxfree?
Oh, you mean stock Android?
Is that available in a format which would be suitable for installing?
I've heard some stuff about Google holding back on certain of their changes to the kernel.
And is the UI stuff that runs atop the kernel also open source?
As a non-denizen of Steve J's reality distortion field, I have to ask:
Is the control freakiness so great that you cannot even install custom themes on your own iPhone?
You have to jailbreak the phone in order to install a custom theme?
By the way, has anyone been able to get OpenMoko to run on an iPhone, Android (like HTC or whatever), or a Palm Pre?
What about identi.ca ?
Don't geeks deserve to notified of tsunamis?
Used to be, on the Internet, no one knows you're a dog.
I've been playing a lawyer for a long time, but I guess it's better to disclose before being found out. You heard it here first.
in letting James "Father of Java" Gosling go to Google.
In a case where the judge is learning about Java, and where testimony may be taken on the history of Java, it can't help to have its creator on the other side.
While it's great that Bugzilla is provding this, I'm wondering if anyone can post their experience with Bugzilla alternatives.
Bugzilla's great ... for developers.
Is there anything that could be just to allow customers to directly enter bugs? Something Trac-like?
Nokia's strategy: lose on every sale, and make it up on volume. Sad to see a storied, century-old company go like this.
For people who have worked with NoSQL (assuming you've worked extensively with SQL before):
1. For someone wanting to either scratch an itch, or come up with the Next Great Thing, would you recommend NoSQL-type solutions to do the standard save data coming in over the web, and later retrieve it, possibly rejigger and summarize it, and feed it back over the web when a user needs it thing?
2. Is NoSQL generally considered faster than SQL equivalents? At runtime or development time?
3. Is there a concept of DB design? Or is it just made up as you go? By doing additional .insert()'s?
I.e., you start off by .create(product). Then add fields: .addAttribute('name', 'Magic Rock') .addAttribute('manuf', 'Rock Emporium')
Then you add in detail for the manufacturer table: .addAttribute('name', 'Rock Emporium') .addAttribute('st', '123 Main St') .addAttribute('state', 'NY')
Is that how it works?
4. And can you change field names later (ALTER TABLE)?
5. What about aggregate functions (MAX, GROUP BY, HAVING)?
The whole thing seems awfully gooey.
I'm thinking about wading into the noSQL waters. Help me out:
If authors aren't normalized, does that basically mean you don't have a separate datastore (table, whatever) for authors? E.g., a publisher might want to keep track of author name, address, etc.
Here's another classic example: country codes vs. country names: (ca, Canada), (us, United States).
If you want to be able to use both, you'd would (classicly) store "ca" in your User table (for what country he lives in), and then have a separate Countries table that tells you what "ca" stands for.
How do you approach that in NoSQL (assuming you want to make use of both codes and full country names)?
Naturally, of course.
Could I pick your brain since you have a bit of NoSQL experience?
How does indexing work in NoSQL? Are there EXPLAIN-type tools available? (EXPLAIN in MySQL tells you whether your query is using indexes or table scans, and can help you understand why your query is slow.)
I'm pretty flexible with SQL. Can you do just about any query you could with SQL? ("Find all customers who have bought at least $100 of stuff over the last year, but who haven't bought anything this year.")
One thing that annoys me is the disjunction between UPDATE and INSERT queries for the same set of fields:
INSERT INTO blah(uid, name, email) VALUES(12,'Goober','goob@example.com')
But if you want to change that to an UPDATE query, you have to move each of the fields around:
UPDATE blah SET uid=12, name='Goober', email='goob@example.com'
This would have been better:
UPDATE blah SET (uid, name, email) VALUES(12,'Goober','goob@example.com')
By the way, if you want to read hard-core fundamentalist, pro-relational stuff by DB guru CJ Date and others, DBDebunk is the place:
http://www.dbdebunk.com/