Spaces are always one character, tabs can be interpreted differently on different platforms/editors, etc. I use spaces, so I know exactly what the code will look like in any monospaced font. M-x untabify and C-M-\ fix non-compliant code nicely in emacs. Interesting correlation with salary, but I don't think there's any specific causation.
It wasn't too long ago that Firefox was viewed as an amazing browser (ob: https://xkcd.com/198/ ), far better than the alternatives, and FOSS to boot. But like it's predecessors, it got slow, bloated, and bogged down in trying to implement features too far outside the core mission of a browser. Chrome came along and snatched the performance crown and mindshare.
If you have already conceded that Google is allowed to harvest all your data in exchange for free products/services, then by all means keep using Chrome. However, if you value your privacy, it is time to give Firefox another chance. It really has improved a lot in the last couple of years in terms of stability and performance, to the point where it meets or exceeds Chrome in every aspect. Give Firefox an honest chance, you might switch back.
Another "me too" vote for Qt. It's a well-designed, cross-platform, highly-stable framework that is appropriate for a wide-variety of development tasks.
The gas tax is $0.30 per gallon. Instead of paying that $0.30, I can choose to pay $0.015 per mile traveled. Paying per mile, I can only go 20 miles for $0.30. Unless I drive a gas guzzler that averages less than 20 mpg, I am being taxed more.
Plus this removes one of the benefits to driving an efficient or alternative fuel vehicle.
Plus (as many prior posters have pointed out), weight of a vehicle is proportional to the amount of road damage it causes, and would be a far better metric for assessing taxes to repair roads.
Dumb.
What kind of diesel engine truck do you have? Most consumer diesel engines (including mine) are direct injection, at least in the U.S. They intake air, compress it, and then inject the fuel directly into the combustion chamber (hence the term "direct injection"). It is the heat of the compressed air that lights the fuel. No spark plug required.
I doubt they are trying to get into semiconductor development other than for their own products. And considering Apple has billions in cash, $278M is a fairly small amount, anyway.
Could you provide a link to this information? To the best of my knowledge, if you have a HDTV with DVI that is HDCP-compliant, you will have no problem watching either of the HD-disc formats either now or in the future. If you have a HDMI source, which you want to connect to a HDCP-compliant DVI input for the video signal, you'll need a converter cable, but it should work fine.
Then the next set of adopters bought HDTVs, only to find out they were not HDMI compatible, and therefore, couldn't run HD content. So, this new push-back of the deadline gives the content makers and the hardware companies more time to develop a whole new DRM scheme to screw those of you who just bought HDMI compatible equipment.
It appears you are confusing HDMI and HDCP. You do not need to use an HDMI interface to view HD content. DVI works. As does digital component video.
I'm sure if the domestic eavesdropping were a narrowly targeted program, the Bush administration would have gotten warrants from the secret courts and there would be no issue. However, the NSA is likely monitoring a huge range of communications and then mining the data for potential "hits" using voice analysis or some other automated technique. Warrants to monitor specific lines or people don't really make sense unless the "hits" pan out.
The 1978 FISA law is out of date given present day monitoring capabilities. The proper thing to do would have been to try to get that law updated, but in doing so, they would have had to reveal their strategy.
Mind you, I am not supporting what the administration is doing at all. But I bet that's the story Alberto Gonzales will be telling the Senate Judiciary Committee.
Slashdot Mirror
Spaces are always one character, tabs can be interpreted differently on different platforms/editors, etc. I use spaces, so I know exactly what the code will look like in any monospaced font. M-x untabify and C-M-\ fix non-compliant code nicely in emacs. Interesting correlation with salary, but I don't think there's any specific causation.
It wasn't too long ago that Firefox was viewed as an amazing browser (ob: https://xkcd.com/198/ ), far better than the alternatives, and FOSS to boot. But like it's predecessors, it got slow, bloated, and bogged down in trying to implement features too far outside the core mission of a browser. Chrome came along and snatched the performance crown and mindshare. If you have already conceded that Google is allowed to harvest all your data in exchange for free products/services, then by all means keep using Chrome. However, if you value your privacy, it is time to give Firefox another chance. It really has improved a lot in the last couple of years in terms of stability and performance, to the point where it meets or exceeds Chrome in every aspect. Give Firefox an honest chance, you might switch back.
Another "me too" vote for Qt. It's a well-designed, cross-platform, highly-stable framework that is appropriate for a wide-variety of development tasks.
The gas tax is $0.30 per gallon. Instead of paying that $0.30, I can choose to pay $0.015 per mile traveled. Paying per mile, I can only go 20 miles for $0.30. Unless I drive a gas guzzler that averages less than 20 mpg, I am being taxed more. Plus this removes one of the benefits to driving an efficient or alternative fuel vehicle. Plus (as many prior posters have pointed out), weight of a vehicle is proportional to the amount of road damage it causes, and would be a far better metric for assessing taxes to repair roads. Dumb.
What kind of diesel engine truck do you have? Most consumer diesel engines (including mine) are direct injection, at least in the U.S. They intake air, compress it, and then inject the fuel directly into the combustion chamber (hence the term "direct injection"). It is the heat of the compressed air that lights the fuel. No spark plug required.
I doubt they are trying to get into semiconductor development other than for their own products. And considering Apple has billions in cash, $278M is a fairly small amount, anyway.
Could you provide a link to this information? To the best of my knowledge, if you have a HDTV with DVI that is HDCP-compliant, you will have no problem watching either of the HD-disc formats either now or in the future. If you have a HDMI source, which you want to connect to a HDCP-compliant DVI input for the video signal, you'll need a converter cable, but it should work fine.
Then the next set of adopters bought HDTVs, only to find out they were not HDMI compatible, and therefore, couldn't run HD content. So, this new push-back of the deadline gives the content makers and the hardware companies more time to develop a whole new DRM scheme to screw those of you who just bought HDMI compatible equipment.
It appears you are confusing HDMI and HDCP. You do not need to use an HDMI interface to view HD content. DVI works. As does digital component video.
I'm sure if the domestic eavesdropping were a narrowly targeted program, the Bush administration would have gotten warrants from the secret courts and there would be no issue. However, the NSA is likely monitoring a huge range of communications and then mining the data for potential "hits" using voice analysis or some other automated technique. Warrants to monitor specific lines or people don't really make sense unless the "hits" pan out. The 1978 FISA law is out of date given present day monitoring capabilities. The proper thing to do would have been to try to get that law updated, but in doing so, they would have had to reveal their strategy. Mind you, I am not supporting what the administration is doing at all. But I bet that's the story Alberto Gonzales will be telling the Senate Judiciary Committee.