HN user

flashingpumpkin

601 karma

Coder

Posts54
Comments53
View on HN
www.campaignlive.co.uk 9y ago

Brands favoured by Brexiters and Remainers

flashingpumpkin
1pts0
ktoso.github.io 11y ago

Scala's Types of Types

flashingpumpkin
3pts0
blog.silentcircle.com 12y ago

Our Move to Geneva, Switzerland

flashingpumpkin
1pts0
erlang.org 12y ago

A farewell to Erlang

flashingpumpkin
11pts1
peepcode.com 13y ago

Meet Elixir | PeepCode Screencasts

flashingpumpkin
4pts0
sokrat.is 13y ago

Selling your first startup | Sokratis Papafloratos

flashingpumpkin
3pts0
www.indiegogo.com 13y ago

Appcelerator dropped PyDev - PyDev is looking for funding support

flashingpumpkin
1pts0
0101.github.com 13y ago

Python function composition similar to Unix pipes

flashingpumpkin
1pts0
www.slideshare.net 13y ago

Why Erlang? GDC Online 2012

flashingpumpkin
2pts1
summly.com 13y ago

Summly: intelligent news summarisation

flashingpumpkin
31pts29
www.youtube.com 13y ago

Juju - Go in Production

flashingpumpkin
4pts0
community.haskell.org 14y ago

Parallel and Concurrent Programming in Haskell (Simon Marlow)

flashingpumpkin
2pts0
github.com 14y ago

Binary data pattern matching for JS derived from Erlang's syntax

flashingpumpkin
9pts2
ascii.io 14y ago

Ascii.io - Record your terminal sessions

flashingpumpkin
1pts0
vimeo.com 14y ago

JQuery UK 2012 - App development stack for JS developers by Paul Irish

flashingpumpkin
1pts0
www.kashflow.com 14y ago

HOW TO: Network at events. (Hint: Stop thinking about 'networking')

flashingpumpkin
3pts0
www.lostdecadegames.com 14y ago

Onslaught 2 prototype open sourced and on Github

flashingpumpkin
1pts0
joxa.org 14y ago

Joxa - Concurrent Lisp on the Erlang VM

flashingpumpkin
2pts0
palletops.com 14y ago

Pallet, Clojure Dev Ops like Chef and Puppet

flashingpumpkin
8pts1
aviflax.com 14y ago

Review: Clojure Programming

flashingpumpkin
74pts13
angularjs.org 14y ago

AngularJS — Superheroic JavaScript MVC Framework

flashingpumpkin
11pts3
www.clojure-toolbox.com 14y ago

The Clojure Toolbox

flashingpumpkin
7pts0
www.pixelists.com 14y ago

Pixel Art Editor

flashingpumpkin
4pts0
www.veddma.com 14y ago

The Veldt

flashingpumpkin
1pts0
www.mnot.net 14y ago

HTTP Caching Tutorial

flashingpumpkin
79pts6
ship.shapewright.com 14y ago

WebGL Space Ship Maker (and 3d printer)

flashingpumpkin
8pts0
downloads.yellosoft.us 14y ago

The Undiscovered Playground

flashingpumpkin
3pts0
www.caffeinehit.com 14y ago

JavaScript UIs with Sammy, Backbone and State Machines

flashingpumpkin
4pts0
github.com 14y ago

A Clojure talk written in Clojure

flashingpumpkin
1pts0
github.com 14y ago

Beam.js: V8 on top of the Erlang BEAM

flashingpumpkin
2pts0

I've got to disagree with the chapter about settings files. Instead of maintaining multiple different settings for different environments, make your default settings file pull modifications for each environment from os.environ, e.g.:

  STATIC_URL = os.environ.get('STATIC_URL', '/static/')
This is a lot saner and won't descend into a mess that is keeping multiple settings files around. It's also a lot easier to explain.

I think it's also worth linking to David Beazley's Curious Course on Coroutines and Concurrency [1]. It's exploring the ideas of a task scheduler implemented in Python. This article reminded me of it. It's not a full VM, but about half way into the PDF he goes into quite some detail on how to build a task scheduler modelled after an OS and how it works in an actual OS. Give it a read.

