hazza1

Looking forward to trying this now, Java is too engrained in the enterprise backend for me to use at work.

He's about the launch his TypeScript training course...

The rules state they don't apply on initial submission?

Potty training at 6 months sounds like the masochists approach. Why would you train before they can physically get on a potty? Yes, they pee all the time at 4 months, do they really gain much being held on a potty?

I don't want to plop a baby in front of TV but likewise I wouldn't want their early months to be all about the potty.

When they're ready, if they've had a rounded start to life it's a just another simple transition.

especially as the author works from home so I assume could choose to live anywhere?

Agreed, I just turned down an online coding interview as it required 3 hours dedicated time, especially for those of us with families 3 hours at home is precious and not usual uninterruptible. Companies who set tasks like this probably aren't the sort of company you want to work for.

Prior to having a family, I'd spend 12 hours on a test but claim it was only 6, now I'd be pushed to spend 3.

you don't really want the overhead of checking types on every call, you know where your applications entry points are - if you need checks add them.

Pretending you're based in Switzerland or some other tax haven to avoid local sales tax gives you a massive advantage over national companies.

You don't need to choose the library but there's still the same amount of documentation to wade through, the amount of learning is the same.

although, code separation is native in React now and if you think http clients is still a thing you're too far into the Angular ecosystem to be helped.

Only if you know typescript and rxjs already is Angular easier to get up and running, react especially with create-react-app is trivial to get going.

Especially as they'll make the code public if you don't pay, so even if you don't have it locally there seems a free way to get it back?

I think it was the fact that v3 to 4 was "basically a new project" with a new paradigm that earnt the reputation for breaking changes but then React Router is such a marketable name I can see why you'd be reluctant to spin off a new project.

Custom hooks encapsulate logic so you can no longer use it in all of your app

Hooks solve some problems nicely, the main killer for me is that they don't work with classes, so you end up with 2 wildly different paradigms in your codebase.

Feels like hooks should have been a clean start in a new framework rather than retrofitted into React.

https://www.quora.com/Has-TJ-Holowaychuk-been-as-prolific-in...

"my new goal is to live a better life. In the end open-source doesn’t pay the bills so it’s best to focus on other things if you can, or if you just enjoy the project then that’s cool."

where I can either get paid to take it or there’s a clear market for the skill

Maybe not Elm then

Taking a Ibuprofen slow release capsule before bed might be easier - it lasts for 12 hour

When in India I was buying a drink and asked the shopkeeper if he could throw away my old can, he literally threw it out the window.

According to the homepage you should install now and it's already used in production by major companies!

> they need to encourage users to build things

Is obvious from feedback on this article that this is alpha quality software. Feel free to be a guinea pig but I'd be very worried if I had any Elm code in production (unless you are no red ink and can hire the language author)

It's an alpha pre v1 language, it's going to break things to get better.

However they also need to encourage users to build things so they can observe patterns and improve the language - often by removing the functionality developers relied upon (in the maintainers opinion wrongly.)

These pre v1 developers are going to get angry and burnt, the main problem is that Elm is ambitious and reliant on just one guy. 18 months with few warnings on breaking changes gives developers a long time to become reliant on deprecated functionality.

I've done some Elm development, the lack of documentation and support unless you hang out on chat channels put me off. I might try again post v1 but that feels a very long way away.

I started this course but really struggled with their strong accents (although subtitles are available)

Guess I know how the rest of the world feels now watching American tutorials.

True, probably a lot of bias in my environment but I interview a lot of people for frontend roles - a couple of years ago Elm was the next exciting language to learn, it's now more often than not Reason.

I've found the opposite, all the momentum seems to be with Reason - I don't hear of many new people picking up Elm.

A release with smaller bundle is an amazing technical achievement but doesn't really address the underlying language and ecosystem issues.

The planned v2 of parcel will have a configuration file.

Why do some people only get their luggage down as they are leaving the plane causing a delay to those who stood early and are prepared to leave?

I don't really see how complex animations is something React (or any UI framework) should be responsible for ?

fetch and CSS handle AJAX and animation absolutely fine with native calls and work well with React, why would you bring in a library to handle these?

The jQuery api was hundreds of different methods, the best of which are now available natively in JavaScript.

React has a very small api, I hardly ever refer to the documentation (unlike when I was a jQuery or Angular developer)

I agree that people reach too early for helper libraries but you can go a long way in pure React.

React used to be so clean and readable - what happened?

It's great these abstractions exist but for me I want a framework where I don't need to think about them. Vue comes closest to the original feeling I got when starting out with React.

Using less memory than chrome is the very definition of faint praise.