MySQL, for all it's so-called flexibility, has abysmal indexing capabilities. It's unicode support is far inferior. MySQL might be faster on a connections per second rate, but falls behind on update speed.
I'm not oblivious to PG's inferiorities though. I guess the biggest issue is that PG's replication is inefficient compared to MySQL.
It was recently reported that there is in fact large diversity in the proportions and types of bacteria living among people in their intestines.
I'm a little surprised more work hasn't gone into studying the bacteria types and trying to find correlation, or better yet, causation between the types of predominant bacteria people have and their weight.
From what I have read online, people have gone to the extremes when they go on low carb diets. Some people do all they can to cut every carbohydrate they can from their diet.
I guess people don't realize that you must consume at least some carbs to stay healthy. As in all things in life, moderation is key.
Idle muscles burn few calories. More so than idle fat, but the fact remains.
Weight training alone will not make a fat person skinny. Cardio alone without weight training is a slow process, but doable. Best practice means doing both.
Personally, I do kickboxing aerobics 3 times per week and 30-45 minutes of weights on other days. So far, after just a month, I can see the results and I haven't even trimmed back my carb intake, which I should do. I have tried hardcore cardio before without weights and it didn't seem especially effective.
Re:What compares to Access on PostgreSQL?
on
PostgreSQL 8.4 Out
·
· Score: 1
OOo Base does indeed with with PG directly or as an ODBC connection.
I've got to say now though, if you're using Base for creating reports on tables that are large, expect it to run painfully slow, even if the data being used in the report is small. It seems to fetch the entire table from the database, regardless of which fields are needed to compile the report.
It's pretty much spot on though. When a new feature comes out for MySQL, the fanatics love to shove it in your face, even if the real RDBMS have had it for years.
PostgreSQL does everything mySQL does, but better. I would have thought great unicode support alone would be enough to sway the mySQL believers but I was wrong. Now I don't even debate the issue unless I'm sure I am even talking to a reasonable human. The whole mySQL vs. PostgreSQL debate usually descends into the mud quickly with neither side listening to the other.
The.NET controls being wrappers for the WIN32 controls is just stupid. The whole point of Winforms is to encapsulate UI classes and events into a logical object oriented structure. When you have to delve into WIN32 messages to handle what should be basic events because you want to add a small feature to a preexisting control, it's a sign there is a problem.
In my opinion, Microsoft did this(partly) because if.NET reimplemented all of the Winforms functionality, it would give software developers MORE portability. Right now, writing cross-platform with Winforms is virtually impossible if you need to subclass controls. If cross-platform were easy, more big software packages that drive Windows dominance would begin to appear for Linux.
No not everyone else in the world has universal health care. Most people in africa don't even have fundamental universal medications like NSAIDs and antibiotics available.
Oh you meant the developed world?
Hate to brake it to you, but even among developed countries, a lot of them do not have health care systems radically different from our own.
The american dream of the 50's is that through hard work and determination, prosperity is within grasp for all.
Now it is more widely understood that class mobility is influenced by many more factors than hard work and determination, but a fundamental theory in retirement planning is that if you put money into your retirement, you will have a more comfortable life during your senior years.
Investment in legitimate funds is difficult enough without the madoff's of the world intentionally ripping people off.
About as stupid as these senators apparently. I mean really....
Siemens, not bidding on federal contracts?
Bwaaaaaaaaaaaahahahahahaahaaaaaaaaahahhaahhahahaa
uh huh mmmmmmmmmmmmmm
my side hurts now. Maybe these senators don't realize, but either directly or indirectly, you'd be hard pressed to find a federal contract that didn't support Siemens somehow. They're a $120 billion a year company making a gazillion little gadgets most senators never heard of, used in everthing from bulldozers to fire alarms.
What madoff did was 100x times worse than your average 7-11 robber.
Yeah, I said it. It's worse than even a violent crime. 7-11 is insured and gets their money back, the crime is far from victimless but there is typically just 1-2 victims and they recover.
Because of madoff, thousands will suffer through the last years of their lives living from social security check to check, will not have access to the medications they need or the mobility required to live a healthy senior life.
I have no pity for the man. 150 years wasn't enough. Sadly, he will die of old age before any possible recompense can be served.
I've encountered relatively few problems so far with cross platform Qt/C++ applications. The most difficult part is when I am relying on external libraries that aren't cross platform, but this doesn't happen very often.
You couldn't pay me enough to want to use WPF. Thanks though.
Winforms and Qt are actually very similar from a UI API perspective. Function names aren't identical, but there are so many similarities that I can switch back and forth between MSVC/Winforms and C++/Qt pretty easily.
Quirks? For starters, rich text boxes in winforms are still wrappers for legacy WIN32 text boxes, meaning reimplementing them to add functionality is a lot more complicated than it needs to be. Using unmanaged code and managed code in the same project is made intentionally inconvenient.
I've been writing some winforms applications and all I've got to say is "no". As a long time Qt programmer, I found winforms initially familiar, but it's got a lot of quirks that drive me nuts.
Exactly. They should start small. Focus on performance profiling, find the most expensive parts of their code and reimplement those in a compiled language.
If they're using Zend and still can't get the performance they need, they just need to accept that PHP's flexibility and rapid development friendliness come at a price-runtime speed.
Agreed. The FCC has been largely absent in meaningful ways in the cellular carrier market for some time. Sure, they managed to sell off some spectrum but that doesn't do anything to solve the current problems in the US cellular market.
My HUGE issue with both Verizon and AT&T is that if you purchase a PDA phone such as a Blackberry, they require you to also subscribe to a special data plan at $20-$30 per month. I don't disagree that data access should cost more than voice, but both carriers already offer a so-called "unlimited" data plan for non-PDA phones at a lower cost. However, they both feel you can charge more just because it's a PDA, despite the fact that a Blackberry is no more capable of utilizing bandwidth than any other network enabled phone.
They're not very honest about why either. I'm in the market to switch carriers and I contacted both companies about why the regular unlimited data plans don't cover PDA's and mums the word. They just spew bullshit form letters about how the Blackberry plans offer unlimited data, but neglect to give any reason why they're special.
A forced unbundling of phone purchases from contracts would effectively end exclusivity agreements also. Competition among handset producers would be based on functionality, not how much the carrier wants to push it based on profitability.
I agree with US Cellular that exclusivity agreements are bad, but ending exclusivity doesn't go far enough to fix the domestic cellular market.
That's kind of my point. Contract rates are based on them subsidizing your purchase of the most expensive phone. People taking shitty "free" phones merely prop up profits.
Carriers do not tell you to upgrade or lower your rates when your contract expires-it's their customers responsibility apparently. Conversely, if you choose to obtain service but already have a phone, they do not offer you a reduced rate.
This in my mind is a strong case of product tying, essentially they offer nothing of value if you choose to not participate in their phone acquisition subsidization plan and is anti-free market. It reduces end user choice because the phone manufacturers hamstring their products to whatever the networks desire. Just look at the newest iPhone supporting tethering but AT&T won't let it be advertised in foreign countries because it will raise expectations for AT&T's domestic customers.
Not sure if you caught my comments on a previously posted related topic, but handset manufacturers currently serve the interests of the carriers, NOT the end users.
This practice is merely exemplified by exclusivity contracts such as the iPhone or Palm Pre. The real issue here is that handset success is based largely on the whims of the carriers, not on functionality or usability. Exclusivity is a byproduct of the common subsidized handset for reduced contract rates system we have in the US. If this practice were ended, so too would be exclusivity deals.
If you'll notice, there are now just a few "classes" of handsets, all with very similar functionality based on the desires of the largest carriers. Tying handset purchases to carrier contracts needs to end!
Slashdot Mirror
MySQL, for all it's so-called flexibility, has abysmal indexing capabilities. It's unicode support is far inferior. MySQL might be faster on a connections per second rate, but falls behind on update speed.
I'm not oblivious to PG's inferiorities though. I guess the biggest issue is that PG's replication is inefficient compared to MySQL.
It was recently reported that there is in fact large diversity in the proportions and types of bacteria living among people in their intestines.
I'm a little surprised more work hasn't gone into studying the bacteria types and trying to find correlation, or better yet, causation between the types of predominant bacteria people have and their weight.
I would bet money there is at least correlation.
From what I have read online, people have gone to the extremes when they go on low carb diets. Some people do all they can to cut every carbohydrate they can from their diet.
I guess people don't realize that you must consume at least some carbs to stay healthy. As in all things in life, moderation is key.
Idle muscles burn few calories. More so than idle fat, but the fact remains.
Weight training alone will not make a fat person skinny. Cardio alone without weight training is a slow process, but doable. Best practice means doing both.
Personally, I do kickboxing aerobics 3 times per week and 30-45 minutes of weights on other days. So far, after just a month, I can see the results and I haven't even trimmed back my carb intake, which I should do. I have tried hardcore cardio before without weights and it didn't seem especially effective.
OOo Base does indeed with with PG directly or as an ODBC connection.
I've got to say now though, if you're using Base for creating reports on tables that are large, expect it to run painfully slow, even if the data being used in the report is small. It seems to fetch the entire table from the database, regardless of which fields are needed to compile the report.
Maybe you can relay back to Oracle please that the eBusiness java interface is god awful slow.
Thanks. You might have more sway than I do.
It's pretty much spot on though. When a new feature comes out for MySQL, the fanatics love to shove it in your face, even if the real RDBMS have had it for years.
PostgreSQL does everything mySQL does, but better. I would have thought great unicode support alone would be enough to sway the mySQL believers but I was wrong. Now I don't even debate the issue unless I'm sure I am even talking to a reasonable human. The whole mySQL vs. PostgreSQL debate usually descends into the mud quickly with neither side listening to the other.
I'll stick with PostgreSQL, thank you very much.
No, even a quirk isn't the right word.
The .NET controls being wrappers for the WIN32 controls is just stupid. The whole point of Winforms is to encapsulate UI classes and events into a logical object oriented structure. When you have to delve into WIN32 messages to handle what should be basic events because you want to add a small feature to a preexisting control, it's a sign there is a problem.
In my opinion, Microsoft did this(partly) because if .NET reimplemented all of the Winforms functionality, it would give software developers MORE portability. Right now, writing cross-platform with Winforms is virtually impossible if you need to subclass controls. If cross-platform were easy, more big software packages that drive Windows dominance would begin to appear for Linux.
No not everyone else in the world has universal health care. Most people in africa don't even have fundamental universal medications like NSAIDs and antibiotics available.
Oh you meant the developed world?
Hate to brake it to you, but even among developed countries, a lot of them do not have health care systems radically different from our own.
The american dream of the 50's is that through hard work and determination, prosperity is within grasp for all.
Now it is more widely understood that class mobility is influenced by many more factors than hard work and determination, but a fundamental theory in retirement planning is that if you put money into your retirement, you will have a more comfortable life during your senior years.
Investment in legitimate funds is difficult enough without the madoff's of the world intentionally ripping people off.
it's not just for Linux.
About as stupid as these senators apparently. I mean really....
Siemens, not bidding on federal contracts?
Bwaaaaaaaaaaaahahahahahaahaaaaaaaaahahhaahhahahaa
uh huh mmmmmmmmmmmmmm
my side hurts now. Maybe these senators don't realize, but either directly or indirectly, you'd be hard pressed to find a federal contract that didn't support Siemens somehow. They're a $120 billion a year company making a gazillion little gadgets most senators never heard of, used in everthing from bulldozers to fire alarms.
This is all political bullshit.
What madoff did was 100x times worse than your average 7-11 robber.
Yeah, I said it. It's worse than even a violent crime. 7-11 is insured and gets their money back, the crime is far from victimless but there is typically just 1-2 victims and they recover.
Because of madoff, thousands will suffer through the last years of their lives living from social security check to check, will not have access to the medications they need or the mobility required to live a healthy senior life.
I have no pity for the man. 150 years wasn't enough. Sadly, he will die of old age before any possible recompense can be served.
I've encountered relatively few problems so far with cross platform Qt/C++ applications. The most difficult part is when I am relying on external libraries that aren't cross platform, but this doesn't happen very often.
You couldn't pay me enough to want to use WPF. Thanks though.
Winforms and Qt are actually very similar from a UI API perspective. Function names aren't identical, but there are so many similarities that I can switch back and forth between MSVC/Winforms and C++/Qt pretty easily.
Quirks? For starters, rich text boxes in winforms are still wrappers for legacy WIN32 text boxes, meaning reimplementing them to add functionality is a lot more complicated than it needs to be. Using unmanaged code and managed code in the same project is made intentionally inconvenient.
Just say no.
I've been writing some winforms applications and all I've got to say is "no". As a long time Qt programmer, I found winforms initially familiar, but it's got a lot of quirks that drive me nuts.
I'll stick with Qt on C++ thank you very much.
Thats about the most informative thing I've read on slashdot this month. Thanks.
I was under the impression ARIN handled IP block assignments, not ICANN. Is that not right?
Exactly. They should start small. Focus on performance profiling, find the most expensive parts of their code and reimplement those in a compiled language.
If they're using Zend and still can't get the performance they need, they just need to accept that PHP's flexibility and rapid development friendliness come at a price-runtime speed.
As the AC noted, ARM's are available, cheap and power efficient. What they are not, however, is very powerful.
They have their uses, but interpreting large amounts of crappy scripts is not one of ARM's strong points.
Agreed. The FCC has been largely absent in meaningful ways in the cellular carrier market for some time. Sure, they managed to sell off some spectrum but that doesn't do anything to solve the current problems in the US cellular market.
My HUGE issue with both Verizon and AT&T is that if you purchase a PDA phone such as a Blackberry, they require you to also subscribe to a special data plan at $20-$30 per month. I don't disagree that data access should cost more than voice, but both carriers already offer a so-called "unlimited" data plan for non-PDA phones at a lower cost. However, they both feel you can charge more just because it's a PDA, despite the fact that a Blackberry is no more capable of utilizing bandwidth than any other network enabled phone.
They're not very honest about why either. I'm in the market to switch carriers and I contacted both companies about why the regular unlimited data plans don't cover PDA's and mums the word. They just spew bullshit form letters about how the Blackberry plans offer unlimited data, but neglect to give any reason why they're special.
A forced unbundling of phone purchases from contracts would effectively end exclusivity agreements also. Competition among handset producers would be based on functionality, not how much the carrier wants to push it based on profitability.
I agree with US Cellular that exclusivity agreements are bad, but ending exclusivity doesn't go far enough to fix the domestic cellular market.
That's kind of my point. Contract rates are based on them subsidizing your purchase of the most expensive phone. People taking shitty "free" phones merely prop up profits.
Carriers do not tell you to upgrade or lower your rates when your contract expires-it's their customers responsibility apparently. Conversely, if you choose to obtain service but already have a phone, they do not offer you a reduced rate.
This in my mind is a strong case of product tying, essentially they offer nothing of value if you choose to not participate in their phone acquisition subsidization plan and is anti-free market. It reduces end user choice because the phone manufacturers hamstring their products to whatever the networks desire. Just look at the newest iPhone supporting tethering but AT&T won't let it be advertised in foreign countries because it will raise expectations for AT&T's domestic customers.
Not sure if you caught my comments on a previously posted related topic, but handset manufacturers currently serve the interests of the carriers, NOT the end users.
This practice is merely exemplified by exclusivity contracts such as the iPhone or Palm Pre. The real issue here is that handset success is based largely on the whims of the carriers, not on functionality or usability. Exclusivity is a byproduct of the common subsidized handset for reduced contract rates system we have in the US. If this practice were ended, so too would be exclusivity deals.
If you'll notice, there are now just a few "classes" of handsets, all with very similar functionality based on the desires of the largest carriers. Tying handset purchases to carrier contracts needs to end!