pags

8 ms·

31.
by pags 11y ago
Probably for chaining
32.
by pags 11y ago
I also found it interesting that doing a Google image search on his name yielded nothing matching the description of the man given in this article.
33.
by pags 12y ago
Definitely. I was surprised at how thoughtful and sane this article is.
34.
by pags 12y ago
I'm not sure that time and bodies necessarily produce good abstractions.
35.
by pags 12y ago
The difference is that the framework is built to be an open source framework - it has general abstractions. Your own patterns and practices are developed to apply directly to what you're building.
36.
by pags 12y ago
Maybe I just don't get it, but I can't even get anything from the landing page. What concerns does this library address? What are the general abstractions like? Why would I even consider digging deeper without knowing the answer
37.
by pags 12y ago
I predict that "decentralized" will be the next big buzzword. That is all.
38.
by pags 12y ago
Awesome.
39.
by pags 12y ago
It should be noted that none of these comparisons - Ruby\Node.js, nor Rails\Node.js, are really apples to apples.
40.
by pags 12y ago
Web - but when the time comes to focus on mobile, Node should still serve us well.
41.
by pags 12y ago
I've heard the opposite declared many times (Node falling, Ruby rising)...there's never a lack of people who are quick to declare the death of any specific technology. That being said, I work for a new, funded startup in SF, and o
42.
by pags 12y ago
It's an entirely pleasant vision.
43.
by pags 12y ago
I can't help but think that he was conveniently leaving out details that give the entire story - clearly he thinks the audience are unintelligent sheep, so surely they'll take him at his word, right?
44.
by pags 12y ago
Isn't he blurring the line between "commit" meaning creating a state you can roll back to (in all version control systems), and "commit" meaning pushing to the "official" code base in a non-distributed sys
45.
by pags 12y ago
This is well put, but I can't offer the same concession about "this" ... what exactly is the problem? It provides access to the state of the object on which you are working, if utilizing OO paradigms within JavaScript. Sure
46.
by pags 12y ago
"fuck" is an edgy word.
47.
by pags 13y ago
This seems pretty spot on to me. More moving parts = more failure points...as a web engineer, I find myself bitten more by the trappings of abstract code structure than by things like faulty algorithms. This ties pretty heavily into why I
48.
by pags 13y ago
Or that not having a GitHub account with a billion stars makes you a bad programmer. Or (gasp) not having a GitHub account at all. Chances are, if you're a full-time software engineer, you're already spending a significant chunk o
49.
by pags 13y ago
I get the sense from reading some of these comments that most people who try Dojo don't really have a clear understanding of what it is, or how to separate and leverage the individual tools that it provides. Too bad, since it's a really po
50.
by pags 14y ago
Why post this stuff? He offers opinion without explanation, this is the same type of JavaScript "wisdom" that probably had him following the conventions he is now nixing in the first place. I'm not sure if his "dogma" disclaimer at the en
51.
Show HN: another jQuery Form Plugin - for HTML5(github.com)
2 points by pags 14y ago|0 comments
52.
by pags 14y ago
https://github.com/pags/fields.js Give it a look. As you described, it simply parses standard input tag params, including HTML 5 types. It's my first attempt at anything like this, so be gentle.