remotesynth

15 ms·

91.
Rethinking DOM Traversal(flippinawesome.org)
2 points by remotesynth 12y ago|0 comments
92.
Simple Content Management with Node.js and Markdown(flippinawesome.org)
2 points by remotesynth 12y ago|0 comments
93.
The State of Hybrid Mobile Development(developer.telerik.com)
3 points by remotesynth 12y ago|0 comments
94.
Slush – A Better Web App Scaffolding Tool(flippinawesome.org)
2 points by remotesynth 12y ago|0 comments
95.
.NET – The Bad Parts(developer.telerik.com)
1 points by remotesynth 12y ago|0 comments
96.
Expose Local Services with ngrok(flippinawesome.org)
1 points by remotesynth 12y ago|0 comments
97.
Using the AWS JavaScript SDK in the Browser(flippinawesome.org)
2 points by remotesynth 12y ago|0 comments
98.
Easier Angular Directives with SweetJS(flippinawesome.org)
1 points by remotesynth 12y ago|0 comments
99.
Code Protection and Packaging for Node.js Projects with JXCore(flippinawesome.org)
8 points by remotesynth 12y ago|0 comments
100.
A Concise Guide to Remote Debugging on iOS, Android, and Windows Phone(developer.telerik.com)
1 points by remotesynth 12y ago|0 comments
101.
Organizing Your CSS Code for Preprocessors(flippinawesome.org)
2 points by remotesynth 12y ago|0 comments
102.
Ten Engagement Strategies to Increase the Profitability of Your Mobile Game(flippinawesome.org)
1 points by remotesynth 12y ago|0 comments
103.
ECMAScript 6: Jump in, the water is warm(flippinawesome.org)
1 points by remotesynth 12y ago|0 comments
104.
Seven JavaScript Quirks I Wish I’d Known About(developer.telerik.com)
8 points by remotesynth 12y ago|0 comments
105.
Will Oculus VR and Amazon Fire TV Change Web App Development?(flippinawesome.org)
2 points by remotesynth 12y ago|0 comments
106.
Lessons Learned Building an HTML5 Games Engine(flippinawesome.org)
5 points by remotesynth 13y ago|0 comments
107.
Improving Browser Detection(flippinawesome.org)
1 points by remotesynth 13y ago|0 comments
108.
by remotesynth 13y ago
I didn't cover that because I think the criteria changes depending on your role and the type of company you work for. For instance, when I was at a large financial company, it needed to be something that was well established, with soli
109.
by remotesynth 13y ago
I don't think I am saying this is a bad thing either. However many people find it overwhelming causing them to react negatively. My goal was, in fact, to turn it into a good thing by helping with strategies to cope.
110.
by remotesynth 13y ago
I've looked into what it would take just to dump jQuery for DOM traversal and manipulation. It can be done in plain JS, but you end up rewriting a lot of methods to fill in the gaps already filled by jQuery. My conclusion was, it'
111.
by remotesynth 13y ago
Thanks! I wasn't aware of those.
112.
by remotesynth 13y ago
If those were the only choices that need to be made, then perhaps it would be easy.
113.
Paralyzed by Choice in Front-end Development(flippinawesome.org)
53 points by remotesynth 13y ago|37 comments
114.
String Templating Considered Harmful(flippinawesome.org)
56 points by remotesynth 13y ago|18 comments
115.
Creating Modular View Components with React and Grunt(flippinawesome.org)
3 points by remotesynth 13y ago|0 comments
116.
Building a Successful Content Site(flippinawesome.org)
1 points by remotesynth 13y ago|0 comments
117.
Improving Speech Recognition in the Browser(flippinawesome.org)
1 points by remotesynth 13y ago|0 comments
118.
Is jQuery Too Big For Mobile?(flippinawesome.org)
47 points by remotesynth 13y ago|55 comments
119.
by remotesynth 13y ago
Great point. I added a link to the project page at the beginning of the article and a link to the downloads at the end.
120.
JXcore – A Node.js Distribution with Multi-threading(flippinawesome.org)
52 points by remotesynth 13y ago|40 comments

More ›