How We Built eBay’s First Node.js Application
Senthil Padmanabhan and Steven Luan, writing for the eBay Tech Blog.
!undefined
This is a tumblelog, kinda like a blog but with short-form, mixed-media posts with stuff I like. Scroll down a bit to start reading, or a bit more to read more about me.
“
Nobody actually wants to use frameworks. We only want to build web user interfaces efficiently and frameworks help.
—
Google’s Polymer and the future of web UI frameworks
Dr. Axel Rauschmayer on Google’s Polymer.
I largely agree with his points, especially the thrust of the above pull-quote. When discussing frameworks and libraries like this, it’s easy to lose sight of the fact that they’re around because of some gaping hole in the language’s native/standard libraries. Google’s recent efforts (e.g., AngularJS and now Polymer) point to more declarative or component-oriented approaches; put in the context of HTML5 and the advancements there, that makes a lot of sense.
I’m interested in Polymer, but I feel like I need some more time to digest it. Like when Twitter open-sourced Flight, there’s this sense of: “Cool! That’s a novel approach…” Which also feels a bit like: “Whoa, that’s really different.” Now to dig in…
How an svn user sees git workflow
Reblogged from DevOps Reactions
“
These APIs becoming public could be a huge boon to those of us that are interested in using JavaScript in their apps in various ways. It would be an official way to do some of the things enabled by third-party platforms (like Cordova, Appcelerator and Impact) or other binding libraries (such as JSBindings).
— Nigel Brooke at Steamclock Software: Apple’s new Objective-C to Javascript Bridge
Tags: Objective-C JavaScript
Automatic Figure Numbering with CSS Counters
Hugo Giraudel, writing at Codrops. It’s a good technique, and I’m hoping to see figure and figcaption catch on.
Repository redirects are here!
So this seems like such a little thing, but this is tremendously important feature that Github just implemented, and I’ll tell you why:
At the BurlingtonJS meet-up last night (5/15) we were talking about Node.js (naturally) and npm and modules and packages and open source projects in a very general way. And one of the points that was made was that there are tons of projects out there — possibly too many, and that when you look at the overlap between different projects, sometimes (“you can just tell”) it’s because someone found an “almost right” solution, but then shied away from it because that project looked out-of-date. So rather than help patch it up and submit a pull request, they went off and built their own solution. And now there are n+1 modules solving that same problem.
And the point that we tried to drive home (I believe it was @r2r speaking) was that the “right” answer is to take a stab at the patch, submit the pull request, and maybe even offer to take over stewardship of the library.
And these redirects make that sort of thing even easier.
So… thank you GitHub!
Tags: GitHub open source
generators in v8
This post on the generators feature in ES6 (over at wingolog.org) is one of the better ones I’ve seen. It’s a good introduction for someone that’s unfamiliar with them.
“
We carefully gauge real-world usage of things like CSS and DOM features before deprecating anything. At Google we have a copy of the web that we run queries against, so we have a pretty OK idea of what CSS and JavaScript out there is using.
—
Paul Irish on Chrome Moving to Blink
Mat Marquis (Filament Group) interviews Paul Irish (Google) over at A List Apart.
Common Patterns in Styleguides, Boilerplates and Pattern Libraries
Tyler Sticka, writing over at the Cloud Four blog, offers up a round-up or field guide of the styleguides, boilerplates, etc. that are out there — including a spreadsheet to organize the patterns he found.
(1/51)
Next »
