CSS-in-JS solves a lot of problems that people that have been writing 'real CSS' have been experiencing for a long time. Writing CSS for very large applications that deal with lots of shared components across engineering teams is a hard task. Some of those problems are alleviated by libraries like styled-components.

It's not for every use case and should only be used when there is a genuine need (rather than 'because it's shiny.') But shrugging off CSS-in-JS because you don't understand it is a bit silly.

Took it to an Apple store and was quoted £700 to fix it which is equivalent to almost half the cost of the laptop. For a single key. Absolute insanity.

What unreleased APIs are you needing to warrant this? We've used any a couple times, but usually just as a placeholder until the data model is locked down.

>- Development time is slower than writing in regular JS/React. This started to become a major issue due to the nature of our project being a prototype (fast iterations on ideas and features).

Again, I can't say I've had this experience. Development time is _initially_ a tiny bit slower, but once you've setup types, the time saved from fixing type related issues adds up very very fast. Also, autocomplete / autoimporting has actually sped up my development time hugely. Not having to worry about figuring out relative paths or imports and just being able to type a component to import it is magic.

>- Lots of frustration when a package doesn't have types (although most major ones do have them).

This is true, but I've found that 95% of the packages we use do have types. The few that don't, tend to be very small indie packages that don't do a lot, so the lack of types isn't a huge issue.

Is this one of those instances where the word 'quantum' is used to hand-wave away weird ideas?

I did. Apple Music still has one major selling point: They own iTunes so anything on iTunes is on AM. For spotify and other streaming services you still have to wait a couple hours to a few days for something to appear on the other streaming services

That being said I moved back to Spotify after a year because of how awful and buggy the UI in AM is. If Apple Music could improve the UI and fix the bugs that have been about for years they could really do well. But I have my doubts as to whether that will ever happen

Well for one the passport as a whole can then be used to commit identity fraud or cloned on the black market.

1) Storing passwords in plain text: Although the post is now down, it pointed to the fact that Nic.IO will email you your password in plain text. Something which everyone that's spent more than a few weeks coding should know not to do.

2) Another pretty major outage back in 2013 that rendered two of my sites offline.

I personally stopped using them after my last IO domain lapsed but this should serve as a stark warning to anyone thinking they can pick up a cute IO domain