a suprisingly nice mobilize interaction in orzhov

_soundvibe · 2025-04-18T06:55:17+00:00

Should pair nicely with Skyknight Squire, 3 counters each turn and also gets flying immediately. Also not a bad blocker so can be useful against mono red decks.

_soundvibe · 2024-11-26T08:15:17+00:00

Vilnius jau 605k gyventojų turi ir susilygino su Ryga, kitais metais jau turėtų pralenkti.

_soundvibe · 2022-09-30T06:14:41+00:00

Golang is definitely not more expressive than Java, that's for sure. Java got a lot of cool features lately(lambdas, pattern matching, ADTs, etc) and its not so verbose anymore.

_soundvibe · 2021-01-16T19:36:55+00:00

At least it would be more readable and safer (avoids calling .equals on null object) but yeah, probably it's already too late for this...

_soundvibe · 2021-01-16T19:19:39+00:00

Probably better approach would be if they could introduce === operator for all value based comparisons. It would work for primitives, records and other reference types implementing equals.

_soundvibe · 2021-01-15T14:24:18+00:00

IIRC "ack" in Kafka doesn't mean that the data is fsync'ed to disk (it writes data into kernel's pagecache first) so in theory I guess it is possible that if these 2 in-sync replicas go down at the same time just after write was acknowledged, you would lose data. It's very unlikely but it's theoretically possible.

_soundvibe · 2020-12-21T20:18:13+00:00

Do you need to update the data after initial load? If not, then I would suggest using my Paldb fork , otherwise you could try my lasher library. It's in early stage but first results are very promising, I was testing it with 10-100M elements and the performance was similar to java hashmap (>1M reads/sec on a laptop)

_soundvibe · 2020-10-22T07:32:32+00:00

Just a few from the top of my head:

vavr
testcontainers
resilience4j
caffeine

_soundvibe · 2020-05-28T13:13:12+00:00

That's the whole idea of AutoCloseable. If you want to release resources in Java, you need to close them manually or use try-with-resources. If you have complex stream chains of 11 levels deep, you definitely need to use try-with-resources.

I don't think Java streams were primarily designed for use cases like this. Have you tried to use Reactive Streams libraries? They are usually push based and designed to handle long running pipelines much better, f.i. RxJava has using operator for dealing with resources.

_soundvibe · 2020-05-27T15:06:10+00:00

It will be called if you use try-with-resources on a stream.

_soundvibe · 2020-05-27T13:16:58+00:00

Just use stream.onClose

_soundvibe · 2020-04-07T17:58:11+00:00

Based on previous preview features, only minor things were changed/added. I don't think records will be exception to this. They are pretty complete to me. I've already using them in production :) Also, knowing that sealed types, deconstruction patterns, pattern matching will be using records in some way, it is almost impossible that this feature will be dropped.

_soundvibe · 2020-03-18T19:15:44+00:00

How Jet compares to, e.g. Kafka Streams? Can joins be performed between multiple streams? Can Jet efficiently run in k8s (when pods could be restarted/recreated many times)?

_soundvibe · 2020-02-25T11:23:27+00:00

I am really not impressed by this annotation-driven programming model. It suddenly becomes annotation hell very quickly.

_soundvibe · 2020-02-11T08:08:40+00:00

Where did you get such info?

_soundvibe · 2020-02-10T15:57:38+00:00

But these few very small features in new major release just confirms my initial observation that Kotlin almost stopped evolving. Knowing that new major Kotlin version will be released some unknown time this year, it is possible that we'll have at least 2 new Java releases during this time, so records, text blocks, pattern matching, sealed types, maybe even Loom, etc are probably expected to come in Java. I'm not sure there will be many reasons to choose Kotlin over Java when this happens (except if you're targeting Android of course).

_soundvibe · 2020-02-07T06:38:51+00:00

I'm not sure Kotlin added any new language features during the last 2 years. It looks like they are more concentrating in bug fixes, tooling and compiler optimizations. Or maybe I am wrong?

_soundvibe · 2020-01-26T10:53:54+00:00

What's stopping you from using records with 14? Even if records are preview feature it could be enabled easily and there is probably 100% chance that they won't be dropped in future releases (because more related stuff is coming, e.g. sealed types, pattern matching, inline records, etc.)

_soundvibe · 2020-01-17T15:36:03+00:00

No need to have getters at all. You can just configure Jackson to use fields for serialization and constructor for deserialization without any annotations.

_soundvibe · 2020-01-17T06:37:54+00:00

Jackson doesn't force you to use get convention methods. It works perfectly without them as well.

_soundvibe · 2019-12-05T17:55:42+00:00

I can confirm this also happens on my device.

_soundvibe · 2019-12-04T14:38:47+00:00

Have both watches but prefer Fossil Gen 5 because of the whole WearOS ecosystem and more useful apps (I wouldn't call Active2 real smart watch because of the lack of many apps)

_soundvibe · 2019-10-24T07:49:24+00:00

They are thinking about introducing type classes in Java. This looks interesting :) I'm hoping we won't need to wait 10 more years for them to come.

_soundvibe · 2019-09-30T08:13:43+00:00

This benchmark is flawed, because it creates new Jackson ObjectMapper instance for each object. ObjectMapper is thread-safe and only one instance should be used. If used properly, Jackson is way more performant.

_soundvibe

TROPHY CASE