4 ms·

I think people will get excited about this and then quickly realize how painful it is to code in a foreign environment from the platform. How miserable it woul

I think people will get excited about this and then quickly realize how painful it is to code in a foreign environment from the platform. How miserable it would be trying to write Java or kotlin targeting iOS apps. I think this will be the same. Just use the native tools and languages for the platform. Swift/Objc/xcode for iOS. Java/Kotlin/Android Studio for Android. You will be so much happier.

AnthonyMouse 1y ago
This depends entirely on how well the thing you're using bothered to support multiple platforms. Browsers are pretty much the gold standard here, ironically. You might have to care if it's Firefox or Chrome but it's very rare for you to have to care if it's Firefox on Windows or Mac or Linux. It's exactly why React is simultaneously horrible and everywhere. So it can be done, it's just a question of whether that framework has done it well, ideally while also doing other things well (unlike React).
oblio 1y ago
> How miserable it would be trying to write Java or kotlin targeting iOS apps. I think this will be the same. What happens in the Java/Kotlin case?
morshu9001 1y ago
idk about Android, but native iPhone dev is pure torture. Hence React Native.
- tcoff91 1y ago
  Android is way worse. iOS has way better APIs. Android studio is way better than XCode though
  - cosmic_cheese 1y ago
    Agreed on SDKs/APIs. Compose improved the Android situation but it’s still a mess compared to UIKit. I’m more mixed on Android Studio. It’s fine I guess, but I wish its UI were more deeply customizable. Many of its design decisions irritate me.
    - tcoff91 1y ago
      Xcode is dogshit though… I’m mostly in Neovim writing typescript (react native) luckily.
      - cosmic_cheese 1y ago
        I've not had much trouble with Xcode in the past 15+ years I've been using it. Its biggest warts involve Interface Builder, which is easily avoidable by using code for UI instead of XIBs or storyboards. With Android Studio, I'd say the ways that it being an IntelliJ IDE puts it above Xcode are cancelled out by other aspects of Android development, which can be abysmal. Swift Package Manager and Clang/llvm code stripping have never made me want to tear my hair out the way that Gradle and Proguard have for example.
        tcoff91 1y ago
        Gradle is the single most confusing build system tool of all time. It’s so bad. I agree that other than JetBrains everything else about it sucks ass.
        morshu9001 1y ago
        I've never seen a build system that makes sense, aside from make which is more for individual binaries. If the higher layer build system were just some Python scripts I can look at and understand, that'd be neat.
        morshu9001 1y ago
        Xcode with Swift v1-3 was broken. Compiler was insanely slow and would segfault from bugs in the type system.

AnthonyMouse 1y ago

This depends entirely on how well the thing you're using bothered to support multiple platforms. Browsers are pretty much the gold standard here, ironically. You might have to care if it's Firefox or Chrome but it's very rare for you to have to care if it's Firefox on Windows or Mac or Linux. It's exactly why React is simultaneously horrible and everywhere. So it can be done, it's just a question of whether that framework has done it well, ideally while also doing other things well (unlike React).

oblio 1y ago

> How miserable it would be trying to write Java or kotlin targeting iOS apps. I think this will be the same. What happens in the Java/Kotlin case?

morshu9001 1y ago

idk about Android, but native iPhone dev is pure torture. Hence React Native.

tcoff91 1y ago
Android is way worse. iOS has way better APIs. Android studio is way better than XCode though
- cosmic_cheese 1y ago
  Agreed on SDKs/APIs. Compose improved the Android situation but it’s still a mess compared to UIKit. I’m more mixed on Android Studio. It’s fine I guess, but I wish its UI were more deeply customizable. Many of its design decisions irritate me.
  - tcoff91 1y ago
    Xcode is dogshit though… I’m mostly in Neovim writing typescript (react native) luckily.
    - cosmic_cheese 1y ago
      I've not had much trouble with Xcode in the past 15+ years I've been using it. Its biggest warts involve Interface Builder, which is easily avoidable by using code for UI instead of XIBs or storyboards. With Android Studio, I'd say the ways that it being an IntelliJ IDE puts it above Xcode are cancelled out by other aspects of Android development, which can be abysmal. Swift Package Manager and Clang/llvm code stripping have never made me want to tear my hair out the way that Gradle and Proguard have for example.
      - tcoff91 1y ago
        Gradle is the single most confusing build system tool of all time. It’s so bad. I agree that other than JetBrains everything else about it sucks ass.
        morshu9001 1y ago
        I've never seen a build system that makes sense, aside from make which is more for individual binaries. If the higher layer build system were just some Python scripts I can look at and understand, that'd be neat.
      - morshu9001 1y ago
        Xcode with Swift v1-3 was broken. Compiler was insanely slow and would segfault from bugs in the type system.