You got hit at 80kmph? Not sure that the carbon fibre can be blamed for breaking in those circumstances!

Idiomatic React is different (it now uses hooks and functional components), but the old style of class based components with methods still works, and can be mixed and matched with the newer style so gradual migration is possible. There have been some deprecations over 10 years, but there are automated code migration tools for those.

Do you have a problem with SMS spam? I can't remember the last time I got a spam SMS message, and I had my phone number on public on my personal website for a number of years.

Perhaps SMS spam is a US thing?

You could consider looking for a job at a software development "agency" that specialises in those technologies. There should still be plenty of such jobs for an experienced developer (especially if you're willing to accept a lower-then-"big tech"-but-still-good salary).

They'll not only provide you with a regular income (no need to find your own clients), but will likely provide you with a work computer and an office space too.

None of those skills are really out of date. Laravel is also still huge. And almost everyone is still using SQL.

And just because these are areas in which there are many juniors devs have doesn't mean that senior devs are competing directly with them.

You're a lot more limited more limited to the kinds of APIs you can safely encapsulate in C. For example, you can't safely encapsulate an interface that shares memory between the library and the caller in C. So you're forced into either:

- Exposing an unsafe API and relying on the caller to manually uphold invariants

- Doing things like defensive copying at a performance cost

In many cases Rust gives you the best of both worlds: sharing memory liberally while still having the compiler enforce correctness.

Rust is better at this yes, but the practical advantage is not necessarily that huge.

I should hope not. Even if your body could withstand the low pressure, you'd suffocate very quickly.

> it's still easier to write a pile of C code and get it to compile than it is to write a pile of Rust code and get it to compile.

As someone who is more familiar with Rust than C: only if you grok the C build system(s). For me, getting C to build at all (esp. if I want to split it up into multiple files or use any kind of external library) is much more difficult than doing the same in Rust.

For some controls (I have in mind <select> and date pickers) there is also a lot of functionality missing from the built-in ones.

Totally. It is like the browser venders just kinda stopped iterating on them. When the reality is people just want the controls and the ability to skin them. Also with all of the events that all of the newer controls have.