Finally, someone made a good and modern replacement for vim. Rust for the win!. My original vim is just full of JS plugins to be able to work with LSP, etc., and it always breaks in some unexpected plugin with every update.

In case you don't recognise this, this is the default HTML error page from GCP Load Balancer. Can we have a bit better look (I'm not asking JS/CSS - hell no, just a bit more touch not to hurt eyes), please @googlecloud ?

Java world before Java 11:.- yay, a new feature. After Java 11:.- A third preview.- A fourth incubation.

The state of #Scala3 development in @IntelliJScala is still disappointing and it seems the company behind had stopped investing sufficient resources. Is there any way to use Metal without changing IDE? (I use Metal with vim, but vim is an editor, not a fully functional IDE).

The latest unfortunate news about circe json library in Scala makes uncertainties about its future. Didn't expect to ask it in 2021, but any recommendation for JSON library for Scala in the coming years? . @aplokhotnyuk I'm curious if jsoniter is available for Scala 3? :).

When a dark mode isn't something you expect .

#Java 14/17: We have records for you.Me: Yay, finally immutable classes without hassle like case classes in Scala. #Java 14/17: Wrong, you need to define "with" methods yourself if you want to create a modified copy of a record. Me: Are we punished for some unknown reason?.

Monad is just a context, but it changes everything.

Nothing is more personal than sending someone a merge request.

Can ask I really politely all of the web site developers? .Please, please, please stop using IP addresses to detect languages when you have my preferences in browser requests and even my settings in cookies. An IP address should be last priority for that. @GoDaddy for example.

RT @IntelliJScala: To support our work on Scala in IntelliJ IDEA do follow @IntelliJScala (please RT).

Static and strong typed code is honest code. Dynamic and weak typing is lying to yourself that you are going to cover it with unit-tests someday and being afraid of future refactorings. If you were honest with yourself and really care, why not to cover it right at the beginning?.

Sometimes syntax #Rust might be really confusing. Correct me if I'm wrong, but there is no way to define explicitly types for async function reference for variables. All you can do is just use type inference in this case. Is there any reasoning for this, or this is WIP?

It is 2020 but the one still can't download the final ISO spec for C++ for free? Really? .(Yeah, I remember you can find some drafts somewhere, but it's not normal for computer languages anymore, is it?).

Is there any (logical) explanation, why #golang went with this syntax:. > map[string]int.> []int{0, 3}. I know that they didn't like to complicate their language, but in what world that syntax is simpler than just intuitively comprehensive.> map[string,int] .> int[] { 0, 3 }.

Published my first #rust cargo for strongly typed pleasures (a haskell newtype replacement macro). This probably exists somewhere else, but I haven't found it yet (so, any hints are welcome).

The one can't appreciate case classes and enums from #Scala enough until they try to survive with records from #Haskell (which still are a nightmare even with RecordDotSyntax). #Rust provides much better support than Haskell, but still not quite there (. Default::default, . ).

Damn, this is brilliant :D.

Is it only me who tries to exit from #ghci all the time using ":q!" instead just ":q"? Cursed by #vim ^^.

RecordDotSyntaxes in #Haskell. Finally.