3 ms·
What I appreciate about this update is how little code it breaks and how little future code is likely to be backwards incompatible. Or to put it another way, wh
by brudgers 7y ago
What I appreciate about this update is how little code it breaks and how little future code is likely to be backwards incompatible. Or to put it another way, what I appreciate is the sameness of the programming environment. To a first approximation nothing needs to be rewritten and newly written code will look just like existing code. What I appreciate is OTP is better and there's nothing programmers have to do (to a first approximation) to get that betterness. Instead, rolling out the betterness is a system administration task.
Basically, what is exciting is how well engineered it is.
- yellowapple 7y ago> What I appreciate about this update is how little code it breaks Other than a bunch of code reliant on the stuff removed from erl_interface, of course. No idea how big of an impact that has on real-world projects, though. The deprecation of erlang:get_stacktrace/0 also gave me a brief heart attack for one of my projects¹, but luckily I had the foresight to gate that to older OTP versions (and with newer versions the relevant code already removes dependence on that function), so I can rest at least a little bit easy. ---- ¹: https://github.com/otpcl/otpcl/blob/73167c58771f700963cbd9f70528456bf745ccbe/src/otpcl_repl.erl#L11 https://github.com/otpcl/otpcl/blob/73167c58771f700963cbd9f7...