1. @fasterthanlime Oh no.......

  2. @jntrnr Happy pride! Very happy for you!!

  3. @botteaap Upgrade to Gradle 8.1 or if you can't, put `@file:Suppress("DSL_SCOPE_VIOLATION")` at the top.

    Gradle prior to that version generates slightly invalid code that the Kotlin compiler correctly complains about.

    Replying to source post

  4. @ivan Definitely not alone, the whole "blocks" concept completely evades me.

    I had to write a blog post for work in Notion and it was about 10x easier to write it in Markdown in Visual Studio Code and import into Notion than to do it in Notion itself.

  5. @jubilee I have a couple that use let chains, would that be useful?

  6. @paul Asahi Linux is already a pretty viable OS option, I expect it to only get better with time.

  7. @fasterthanlime inline code snippets are monospace but block ones are not? That is...new

  8. @alsutton That's a pretty uncharitable interpretation of the situation at hand. Compose Compiler is built on a foundation with no stability guarantees so it's neither JetBrains' fault when they make breaking changes in any version nor Google's that they strictly enforce what version they claim compatibility for.

    Both organizations are collaborating to improve the situation but in the mean time I would rather have this explicit discouragement upfront than obtuse build errors towards the end.

  9. @marcan@treehouse.systems Never once did he question why sites would elect to punish HN referrers or try to address that.

  10. @foone If you haven't provisioned a new toolchain yet, the env variable RUSTC_BOOTSTRAP=1 makes the stable compiler not complain about trying to use nightly features.

    If someone asks, you didn't hear about it from me :D

  11. @SylvieLorxu There is a emulator device type titled something to the tune of 'Resizable (experimental)' which does give you the option for a foldable sized display but sadly no dual-screen yet.