Really interested to give this a try. I haven't used RWX for CI yet (overall my builds wouldn't have benefited enough from the caching), but docker build times are definitely a pebble in my shoe
The metric used here is an incorrect metric of social mobility. It compares father-son income correlation (which depends mostly on inheritance taxation and many other factors), while a better idea would be to compare the percentage of high achievers who started from humble beginnings.
Indeed, US education system is somewhat strange, to say the least. However, all these metrics are almost designed to present the US in bad light.
How about "the percentage of millionaires who were born in a poor family"? I bet this is where US shines. Rich people in most other countries are mostly from old money.
> You can't possibly know instantly all the exceptions to handle for a function (given it calls other functions w/ exceptions), whereas, if it returns a fixed bunch of error codes, then you can know why that specific function failed and handle appropriately.
presume that, despite not being able to know all exceptions to handle in advance, you somehow have knowledge of all error conditions in the event that you're using error codes?
> presume that, despite not being able to know all exceptions to handle in advance, you somehow have knowledge of all error conditions in the event that you're using error codes?
I guess that it is indeed the case. If you call one function, you can read the documentation of said function and read about its return values, including error codes. This specification cannot not change if one of the libraries nested deep within this function is replaced. However, with exceptions, if you use a new implementation of a deeply nested function it may raise a new exception that nobody was aware of at the time of writing the outermost functions.
Usually documentation tends to have this, or you can look at the function and immediately know what it will return, whereas with exceptions any passthrough errors are transparent.
I don't know that the Macromedia deal was all that bad.
While there are few, if any, surviving remnants of Macromedia software within Adobe, the acquisition of Macromedia both eliminated its most serious competitor and provided an influx of engineering talent.
Using stock price as a surrogate for overall performance, they went from ~$35 at the time of the acquisition to ~$155 today, with annual net income rising from $600M to $1.6B today.
