bceagle

Really proud of the Angular community and the hard work of the organizers to make this happen.

Isn't Jasmine used more often than Mocha/Chai on open source? Perhaps just for the front end projects?

The async pipe to do asynchronous binding is pretty sweet. I think (if I remember correctly) they tried to do something like this by default in Angular 1 (i.e. wait until promises resolve and then display the result), but then they took it out because it was causing other issues. If you did want all your bindings to by async in Angular 2, though, I wonder if there is a way to set a global configuration option or something. That way you don't need to include the | async with each binding.

Yes. Updated now. It should have read "6. Server Rendering"

There is a big, big difference between Angular and the other frameworks you mentioned. Angular is part of a larger ecosystem (i.e. JavaScript) that is going through massive changes on its own (i.e. ES6 and all the other new JavaScript goodness). Angular can stand pat and do nothing while the world around them changes, but that is probably not the best strategy either.

Hopefully we didn't come off as too harsh. We were more poking harmless fun than trying to criticize. The Googlers I know that use Dart love it and swear by it.

Fixed now. I am not a fan of blogger.

Did you see the blog post from last week on Angular's efforts to help developers transition from 1 to 2?

http://angularjs.blogspot.com/2015/08/angular-1-and-angular-...

As for little/no benefits, that is certainly not true. Angular 2 is going to be better in almost every way from Angular 1 and there are many great apps built off Angular 1. If you haven't tried Angular 2, I suggest giving it a go once the they get to beta.

Do'ah. Valid criticism. We generated the pie charts from Google Forms (where we had the survey), but we didn't like they way they displayed the results (they were out of order). We should have added the color legend to our sorted results. I will add that later tonight after work. Apologies.

Shoot, yeah, you are right. I am one of the authors. I just updated this, but it looks like the page is cached so will take a couple minutes for it to correctly show 196.

I think it is hard to appreciate DDoS until you are the target. About 7 years ago, my business partner made fun of a hacker who was trying to blackmail us and before we knew it, we were under attack. I didn't even know what DDoS was at that time, but I certainly found out. We had an eCommerce site and it was down hard for three days until we found one of the very few companies providing any level of DDoS protection at that time. We finally got the site back up, but the damage was done. We ended up closing down that business a couple months later.

I have found people that are often the most satisfied at work are the ones that have figured out the best way to play a game with their own emotions and instincts. They understand when they are tired and what makes them tired. The know how to dangle the carrot in front of themselves to get to the next level. Sure, they may dislike work at some instinctual level just like everyone else, but they control that along with everything else in their lives.

There is no doubt Google continues to get better at indexing client side rendered HTML but it is not perfect and indexing is not the same as ranking high in organic search. For ranking, there are distinct advantages to server rendering. The biggest one is consistent initial page load performance. Long story short, if you care about ranking and not just indexing, you still need server rendering.

Yeah, I am in the same boat. I just initiated a chargeback through my credit card. Sucks.

This is somewhat of a response to a lot of discussion recently about how Angular2 doesn't have two-way data binding. It's sort of funny because two-way data binding is a really nice feature for prototyping and getting people started, but it is horrible for building large, robust web apps. I think the Angular team made the right move here, but I hope that they are able to come up with other easy ways to get people started on Angular and enable quick prototyping.

At the end of this presentation Dave seems to show that Angular2 is visibly faster than React. However, he tweeted after his talk:

Full disclosure: In my talk, I accidentally left the setTimeout() for the Angular2 demo at 0ms, while React was at 500ms.

This talk was awesome. Aaron Frost mentioned later that this talk got the first standing ovation in ng-conf history. Whether you love or hate Angular, you will be on the floor laughing your ass off.

Not concerned with performance at all

I would strongly disagree. Watch this link to when Igor talks about Angular performance.

https://www.youtube.com/watch?v=QHulaj5ZxbI&t=35m30s

You would almost never use the runtime checking in production. This is an optional feature that you would only use in development.

This will not be the case at all with Angular2. Most of the "angular" stuff will be in annotations and your code is going to be vanilla ES6 for the most part (well, with TypeScript). So, you actually are going to have a lot more freedom to mix and max other technologies.

Also, FYI, the barrier in 1.x is not that high, either. There are many integrations between Angular and other frameworks (including React, FYI).

For some of my projects the build process is pretty complex and gulp provides true value. However, after thinking about it more you could alway standardize on build through package.json script and if gulp was needed you have package.json refer to the gulp build.

This makes sense but if you are using Gulp for legit reasons with certain projects there is something to be said for doing it for all your projects just to keep things consistent.

Sure, this is annoying, but the reality is that this type of stuff is very easily avoided through the use of linters. IMO, you should never work on a dynamic scripted language like JavaScript without constantly running a linter in the background to pick up stuff like this.

Changes in Angular do not trigger a full re-render. The thing the author is trying to point out is that changes trigger a digest cycle and a digest cycle can (in some situations, not all) take a long time to figure out what has changed. But, once it figures out what has changed, it will only change those specific elements in the DOM.

At the end of the day, what we are talking about is Angular 1.x is not as efficient as React at figuring out what to modify in the DOM.

However, just be aware that this will all change in Angular2 where you can use an immutable data structure (just like React) or observable (if the situation warrants it) to quickly figure out what DOM updates need to occur. Read here for more:

http://victorsavkin.com/post/110170125256/change-detection-i...

I have to say this past month living in Boston has been really challenging on so many levels. Tension from difficulties getting to work, playing chicken on the narrow roadways, inability to get out of the house with the kids, finding baby sitters to cover when school is cancelled and the never ending shoveling. I love Boston, but I would not be able to take many more winters like this one.

If I had to narrow things down to one primary issue, though, I would have to say it is the total failure of the public transit system, the MBTA. Things wouldn't be nearly as bad if the T was running smoothly, but even now the commuter rail is running on a reduced schedule (which results in completely packed trains that are often late) and various subways trains break down on a daily basis.

Not fun.

I think James is on target in many ways, but I just wish it wasn't such a bleak near term outlook for high end mobile web apps. I don't want to write my app differently for different devices. I know that is the reality of today, but it is an unfortunate reality.

That said, many apps don't need to push the limits and PhoneGap or a similar solution is sufficient.

Check out this episode of JavaScript Jabber for a good explanation of io.js:

http://devchat.tv/js-jabber/147-jsj-io-js-with-isaac-schleut...

tl;dr is that all the core contributors outside Joyent started working on io.js with an open governance model. Everyone wants to join back together but only after Joyent agrees to put node under the same governance model.

So it won't actually use web views? Interesting.

This is really just a compilation of previous rants against Angular. If you want to get a more balanced view, you can read my article dealing with a lot of this: https://medium.com/@jeffwhelpley/screw-you-angular-62b3889fd...

There are a few comments here that imply the problem with Boston is the weather or culture. That is way off base. Of course there are people that hate the weather or don't like the culture, but there are just as many people that love it.

Also, while Boston doesn't have a huge consumer success story, the startup and tech scene is thriving. Just spend a couple months going to meetup groups or other events like the CIC Venture Cafe and you will understand.

The problem as the author alludes to is not with starting companies, but growing them. More specifically, there is no doubt funding for consumer-based companies is easier in the bay area. It really bummed me out to see Technical Machines and Platiq move to the San Fran.

That said, I do think things can and will eventually change. Paul English and others have started to heavily invest in consumer based businesses in Boston. I believe like he does that other than the issues getting funding, there is no reason why consumer based businesses can't thrive here.