Here's a blog post with more information about its creation and development: http://www.thomasboyt.com/2013/03/24/announcing-noted.html
3,882 karma · joined March 12, 2011
website: thomasboyt.com
I'm really glad to hear that they're adding an adapter type that can be more powerful than just an $.ajax call while not being quite as complex. It was by far my biggest complaint with Ember.
(of course, I hope this doesn't stifle development of more full-featured adapters - I think half my problems with Ember Data come from the LocalStorage adapter I'm using having some major issues ;p)
Content ownership is a little murkier, of course, because 9GAG is a company that thrives off stealing and rebranding the content of others. There's also no reason they couldn't have played ball - there's lots of alternative mobile clients for sites like Reddit and Hacker News because they create a healthier community and fill a niche that the creators of those sites can't fulfill. Still, if 9GAG decided they wanted the ad revenue this app would deprive them of, I can't really fault them.
(though, to be clear, I still totally fault them for being a shitty company that steals content!)
Definitely doesn't seem targeted at newer Clojure users. Also, the use of Datomic as a default data store rubs me the wrong way, mainly because I've never even seen it outside of a few HN articles :p
Of course, remember, this is EA - to them, Dead Space, the most popular survival horror franchise of the last five years, underperformed.
Still, I doubt this has much at all to do with SimCity. If it does, it has more to do with its low MetaCritic score than actual user complaints.
Nah, kidding. So they're totally right that there's a significant amount of state in the router, in that that's where you define which model and controller (and, depending on how fancy you get, what views and templates) to use on a given page. So those are essentially state.
The state that can make a controller fat is essentially state that's too important for a view but doesn't need to be universal to the page. For example, with my Dropbox controller, the controller has a state property that handles the various permutations of the state of syncing (i.e. it could be doing nothing, currently saving, done saving, failed saving, etc.). This state is set by the controller on the controller, and used by multiple views to determine things like which label a progress modal should have.
For example, if you had a controller representing a list, you might want to keep track of which item is selected on the controller. That way, if there are multiple views that can act on the currently selected item (for example - you might have a list item view that has a template that renders the item, and then a separate view that are buttons that trigger actions that act on the current item), they all have access to it.
Plus, I always think of state defined in a router as being limited to specific pages/routes, whereas some of my controllers are used on several different routes.
As far as I attempted to implement it in my app (https://github.com/thomasboyt/noted-app), it seemed simple enough. Models were data; all they contained was their properties and operations that controlled their properties.
I mainly used controllers as the "state" for parts of my app. In Ember, this doesn't even need to mean it's tied to a specific model type. For example, my Dropbox integration is handled within a controller that's bound to several separate views (in this case, those views included buttons that triggered syncing and modals that displayed the progress of syncing). There's no "Dropbox model," just other models that I'm using this controller to sync. Controllers are not simply an intermediary between models and views, they are an intermediary between state and views.
> I'm trying my best to reconcile this with the notion that a controller (classically speaking) is supposed to ... well control the view. Here, it's not doing that.
I think what the author was looking for in controllers is what's actually handled by, well, views. The view handles any user interaction, and then uses the controller to change the state of various bits (whether calling methods in the controller or simply updating properties on it).
To sum up: model is data, controller is state (including instance(s) of models), and the view is user interaction. Templates can bind to properties on any of these. Routes are what hook these components together depending on the page.
This was the part that was most surprising to me. That's an incredibly good success rate (albiet with a small test) for something that's trying to mediate such a polarized situation. All it takes is either party not being satisfied with what they got to push it to court, so it must be extremely good at helping both sides feel comfortable with the outcome.
I like it. Obviously, I don't expect (or want) Chrome to replace my text editor any time soon, but this will be great for quick fixes.
It's pretty much a total hodgepodge of out-of-print material. You won't find 4th edition rulebooks or anything like that, but there apparently are a handful of 4th edition scenarios there.
|video|(http://youtube.com/watch?v=abc)
It was literally as simple to use as the original App Store, which was incredible. I've never seen that kind of excellent design in an app designed for piracy. It seriously "just worked" in the same way that you'd expect any iOS app to work: you searched for an app, clicked install, it'd take you to a mirror (usually on a site like Mediafire), download it in the background, and install. The interface had a shocking amount of polish, too.
I can't really argue, as a developer, that it's a shame that development has stopped on it, but still - there must be a lot of smart developer talent in that group that will hopefully be put to better use now :)
Here, I'll help by pasting one of the more important paragraphs right here:
At Quantico, Pfc. Manning treatment wasn’t by the book: the sleep depravation and stripping of clothes; the humiliation; the taunts and mockery; the nine months of putting Pfc. Manning in protected custody citing concerns over suicide—concerns that were rebuffed relentlessly by both Pfc. Manning himself and qualified psychiatrists. That’s why Coombs is looking to have the case against his client thrown out, and Manning’s own testimony this week only accentuated the living nightmare he was made to endure for nearly a year while only a half-hour drive from the capital of the nation. As testimonies from Quantico staff, health professionals, and the private himself continued late into the night all week, often for hours without intermissions, more unraveled about not just the torturous conditions imposed on Pfc. Manning but the blatant mismanagement in the same institution he is accused of blowing the whistle on.