Interpreted code is great if you can babysit all the deployments. Generally, when you have to actually ship software, the sooner you find the bugs, the better. It doesn't get any earlier than compile time.
I have made brief forays into interpreted languages, and always feel immense pain and frustration from the lack of a compiler.
It's still worthwhile if you aren't upgrading the OS. Replacing MOBO + CPU + RAM is still cheaper than replacing a whole machine. Keeping the case, power supply, drives, keyboard, mouse, monitor, etc. etc.
Motherboards have gotten so all-inclusive lately, and USB so ubiquitous, that expandability is generally moot. Unless you're gaming, of course.
I use 1/1/1970 often, because it's ZERO in UTC.
Shocked no one has "gotten that" yet, even here.
How can you *stand* smooth scrolling? It's so slow!
It's one of the first things I turn off, in any app.
No schedule, feature based or time based, will have all upstream developers in sync. Someone will always be developing new stuff and want to squeeze it in.
At least this way, there's a known target that developers can be (made) aware of.
Maybe they work like treads on car tires... let there be someplace for liquids to move *away* from to improve grip. Or, maybe having "with oil" and "without oil" surfaces that can be selected by varying grip allows gripping different types of surfaces.
Also, grip isn't the only thing hands do. Wiping or scrubbing with your fingers requires some level of abrasiveness.
I suspect that there may be a connection between building calluses and having prints. Possibly, prints are just the way we make "tough" skin that is more resistant to injury.
Who wants a video? I don't have time to watch a video. Give me text I can skim.
One way to make your old car run better is to look up the price of a new model.
