4 ms·

The app store page doesn't mention debugging, so I assume it's not there. And probably not "go to definition". Completion quality is also questionable. These a

by pquki4 2y ago

The app store page doesn't mention debugging, so I assume it's not there. And probably not "go to definition". Completion quality is also questionable. These are very hard problems, even for a language with strict typing like Java. It's not easy to get these basic lookups correct and smooth. Personally I wouldn't call it an IDE (yet).

pandemic_region 2y ago
>It's not easy to get these basic lookups correct and smooth. Exactly, Intellij has been in the autocompletion industry for what, almost 2 decades? And still they present me with types in the autocomplete drop-down that I have never ever used in any of my projects. Yes I know, but I got tired eventually from excluding them. In my brain autocomplete is not hard, yet for an IDE guessing seems really really hard. AI improved this, at the cost of a second latency. No thankee sir.
- qwerty456127 2y ago
  Yet IntelliJ has always (figuratively, I dunno about its first years) been famous for having by far the best auto-completion ever. People used to become very upset when they were forced to use Eclipse after experience with IntelliJ.
  - pandemic_region 2y ago
    True, it was good and lightning fast back then. Granted, the language (java) was arguably simpler then. Autocompleting a lambda is nightmarish at the moment. Nowadays it gets in the way more often than not. I feel it's starting to implode very slowly.
  - pjmlp 2y ago
    My experience with InteliJ has made me stick to Eclipse and Netbeans, unless external forces require me to use it.
    - canadianfella 2y ago
      [dead]
- MrBuddyCasino 2y ago
  > autocompletion industry This is a great line.
- gbear605 2y ago
  If you’re talking about the new autocompletion AI that they added a few months ago, you should be able to turn that off in the settings.
  - pandemic_region 2y ago
    And so I did after thirty seconds of using it.
- wg0 2y ago
  Why auto complete for a static language would be hard? Everything is known in advance. Genuine question.
  - invalidname 2y ago
    Because Java is static and relatively simple, the level of autocompletion is absolutely fantastic. E.g. a simple case, typing: int a = obj. Would show first only methods that return integers. But this gets far more sophisticated with completion anticipating your preference, naming variables for you, filling in the parameters with sensible values etc. Going back to the simple list of options is a bit of a pain. Also, this needs to be written in Java since it needs to read the API classes to make suggestions. But his editor code is probably in Swift.

by pquki4 2y ago

pandemic_region 2y ago

>It's not easy to get these basic lookups correct and smooth. Exactly, Intellij has been in the autocompletion industry for what, almost 2 decades? And still they present me with types in the autocomplete drop-down that I have never ever used in any of my projects. Yes I know, but I got tired eventually from excluding them. In my brain autocomplete is not hard, yet for an IDE guessing seems really really hard. AI improved this, at the cost of a second latency. No thankee sir.

qwerty456127 2y ago
Yet IntelliJ has always (figuratively, I dunno about its first years) been famous for having by far the best auto-completion ever. People used to become very upset when they were forced to use Eclipse after experience with IntelliJ.
- pandemic_region 2y ago
  True, it was good and lightning fast back then. Granted, the language (java) was arguably simpler then. Autocompleting a lambda is nightmarish at the moment. Nowadays it gets in the way more often than not. I feel it's starting to implode very slowly.
- pjmlp 2y ago
  My experience with InteliJ has made me stick to Eclipse and Netbeans, unless external forces require me to use it.
  - canadianfella 2y ago
    [dead]
MrBuddyCasino 2y ago
> autocompletion industry This is a great line.
gbear605 2y ago
If you’re talking about the new autocompletion AI that they added a few months ago, you should be able to turn that off in the settings.
- pandemic_region 2y ago
  And so I did after thirty seconds of using it.
wg0 2y ago
Why auto complete for a static language would be hard? Everything is known in advance. Genuine question.
- invalidname 2y ago
  Because Java is static and relatively simple, the level of autocompletion is absolutely fantastic. E.g. a simple case, typing: int a = obj. Would show first only methods that return integers. But this gets far more sophisticated with completion anticipating your preference, naming variables for you, filling in the parameters with sensible values etc. Going back to the simple list of options is a bit of a pain. Also, this needs to be written in Java since it needs to read the API classes to make suggestions. But his editor code is probably in Swift.