fuzzy2

It’s really not that bad. However, with a standard NixOS setup, you still have a tremendous amount of non-reproducible state, both inside user accounts and in the system. I’m running a “Erase your darlings” setup, it mostly gets rid of non-reproducible state outside my user account. It’s a bit of a pain, but then what isn’t on NixOS.

https://grahamc.com/blog/erase-your-darlings/

Inside my user account, I don’t bother. I don’t like Home Manager.

Oh wow, I never noticed. It appears I’m running a ~1 year old version (2023.4.0) that just stopped auto-updating. It doesn’t have any restrictions and doesn’t require an account.

Just curious, what’s your gripe with Insomnia? I find its UX a little clunky at times but haven’t found anything limiting my use cases.

To put it simply: Postman is for everything but what curl is for. Sure it also performs the actual request somewhere under the hood but that’s mostly irrelevant. Having a single integrated user interface (it could also be a text UI) to craft a request, sometimes sending JSON, sometimes a file, then sending it to inspect the result, then modifying the request then doing it again is very powerful. Not to mention OAuth/OIDC support and the like.

Sometimes, you have to find out how an API works, exactly. Sometimes you want to test your own APIs in ways the regular clients do not allow.

I’d say—yes, very much so. Pointer movement is damn near perfect now on the Dell Precision I have at work. Clicking unfortunately not so much, but it’s mostly bearable.

Also, at 15×9 cm, it has over 5 times the area of the teensy trackpad on my old ThinkPad R61, which is just 5.5×4.8 cm.

Thank you taking the time to answer. Dagger looks cool, maybe I'll get the chance to use it in the future.

This form factor is already well-established, though 300 km/h is still very fast.

Actually, it is the only (display) protocol. HMDI Alt Mode, while specified, never really manifested and is effectively dead. DisplayPort is the only alternative and is more flexible anyway.

Its packet-based nature is not relevant for DisplayPort Alt Mode, by the way, because it gets dedicated pins. Sometimes enough for two lanes, sometimes enough for four. It's hilariously consumer-unfriendly. Only Thunderbolt leverages the packet stuff and can transport up to eight lanes worth of DisplayPort.

macOS does not support MST.

Who is supposed to get this? I don't know.

I think grandparent’s concerns were not with using Docker in general but instead with how the Testcontainers library orchestrates it. I assume there’s an alternate approach behind the critique, and that’s what I’m interested in.

I'm interested to hear what you would do instead! I'm using Testcontainers in a very basic scenario: A web app with a PostgreSQL database. There are different database backends available (like Sqlite) but I use PostreSQL-specific features.

Currently, in my integration testing project, I use Testcontainers to spin up a PostgreSQL database in Docker and then use that for testing. I can control the database lifecycle from my test code. It works perfectly, both on my local PC and in the CI pipeline. To date it also did not interfere or conflict with other Docker containers I have running locally (like the development database).

From what I gather, that is exactly the use case for Testcontainers. How would you solve this instead? I'm on Windows by the way, the CI pipeline is on Linux.

But they can replace a lot of native apps. Calendar, Notes, Weather, Maps (to an extent), Reminders, Calculator, $CellProviderApp, Stocks, Cloud Drive (Apple, Google, Microsoft, …, to an extent), Translator, Mail, various Messengers, Youtube, Amazon, various public transport ticket apps, EV status apps, parcel tracking apps, …

I’m only on home screen 2 of 5 and oh my, it’s almost all of the apps. Granted, some would perform worse in some ways. Some could not realize all features (like automatic photo upload). More integration (like sharing to PWAs) would be needed. But some others? Yeah. Why even develop an app?

The performance degradation is just my experience from a Galaxy Nexus, a Galaxy Tab 2, a Nexus 5 and most of the older Android phones friends & family have/had. I don't remember from the earlier Android days.

It's entirely possible this is "fixed" nowadays, because flash/UFS technology has progressed and/or device makers are finally using slightly less crappy components.

Not what I was referring to. PWAs are a specific combination of web technologies. They're not "JavaScript apps". They really are web apps, even when "installed".

? My definition of an app-like experience is that it’s not a browser. No address bar, no tabs, no GUI elements whatsoever but the web view. That’s a PWA. Local storage is merely a supporting technology. Push notifications are not required at all.

It’s not that easy. I switched to iPhone mainly because of Android phone makers’ abysmal update policies. Heck, I had a Nexus 5 and it was “killed” merely 1.5 years after I bought it. Because newer Android required newer graphics drivers and Qualcomm said “no”. Supposedly things are better now, but are they really?

My iPhone 7 was my daily driver for 5 years and was only retired because I got an offer that was too good to pass up.

And then there’s also the degrading storage on many Android phones. They just become sooooo slow. My iPhone 7 is slow now, too. After 7 years, not after 3.

The video in the article (https://www.youtube.com/watch?v=AST12aDGf0Q) shows that PWAs are completely gone. They are degraded to pinned bookmarks that open in your default browser. Yes, you can still pin bookmarks, as you always(?) could, but those are not PWAs.

Only PWAs can offer a true app-like experience.

They’re not Javascript apps though. They’re HTML with Javascript over HTTPS, rendered by a browser engine and… oh wait, that’s a website.

I’d like to quickly address the second paragraph. From my experience, iPhones last until their software support runs out, barring any accidents. Furthermore, PWAs need not be offline applications (so TFA overblows the data loss potential ever so slightly) but often work exactly like you want them to.

I use the Outlook PWA. It’s great because I don’t have to let my company manage (part of) my phone.

Except they're two sides of the same coin. The underlying technology (software) is almost all the same. And it is not problem-free, unfortunately.

People will actually revert commits? For real? At work? Where do I get to sign up?

Okay, but again, which documentation is that? Technical or business?

Because I do not see business documentation evolving with code. And depending on what the code does, business documentation could be much more important than technical documentation.

Where would it need to be not to die? Also, what kind of documentation? Technical? Or business?

Maybe! But here's another take: everyone else makes too few phones, nowadays. Exactly one, that is. Well, maybe two, if you count folding phones. After Palm and then HP failed with webOS, it's now all the same.

How come this is the future? It's freaking boring.

I'm sorry to hear you feel that way. I participated in many "offline" workshops and most of them were great. They allow for real debate by offering the full range of human communication.

I never once had the same experience in a remote or hybrid workshop.

And yet technology surrounding remote work has failed us, curious. Bad internet, bad software, bad hardware, the holy trinity of communication enshittification.

I can code anywhere and I can text anywhere just fine. 1:1 calls work more often than not. But boy do I abhor remote workshops. They suck in every way possible, and even in some previously thought impossible!

"My car isn't like that so it can't be a problem", really? Wow

There's dozens of forum apps available, both classical and endlessly scrolling. Discourse is well-known but suffers from extreme feature creep. Flarum, myBB, NodeBB, Vanilla, …

And then there's also closed-source apps.

Will Microsoft sort this out though? Looking at the state of modern software in general, I very much doubt it. Ridiculously complex software tends to have ridiculous bugs.

(Also, these half-baked UI upgrades have been going since Windows XP, not a single coherent concept since then.)

No, that was the Secure Boot scare. TPM is unrelated to that particular matter, though it can interact with Secure Boot (as part of Measured Boot).

Both technologies apply to any operating system and provide important software security benefits.

Somewhat? This voltage isn’t (just) about the battery, but about all power connections. Cables can only take so much current after all! At 150 KW, you need 400 V × 375 A. That is an insane current figure. At 800 V, it’s just half the current.

I’ve used a 300 KW DC charging station once. The cable is very thick and heavy. There are practical limits.