lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

66
active users

#Kotlin

0 posts0 participants0 posts today
do you know vue, quarkus, and/or kotlin? want to work with a weird trans girl on a project? i wanna collab with folks on making a feature-rich self-hostable feed reader! I have a basic prototype rn and I'm wondering if anyone wants to collaborate?

#vue #quarkus #kotlin

(pls don't make fun of my code lol i'm still learning but i think i'm picking stuff up fast)

Over five years now I'm programming on the JVM. Started out with #Java, moved to #Kotlin as my daily driver, dipped my toes into #Scala and once in a while enjoy experimenting with #Clojure. Groovy outside of gradle files, is still a gap to fill.

I had the urge to go behind the language and explore the realms of bytecode, linking and loading and JIT compilation and the helpful people on the RockTheJVM discord recommend me this amazing book: "The well Grounded Java Developer" which goes into this step by step.

It let me appreciate what an outstanding piece of software the JVM really is.

manning.com/books/the-well-gro

Manning PublicationsThe Well-Grounded Java Developer, Second EditionUnderstanding Java from the JVM up gives you a foundation to grow your expertise and take on advanced techniques for performance, concurrency, containerization, and more.

tl,dr: imho beginners should start with with either Go or Lua

Friends hit me with the age old question for their child which wants to learn programming: which language should one start with?

This had me thinking quite a bit. First thing that came to my mind was #Kotlin, my favourite, but I wouldn't recommend it for beginners, because it is quite heavy in high level concepts.

To get results quickly the obvious choice would be a dynamic language like #Python or #Lua. The later being embedded in many games.

On the other hand, to get a good understanding of data structures a strongly typed language would arguably be better. #Java wouldn't be bad for this because its verboseness makes these things visible at all times. But since I tipped my toes into #Go, I think this has actually the best balance between ease of use, use cases and teaching important concepts.

Anyway, maybe I'm missing an important point here. What would you recommend for beginners?

🚨 We've extended the deadline to Sunday, May 18th at 11:59 PM EST! 🚨

We’re seeking an experienced developer passionate about open-source, technical leadership, and community-driven development. The Processing Project Lead will manage software maintenance, the roadmap, documentation, and contributor support.

Read more and apply at: processingfoundation.org/emplo

Full-time, fully-remote, $95K

Wait, when you do

class Foo () {
val foo: Int

init { ... }

val bar: Int
}

in #Kotlin, it initializes foo, before it runs init, but bar doesn't get initialized until after ???

Who the heck thought that was a good idea?!

UPDATE: Aha! I guess I didn't realize there are "init blocks" in Kotlin, and thought they're the same as “init methods” in other languages, but you can have multiple init blocks, and there are separate "constructors" in Kotlin.

Is Node.js the future of backend development, or just a beautifully wrapped grenade?

Lately, I see more and more backend systems, yes, even monoliths, built entirely in Node.js, sometimes with server-side rendering layered on top. These are not toy projects. These are services touching sensitive PII data, sometimes in regulated industries.

When I first used Node.js years ago, I remember:
• Security concepts were… let’s say aspirational.
• Licensing hell due to questionable npm dependencies.
• Tests were flaky, with mocking turning into dark rituals.
• Behavior of libraries changed weekly like socks, but more dangerous.
• Internet required to run a “local” build. How comforting.

Even with TypeScript, it all melts back into JavaScript at runtime, a language so flexible it can hang itself.

Sure, SSR and monoliths can simplify architecture. But they also widen the attack surface, especially when:
• The backend is non-compiled.
• Every endpoint is a potential open door.
• The system needs Node + a fleet of dependencies + a container + prayer just to run.

Compare that to a compiled, stateless binary that:
• Runs in a scratch container.
• Requires zero runtime dependencies.
• Has encryption at rest, in transit, and ideally per-user.
• Can be observed, scaled, audited, stateless and destroyed with precision.

I’ve shipped frontends that are static, CDN-delivered, secure by design, and light enough to fit on a floppy disk. By running them with Node, I’m loading gigabytes of unknown tooling to render “Hello, user”.

So I wonder:
Is this the future? Or am I just… old?

Are we replacing mature, scalable architectures with serverless spaghetti and 12-factor mayhem because “it works on Vercel”?

Tell me how you build secure, observable, compliant systems in Node.js.
Genuinely curious.
Mildly terrified and maybe old.