I charge my s25 to 80%. Previous phone (pixel) was also limited to 80%, but radio stopped working after 2 years so I had to buy a new phone.

Same for my s24, 80% battery limit and slow charging at night (most of my charging). It's been over 2 years and the battery seems to last just as long as day one

In both cases I get https://example.com/ in FF.

I think they are saying passwords are salted and we use multiple rounds of hashing to prevent rainbow tables and slow down brute-forcing the password (in case of db leak). We don't need to do that for randomized long strings (like api keys), no one is guessing 32 character random string, so no salt is needed and we don't need multiple rounds of hashing.

OHHH that makes sense!

I added custom captcha (simple math as slightly distorted pictures with audio alternative) on one of my forms, it prevents ~80% of spam submissions. less than 1% of spam passes, other ~20% are blocked on key words (like "sex", "passion", etc...).

Not sure why you’re telling me that. I’m not criticising CAPTCHA, my parent comment was.

I am just confirming that CAPTCHA still works against most basic bots.

It's interesting, couple of things you can fix/change:

1. It's annoying to be asked to provide username every time I complete a level. Can you simply remember my previous choice? Instead something like next level button would be my preference.

2. Tab works until it stops working, it will switch between game elements and then at one point it will focus on buttons (firefox, windows).

1. interesting, I already have something in place for this, it should auto submit after the first time, storing an anonymous userId in cookies. might have been too lax on the browser testing. 2. tab is not a first-class citizen, so your milage may wary :)

So is local stack dead? Is this situation the lesser evil? Or is it not dead and we will see a villain rise?

Edit: I see now, they have commercial offerings: https://www.localstack.cloud/pricing

I am not sure if my corp will be willing to pay or tell us to find something else, but I use it everyday, our integration tests depend on local stack.

IMO, the trajectory was set back when they removed the option for monthly payments. Minimum US$450 to play made it a non-starter for my projects (even with commercial ambitions). They changed this just as I started to integrate (~2024, I think) so I kept to the free capabilities. Have been waiting for the other show to drop and here we are.

Edit: looks like they’ve reintroduced monthly billing within the last few months. I guess that’s a sort of win, even if not for the OSS community. But I’d still be reluctant to get into bed with them at this stage.

> If Photoshop ran in the cloud

Off topic, but there is something like that: photopea, it's free and it's good enough for my use cases (I need it once a year maybe).

It's served from the cloud but it runs entirely on your PC (except the AI generative tools). It can't run entirely offline though, because the js, webassembly, and assets are served chunked as-needed.

Saying Photopea is good enough is really underselling it. It's so far ahead of anything offered by the open-source community.

I'd be so happy to pay for a fully offline version of Photopea!

> The goal of specs is largely to maintain desired functionality over many iterations, something that pure code handles poorly.

IMHO this could be achieved with large set of tests, but the problem is if you prompt an agent to fix tests, you can't be sure it won't "fix the test". Or implement something just to make the test pass without looking at a larger picture.

I find myself babysitting agent-derived tests unless I specifically say what the in variants and edge cases are. Sometimes I'll ask it if I missed anything and it'll be helpful. But I have to be proactive.

After ~13 years of working with C#, I moved to Kotlin. It's such a beautiful language. When I have to read docs for a Java lib I realize why I like Kotlin.

I want to say culture around Java doesn't have to change, new culture is growing around succinctness (if not simplicity) of Kotlin, and it gets most of the benefits of Java ecosystem.

I also like Kotlin. The readability is awesome. ;)

  inline fun <reified T> Any?.cryptic() = (this as? T)?.let { it::class.simpleName?.also(::println) } ?: Unit

I get the snark, but also - there is this "ideal Java code style" that most experienced devs tend towards. Unfortunately I don't see anything like that for Kotlin (yet?), and there are a bunch of patterns that I really dislike. I sometimes feel people just toy around, like "wow I can make this into an extension method, how cool" and leave that as the code.

In general, I really dislike extension methods, especially when paired with tiny objects with barely any functionality to begin with. Like people build a mental model of what a thing is based on how can it be used - but if you leave that empty and put every behavior at different files in the form of extension methods you make this understanding very hard to build up.

Add to it that it removes polymorphism and often actually hinders readability.. so my point is, having more ways to write code is not necessarily a positive.

I must say I prefer C# over Java. They're pretty similar in a lot of ways, but LINQ is much nicer to use than the Java streaming equivalents. And there are some odd warts like Java lacking unsigned types.