11–20 of 75 posts
We've already seen something similar before: when Apple "modernized" many of the their Cocoa Touch APIs to work better with Swift.
What does "already seeing this" have to do with any meaningful input on the subject?
Earlier quoted context omitted.
Discoverability via autocomplete is much higher in the second one. Extension methods probably seem really strange to anyone coming from a FP background (myself included), but in practice they've ended up being pretty useful when paired with Intellij.
Doesn't it get a bit overwhelming to get a huge list of choices with autocomplete? I've never done any serious work with Java or Kotlin, so I'm genuinely curious. As long as you have good docs, I find discoverability is rarely an issue. One of the first things I do when picking up a language is look through its built-in constructs, to familiarize myself with the available options.
I don't think it's the built-in constructs which are hard to find. In JVM-land, it's sifting through often verbose library interfaces that makes discoverability a huge win. Looking in Javadoc for that single function to convert from Type A to Type B properly can be a real pain.
Still working in Java on Android. Have a feeling that I will be left behind soon.
Same here. On my my most recent project the client requested we use Java, since after they take over they can use devs with Java knowledge.
We've already seen something similar before: when Apple "modernized" many of the their Cocoa Touch APIs to work better with Swift.
Earlier quoted context omitted.
What does "already seeing this" have to do with any meaningful input on the subject?
I was providing a parallel from my experience, which I thought might foster discussion on how such an API improvement might proceed based on historical anecdotes. Was this not a welcome addition?
Ugh, okay. It's going to be a blast refactoring all my existing code and custom tools to reference this new package.
We've already seen something similar before: when Apple "modernized" many of the their Cocoa Touch APIs to work better with Swift.
Can you elaborate on what we have seen? Modernization in quotes suggests that Apple wasn’t successful.
Earlier quoted context omitted.
I was providing a parallel from my experience, which I thought might foster discussion on how such an API improvement might proceed based on historical anecdotes. Was this not a welcome addition?
i think people are interested in the lessons learned in the past. are you sceptical or hopeful? how did apple's stab at this work out in the past? is it fundamentally flawed or deeply overdue.
Why is it that these large web companies can put out such sophisticated tools, and yet can't make a functional web page? Literally cannot see the content you are trying to show me. https://imgur.com/a/lXY8J And no, there's no scrolling or zooming allowed. Seriously, let's stop the focus on web framework du jour and actually make web sites that work, please.
Looks like it could be fixed by adding a CSS "white-space: pre-wrap" to the
elements they're using to display this code.
Still working in Java on Android. Have a feeling that I will be left behind soon.