darth_mastah

Thanks for sharing. Really good and honest write-up. Everyone needs to put bread on the table. It's much more rewarding investing your time in your own project than selling your time to some corporation. At least you actually have something to show for it. Respect. And if people found your project useful - you succeeded. The mere fact that the apps were making money shows that those apps were used by some other people who found them worth using.

+1

W3schools is contributing to poor education amongst junior web developers.

Absolutely. I second that. I would be willing to spend a couple of hours on an interview task, which could give the interviewer an idea about my skills, but more than that I would see as an overkill. Besides, in my view, showing some OS repos on GitHub can be a good alternative.

I hate to say that, but I just seem to have broken it. Here's how: I put 0.1 in A1, 0.2 in A2 and =A1+A2 in B1. Now B1 displays "=A1+A2" instead of the result.

From web dev perspective Safari is becoming new IE6. CSS3 written to spec, working fine on anything else including IE11 tends to fail on Safari. I'm sure I will get a lot of hate from Apple fun boys and girls, but that has been my and my colleagues' experience recently.

Really good article, somehow missed by HN audience.

No matter what framework or library you choose, if you go past the to-do list project you will encounter certain pain points. I worked with jQuery when it was the new kid on the block, with Angular since it first came out and now with React. Every one of them gives you grief now and again. However if you develop pragmatically you learn how to avoid those pain points early on in the process even if it means investing some time. It will pay off later on. And if there is absolutely no way to mitigate the pain - just move on to another library.

It makes me sad to see people ranting about how much typing there is in Redux or Typescript or how much boilerplate and so forth. To me this behaviour screams immaturity, because I don't know how else to explain spending energy on wining instead of finding a solution. Especially, that you don't need to look far - take redux-actions for example. Nice and simple, makes all the heavy lifting for you. If that's not cool in your view how about you actually contribute and write something of your own, rather than moan?

I found it really enjoyable and rather funny. I really liked the attention to detail as well, e.g. replicating last 5 searches in order to stay stealthy. I imagine that lots of effort went into the hacking exercise and the write-up. Nicely done.

The skill tree is absolutely great.

I get 404 on this link.

I hear you. I moved to the UK ten years ago, because I fell in love with this beautiful, mature, tolerant country. It hurts to see what the populists are trying to do. It's neither good for the people of Britain, the economy, nor the rest of Europe. Shame on you, Theresa May. Shame on you. I say it while I still can.

> Others may choose to use a bundler to concatenate all of the JavaScript files into one or two packages, and load them asynchronously to avoid these problems, typically leading to a SEO-unfriendly Single-Page Application primed for Front-end SPOF.

Shortsighted as I am, I struggle to see how fetch-inject guards against SPOF?

Having said that, I can see how this library could be useful for projects with no bundler.

Interesting. I didn't know that one. I use HN firebase API to feed an Elasticsearch cluster.

Thanks and nice work! Are you using Algolia API?

Didn't quite get what you mean about PR folks at Uber, but thank you for appreciating the eternal joke :)

I was talking about React ecosystem, rather than the library itself. The latter is solid, the former though... not so much.

> Now either the answer key is regularly wrong, or I just don’t know what street signs and mountains are.

Clearly, the author is a bot.

> you shouldn't be using Redux until you need it

In my experience whenever you start dealing with state you need it. Which is in fact quite early in the project.

+1

> Don’t use Redux if you don’t need it, as it is intentionally verbose.

Yeah... People say that, but is it true? Lifting the state gets very messy very quickly and you end up with a spaghetti code before you know it, with the separation of concerns dying short yet painful death. For that reason I use Redux even in small projects, guarding myself against unnecessary verbosity with redux-actions. It's really that simple. I understand the need to prove that React can stand on its own without Redux, but the truth is, without Redux it's limping.

Way to go.

Why limit yourself? Draw the line between you and not-you. Such fun.

I may be wrong, but I use webpack to remove exactly the the pain point of running jsx from the command line, concatenating files and minifying them. It does good job there and saves me time.

I don't see what's wrong with redux for medium/small apps?

Yeah, it gets annoying really quickly. You go three components deep and you're ready for redux.

I agree. React is a great rendering library which somehow became the core of a mix and match framework, plagued by backwards incompatibility and maintained by plethora of individuals. As a result upgrading dependencies is never safe and and each of tens of them is quite likely to introduce breaking changes or become obsolete, leaving you having to make unnecessary changes in your app.

Don't get me wrong, I think React is good at what it does, which is rendering. I just don't think the maintenance of a react app, which includes dependency management, is worth the benefits. Similarly the current model of reinventing everything in the "react way" is hardly speeding up development.

Horrifying. Watching videos like that makes you think: "is it safe to go to the U.S. for holidays"?

I've been doing it for two years. It's good.

Very good work, the Grid Garden.

As a side note, I find the grid API confusing as well.

Respect. https://frontendmasters.com/ should give you a good start. There's a fee but well worth it. I would recommend Douglas Crockford and Kyle Simpson for a start.