hccampos

I am also one of the developers of the original Goo Create (worked on it between 2014 and the end of 2016) and I can confirm it is indeed the same app (including colors, icons, etc). Amazon basically just added some integrations with AWS and a new logo.

It is the evolution of it indeed. Amazon got the code after Goo Technologies went bankrupt, added some integrations with AWS and rebranded it.

As others have mentioned, this is all possible with Angular >=4, both in WebStorm and VSCode. The main issue is with performance and debugging. Using Angular's AoT compilation is still extremely slow and your squiggly lines take several seconds to show up after you modify a template in your editor. And no stepping through templates either when trying to debug why something isn't rendering properly.

But, imho, the biggest problem with Angular, by far, are it's NgModules. You can't just import a component normally and use it in your template. You need to also add it to an NgModule to make it available in the templates of the components inside that NgModule. And if for some reason you stop using a component, you need to remember to clean up the module as well since nothing will warn you about unused declarations or imports in NgModules.

And then there is also the fact that you can't directly import a function/constant and use it directly in the template because, like Components, the template engine needs to be told about it. So you need to add properties to your component class which are just providing access to things you imported above. So. Much. Pain.

Some people really like templating languages but imho just using TSX (which is just mapping to function calls) and normal ES modules is the best solution by far.

Problem is you get a cumbersome templating language, extremely verbose component declarations, even more verbose dynamic components and a bunch of other horrible stuff.

In React it is a breeze to make Higher Order Components to connect to a store and it also makes it much easier to separate those smart components from small reusable presentation components.

I have seen people shy away from making smaller components just because Angular makes it so damned painful to make components. It is just easier to stuff everything in a template and copy paste everything around, which leads to a serious case of spaghetti code. I am happy for you if you don't have to work with something like that. I do, and I can tell you it is not nice in any way.

Well, the more people are aware of how bad Angular are, hopefully the less momentum it will get and the less jobs using it there will be.

This makes me feel sad. As you said, maybe React could do more when it comes to packaging things up. I think Create React App is a good step in that direction but there is still work to be done.

For most apps, yes I think MobX is easier. However, both of them, combined with React/Preact are hugely superior to Angular.

If you don't like TS stay away from Angular. In fact, just stay away from Angular, even if you like TS. You will save yourself a lot of headaches...but hey with Angular you might be able to hire some cheap/junior programmers who are familiar with OOP or move some backend guys who like C#/Java to do frontend.

I have to agree with your general point.

However, to me it's not really that Angular is bad in itself, it's more that the alternatives (React/Inferno/Preact combined with redux or MobX) are just superior in so many ways, and by a huge margin.

Once you've done React with TS/TSX, with type checked components all the way, great code completion, incredible performance...it's hard to go back.

Angular's components would be ok if React didn't allow you to declare functional components in just a few lines of code, create HOC to decorate exiting components, etc. Angular's components are certainly better than Angular 1's but when you compare it with what you can do with React it just can't compete.

Honestly, from my experience, there is not a single thing that Angular does better than React and friends. Not a single one. It does things better than Angular 1/Ember/Backbone but that's it.

I think this is a bit like the solar/renewables revolution that is happening in energy. There are more efficient combustion engines, filters and whatnot, but when you compare them with the other paradigm, it falls short.

Is it just me, or this is a the very least completely ridiculous?

I wonder how noticeable the recent performance improvements really are.

I have been on VSCode for a while but might give Atom a try for a change, and see how much it has evolved.

While this is fun to play around with, and definitely helpful when using threejs directly, for a fullblown editor on the web there is nothing that beats PlayCanvas at the moment.

This might be useful for people who want to get started with WebGL and web-based 3D engines:

https://playcanvas.com/ http://babylonjs.com/ https://threejs.org/ https://github.com/GooTechnologies/goojs https://whsjs.io/#/

Enter gltf https://github.com/KhronosGroup/glTF

Live stream: http://www3.nhk.or.jp/nhkworld/en/live/