zygimantasdev

I always kept hearing that elastic search was a great product, helped to solve some difficult problems and was open source. However, when I wanted to use it I quickly found out that some important features are paid only. And the licenses cost a ton. It felt very disingenuous for it to be called open source when there are things I cannot use for personal or commercial use. Amazon enabled me to use this stack the way I wanted and now again I think elastic search is a great product. Reputation wise I think Amazon's move will only help them. Not sure business wise

I wonder if the idea for this attack came from Silicon Valley tv series

You can reuse almost as much without forcing one framework for all teams - making it not least efficient way possible. Not using one tool will encourage team to explore new possibilities, alternatives, learn new paradigms and thinking. In long term this is certainly more effective.

Web is not dead simple (I consider web to be frontend development in this context). Why I would consider web to be hard: - it is harder to do frontend development than backend, because you write code which is sent to one of thousand different compilers, creating another layer of difficulty. Versus controlled environment where your backend code is being run - While there are only few patterns which are applied to FE development, there are many new features(PWAs, real time syncs,..) coming into web. Taking advantage of them requires learning, coding and refactoring. You might say - this is just reinventing the wheel - while partly that is true, developers will still need to learn, adapt knowledge to web, build tools.

The problem is how will you find that your tech has stagnated? If nobody experiments with new tech - who will teach others? How will that knowledge come into your corp? Hiring new people to do that will not work, because: - People being hired will be evaluated by legacy people (different thinking will be considered disadvantage during interviews) - Legacy people will not listen to new hires since they have no credibility and it "has been the way it was always done"

>At the mid-size corporation that I work at, we just standardized all Javascript development on Angular from a mismash of a ton of technologies. Angular seems very well suited for this role.

In my experience centralisation and fixation on specific technology leads to stagnation quickly. IMO you should allow teams to choose their own tools. How else will you improve?

Wouldn't be suprised if somebody from techcrunch owned those 12 shares just so they can write this clickbaity article

Not directly related to the article, but IMO CSS is good for what we have now. There is no better alternative. As for Javascript - there are many great alternatives. (Scalajs, Purescript, Elm, Typescript,...)

As EU citizen I wouldn't mind. If these corps decide its not profitable for them - for sure an alternative will pop. (Currently using two of those services)

Are you sure it works for vast majority of users? At least in my developers circle who use macOS for web* development - all of them have issues with docker high cpu usage due IO. Some use docker-sync to go around the issue.

As for bug reports - zero feedback from anyone on that thread from maintainers. If you are one of the maintainers - it might be good to write this comment on that thread instead of HN

* - I understand that web developers might be a small percentage of users and my case doesn't represent everybody

Using Angular2 for 10 months now. Can say it has been a pleasure to work with it. Sure there are some problems - but it is open source. Free. Can't be complaining about stuff you get for free ;)

One thing - name of the framework should have been something different. At first we thought it is going to be called Angular2 and later it became just Angular. You can imagine that whole community will have to rename their libraries and etc.

In overall, big thank you from our frontend team for giving us a great framework

At least it is fast. [1]

1345MB/s sequential write

2000MB/s sequential read

And 13 inch model's SSD is replaceable [2]

[1] - http://wccftech.com/macbook-pro-2016-fastest-stock-ssd/

[2] - http://wccftech.com/macbook-pro-13-inch-ssd-fast-replaceable...

[()] indicates two-way binding. If you curious you can read more in docs [1], while ngFor is just an attribute directive which changes DOM [2]

[1] - https://angular.io/docs/ts/latest/guide/template-syntax.html... [2] - https://angular.io/docs/ts/latest/guide/attribute-directives...

Looks really good. Thanks!

Thanks for the tips! Already had been trying to understand css tricks - but always looking for more relevant information in one place - a book.

Thanks - will check it out. Although from a quick glimpse at the reviews it seems a little bit outdated.

Will check it out - thanks

Looks really good. Thank you!

Thanks for the answer. I will check it - never thought of doing that!