Yep - hi Trek :). I don't know how this got pushed to HN again but there will be a followup. I'm wondering if it's coincidental :)
743 karma · joined March 25, 2010
Yes, Alt.NET came along in 2009 or so and managed to do some good things, not soon enough really and all the silly flame wars actually did more harm than anything.
These were choices made by my contracts and my employers. What you're saying is valid: I could have pushed to use another system or platform. I can do this now - but back then it was not nearly as easy to just pick up and learn the intricacies of different platforms. You might disagree, it's sort of subjective - but installing PHP/MySQL was a complicated affair if you're not familiar.
Finally - the whole premise of the post was the very question itself: "Did I do the right thing?". I was questioning, and I had to make a choice. I constantly did (and still do) that.
You can use a SQL query for this or a simple map/reduce - either way my argument is to focus on transactional design that works best for your system - don't conflate reporting needs with your live system (i.e. BA queries).
Many businesses (including startups) have moved to using document stores for high read environments and scraping nightly drops to their backend analytics systems. This is smart - you don't want to run summing/aggregation on a live transactional system for (hopefully) obvious reasons.
EDIT: it's also worth noting that map/reduce is typically much more powerful when aggregating large datasets. When trying to run analytics on top of a transactional system, developers like Ray here would end up with multiple joins and groupings - all of which slow everything down. Map/reduce certainly isn't perfect, but the author dismisses it as difficult witchcraft when, in practice, parallel execution of MR queries can greatly decrease resources and time to information.
I sort of think we've moved beyond this discussion.
Congrats on the launch - will be neat to see what this turns into.
Honestly, as it stands, I don't know if I'd ever try and explain Ember to anyone aside from the basics which I've done.
The concepts are interesting - as you say - but in practice it just feels like a mediation on "what can we leverage with clever naming" that results in code that is ... less than clear in intent and purpose.
The API is the thing (to me) that brings it down. Nothing is discoverable and it's not easy to jump from one context to the next. In Angular, for instance, it's a pretty simple jump to understand that if you want an ability/function, you'll need to inject it.
This leads you to understand that "I need to do a JSON call... hmmm" and then boom: $http.
Ember isn't this way. It isn't until you grapple with models that you understand you'll be writing jQuery code to get remote data. In my mind this is a huge gap, given Backbone's ability to do it straight away, and Angular's injectable $resource stuff.
I like the ideas, but the API needs to be rebuilt.
I like what you've done after having followed the link here, but it kind of wanders into discussions about IE and UTF8, and then actions and interactivity.
I was trying to show the core of what Ember is and does. Hopefully you can see that our goals were slightly different?
Easily interpreted as trolling. I think you're doing yourself a disservice.
One person telling another to "shut it" is not censorship. Both have a right to speak their minds. Censorship is when you're told by someone with authority that what you're saying/writing/expressing should not be expressed for whatever set of reasons.
You telling someone to "just go away" is equal to this.
There's a standard in the US that your right to free speech shall be upheld but not in the case of hate speech or insighting unrest and violence (also known as trolling). This is for very good reason (ask Weev what he thinks) - which is that we need some form of law to protect us from one person riling up a mob to violence, or a single deranged person from stalking and harassing another.
Trolling a community to provoke thought and discourse is a time-honored profession that predates the internet by millennia (Jesus is often considered one of the best trolls in history).
Taking a contrary position "just because" or for sport is rude. But it's tolerated. How much of me would you like to tolerate in person? Here, online, I'm just a name in a message thread. In person it's a whole different deal. You have rights to protect you from my thoughts, and I have rights to express those thoughts.
Where the twain shall meet?
These apps are built on the web. One look at the Discourse Ember code and I think you'll understand perfectly the confusion I'm writing about.
But I'm curious: do you use Ember or are your responses "what you think"
>Most of your controllers will be very small. Unlike other frameworks, where the state of your application is spread amongst many controllers, in Ember.js, we encapsulate that state in the router. This allows your controllers to be lightweight and focused on one thing.
How is the controller not the data as far as the View is concerned?
They say as much in their guides as well.