mattdawson

Exactly. As a developer, I can appreciate that every framework has different strengths and that you should use the tool appropriate for the task, but the fact of the matter is that I have work that needs to get done now and if I spend all my time choosing the perfect tool, I won't ship anything. I have a toolbelt stocked with the tools I like best. I wouldn't want to stifle the discussions on which one's "best," though, because they can be really informative for those looking to add a new tool to their stack.

I worked in DC at a PAC for 3 years, and I can confirm that, without a doubt, lawmakers in Washington vote where either a) the money leads or b) the most ruckus gets stirred up, at least 90% of the time. Every congressperson has their pet causes (the other 10%) but for the rest, they're voting in large part based on those two factors. How could they not? There's simply too much going on to really learn about every issue that comes across their desk.

The ruckus matters.

I'm working on a few relatively complex web apps where the CSS download time don't come to anywhere near that size. In my world (mobile devices, in particular) 320k would be totally unacceptable. 100k is about the point where I start re-evaluating my design.

  filetype plugin on

  setlocal tabstop=4
  setlocal softtabstop=4
  setlocal shiftwidth=4
  setlocal textwidth=80
  setlocal smarttab
  setlocal expandtab
  setlocal smartindent

[edit: see here - http://news.ycombinator.com/item?id=1781074]

I've been developing with Django for the last two years (a screencast series by ericflo is actually what got me started), and I just recently started work on a major Flask project. Flask is terrific.

What Armin is doing with his curated extensions gallery is one of Flask's biggest strengths. You get all the awesome flexibility of a no-batteries-included architecture, but with a great set of fallback tools if you just want to get up and running fast.

Not to mention SQLAlchemy is just a ridiculously awesome piece of software, and it integrates with Flask very well.

I can't be the only person who had this thought.

[1] http://en.wikipedia.org/wiki/Danger_Room

They can be made to be tightly coupled, but they're not necessarily intended to be. A lot of themes override core WordPress functions via a functions.php in the theme root directory. You don't have to include any core WP code in your theme, but WP provides an easy way to do it if you need to.

That WP would pursue this if not puzzles me.

IMHO, Mullenweg comes off looking like a brat in this whole mess. Regardless of the legality of the whole thing, this seems to be a straddling-the-line kind of situation, which makes it feel like there's some kind of ulterior motive at play.

Edit: This link from elsewhere in the thread totally changed my opinion. http://drewblas.com/2010/07/15/an-analysis-of-gpled-code-in-... Seems like Thesis should pretty clearly be GPL.

For a better explanation than I could ever come up with: http://stackoverflow.com/questions/986006/python-how-do-i-pa...

Just to play devil's advocate: if it looks like a duck and quacks like a duck, why would I call it anything other than "duck"? It may be technically correct to say that (in Python, at least) everything is passed by value. But if it helps someone remember that lists may be altered when passed to a function and that tuples can't, what's the real harm?

Again: devil's advocate.

http://daringfireball.net/linked/2009/11/06/openofficemouse

That being said, it's still my favorite audio player. It's one of only two programs I miss when I'm working on Linux.

I like how you follow HN's lead and make read content headlines a lighter gray. But there's no corresponding effect for the screenshot slides. That definitely reduces the usefulness of the read state.

So I want to be excited about this, but I find the "community microblogging" idea really confusing. I was clicking through their example site for FOWA, and I just don't get it. And this is coming from someone who just read an article explaining how it works!

Does anyone else have an opinion about this practice of putting a skeleton project inside a packaged app as Simon is doing with most of his apps?

I ask because I've been moving towards making the apps as novice friendly as possible - that is, including some pretty comprehensive views and templates in the app rather than a project. But in the back of my head, I'm always thinking, "who is this novice developer I'm packaging this for anyway?"

Simon's method appeals to me in terms of slim app code, but it's quite a different approach from what I've been doing.

In my opinion, the only way anyone new to vi is gonna be sold is by struggling through the learning curve. They'll have an "ah-ha" moment soon enough.

I can't imagine that Arch is the only one either. Xubuntu, anyone? Ubuntu comes default with some strange flavor of vim that I can't stand, so I always install vim-nox ASAP on new machines.

I'm a designer and programmer and was stuck on Vista for a little over 3 months after starting my current job. Photoshop required at minimum two reboots a day. Absolute hell.