#kotlin#ttrpg
I'm thinking of re-writing my Random Dungeon Creator app.
Does anyone have tips for how to build the code, what data structures to use, etc?
I threw it together in Java, with a combination of database and JSON for the raw data, but feel I can rewrite it better.
Help/direction appreciated
I suppose I should properly introduce myself. I'm haliphax. I like futzing around with #TextMode applications. I've been in "full stack" #WebDev for just over 20 years now and love to write #Python / #TypeScript projects, but my day job involves a lot of #AWS, #microservices, and #Kotlin.
I think I quite like #kotlin (at least, as far as language and tooling… jury’s still out on the larger ecosystem). It sits comfortably in-between #csharp and #fsharp, and without any of the eye-roll-inducing quirks of #rustlang.
Mayhaps I’ll keep with it for a while… maybe I’ll even do a blog post 😮 (but probably not😅).
Guess I should post a new introduction since I moved servers and this account has no posts at all 😛
I'm a developer/coder. I used to be very much into mobile development (both #iOS and #Android) using #Swift and #Kotlin. Now my main area of interest is digital creativity using #AI to generate art, text, and music.
I don't post a lot generally, but do daily postings of interesting papers from the cs.CV category on arXiv.org. So first thing in the morning, there will be a barrage of posts from me and then probably nothing much for the rest of the day 🙂
I also post a daily set of images based on my #StableDiffusion prompt of the day — I generate a bunch of images through the day based on a single prompt, pick the four best images (according to me) and post them the next day.
We have static #programming languages that are both adequate for the server-side and can target the client-side (Javascript, WASM, native, etc), such as #Scala, #Kotlin, #Rust, #FSharp, #Typescript.
The biggest advantage of using the same language is that you can share code, starting with the data models, alongside serialization, and parsing/validation rules. The API can thus be easily kept in sync, and a server-side test is also relevant on the client-side.
I have just learned that "#Java Bean" has two completely different and incompatible definitions.
One is a dumb, badly designed data object with getters and setters.
The other is... a service object managed by the Spring framework IoC container.
Holy hell. This is 10x worse than #Laravel "facades."
Am I wrong here? This is what I'm finding from online tutorials. Is there more nuance that is not coming through, because for now I just hate #Spring even more.
@akop I am so glad about languages like Kotlin which offer non-nullable types. Exactly that will get unnecessary and also survive refactorings. #kotlin