3 ms·

Sounds like they were using elixir like Java or go. I’ve never even used exceptions

• georgia_peach 4y ago
  Java and Go never did this to me on a point release: warning: System.cwd/0 is deprecated. Use File.cwd/0 instead warning: String.strip/1 is deprecated. Use String.trim/1 instead warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead I'm sure that underscore was just killing them.
  • mstipetic 4y ago
    It didn’t break, it gives a timely deprecation warning, you can probably fix it in an hour or two with basic grep, where is the problem?
    • georgia_peach 4y ago
      Problem being that this happened on every point release. It would be a non-issue if it only happened before a major release. Spending "an hour or two" to update source and dependencies every time the runtime is upgraded is an expense I have only encountered in elixir. It didn't help that, circa 2018, many of the dependencies had been abandoned by their original developers, so even more work for us...
  • smackeyacky 4y ago
    Android development is kinda this stupid too, just for the record. I mean, they slowed down the breaking function names but quadrupled down on syntax warnings where handler style got deprecated and whatnot. Super annoying to do a simple upgrade only to see a sea of yellow warnings in Android Studio. .NET is no better.
    • georgia_peach 4y ago
      Can't speak to .NET, but even the worst server-side languages feel like a reprieve compared to the hellscape of native mobile development.