georgebashi

Sounds like you're after Autodesk's Revit: http://www.autodesk.co.uk/adsk/servlet/pc/index?siteID=45293...

Your link was broken, I found it here: http://en.wikipedia.org/wiki/Wikipedia:Don%27t_use_line_brea...

I've just made the switch after finding out about prezto from this thread. The reason the upgrade process isn't documented is that, unfortunately, there isn't one. You just have to remove oh-my-zsh and install prezto, then move over any modifications you've made manually.

That said, it wasn't much work, and I've been using it for the past couple hours and I really like it!

Received! Thanks! I noticed from your profile you wrote LOGO for python — I did the same for processing! http://terrapin.sourceforge.net/ Great minds :)

This is one of my major annoyances with Dropbox — I'd love to shift everything to my Dropbox, but the slow sync speed is painful.

I signed up a long time ago for an AeroFS invite but had no joy. Anyone got one they could share? I'd love to try this out.

API keys are not the only method of authentication.

I think the point of API keys is so that if you were to build and publish an abusive client (think badly written iOS app), it's easier to stop the DDoS, rather than having to ban thousands of end-user IPs.

I used Droid Sans for a while, but missed having a proper bold variant. Source Code Pro is the first "coding font" I've seen that comes with a decent set of weights (6 from Extra Light to Black), which will be nice for adding some variety to colorschemes.

I hear Asana is good — haven't yet tried it myself, but from reading the docs it looks like it does most of what you're after.

http://asana.com/

I've tweaked mine to this, which includes untracked files, but honours your gitignores:

  let g:ctrlp_user_command = ['.git/', 'cd %s && git ls-files --exclude-standard -co']

It was annoying me that I couldn't open files I'd just created with CtrlP, as they wern't yet tracked.

I started using XSLT about a year ago and had exactly the same initial reaction - it looks ugly and verbose, it's difficult to debug, and badly written code is almost impossible to understand.

A (difficult!) year of daily use behind me, I've found that all the above problems disappear. People come to XSLT expecting a procedural DSL for modifying an XML file which they can pick up in a day or two, and very quickly their code spirals out of control as they try to twist XSLT into what they expect. It very clearly isn't a procedural language, which is why I think it gets labelled as functional, because it doesn't accurately fit either model.

Once you develop good code style and know the pitfalls to avoid, it's perfectly pleasant to use. It's also significantly easier to get along with if you use a full blown XSLT IDE like oXygen, which allows you to breakpoint, see the call stack, and trace back which template generated a specific part of the output.

I agree, but I think this format could work well in certain situations where it can be done automatically, like for comments with karma. You could vary the threshold for hidden comments, so mobile users see less but overall higher quality comments (with a link to show hidden ones), and desktop users see all by default.

I've seen this tip a few times before, but have always wondered: isn't this what the OS disk cache should do? One of the "possible uses" is:

What if you're an internet host and you want to show off your massive bandwidth by having users download a dummy .bin file of 100MB. You'll find that if many users access this file at the same time, your hard drive becomes the slow factor and you're running into disk IO problems.

Surely the OS should keep this 100MB around, rather than re-reading it from the disk over and over? By keeping it in tmpfs, aren't you just "locking" the file in RAM, and defeating whatever "optimal" choice the OS is making over what files to keep around? Isn't this something better done by vmtouch? (http://hoytech.com/vmtouch/)

While it would mean an easy transition, I'm not sure this is the best way either. As others have noted, I've seen odd cases of things performing extremely poorly or failing in strange ways under OpenJDK 6.

Remember, if people have Sun's Java installed now, it's because they deliberately opted to install that over OpenJDK - Sun's has always been in the partner repo, which is disabled by default, OpenJDK being the default on Ubuntu. Silently moving people back to OpenJDK would cause all kinds of non-obvious breakage.

I find GitPop to be really useful for finding the most popular fork. It shows you the number of watchers, forks and issues for each fork, which makes spotting the "best" one a lot easier. It even has a handy bookmarklet!

http://gitpop.heroku.com/

Cherokee is a fantastic server, especially for beginners. The documentation is much more thorough than nginx, which can be confusing at times.

That said, the downside is that cherokee uses a weird config format that isn't very human readable / editable, and doesn't play nicely with version control. This means its difficult to start automating with puppet or chef, as you can't easily template the config.

Because these work out-of-the-box on an installation of Snow Leopard or Lion - or in fact, any machine with python 2.6 and/or libxml2, which includes the latest Ubuntu LTS release.

There's definitely better tools out there if you're willing to install something - but these are great when you're in a pinch.

The github.user and github.token settings aren't used by git, by the way - they're used by any tools you might use that can use the github API. They aren't required for pushing or pulling over ssh.

Which do you use? I've had a quick google and only found Guilt as a serious contender, and that doesn't seem to quite do what hg patch queues do (especially wrt publishing queues). I'm interested as it seems like quite a common workflow (for me at least) that doesn't really fit into the Git model.

Because vim's paste command, p, will paste what was last removed with a command (such as d or c). Although you're not explicitly told that d and y are analogous to cut and copy, after learning the mechanics of p, each command you learn adds a new (and powerful!) mechanic which doesn't have a parallel in the normal cut/copy/paste model.

I think Jon Markwell's comment on Twitter sums it up really: "Something that's been on my mind for a while: Feels like the values of Twitter the company have moved away from those of the product we love" (http://twitter.com/#!/jot/status/81434698773049345)

Twitter-the-product is friendly, sociable and open. Twitter-the-company is increasingly evil - is the recent shift away from being developer-friendly with loose T&Cs to locking everything down something specific to twitter or is it endemic to a company of their size and a product of their growth?

That'll definitely give you a speed boost, as the interpreter doesn't have to get involved (if configured right). However, this article is talking about IO clogging apache workers. The issue is that the worker must do two jobs: generate the page (using mod_php) then send it to the client. Using nginx in front of apache means that nginx handles the IO to the client (which it is extremely good at), leaving the apache workers to handle nothing but generating pages, hence getting overall higher requests/sec from the same machine.