Aside from the usual separation of tech stacks for different teams, the big thing for me is lack of any sort of type hinting or safety in templates at least in the big frameworks such as Django, Rails etc. I would much rather work with a separate build process that utilizes typescript than deal with the errors that come out of incorrectly reading formless data and making typos within templates.

Is that really such a big problem? These days you can type annotate what you pass to the rendering function for templates and then you know what type you have in the template. If you have a minimum of testing, heck even manual testing will do, I don't think too many mistakes make it to staging, let alone production. I would think it well worth to be able to opt out of the JS ecosystem.

Are you saying it is "explicit" in that it is explicitly stating itself as such or that it contains explicit content? Because the former is honest and the latter seems to be untrue. Also you are replying to every comment here calling the author of the article a "disgusting pervert" and accusing them of a lot of things and I'm not sure it's adding anything to the conversation. It's a harmless journalling app

Sure it's harmless, but I think the app has enough suggestive content to be "explicit." There is a section where you can track your toy performance with options including ropes and vibrators.

It is a tracker of sexual activity.

It has no other purpose.

It ain't livejournal, my man

I don't know what this comment means. I know this. Are you ok?

I don't know for sure but they have to be counting users like me whose phone has had Gemini force installed on an update and I've only opened the app by accident while trying to figure out how to invoke the old actually useful Assistant app

Having actually used Audacity, the modes were horrid and not at all intuitive to use and everything demonstrated in the video only looked like vast improvements (aside from the logo). I am failing to see how adding handles wastes space that could be used for any extra information especially when the tradeoff is an incredible degree of customisation for my UI. In terms of precision, they're working on accessibility issues but I'm not sure how this change is any special than any other UI.

> I am failing to see how adding handles wastes space that could be used for any extra information

What is there to see? You add a bar that takes space. That space can be taken up by something useful. Just like you have apps that hide app title bar and app menus so you can have more space for your precious content. This is especially useful for high-info-density apps like these audio/video/photo authoring ones. Note how tiny those handles are in the video, why do you think that is?

> tradeoff is an incredible degree of customisation

You don't have that tradeoff, neither of the 2 solutions are anywhere close to "incredible customization", so you can pick either without it.

> In terms of precision, they're working on accessibility issues

Working towards what magic solution?

> but I'm not sure how this change is any special than any other UI.

why does it have to be special? Just a bog standard degradation common to any UI (re)design, nothing special about it.

> the modes were horrid

Of course they were. Just like they were horrid in that MS Paint app the dev worked on before. But you can make any UI primitive horrid, even buttons, that's no reason to remove them, but to improve them!

> Pipenv is just straightforward and “just works”

I have worked on numerous projects that started with pipenv and it has never "just works" ever. Either there's some trivial dependency conflict that it can't resolve or it's slow as molasses or something or the other. pipenv has been horrible to use. I started switching projects to pip-tools and now I recommend using uv

I do not want to work with all the untyped strings and random class selectors. I'd say the code is easy enough to read but nigh on unmaintainable.

Because on my Android phone, the alarm accepts a date and rings only on that date

Got a ton of pushback for talking about how buggy the OS has been. "it doesn't happen to me" all right bully for you now I have to helplessly send a bug report and live with a machine that just crashes and restarts if I dare to open the lid seconds after I closed it

There is no connection between whether an app is native or electron based and its UX so not sure why you'd bring this up. There's enough and more native apps with horrible UX and plenty of electron apps with excellent UX.

Happened to my father who got routed through ads on his phone while booking flight tickets to some seedy website. He regretted it but thankfully got refunds initiated successfully because of issues with the flights themselves and a lot of back-and-forth. He resolved to only do critical monetary operations on his laptop where I've installed any and every possible adblocker.

The web is so hostile to the inform and the old. It takes one moment of weakness and there's someone ready and waiting with a scam.