robovm VS 4.2BSD

Naturally depends on the use case, yet they work good enough to be in business for 20 years.

https://www.ptc.com/en/products/developer-tools/perc

https://www.aicas.com/wp/products-services/jamaicavm-tools/

https://www.codenameone.com/

Android 5 & 6 (only changed back into JIT/AOT due to long compile times), https://www.infoq.com/news/2014/07/art-runtime/

Unfortunely the best well known, Excelsior JET, is no longer in business, most likely due to GraalVM and OpenJ9 being available as free beer, while PTC, Aicas Codename One are safe in their domains.

There is also RoboVM (https://github.com/MobiVM/robovm) as free beer, however it actually started as a commercial product, and the acquisition from Xamarin kind of stagnated it (naturally).

I think libGDX still uses RoboVM, but I’m not sure if it’s being actively developed anymore.

For iOS the RoboVM project intends to be an AOT compiler for Java bytecode.

Kotlin is not ideal for iOS development afaik (maybe with RoboVM). With regards to Android development, it is perfect. For desktop applications it's good, there are always tradeoffs here. With regards to payment, I believe it is generally the case that you're paid more the harder the language is to learn (so C > C# > Python). This also affects how much people are looking for a certain kind of developer - there are more JS jobs than jobs requiring a C++ developer. Kotlin is a good choice to start though. It's not too complicated, it's not so simple that it's limiting you somehow, it's not too slow for most applications (+ it supports native somewhat) and it has a good environment with stable libraries you can rely on.

Yes, these are the native code compilers for Java, able to target Apple mobile platforms.

https://www.codenameone.com/

https://gluonhq.com/products/mobile/

https://github.com/MobiVM/robovm

Not only early Unix; look at the original inet_addr implementation [0]. It accepts not only "0x" but also just "x" as the 16-base prefix, it doesn't really care about the numbers overflowing, and it parses 09 as equal to 011 (which is decimal 9). And the less said about the coding style, the better.

[0] https://github.com/dank101/4.2BSD/blob/master/lib/libc/inet/...

No need to guess. My man page for inet_aton says it comes from 4.3BSD: https://github.com/dank101/4.3BSD-Reno/blob/master/lib/libc/...

The earlier inet_addr from 4.2BSD has the same logic: https://github.com/dank101/4.2BSD/blob/master/lib/libc/inet/...

inet_aton and inet_addr parses addresses the obvious way. Using something like strtoul or especially sscanf would be stilted. The beauty of C pointers is that it makes simple parsing tasks very easy--perhaps too easy.

It probably made sense in 1983.

https://github.com/dank101/4.2BSD/blob/master/include/netdb....