107 karma · joined May 21, 2009
I used to have 5 or 6, some related to different companies, some for junk, etc., but now I find it much easier to just use a single address for everything.
There are bound to be loses during the transition.
Glad someone caught it though.
Aside from the plugins, the structure of Vesper is just Sinatra, Rack and Rake (/public, /views, config.ru, Gemfile, Rakefile, etc.) plus application and config directories. When the app is run, it does all the normal rackup stuff, and loads everything in /config and /application. There wasn't a need to do anything more.
That's where this whole thing started. I got tired of the routes file in Rails (my biggest Rails complaint), so I switched to Sinatra, and this is how I ended up writing a lot of apps.
Sidenote: /data and /tests are both generated by default plugins.
By unstructured, I just meant the MVC thing. Most frameworks I've used start off with the assumption that I want to use MVC directories. Sometimes I do, sometimes I don't. Most of the time I want to use the concept of models and controllers, but instead of separating them into different directories and files, I want to group related models and controllers together - i.e. a users.rb file with the User class and the associated routes for sign in, profile editing, etc.
The plugins were extracted from code I use in a lot of apps, but not all. That's why a plugin is so similar to a full project, with a few extras thrown in, like hooks (they just run code are certain times during loading). I'm mixed as to polluting the main project with assets, so I just did both. A plugin's /application, gemfile and /tasks don't get moved into the main project. But sometimes it makes sense, such as DataMapper and a /data folder, and MiniTest and a /tests folder. It's really optional.
Now for gems: There's nothing stopping anyone from adding gems to a project. They should work just fine, and I do it all the time. But at the same time, I work with a lot of designers and just-getting-started programmers who have no idea how to write a gem, but still have code they reuse a lot. The 'plugins-as-a-repo-in-a-live-folder' allow for that, while not stopping them from using gems if they fit the bill. A few of the plugins are nothing more than wrappers for gems with a little config pre-written.
If Padrino encourages not developing plugins, then yes, that would be a big difference.
By Sinatra plugins, I'm guessing you're talking about extensions (http://www.sinatrarb.com/extensions-wild.html)? If so, how are they not compatible with Vesper?
I just wanted to use something a little more lightweight and unstructured. Without the plugins, Vesper is basically just a Sinatra app. You can organize it as MVC, or not. There's not much abstraction from adding code to a Sinatra app, and everything glues together nicely. Also, I really like developing plugins this way (put the code from an app into a git repo, and you're done).
There are still a few plugins I'm writing now (DataMapper REST services, Stripe boilerplate, user accounts, URL based commenting, Linode stack script, etc.), but since the whole project is moving along nicely, even getting a decent amount of downloads, I thought I'd share.
It's my first gem and my first public project.
Also, there are plenty of reasons to travel around town that don't involve what you need in your daily life. What about when your friends want to meet at a bar on the other side of town? If that's 5 blocks, no big deal. If that's 15 miles it becomes a problem.
High population density doesn't make public transportation efficient, good planning does. If the public transportation system is designed for a city of 2 million, and the city grows to 7 million, the public transportation system won't be effifcient, or pleasant to use, at all. The unpleasantness and eneffieciency is one of the reasons so many people have cars to begin with. Private transportation takes you where you want to go, when you want to go there, in an environment of your choosing. As is mentioned in other comments here, walking when the weather is bad (cold north, too humid south) is very unpleasant no matter what.
Edit: I know that won't work for everyone, but that's why we have choices.
Example:
In Atlanta (my home town) there are about half a million people living in the city. Though there are poor areas, the economy as a whole is much bigger than that, but the infrastructure isn't - even if you removed the cars. Here's where it gets tricky. Add in the population of the surrounding suburbs and the number jumps from half a million of over 6 million. If all of us lived in the city, not only would it be even more overcrowded, but it would collapse. If we somehow managed to make it work, it would cease to be small connected communities and become one giant urban sprawl. Look at NYC or LA for example. Riding a bike from one end to the other doesn't work so well.
At the same time, if you removed the city from the suburbs they would go broke. Suburbs without cities are just small towns, which don't usually have bustling economies and are often poor (relative to a city).
Suburbs are the natural growth/overflow of cities. When a city gets too big to sustain itself it either spreads the population out with suburbs or becomes an overpopulated, overcrowded urban area that's big enough to need to drive everywhere anyway (or take a cab). All those people have to go somewhere.
If my cost of living went up 10x, I couldn't afford to live this way. If it happened to everyone in the suburbs here and we all had to live in the city, the city would fall apart.
Instead of the historically traditional city with surrounding small towns, we connected the towns to each other and to the city with cars. It's one big culture, and one big economy.
What I think will be the most interesting, long term, is what will happen when the need to commute starts to drop. Remote working already has a lot of growing traction in the tech industry, but I can see it spreading to lots of other industries as well. Most jobs that aren't transportation or retail can be done, at least most of the time, from a home office. A 20% increase in remote working would have a huge impact on how everything fits together.
My point isn't that cities or suburbs are better, just that there's a place for both. Having lived in both and now getting to enjoy the best of both has allowed me a life I couldn't possibly have if I was stuck in one or the other. Scaling for automobiles works out really well for people who enjoy automobiles and the communities they create, which are not only livable, but enjoyable, for the people who want that kind of life.
I don't have a problem with ads, though Google is a good case of not needing Flash to make effective ads.
And how much of that is just ads?
Check out Steven Frank's thoughts on the subject: http://stevenf.tumblr.com/post/73315911/the-politics-of-flas...