GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    phiofx (phiofx@hachyderm.io)'s status on Monday, 15-Jan-2024 16:36:15 JST phiofx phiofx

    For several years it seemed like deficiencies of older ecosystems will usher new takes: #rust fixing #cpp, #kotlin fixing #java, #julia fixing #python, #wasm fixing #javascript etc.

    But it no longer feels so. Maybe it was a case of "you have to move fast to fix things" and as incumbents raise their game the window of opportunity closes. The vast investment in established stacks incentivises patching the most egregious weaknesses.

    One exception seems #golang, which found a network niche

    In conversation Monday, 15-Jan-2024 16:36:15 JST from hachyderm.io permalink
    • Embed this notice
      tamas 🦀 (tamas@hachyderm.io)'s status on Monday, 15-Jan-2024 16:55:18 JST tamas 🦀 tamas 🦀
      in reply to

      @phiofx I think it’s a matter of perspective and not a once in our life event. You describe the creation of very new technologies (Rust is only 8 years old, wasm 6, kotlin and julia 12). C++ first appeared 39 years ago. As new tech matures there will be new challengers.

      In conversation Monday, 15-Jan-2024 16:55:18 JST permalink
    • Embed this notice
      phiofx (phiofx@hachyderm.io)'s status on Monday, 15-Jan-2024 17:03:56 JST phiofx phiofx
      in reply to
      • tamas 🦀

      @tamas oh for sure. its only a gut feeling anyway. but the pattern I sort for see is that 3-4 years ago the newcomers had an easier time because the incumbents were more stagnant. For example the complain that python is not fast enough prompted several iterations and more are coming.

      In conversation Monday, 15-Jan-2024 17:03:56 JST permalink
    • Embed this notice
      phiofx (phiofx@hachyderm.io)'s status on Monday, 15-Jan-2024 17:35:32 JST phiofx phiofx
      in reply to
      • MobileOak

      @MobileOak but as far as I know kotlin has not made any meaningful dent outside the android domain (the vast corporate space that determines the future of java). So its fate is highly linked to the whims of Google and even they hedge their bets with dart/flutter

      In conversation Monday, 15-Jan-2024 17:35:32 JST permalink
    • Embed this notice
      MobileOak (mobileoak@fosstodon.org)'s status on Monday, 15-Jan-2024 17:35:33 JST MobileOak MobileOak
      in reply to

      @phiofx on Android, Kotlin is the standard now. You can't get a job if you only know Java.

      In conversation Monday, 15-Jan-2024 17:35:33 JST permalink
    • Embed this notice
      phiofx (phiofx@hachyderm.io)'s status on Monday, 15-Jan-2024 17:41:02 JST phiofx phiofx
      in reply to
      • Kai Klostermann

      @OddDev ha ha, fair enough, but thats as anecdotal as my hunch

      I don't mean that none of the new proposals will make it into say "top 5" universal language, its just that there is a pattern that it may take longer (if ever) than what the sentiment was few years ago

      In the rust vs cpp space the latter is definitely trying to get its act together, whether people will again build greenfield projects remains to be seen

      In conversation Monday, 15-Jan-2024 17:41:02 JST permalink
    • Embed this notice
      Kai Klostermann (odddev@floss.social)'s status on Monday, 15-Jan-2024 17:41:04 JST Kai Klostermann Kai Klostermann
      in reply to

      @phiofx What? Rust is all over the place lol.

      In conversation Monday, 15-Jan-2024 17:41:04 JST permalink
    • Embed this notice
      phiofx (phiofx@hachyderm.io)'s status on Monday, 15-Jan-2024 17:49:57 JST phiofx phiofx
      in reply to
      • danjac

      @danjac yes, the vast prior art of older languages is both a curse and a blessing.

      discussing the real advantages of new takes is subtle enough, but weighing these against the benefit of reusing existing know-how for both current and future projects is very tricky. in applied maths this is the problem of subtracting two large numbers (catastrophic cancellation): your result is unstable, very sensitive to assumptions

      https://en.wikipedia.org/wiki/Catastrophic_cancellation

      In conversation Monday, 15-Jan-2024 17:49:57 JST permalink

      Attachments

      1. No result found on File_thumbnail lookup.
        Catastrophic cancellation
        In numerical analysis, catastrophic cancellation is the phenomenon that subtracting good approximations to two nearby numbers may yield a very bad approximation to the difference of the original numbers. For example, if there are two studs, one L 1 = 253.5 cm {\displaystyle L_{1}=253.5\,{\text{cm}}} long and the other ...
    • Embed this notice
      danjac (danjac@masto.ai)'s status on Monday, 15-Jan-2024 17:49:58 JST danjac danjac
      in reply to

      @phiofx I think there is also improvements in the original languages. For example Typescript or typed Python.

      Rewriting from scratch even in a "better" language is expensive and fraught with problems - you risk reintroducing bugs without perfect understanding not only of the original code, but the original context. But gradual improvement over time is better.

      Question is whether new ecosystems are adopted for new projects. Maybe that is more an economics question.

      In conversation Monday, 15-Jan-2024 17:49:58 JST permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.