Unlocked Galaxy S3 (Amazon): ~$660
Unlocked Galaxy Nexus (Google Play): $349
188 karma · joined March 10, 2010
Unlocked Galaxy S3 (Amazon): ~$660
Unlocked Galaxy Nexus (Google Play): $349
Now that I checked the tutorial again, there seems to be a "Press enter to submit commands" help text before the command prompt. If you just added that, great, since that would have been my first suggestion anyway :)
As a developer using Git daily I can only guess what the most problematic parts of this tutorial are for beginners. I hope you get a lot of good feedback and data from all the people visiting the site!
From the blog post[1]:
"If you know of a developer, designer, or other knowledge worker that would benefit from using Git but that hasn't made the leap just yet, send them over to try.github.com when they have a spare 15 minutes."
As a developer, it would be nice to know how well this tutorial really works for non-developers. To me, it seems that the tutorial introduces way too many concepts and details in a very short time for a non-developer to understand.
For example, there are a lot of people that work daily with a computer but freeze completely when faced with the task of using a command-line interface. Yes, clicking on the command does write it in the console but you still have to know to press the return key to actually execute the command.
I'm not saying people shouldn't learn Git, I'm just wondering what the target audience and purpose of this tutorial is.
Implementing interoperability with all the possible cloud storage systems shouldn't be left to each app developer separately. This should be a feature of the operating system.
As an Android user, I'm genuinely interested if iOS users find the sharing options between apps too limited. Do you often end up requesting new sharing options from the developers of your favorite apps?
Also, not every piece of data is a file I'd want to save to Dropbox. For example, I share article URLs from Flipboard to 2cloud many times a day (2cloud opens the URL on my desktop browser). I'd hate to have an extra save/open step between the apps.
For example, if I share a photo from the Android Gallery app to Instagram, add some trendy filters and share the modified photo in Instagram, I end up with three copies in the filesystem: The original, and two copies made by Instagram to preserve both the original and filtered version.
After all, Instagram doesn't know/care whether the photo came from a camera or from another app, so it always saves a copy of the original.
Also, each time I share the photo to Twitter, Facebook or other cloud service I create another copy with different resolution, (re)compression and even dimensions, which is saved to the service out of my reach.
I guess having multiple unsynced copies of the same information is a problem that won't be solved as long as we want to have the ability to distribute information freely. One interesting development would be better content-based matching of files (e.g. Google similar image search, content-based indexing of photo subjects in Google Drive).
I can take any photo, URL or file and open/share it in/to another app. The OS and app developers take care of which apps support which resources, so as a user I'm always presented with a sensible list of apps currently available on my device.
I'd say the notion of a file with a specific file type is too abstract and technical for most use cases for casual users. The UI should group pieces of data as human-understandable resources (i.e. a "picture" can be a .jpg, .png etc.). With this level of abstraction, a user can be expected to understand when presented with a list of apps:
OS: "What do you want to do with this URL?"
User: "Share to Twitter/Facebook/My other browser"
Fortunately, other editors are already adopting similar features. Just today I was fiddling around with Ace, a web-based code editor, and noticed that they support multiple cursors too! Just select multiple words while pressing the Ctrl (or Cmd) key.
Live demo: http://ace.ajax.org/build/kitchen-sink.html
The nicest thing is that I only found this by accident because I'm so used to using multiple cursors in ST2. It's a great feeling to be surprised that something works just the way you sub-conciously expected :)
Thanks for the incredible work!
I assume the layout breaks on my setup because I have set the default browser font size to 18px and you're using em's (which are relative to the base font) to define all your font sizes.
Using relative font sizing isn't necessarily bad, but you should make sure that the whole layout is flexible enough. For example, you have set a static pixel height for the speech bubble and "full stack" containers. With a slightly different font setup that can cause the text to overflow (as can be seen in the screenshot above).
Great work this far, I'll bet you can make this a lot better by reading all the feedback in these comments.
The followshows interface gives a nice overview of the air dates and what I should watch next.
Also, if you're currently using http://mytvrss.com you can import the feed straight to followshows in the settings.
I know where home is but I still don't know whether or not I have to run to catch the next train.
I love the simple but powerful UI. It's not often you see something that makes you think "Why hasn't this been done before?".
I would even gladly pay a buck or two for an Android version ;)
EDIT: grammar
The creator of IcoMoon (http://keyamoon.com/icomoon/) has made a nice demo video:
http://dev.tinkercad.com/blog/2012/1/30/press-release-tinker...
http://i.imgur.com/D77Ey.png (the a's are especially choppy)
Chrome on Windows uses a different engine for rendering text than Firefox or IE. They're working on a fix: http://news.ycombinator.com/item?id=3523375
http://eligrey.com/blog/post/better-font-smoothing-in-google...
This has been an open issue since 2009. I'm surprised it still hasn't been fixed even though it's a daily nuisance in the world of beautiful web fonts and large type sizes:
http://code.google.com/p/chromium/issues/detail?id=25541
http://code.google.com/p/chromium/issues/detail?id=105944
EDIT: an official DirectWrite port of Chrome/Win is currently under development:
https://groups.google.com/a/chromium.org/group/chromium-dev/...
Pink = Clean, Calming, Warm
So women can't be rough, excited or cold? We need more heroines like http://en.wikipedia.org/wiki/Lisbeth_Salander
As mentioned in other comments, LiveReload does this for CSS or SASS (Mac only, unfortunately).
The actual script on the site is unminified and quite easy to grasp: Since it's only a client-side solution it has to resort to polling every stylesheet every second(!) and check the file's Last-Modified header from the ajax request.
This is hardly an optimal solution, since you end up making a lot of requests even though no changes are being made. In addition to the performance standpoint, you end up cluttering any ajax monitoring views (e.g. Chrome dev tools).
LiveReload (http://livereload.com/) seems to be a good alternative (Mac only). Any suggestions for similar solutions for other OSes?
EDIT: Just tried the experimental v0.0.2 Windows release of LiveReload. Installation was really easy, and I got it working with the Firefox extension right away. More info: http://help.livereload.com/kb/roadmap/latest-development-bui...