Live data from Hacker News

Angular 4.0.0 Now Available

angularjs.blogspot.com

331–340 of 360 posts

Re: Angular 4.0.0 Now Available

#331
post #320

Earlier quoted context omitted.

> - It requires more planning to do anything That's the idea. You think about what you're going to write in a strongly typed language rather than just throwing stuff at the wall hoping that something will stick. > - The rigid interfaces mean that I need to spend more time researching how to use various modules/libraries I don't understand this. In one case you have an API where the types of all the functions is avail…

>> - It requires more planning to do anything > That's the idea. You think about what you're going to write in a strongly typed language rather than just throwing stuff at the wall hoping that something will stick. I think this is a valid point for developers who only have a few years of experience but I've been coding professionally for over a decade now - I don't need the compiler to artificially slow me down - I'd…

>I think this is a valid point for developers who only have a few years of experience but I've been coding professionally for over a decade now - I don't need the compiler to artificially slow me down

You'd be surprised.

There's a reason that developers after decades of dynamic languages turn increasingly to types (of which Flow and TS are examples in the JS world).

Re: Angular 4.0.0 Now Available

#332

Earlier quoted context omitted.

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 recom…

Sorry, but this is one of my technical pet peeves. Polymorphism isn't solely an OOP concept. Every language has polymorphism of some sort. Most have several. Duck typing is an example of polymorphism actually. You probably mean "inheritance", which is a way to achieve polymorphism, not a synonym for it.

I think something must have a form before you can say it has many. By your definition a cloud is a polymorph instead of a random shape. If you weaken the definition that much, it takes on a lot less meaning.

Re: Angular 4.0.0 Now Available

#333
post #183

Hmm. I see that Angular is getting aaaaalot of hate here. I really tried to understand why but have not found really valid reasons, just preferences. I have used Angular 1.x a lot and have just tried Angular 2. It really enables me (somebody who comes from primarily strong backend dev experience) to work on frontend SPA apps productively and fast. It does not 'feel' heavyweight or that it gets in my way too much, but…

I wrote https://www.smsforecast.com using Angular2 and personally love the changes made from 1.X, I'm happy to see 4.0 come out along with it's bug fixes and features.

1.X felt messy, but writing web apps in Angular > 2 feels really clean when done right.

Re: Angular 4.0.0 Now Available

#334
Angular is being overengineered, why for example do you need dependency injection having modules system. It's better to go with VueJS, it can do all that is needed being simple, fast, lightweight and VERY developers friendly.

Re: Angular 4.0.0 Now Available

#335

Earlier quoted context omitted.

Sorry, but this is one of my technical pet peeves. Polymorphism isn't solely an OOP concept. Every language has polymorphism of some sort. Most have several. Duck typing is an example of polymorphism actually. You probably mean "inheritance", which is a way to achieve polymorphism, not a synonym for it.

I think something must have a form before you can say it has many. By your definition a cloud is a polymorph instead of a random shape. If you weaken the definition that much, it takes on a lot less meaning.

The wikipedia page lists three types of polymorphism. Duck typing is linked in the page as another kind of polymorphism. I've seen several other types in the wild, such as link-time polymorphism.

https://en.wikipedia.org/wiki/Polymorphism_(computer_science...

The general idea is that you can have one expression dispatch to many different concrete implementations depending on the context. Virtual function calls is one approach, but C uses function pointers, C++ uses templates, dynamic languages use duck typing, several languages use message passing, and so on.

Re: Angular 4.0.0 Now Available

#336
post #125

Earlier quoted context omitted.

It's interesting how OP says people are moving towards more functional-style Javascript, but also dismisses statically typed Javascript. The two work really well together.

I'm convinced functional style is a fad and nothing will change my mind. The style has been around for forever and there's a good reason most languages are still OOP. We're in the phase of the hype loop where everyone assumes language designers from 15 years ago are idiots. In another few years everyone will be talking about the revival of OOP

> nothing will change my mind

This is a HUGE red flag if you're seeking employment long-term in the tech sector.

Re: Angular 4.0.0 Now Available

#337
post #138

Earlier quoted context omitted.

Didn't GWT provide you with type checking on the frontend 10 years back ? Still works, incidentally.

If you are Java heavy, GWT is still a great option. It is extremely mature and can do pretty much everything you want to do.

I'm glad to hear that there are some mature options out there.

Re: Angular 4.0.0 Now Available

#338
post #316

Earlier quoted context omitted.

This still doesn't describe how Angular is objectively "better." In fact, because it requires Javascript just to render HTML, it is objectively worse than straight up HTML delivered from a server-side solution.

> This still doesn't describe how Angular is objectively "better." Of course. Because it isn’t. It’s not worse either. It’s different . It’s a completely different approach to creating web applications. Everyone has different criteria to meet. Working without JavaScript usually isn’t one with modern web applications .

To be clear, I don't eschew JavaScript. Of course you need that for applications. JS stuff goes into a Mako template where I import and call the JS when I need it.

This has the added benefit of extremely small page sizes. Nothing gets loaded globally. Every page has only and exactly what it needs to function properly.

I'm just wondering if I am that much of a dinosaur and I need to invest the time into learning some of these frameworks to be competitive on the market in the future.

What I do works well. It's fast, it's scalable, and I'm very fast at developing with that toolchain. The code is clean, clear, well-organized, and modular. Anyone who knows Python, SQL(Alchemy), and JavaScript can pick it up and work with it.

I can work on any different part of an application without worrying about if it might break something elsewhere. I feel like the patterns I've gotten comfortable with are kind of a sweet spot between micro-services and monolithic. My apps are technically monoliths, but the various modules are clearly isolated.

I'm in my late 30s now, and I want to keep up and not turn into one of those old guys who refuses to stay current. I'm genuinely curious what the value proposition is, outside of learning a new paradigm for its own sake. There's always value in learning new ways to solve problems you already have a good handle on.

But outside of those things, is there some secret magic I'm missing out on?

Post reply on HN