Re:Bible re. making money
on
OSI vs SCO
·
· Score: 1
I haven't really studied what the Bible says re. accumulating more wealth than you need. But "making money" doesn't imply accumulating more than you need.
MIT's Athena is used by nearly the entire community of 30,000 students, faculty and staff. The 9,000 students make almost daily use of it. It consists mostly of Solaris and Linux desktops. MIT spent much of the 1990s waiting for NT's capabilities to catch up to the hype. Finally, in the past couple of years, they've been able to make Windows desktops be part of the system. However, these are much more costly to maintain than the POSIX2-based boxes.
In short, your point is demonstrably wrong.
It's one integrated system. If you surpise me by actually giving an example of a company with 20,000 Windows desktops, I'll bet they're separated into a large number of islands of control ("domains"), and not one big system like Athena. MSFT just can't make systems scale like that.
The verses you quoted (Luke 18:24 and 1 Timothy 6:10) teach that the love of money makes it difficult for people to prioritize spiritually, not that making money is immoral.
Re:ESR just couldn't resist...
on
OSI vs SCO
·
· Score: 1
Before its meaning got distorted, the majority of people who said or heard "hacker" thought it meant something more like what ESR says. By your reasoning, no bad press, law enforcement, etc. would have changed that. But you're wrong. Word meanings change. They can change back. Deal with it.
Re:GPL the best bet
on
OSI vs SCO
·
· Score: 4, Informative
I like the GPL, but please note that BSD or any other free-software license would have the same result in this case. Any license they grant to the public precludes trade secret violation, and copyright violation is limited to breach of the license.
Perhaps if you learned to write adequate code that checked its user input, you wouldn't be so dependent on having the database do it
for you.
Perhaps if I, along with everybody else who writes code to access the database, always, without fail, makes sure to validate user input. And if when new constraints get introduced we make sure to update all code that validates user input, then we'll be fine. However, one great thing about a real database is that you only have to specify constraints once, no matter how many apps insert data.
My impression is that PHP doesn't have any significant advantage re. dynamic web content, at least not since automatically putting form inputs into variables was found to be a security hole. Got an example of code that shows off PHP's dynamic web abilities?
Yeah, that code in MySQL that makes sure users use updated whois clients is really cool. PostgreSQL might get a similar feature soon, but by then MySQL will have an even better feature that prevents The Register from publishing bogus articles about servers being down when they're up. MySQL rocks! Go MySQL!
It's premature to speculate on the cause of the outage
On a more serious note, it's premature to even say there was an outage.
That's the syntax I was taught in spring 1987. Sure, it was technically allowed for a Scheme implementation to omit it and still claim conformance, but I don't think I ever encountered an implementation that omitted it. Certainly all the major implementations have supported it for a long, long time. I'm glad the 1998 standard (R5RS) requires it.
Very few pages benefit from threading, so I'm not surprised PHP hasn't made it a priority. You could always code most of your project in PHP, but use a thread-enabled language like BRL for those few pages.
The problem is the tradeoff between making a language flexible and making it optimizable. The limitations of SQL are there mostly to help the optimizer. However, if you want to extend SQL in interesting ways, the standard is always being updated. See about getting involved nin the committee.
Forth was my first language after Basic. It was so much more expressive! A maze-generating algorithm that I couldn't wrap my head around when programming in BASIC suddenly became obvious when programming in Forth. Having recursion really helped.
Plus, few people end up with jobs or projects that force them into Forth against their will, so there isn't much hatred out there.
For queries involving multiple tables, the database itself will be able to optimize better than any RAIDb controller. Full replication will always be better. Each individual db server has direct access to all tables and can formulate a good query plan.
The only situation where partial replication would speed things up would be a large number of write-intensive tables. I expect most apps would have one, two or possibly three write-intensive tables. I don't know if TPC-W is realistic.
The How to Design Programs book and DrScheme environment make for a good start. DrScheme has settable "language levels" that turn off advanced features. This lets you get more intelligible error messages when you're just starting out. Without this feature, programmer newbies get strange error messages when a typo unintentionally invokes advanced language features.
Sheesh, why do you have to write so many paragraphs? Just say, "True freedom would let me both copy GPL code and restrict the freedom of others." That's all you're saying, really.
Whine all you want. The situation is you have to choose one or the other. If you want to restrict others' freedom, don't copy GPL code. It's that simple.
P.S. RMS does not claim that GPL-incompatible licenses are automatically non-free. You're the one making that claim when you say true freedom means being able to license derivatives however you want.
Slashdot Mirror
I haven't really studied what the Bible says re. accumulating more wealth than you need. But "making money" doesn't imply accumulating more than you need.
MIT's Athena is used by nearly the entire community of 30,000 students, faculty and staff. The 9,000 students make almost daily use of it. It consists mostly of Solaris and Linux desktops. MIT spent much of the 1990s waiting for NT's capabilities to catch up to the hype. Finally, in the past couple of years, they've been able to make Windows desktops be part of the system. However, these are much more costly to maintain than the POSIX2-based boxes.
In short, your point is demonstrably wrong.
It's one integrated system. If you surpise me by actually giving an example of a company with 20,000 Windows desktops, I'll bet they're separated into a large number of islands of control ("domains"), and not one big system like Athena. MSFT just can't make systems scale like that.
The verses you quoted (Luke 18:24 and 1 Timothy 6:10) teach that the love of money makes it difficult for people to prioritize spiritually, not that making money is immoral.
Before its meaning got distorted, the majority of people who said or heard "hacker" thought it meant something more like what ESR says. By your reasoning, no bad press, law enforcement, etc. would have changed that. But you're wrong. Word meanings change. They can change back. Deal with it.
I like the GPL, but please note that BSD or any other free-software license would have the same result in this case. Any license they grant to the public precludes trade secret violation, and copyright violation is limited to breach of the license.
Perhaps if I, along with everybody else who writes code to access the database, always, without fail, makes sure to validate user input. And if when new constraints get introduced we make sure to update all code that validates user input, then we'll be fine. However, one great thing about a real database is that you only have to specify constraints once, no matter how many apps insert data.
My impression is that PHP doesn't have any significant advantage re. dynamic web content, at least not since automatically putting form inputs into variables was found to be a security hole. Got an example of code that shows off PHP's dynamic web abilities?
Sheesh, what do you want, some weird characters like ] to open a string and [ to close it? Nobody would ever use that.
Yeah, that code in MySQL that makes sure users use updated whois clients is really cool. PostgreSQL might get a similar feature soon, but by then MySQL will have an even better feature that prevents The Register from publishing bogus articles about servers being down when they're up. MySQL rocks! Go MySQL!
It's premature to speculate on the cause of the outage
On a more serious note, it's premature to even say there was an outage.
That's the syntax I was taught in spring 1987. Sure, it was technically allowed for a Scheme implementation to omit it and still claim conformance, but I don't think I ever encountered an implementation that omitted it. Certainly all the major implementations have supported it for a long, long time. I'm glad the 1998 standard (R5RS) requires it.
Very few pages benefit from threading, so I'm not surprised PHP hasn't made it a priority. You could always code most of your project in PHP, but use a thread-enabled language like BRL for those few pages.
The problem is the tradeoff between making a language flexible and making it optimizable. The limitations of SQL are there mostly to help the optimizer. However, if you want to extend SQL in interesting ways, the standard is always being updated. See about getting involved nin the committee.
Quien dijo que fue Spanish? En muchas partes de North America es mas comun to speak en una mezcla de las tus languages. Iz call Spanglish.
Forth was my first language after Basic. It was so much more expressive! A maze-generating algorithm that I couldn't wrap my head around when programming in BASIC suddenly became obvious when programming in Forth. Having recursion really helped.
Plus, few people end up with jobs or projects that force them into Forth against their will, so there isn't much hatred out there.
I maintain that BRL kicks PHP's butt when it comes to small, simple CGI scripts.
For individuals and small businesses content with 99% uptime, a project like this is overkill. It's still interesting though.
For queries involving multiple tables, the database itself will be able to optimize better than any RAIDb controller. Full replication will always be better. Each individual db server has direct access to all tables and can formulate a good query plan.
The only situation where partial replication would speed things up would be a large number of write-intensive tables. I expect most apps would have one, two or possibly three write-intensive tables. I don't know if TPC-W is realistic.
The How to Design Programs book and DrScheme environment make for a good start. DrScheme has settable "language levels" that turn off advanced features. This lets you get more intelligible error messages when you're just starting out. Without this feature, programmer newbies get strange error messages when a typo unintentionally invokes advanced language features.
Sheesh, why do you have to write so many paragraphs? Just say, "True freedom would let me both copy GPL code and restrict the freedom of others." That's all you're saying, really.
Whine all you want. The situation is you have to choose one or the other. If you want to restrict others' freedom, don't copy GPL code. It's that simple.
P.S. RMS does not claim that GPL-incompatible licenses are automatically non-free. You're the one making that claim when you say true freedom means being able to license derivatives however you want.
The Scheme programming language has a built-in rationalize function to solve just this type of problem:
(rationalize 924/1000 1/2000)
Yields 61/66.
Of course, 74.9% of all statistics are just made up on the spot anyhow.
Yes, there most certainly are other concepts to be introduced first.
Come on, lighten up. If you really want to join a community free of clueless people, you can always...
um....
I'll have to get back to you on that.
> cutting Jar Jar Binks out of Star Wars 1
Will CleanFlicks do this? Do they have an 800 number?If Gates had hubris, he would think his company good enough to stomp the competition without needing underhanded tactics.