120 karma · joined July 22, 2012
https://en.wikipedia.org/wiki/Demography_of_Japan
http://www.indexmundi.com/energy.aspx?country=jp&product=oil...
Now I do Python. And with Python I "got" something too : writing tools, coding, etc. is not like mathematics (like Scheme) anymore. It became a social activity. I'm in the field of ERP right now (arguably not the most theory-oriented stuff). It's because I spend most of time using API's by other and making API's in the hope that they will be used by other (none of those API being worth much in terms of computer "science" (stuff like algorithm). I'm also building tools to augment productivity of other people; which is also quite social.
So from the abstract Scheme programming, I've moved to Python social programming. That keeps me happy (I must confess that studying Voronoi diagrams, or 3D structures packing remain what made me really tick :-) )
Eventually, those things will get fixed, but when the damage is done (see asbestos), i.e. when it's too late.
The problem is that market pushes business to make money, not to be virtuous. That's because when a business must choose between "closing" and "going on but being less than virtuous", the business says "I don't have choice, it's either live or nothing", so I choose "live on".
I understand that not all business operate like this. But many people will make that choice because it's practical. Much like choosing between free software (politically fine but economically broken (that's an approximation)) and proprietary software (ok to enslave people but economically viable).
That's the difference between the powerful and the powerless. The powerful thinks the imbalance is a fact that will never change; the powerless thinks that must change.
The problem in corporate world nowadays is that the powerful people disguise this difference all the time. For example : "hey, you can negotiate your salary and if you disagree, you have total freedom to go somewhere else. How powerful you are !"
I'll sure read your book, but I'm under the impression I'll see another, maybe very sophisticated disguise...
(yes you can call me a "socialist" (in the European sense) :-) because all of this is super political in fact)
Hopefully, we'll get better.
Moreover, you're definitively right. I just watch Belgian TV (official channel). And I can say that people (opposed to governments) of Syria, Libya, Palestine,... are 99.99% of the time represented as mourning their death, singing and jumping; or represented with ruins behind them; or with weapons, or as super poor (compared to our materialist standard down here). So it's very hard for us to build a correct representation of what it is to live in the "orient". The web can give more information, but many (I guess) people get their information from mass media.
So yes, it's super biased towards western (ex colonialist) societies... And that's a shame. I'd love to see what's good in Africa, Turkey, south america, china,...
That's basic risk analysis
With that kind of reasoning, you'll favor research for medicine against rare 100% lethal diseases instead of 20%-lethal cancer...
For BigDecimal, my grief is that it makes code horrible (at least in my experience, I'm still locked in JDK 1.7).
BigDecimal has the problem I see with the rest of my griefs : it is possible to compute things correctly with code (obviously), but the way the code is written is ugly (and painful).
BigDecimal yearly_amount = new BigDecimal("1000.00");
BigDecimal daily_amount = yearly_amount.divide(new BigDecimal("12")); // Beware the rounding issue
Wouldn't it be nicer if : money<4> yearly_amount = 1000.00 EUR; // 4 decimals
money<2> daily_amount = yearly_amount / 12; // Beware the rounding issue !
Of course, this notation doesn't help much with rounding, but at least it makes the code easier to read. And trust me, using BigDecimal, doesn't prevent many people of making mistakes with rounding.Of course one can make computation on those types, but it is so un-natural that it scares me :
* BigDecimal for currency, let me laugh * Date/timestamp without proper casting rules * Types towers with inheritance, generics, etc. Pfff... * Still no fine library to represent an address * Representing mutable ordered lists in SQL databases is still quite painful (possible, sure, but there's so boiler plate code to write)
So the data representation/manipulation problem, which goes with the data longevity you observe, that's something to learn about...
There's no reason to love current programming languages :-( (but I do love Python :-) 3 of course :-))
But to me, Seneca is not an issue. What he wrote reminds me of my humanity, encourages me on being a better me in the way it pleases me.
So, even after reading the long article, I still prefer the subjective picture I have of Seneca rather than his actual history. I'm human :-)
This guy's energy would be better spend at tackling the economical and political problems we have to solve to actually improve the situation... And we need more than a dream...
(now that's a bad joke)
Could you elaborate on this ?