Now function colouring is interesting but not for the reason these articles get excited. Recolouring is easy and has basically no impact on code maintenance. BUT if you need that code path to really fly then marking it as async is a killer, as all those tiny little promises add tiny delays in the form of many tasks. Which add up to performance problems on hot code paths. This is particularly frustrating if functions are sometimes async, like lazy loaders or similar cache things. To get around this you can either use callbacks instead or use selective promise chaining to only use promises when you get a promise. Both strategies can be messy and trip up people who don’t understand these careful design decisions.

One other fun thing is indexeddb plays terribly with promises, as it uses a “transactions close at end of task” mechanism, making certain common patterns impossible with promises due to how they behave with the task system. Although some API designers have come up with ways around this to give you promise interfaces for databases. Normally by using callbacks internally and only doing one operation per transaction.

District based heating is generally much more efficient than per building heating, and this side steps many of the issues that you would have installing/maintaining servers on your property.

Honestly my only concern is the impact of having a data centre nearby. They are asking for people to put a deposit down for the heating. I won’t encourage it, but I will make use of it if they put it in!

I hate this philosophy. But it’s seems to be the preferred path for Microsoft.

But instead we’ve found a way to circumvent the process. Losing the understanding of your own problem and the new ideas that come off the back of it.

I’m reminded of the story that NASA had a research project to make pens that would work in space, and Roscosmos just used pencils. I always thought NASA came off worse in that anecdote, but I wonder what they learnt while making the pen…

Then of course we produced it at industrial scale for decades flooding the entire planet with this stuff.

- Put your child on the potty during changes, and first thing in the morning. Build’s association and encourages bladder control. Do this long before trying to get them out of nappies.

- Reusable wipes are also a massive win. We have face wipes and bum wipes, basically just soft cotton. Bit of water under a tap and your good.

- Our biggest hurdle for moving away from nappies was nursery, as they wouldn’t consistently put a younger toddler on a potty.

- Introducing a potty earlier means less poopy nappies, turns out even a toddler dislikes pooping their pants.

- Expect a stupid amount of laundry, and the nappies to leak a bit ( so more laundry ). You also can’t use a drier with them as it damages the water proofing layer.

- Travelling is harder… Used nappies should be cleaned within 3 days, so expect to take dirty nappies away with you for washing plus clean nappies/boosters/cloths/bags.

- It’s easy to buy new/almost new/good condition second hand. Either people want to do it but don’t get on with it, or never start, or potty trained. Means a significant reduction in cost. But expect ones that have been used less to be more water proof and Velcro to work better etc.

- Our daughter loved playing with the clean ones, putting them on toys, using cloths etc. Probably helps they have cool designs on the outside. I expect a disposable wouldn’t work well after it had been played with.

- If you need to use disposables while you’re away etc the chemicals can cause rashes after your child has adjusted to their absence.

- When they start weaning you have to “remove the solids” before washing. Yes this is unpleasant, but more often than not is just upending it over toilet. You get used to it. Same as nappy changes in general and washing nappies.

- When we did swap to pants we didn’t do anything special. Just stop nappies, ensure you have a potty nearby, and deal with it for a few days. It’s uncomfortable for them and they learn fast. Expect a bit of frustration and wanting the old routine back.

I dislike the “you can change the syntax” argument because that just doesn’t happen. Closest thing is a new language that compiles to another.

That being said while I don’t struggle much with the glare from oncoming headlights I find that visibility beyond the oncoming vehicle can be severely limited by the bright light. This often causes me to slow down and squint to be careful of any dangers beyond the vehicle.

Despite all this I think it’s still a move in the right direction.

The only “big” local first app I’m aware of is Linear.

So yeah entirely unsurprised that people aren’t engaging with science on X

It scales pretty well from that, allowing you to build logic trees in a scratch like environment or go full code with JS.

Trial version is free, and browser based so no install. Loads of examples and demos in the editor to try as well.