delambo

Again, thanks for the feedback. Right now, I'm literally putting together a pull request to improve this functionality.

Some cards do have links inside of them - they may have external source links or sticker links, and fortunately we just removed author links which will make this easier. I'm wrapping inner elements in hyperlinks which should fix everything that you mentioned.

As I mentioned, for the moment, you can use the card titles which are wrapped in hyperlinks.

I assume you are talking about the recipe cards not being links? It's tough to build a linkable card with links inside the card without using JavaScript. The actual html link is the title of the recipe so you should be able to use that if you really intend to not use JavaScript.

I'm in the process of putting together a pull request to make sure the link underline shows on hover (that worked at one point!) and to get middle-click working on the card for users that do use JavaScript.

Thanks for your feedback!

The best way to organize a mix in iTunes is to create a playlist with all of the songs, make sure the album title is the same for each artist, then select all of the songs and open the Info menu (CMD-I) and mark them as a Compilation. Marking them as a compilation will organize them on the file system together under the "iTunes/.../Music/Compilations/" directory, which hopefully will make migrating off of iTunes in the future an easier thing to do.

To that point, it's interesting how many claim that Backbone is yesterday's tech and that we are now 2 or 3 iterations of javascript frameworks past Backbone, yet most of these large sites are still using Backbone! It's possible that a lot of the sites would use something other than Backbone if they were built today, but it's clear that Backbone will be around for some time.

Even though Lebron James is the best player in the world, why is there a good chance that the Heat won't win the championship this year?

Also, could a team of Lebron James level players win a championship?

I think the greatest advantage to static typing is the IDE support. Compile-time error checking is overrated, and in my several years of writing JavaScript, I've never seen a bug in production that could have been prevented with static analysis. That might be because I know the language well, but it's not a feature I need.

"What's true of all bugs? They passed a type checker and they passed the tests!" - Rich Hickey

Here's a trivial example:

I have a Modal class which depends on some utilities in a Utility class, but the Utility class depends on the Modal class because there are some utilities that show Modals.

This is not a broken architecture and is handled just fine by other programming languages/dependency handlers.