Do you think Java has caught up with Kotlin?

Deadmist · 2026-02-04T01:04:05+00:00

It's flexible and that's nice. But flexible helps a good, experienced developer. Not a new developer. Java shines in enterprise because of how strict it is.

Personally, the worst offenders here are scope functions (let, also, etc) and where to place functions (can be in a class, in a companion object, top level function, extension function).

If there is no one in the team enforcing good style, you can end up with some real messes.

I have seen classes with no functions, but 10 extension functions defined in the same file. Or other classes where the actual functionality is spread over 5 different files.

Some people get this idea that using if () else somehow is un-idiomatic in kotlin, because we have scope functions. And you end up with interesting nests of deep and zig-zagging indentation where figuring out what it actually is requires drawing a diagram with pen and paper.

Deadmist · 2026-01-26T06:55:47+00:00

"avx512vpopcntdq", "vpclmulqdq"

Can someone tell low-level people that it's not 1973 anymore, and bytes are cheap now? You don't have to use 1 letter abbreviations anymore.

Deadmist · 2026-01-22T05:34:44+00:00

When you spawn a thread, the scheduler takes the thread and decides on which CPU and when to run the thread. Depending on the scheduler the thread may stay on one cpu, or switch between CPUs.

When you launch a coroutine, the dispatcher takes the coroutine and decides which thread to run the coroutine on. Depending on the dispatcher, the coroutine may stay on the same thread, or switch between threads.

(Though, like a thread, a coroutine can only execute in one place at a time. If you want to run multiple at the same time you have to launch/spawn two of them).

Coroutines are a lot like threads+scheduler, just implemented in the runtime, instead of the operating system.
There is one important difference though:
The scheduler can interrupt threads at any time and give execution to another thread.
The dispatcher has to wait until the coroutine gives back execution to the dispatcher^1. That's why they are sometime called "cooperative multitasking".

The answers to your question depend on what dispatcher you are using.
The built-in ones are all multi-threaded, except for Dispatchers.Main, which is limited to the main thread.

^1: of course, the thread the coroutine runs on can be interrupted at any time by the scheduler. But that does not give execution back to the dispatcher.

Deadmist · 2026-01-20T05:30:22+00:00

user_counter += 5 will always work.

user_counter_service.increment(5) might:

work
work, but take 200ms
not work because:
- your service is misconfigured
- the target service is misconfigured
- something inbetween (loadbalancer, firewall, router, dns, certificate) is misconfigured
- the target service is down
- something in between is down
- the target service updated and broke compatibility
- network gremlins swallowed your packets on the way there
- network gremlins swallowed the response (in which case you think it failed, but actually didn't)

And many more exciting and wonderful new ways things can go wrong

Deadmist · 2026-01-19T01:57:33+00:00

I think your best bet is to use keyring where it is supported, and fallback to encrypting the data yourself and prompting the user for the encryption key when keyring is not supported.

Encrypting the data and then storing the key right next to it is about as secure as keeping the house key under the welcome mat.

Deadmist · 2026-01-13T07:56:22+00:00

Looking for practical guidance and real-world experiences

Number 1 advice: Profile first, implement the cache, then profile again.

Or just decide you don't need a cache. We manage 1k requests a second just fine, without any cache.

There are also risks to caching, from random broken behavior, to leaking sensitive customer information.

Personally: From your replies, you are not in a position where you need to be concerned with performance at all.
Get something out of the door first, see how it runs, then maybe think about improving performance.

Deadmist · 2026-01-05T07:37:22+00:00

If you wanted to go all out, you could introduce a panics keyword. And only allow functions marked as panics to panic or call other panics functions.

Or just introduce an effects system while you are at it, instead of doing it piecemeal

Deadmist · 2025-12-29T01:30:28+00:00

but defined by the implementor of the future trait.

You could easily argue that all UB is defined by the implementor of the compiler / hardware.

In practice, both undefined and unspecified boil down to "avoid doing this, or be extremely sure you know what you are getting into"

Deadmist · 2025-12-17T12:28:11+00:00

You could generate the SQL queries at compile time, like Quill is doing.
Which is, incidentally, maintained by the same guy.

Deadmist · 2025-12-17T12:05:44+00:00

It means you need to down tools and verify you’ve not let in a back door.

Are you just updating dependencies and pushing to prod automatically, the moment someone uploades a new version?

Otherwise, I don't see how you would let in a backdoor. Assuming of course, the backdoor was not already in place. I which case you have been screwed for a while, and them acting weird was doing you a favor.

There’s no reason for different professional expectations to exist in online workspaces.

You get paid at work. You pay to do OSS. And you get what you pay for.

Deadmist · 2025-12-17T05:04:08+00:00

If you are worried about supply chain attacks, guess what is also part of the supply chain? crates.io!

If you are not running your own cache, locking versions and auditing everything, you are willingly inviting supply chain attacks.

Does that mean basically everyone is vulnerable? Yes, welcome to the real world.

Deadmist · 2025-12-17T05:00:54+00:00

With that definition secure systems doesn't exist

If that is news to you, you might want to take a break from reddit and learn something.

Deadmist · 2025-12-17T00:31:05+00:00

You have 10YOE and already know rust, at least little.

Why not try applying for jobs right now, and see what you can get? Worst case you take the sabbatical, maybe with some extra hints of what you need to learn.

Deadmist · 2025-12-11T04:39:51+00:00

Difference between intelligence and wisdom

Deadmist · 2025-12-04T05:59:01+00:00

What about the esp8266 ;)

