Finally I can recommend virtual threads without significant caveats.
Readit Newsbberrry commented on Feds Link Cyberheist to 2022 LastPass Hacks krebsonsecurity.com/2025/... · Posted by u/todsacerdoti
I think in some cases the iteration count was like 5000.
Mine had iteration count 1. I was livid when I found out. Fucking amateurs taking on the responsibility to safeguard everyone's passwords
bberrry commented on Why is the American diet so deadly? newyorker.com/magazine/20... · Posted by u/johnkpaul
I think this is an accurate point. I would also add preservatives. Companies have an incentive to increase shelf-life, so they pump these products full of them, despite their effects on health.
What evidence is there of preservatives having detrimental effects on humans (in the doses we actually receive)?
bberrry commented on Translating 10M lines of Java to Kotlin engineering.fb.com/2024/1... · Posted by u/ermatt
Honestly, none of those differences you listed seems especially compelling to me, except possibly for the ?. operator.
What would be compelling: Array types that don't hate generics, or generic collection types that don't hate primitive types. Does Kotlin improve on Java at all here? It's such a pain having to remember this bonus complexity when all I want is a consistent way to manage a bunch of things. (I suspect not, as I think the limitations are at the JVM level, but I don't know.)
Kotlin does improve on the primitives/boxed situation. For example in Kotlin there is just "Int", not both "int" and "Integer". The language will use stack-allocated primitives wherever possible and boxed objects when necessary (in Collection generics or when you've explicitly opted into nullability). The distinction is abstracted away from you as a programmer. Sounds like the consistency you want.
bberrry commented on Translating 10M lines of Java to Kotlin engineering.fb.com/2024/1... · Posted by u/ermatt
I used to do Java and Scala.
In 2020 I started a new project in Kotlin.
I like Kotlin, but what I hate is that in the meantime I migrated all my programming to Neovim and Helix. All programming? No, not Kotlin, because the LSP isn't there and JetBrains clearly has no interest, they want to sell their IDEs.
Now don't get me wrong, I have an IntelliJ license since 10 years, even back when I was employed and paid it out of my own pocket.
It's not about the price. I would gladly pay for the LSP implementation. But I don't want to use IntelliJ anymore.
So a new project on the JVM where I have a say in the stack? Java or maybe Scala. No more Kotlin.
This is the biggest issue with investing in Kotlin IMHO. The stewards of the language have a conflict of interest in democratizing the tools.
bberrry commented on Translating 10M lines of Java to Kotlin engineering.fb.com/2024/1... · Posted by u/ermatt
bberrry commented on Translating 10M lines of Java to Kotlin engineering.fb.com/2024/1... · Posted by u/ermatt
> And I don't need any of the tools you mention because it does the right thing by default.
I mostly agree with you, but Spring+Kotlin does require the allopen plugin, so it's kind of hacking Kotlin to do the wrong thing (all classes open) in order to support an arguably bad design choice by Spring.
Can't blame Kotlin for that. And it's a very minor sin frankly.. set-and-forget.
bberrry commented on Translating 10M lines of Java to Kotlin engineering.fb.com/2024/1... · Posted by u/ermatt
My biggest pet peeve with Kotlin is that they got rid of checked exceptions and replaced them with nothing at all. All error code flow is now just invisible unchecked exceptions, the single worst kind of error handling imaginable.
I know they added the Result type later on, but there's zero convenience to it, so you have to manually handle every error, even if you just want to bubble it.
Checked Exceptions were better, though Rust still has the best error handling in any non-functional language.
Depends on what you're writing I guess (as always). I write backend services and if there is an exception thrown, generally the whole request is forfeit. So a top-level exception handler is all that's needed.. no checked exceptions ruining my lambdas or streams like in Java.
Pix revolutionised the way we transact in Brazil. I've used Pix to pay for things that cost only cents, and I have a friend who bought her house using Pix. The system just works for any transfer amount. And it's so easy to use.
Its speed is truly baffling, and so is its reliability. Never have I failed to make a Pix payment because of downtime. I never cease to be amazed by how fast money arrives in my Brazilian account when I make a withdrawal directly from my EUR wallet on Wise. I receive a push notification from my Brazilian bank before Wise finishes running the animation of confirmation of withdrawal. It's like magic.
And it's so widespread that nowadays I don't even question whether someone accepts Pix. When I get in a taxi, no matter how old the driver is, it's certain that they take (and prefer) Pix.
I've even had homeless people ask me for Pix instead of change on multiple occasions.
Cryptocurrencies don't stand a chance.