i've been playing the CS:S release that i bought from steam. It said nothing about being a beta when i bought it. Have you been to the steam forums lately? Why is there no answers for all the multitude of problems people are fixing? you'd think they had a code freeze after the rating submision, so what exactly are they doing then?
great, some honest feedback gets modded flamebait. i guess since someone didn't pay me to rate it > 95% then my opinion doesn't matter. i guess doom3 was not at all a boredom fest either. i'm sure whoever modded me down played CS:S./. users show their normal ignorance as usual. nothing changes.
Responsive to the community? There is rampant problems with a known exploit that crashes all clients connected to a server. There is 0 cheat protection and aimbots, wallhacks are everywhere. Nice token or not, i paid for a finished product and did not get one. CS:S is more like counter strike lite, only 2 models, very few maps, no dev tools.
Have you played it? Do you know what your talking about?
There will be no joygasm for most if they don't fix the exploits and bugs in the product. If HL2 is anything like the Counter Strike Source release expect a beta quality product with minimal support.
He does have a point about people using xml for human readable formats sucking. I'm getting sick of having to edit ugly xml format config files. My though is if you are going to use xml to store startup/config data, give me an easier way to update my config. For example;
./updater -u name=value
or better yet include a gui that can properly represent complex nested data structures. otherwise, what is wrong with the good old
#standard txt config
name=value
XML configs do not help the end user to use an application effectively with a short learning curve. It does however allow the developer to be lazy, say RTFM, and slack on documentation, which is the core problem with most of the OSS movement.
ok the topic here should be mysql vs postgres but seeing as how it has been trolled to death I though I would add my.02 and a question.
I've been reviewing and making infrastructure architecture recommendations for > 6 years. My experience has been that the people who can demonstrate scale and efficiency tend to choose systems that do not bottleneck the database. I have used mysql, postgres, as well as oracle. Generally people say that mysql is limited in features, but is that a bad thing? When you have a "large system" and outgrow a 24 processor sun or IBM box you start to consider things like multiple database servers, moving cpu load onto the commodity hardware in the application layer, and data partitioning. DR for large system and the cost a site failure and full restore for such a large system are also valid concern. Most sites with the characteristics of a "large system" are Financial, Telco, Data Warehousing, and batch processing fit an Oracle, or DB2 profile very well. Generally internet sites that don't grow so big (>200GB data), or get Tons(>20Mb/s) traffic tend to do fairly well with anything, even M$ SQL.
Can someone with the deep experience (in both systems), and some spare time, please create a feature/fault matrix for both production and development versions of mysql and posgres and submit the link as a reply? It wouldn't hurt to throw in oracle/DB2 to see what repaying for your software every year gets you.
Slashdot Mirror
i've been playing the CS:S release that i bought from steam. It said nothing about being a beta when i bought it. Have you been to the steam forums lately? Why is there no answers for all the multitude of problems people are fixing? you'd think they had a code freeze after the rating submision, so what exactly are they doing then?
great, some honest feedback gets modded flamebait. i guess since someone didn't pay me to rate it > 95% then my opinion doesn't matter. i guess doom3 was not at all a boredom fest either. i'm sure whoever modded me down played CS:S. /. users show their normal ignorance as usual. nothing changes.
Responsive to the community? There is rampant problems with a known exploit that crashes all clients connected to a server. There is 0 cheat protection and aimbots, wallhacks are everywhere. Nice token or not, i paid for a finished product and did not get one. CS:S is more like counter strike lite, only 2 models, very few maps, no dev tools. Have you played it? Do you know what your talking about?
There will be no joygasm for most if they don't fix the exploits and bugs in the product. If HL2 is anything like the Counter Strike Source release expect a beta quality product with minimal support.
Armature porn lovers rejoice. You just got that much uglier.
or better yet include a gui that can properly represent complex nested data structures. otherwise, what is wrong with the good old
XML configs do not help the end user to use an application effectively with a short learning curve. It does however allow the developer to be lazy, say RTFM, and slack on documentation, which is the core problem with most of the OSS movement.
ok the topic here should be mysql vs postgres but seeing as how it has been trolled to death I though I would add my .02 and a question.
I've been reviewing and making infrastructure architecture recommendations for > 6 years. My experience has been that the people who can demonstrate scale and efficiency tend to choose systems that do not bottleneck the database. I have used mysql, postgres, as well as oracle. Generally people say that mysql is limited in features, but is that a bad thing? When you have a "large system" and outgrow a 24 processor sun or IBM box you start to consider things like multiple database servers, moving cpu load onto the commodity hardware in the application layer, and data partitioning. DR for large system and the cost a site failure and full restore for such a large system are also valid concern. Most sites with the characteristics of a "large system" are Financial, Telco, Data Warehousing, and batch processing fit an Oracle, or DB2 profile very well. Generally internet sites that don't grow so big (>200GB data), or get Tons(>20Mb/s) traffic tend to do fairly well with anything, even M$ SQL.
Can someone with the deep experience (in both systems), and some spare time, please create a feature/fault matrix for both production and development versions of mysql and posgres and submit the link as a reply? It wouldn't hurt to throw in oracle/DB2 to see what repaying for your software every year gets you.