80 karma · joined June 1, 2011
> Optimization flags in general should not change visible program behavior, except for performance.
The only behavior you would be able to observe before, that you wouldn't after disabling overflow behaviour, is a crash, and you would have fixed that anyway as soon as you observed it.
Of course, if there is $370 Million on the line, maybe just disable it and hope for the best :-)
For those who don't know, that's the Liskov Substitution Principle [1]
[1] http://en.wikipedia.org/wiki/Liskov_substitution_principle
I expect he had connections and/or was able to bribe his way towards becoming a tour guide. Tourism, after all, is a foreign currency earning industry.
I'm working on something similar: https://wikidocs.com. Although our's closed source at the moment (can't say whether or not it will remain closed), we will provide a downloadable package you can run yourself.
I found his use of the word "crisp" very interesting. I believe it means to keep your code short and to the point, without any extra embellishment.
FYI
The best resource I found so far is http://www.dailynk.com/english/ . At least one more story like the OP's can be found here http://www.dailynk.com/english/sub_list_last.php?page=1&...
There is an organization that tries to do something about this http://libertyinnorthkorea.org/ . They have some videos as well that are worth watching http://www.youtube.com/user/linkglobal
Now, with the GPLv2, it is possible to use Aloha freely in most websites/webapps. You don't distribute your website/webapp and therefore are not bound by the GPLv2 to divulge your website's source code.
The GPLv2 _would_ take effect if you distribute your website in the traditional sense - a package that someone can run himself.
(IANAL and can't speak for Gentics etc.)
I expect the size would be around 300KB if only the basic plugins are included.
Still, it's a lot bigger than redactor - point taken.
Drupal is interested in integrating Aloha, and we are currently discussing several improvements that would be necessary for them. Have a look at the issue tracker. I think the UI À la carte and accessibility will be the next big user-visible developments.
Datomic is a commercial database system developed in Clojure. The peer library is what you use in your client application to query the Datomic server. The peer library is written in Clojure. I expect that means calling Clojure from Java, and including the Clojure runtime jar in a client application, is safe/stable/supported enough to build a business on top of it.
I'm still learning though, so take what I said with a grain of salt.
I wrote a simple implementation that uses google closure templates to pre-render the page with dynamic content on the server, and to me the app felt more stable. This feeling may be entirely subjective, as I didn't make any actualy measurements.
A counterargument may be that this approach does not scale and would overload a server resulting in worse stabilit/render-time in the end.