Angular Material 1 will enter a maintenance mode • Hacker News Board

Re: Angular Material 1 will enter a maintenance mode

#51

Post by Someone » Mon, Jun 06, 2016, 8:37 PM UTC

lyschoening wrote: post #31

Someone wrote: post #22

Earlier quoted context omitted.

Doing that takes somewhat of a leap of faith. Why would one believe that, a year from now, we won't be in the situation of "Angular Material 2 is still missing a few essentials, but it is a good idea to speed up work on Material 3 now. Angular 3 will be out soon and many people will be unable to switch until Material 3 has caught up with the original." ? If one fears that, it may be better to switch to another librar…

I am also a bit afraid about the future of Angular, primarily because the Angular team is working on way too many projects that sometimes seem needlessly complex. I don't think anyone could pick this up for Google if they dropped the ball on Angular. A hypothetical Angular 3 worries me less. The bulk of the differences between Angular 1 and Angular 2 come down to making use of technical improvements to JavaScript its…

"There will be further changes in the future, but nothing as radical as modules, classes and the different asynchronous-related features"

I expect huge changes. I foresee a future where each webpage is an almost empty tag that does little more than defining a grid that loads a big blob of WebAssembly that builds the actual 'page' (if you can still call it that by that time). One advantage would be that, say, a Python or Rust framework can run Python/Rust in the browser. Another 'advantage' would be that large companies could keep their front-end code more secret (WebAssembly obfuscates better than minifying does)

Re: Angular Material 1 will enter a maintenance mode

#52

Post by franciscop » Mon, Jun 06, 2016, 9:53 PM UTC

nixgeek wrote: post #18

franciscop wrote: post #3

I am the author of a slightly popular CSS library [1] and JS library [2] and I feel the pain explained here, trying to keep up the pace of issues and PR is daunting. However, cmon Google! You are not a sole developer lost somewhere in Spain. Get your act together and really support your own libraries for a sensible amount of time. Or hire more people to do so. [1] http://picnicss.com/ [2] http://umbrellajs.com/

Not sure if sarcastic or serious. It seems to me that a major problem for Open Source in 2016 is assumption of support from the originating entity or person. Does this base assumption not risk alienating individuals and organisations into saying, "Should I release this at all?". Why should they hire people to support something which generates, as far as I can see, no revenue for Google?

English is not my native language so I apologize for the misunderstanding, I didn't mean any sarcasm here.

There is a big difference between releasing software "as-is", and saying - or making it look like - it will be supported for a long time:

> "it was previously stated that Angular 1 will be supported for a long time to come" - Zach Bjornson

Arguably, one of the main goals of Open Source is to be used. If companies that set expectations of support don't support it, then I think the future of Open Source is really doomed.

Re: Angular Material 1 will enter a maintenance mode

#53

Post by whamlastxmas » Mon, Jun 06, 2016, 10:45 PM UTC

beeker87 wrote: post #38

I truly feel sorry for those who started learning web development somewhere between 2009 and 2014. During that time, it seems like what would be accepted as the new standard for creating web applications was completely up for grabs. You had Angular, Backbone, Ember, and probably many others that just didn't get noticed. Can you imagine being a new developer during this time, trying to learn how to create a web applic…

>are we trying to have every site look and function just like the Google platform now?

The internet would be a thousand times better if every website used Material Design properly. The amount of broken and poorly designed bullshit out there is staggering. Websites worth tens or hundreds of millions of dollars flat out not working. Or working so slowly they may as well just not work. Even the ones that wind up working, they have horrific UI/UX decisions.

Re: Angular Material 1 will enter a maintenance mode

#54

Post by xviia » Tue, Jun 07, 2016, 2:13 AM UTC

spinlock wrote: post #29

xviia wrote: post #19

I have determined that relying on Google products is just a bad idea. I once included Google's V8 engine on a project I was working on. Google would regularly make breaking changes with no documentation . Developers were required to figure out the new interface on their own... occasionally you would find someone else on a forum somewhere who had reverse engineered it, saving you the time. Sure, Google can do whatever…

Google does expect you to put in a lot of continuing effort to use their APIs as well. I suspect this is deeply engrained in their culture.

If by "continuing effort" you mean, "parsing new errors in your build, realizing that functions you used have been removed, and finding no information on the web", then yes, I absolutely agree

Re: Angular Material 1 will enter a maintenance mode

#55

Post by lamontcg » Tue, Jun 07, 2016, 4:54 PM UTC

lamontcg wrote: post #35

Redoubts wrote: post #14

Earlier quoted context omitted.

I understand closing PRs if they're complicated and out of scope, but closing issues doesn't make sense. These bugs don't go away just because the primary developers are leaving.

Closed issues don't go away. Lots of bugs are edge conditions that not enough people care about for the developers to ever pay any attention to fixing. They fall under the category of "sure, and if you submit a PR, we'll merge it". I imagine there's also issues for architectural problems with 1.x which will never, ever get fixed because nobody will be willing to spent the time massively refactoring the codebase. From…

Relevant link that just popped up on HN 24 hours later:

https://blog.jessfraz.com/post/the-art-of-closing/

If active project are always supposed to be closing, then deprecated 1.x branches of projects should have an even higher bar for anything they keep around open.

Re: Angular Material 1 will enter a maintenance mode

#56

Post by spinlock » Tue, Jun 07, 2016, 9:38 PM UTC

btdiehr wrote: post #47

spinlock wrote: post #30

Earlier quoted context omitted.

This is just going from version 1 to version 2. It's not like the new framework[1] that's replaced React. /s 1: https://github.com/developit/preact

Except preact won't replace react.

I'm pretty sure it already has.