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.
Here's yesterday's talk "Creative Coding in #OPENRNDR" at the #Kotlin Conf 2024. The first half show work by Edwin (principal developer of the framework) and the RNDR team.
The second part, starting at 6:32:25 (25 min. long), live codes a poster with two graphic layers and one with text.
I really like #kotlin's (and others') approach to nullability, where nothing is nullable by default and you mark something as nullable by adding '?' to the type. And the '?.' syntax is nice too. 'foo: Foo? = ...; foo?.doThing()' is nicer than 'foo: Optional<Foo> = ...; foo.map(|it| it.doThing())', and both are miles better than "everything is always implicitly nullable unless annotated with '@NotNull' #plt
:amaze: If you are looking for an awesome 2FA application for Android and iOS, 2FAS is fucking gorgeous.
Simple, efficient, smooth, great UI, nice UX, and also #opensource under libre license GPL 3.0!
The project is hosted in GitHub, written in #Kotlin for #Android and #Swift for #iOS, pure native tech 💪
Hab ein bisschen weiter an der Kugelbahn gebastelt und etwas Schnickschnack eingebaut. Es gibt Schalter, die beim Überrollen Barrieren öffnen und einige Bahnelemente sind jetzt festgeschraubt, so dass sie sich nicht mehr verschieben lassen.
Ich überlege mir jetzt noch etwas mehr Schnickschnack 😀
Leider ruckelt es etwas im Android Emulator, aber auf dem Handy selber läuft alles total flüssig.
I can't deal with languages with optional semicolons! I like languages without semicolons, but when they're optional, especially if they feel "C-like", I always end up adding semicolons to some lines even when I try to write in a semicolon-less style. I'm writing some #kotlin now and I decided to just use semicolons consistently because the alternative is seemingly to use them inconsistently.
Strangely, this isn't an issue I have in #golang. I do have it in #rust however.
Annotated strings in kotlin with ParagraphStyles or SpanStyles work great for simple forms of MFM (Misskey-Flavored Markdown), but the more complicated they get, the more I'm starting to think I need to look for a better option. Like, what the hell do I do for a blockquote? Or better yet, what the hell do I do for the animated ones? I'm getting really frustrated. If anyone better at Kotlin / Android development has any suggestions for me, please let me know because I am running out of ideas. #AndroidDev#kotlin#JetpackCompose
Async/await in #TypeScript is essentially “direct style”. It will be interesting to see if Effect, a monadic effect system, will take off, as a case study for #Kotlin & #Scala — although for “direct style”, these have the advantage of context parameters.
Curious to know how other #android (or #kotlin) libraries handle Android process death. Or do they?
I have an SDK that requires a suspended initialisation before being allowed to access other functions for that library. This is because a data set needs to be loaded. On process death the usual initialisation seems to be skipped causing users of my SDK issues.
I'm convinced this isn't something the SDK should be aware of but want to cover all bases thoroughly.
I'm very happy that I figured out how to place the icons in columns (responsive) and the names under the thumbnails. I find aligning things in Swing even harder than in CSS.
In case you want to try an alternative JSON (de)serialization library for #Kotlin, Kondor https://github.com/uberto/kondor-json by @ramtop is great. No annotation magic, just functions explicitly defining the mapping. No external dependencies. As fast as Jackson.