I actually use Kitty with tmux/vim. I noticed a massive improvement in rendering speed over iTerm. This was after messing with iTerm's own accelerated rendering which wasn't as much of an improvement as I had hoped.
Doesn't this still effectively break the back button or at least the users view of the back button? To the user although there are visual hints, he/she hasn't left the page. Scrolling down the page however creates multiple history entries.
This would be perfect if clicking the nav didn't cause a page reload. I expect the page to go back to an entirely previous page, if I hit the back button in this case.
That would not be the case if the sections of content were different from one another.
- A super-scrolling page with different sections of content might keep the back button functionality the way it is here.
- Homogeneous content like Facebook posts should not incur a back button through the pagination.
I would say that "each person in people" is a far cry from the type of logic in views normally frowned upon. What would you propose to be different in this case? Where does iteration of this type belong?
Check out mustache. It has things that can be used for iteration but it isn't explicit and you decide what actually happens at runtime in code rather than in the template.
The {{#array}}item{{/array}} syntax is functionally equivalent to and equally logicless as {{#each array}}item{{/each}}, only the latter (handlebars) has the benefit of being precompilable and easily extensible by frameworks such as Ember, Meteor, and the like.
They may be equivalent, however, the first version has the freedom to do what they wish, for example, what is represented by array may not be directly iterable or it may be filtered. Precompilation is available in a variety of languages for mustache, including js.
IMOH, handlebars is a lazy version of mustache where the developer using it sacrifices maintainability and encapsulation. Which is probably ok for most apps that don't grow beyond a single developer.
I'm a WoW user as well. I will say from experience that you do not have to argue with anyone about removing the authenticator. You simply submit a support ticket containing a picture of your drivers license. The authenticator is usually removed in a few hours. I've done this multiple times now due to formatting my phone without grabbing my restore codes for my authenticator.
I have actually been toying with building out something like this as well. My wife is a photographer and building something around dropbox and glacier only made sense.
The mission control bar looks very familiar. Although I can't remember the name of it now, I seem to remember there being a debug bar of sorts that worked with merb/rails projects that had the same type of look. Anyone remember the name of it?
Maybe your thinking of the old FiveRuns Tune-Up app. I used that all the time when I was doing early rails projects. They got bought and shut down awhile ago but I found an old TechCrunch article on it.
