"epoll: The API that powers the modern internet"
conditional git configuration
i use this to manage profiles between different different roles, each of of which has a different project directory
"Perhaps Emotional Dependence on Celebrities Has Gone Too Far" by Freddie_deBoer
"‘Magical’ Error Correction Scheme Proved Inherently Inefficient"
"Database-Instance using half of available CPU cores" dba StackExchange
Song: Frazey Ford - Done
the author argues that java tends to wait and see and then cherry pick the features that prove themselves valuable.
the upstart projects usually have less manpower to innovate much beyond their initial set of foundational ideas that made them take off. after a while, java tends to integrate the juiciest bits, diminishing the unique selling point of its competitors.
does the same apply to kotlin? has kotlin's downfall already begun? imo, no / not yet.
for one, there's been massive buy-in from google for the Android platform. this alone significantly changes the game.
and lastly, in my personal opinion, kotlin has a few killer features that aren't present in java and would be very hard to steal, as they'd fundamentally change java's characteristics and compatibility to earlier versions.
nullability handling; compared to kotlin's
Optional wrapper feels clunky and, more important, it's not enforced. if it's not enforced by
the type system, guarantees are weak and developer adoption is leaky.
everything is an expression: no idea whether java could implement this without breaking compatibility. this and implicit returns are an improvement on the scale of
anonymous objects vs.
scope function blocks: may be possible in java, but i see no attempts to emulate them.
also kotlin is similar enough to java to have a very low barrier to entry for new developers.
all in all, i see the authors point, but i don't think we've reached the point of kotlins decline for at least a few more years.