723 karma · joined September 10, 2007
Postgres is still my preference for a RDBMS. Schemas, Triggers, JSON, Geo, PL, robust data types, it just offers so much more then MySQL/innoDB/MyISAM.
I've also wondered why Ryan never reached out to his audience for people to intern during his downtime.
All in all, just my two cents on the issue, from two view points.
https://news.ycombinator.com/item?id=7077493
You tend to ignore people, you're the same as a recruitment agency. I personally think these threads should be restricted to direct hires, not your skimming-the-top fodder.
Awesomeness.
Brackets is really neat, it just attempts to be a good editor, it has some unique features like toggling css inline from an html file for example and other jazz.
So Atom isn't something that's really set apart from webkit-based editor, but I don't think that's what's important here. It's the potential the stack offers us.
There's also not as much competition in this area, but it's sorely needed. I feel vim, emacs, textmate, sublime and most the editors are generally closed source or have huge code bases, and they are hampering the process of innovation by creating walled gardens or creating a barrier to entry. With a editor based on web technologies things really open up a lot.
Think about an editor where you can write a feature, pass the tests, and have a hot reload. No compiling, no closed source or plugin system. Just simple coffeescript/javascript some html and css. And bam, you've rewritten your status bar without effecting work in progress. That's something an editor should give us.
I digress, I'm just excited by this.
What's important is that it's a text editor on top of web technologies. I was poking around doing the same a couple months back, brackets has been doing it for even longer. It's honestly sorely needed because of the amount of expression one can put into due to it's technological stack. An open, compile-less, hot-reloading editor sounds like a dream coming true.
I'm excited for it.
It also appears to be built around react, so that's really cool as well. And the code is simply great.
https://github.com/meteor/meteor/blob/devel/packages/livedat...
2. Rails + Pusher
Those are the best solutions, at hand that would work well with Rails.
I wouldn't advise smashing a Rails app and a Meteor app together unless you have a solid case to do so (like migrating).
Rails, aside, I'm happy to here oplog has landed. 1.0 feels imminent, the tension is growing, even here in Toronto. Stop waiting sheeple, Meteor is great as is, and it's only getting better.
Asset ordering for packages is another important issue I'd like to see rolled out for 1.0.
In terms of growth, who knows, right now it appears to be linear, but I feel a ramp up is coming.