Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Retozi
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
Retozi
12y ago
This still introduces a new link, which will overload your brain if you have too many of those. To give you some context: In the app I'm developing now, we've got roughtly 25 global user interactions (meaning an event that will be
32.
▲
by
Retozi
12y ago
The flaw with such a strategy is that it does not scale. (We used to do exactly what you described). In a big "eventful" app, you will have way too many events to keep track, and you will constantly be browsing trough different mo
33.
▲
by
Retozi
12y ago
Well, I remember all these things just too well from our Backbone App (not Backbones fault, but ours!), and I would never go back there again. So now I have 3 things to add to A and to B, because B needs to refresh everytime A does We use
34.
▲
by
Retozi
12y ago
yep, that's all it does. It just inverted the sequence dependency. You call it "worse". But I argue that it is a much better mental model in the specific use case of updating state given an external disruption from the user.
35.
▲
by
Retozi
12y ago
I do not have much experience with Angular, however, I feel the arguments over different frameworks depend a lot on the specific nature of your app. two-way databinding is perfectly fine and really helpful for a lot of apps. However, it wil
36.
▲
by
Retozi
12y ago
writer of the article here: I simply cannot follow the argument about "added complexity" The use case defines the minimum amount of links you have to make, in this case 4. Now you have two options: You just roll with it (we used t
37.
▲
by
Retozi
12y ago
I disagree. You need far less infrastructure for managing application state and if you're willing to settle for the DOM hierarchy communication, you need close to zero, because the communication is endogenous. You can go very very far
38.
▲
by
Retozi
12y ago
The app the blog is based on is actually implemented in chaplinJS in production. It is a big improvement over Backbone, but it doesn't have the conceptual clarity of React. I actually moved to React because I was not satisfied with th
39.
▲
by
Retozi
12y ago
https://ghost.org There seems to be issues with some mobile clients that I cannot replicate on my ipad and galaxy s3