• 5 Posts
  • 977 Comments
Joined 3 years ago
cake
Cake day: August 2nd, 2023

help-circle





  • That’s a very open-ended question. You may want to narrow it down a bit, unless you’re truly just looking for anything.

    Some helpful information would be your experience level (are you only looking to learn or is your goal to create something), what languages and frameworks you know, if you’re looking to join an existing project or lead your own, what type of collaboration (collaboration could mean anything from working on the same git repo to remote pair programming), what you look to get out of it, how much time you’re willing to invest, and other things in a similar vein.







  • Quetzalcutlass@lemmy.worldtoScience Memes@mander.xyzRadioactive Steel
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    13 days ago

    There are examples of lost metals in real life. Damascus/wootz steel (the actual historical metal, not the pattern welding technique often marketed as Damascus steel) was produced for multiple millennia and was prized for its ability to hold a sharp edge and resist shattering, before the technique to make it was lost in the early 1900s.

    Modern material analysis has identified some of how and why it was so resilient and metallurgists have come up with reproductions that achieve most of its qualities, but the exact technique and circumstances behind it remain lost to time even though it only stopped being produced a mere century ago.







  • My main concern with using something like this in a business is whether it will still be maintained a decade or two from now. Kotlin has the support of several major players in the Java ecosystem and is virtually guaranteed to stick around. If JADEx is abandoned, it becomes an additional maintenance burden on the team.

    (Though point in your favor, they can maintain it since it’s open-source. Greybeards have nightmares about updating critical projects reliant on old, long-abandoned C/C++ dependencies.)

    Unlike a Kotlin migration, there’s no new language for the whole team to learn, no need to flip the entire codebase at once.

    Kotlin is designed for trivial bidirectional Java interop. Mixed-language projects are explicitly supported as a basic feature, so you don’t have to convert the entire codebase at once. You can go through file-by-file, rewriting a single class in Kotlin at a time, same as in JADEx.

    I’ll admit null safety in a mixed codebase can be a pain* - though I’m guessing JADEx doesn’t escape that pain point either. Edit: the same issues Kotlin has are mentioned in the article, though both languages provide tools to find and fix them.

    * Also needing to spam @JvmName and @JvmStatic everywhere to make everything compile into the proper Java equivalent. Moving statics to an auto-generated ClassNameKt.class by default and the whole companion object model are the two things I hate most about Kotlin.