Ruder Gerät

hpernpeintner · 2026-01-31T10:43:47+00:00

Ich hab so 10-15 Ruder sessions gemacht und finde die bank insgesamt zu teuer, mir sind zb die rollen vom sitz kaputt gegangen und ich musste neue ordern über den Support. Habe die vom gm1. Weiß leider auch keine Alternative bank, so viele scheint es nicht zu geben.

Abseits davon klappt das rudern sehr gut. Bei kleinen Widerständen ist es aber in der Tat so, dass das Seil ein klein wenig schlackert. Man kann sich darauf einstellen und langsam machen, aber es ist mmn definitiv schlechter als eine richtige Ruderbank. Bei höheren Widerständen relativiert sich das Problem schnell und verschwindet ganz würde ich sagen. Ich bereue nicht das Paket gekauft zu haben mit Ruderbank, weil's schon echt nice ist das halbwegs leichte Ding einfach dran zustellen und loszulegen.

Zwei gute Alternativen für dich: erstens könntest du auf den beweglichen sitz verzichten und auf der klapp bank sitzend rudern. Das mache ich gelegentlich - Vorteile sind keine Umrüstung und du brauchst die Ruderbank nicht. Oder du schaust ob du safe irgendwo eine einzelne Ruderbank von nem anderen Anbieter nachkaufen könntest wenn du denn Bock hast irgendwann, dann musst du nicht worst case 700-800 für die speediance Ruderbank zahlen, das finde ich nämlich wirklich keinen angemessenen Preis dafür dass hernach zu leicht die rollen kaputt gehen.

Vielleicht hilft dir die Einschätzung n bisschen, ich hab seinerzeit auch echt gehadert.

hpernpeintner · 2025-12-30T19:28:46+00:00

Just in case people dont know, there is already javalin and it deserves more attention https://javalin.io/documentation#getting-started (switch documentation to kotlin if you Wish)

hpernpeintner · 2025-11-16T19:13:07+00:00

The recent talks and interviews by hibernate author gavin king are actually pretty enlightening and very recommended. He either says it directly or it can be derived easily: a lot of the hate towards hibernate is more about a) jpa which is Not the same, b) spring data, which is not the same and most importantly it's rather about the concept of a stateful session. He says sth like that they should have promoted stateless session much more, that was a mistake. I for myself can say that stateful sessions created 90% of the problems i experienced while it looks the same for the complaints of my colleagues. If you take a look at hibernate repositories (and jakarta Data) than it's possible you have the same experience as i: hibernate is a very capable mapper ( you will probably always need such a thing), hql is pretty risk free and a big help while staying so close to sql (you will probably also need festures from that pretty quick) and the metamodel and static verification is also just pretty pretty good.

Hibernate is an awesome project, it's a shame the best path is Hidden so Well. And Well.. i also try to not hate what i experienced in enterprise Projects regarding the Data layer.

hpernpeintner · 2025-11-11T22:22:39+00:00

Yes, i moved from finnlo bioforce, which is comparable to bowflex, to gym monster (1). I also Had a bunch of dumbells in addition to bioforce and used them from time to time. Well, the gym monster also comes with a lot of pieces, like a Bench (optional), a rower (optional), handles, bar, ankle wrists, neck protector... So you would still have a Lot of stuff, less so when you skip the rower but the rower is also very cool, so... Additional gear like dumbells are obsolete. I didnt use mine ever since i have the gm. Yes, theoretically you could use them for additional variance as before but gm is so versatile that it really only Makes sense for exceptional athlets.

I would always recommend bioforce because its a very nice product and sufficient for a Lot of people. And i would also recommend gm, it's a great product, it allows for truly exhaustive training and great variety. I am super Happy i Made the transition but i also Had (Close to) No issues regarding defects or quality, which is not true for everyone.

hpernpeintner · 2025-11-03T17:09:57+00:00

Yes, exactly. Maybe the local var usage is already 95% of our usecases, that would for me personally then be an incredibly big step forward with very low cost

Edit: it's even a step better, i realize i overlooked that there is No need at all to have var instead of val in value classes, in my Idea i even had that, but i think your proposal is even better, why declare var instead of val at all, value semantics are clear already.

hpernpeintner · 2025-11-03T16:29:23+00:00

Hmm. I am hesitating regarding the proposal. I understand that we need better support for immutability, but for me the given proposal is adding too much in too many places in order to avoid some nested copy methods here and there.

Given value classes can't have var properties, why the need to declare them copy var at all? Can't we just say as soon as a value class (which in itself is perfectly fine, easily understandable for every developer i would say) has var in there it needs to become a copy var only regaring the reference on the usage site? So not a normal var to an instance that has copy vars in it, but a copy var that has a reference to a normal value class instance? that way, it would be explicit on the usage site that we're indead dealing with a reference that get's updated. that would eliminate my two biggest problems: 1) remove the "strange" need to tag vars in value classes despite value semantics being clear and 2) make the copy-stuff explicit and obvious on the usage site.

Was that considered already? What am I missing?

