ec changed the topic of #elliottcable to: a π―ππ ππ π―πππππππππ π―ππππππ slash sΝΜuΝΝpΝΝeΜΜΊrΜΌΜ¦iΜΌΜoΜΜ¬rΜΜ cΜΝα»₯Μ§ΝαΈ·Μ‘ΝΕ£ΝΜ || #ELLIOTTCABLE is not about ELLIOTTCABLE
<ec>
well that was several days' work, that nobody's going to read
<jfhbrook>
and yeah, that's a good point - idk if I'd expect them to solve the Greater Problem, using semver properly aside, but it's true that having to choose one of those strategies is less than ideal
<ec>
I have Opinions, but I tried to keep them out of the post
<ec>
basically, I think the existing concept of "ABI compatibility" β or at least the patterns surrounding it β are something we're gonna have to start giving up, moving forward, in the compile-to-higher-level-languages universe
<jfhbrook>
I think you're correct
<ec>
i.e. frankly, every-small-team-compiler-ever being able to be like "smeh we're gonna break ABI compatibility" just β¦ isn't going to work, in the JavaScript world.
<jfhbrook>
I mean, at one job we shipped version 32 of an API within a year - "we get it bro, you semver"
<ec>
but that's an argument for another time, ugh, I just want to make sure that somebody other than me in the community is *aware* of these issues. so few people building libraries β¦
<ec>
mostly for reasons exactly like these lololol