[1] http://www.dabeaz.com/coroutines/

The issue I had with Pyjamas is that the whole tool-chain and compilation was a bit borked and the documentation a bit vague. After playing around with it for a day I decided it was too cumbersome so I ditched it in the end and tried py2js which Pyjaco is forked from. Mind you that was 2 years ago so a lot might have improved in that time but it convinced me that writing JS in Python is (was) not really feasible.

I really like that they opted to do everything over SSH in contrast to both Chef and Puppet that need a client/server configuration or at least some of their packages installed locally.

We do all of our deployments with Chef Solo and push our Cookbooks via Fabric over SSH to our servers. Pallet is definitely something to have a deeper look at as I don't like installing more than the bare essentials of what our apps need on our servers for various reasons.

Sigh. I feel your pain. They've deleted the Python SDK unanounced from Github two weeks ago. Not really responsible if you consider there were dozens of watchers and possibly at least as many other sites / projects depending on it. (Also that's ignoring the fact that their docs state 90 days warning period :()

edit Typos, writing on the phone and it's late.

I've got to disagree with you.

It's clumsy, inflexible and restrictive.

Pretty much anything can be swapped out with custom code. Need a custom auth backend? Just write a class. Need custom session backends? Just write a class. Need to customise a certain view of an application? Just override the url. Don't like the ORM? Just use something else. Have special caching needs? Write a backend.

A look at the release notes are full of good things and following them is definitely worth it. Since 1.3 you've got class based views that make it dead easy to create RESTful views for example. There's new logging support, you can have multiple databases with different backends.

The community is pretty much dead.

It's true that there was a lot more blogging happening in the earlier days. I suspect that the community is simply busy building new things - but a look at the CheeseShop shows on any day a healthy amount of new and updated Django components. Right now there are 7 Django projects on the main page.

All my Django projects ended up being a big mess, and I had to undjango my way out of the various restrictions it placed on me.

I'm a big fan of how Django creates structure through its applications. It makes it very easy to build parts of functionality on a plug and play basis and use them across projects.

Django offers a lot of functionality and it can be difficult to pick the right ones being a newcomer. But once you get the hang around applications and repositories and start working with "advanced" Django and Python features and apps like the built in signals, Celery, Fabric, GUnicorn, etc building and deploying apps becomes a breeze.

We've adopted a way that allows us to do basically this:

    mainWindow.menu "File", (err, file)->
        openMenu err, (err, menu)->
            getItem err, "Open", (err, item)->
                click err, item, (err)->
                    getChild err, getChildType("Window"), (err, dialog)->
                        if err? and err instanceof NoFileError
                            # do stuff
                        if err? and err instanceof InvalidClickError
                            # do other stuff
                        if err?
                            throw err
                        # do stuff with dialog if no err
                        
Each function takes as first argument an error and as last a callback. If there's an error, the function just passes the error up the callback stack until it gets dealed with.
    fun = (err, args..., callback)
You can't pull that off if your code is heavily object oriented though:
    mainWindow.menu "File", (err, file)->
        # If mainWindow.menu errors, file is undefined 
        # and the call to openMenu throws an error
        file.openMenu err, (err, menu)-> 
            # ...
Breaking your code/api up with modules instead into classes fixes that.
[dead] 16 years ago

Hm yeah. I second that. My votes didn't have an effect on anything for a couple of months now, which is very disappointing when coming across good stories and comments. Voting degraded for me just to keep bookmarks around in my saved stories. :(

To be honest, most of that stuff works just fine in BASH too.

http://gist.github.com/277975

That's my bash prompt, doing the same. Except, it doesn't factor in mercurial repositories, but that'll be a breeze to add.

Displaying: (<virtual_env>) user@host [ <folder> ~<branch> <* available changes>]$

> - Dont Count on autocompletion (at least not in eclipse)

Tbh, PyDev for Eclipse is pretty darn good. Doesn't fail me on autocompletion, function arguments etc, except for places where objects are created dynamically. Also, I find it very handy being able to navigate to any one places in my $PYTHONPATH with one keystroke on F3 and get the documentation + the implementation to read through. Keeps me away from most documentation sites and inside the IDE.