This is a case of should be this way, but never will be. People have and always will respond to personal incentives, which is why framing this way is doing well.
If people are incentivized to get solar roofs for personal benefits and it happens to also help the "Life Economy," this is good. Especially because more people will get them when they're framed in terms of what an individual gains from installing it, not what Humanity gains.
Short summary: Many systems (including Unix) store time as a signed 32 bit int, with the value 0 representing January 1st 1970 00:00:00. This number will overflow on 03:14:07 UTC on 19 January 2038.
It is Y2K-ish; it's "different" so I'm not sure about seriousness. I'm thinking it simultaneously could be easier and more difficult, the standard "it depends" type answer. :)
Y2K is more of a formatting / digit representation problem than a pure data type overflow. The solution for Y2K was to switch the representation of year from 2 to 4 digits, along with coding and logic changes to go along with this.
For Unix / Linux, the solution for the 2038 problem involves changing time_t from 32 bits to 64 bits. At a higher level (eg what's in your C++ code), instinctively I don't think this in itself would involve as many code changes (maybe some data type changes, but probably less logic changes than Y2K, that's my guess). I believe several platforms have already moved towards 64 bit time_t by default... some support this by default even on 32 bit systems, such as Microsoft Visual C++ -- https://msdn.microsoft.com/en-us/library/3b2e7499.aspx
Since this involves a data type overflow issue, though, we're dealing more with platform specific / compiler / kernel type issues. I don't know, for instance, how easily 32 bit embedded type systems could handle a 64 bit time_t value. I understand that there are some technical issues with Linux kernels (mentioned in some of the comments) that prevent them from moving to a 64 bit time_t irregardless of platform (time_t should always be okay on 64 bit platforms, it's the 32 bit platforms that will have the issue...)
The good news is we have 21 years to think about it...
Nothing significant except that the storage spot for unix will fill up. Unix used to use a 32bit variable to store time in seconds since the epoch of 1970, so it will overflow in the year 2038. Most modern Unix systems have fixed the problem already, but Linux has a harder time than the others, and is still working on their fix.
Right but randomly posting in a link to Veblen good on Wikipedia because it's one example of when raising prices doesn't lower demand doesn't mean it's in any way relevant to this discussion. Almost no one would argue that this kind of travel is a Veblen good.
Are you able to keep it enjoyable? Invariably when I ask people who run hobby-based stores selling things like toy trains, comic books, or stamps, they tell me it's no longer fun to them.
Depending on one's perspective, it may be taken as negative or an honest feedback. I am from India and already know about all of these 'breads', but the first thought that came to my mind was the same - how useful this article would have been, had the pictures been real ones rather than their cartoon like representations.
Its not a negative comment, its a constructive feedback. If they had real pics of those items I guarantee you that your brain would tell you to go to the nearest Indian restaurant and get eat all that food.
