This but make it so only the browser can’t tell time.

Noooo, you don’t understand, we just have to never make this mistake again and then there won’t be anymore regressions!

(run { this@comment.parent?.apply { this.value === true } } == true) ?: if ((this@comment.value as? Boolean) != true true) false else true

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

That’s a lot of work to not use Kotlin…

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.

“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…”

What if the suggestions have warnings like “experimental” or “unstable”?

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

I’ve worked in both android and spring boot and rewriting your security to use a filter chain is nothing* compared to the shenanigans google likes to pull. Keeping up with the deprecations and imaginary “best practices” is half the job. It’s like someone combined the worst parts of react with the worst Java timeline and forced people to write inscutable spaghetti that’s completely impractical/impossible to test.

*there are valid criticisms of spring security, but I think this particular change improved things, even if it felt pointless

I mean unit tests. I work on Spring Boot apps where there are distinct layers (controller -> service -> persistence), and you generally inject mocks into your object to isolate tests to the specific code you want under test. One benefit of this approach is that it’s pretty easy to get 90% coverage.

How do you write tests?

Germany uses a comma, and you can check this by setting your phone to en_DE.