I listened to a VHF station from Greece in the Czech Republic (> 1000 km) on (I think) Wednesday 12:xx MET DST (i.e. 6:xx EDT). Even the RDS functioned.
Is it my fault that your company may have shipped me a faulty unit, and that I find your performance-decreasing "fix" unacceptable?
How do you know that the performance decreases? I tried to search the available resources but I didn't find anything. Unfortunately I don't know what the difference between the refresh modes means practically. Do you? - if yes, please post. Until it is a proven fact that the patch hurts you, you have no right to request a new unit from them, if the patch solves the problem. C'mon, had you got an unit with the defect and the patch already installed, would you notice?
If you are using Intel processors, do you request a new processor every time Intel publicizes a new errata? Did you know, that your BIOS probably loads microcode patch to it on every boot and if it doesn't, your Linux driver can do it for you?
It is unfortunate that such thing happened. People who lost their data have every rigth to bitch. But shit happens and to fix the problem in the most cost-effective way is also in the interest of customers. I am really more comfortable spending 5% more on batteries (if the battery life is really affected) than having to buy the next unit at $50 more.
You're no longer in touch with your job description, and have forgotten exactly what it is that you're supposed to be doing for your company and your public.
Well, I think he is doing exactly what the company told him to.
On your webpage you say you are working as programmer for an ISP (btw, your server doesn't seem to recognize that there is an index.html in the directory). Are you really, really sure that your customers never lost a cent due to screwup on your side? If yes, come to Europe, the company where I work needs such people - actually we have yet to see someone like that:-)
Making noise is one of the things that keeps the open source system healthy.
Yes. And being software developers and not diplomats the language used is not always the most polite in the world - I personally think it is fully OK, but not everyone thinks so. I am not a kernel hacker, but I already have the experience of being flamed down by one of the gurus (well - he was right:-)), after which I responded by sitting down for a day and identifying a though bug in his code:-) Someone else might respond with "Fsck you" and never again read l-k.
The current discussion regarding ReiserFS is not very significant, although it would be sad if it ended with Hans giving up his high-quality work. What bothers me more is that IMHO we are approaching a limit where the current way of project management won't work in the long term and there is very little being done about it. Just a few points:
There is no version control system - instead we play games with x.y.z-test-pre-ac-aa-whatever and if something goes wrong, we binary-search the exact version where it happened instead of getting clue from changelog.
There is no issue tracking system (the TODO saga on the l-k is better than nothing, but...).
The design papers are missing (even a separately archived and publicized relevant mail threads would help).
There is no regression testing (no doubt the developers of the particular subsystem have something, but it is not readily available).
Some problems were identified and adressed - the big delay between 2.0 and 2.2 due to missing definition of the target feature set and (hopefully) the horrible state of 2.2.0 when it came out due to allowing non-bugfix changes in the last pre-versions. Alan Cox does a great job at integrating and testing the patches.
I hope that when the 2.4.0 comes out, the core developers will look back and discuss what can work for next years and what cannot.
Well - if this is a problem for distributed.net, why don't they insist on everybody running the clients on machines with ECC memory only? There are tons of marginal RAM-motherboard combinations out there and the problems are sometimes as hard to spot as in the overclocking case.
Dick size contest? Sometimes maybe but I see it more like best bang for the buck contest - my system with 2 Celerons 433 @ 507 MHz (perfectly stable also at higher speed but I prefer the safe side) was a lot cheaper as the same with non-OC P II sometime last year.
Well, I am also using MSVC and I surely could imagine more stable system, although 6.0 is quite good.
The Intellisense absolutely rocks. However it is not only IDE what counts. I personally can live with vi, make, ddd etc. But it is plenty of mature tools available for M$ environment that makes a difference. Try to profile your code with gprof and then try to do the same using Rational Quantify. Try to make a coverage analysis without recompiling your code under Linux. Try to catch memory errors with ElectricFence - due to how it works it will eat all your memory in a few seconds in all but trivial programs.
Yes, the tools are expensive, but they save a huge amount of time.
Re:Red Star Is To Commies As Swastika Is To Nazis
on
Mozilla M16 Released
·
· Score: 1
Hmm. Coming from an ex-communist country (Slovak Republic) and being brainwashed with the ideas for quite a long (I was 21 when the east-block fell apart) I cannot quite agree with you. The system "noble in intent" claimed at least as many lives as the nazism. Of course we never heard about it, just as the most of Germans did not hear about the Nazi murders.
I own a Mozilla T-shirt. Unfortunately I can wear it only in the community where people know about the Mozilla logo. All others will see a red star and instantly connect it with the communist symbol.
This is not to say I am against the symbol itself, you just can do nothing against the implications of using it.
Just yesterday a hungarian plane returned to Prague shortly after takeoff and made an emergency landing after reporting a fire alarm - fortunately a false one. The media speculate about cell phone involved - we probably never find out whether this was indeed the reason.
We are using unixODBC at the company. We are using ODBC mainly to be able to have single source under Win (native ODBC, several possible databases) and Linux (PostgreSQL only at the moment), so I cannot speak on cooperating with other databases, but the Web page mentions some solutions.
Slashdot Mirror
I listened to a VHF station from Greece in the Czech Republic (> 1000 km) on (I think) Wednesday 12:xx MET DST (i.e. 6:xx EDT). Even the RDS functioned.
How do you know that the performance decreases? I tried to search the available resources but I didn't find anything. Unfortunately I don't know what the difference between the refresh modes means practically. Do you? - if yes, please post. Until it is a proven fact that the patch hurts you, you have no right to request a new unit from them, if the patch solves the problem. C'mon, had you got an unit with the defect and the patch already installed, would you notice?
If you are using Intel processors, do you request a new processor every time Intel publicizes a new errata? Did you know, that your BIOS probably loads microcode patch to it on every boot and if it doesn't, your Linux driver can do it for you?
It is unfortunate that such thing happened. People who lost their data have every rigth to bitch. But shit happens and to fix the problem in the most cost-effective way is also in the interest of customers. I am really more comfortable spending 5% more on batteries (if the battery life is really affected) than having to buy the next unit at $50 more.
You're no longer in touch with your job description, and have forgotten exactly what it is that you're supposed to be doing for your company and your public.
Well, I think he is doing exactly what the company told him to.
On your webpage you say you are working as programmer for an ISP (btw, your server doesn't seem to recognize that there is an index.html in the directory). Are you really, really sure that your customers never lost a cent due to screwup on your side? If yes, come to Europe, the company where I work needs such people - actually we have yet to see someone like that :-)
Yes. And being software developers and not diplomats the language used is not always the most polite in the world - I personally think it is fully OK, but not everyone thinks so. I am not a kernel hacker, but I already have the experience of being flamed down by one of the gurus (well - he was right :-)), after which I responded by sitting down for a day and identifying a though bug in his code :-) Someone else might respond with "Fsck you" and never again read l-k.
The current discussion regarding ReiserFS is not very significant, although it would be sad if it ended with Hans giving up his high-quality work. What bothers me more is that IMHO we are approaching a limit where the current way of project management won't work in the long term and there is very little being done about it. Just a few points:
- There is no version control system - instead we play games with x.y.z-test-pre-ac-aa-whatever and if something goes wrong, we binary-search the exact version where it happened instead of getting clue from changelog.
- There is no issue tracking system (the TODO saga on the l-k is better than nothing, but...).
- The design papers are missing (even a separately archived and publicized relevant mail threads would help).
- There is no regression testing (no doubt the developers of the particular subsystem have something, but it is not readily available).
Some problems were identified and adressed - the big delay between 2.0 and 2.2 due to missing definition of the target feature set and (hopefully) the horrible state of 2.2.0 when it came out due to allowing non-bugfix changes in the last pre-versions. Alan Cox does a great job at integrating and testing the patches.I hope that when the 2.4.0 comes out, the core developers will look back and discuss what can work for next years and what cannot.
Dick size contest? Sometimes maybe but I see it more like best bang for the buck contest - my system with 2 Celerons 433 @ 507 MHz (perfectly stable also at higher speed but I prefer the safe side) was a lot cheaper as the same with non-OC P II sometime last year.
As everyone following the Linux kernel development knows, if it compiles, it's good, if it boots, it's perfect.
The Intellisense absolutely rocks. However it is not only IDE what counts. I personally can live with vi, make, ddd etc. But it is plenty of mature tools available for M$ environment that makes a difference. Try to profile your code with gprof and then try to do the same using Rational Quantify. Try to make a coverage analysis without recompiling your code under Linux. Try to catch memory errors with ElectricFence - due to how it works it will eat all your memory in a few seconds in all but trivial programs.
Yes, the tools are expensive, but they save a huge amount of time.
I own a Mozilla T-shirt. Unfortunately I can wear it only in the community where people know about the Mozilla logo. All others will see a red star and instantly connect it with the communist symbol.
This is not to say I am against the symbol itself, you just can do nothing against the implications of using it.
Just yesterday a hungarian plane returned to Prague shortly after takeoff and made an emergency landing after reporting a fire alarm - fortunately a false one. The media speculate about cell phone involved - we probably never find out whether this was indeed the reason.
We are using unixODBC at the company. We are using ODBC mainly to be able to have single source under Win (native ODBC, several possible databases) and Linux (PostgreSQL only at the moment), so I cannot speak on cooperating with other databases, but the Web page mentions some solutions.