Ir para o conteúdo

Alexander Reelsen

@spinscale.bsky.social did:plc:yklisov533zvvd4a3ejpktzq

Husband, dad, enjoys working distributed, likes distributed databases & search engines, the JVM, Basketball/Streetball fan, gulps coffee, lives in Emsdetten/Germany, occasionally blogs at https://spinscale.de

No Bluesky desde

Seguidores
269
Seguindo
474
Posts
751
Dias nos rankings
0

Resumo

Alexander Reelsen (@spinscale.bsky.social) é um usuário do Bluesky desde 21 dezembro 2024. Tem 269 seguidores, segue 474 contas e publicou 751 posts.

Aparições nos rankings

Os melhores dias em que posts desta conta entraram na lista diária do Debya.

Esta conta ainda não apareceu em um ranking diário.

Posts curtidos recentemente

Curtidas públicas da rede Bluesky.

  • joschi@joschi.work

    Is this good? Asking for a friend… (device: STRONG LEAP-S3+) #XCPE #AndroidTV #GoogleTV #Botnet

    Ver post
  • Sylvain Wallez@swallez.com

    Quand je lis le CTO de Proton dire "Your job is no longer to write code. Every engineer is now a manager of agents" ça me rappelle les années 90 (oui, j'étais déjà au boulot), où nombre de grand-comptes ont outsourcé leurs développements, parce que ça n'était pas leur core business.

    Ver post
  • Rafael Winterhalter@rafaelcodes.bsky.social

    Running a single module scews the measure, too. A big build, where build time matters, will take minutes. Two seconds of them to warm up, maybe, but you will lose two seconds on each forked call to Javac, jar, Javadoc. This cannot work.

    Ver post
  • Rafael Winterhalter@rafaelcodes.bsky.social

    Unlikely. With repeated builds, most runtime goes to JVM tooling. If you use Javac via the tools API and keep the VM warm through a daemon, you will outperform Rust by length. Warm Java in itself is hard to beat.

    Ver post
  • Jesse Wilson@swank.ca

    ‼️ An OkHttp interceptor to defend against today’s TLS disaster

    Ver post

Entre para ver mais

Contas que bloqueia

No Bluesky, bloqueios são registros públicos.