434 karma · joined April 6, 2009
Something's wrong here.
1. Ask HN: How much coffee do you drink?: http://news.ycombinator.com/item?id=4606007
2. Ask HN: Coffee Drinkers, How Do You Brew? http://news.ycombinator.com/item?id=4408221
1. it's not efficient
2. we'd need to design a complete new protocol (keep in mind that you'd need to include query parameters) which for advanced query language like RQL is challenging
3. with a new protocol we'd need also versioning (for ensuring backward compatibility)
And the list is probably much longer.
alex @ rethinkdb
> Apple's patents haven't stopped me from being creative. No one has asked me not to design using rounded corners. How about you? I bet not.
Patents have stopped people from being creative. I don't think it's a matter of stopping you or me, but a more general perspetive. I'm no specialist in patents, nor is it a topic that I like talking about, but imho a critical issue is with their generality: rounded corners, mouse clicks, page turns seem like very very wide ideas.
> When you buy Apple you're not just buying hardware or software. You're buying into a ecosystem and that ecosystem works really well! Now if Apple's ecosystem doesn't suit your needs then you're still free to not use it or jailbreak your iStuff.
I do buy Apple products because they fit my needs and their current limitations are not over the threshold I feel comfortable with. Now. But ideally I'd prefer to buy into an ecosystem that is not closed. I'd like to know that in the future when a shift occurs I'll be able to get my things and move to what fits the needs I have at that time.
A related question is: should I complain or not about it if I already chose to buy into it? Me belief is that by expressing ourselves and not being complacent with the status quo we are able to influence things.
So far most of the tools have been created in a very strict, single purpose way. While that's a good engineering approach it also leads to limitations that are hard to overcome. I do remember the early days of Eclipse when they had to build their own java compiler to be able to pull out enough data for the IDE. And that's the simplest example. Or think of the days before JMX.
Obviously this is not a simple problem to solve. I think the only way we could fundamentally change things is to completely rethink the way programming models/environment are thought.
On the other hand, I couldn't say for sure why I was listening to B&A. Maybe because Marco is a person with many hats & interests and the podcast wasn't focused only on Mac news?
This is something I've been looking for. I had to use an external diff tool or vimdiff, but this might change things quite a bit.
The other thing that would be a great addition to ST2 (if not existing already) would be a search by symbol in all project files. Currently Cmd+R is great for navigating to a symbol in the current file. Extending this to a whole project would be awesome.
Nice!!!
This approach could work well when:
- you don't access child documents directly
- you don't update child documents too often
- child documents are usually unique entities
As you can see from the rules above, this would not be a good solution for the Store -> Categories -> Products (contradicts 1. and 3.) But it could work with models like Content -> Votes, Blog -> Comments, etc.
As a side comment, I don't think app exclusivity as user acquisition technique is working anymore. It's an important aspect, but it's part of a larger picture.
alex @ rethinkdb
In a previous incarnation RethinkDB was a highly optimized storage engine for SSDs implemented in C++ to be able to take full advantage of both low level SSD and kernel access.
The current distributed engine was built on top on this storage engine and I think it only made sense to continue with C++.
2. We're putting together some comparisons, hope to add them to the site soon.
3. There are already a couple of answers to this question on this thread:
https://news.ycombinator.com/item?id=4764137
https://news.ycombinator.com/item?id=4763939
alex @ rethinkdb
We had to start from somewhere and we also wanted to get a feel of what are the most requested libraries so we can focus our energy in those directions.
alex @ rethinkdb
alex @ rethinkdb