214 karma · joined August 5, 2012
It doesn't matter if they are web apps or other apps. They are separate, and because of this, shitty.
Edit: Itunes for music was massively dominant because it has everything. Separate stores for every single music publisher would be ridiculous. The same goes for other media.
Also, common carrier phone services only had usage charges for long-distance service.
Someone else just needs to come out with better and cheaper services. Comcast sucks and is milking their monopoloy.
A line of Ruby is worth a <INSERT-RAGE-HERE> lines of Java.
The idea is that you are designing for responsiveness. You are removing the worry about what should be on the left or the right or how wide things should be. You are focusing on what things are related, the relative importance of different things, and the content/interaction.
/artist/{artist}/albums
/albums?artist={artist}
AlbumsController#index(artist)
Do:
/artist/8/albums
/albums/9
Don't:
/artist/8/albums/9
Using query filters versus nesting are virtually synonyms. I would say there is a minor semantic distinction in that the first one is a definite relationship, and the second one is a possible relationship. That is, "get the albums for artist 8" versus "get the albums searching for artist 8". The search could include other parameters as well, making it not as definite.
/artist/8/albums
/albums?artist=8