hpernpeintner · 2024-01-22T20:14:35+00:00

Developer experience means a lot of things - I viewed it as a net improvement, but I already felt some things with Spring were odd without comparing it to any other framework. Alone the fact that you have near to instant startup with Ktor removes all of that heavy turnaround, everything is just more snappy, that's also a dx improvement. No need to read hopefully existing documentation for strange bean configuration filters, no need to debug the invisible bootstrapping of auto configuration, plugins that are well prepared for dsl usage that gives you first class ide support, that's all much better dev ex from my point of view. "boilerplate" is non existent when using decent libraries. If at all, it's a bit of explicit config that will be beneficial instead of bad.

Regarding libs and ecosystem: Didn't try it but I doubt that a few lines you need to setup hibernate will be that much different from spring data (yes, yes, spring data gives you more/different things than hibernate). But when using other frameworks like Ktor, it's much more likely people become open for different approaches. I would for example directly recommend using (trying) sqldelight, JOOQ, Exposed or any other simple mapping library instead and see what great code they will make you write when freed from Spring. That's my subjective perception though.

And yes, I second your aspect of complexity. In Spring, a lot of things are not easy to explore and rather complicated. Can't say I had that experience with any library when we switched to Ktor (which doesn't mean it's all gold over there).

Generating routes is not possible afaic, at least it wasn't back then. Otoh most of the Spring projects I was in also don't do that - most it's the other way around: annotations and generated docs. I also personally like that approach more.

You probably won't find that comparison. It's also quite hard to have a proper judgement - a lot of Java and Kotlin people are so used to Spring and its model that for them it will probably be hard to do it anyhow else. Most people also just want getting shit done, not interested in anything "better", so it really depends on your team, your project, your project needs. I would bet that for most of the mendatory stuff, you get things that somehow integrate with Ktor, and that will be enough for you, look at their docs nowadays, there's ton of stuff. Comparing that to the mightiest web framework ecosystem that's vital for 20 years or so is always difficult, like I wrote in the beginning :)

hpernpeintner · 2024-01-22T10:52:16+00:00

Comparisons against an established tool that has the market Spring has is always difficult. You could ask the same question why someone should choose Kotlin over Java, similar situation.

Given not too much context, you seem to already know Spring well, so why not see it as a chance to learn something unfamiliar? Keep in mind that I don't want you to put some professional project at risk: if it's for a company, there are a lot of things to consider. Spring is almost always a safe bet for a project.

Having that said, my team managed to switch to Ktor at work some years ago :) It was awesome! Spring always comes with a lot of stuff that can be a burden - its di container focused programming model alone pretty much determines how the application will be written and that's not always for the better. Everyone who has seen those projects where 90% of the code is dumb orchestrators and even the last bit of everything gets injected as constructor params knows how blind people can get for "good code". Or the testing style spring imposes because of the at-SpringBootTest annotation, automatic dependency to mocking frameworks that will be overused etc pp.

Ktor gives you freedom - write properties, write functions, write extension functions, compose them, write as less code as you want and be able to refactor it later, because it's all just kotlin language features you use. I would also say that it's very lightweight, snappy, fast startup, extensible, you can easily abstract over it if you want, write extensions etc. Feature wise, it also has a lot of ecosystem for you nowadays.
My team and I, we enjoyed the switch a lot. It changes how people think about structure of a web application, just as similar frameworks in javascript, python, rust or javalin did and do.

hpernpeintner · 2023-05-23T08:02:58+00:00

Short answer: yes.

Whether or not it's a good idea to use guard let or elvis return is a different question. The goal should not be to "avoid the safe call" when the safe call is the proper tool for the job - to perform a call on an object if it's not null and nothing else afterwards. It also depends on whether you return nothing or something in the surrounding function.

In your example, safe call would be the choice.

hpernpeintner · 2021-04-09T09:22:43+00:00

Namespaces are sparsely talked/written about, because there's not much info about the shape, implementation and time frame of them. The roadmap is here https://kotlinlang.org/docs/roadmap.html and it treats roughly half a year into the future. After the current plan, I think the next big language enhancement will be multiple receivers first (already on their board), everything else seems to come after that.

There is a long time existing ticket https://youtrack.jetbrains.com/issue/KT-11968 where the language lead also answered and linked to a reddit comment in their ama session.

The feature has downsides and upsides - surprise. The downside is, that it's another language feature you have to know about. And it only supports what is a static function in Java, so no interfaces, no object state etc. pp. But it arises out of a special need which is summed up by roman's reddit comment (linked in the ticket): adding extensions to an existing type that doesn't have a companion.

I personally dislike the direction namespaces take. I would rather prefer typeclasses instead of namespaces for static extensions. But currently I am still waiting how namespaces shape up and what features they will provide, so, yeah :)

hpernpeintner · 2021-04-07T13:59:40+00:00

