Important question for me as well. As a solo amateur developer I don't have time to keep up with the constant development of all the different platforms.
I love the idea of this tool.
This came just at the right time. I'm putting together a series of animations for patient education. In trying to make things cross-platform I had to resort to AE and non-interactive video. Lottie looks like it will enable me to string together something nicer, using native drawing functionality, and can incorporate more interactivity.
what kinds of JVM issues did you run into in deployment? for personal projects I have always used C++, Python, RoR, MEAN, etc. but at work where my role is non-dev, our software dev team likes Java and the heavy weighted GWT... frankly shutting me out. I'd love to know how to convince them to switch out of Java.
No being a computer scientist I have to admit I do not appreciate the intricacies of the 'problems with SQL' blog entries. But working with htsql I gotta say it seems a lot more intuitive than SQL. It feels like the logic correspond much better to my mental model. And that there is much less of the jumping up and down the code to nest my SQL code logic that I find myself doing all the time.
Is there a way to install this on a PostgresQL instance on Win8?
I have found SQL to be cumbersome for expressing temporal relationships, eg find all the event As that happen within one week of event B. There's not necessarily a data schema link between the table for event A and the table for event B.
interesting! that seems to be consistent with my experience. I can never work at my quiet office where just sitting down bores me to tears and puts me to sleep in less than an hour. working at a cafe on the other hand I can go on for hours.
Do you have more info on the introvert/extrovert link?
great points. I've been a big fan and advocate of android for some time. But I've have been disappointed and still am disappointed by how much hardware is necessary to run even basic tasks like getting onto the Internet and reading a static page, how even scrolling through the basic launcher interface stutters, even on the new nexus 7, how switching between apps can take so much time.
it seems that Android as a solution to the problem of a mobile phone is overshooting a big chunk of the market. in that sense I think FxOS is in a good position to disrupt the mobile space.
From teh pov of small teams, I think the most important difference is that GAE takes care of systems maintenance completely. No worries about having someone on call to fix the server, to monitor load, to periodically patch the server software. That is one less systems administrater needed, which can be a significant cost.
The problem with GAE as many have pointed out is being locked-in to the GAE architecture. I'm betting on open source systems built on top of AWS, specifically scalr. Can anyone comment on their experiences with scalr?
"3. The a priori likelihood that your site will be popular enough to demand the scalability GAE can apparently deliver is very low, indeed nil. Are you willing to pioneer on an inconsistent infrastructure when you could use a proven relational one?"
The perceived probability of "getting popular enough" is for most start-ups non-zero. Else many start-ups would not even exist at all. That is, the expected value of the entire start-up endeavor, E(start-up)--say in the unit of dollars--is driven by these rare, but extreme outcomes.
Given this is the case, my impression is that:
P( failure to scale | RDBMS ) > P( failure to scale | BigTable/simpleDB )
(that is, it is much more difficult to scale up RDBMS than BigTable/SimpleDB)
and P( success | failure to scale ) is near 0,
then it makes sense to prepare for that possible rare outcome of having to scale, in order to preserve that expected value.