With time zones you can simply look up the time at a given location to know which part of the day it is, time corresponding to a part of the day is extremely useful, especially when you're moving through different countries or working with foreign people. It's much easier to change the time zone of your clock than to adjust to a day that starts at 16 o'clock. The different time zones give you more information, and given that most electronic devices can convert between them easily and display multiple at the same time, it's not really harmful.
DST is the beast that needs to die, because it makes it hard to represent the exact time me with the local time plus a simple offset. After DST dies, we should try to deal with unusual time zones that do not match the local solar mean time that you have in countries like Russia or offsets that have half an hour in them like you have in Iran.
If time zones make it difficult for you, work on the better integration of the tools dealing with them.
That's not a fault of Real Networks alone, but of proprietary software in general. You can't predict in advance which company would do that to you. You really can't. If you're using some piece of proprietary software you need to be ready, at some point in the future it might stop being supported, you might not receive important updates or it might get disabled for you.
You're exaggerating the problem, though. It's natural and it happens with everything. For one, to a lesser extent it's also true for free software and hardware devices -- almost everything eventually reaches its end of life and stops being useful, you can't expect to use anything that you've bought forever. You got the software, it was useful for you for the time it was available. Great. It stopped working, OK, that's not good, but it doesn't diminish its usefulness and you should have known it was going to happen the day that you bought it. Even more so when it was a proprietary package.
How do you enable SSL for "some users"? It means you have to send your credentials over an unsecured link until your secure connection kicks in, which is insecure. Even trying http before trying https is considered unsecure -- even if the cookies are correctly set to require require SSL, you reveal what site are you connecting to, possibly what URL from the site you're trying to access, etc. Verifying which user it is *before* enabling SSL sounds like a very bad idea.
Enable it for everyone, set the cookies to SSL only, make sure that all links are a permanent redirect to the SSL version, and encourage users to use https URLs when they send links, keep bookmarks or try to access twitter. Possibly issue a warning for a set of the possible URLs.
Out of a dozen patents that should be either invalid or are invalid, the fact that the court recognized one as valid is still a loss, even if it is a small one. This is a victory for Apple, even if they "lost".
Try reporting it against LibreOffice then, another management, another attitude towards bug reports. It's much more likely that your issue will be fixed, and by the way that's one of the reasons why LibreOffice is a good idea – fixing what's wrong with OpenOffice.org.
Just because it is a text browser with very little features doesn't necessarily make it safe, although the chances for a vulnerability are lower under the *same* conditions.
Because it doesn't work? There is no generic LaTeX to HTML convertor out there, and all of them handle only specific use-cases.
In particular, all convertors either try to parse part of the LaTeX code or try to interpret the DVI that is produced as a result. With the first approach you'd have to limit your use of packages, because otherwise the convertor will fail unless it's a complete LaTeX implementation. With the second approach you won't be able to use XeLaTeX because it doesn't produce standard DVI files, and instead produces a new extended format which is not supported by any other tools yet. And you should really be using XeLaTeX for serious work.
latex2html uses the first approach, and it fails to work with documents that use UTF-8 international characters, and if it will fail particularly spectacularly if you use some more interesting packages.
The best approach is to use a subset of LaTeX that you can safely convert to another format, using tools written by yourself is actually easier than using the tools that are available, because the tools available also handle only a specific scenario, only that you don't know which one. I have my own personal simplistic format that I convert to XeLaTeX code and I plan to create XHTML convertors when I happen to need them. It's really simple, I have a few macros that I replace with XeLaTeX code and a template.
Not only does it prove that the security contractor didn't provide any security, the leaked data also seems to suggest the same. From the comments at TPB: "hey, I was just looking at file 23223140 003.pdf and it looks like someone is getting WAY over billed on the materials. is it just me or are they charging $500 for a $30 wrench?"
The way things in the KDE world are done, soon you'd be most likely able to configure your desktop to look exactly like Unity if you like, without that being the default or only choice.
Million? Try billion. Or many billions. That way it would be comparable to launch prices, and to the price of putting it in higher orbit which would be the only way of not deorbiting it.
The coil will weight less than a horseshoe, but how big would it have to be? What about the cryogenic cooling facility? How much does the superconducting wire cost? Can you give an example of such coil that can be used on an aeroplane? I mean, if there was cheap technology to store electrical energy that was feasible for vehicle and aircraft use, we'd be using it, and electrical cars wouldn't be relying on incredibly expensive LiON batteries now. I haven't heard of one yet.
From TFA: 'The power capacity of battery technology, he continued, would have to grow by “at least a factor of four before we are near where we need to be to accomplish this.'
This is when electric aeroplanes would become really feasible.
Vibrations going through solid objects are called sounds. And in A/V streams, you'd often have the sound and the video being taken from different viewpoints. If you're watching someone doing a spacewalk, would you be bothered that you can hear what they are saying (through the microphone in the suit), even though the camera is almost floating in deep space and not hearing anything?
Slashdot Mirror
With time zones you can simply look up the time at a given location to know which part of the day it is, time corresponding to a part of the day is extremely useful, especially when you're moving through different countries or working with foreign people. It's much easier to change the time zone of your clock than to adjust to a day that starts at 16 o'clock. The different time zones give you more information, and given that most electronic devices can convert between them easily and display multiple at the same time, it's not really harmful.
DST is the beast that needs to die, because it makes it hard to represent the exact time me with the local time plus a simple offset. After DST dies, we should try to deal with unusual time zones that do not match the local solar mean time that you have in countries like Russia or offsets that have half an hour in them like you have in Iran.
If time zones make it difficult for you, work on the better integration of the tools dealing with them.
That's not a fault of Real Networks alone, but of proprietary software in general. You can't predict in advance which company would do that to you. You really can't. If you're using some piece of proprietary software you need to be ready, at some point in the future it might stop being supported, you might not receive important updates or it might get disabled for you.
You're exaggerating the problem, though. It's natural and it happens with everything. For one, to a lesser extent it's also true for free software and hardware devices -- almost everything eventually reaches its end of life and stops being useful, you can't expect to use anything that you've bought forever. You got the software, it was useful for you for the time it was available. Great. It stopped working, OK, that's not good, but it doesn't diminish its usefulness and you should have known it was going to happen the day that you bought it. Even more so when it was a proprietary package.
How do you enable SSL for "some users"? It means you have to send your credentials over an unsecured link until your secure connection kicks in, which is insecure. Even trying http before trying https is considered unsecure -- even if the cookies are correctly set to require require SSL, you reveal what site are you connecting to, possibly what URL from the site you're trying to access, etc. Verifying which user it is *before* enabling SSL sounds like a very bad idea.
Enable it for everyone, set the cookies to SSL only, make sure that all links are a permanent redirect to the SSL version, and encourage users to use https URLs when they send links, keep bookmarks or try to access twitter. Possibly issue a warning for a set of the possible URLs.
I don't worry about Hurricanes, I have TornadoGuard on my iPhone.
It's still bad that such simple idea is patentable according to the court.
Out of a dozen patents that should be either invalid or are invalid, the fact that the court recognized one as valid is still a loss, even if it is a small one. This is a victory for Apple, even if they "lost".
http://worldwide.espacenet.com/publicationDetails/description?CC=EP&NR=2059868A2&KC=A2&FT=D&date=20090520&DB=&locale=en_EP
Try reporting it against LibreOffice then, another management, another attitude towards bug reports. It's much more likely that your issue will be fixed, and by the way that's one of the reasons why LibreOffice is a good idea – fixing what's wrong with OpenOffice.org.
Perhaps schools and workplaces can grow up and not cause a panic over an educational image that somebody might shocking showing up on the screen?
You mean that the Death Star is younger than previously thought? Woah, what destroyed Alderaan then?
An empty start is what you have anyway – you start by downloading a browser over a non-secured link that trusts a given list of CAs.
Is IE9 safer than Firefox + NoScript running on a non-Windows operating system that's less targeted by malware authors?
While Lynx is probably very secure right now, it has seen a security hole or two: https://secunia.com/advisories/product/5883/?task=advisories
Just because it is a text browser with very little features doesn't necessarily make it safe, although the chances for a vulnerability are lower under the *same* conditions.
Sure, it's the responsibility of the developers of the addons to fix the problems created by Mozilla.
We get it, GIMP makes you look like a serial killer.
Because it doesn't work? There is no generic LaTeX to HTML convertor out there, and all of them handle only specific use-cases.
In particular, all convertors either try to parse part of the LaTeX code or try to interpret the DVI that is produced as a result. With the first approach you'd have to limit your use of packages, because otherwise the convertor will fail unless it's a complete LaTeX implementation. With the second approach you won't be able to use XeLaTeX because it doesn't produce standard DVI files, and instead produces a new extended format which is not supported by any other tools yet. And you should really be using XeLaTeX for serious work.
latex2html uses the first approach, and it fails to work with documents that use UTF-8 international characters, and if it will fail particularly spectacularly if you use some more interesting packages.
The best approach is to use a subset of LaTeX that you can safely convert to another format, using tools written by yourself is actually easier than using the tools that are available, because the tools available also handle only a specific scenario, only that you don't know which one. I have my own personal simplistic format that I convert to XeLaTeX code and I plan to create XHTML convertors when I happen to need them. It's really simple, I have a few macros that I replace with XeLaTeX code and a template.
"Flying" could mean "able to fly", not "flying at the moment". And all objects can fly if there's a big enough explosion....
If you're going to ignore the answer to a question, sometimes is best to not ask it at all.
Not only does it prove that the security contractor didn't provide any security, the leaked data also seems to suggest the same. From the comments at TPB: "hey, I was just looking at file 23223140 003.pdf and it looks like someone is getting WAY over billed on the materials. is it just me or are they charging $500 for a $30 wrench?"
Girls do geeks again. However, they are all female geeks. Sorry.
The way things in the KDE world are done, soon you'd be most likely able to configure your desktop to look exactly like Unity if you like, without that being the default or only choice.
Million? Try billion. Or many billions. That way it would be comparable to launch prices, and to the price of putting it in higher orbit which would be the only way of not deorbiting it.
The coil will weight less than a horseshoe, but how big would it have to be? What about the cryogenic cooling facility? How much does the superconducting wire cost? Can you give an example of such coil that can be used on an aeroplane? I mean, if there was cheap technology to store electrical energy that was feasible for vehicle and aircraft use, we'd be using it, and electrical cars wouldn't be relying on incredibly expensive LiON batteries now. I haven't heard of one yet.
From TFA: 'The power capacity of battery technology, he continued, would have to grow by “at least a factor of four before we are near where we need to be to accomplish this.'
This is when electric aeroplanes would become really feasible.
Don't underestimate them.
Vibrations going through solid objects are called sounds. And in A/V streams, you'd often have the sound and the video being taken from different viewpoints. If you're watching someone doing a spacewalk, would you be bothered that you can hear what they are saying (through the microphone in the suit), even though the camera is almost floating in deep space and not hearing anything?