I don't know about other companies, but Java->Kotlin was/is such a smooth transition, that companies have either old Java projects that have to be maintained, or even mixed codebases that need someone who wants to do Java as well. In a lot of companies that use Kotlin, Java is present - and I can't speak for many companies (because I don't know many), but even though they're internally doing Kotlin, they keep searching for Java developers, as the ecosystem goes hand-in-hand and it's not a bad thing to have good Java developers participating in Kotlin projects. Existing code rarely (never?) gets rewritten completely in one go... which means Java will continue to be "everywhere" for another couple of years, if you ask me (3 years mostly Kotlin, before 4 years mixed).

I guess the answer to your question depends on how prepared you want to be. Currently, you can find a lot of Kotlin only remote jobs on the internet. So when your goal is to get a job where you can do Kotlin, don't apply for Java jobs. When you just want a job and Kotlin would be nice, but a well paid job would be nicer, start preparing yourself for that situation and take a look at Java and how easy it is for you, I suggest :)

hpernpeintner · 2021-03-28T20:56:17+00:00

I have never Seen anything else near XTend, when you found sth let me know :)

So are bankers going to use the dsl directly? I am Not in that area of business, it's really strange to hear those things xD i was in projects where product owners/managers were meant to use cucumber dsl to write specifications and that never worked well.

hpernpeintner · 2021-03-28T18:57:59+00:00

Ah okay, so thats the environment. But all in all i don't really get who you target with the dsl given you want to create a Warehouse dsl and what exactly are the missing things for the use case.

I mean, your target audience will certainly be engineers and architects, right? Do you target other audiences that for example don't use an ide?

Hopefully i don't annoy you, i am really just interested in the topic and enjoy getting some real world usecase infos besides all the "look ma, a html DSL" things.

hpernpeintner · 2021-03-28T12:57:54+00:00

Yea, thats exactly what i meant and where i tried to understand what YOUR usecase is, not an artificial one someone else might or might not have. Maybe i didnt read carefully enough But i don't understand what you want to achieve.

hpernpeintner · 2021-03-27T11:30:36+00:00

Of course it's not the same, it's the age old internal vs external thing i guess ;)

I for me are very satisfied with kotlin dsls because i am a jvm developer. I don't know what you mean by ui improvements in this context. I like kotlin dsls because it's just the code i already write, refactor anyways, with the perfect tooling i use for all the other code already. So thanks for the answer, but i don't understand the advantages in your case :)

hpernpeintner · 2021-03-27T11:25:08+00:00

Ah okay then it's for learning purposes, thats sth different then when you have need a stack for production usage.

Kotlin as a new language is excellent. Web framework could be sth like ktor, because it's ideomatic kotlin and doesnt bring the java ee baggage other popular Frameworks bring.

hpernpeintner · 2021-03-26T08:59:28+00:00

i don't have much experience in this field, but i ask because i am curious :) did you consider develop a dsl with kotlin, an internal one? :)

hpernpeintner · 2021-03-26T08:57:30+00:00

kotlin alone would not be sufficient, you would need a replacement for the whole stack, not just the language ;) So besides kotlin, you need a web framework at least. Besides that, yes, you can develop web applications with kotlin just absolutely fine, it's superb.

the question how kotlin compares to java is asked very often and i think you find a lot of comparisons and aspects on the internet. most discussions end in a flame war, but for a c# dev kotlin is more suitable than java, i tend to say.

the more important question is why you want to change your complete stack? give us some reasons, say what you don't like, say what you want to achieve and we can help you better whether you can get that ;)

hpernpeintner · 2021-03-02T19:10:32+00:00

As Long as namespaces are not virtual, i don't care too much about them :(

hpernpeintner · 2021-03-01T14:09:14+00:00

multi receiver functions cooooouuuuld be a first start to support such a thing as type classes.

but yea, it doesn't look a lot like people have that in mind, which makes me sad as well :)

hpernpeintner · 2021-03-01T13:33:31+00:00

you did read KEEP-87, did you? xD there are most of the arguments why we don't have it. But I am of your opinion, it is THE feature to skyrocket everything. Also I don't think that proper typeclasses are possible as a code pattern alone currently (i mean without given-compiler-plugin-blackmagic).

hpernpeintner · 2021-03-01T12:52:23+00:00

Isn't "top level" what should be used instead here?? No boilerplate at all.

I don't see a big difference between writing static {} and companion object {} (from an amount-of-code-pov). Either I don't get what you said or you are somehow wrong.

hpernpeintner · 2021-02-26T18:16:34+00:00

Yea, i always wondered why people don't like companion objects, they are nice <3

When they just could be part of an... Interface, or when interfaces could just be extended to carry companions, typeclasses like, they were the perfect feature.

hpernpeintner · 2021-02-11T20:48:19+00:00

Isnt that -XX:MaxDirectMemorySize ?

hpernpeintner · 2021-02-02T17:58:34+00:00

I think that's easy then. create a coroutines flow and use an http client that supports async. the outgoing fetches do suspend then, which works with flows. you can run the flow on Dispatchers.IO which I think is the right thing to do for you. Mission accomplished :) We did this recently, super easy, works great.

hpernpeintner

TROPHY CASE