Angular v8.0

Post by lostjohnny » Thu, May 30, 2019, 9:59 AM UTC

kaoD wrote: post #70

royjacobs wrote: post #67

Earlier quoted context omitted.

Since JS is the only thing you can actually use[1] in a browser you can argue that anything that runs in the browser is syntactic sugar (and in fact, Typescript is syntactic sugar). A less flippant analogy might be macro support in Rust. It's clearly part of Rust, but the syntax is completely different and it requires IDEs to have completely separate processing just to handle it. I wouldn't consider that to be mere s…

JS and JSX are isomorphic (in the mathematical sense) hence why JSX is considered just syntactic sugar. JS and TS aren't isomorphic (there's no inverse morphism once you go TS->JS that can bring the resulting JS back to the original TS) hence why TS is a different language (even if a superset of and compiled to JS).

    "{{title}} spends {{calc}}"

    `${title} spends ${calc}`

    "{{title}} spends {{calc}}"

Post by antonkm » Thu, May 30, 2019, 10:52 AM UTC

marfusios wrote: post #175

antonkm wrote: post #172

Earlier quoted context omitted.

I disagree. If you use create-react-app you get best practices out of the box. React is also much less abstraction away from vanilla JS. Learning Angular is learning a new language with a whole bunch of restrictions. Learning React is like learning JS++. (This is my personal experience based on three Angular projects and ten+ React projects.)

Yea? What about routing, forms, state, styles encapsulation, code separation to modules, http clients, etc. A lot of choices for new React project, zero choices for Angular === faster startup.

Post by allover » Thu, May 30, 2019, 12:15 PM UTC

azimuth11 wrote: post #140

allover wrote: post #89

Earlier quoted context omitted.

> and I still have no idea how I only do stuff on the client in a SSR environment (stuff that i did in componentDidMount) The 'useEffect' hook - it won't be executed if you use e.g. ReactDOMServer.renderToString() for SSR useEffect(() => { console.log('Client side only'); }, []); Codesandbox: https://codesandbox.io/s/peaceful-dew-nvw83

While you wouldn't want to leave "console.log" in your code in production, you can use them in function components just like a classes' render methods. A better example (from the video "React Today and Tomorrow and 90% Cleaner React With Hooks" from October[1]) is something along the lines of updating document.title = `${some} Page` or possibly calling an API. [1]: https://www.youtube.com/watch?v=dpw9EHDh2bM

Post by nicoburns » Fri, May 31, 2019, 10:33 AM UTC

jamesgeck0 wrote: post #169

nicoburns wrote: post #164

Earlier quoted context omitted.

This is precisely what I don't like about Angular. That there is all this stuff . And I have to care about what it is doing under the hood (and this is complicated and not especially well documented). In React if I have performance issues, then it's pretty easy to work out what's causing them.

You can largely ignore what Angular is doing under the hood, tbh. If you're having performance issues, the answer is often related to change detection (aka, Zone.js).

Post by davedx » Tue, Jun 04, 2019, 7:18 AM UTC

rufugee wrote: post #127

davedx wrote: post #78

Earlier quoted context omitted.

As a long time React developer, I second this. Especially this part: > There's no need to evaluate different routers, form libraries These two things have been the bane of my React development experience ever since the days of "flux". Every new React project I start I end up using a different set of libraries, and it's not just me either -- a very experienced React dev I work with just switched our React e-commerce S…

If you were new to React or Angular, but needing to choose one for a single developer project, which would it be now in 2019?