OverAPI

Roughly a million API cheat sheets.

Harp

Harp looks like a nice static site generator/server for modern languages and approaches.

More frameworks!

More frameworks compared! Begging the question of when I'll write my metaframework.

Riot.js

Riot.js is a JS framework that minifies down to about a single kilobyte. And has a nice, clean structure as well.

Command lines in the browser

A lot of the tools I build for my own use are command-line-based (the various perl Shell modules are pretty useful and very quick to put together), so lately, since REST APIs seem to be a really nice way to build new functionality, I'm thinking, how can I do a command line in the browser?

Seems I'm not the first. Blue Sky on Mars posted on this topic in 2011 and even started a Google Group (which unfortunately didn't last too long).  These were more focused on shell replacements, though, which is more than I want or need.

But hey - Josh.js is perfect. And the examples are easy to understand. Add this to a Mojolicious backend and I think I've got a pretty snazzy way to organize functionality.

Kapi

Some sort of framework for building PHP-based RESTful APIs, apparently. I like this for its semantic flavor.

JS framework popularity

An analysis of Github Archive to gauge popularity trends in JavaScript webapp frameworks. I love this stuff.

Web frameworks and architectural description language

I've been toying with Mojolicious lately, gearing up to get over my fear of complexity and jump in with some simple UI for some little projects.  There's a great Flask megatutorial series I'd like to follow along with, reimplementing the various steps in Mojolicious. (See also this example blogging app in Mojolicious::Lite.)  But "porting" a tutorial begs trips the usual circuit breakers in my mind:

Namely, a Flask webapp and a Mojo webapp are both projections of the same abstract webapp, and what I really want is to describe that abstract webapp in a higher-level language.

I should really just no longer call it Decl.  I should just call it Hylaea right off the bat.  [pause]  Yeah, that name is pretty uncluttered!  There's a guy in Paris calls himself Hylaean (tweets some interesting stuff, not a lot of activity on Github and it shows he prefers the MS ecosystem - a guy worth following, actually) but that's about it outside the Anathem Wiki, and "Hylaea" without the 'n' is free as a bird.

Anyway, there is a semantic abstraction of the notion of the webapp that can be expressed in Mojolicious or in Flask or in, you know, any of the thirty thousand other webapp frameworks out there, am I right?  But the abstraction, at some level, is the same for all of them, it's just that by working in one or another stack or language you might be led in different directions in development due to the affordances of the environment (that's a cogsci term I find particularly apt here).

That stack/language/environment/ecosystem is what we call the architecture on which we're developing a given app - but the way we think about the structure of the app or program or whatever (because this obviously goes way beyond webapps) is some kind of shared semantic structure that I think is amenable to externalization.

Note, of course, that the specific description of a particular architecture or app is a kind of "skeletal form" - because it doesn't encode all the knowledge about a thing, it just identifies it and evokes the library of concepts stored in the (getting back to Hofstadterian research here) the Lexicon.

Meditation prompt: is there a difference between Decl and Hylaea?  I kind of think there is.  Decl is an interpreter in Perl for declarative structures, but remains a pretty Perly thing.  Logic is still represented in Perl, for example.  Hylaea might be the overall programming system or something. Let's consider this for a while.

Effective Django

Here's a good tutorial.

Web framework benchmark

Wow - here's a pretty amazing graph comparing speed of trivial JSON serialization of a freshly created object over about twenty different frameworks.  There's a huge spread.

On that note, let's get a Web framework link dump here, OK?

• Flask Megatutorial - a series on Flask that I think I'm going to work through.
• Getting started with Django
• and Django Best Practices

Play: Web framework

Play is a Web framework for Java/Scala.

Junior: native-look mobile HTML5 framework

Boilerplate!  I love this stuff.

Backbone boilerplate

How to start writing backbone server-side JS.

Noir

Deprecated, but interesting: a Web not-quite-framework in Clojure.

Punch

Punch is yet another static content builder, and looks pretty neat.

This post is tagged "Web frameworks, build systems, boilerplate".  It's interesting to see those tags converging.  Very interesting.

roots toolbox for web products

roots is a static site compiler written in node.js.

Rewriting Reddit

Thoughts by Aaron Swartz on the occasion of the Reddit rewrite from Lisp to Python using his web.py.  The short version is that Python does have a lot of frameworks [see], but that they all suck, essentially.  He has some interesting things to say about Django, for example.

How to build a Web app from scratch

Boilerplate! [github]

Base components: Coffeescript, jQuery, Underscore, Backbone, Handlebars (template engine), Less, WordPress API for content entry.

Nice overview!

A Django REST framework

APIs and Web frameworks: a Django REST framework.

Django drip

A good real-life, but small, Django application that's open-source and thus ready for understanding, Django drip is for management of email drips.