lucperkins

8 ms·

31.
by lucperkins 14y ago
Try going into the console and seeing if the app is running anyway. Sometimes 500 errors spring up superfluously, even when things run fine. A small hiccup that we're working on aggressively.
32.
by lucperkins 14y ago
You could say that. But it should be noted that what is currently free will always be free.
33.
by lucperkins 14y ago
I think that that's a good description overall, although I would add that the free plan allows deployment to all currently available IaaS and hence to do things like run analytics on the different infras to see what works best. But I would
34.
by lucperkins 14y ago
The "etc." simply means that we're looking to expand the number of database options over time beyond this list
35.
by lucperkins 14y ago
Java documentation is on the way soon
36.
by lucperkins 14y ago
True, there are still glitches to be worked out. We just entered general availability a few days ago. I would encourage you to give it another shot. Errors of this sort tend to arise somewhat randomly.
37.
by lucperkins 14y ago
Support for Redis is indeed on the way and a very high priority
38.
by lucperkins 14y ago
There's no mention of disk usage because it doesn't matter and has no effect on price. Pricing is based solely on RAM usage. The thing is, economies of scale in the infrastructure space have made this kind of pricing model extremely feasibl
39.
by lucperkins 14y ago
Yes. There are also plans to expand to Amazon-Tokyo and Rackspace-Hong Kong
40.
by lucperkins 14y ago
They might indeed do that. We'll see. Meanwhile, AppFog will be up and running on dozens of data centers by the end of 2012. Those currently available are just the beginning.
41.
Other amazing entries from the OpenStack contest(blog.appfog.com)
1 points by lucperkins 14y ago|0 comments
42.
The winners of the AppFog/OpenStack competition have been announced(blog.appfog.com)
2 points by lucperkins 14y ago|0 comments
43.
by lucperkins 14y ago
My point wasn't that these things don't exist in other languages. Again, I'm not saying that PHP is objectively better than anything else. I know not to play that game. All that I'm doing is remaining steadfast in my claim that PHP doesn't
44.
PHP's brighter future? On the "PHP the Right Way" project(blog.phpfog.com)
15 points by lucperkins 14y ago|14 comments
45.
Daniel Clifford on Optimizing JavaScript for the V8 Engine(blog.appfog.com)
1 points by lucperkins 14y ago|0 comments
46.
by lucperkins 14y ago
That's a good point. I hadn't seen things quite this way. But you're absolutely right about complexity being a potential problem. For basic CRUD apps, it seems to me like traditional MVC is absolutely the way to go, hence my bristling at th
47.
Putting the MOVE framework in proper perspective (blog.appfog.com)
2 points by lucperkins 14y ago|2 comments
48.
LinkedIn brings some sanity to the node.js debate(blog.appfog.com)
2 points by lucperkins 14y ago|0 comments
49.
Without them your app is a wafer in the wind: on data models and persistence(blog.appfog.com)
3 points by lucperkins 14y ago|0 comments
50.
NoOps is a New Ops: AppFog is an Ops Company(blog.appfog.com)
1 points by lucperkins 14y ago|0 comments
51.
Infrastructure Neutrality is a Now an Absolute Necessity(blog.appfog.com)
1 points by lucperkins 14y ago|0 comments
52.
The developer's toolkit: CoffeeScript(blog.appfog.com)
2 points by lucperkins 14y ago|0 comments
53.
Twitter Bootstrap and the rise of total front-end frameworks(blog.appfog.com)
2 points by lucperkins 14y ago|0 comments
54.
by lucperkins 14y ago
No. Sometimes I spend a lot of time and effort seeking out niche genres and digging through blogs and news sites to find "good" music. But sometimes I don't want to put in all that effort, and then putting on "Kind of Blue" or the first Wee
55.
by lucperkins 14y ago
But how often does trying-to-be-better-and-failing come along and torpedo good-enough-for-the-job?
56.
by lucperkins 14y ago
Culinary powerhouse? No. But it is undeniably a powerhouse in delivering food consistently and reliably.
57.
by lucperkins 14y ago
This is true now, but Dart is also less than a year old. I don't have strong feelings toward Dart either way, but these things have a gestation period. Internet Explorer didn't support JavaScript at first either, and Safari and Chrome didn'
58.
by lucperkins 14y ago
Agreed on what you said about writing scalable, secure web apps. No question about it. But I should say as an aside (and you wouldn't necessarily disagree, I don't think) that these kinds of problems are not exclusive to PHP. JavaScript get
59.
by lucperkins 14y ago
I use words like "might" very intentionally! And yes, right you are that my conclusions about things might change radically. I'm already appalled at some of the things that I thought even weeks ago...
60.
by lucperkins 14y ago
Then double freaking high five :)

More ›