If higher-level abstractions should be at the top of the file, then shouldn't all imports be listed at the bottom? 🙈

Awesome talk by @AndreiPangin "A Simple Approach to the Advanced JVM Profiling". Lots of profiling on the JVM wisdom and reasons why async-profiler is the best tool in town (I just wish it had more regular releases 🙏)

Random idea: integrate LLM into a disassembler to make the code somewhat readable even if it was obfuscated. Or observe program behaviour at runtime and generate source code that could reproduce the behaviour 🤔

TIL there is a JITWatch4i plugin for IntelliJ to analyze/visualize JIT compiler activity, generated assembly, etc., and there are nice examples in its readme

It's party time 🥳 Because we will have folding regions for function/constructor arguments in Kotlin And I will be able to retire this plugin

It's fascinating how much the lack of a fast feedback loop contributes to the difficulty of a problem. And the "industry standard" infrastructure solutions only make it harder for the sake of scale that you can't have or don't need. I hope the era of "cloud mainframes" will end.

@yx_weili Took me a while, but you're basically saying that it should've been 4721 on the map 🧐 Thank you for the correction!

What if in addition to the type inference, there was parameter/variable name inference (e.g. lower camel case based on type and name clashes is an error)? This could encourage the use of tiny (aka micro) types 🤔

@yx_weili To be honest, I didn't expect any of the start of years dates align at all 😅

I'm not convinced about functional parameters called "block" given the ambiguity of "code block" and "to block". It's often obvious from context (until it's not), but then there is `async { block() }` in Kotlin where the block doesn't block.

Arguably, there is sometimes a trade-off between expressive code structure/formatting and its usability in debugging tools (e.g. stepping through functional code). Ideally, this is to be fixed by the tooling, but in practice, it is something to consider for libraries/frameworks.

[offtopic] Trumpety-trump, trump, trump, trump Did anyone say the war will stop in 24 hours?

TIL while iA Presenter is good at quickly creating reasonably looking slides from Markdown, you can pretty much get 80% there with the reveal.js Markdown plugin

Maybe it's already a thing but why isn't there a tool (I mean an executable file) for GraalVM native image that could look at a project and using reasonable guesses just compile it into a binary? (Asking so that I can avoid modifying any Gradle scripts.)

"feature" not "features" #notpayingfortheeditbuttonanditstoolatetofixthisplaceundermsukdictatorshipanyway

Here is an old message that not all progress is always progress What would this mean for software? Labeling apps, UIs, or APIs as long-term support and avoiding breaking changes for many years (assuming the company survives)?

Speed vs correctness is a false dichotomy (at least for creating software). It's about making progress without too many negative consequences (broken software, wasted effort, bad design, etc.). Some problems can't be solved by "thinking harder", see #noPRs

RT @intellijidea: 🦋 IntelliJ IDEA is now also on Bluesky! Follow us to stay updated with coding tips, feature highlights, and community ne…

@martinbonnin I'm using Amper on a pet project and it's a great setup with ~5 LOM (lines of yaml) but if anything, the build is even slower than Gradle, >2 seconds without any code changes. I'm becoming jealous of Maven build times 😱🙄