265 karma · joined April 7, 2011
PS. Anyone who bemoans the lack of "ribald proletariat banter" without a trace of irony is putting themselves squarely in the sights of the same banter ("wanker"), IMO.
- I like the default keybindings for pretty much everything
- I like that the concept of a buffer is not connected to the concept of a window or frame or anything. That I can have the same buffer open twice in separate windows is useful.
- It's cross platform & I can be productive on remote servers if necessary.
My least favorite days are when I need to customize something and rather than it taking 15 minutes it takes 3 hours as I refresh my memory on elisp. I would prefer to spend this time being actually productive.
Plugging the Raspberry Pi in and having it display immediately on the TV almost brought tears to my eyes. Maybe the situation is improved for the BeagleBone?
I feel like the same thing applies to Excel. Essentially what gets built with Excel are small programs where all the variables are unnamed, everything passed around is a numerical value and there's almost no capacity to see the entire 'program'.
These always get built because Excel is easier to start with (and you can always pass an Excel spreadsheet around and let other people 'run' it), but it means in the long run with the bigger programs you hit exponential complexity pretty quickly and by then you're invested in Excel, even though R or Pandas would have been more appropriate for the size of the program. Just my two cents (coming from businesses that LOVE excel for completely insane purposes).
Kids can still have a fully working linux system hooked up to their tv for $35, which regardless of the OSS status of the hardware is still a win for education in my opinion.
Fyi, debug is still on for your chartulo.us site, after watching the animated typing produce a url, that url leads to the django yellow 404 :)
This is my sticking point: if the power comes from the recipes, how does having a web interface help any of that? I think this is a great piece of work, but I just can't see what the advantages are over any of its competitors given that all the actual work is still being done in the same way (e.g. shell scripts).
I would add that you bring up GitHub a number of times as a comparable service, but I think that the key difference is that a number of core git features are actually implemented by GitHub (e.g. fork, log, pull) and although this all looks great it isn't the reason (IMO) why it's successful, it's because it makes a common operation easier (i.e. git repository management). I think that you would need to make common dev-op "recipes" easy to generate before the GitHub comparison is correct.