That is correct. You also need to store *when* it was created if you want to handle DST changes in some cases, depending on how you want to use the dates.
I'm not sure you understand what I mean. A UTC time is not affected by timezone or daylight savings time. If you store local dates in the current timezone, it's affected by both. At least twice a year you're screwed for an hour and don't really know what time it is. UTC times can be displayed in any timezone/DST combination you like... they're absolute times. I work on international systems that deal with these problems all the time. Saving times in UTC is the only way that actually solves all of the problems, including people creating data in one time zone and it being used in another.
I think all dates and times should be stored in UTC (not GMT). Storing them in anything that is affected by time zones and DST is just asking for trouble. DST and Time Zone are presentation problems... not storage problems.
If his code is hard to understand, maintain, or add features to quickly to without breaking things, then management better damned well deal with him, as what you're describing is not 'good code', whether it works or not. On a complex project, I'll take maintainable but not all features completely working for quite a long time over everything working but unmaintainable. Writing the initial code is the easy part. It's when the first changes need to be made by someone else is when you find out if it was well done or not.
I wish it was an advertisement... I'd buy one. They way it's looking right now, I'll probably buy a Nexus 4 if I can manage to get my hands on one. If Ubuntu gets a decent Linux phone out soon enough without screwing it up I might buy one of those.
Have you not been paying attention to how the 'game' is now played? It's now more about suing people than actually making products that people *want* to use.
I'm sorry, but accessible mass storage is an anachronism? So, users are *supposed* to be forced to access their devices through proprietary clients only, forcing them to be tied to single marketplaces, 'approved' OSes, etc? Somebody's been drinking the Apple Kool-aid.
I'd rather have a pure hardware platform that can do anything, try it at a series of things and see what it's most useful for. That's how actual creativity and innovation happens. A 'targetted' product is a more limited product. I'd like to see things run as open platforms, not appliances.
I think people are missing the point of the 'Metro' interface. It's not about the interface... that's just the excuse. They want to lock down the software market and get a cut of all the sales, plus more control over what's installed. Metro will stay. The older interface will become less and less useful... more and more crippled. They want what Apple has with iOS. Even Apple wants what they have with iOS and is doing the same thing with OS X.
I'm not sure why you disagree with me... DAS keyboards use mechanical switches. They would be one of the first ones I'd recommend. There are gaming keyboards that are a bit cheaper, but DAS makes a well-known, reliable product.
Slashdot Mirror
I think pretty much everyone would rather have them on vanilla Android.
That is correct. You also need to store *when* it was created if you want to handle DST changes in some cases, depending on how you want to use the dates.
I'm not sure you understand what I mean. A UTC time is not affected by timezone or daylight savings time. If you store local dates in the current timezone, it's affected by both. At least twice a year you're screwed for an hour and don't really know what time it is. UTC times can be displayed in any timezone/DST combination you like ... they're absolute times. I work on international systems that deal with these problems all the time. Saving times in UTC is the only way that actually solves all of the problems, including people creating data in one time zone and it being used in another.
Other than that fact that good unit tests would have caught this problem, not much.
I think all dates and times should be stored in UTC (not GMT). Storing them in anything that is affected by time zones and DST is just asking for trouble. DST and Time Zone are presentation problems ... not storage problems.
If his code is hard to understand, maintain, or add features to quickly to without breaking things, then management better damned well deal with him, as what you're describing is not 'good code', whether it works or not. On a complex project, I'll take maintainable but not all features completely working for quite a long time over everything working but unmaintainable. Writing the initial code is the easy part. It's when the first changes need to be made by someone else is when you find out if it was well done or not.
I wish it was an advertisement ... I'd buy one. They way it's looking right now, I'll probably buy a Nexus 4 if I can manage to get my hands on one. If Ubuntu gets a decent Linux phone out soon enough without screwing it up I might buy one of those.
Of course, you can always support both.
Have you not been paying attention to how the 'game' is now played? It's now more about suing people than actually making products that people *want* to use.
I'm sorry, but accessible mass storage is an anachronism? So, users are *supposed* to be forced to access their devices through proprietary clients only, forcing them to be tied to single marketplaces, 'approved' OSes, etc? Somebody's been drinking the Apple Kool-aid.
That's a lot of money for space research. . Do they know something we don't?
I'd rather have a pure hardware platform that can do anything, try it at a series of things and see what it's most useful for. That's how actual creativity and innovation happens. A 'targetted' product is a more limited product. I'd like to see things run as open platforms, not appliances.
I think people are missing the point of the 'Metro' interface. It's not about the interface ... that's just the excuse. They want to lock down the software market and get a cut of all the sales, plus more control over what's installed. Metro will stay. The older interface will become less and less useful ... more and more crippled. They want what Apple has with iOS. Even Apple wants what they have with iOS and is doing the same thing with OS X.
Why should he have to? "Innocent until proven guilty" should still apply until the copyright mafias completely buy out the government.
You are correct, propaganda is the more accurate word, but I consider propaganda for a commercial entity to be advertising.
This is more of the ongoing Apple advertising, poorly disguised as 'technology news'.
Someone wanting to try Linux to see what it's like will most definitely see that it's there.
... or let lawyers create a patent system ...
Strange, I use 64 bit Linux pretty much exclusively and use quite a lot of 32 bit software, including Flash.
The KDE developers don't think they work for Apple and seem to listen to what users want.
It's because of attitudes like this that things take so long to improve and people end up getting locked into platforms and formats.
Sorry, duh, that's what you meant. That's twice now. I think I'm having a bad reading comprehension day.
If you don't like Ubuntu, pick a different distro.
Sorry, I misread that ... I thought you said that I returned *to* my DAS keyboard.
I'm not sure why you disagree with me ... DAS keyboards use mechanical switches. They would be one of the first ones I'd recommend. There are gaming keyboards that are a bit cheaper, but DAS makes a well-known, reliable product.