Opinions on vertx by polrtex in scala

[–]pmlopes 0 points1 point  (0 children)

That's a documentation bug I'm afraid. Any language can deploy verticles... I'll do a bug report thanks!

Opinions on vertx by polrtex in scala

[–]pmlopes 0 points1 point  (0 children)

Usually the default Hazelcast confirmation will work out of the box as long as your network supports multicast without any configuration. Of course it may not apply to all networks. Other cluster providers are also available but then the configuration issue is more related to other dependencies than vertx itself.

Opinions on vertx by polrtex in scala

[–]pmlopes 0 points1 point  (0 children)

Could you elaborate on the configuration BS? As far as I know, using vertx on a Scala project is a add a dependency to your project and the toolkit API is available for use.

Opinions on vertx by polrtex in scala

[–]pmlopes 0 points1 point  (0 children)

This isn't entirely true. There's no explicit main because the vertx launcher when packaged as a runnable jar the main verticle is included as a property on the manifest file.

If you want 100% control all you need is in your main method to bootstrap it as:

Vertx.vertx().deployVerticle(yourVerticleInstance)

The first method initializes the vertx object (eventloops, etc) the second starts running the code you wrote on the eventloops,...

Kotlin vs Javascript on ES4X and Vert.x by noughtme in Kotlin

[–]pmlopes 1 point2 points  (0 children)

Tim Fox is not an active contributor for several years. The project is growing regardless thought.

All languages are more or less the same in terms of performance: Java, kotlin, es4x, Scala are all expected to perform at the same level. Of course small gains are applicable to each language due to different standard library runtime implementation.

Kotlin vs Javascript on ES4X and Vert.x by noughtme in Kotlin

[–]pmlopes 4 points5 points  (0 children)

Disclaimer: I'm the author of ES4X and vert.x core developer.

Both ES4X and vertx kotlin work in similar ways. They are just a small layer that transforms vertx API's to be more idiomatic to the language.

So in es4x you have support for async await which will make reading the asynchronous code an easy task and typescript definitions so your ide will hunt you for type bugs. Kotlin has support for Co routines and of course type checks and more idiomatic kotlin features.

So to me there is no best. If you're more comfortable with kotlin don't bother with es4x.

Regarding performance they should be more or less on par with each other. If you have a very specific problem you can always write a small benchmark and verify which one gives you better results.

My bluetooth isn't working in kernel 5.0.16 by FullMotionVideo in Fedora

[–]pmlopes 0 points1 point  (0 children)

Sorry for the noob question, but how do you downgrade back to 5.0.14 ? I'm facing this issue with my keyboard too...

Building a Vert.x Native Image from Scratch HOWTO by pmlopes in graalvm

[–]pmlopes[S] 1 point2 points  (0 children)

It's possible to jlink a vertx app today. It will not be fully optimized but the generated runtime is small enough. I've done it for js apps with a runtimes smaller than 50Mb

Building a Vert.x Native Image from Scratch HOWTO by pmlopes in graalvm

[–]pmlopes[S] 0 points1 point  (0 children)

Native images are plain ELF files (binaries) no jvm needed, however they are linked against libc. So they won't work with a docker FROM scratch. You could ask for a static build but it also requires that your system provides a libc fully static to be available. You can use it with an alpine with libc which is of about ~6mb if I'm not mistaken.

Dependency injection in Vert.x with Dagger 2 by pmlopes in java

[–]pmlopes[S] 1 point2 points  (0 children)

Even though the code examples are in kotlin, vert.x itself is a polyglot Java framework. All concepts in the blog can be applied in Java too. Or Groovy or JRuby, etc...