JetBrains

Obviously, I use too much #jetbrains, I am surprised fleet eating this much disk 🤓

@jetbrains @fleet

Hilarious UI glitch!

The UI asks your country of residence, wants you to pick it from a list. No search, and the list is looooong. In the German version of the UI, country names are offered in German ✅ . The list is sorted alphabetically - but not by the German country names as displayed, but alphabetically BY THE ENGLISH VERSIONS! "Deutschland" is somewhere in more or less G 🤦‍♂️ !

Seen at the checkout page of @jetbrains's Python dev survey that https://pypi.org/ currently advertises.

On se retrouve mardi prochain à Bordeaux pour parler de #ComposeMultiplatform !

Compose Multiplatform permet d'écrire de l'UI en Kotlin, dans le style de #react. Compose est la manière officiellement recommandée de développer des applications Android, et est compatible iOS, desktop, et web.

À l'occasion de l'événement, @jetbrains offre deux licences annuelles, qui seront tirées au sort.

En savoir plus, et s'inscrire (gratuitement) : https://BordeauxKt.io

#kotlin #JetpackCompose #AndroidDev #iosdevelopment #KotlinMultiplatform #composemultiplatform #webdev

After seeing people use the @jetbrains UI to commit to git I understand where all those - sorry: shitty - commit messages come from....

🙈

An improvement would already be to have a "Subject" line and the text box.

And have the subject line follow the Beams Rule.

Sonthat the first line of the commit message finishes the sentence

"When this commit is applied it will..."

And please: No longer than 56(?) characters (Unicode). Keep it short. You got the textbox to explain *why* in full length.

The JetBrains Developer Recognition Program is expanding! Recognized #GitHub Stars can now enjoy free access to all JetBrains IDEs.
Learn more ⬇️

https://blog.jetbrains.com/blog/2024/10/08/github-stars-join-the-jetbrains-developer-recognition-program/

@khalidabuhakmeh I was expecting this toot from you 🕺 I still wonder which one is the real jetbrains account below, anyway it would not hurt mentioning more accounts, this is a good news

#jetbrains @[email protected] @[email protected]

Dlouholetým partnerem ne-konference @jopenspace je společnost @jetbrains tvůrce integrovaných vývojových prostředí, které většina z nás denodenně používá. Tři nejlepší talky se mohou opět těšit na roční licence IDE dle svého výběru! #JOSCZ24

Good news from today, I got my open source licence from @jetbrains for https://github.com/ozkanpakdil/swaggerific thank you #jetbrains 🤓

Not a fan of the #AI hype at all, but @jetbrains #RustRover new full line code completion feature is impressive

https://blog.jetbrains.com/blog/2024/04/04/full-line-code-completion-in-jetbrains-ides-all-you-need-to-know/

Do you find it tedious to build a file tree with snake-case text and dates to create the file for your blog posts?

I do too!

In this blog post I show you how I automated that with Webstorm.

I'm pretty sure it works with all other @jetbrains IDEs!

https://blog.charlesdesneuf.com/articles/create-a-new-file-at-the-right-place-with-prefilled-content-thanks-to-jetbrains-ides/

Link to a (frustratingly) deleted question on Stack Overflow. Text and image copied below incase you don't have the ability to see it. (Not sure why the image shows multiple times.)

Is there any way to more granularly control IntelliJ IDEA's inspections' "Nullability and data flow problems" option "Treat non-annotated members and parameters as @Nullable"? Preferably for unboxing specifically?

I am aware I can use a variety of @Nullable annotations in a variety of places in the code to make the warnings appear. That's not always an option as the place the boxed primitives are coming from may be other libraries you don't have control over. (Imagine if the Holder record below was from a different project.) I included other examples below to illustrate my point.

public class Sample {

    private final Boolean value;

    public Sample(Boolean value) {
        this.value = value;
    }

    private boolean isValue() {
        return value; // I would like a warning here
    }

    private static Boolean boxedTrue() {
        return true;
    }

    private static boolean unboxedTrue() {
        return boxedTrue(); // No warning here, but that's understandable since never null
    }

    private static Boolean boxedNull() {
        return null;
    }
    
    private static boolean unboxedNull() {
        return boxedNull(); // Only warning in the file (by default)
        // "Unboxing of 'boxedNull()' may produce 'NullPointerException'
    }

    public record Holder(Boolean value) {}

    public boolean openHolder(Holder holder) {
        return holder.value(); // I would like a warning here
    }
}

When "Treat non-annotated members and parameters as @Nullable" is enabled, the following gives warnings. While that makes sense given the name of the option, there is code like this literally everywhere. It adds hundreds of warnings to my project. I'm trying to find more granular choices.

    public static ZonedDateTime timeStuff(LocalDateTime localDateTime, ZoneId zoneId) {
        return localDateTime.atZone(zoneId); // I do not want warnings for this
    }

I see that the Java Class Library has JetBrains annotations despite not actually being annotated. Is there perhaps some way to add these automatically to libraries if there is no better way to control the inspection?

Just installed the new version 2024.2 of @jetbrains #webstorm
I really really hate the new UI and I am very annoyed how Jetbrains tries to force me to use it.
Now it's even just a plugin 😠
Jetbrains, I'm a paying customer. This will stop at the moment when you no longer support the classic ui.

What de hell is this ? (PhpStorm 2024.2) #phpstorm #jetbrains @jetbrains #php

All popular IDEs (and most apps) seem stuck in a single-monitor paradigm. When are we going to get an IDE that sets the bar for working with multiple monitors? For inspiration, look at multi-monitor audio engineering consoles. Please
@jetbrains

Has anyone in the #Rust world taken a serious look at what would need to be done for Rust-LLDB to have the level of usability that the @jetbrains @rustrover debugger has, e.g. for actually understanding enums etc.? If so, can you point me at it? I would like to understand the status! (Also, major props to the RustRover team here.)

ok, @AsahiLinux ([email protected] remix) installed on this m1pro macbook pro. and it's working. @jetbrains #IntellijIdea installed and working too even if its name is awkward af, building and running my project in @eclipseadoptium #Temurin #java but JetBrains Toolbox crashes when it tries to open the window. everything else seems ok and *noticeably* snappier than same under vmware fusion on a mac studio. mastodon access via @Tuba

Messed around this weekend trying to make a desktop app with #Kotlin and #ComposeForDesktop, and it's clear to me that it still has a long way to go. The documentation for it is severely lacking and #KMP libraries really seem to be focused on mobile rather than desktop.

Then there's @jetbrains Slack, which would be cool to use to ask questions if only I could figure out how to get access. You can read archives, but if people link to other threads or messages, the link simply doesn't work.