You've only captured half the point. Yes, the MacMini's capable. Yes, it's not as fast or even as feature rich as a competetive PC. What about the other side of the coin? The person wanting a quiet, unobtrusive, low maintenance computer that they can stick in their living room or den? You won't match the MacMini's 'features' in the PC world in those respects.
While you've built the cheapest PC powerhouse for a corporate setting, you certainly haven't built a computer for the home or casual user.
Mr. Schrock's argument can be responded to quite readily with a single quote: "Ask not what your country [operating system] can do for you but what you can do for your country [operating system]." Thanks Jack, I'll take over from here.
Mr. Schrock's confusion over Linux appears to be rooted in two points of ignorance: "What & Why is Linux" and "What's the difference between a Linux distribution and the Linux kernel".
Linux is a community operating system. Community in the sense of ownership and more importantly contribution. Complaining about Linux missing specific features is not a reflection of the operating system but a reflection of your contribution to it. If your concerns are truly important to you rally around them. That means if you can code do so but if you cannot, work to get others interested, be they other kernel developers or commercial entities. Grousing about how misguided the priorities of others is not constructive in the least and in fact may have the opposite effect, alienating those that would otherwise support your cause.
A Linux kernel 'release' is a snapshot, not truly intended for customer usage, of the current state of Linux kernel development. It is analogous to a private entity's internal development group creating milestone builds of its technology. The fact that the Linux effort is performed in public as opposed to Solaris' private development makes it no less valuable then Solaris' internal builds are for Sun. The similarities don't end there. The Linux operating system has multiple distributions. These are composed of a development snapshot of the Linux kernel plus many other packages necessary to round out what the general public considers necessary for an operating system. Solaris has only a single distribution, packaged by Sun, that contains code seeking a similar aim. Linux distributors, similar to Solaris' sole distributor, may package other code, kernel related or otherwise, to add functionality deemed critical. This is done regardless of the direction of the Linux kernel development effort and not necessarily in line with the Linux kernel contributors desires. This again reflects the public nature of Linux development and is a strong argument in favor of keeping Linux kernel and distribution development distinct.
Why could Sun not work with Linux to make its own distribution incorporating functionality of perhaps its own design? Mr. Schrock submits version tracking as the primary issue, regardless of multiple Linux distributors managing to do this with little complaint. Why even entertain this as an issue? Before complaining about tracking kernel version changes Mr. Schrock, with everyone else, should put forth the effort to work with the community before grousing about the potential negative results. Mr. Schrock's concern regarding the Linux kernel's development community's propensity for rejecting what he believes are important features is a red herring. Not only has Mr. Schrock not invested the time necessary to understand why specific Linux kernel code contributions were rejected but has also never submitted changes of his or Sun's own making to work through the process.
As Mr. Schrock's argument can be responded to quite readily with a single quote: "Ask not what your country [operating system] can do for you but what you can do for your country [operating system]." Thanks Jack, I'll take over from here.
Mr. Schrock's confusion over Linux appears to be rooted in two points of ignorance: "What & Why is Linux" and "What's the difference between a Linux distribution and the Linux kernel".
Linux is a community operating system. Community in the sense of ownership and more importantly contribution. Complaining about Linux missing specific features is not a reflection of the operating system but a reflection of your contribution to it. If your concerns are truly important to you rally around them. That means if you can code do so but if you cannot, work to get others interested, be they other ke
Why post news of your own content if your site can't handle the Slashdotting?
There should be a formal Slashdot guideline that if the server has not handled the slashdot effect in the past posting of your own content should not be permitted. Of course that wouldn't keep out the punters but it's certainly no fun to see "valuable" Slashdot comments on content that you can't visit.
This is the second time in the last few weeks that Tweaktown has done this. First with the system tweaking post and now with this. Neither could be visited for 24 hours after the Slashdot news story was posted. Sad, just sad.
BEEP was never meant to be all things to all people. If your application is solely concerned with sending small "hello"-type messages back and forth then there are much lighter-weight protocols to use. But if your application requires the transfer of moderately sized data packets then the additional weight of an XML envelope is trivial.
Obviously the hello example is meant to illustrate the protocol and not necessarily it's best usage.
BEEP's an impressive protocol framework with even more impressive implementations.
I'm using it in a burgeoning open source project because of it's ability to multiplex bidirectional communication channels in a transparent fashion. Other features such as dynamic client/server roles, authentication, and channel encryption are just icing on the cake. The less I have to muck around with protocol state details the better!
When I first started looking at BEEP I was impressed by the spec but I was suspicious as to the quality and breadth of implementations. After looking through the high level Java abstractions and more specifically BeepCore-Java I was able to throw together a workable protocol that's proven to be extensible and quite robust in just a few days.
The BEEP community is alive and well!
There are a number of opensource BEEP implementations:
BEEPCore-Java - Java implementation with a BSD-like license
BEEPCore-C - C/C++ implementation with a BSD-like license
PermaBEEP - C implementation with a SleepCat-like license
But the best source for information is the Beepcore.org site which has, among other things, an excellent whitepaper on the justification and design of the BEEP protocol.
Don't click on the article link hoping for a review from the fine folks at Security Focus. This is simply an install HowTo; editorializing is kept to a minimum.
Sounds like your tuning was out of whack. You're not very specific about what you tuned (heck, if everyone was specific what fun would Slashdot be?) but I'd bet you had 2 wires crossed somewhere. We're running an system with, what would appear to be, a larger number of inserts and retrievals, for stock quotes and have had completely different results from your experience. We're very happy with the performance and find in a mixed insert/select situation InnoDB is quite a bit faster than MyISAM.
After your bad experience did you send an email to Mr. InnoDB, Heikki Tuuri? He's quite attentive and I'm sure would like to hear what happened with your application.
Not to mention when you're playing with databases or other vaguely unknown programmatic quantities, best not to test them in production. Perhaps if you had run the system in a test environment the lessened pressure would've enabled you to be better equipped to resolve whatever situation was occurring.
MySQL is most definitely capable of supporting ACID functionality.
One of the nice features of MySQL is the capability of having pluggable persistence managers. An example of that is the default, MyISAM, which you are correct in saying does not support ACID. But with the release of MySQL-Max, which happened awhileago(tm), and MySQL v4 out of the box, support for 3 additional backends was added, BerkelyDB, Gemini, and InnoDB, all of which have complete ACID support. InnoDB also supports row level locking and even an initial implementation of foreign keys.
InnoDb is is in use here at Slashdot as well as a good deal of other sites demanding high-transaction throughput with full ACID support.
With the addition of foreign keys and stored procedures functionality, all of which are on the slate for the 4.x series, the reasons not to use MySQL are lessening every day.
Side note: Yeah, I know Gemini is the red-haired stepchild of the MySQL world. It's still a decent table manager.
The best ad was EDS' "running with the squirrels" right near the beginning of the game.
Though the Cingular ad with the disabled gentleman painting was very well done. Too bad he's just whoring himself out for a wireless company. With not even a mention of a charity or support organization for the disabled it was an empty, cheap ploy.
"When you run with the squirrels you have to think like the squirrels." Too funny.
Todd Hollenshead's Quake3World forum posts carry this information as well as much more. Including a little bragging about Id's Linux support:
"I challenge you to find a developer who has done more to support the Linux community than id. There isn't even a second place."
Just for clarification and perhaps there's little difference between the two, but the Microsoft business lemming Goodhew screwed up the Gosling quote and not Anders.
Slashdot Mirror
You've only captured half the point. Yes, the MacMini's capable. Yes, it's not as fast or even as feature rich as a competetive PC. What about the other side of the coin? The person wanting a quiet, unobtrusive, low maintenance computer that they can stick in their living room or den? You won't match the MacMini's 'features' in the PC world in those respects.
While you've built the cheapest PC powerhouse for a corporate setting, you certainly haven't built a computer for the home or casual user.
Mr. Schrock's argument can be responded to quite readily with a single quote: "Ask not what your country [operating system] can do for you but what you can do for your country [operating system]." Thanks Jack, I'll take over from here.
Mr. Schrock's confusion over Linux appears to be rooted in two points of ignorance: "What & Why is Linux" and "What's the difference between a Linux distribution and the Linux kernel".
Linux is a community operating system. Community in the sense of ownership and more importantly contribution. Complaining about Linux missing specific features is not a reflection of the operating system but a reflection of your contribution to it. If your concerns are truly important to you rally around them. That means if you can code do so but if you cannot, work to get others interested, be they other kernel developers or commercial entities. Grousing about how misguided the priorities of others is not constructive in the least and in fact may have the opposite effect, alienating those that would otherwise support your cause.
A Linux kernel 'release' is a snapshot, not truly intended for customer usage, of the current state of Linux kernel development. It is analogous to a private entity's internal development group creating milestone builds of its technology. The fact that the Linux effort is performed in public as opposed to Solaris' private development makes it no less valuable then Solaris' internal builds are for Sun. The similarities don't end there. The Linux operating system has multiple distributions. These are composed of a development snapshot of the Linux kernel plus many other packages necessary to round out what the general public considers necessary for an operating system. Solaris has only a single distribution, packaged by Sun, that contains code seeking a similar aim. Linux distributors, similar to Solaris' sole distributor, may package other code, kernel related or otherwise, to add functionality deemed critical. This is done regardless of the direction of the Linux kernel development effort and not necessarily in line with the Linux kernel contributors desires. This again reflects the public nature of Linux development and is a strong argument in favor of keeping Linux kernel and distribution development distinct.
Why could Sun not work with Linux to make its own distribution incorporating functionality of perhaps its own design? Mr. Schrock submits version tracking as the primary issue, regardless of multiple Linux distributors managing to do this with little complaint. Why even entertain this as an issue? Before complaining about tracking kernel version changes Mr. Schrock, with everyone else, should put forth the effort to work with the community before grousing about the potential negative results. Mr. Schrock's concern regarding the Linux kernel's development community's propensity for rejecting what he believes are important features is a red herring. Not only has Mr. Schrock not invested the time necessary to understand why specific Linux kernel code contributions were rejected but has also never submitted changes of his or Sun's own making to work through the process.
As Mr. Schrock's argument can be responded to quite readily with a single quote: "Ask not what your country [operating system] can do for you but what you can do for your country [operating system]." Thanks Jack, I'll take over from here.
Mr. Schrock's confusion over Linux appears to be rooted in two points of ignorance: "What & Why is Linux" and "What's the difference between a Linux distribution and the Linux kernel".
Linux is a community operating system. Community in the sense of ownership and more importantly contribution. Complaining about Linux missing specific features is not a reflection of the operating system but a reflection of your contribution to it. If your concerns are truly important to you rally around them. That means if you can code do so but if you cannot, work to get others interested, be they other ke
Why post news of your own content if your site can't handle the Slashdotting?
There should be a formal Slashdot guideline that if the server has not handled the slashdot effect in the past posting of your own content should not be permitted. Of course that wouldn't keep out the punters but it's certainly no fun to see "valuable" Slashdot comments on content that you can't visit.
This is the second time in the last few weeks that Tweaktown has done this. First with the system tweaking post and now with this. Neither could be visited for 24 hours after the Slashdot news story was posted. Sad, just sad.
BEEP was never meant to be all things to all people. If your application is solely concerned with sending small "hello"-type messages back and forth then there are much lighter-weight protocols to use. But if your application requires the transfer of moderately sized data packets then the additional weight of an XML envelope is trivial.
Obviously the hello example is meant to illustrate the protocol and not necessarily it's best usage.
BEEP's an impressive protocol framework with even more impressive implementations.
I'm using it in a burgeoning open source project because of it's ability to multiplex bidirectional communication channels in a transparent fashion. Other features such as dynamic client/server roles, authentication, and channel encryption are just icing on the cake. The less I have to muck around with protocol state details the better!
When I first started looking at BEEP I was impressed by the spec but I was suspicious as to the quality and breadth of implementations. After looking through the high level Java abstractions and more specifically BeepCore-Java I was able to throw together a workable protocol that's proven to be extensible and quite robust in just a few days.
The BEEP community is alive and well!
There are a number of opensource BEEP implementations:There's an excellent IRC channel at OpenProjects with the kitschy name #beepnik.
There's the obligatory O'Reilly book, BEEP: The Definitive Guide.
But the best source for information is the Beepcore.org site which has, among other things, an excellent whitepaper on the justification and design of the BEEP protocol.
Don't click on the article link hoping for a review from the fine folks at Security Focus. This is simply an install HowTo; editorializing is kept to a minimum.
Sounds like your tuning was out of whack. You're not very specific about what you tuned (heck, if everyone was specific what fun would Slashdot be?) but I'd bet you had 2 wires crossed somewhere. We're running an system with, what would appear to be, a larger number of inserts and retrievals, for stock quotes and have had completely different results from your experience. We're very happy with the performance and find in a mixed insert/select situation InnoDB is quite a bit faster than MyISAM.
After your bad experience did you send an email to Mr. InnoDB, Heikki Tuuri? He's quite attentive and I'm sure would like to hear what happened with your application.
Not to mention when you're playing with databases or other vaguely unknown programmatic quantities, best not to test them in production. Perhaps if you had run the system in a test environment the lessened pressure would've enabled you to be better equipped to resolve whatever situation was occurring.
One of the nice features of MySQL is the capability of having pluggable persistence managers. An example of that is the default, MyISAM, which you are correct in saying does not support ACID. But with the release of MySQL-Max, which happened awhileago(tm), and MySQL v4 out of the box, support for 3 additional backends was added, BerkelyDB, Gemini, and InnoDB, all of which have complete ACID support. InnoDB also supports row level locking and even an initial implementation of foreign keys.
InnoDb is is in use here at Slashdot as well as a good deal of other sites demanding high-transaction throughput with full ACID support.
With the addition of foreign keys and stored procedures functionality, all of which are on the slate for the 4.x series, the reasons not to use MySQL are lessening every day.
Side note: Yeah, I know Gemini is the red-haired stepchild of the MySQL world. It's still a decent table manager.
Though the Cingular ad with the disabled gentleman painting was very well done. Too bad he's just whoring himself out for a wireless company. With not even a mention of a charity or support organization for the disabled it was an empty, cheap ploy.
"When you run with the squirrels you have to think like the squirrels." Too funny.
Give Galeon a try: http://galeon.sourceforge.net/
<p>
It uses Mozilla's rendering engine but strips out all the non-browsing cruft.
Todd Hollenshead's Quake3World forum posts carry this information as well as much more. Including a little bragging about Id's Linux support:
"I challenge you to find a developer who has done more to support the Linux community than id. There isn't even a second place."
Just for clarification and perhaps there's little difference between the two, but the Microsoft business lemming Goodhew screwed up the Gosling quote and not Anders.