Hacker News: olcay_

New comment by olcay_ in "Deno Desktop"

olcay_ — Mon, 22 Jun 2026 08:20:30 +0000

There's Compose Multiplatform if you are willing to switch to Kotlin. Only caveat is that it uses Canvas rendering on web.

New comment by olcay_ in "Anthropic's open-source framework for AI-powered vulnerability discovery"

olcay_ — Fri, 05 Jun 2026 01:31:53 +0000

Anthropics is Anthropic's user name on GitHub

New comment by olcay_ in "It's hard to justify buying a Framework 12"

olcay_ — Fri, 29 May 2026 22:50:23 +0000

That's not what they're saying at all.

New comment by olcay_ in "I analysed 20 years of my chats"

olcay_ — Thu, 28 May 2026 13:44:22 +0000

I set my chats to be automatically deleted in 24 hours. This way when we have a small argument with someone, there's less chance of someone being triggered/angered by re-reading the chat. Although there have been rare cases where I had big arguments and would've liked to have the receipts.

New comment by olcay_ in "DeepSeek makes the V4 Pro price discount permanent"

olcay_ — Sun, 24 May 2026 15:57:03 +0000

I'm using the official API and I've had no issues.

New comment by olcay_ in "The Emacsification of Software"

olcay_ — Thu, 14 May 2026 01:29:29 +0000

If WASM succeeded in being the one universal ABI, it could be the perfect successor to the unix pipe for the AI age. Wasm modules for libraries, that double as terminal tools.. One could only imagine

New comment by olcay_ in "Teaching Claude Why"

olcay_ — Sat, 09 May 2026 16:25:59 +0000

It's interesting that they lowered the misalignment rate by that much with only 3m tokens of training.

Maybe we can align models by ourselves to our liking in the future.

New comment by olcay_ in "Principles for agent-native CLIs"

olcay_ — Thu, 07 May 2026 22:59:36 +0000

⅑3²

New comment by olcay_ in "I cancelled Claude: Token issues, declining quality, and poor support"

olcay_ — Sat, 25 Apr 2026 01:09:32 +0000

Claude Code has something about picking sensible choices instead of asking questions in the system prompt, that's probably the problem.

New comment by olcay_ in "Codex for almost everything"

olcay_ — Thu, 16 Apr 2026 21:57:15 +0000

Anthropic coming out to say they won't surveil Americans wasn't actually a positive for me. It meant they're okay with surveilling the rest of the world, which in turn signaled "fuck you, you're inferior, deal with it" to me (as someone from the aforementioned rest of the world).

When OpenAI snatched those contracts, it made me think no worse of OpenAI. The surveillance was already factored into how I saw them (both).

New comment by olcay_ in "High-Level Rust: Getting 80% of the Benefits with 20% of the Pain"

olcay_ — Sun, 12 Apr 2026 10:05:09 +0000

There definitely is Kotlin without Java, and you can compile Kotlin code for use in jvm, ios/ipados/macos, android, wasm/js, and native.

New comment by olcay_ in "Meta told to pay $375M for misleading users over child safety"

olcay_ — Wed, 25 Mar 2026 12:46:44 +0000

I think they meant that Meta is offloading the cost (fines) of farming minor's data onto the operating systems. With an up-front cost of 2 billion dollars in lobbying, they can avoid paying 300m+ fees regularly.

New comment by olcay_ in "So you want to write an “app” (2025)"

olcay_ — Tue, 10 Mar 2026 01:13:50 +0000

I think Jetpack Compose is not actually as bad as you think. I think it's really great and I wish more people caught on actually.

I can't comment on the learning materials as I was following it since the project started and I was already accustomed to the Android Developers website.

Kotlin has a few reactiveness concepts that make reactivity easier but might scare off developers from other languages. The most important ones are Flows and Coroutines.

Say you want to have a UI that shows the current list of connected devices that should always show up to date info. The function to get the list would be something like this:

  val devices = manager.getDevices()

But you need it to be declarative instead of imperative, so you use a Flow:

  val devices = flow {
      while(true) {
          emit(manager.getDevices())
          delay(1000)
      }
  }

Devices is now a cold flow. It does nothing unless it's being collected. When you start collecting it, e.g. by using collect:

  devices.collect { list -> ... }

Now it starts running the while loop and you get the up to date devices list in your lambda every second. You can also make the lambda run only when the list has changed, or debounce it, or run only for the latest value, and more with trivial function chaining. But this function is suspending, which is Kotlin's way of async functions, and suspend functions take turns running on the threads that are managed by the coroutine scope they are in, so you need to provide it a coroutine scope by wrapping your collection in scope.launch { ... } .

And your viewmodel can now collect the flow in a way that's going to be accessible without suspending (async) functions by turning it into a StateFlow:

  val devicesStateFlow: StateFlow> = devicesFlow.stateIn(scope, some more arguments...)
  // Now synchronous code can call like this:
  print(devicesStateFlow.value)

  // And Compose (reactive ui) code can do this in Composable functions:
  val devicesState by vm.devicesStateFlow.collectAsState()

I think that was the source of confusion you had when you were trying to use datastore. It's designed for reactive applications so you were supposed to use it in a viewmodel, turn it into a stateflow and collect it as state in your ui.