Out at Shine's various client sites, our teams often meet to discuss the pros and cons of various technical solutions. And in the past, there was one particular Shine manager who, if he was in attendance, would regularly pipe up and ask the question: what's the problem we're actually trying to solve?
From time to time, developers will come to my desk seeking advice. There's a problem they're trying to solve, they've got a couple of possible solutions, but they're not sure which one to choose. I have a standard approach for dealing with this.
Server-side rendering a React app is a miracle on-par with childbirth and modern air travel.
OK, that opening sentence was a little over-the-top. I apologise to birth mothers and those in the aviation industry.
Let me start again: server-side rendering a React app is...kind of cool.
That said, it can be a little tricky to get started, especially if you're trying to do it with an existing app.
We'll build up a simple example to demonstrate. I'm going to assume you've got some knowledge of:
However, you are not required to have knowledge of:
Let's do this.
I just spent a couple of days at the YOW! Connected conference and had a great time, despite nursing a bit of a cold. There were a tonne of great talks at the conference covering a wide range of topics, but in this post I'm going to briefly reflect on one specific trend that interested me at the event: the way in which UI platforms are advancing to adopt modern languages, and are even influencing each other in the process. The end-result: they're all moving towards languages that are both functional and statically typed.
Full disclosure: This year I was a member of the programme committee for the conference. So in writing this post, there's a bit of a risk that I'm creating an echo chamber for myself. All I can really say in my defence is that I hadn't consciously made these connections in advance - it was only afterwards that I saw a trend!