lucperkins

11 ms·

61.
by lucperkins 14y ago
I think that Sinatra will become increasingly popular within the Ruby community (and financial help from Heroku/Salesforce can't hurt!), but I also think it's interesting that the micro-frameworks inspired by Sinatra (Flask for Python, Expr
62.
by lucperkins 14y ago
Absolutely agreed. I really love JavaScript for a lot of reasons, but it still astonishes me that that our lingua franca was designed in 10 days. In 1995. For NETSCAPE. I'm not so sure I would describe the mishmash as unambiguously depressi
63.
by lucperkins 14y ago
1. I wouldn't want to do anything at a meaningful level of complexity without templates. No question about it. And I think that having so many templating frameworks is wonderful (ERB, Jade, haml, etc.). I was only arguing that PHP lets you
64.
by lucperkins 14y ago
I agree, but just out of curiosity: what do you think would be the language of choice beyond JS for the browsers of the future? I honestly don't have a clue. I might guess Python because it's so big at Google and Chrome is already more or l
65.
by lucperkins 14y ago
Right right right. I would add this: Ruby could well be considered "passé" someday (history tells us it necessarily will be), and the Rubyists of the future would really bristle at the suggestion that what they're doing is worth less simply
66.
by lucperkins 14y ago
Exactly. Correspondingly, my hope (along with one of the folks below) is that advances in hardware will obliterate any speed difference and enable the back end to be king. Time will tell.
67.
by lucperkins 14y ago
You could be right about these numbers becoming meaningless. But in the meantime, there is a noticeable difference, and that can mean life or death in the jam-packed web dev market that we see today. If cramming as much application logic as
68.
by lucperkins 14y ago
Nice to see PHP get some love from polyglots!
69.
by lucperkins 14y ago
No, "absolutely everywhere" is not an argument by itself. But sometimes ubiquity is earned. If Facebook powered its front end using FORTRAN, I would call it a quiet powerhouse, too!
70.
by lucperkins 14y ago
I certainly didn't mean to say that languages like Python and Ruby are inflexible! What I meant to say is that you can't use either of them in direct conjunction with HTML the way that you can use PHP. This was what I meant when I said "gen
71.
by lucperkins 14y ago
Well said. RESTfulness will ALWAYS have its place, and blogs are the example par excellence. Even in Node, which prides itself on its async/non-blocking capabilities, there are all kinds of ways to incorporate REST.
72.
by lucperkins 14y ago
And now I'm doing some research and finding Catalyst and others. Looks like there's more going on in Perl web dev than I realized. Foot.in.mouth.
73.
by lucperkins 14y ago
That said, I am indeed among the people keeping my fingers crossed for a Perl renaissance in web development.
74.
by lucperkins 14y ago
Maybe. I actually like Perl a lot, and there are lots of things you can do with it that you'd never want to use PHP for. The difference is that in the world of web development (and this is the crucial distinction here), Perl has neither the
75.
by lucperkins 14y ago
I'm not convinced that it will fade, especially given the rise of mobile devices (as the gentlemen has already pointed out) and what I expect will be a marked improvement in browsers in the coming years (Google Chrome/V8 is a good example).
76.
by lucperkins 14y ago
"Scalable, reliable and robust." Couldn't have said it better myself. Thanks.
77.
by lucperkins 14y ago
I think you're right about a lot of things. Things like Backbone (which I wrote about at http://blog.appfog.com/putting-some-mvc-meat-into-your-app-b... ) will make recourse to the back end more and more selective as time goes by. JavaScri
78.
by lucperkins 14y ago
It depends on how you define powerhouse. Is PHP my favorite language or framework? No. But the use cases I provide show that it's worthy of consideration. Perl, on the other hand...
79.
by lucperkins 14y ago
1. The gentleman's comment was indeed quite curious, and I wish that I could have used this info as a comeback. Thanks! 2. Direct HTML embedding could be seen as a weakness, yes, but that all depends on the kind of project. That's why I des
80.
by lucperkins 14y ago
You're quite right that the analogy isn't perfect. The point I was trying to make, though, is precisely that PHP development can proceed without any recourse whatsoever to a framework. Jumping straight into web dev without an accompanying f
81.
PHP: the quiet powerhouse(blog.appfog.com)
89 points by lucperkins 14y ago|134 comments
82.
by lucperkins 14y ago
A good example for you might be the "jQuery: Novice to Ninja" book. It cuts out a lot of the BS that makes other books annoying and cuts straight to the chase of DOING. Think of a group of sample projects, or maybe even think of a single pr
83.
by lucperkins 14y ago
I agree, although I would argue for making JavaScript your primary language for web development, especially in light of (a) the possibility that has emerged in the past few years of running JavaScript on the front and back end (I'm referrin
84.
by lucperkins 14y ago
Well, Backbone as it stands doesn't really allow you to have these kinds of app-in-itself unities capable of communicating with one another. Clearly, this isn't for everyone and for all purposes. Backbone is "fine as it is" for plenty of th
85.
You’re a polyglot. Shouldn’t your PaaS be polyglot too?(blog.appfog.com)
2 points by lucperkins 14y ago|0 comments
86.
Putting some MVC meat into your app: Backbone.js(blog.appfog.com)
5 points by lucperkins 14y ago|1 comments
87.
Time for Cron in PHP Fog(blog.appfog.com)
2 points by lucperkins 14y ago|0 comments
88.
Venturing beyond Rails: Sinatra(blog.appfog.com)
2 points by lucperkins 14y ago|0 comments