I feel uncomfortable when reading your post. Passive aggressive, attacking the OP's architectural decisions, assuming that he didn't have any clue building a proper Ruby system. I am not a fan of Go, not at all, but I know that Ruby has significant issues which the OP also outlined quite well and you seem to just ignore them.
But Paul Graham knows exactly why you are sticking to the past (just replace 'Blub' by 'Ruby'):
As long as our hypothetical Blub programmer is looking down the power continuum, he knows he's looking down. Languages less powerful than Blub are obviously less powerful, because they're missing some feature he's used to. But when our hypothetical Blub programmer looks in the other direction, up the power continuum, he doesn't realize he's looking up. What he sees are merely weird languages. He probably considers them about equivalent in power to Blub, but with all this other hairy stuff thrown in as well. Blub is good enough for him, because he thinks in Blub.
When we switch to the point of view of a programmer using any of the languages higher up the power continuum, however, we find that he in turn looks down upon Blub. How can you get anything done in Blub? It doesn't even have y.
By induction, the only programmers in a position to see all the differences in power between the various languages are those who understand the most powerful one. (This is probably what Eric Raymond meant about Lisp making you a better programmer.) You can't trust the opinions of the others, because of the Blub paradox: they're satisfied with whatever language they happen to use, because it dictates the way they think about programs.
> You really don't need a package manager for Go. Honestly, the main reason [...] is because you're deploying source code to your production environment
Not sure if I would agree with that. A full-fledged package manager automates the process of installing, upgrading, configuring and removing software packages in a consistent manner. Dependency management and semantic versioning is an important part to provide this consistency.
Wether you deploy source code or binaries does not make any difference why a package manager is always good to have.
A huge photo collection is the best lock-in for an OS. So to have a top-notch app here is a smart move from Apple.
I have like 70GB of photos in iPhoto and somehow this stops me from fully migrating to another OS. Just the thought of moving this 70GB to another file system, OS and photo program let me stick to OSX forever. And photos especially the family ones are maybe the most important 'personal' data of a user.
Besides, iPhoto is not bad but the many format changes in the past were a bit tiring.
In general I prefer Dropbox as a cloud file storage--they have the best clients of all OSes and security features like no other (remote wipe), now I just need a cross platform photo database which is separated from my cloud storage provider.
Really like the idea and just had this thought: why not just present the code in color, normally indented (so not like minified) and in your favorite theme (such as Solarized Dark) in a long portrait format poster, then put some glossy finish on it and I'd buy instantly.
Probably I am alone here but I think that Snapchat is the biggest innovation in the social space since Facebook and not just because of it's ephemeral nature. Let me elaborate and give my view why I think Snapchat is great and one of my most used apps.
- To start, Snapchat changed my communication behavior heavily. Before Snapchat people used any kind of messengers when they had a clear intent to start an interaction with another person. With Snapchat you just send something. You do not want to start a conversation, often you just share what you do right now, how you feel and very often it's so close to what you are and not some polished something you would like to be. You share emotions in forms of pics also on Instagram and Facebook but this is different since the emotions you present there are highly curated, see below for more.
- There are no 'likes' and this is wonderful. The existence of likes sets us under pressure. If we post something on Facebook and do not get a single like it's embarrassing and leads to postings which are only of outstanding nature painting a distorted picture of our life. Facebook is anything but not reflecting reality.
- Sending and selecting a few contacts is so fast and I do not know one single app which has a slicker process. This again leads to so much more honest and personal messaging. Since I target on other platform many more people I have to take care about my postings. On Snapchat I can quickly select a bunch of people and leave those out who might be bored by a single snap.
- The process of taking a picture is different than with the stock camera of a phone. You take a pic which is NOT saved—usually it's immediately saved and if you do not like it you have to go the the gallery, delete it and confirm again that you want to delete it. This is very annoying if you take selfies. Snapchat turned this around and once you find the right shot you can send and/or save it. Small thing but so convenient.
- Features like slide-in filters, painting on the pic, amazing video calling are just nice amenities but again show that Snapchat's interface is just great and miles beyond other cluttered UIs.
- One feature which I want to mention is putting text on pictures, no rocket science but again sometimes so funny and shows similarities to those meme generators.
- Finally, the ephemeral thing is not the key feature but it's the brand and the DNA of Snapchat, everybody knows that there's no privacy, people can screenshot the snaps and share it, period. But it's about being oneself and understanding that the pictures are just 'throw-away products', no shiny thing kept forever. This again leads to a very honest snaps. Snapchat is not about looking good.
I encourage everyone who doesn't 'understand' Snapchat's success to try it, it strengthens the relationship to close contacts and friends much more than other 'social app'.
this is really AWESOME and finally shows what is possible with the power of nowadays browser rendering engines paired with a good JS lib (React is my favorite js lib).
I like very much the butter smooth transitions on any phone and it's nice that you spent so much attention in getting this thing so responsive, well done man.
When will this thing be live, having more documentation and can I play already around with the stuff on Github?
The post implies that Google wants to get rid of URLs the core of the Internet but that's not true -- Google wants links, latest example is the possibility to deep link into any Android app via URLs.
> Gone are the bulky angles and edges of tabs and menus. In Firefox 29, you’ll see streamlined, almost aerodynamic, curves giving emphasis to your current tab and subtly understating the rest.
5 years after Google Chrome introduced them [rounded tabs]
This is the best which could happen to HTC, cheap PR around a phone nobody would have noticed. HTC lost significant market share compared to other Android handset makers Samsung, LG and Sony recent years.
But Paul Graham knows exactly why you are sticking to the past (just replace 'Blub' by 'Ruby'):
As long as our hypothetical Blub programmer is looking down the power continuum, he knows he's looking down. Languages less powerful than Blub are obviously less powerful, because they're missing some feature he's used to. But when our hypothetical Blub programmer looks in the other direction, up the power continuum, he doesn't realize he's looking up. What he sees are merely weird languages. He probably considers them about equivalent in power to Blub, but with all this other hairy stuff thrown in as well. Blub is good enough for him, because he thinks in Blub.
When we switch to the point of view of a programmer using any of the languages higher up the power continuum, however, we find that he in turn looks down upon Blub. How can you get anything done in Blub? It doesn't even have y.
By induction, the only programmers in a position to see all the differences in power between the various languages are those who understand the most powerful one. (This is probably what Eric Raymond meant about Lisp making you a better programmer.) You can't trust the opinions of the others, because of the Blub paradox: they're satisfied with whatever language they happen to use, because it dictates the way they think about programs.
Source: http://www.paulgraham.com/avg.html