Live data from Hacker News

Angular 4.0.0 Now Available

angularjs.blogspot.com

111–120 of 360 posts

Re: Angular 4.0.0 Now Available

#111
post #90

Earlier quoted context omitted.

I really don't want to sound like an ass, but if you were at the stage of 'learning AJAX' a couple of months ago you are probably not in a position to judge the merits of JS frameworks like React, Vue or Angular.

As someone who is new to React, Angular, Vue, etc., he/she is in the PERFECT position to judge them. Libraries/frameworks are not just about performance, but how you learn them as well. Those frameworks/libraries don't write themselves.

Frameworks are also about comprehensiveness. The start of the learning curve is not the sine qua non. That always reminds me of those complaints that writing a "Hello World" application in your GUI library of choice requires plenty of boiler plate etc., but you're probably not going to spend your developer life doing that. Often benefits for larger apps aren't obvious for the neophyte.

This is really aggravated that -- as opposed to native GUI libraries -- frontend requirements vary wildly. You might just need it to embellish some elements (i.e. the jquery level), you might also use it to build some large desktop app replacement.

Which is why I take most comparisons with a large grain of salt. In this regard, "JS framework XYZ sucks/rules" is the new "PHP is great/awful".

Re: Angular 4.0.0 Now Available

#112

I'll probably try it. But man, am I getting jaded about all this javascript framework stuff. Every 6 months stuff breaks, every 2 years there's a huge shift. The problem with javascript I've been facing is value. Time and effort doesn't always correlate to what I get in the other end. In fact, I can say when building, going single-page is a time sink. And it's almost always a mistake to go SPA first. Using a django o…

Look into polymer. Let's you do server side rendering then use custom web components for the widgets needing interactivity.

I found building sites this way refreshing.

Re: Angular 4.0.0 Now Available

#113

I'll probably try it. But man, am I getting jaded about all this javascript framework stuff. Every 6 months stuff breaks, every 2 years there's a huge shift. The problem with javascript I've been facing is value. Time and effort doesn't always correlate to what I get in the other end. In fact, I can say when building, going single-page is a time sink. And it's almost always a mistake to go SPA first. Using a django o…

You should try ClojureScript. Much simpler tooling (native tooling on top of Google Closure), nice integration of server and client side code.

We are not quite at the point of using NodeJs on the backend normally (and honestly the JVM is 100x better) but you can share the language.

You want get a django or rails like app at the moment.

Re: Angular 4.0.0 Now Available

#114

Angular core team here, we're pretty excited about this release. Main change, as noted, is the new View Engine. The design doc[0] is worth a read if you're interested in front-end at all. Happy to answer any questions! [0] https://docs.google.com/document/d/195L4WaDSoI_kkW094LlShH6g...

Can we expect Angular 4 best practices before 2020?

Re: Angular 4.0.0 Now Available

#115

I'll be that guy. I'm sure the Angular team are great people, and they're clearly talented devs... but stay away from Angular. It doesn't help with the problems you will actually face. Typed Javascript is a cargo cult. Angular just plain confusing for no apparent benefit. Dependency injection is bizarre. The distinction between modules, components, and directive is unnecessary. The Javascript community in general is…

My guess would be that static-typing is what they're trying to add albeit in an OOP form.

Javascript is more of a 'Prototype' based language. They call things 'Object's but I've seen few portions of JS code that actually use OOP in the traditional sense (encapsulation, polymorphism, etc)[0]. Mostly objects are just used for namespaces for finding vars and functions.

Agreed on the frameworks versus libs.

I would recommend that you work on a large codebase in a statically-typed language for a spell. Duck-typing is great for a shell script or blog post but things may be different when refactoring 100k lines of code, finding references, etc.

[0] Yes I know about the JS 'library' 'pattern'. That's more gymnastics than encapsulation.

Re: Angular 4.0.0 Now Available

#116

Can anyone from Angular team please make integration with Google Cloud Endpoints, or at least show how it's done? the official documentation is for AngularJS 1.x: https://cloud.google.com/solutions/angularjs-cloud-endpoints...

Hi wiradiksuma. Ive filed a request internally to update the docs. Feel free to email me at bookman@google.com to get status updates.

Re: Angular 4.0.0 Now Available

