And now the IntelliJ plugin isn’t included in the all products pack for some reason.

Edit: It looks like it actually is included, or is supposed to be.

The website is state of the art for 2015 ± 15 years.

The omission of Swift here tells you all you need to know I think.

Edit: I misread this, but my point stands regarding Swift, it has a pretty big usage-reputation gap.

What is your goal? Custom stuff isn’t too hard if you just want to implement basic password login and token-based auth. Otherwise you could use something like Firebase, Okta, or Cognito.

What about ftp? 🤔

Yesterday, for capturing URLs.

Look the issues with java.util.UUID and Postgres.

I found the if-blocks more concerning than the lack of parentheses. Although I would’ve preferred parentheses for better parity with Kotlin for the if-else blocks (instead of then).

“Okay Todd, looks like Steve is working on auth, so you’ll be on the blacklist today-… ahah I mean, working on the blacklist today ahem…”

Not all heat can be converted to work by the second law of thermodynamics. Now the question is, how hot can the star be for it to sustain life? Can most of its light be UV with very little visible? https://courses.lumenlearning.com/suny-physics/chapter/15-4-carnots-perfect-heat-engine-the-second-law-of-thermodynamics-restated/

What I mean to say is that Google isn’t invested in native android either. It’s been repeatedly strip mined by first-timers looking for a quick promotion and left to burn.

Things got so bad that Google gave up on native Views and created Jetpack Compose, which has been a source of many complaints related to performance.

In 2024 Flutter has instant hot-reload, and the “native” (but 100% bundled) solution still requires a complete reinstall on the device. In fact, Dart can compile to native code (or JIT) without an issue, yet Kotlin Native is barely in GA in the new compiler support has been lagging while the new compiler isn’t out of beta and is still poorly supported by tooling.

Consider the absurdity: React Native is the only true native framework out of RN, Jetpack Compose, and Flutter. And all of this barely scratches the surface of the tooling problems that Flutter 99% avoids by allowing development on desktop, web or iOS simulator.

I won’t be recommending that anyone use Dart or Flutter on new projects.

You seem to think Google cares at all. Android has been languishing and Flutter is lightyears ahead. KMP is junk compared to what Flutter has accomplished with a fraction of the bells and whistles.

I just hate reading it. I wish it looked more like Kotlin and less like JavaScript 😭

As someone who switched from another domain to tech, I suggest trying to reason through your hesitation to switch away. Do you want to stay in tech because you like tech or because you’re afraid of “giving up”?

In my other domain, I worked hard and did OK, but not stellar. In tech however, it’s a completely different story. The other domain was “cool”, and I don’t regret what I learned along the way, but tech clearly comes easier to me compared to someone doing well in the other domain.

You need to be honest with yourself before you make the decision to switch. Are you running away from tech or towards something else?

I recall snapshots not being quite as cheap as on ZFS.

Wow this is awful on mobile lol

How do you feel about Kotlin?

Here’s a simple approach:

• Basic auth via a custom header, like X-Auth
• JWT auth on Authorization header
• uuid on the JWT (as a claim) that gets stored temporarily (until it expires) to allow the server to revoke the token

Initial request -> server looks for Authorization header, falls back to X-Auth header -> generates JWT and sends back to client in Authorization header (or whatever makes sense)

Subsequent request -> server looks for Authorization header -> checks JWT against revocation database/table and that it isn’t expired

Subsequent request with expired token -> server returns 401, client retries using X-Auth header -> server sends back JWT on Authorization header -> client updates locally-stored JWT for future requests

There are probably ways to make this more standard or optimal, but this is a simple approach.

I worked on a team that did, and it was the second-worst application I’ve ever touched.

How do you feel about line breaks?