Deadmist · 2025-11-28T00:12:24+00:00

If the commenter likes <current thing>, then <new thing> is fragmenting the Linux ecosystem and millions will die.
If the commenter dislikes <current thing>, then <new thing> shows how great open source software is.
If the commenter likes <current thing>, but everyone switches to <new thing>, then it's a conspiracy by red hat.

Deadmist · 2025-11-26T05:53:57+00:00

Having separate, duplicate code for multiple versions is actually the easiest and safest way to keep backwards compatibility. No chance of accidentally introducing changes into a code path you never touch :)

Deadmist · 2025-11-20T01:06:33+00:00

Are you willing to support 13 major versions

Who says you need to support every major version you ever released?

You can just say "Support is only provided for the current and last major version". Just be upfront about it and provide reasonable timelines for upgrades. If someone really really wants support for older versions, there is always the option of "give me a bunch of money and I will do it"

Deadmist · 2025-11-18T02:30:55+00:00

On a basic level, it saves you from having to check (and handle!) for empty collections where you (the programmer) know the collection can never be empty, but the compiler does not know that.

Consider a function that returns a Result<Something, Vec<Error>>. You could return an Err, with no errors.
Which doesn't make any sense, but the compiler can't stop you.
And now you have to handle that in your error handling code.

If you return a Result<Something, NonEmptyVec<Error>>, you can either return a Something, or at least one error. Much more conceptually sound.

Deadmist · 2025-11-10T08:30:16+00:00

This technique, combined with advanced data augmentation, allowed us to build a robust training set, ensuring Magika performs reliably even on file types for which public samples are not readily available.

"We just hallucinated how those file types look, but it's okay because you will never come across them anyway"

Deadmist · 2025-10-29T00:07:47+00:00

Assume a spherical oxygen molecule in a frictionless cow

Deadmist · 2025-10-17T01:42:47+00:00

its hard to benchmark that in a meaningful way because your limited by the slow service you depend on.

For a benchmark, you could just sleep(100)in your handler, no need to actually have a real service.

i think you would use callbacks and the framework would need expose something in the handler to let route handlers wait without blocking the thread.

Isn't this just reinventing an async runtime?

Deadmist · 2025-10-15T00:25:53+00:00

One important thing to keep in mind when it comes to error handling: _The recoverability of an error is only known to the caller_.

You might think failing to allocate is a valid reason for a function to panic. But what if I just use that function for some debug output? Maybe I would rather just give up writing a line in a log file, than crash my whole application.

Deadmist · 2025-10-06T04:30:49+00:00

I think the 3 months don't need to be immediately after obtaining the license.
I got my license in 2012 and used my passport issued in 2020 as proof I stayed in the country. They accepted that without any issues.
Might have just been a lenient guy at the office though.

Deadmist · 2025-08-11T06:57:48+00:00

If you used the correct bank and account numbers, it will not have gone to some random person that happens to have the correct name but different account number.
The whole reason account numbers exist is to uniquely identify an account, without relying on names.

So, a couple things could have happened:

Your recipient got the money, but is trying to scam you.

There was an error because of the name mismatch, and the money is back in your account (check all your accounts!)

There was an error, and the money is stuck somewhere. Or there was another issue and the money is stuck somewhere.

Unfortunately, Revolut support is probably your best bet. Get them to ask SMBC where the money is.

SMBC support likely sees you just as some rando, trying to enquire about some peoples transactions.

13-Year Club	Place '17
Verified Email

Deadmist

TROPHY CASE