#117
post #106

Earlier quoted context omitted.

I have a question. Who thought it was a good idea to make Angular 2 incompatible with Angular 1? You had it, and you blew it. Most people aren't going to use any version of Angular, now, and have switched to React and Vue.

"Who thought it was a good idea to make Angular 2 incompatible with Angular 1?" This is so much discussed that I am not going to answer that. Google it. But according to the latest StackOverflow survey [1] Angular is still bigger than you think: AngularJS 44.3%, React 19.5% [1] http://stackoverflow.com/insights/survey/2017/

Because Angular was the only real choice for awhile. That's like saying PHP is still bigger than you think because half the web runs on PHP but that is old legacy shit. Almost othing new and serious is using it.

Re: Angular 4.0.0 Now Available

#118

Earlier quoted context omitted.

I really don't want to sound like an ass, but if you were at the stage of 'learning AJAX' a couple of months ago you are probably not in a position to judge the merits of JS frameworks like React, Vue or Angular.

Despite being new to AJAX, I wrote a Vue app within a week, 4-5 weeks into reading Angular, I was still reading the docs. Edit: removed a brash statement.

Yes and no. It says as much about you as it says about Angular or Vue. Look, Angular is far from being my favorite framework, and I have nothing against Vue, I'm more of a ClojureScript / om.next guy myself. I'm just really allergic to brash statements about frameworks, or hype in general.

How easy it is to get up and running with a framework doesn't actually tell me that much about the framework. Is the apparent simplicity simply an artefact of a huge layer of magic that I will end up fighting 4 months down the row?

A good example for this is actually the much maligned Angular 1, two-way data binding looks easy on the surface, but it comes with a cost. And guess what, two-way data binding was all the rage for a while in the HN echo chamber during the early days of Ember, Angular and Knockout.

In the end, whether you use Angular, React or Vue is really secondary to what you build with it. You can create shitty and good code with all of them.

Now, specifically about Angular2+. People act as if its approach was this awful, monstrous abomination. This all really depends on your circumstance tho, or not? There are instances where it makes perfect sense to tailor your setup and use a libraries-first approach. But if you do this, let's say in React, you need to make a lot of decisions up front. Do you want manage state? How? Redux? MobX? What about message buses? Do you want to use Flow? Just ES6 / Babel? TypeScript? What about routing? Lazy-loading? What about bundling? Webpack? Rollup? And so on.

Now, if you are part of a heterogenous developer team working in an enterprise shop, maybe you are happy to know that there is a framework that has made a lot of decisions already for you and prevents you from having to discuss the initial setup for 2 months, but at the same time is flexible enough to be adapted to your needs (I mean, this even applies to experienced front-end shops, there's nothing more horrible than endless discussions about shit like pure ES6 vs Flow vs TypeScript from senior devs). On top of that it uses patterns that you already know, such as dependency injection and annotations. While you personally might not feel at ease with this, many developers do.

Re: Angular 4.0.0 Now Available

#119

I'll be that guy. I'm sure the Angular team are great people, and they're clearly talented devs... but stay away from Angular. It doesn't help with the problems you will actually face. Typed Javascript is a cargo cult. Angular just plain confusing for no apparent benefit. Dependency injection is bizarre. The distinction between modules, components, and directive is unnecessary. The Javascript community in general is…

Holy smokes, I can't believe how serendipitous this is. I am 5 minutes into a Pluralsight course on Angular 2. I really like the idea of Typscript, but now... now I guess back to the drawing board on what to learn.

If you're going to switch JS frameworks every time some hipster on HN tells you to, you're never going to get anything done. Use Angular/TS if you like it.

Re: Angular 4.0.0 Now Available

#120
post #109

Earlier quoted context omitted.

Despite being new to AJAX, I wrote a Vue app within a week, 4-5 weeks into reading Angular, I was still reading the docs. Edit: removed a brash statement.

It says nothing more than Angular has a lot more documentation. Perhaps because Angular has a lot more features.

Please note that I didn't say Angular sucks. I merely pointed out that Vue is easy to learn.

I am hardly an expert on either Angular/Vue to recommend them based on their internals, I stated my experience, of course, the final decision depends on those who choose one framework over another.

Post reply on HN