tomdale

22 ms·

151.
The new emberjs.com(emberjs.com)
143 points by tomdale 14y ago|47 comments
152.
SVPullToRefresh - Give pull-to-refresh to any UIScrollView with 1 line of code(github.com)
2 points by tomdale 14y ago|0 comments
153.
by tomdale 14y ago
When Mozilla ships better developer tools than Chrome, I'm sure there will be posts just like this one. The fact that developers prefer Chrome is not a failing of developers; it's a failing of Mozilla to provide compelling tools.
154.
by tomdale 14y ago
This is a great resource and I'm glad Majd wrote it. However, this is really the kind of content that should be coming out of Google itself. Google is in an interesting position. Of all of the major Silicon Valley tech companies, I think Go
155.
Modern Web Development(jtaby.com)
605 points by tomdale 14y ago|85 comments
156.
by tomdale 15y ago
I wouldn't say that the sun is setting on Rails-style MVC frameworks, but I do think their role in the ecosystem is going to change. Before, most people could get away with writing the entirety of their app as a single Rails or Django app.
157.
by tomdale 15y ago
As I noted in my lunch talk at Carbon 5 the other day, Ember.js optimizes for developer productivity--which is not to say that you can't have multiple goals, but at the end of the day, one thing has to be your priority. For the past few mon
158.
by tomdale 15y ago
On the contrary, I've found the discourse between Jeremy and Yehuda vigorous, respectful, and edifying. In my opinion, these are the best kinds of technical discussions; they are like a rock tumbler that wears away at our solutions until we
159.
by tomdale 15y ago
Hey, Ember.js maintainer here-- Luckily, providing a widget library is, and will always be, outside the scope of Ember.js. While we'd be quite pleased to see someone else develop a widget library on top of Ember, it's not something that we'
160.
by tomdale 15y ago
This story is very sensational and pretty wildly inaccurate. Like many companies, your experience at Apple will vary based on which group you join. I wouldn't call my series of interviews more daunting than any other major Silicon Valley co
161.
AMD is Not the Answer(tomdale.net)
39 points by tomdale 15y ago|2 comments
162.
by tomdale 15y ago
From the article: This is also known as the principle of abstraction, because it means that it is easy to refactor common code into methods that take a block. I can attest that quickly refactoring code in Ruby is much more straightforward
163.
by tomdale 15y ago
Updated to be more clear; thanks!
164.
by tomdale 15y ago
But both seemed to suffer the same problem, they are quite monolithic, everything is build around the fact your app is a 'backbone' or an 'ember' application, they arent just libraries that provide specific functionality. Isn't that the r
165.
by tomdale 15y ago
The point of Ember.js is to reduce the amount of boilerplate a developer needs to write to perform common tasks. I think Thomas did a good job of explaining how you can accomplish the same thing in Ember.js with fewer lines of code (and rem
166.
by tomdale 15y ago
Would this be useful for environments where extreme performance is necessary, such as Fibonacci API servers?
167.
by tomdale 15y ago
Sure, but then you have to create a function for each property, even if it's a number or a string. Those bytes add up significantly in large applications. Additionally, specifying the property as a string allows you to implement "unknown pr
168.
by tomdale 15y ago
The advantage of using accessors is that your implementation can switch between static properties and computed properties and the consumers of your API don't have to know which is which. This is called the uniform access principle and ends
169.
by tomdale 15y ago
Just to be clear: all existing SproutCore 2.0 apps are Amber apps. It's a brand change, not a code change.
170.
by tomdale 15y ago
Handlebars (handlebarsjs.com) solves several of these issues: Items in lists don't have to be objects with fields; you can display primitives like strings and numbers by using {{this}}: {{#each tags}} <li><a href="tags.h
171.
Easily deploy web applications with Strobe [screencast](vimeo.com)
20 points by tomdale 15y ago|1 comments
172.
by tomdale 15y ago
To be fair, this book is about libraries that are strictly MVC implemented in JavaScript, and no more. At the time Alex was writing the book, SproutCore 1.4 was the current version, and is obviously a "full-stack" framework, including a UI
173.
by tomdale 15y ago
I respectfully disagree. The paradox of choice is not, I think, controversial to anyone here. There is a cognitive burden to new web developers when deciding which framework to use. Often times, they'll make the wrong choice, say "forget it
174.
Building the Next Generation of Mobile Web Apps(jtaby.com)
12 points by tomdale 15y ago|6 comments
175.
by tomdale 15y ago
Great post. I think it is important that more developers learn the importance of managing state. Almost every application ends up with the kind of bugs where you have two properties set on an object that are mutually exclusive, and you can
176.
Using SproutCore 2.0 with jQuery UI(yehudakatz.com)
22 points by tomdale 15y ago|0 comments
177.
by tomdale 15y ago
We have been working on several JavaScript-related tools that build on top of RubyGems. The most recent versions of RubyGems issued what were, IMO, user hostile deprecation warnings, which confused and alarmed our end users. We were not awa
178.
by tomdale 15y ago
Not at all! I'll clean up the wording. Thanks!
179.
by tomdale 15y ago
I had that originally in the House Rules section but removed it. I'll reconsider the best way to word this without trying to cause a server/browser JS flamewar.
180.
by tomdale 15y ago
Would you be willing to submit a pull request? I don't know enough about MooTools but would be happy to merge.

More ›