Hacker News new | past | comments | ask | show | jobs | submit | danskil's comments login

Looks great, is it bad i'm already wishing it could export to pdf for speakerdeck? Does that defeat the simplicity?


This is at odds with the simplicity, but there's no question that an artifact of the enhanced version is important for publishing a slide deck.

Quick tests with the Chrome "Print to PDF" and a "convert to PDF" extension failed miserably...


Just got this book, and i'm loving it.


I live in Austin, please don't do this. Not to mention our sidewalks aren't nearly as dirty as say LA, and it won't look as nice. A few years ago whrrrl put down a bunch of chalk on the sidewalks and never cleaned it up, it's still there and now it's just embarrassing. Graffiti is graffiti. Etching your name into dirt is still etching your name into something.


You should not use SQLite in production.


I downvoted you. Here's why:

I've deployed SQLite to a large number of production software, from embedded systems to web servers handling thousands of daily vistors. In fact, SQLite is my tool of choice when it comes to a small/medium relational-db-based web project.

Sqlite is not a toy db. It is an impressive piece of software engineering.

So, unless you have a very narrow definition of the word production, you should do read up on SQLite (the official website is excellent) and seriously consider it for your next project.


SQLite should absolutely be used in production, where it makes sense. The one area where sqlite has a big disadvantage is concurrent writes. If you have read-only data, cached data, etc. then sqlite can happily be used in a high traffic production system, with millions of rows and many GB of data. It's also a good store for configuration data, or something like an admin backend. The portability of sqlite database files is a really nice feature.


This is true, I should have said "it's not mature".


I was just doing a write up on swapping auth back ends to gain more security http://schneems.com/post/24678036532/zomg-my-passwords-are-i....



Ha. Thanks. Couldn't figure out how to do that...


they don't seem to be related to foursquare at all...no about us/contacts page

Is this a facebook/phishing app?


Not a facebook/phishing app - just very new :)

Check out the feedback tab for some info. About us coming soon.


interesting idea, though in keeping away from feature bloat, wouldn't it be much much easier, and just as effective to put that information in the read me?

I realize the you said they don't want to but the info there, but why? If you really wanted to abandon the project why not just close the repo, which would shift all your traffic to another fork?

If github implemented this feature, I wouldn't be upset, but it seems very single purpose. Maybe a status flag, so the author can not just say "abandoned", but "up to date", or "active" though again, all of that can be seen through the commit history.

Just my 2 cents.


I agree that while this is a good idea, Github probably has bigger fish to fry and that at this point it should do fine to put the notice at the top of the README.

Perhaps someone can add the feature to the open-source Gitorious.


Read on slicehost, ask questions on server fault -> repeat


I bought logo design love (book) and was emailed by the "author" asking me to write a review...so i did


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: