Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
AngularJS is everything I expect from a framework. That’s not a good thing. In November, December, and January, I reviewed AngularJS for Let’s Code JavaScript’s “front-end frameworks” series. All together, I spent forty hours researching, coding, and problem-solving. As usual, my goal was to explore and critique AngularJS by creating a real application. 
No comment yet.
Sign up to comment
Scoop.it!
* Composition
Scoop.it!
We just rewrote our dashboard using Facebook’s React.js framework and the Flux application architecture. Here are some things we learned along the way.
Scoop.it!
As much as I enjoyed Ember’s ambition, I’ll admit that I was bearish on the future of the framework. Angular was the next obvious step beyond Backbone and I worried that Ember had bit off more than it could chew. Today Ember may not be as popular as Angular or Backbone, but I am bullish about its future. We’ve seen a growing number of companies using Ember, but to me, it’s all about the benefits for developers.
Scoop.it!
I've been developing Single-Page Applications for a while. I started using plain JavaScript, then jQuery, then a bunch of other crazy libraries, to then finally settle with AngularJS. I've been a fan since day one, and I believe users can benefit a lot from them.
Scoop.it!
For Daniel and many React devs, there is no debate. If you care about performance, you use React instead of Angular. Period. I don’t think it is quite that simple. Performance is a means to an end. The real goal is providing a great user experience. No doubt speed matters, but not all changes in speed are perceived by humans the same way.
Scoop.it!
Not everything with Angular.js is bad and team behind it is brilliant. Vojta Jína did fantastic job with new DI container. Misko Hevery wrote awesome articles about TDD and writing testable code. And more. But I suppose initial decisions were wrong therefore I consider Angular as dead end. Is Angular worth the risk? No.
Scoop.it!
Unless you’ve been living under a rock (or perhaps in a van down by the river) you may have noticed that Node.js is kind of a big deal. Since its introduction in late 2009, Node has steadily grown in popularity and now occupies prime real estate as a (if not *the*) de facto choice of server-side infrastructure for the modern web stack. Node’s popularity is based on a few distinct advantages relative to its competition. First, Node is fast and very scalable, due to its lightweight hosting model and default pattern of asynchronous I/O (which is a fancy way of saying Node doesn’t wait around doing nothing while that 5 second database query you just issued hasn’t returned yet). Second, in contrast to its power, Node’s core programming model (the concepts needed to understand “the Node way”, and the actual APIs that implement those concepts) is very simple and straightforward.
Jan Hesse's insight:
Scoop.it!
Meteor blurs the line between client and server, and actually takes advantage of the fact that it’s all Javascript. Methods are functions that can be invoked from the client, the server, or both. With Meteor, you’re actually sharing big chunks of code between the client and server. While it’s possible to do something similar using ember/node, it’s difficult enough that most people don’t do it. This really changes how you build things. More client/server sharing = less code = less work and fewer errors.
Henrik Våglin's curator insight,
August 17, 2014 7:40 AM
Yes it is, but I'll waiting for a 1.0 release before I'll take a serious look myself...
Scoop.it!
The technology should serve the team. I think Angular does that well, but other solutions may be a better fit for your team, given experience, mindset, project history, or other factors. Angular covers a good range of functionality for building robust web applications. Wintellect has used Angular successfully on very large enterprise projects, using hundreds of controllers, services, and directives. It worked well for us on a large, distributed team.
Scoop.it!
JavaScript front-end codebases grow larger and more difficult to maintain. As a way to solve this issue developers have been turning to MVC frameworks which promise increased productivity and maintainable code. InfoQ asked the opinion of experts practitioners about how they use these frameworks and the best practices they follow when developing JavaScript applications. We'll go beyond buzzwords and get practical insight from experts about what has actually worked for them. We'll also talk about technologies (like AngularJS) that go a step further, and define the future of how the standards and web development will evolve.
Scoop.it!
From
lemur
My plan was initially quite complicated, but i took a step back in the planning phase and set myself a first goal: the app must be simple. Like first Twitter was simple. Only implement basic functions and make it usable. It was going to be a place where you can ask questions, with a fixed number of answers, and other people could answer them anonymously. It would not need images (except kittens) and will have the smallest number of pages possible.
Scoop.it!
What are the chances to mess up? There are a few. From what I gathered at several events and from various talks I see the following dangers:
|
Scoop.it!
How to Stop Micromanaging Everything Over the course of the next few years, the way we code is going to change in radical ways, pushing us in a fundamentally different direction than the one we’ve been sprinting for the past 30 years or so. These changes will lead to many important breakthroughs in programming techniques, processes, application scalability, and quality controls.
Scoop.it!
You can achieve a lot with HTML5 and CSS, but only if you employ JavaScript libraries as well. It used to be possible to restrict down to one or two libraries, but nowadays, the pressure is on to do more with a web page with such features as touch gestures, dynamic DOM updates or CSS switches. Is there such a thing as too much Javascript? Are we near the limits of what we can do with this technology?
Scoop.it!
After dealing with the pain for some time, we convinced the appropriate parties that it would be best to switch to a more mature and fully baked framework. When evaluating new frameworks, we took the following things into consideration:
Scoop.it!
While these individual libraries and the resulting custom stack have the potential to do some things very well, the unfortunate reality is that a great deal of the functionality must be gathered together from disparate sources, written in-house and require a dedicated team of maintainers in order to meet the demands of enterprise software development.
Delchina Angelova's curator insight,
October 27, 2014 11:01 AM
Not sure the compare is fair but questions are good.
Scoop.it!
Developer Michael Perrenoud describes what it's like for .NET developers who want to explore the MEAN stack -- MongoDB, Expressjs, AngularJS, and Node.js I was standing in the middle of a matrix I'd avoided for a very long time: Microsoft vs. The World. It was a decision I thought I'd never have to make. Here I was, 33 years old and feeling like a dinosaur. Don't get me wrong, the skill set I had wasn't so out of date that it was already dead, but I could feel the market shifting. I knew that if I didn't make a change, in 10 years, I'd be staring down that same barrel those COBOL friends of mine were right now.
Scoop.it!
Contents:
Scoop.it!
The following is my step-by-step refactoring path, including close look at some MVC-ish solutions. You can use it to get ideas on revamping your own spaghetti app, and/or to see how to approach design of <canvas>-based app, specifically. Each step is made as a separate commit in fabricjs.com repo on github.
Scoop.it!
9 anti-patterns for teams moving to node.js. Learn from the experience we've had in adopting node.js at PayPal.
Scoop.it!
In doing our trainings and in writing my book, Human JavaScript and within our team itself we’ve come to realize there is a huge gap between picking a tool, framework, or library andactually building a complete application. Not to mention, there are huge problems surrounding how to actually build an app as a team without stomping on each other. There are sooooo many options and patterns on how to structure, build, and deploy applications beyond just picking a framework. Few people seem to be talking about how to do all of that, which is just as big of a rabbit hole as picking a framework!
Scoop.it!
Are you a programmer who is considering learning JavaScript, but unsure whether it is worth the pain? Then this blog post is for you: I argue that it is worth it and give tips for surviving the language. Contents:
Scoop.it!
From
yauh
Meteor is the new isomorphic JavaScript framework that will make developer's lives so much easier and make users fall in love with your app again. I recently published a rather sarcastic article based on all the FUD I have been hearing the last couple of weeks about what I believe...
Scoop.it!
Single page web applications - or SPAs, as they are commonly referred to - are quickly becoming the de facto standard for web app development. The fact that a major part of the app runs inside a single web page makes it very interesting and appealing, and the accelerated growth of browser capabilities pushes us closer to the day, when all apps run entirely in the browser.
|
