AngularJS ? about pgweb

[sosedoff]

Im open to pretty much any web framework that would simplify development. Currently there's
bunch of jquery code that works, but at some point it will be painful to add new features.

[abourget]

So I was thinking of following in the lead of the Google Web Starter Kit, with some Gulp goodness, angular and following the Google best practices for Angular (there's a Google Doc about it somewhere).

I'm so tired of using pgadmin3 and I think you've found a sweet spot with Go and bindata :-)

[sosedoff]

Great, you can just fork repo and start building up the app. Let me know when you have something to look at.

[abourget]

That would add npm and node as a development dependency. We can still package the whole thing in one executable.. which is so sweet :)

[sosedoff]

I would prefer to have a very minimal amount of dependencies if possible.

[abourget]

ok, so you don't want any of npm/node stuff in there ?

[abourget]

I'll start without

[sosedoff]

I dont mind, just keep number of dependencies as low as possible.

[abourget]

Want to vendor in the angularjs dependencies or use CDNs ?

[abourget]

Also, which browsers do you want to support ?

[abourget]

I guess you're okay with A-grade browsers, as you used jQuery 2+

[sosedoff]

We cant really use CDN as it would break app without internet connection.
Browsers: chrome, safari, firefox and ie. App should be simple enough to work on
last 2 major revisions.

[abourget]

Got it

[miguelcobain]

With the recent announcements regarding AngularJS 2, I think EmberJS is a safer choice.
There will be no migration path between Angular versions.

Just a heads up. It might be worth to wait for Angular 2 as well.

[abourget]

Guys it's all done.. we just need to merge it. Angular is a fine framework, has massive adoption and talent around it. Don't see why we'd need to rewrite it at this point.

#32

We can migrate to AngularJS 2 when we want.

[abourget]

What is that recent announcement ?

[sosedoff]

This will be merged in for 0.5 release. I'd say this could happen in the next couple of weeks.

[miguelcobain]

@abourget Check http://jaxenter.com/angular-2-0-112094.html

tl;dr:

It’s also been confirmed that there will be no migration path from Angular 1.X to 2.0.

I come from an EmberJS background and I was astonished by this announcement. Ember community also puts migration and incremental updates at first.

So, it looks like upgrading to AngularJS 2 won't be as easy as "when we want".
But maybe by then there will be other solutions for that!

Great job on #32!

And sorry for not checking the PR's before, I didn't know you already wrote the Angular version!

[abourget]

It's great that there is innovation on that front, and is yet another reason to learn Angular.

You prefer frameworks that are stuck in the past ? If Ember doesn't have a path for future greatness, it'll rot and become obsolete, along with your knowledge of it. I prefer investing my time learning things that I'll be able to use and reuse for many years, even if that means some work at some point.

AngularJS 1.X won't disappear (the just released Angular 1.3 is already years ahead anyway), but at least there's going to be hope that we can migrate to something even more excellent in the future..

[miguelcobain]

@abourget

First of all, I absolutely DIDN'T mean to turn this into a silly Ember vs Angular discussion. I'm definitely not a fanboy of anything, so I really feel my opinion is unbiased.

Both frameworks are really really awesome, but they're also different. I see frameworks, libraries, operating systems, etc, as tools. You wouldn't fasten a nail with a screwdriver, right? This happens in developers everyday lives as well. Angular and Ember must have their own set of problems and users.
I like Angular, just didn't like that announcement of Angular 2. And many people using angular in production or OSS projects like pgweb didn't like this as well...

However, I must disagree in one thing. Ember isn't at all stuck in the past. There is a difference between stability and stagnation that people don't seem to understand. Ember is stable, but not stalled. Ember's motivation is Stability without Stagnation (credits to @tomdale on this one :D).
Consider reading the brand new Ember 2.0 plan and see the differences for yourself. Also, it is known that Angular will implement features as routing, es6, etc, that Ember is supporting right now.
Ember is now looking at things like Virtual DOM (definitely isn't "past") and borrowing things from React and Angular itself.

I wouldn't say Ember is ahead of Angular and neither vice-versa. They've just taken different paths.

Anyway, my point was to add something of value to this project. And I said that without seeing your PR, and I'm terribly sorry for that!
I seriously believe pgweb is very well served with your hard work at #32! I didn't mean to devalue your work, sorry!

[abourget]

heeheh, sorry @miguelcobain didn't want to irritate.. guess I failed. Shouldn't have said stuck in the past, should've delayed my response too :) . Thanks for pointing the Ember 2.0 roadmap. I actually don't know much about Ember, and I get pretty excited for Angular related stuff. I ask for your forgiveness.

[kenhahn85]

Is this conversion still in progress? ReactJS has taken the JS community by storm, and is a very maintainable way to build front-end apps.

[abourget]

I'm doing more Polymer these days :) You're free to pitch it what you want.. I think we should close this one.

Someone else will take leadership in doing a solid UI..