I meant doesn’t change with respect to time zones. Leap times are still relevant in that scenario as each solar rotation doesn’t divide into a whole number of days and leap seconds due to variance in rotation.

With respect to the meridian I envision it rotating around the earth once per year, hence sidereal. So 0000 would rotate around the earth through the course of the year. Each day it would be one degree farther.

Most likely is I’m just completely full of shit.

My suggestion has always been universal sidereal time. It is singular, doesn’t change, and carries no colonial baggage since it rotates around the whole earth. Even suitable as a home time if we become spacefaring.

Wait, so you’re saying the trip to the national anthropology museum was for work? Maybe.

Would she not be considered a tourist for her trip to Mexico City?

Greg would.

Like with everything, context matters. Sometimes it can indicate poorly structured control flow, other times inefficient loop nesting. But many times it is just somebody’s preference for guard clauses. As long as the intent is clear, there are no efficiency problems, and it is possible to reach the fewest branches necessary, I see no issues.

That isn’t the issue here. I agree with you, but in this case the filter is on Reddit’s side. It is common and justifiable for corporate machines to use a vpn. Sometimes public traffic doesn’t go through, but not always.

Alternative proposal: While your net worth exceeds some function of GDP, laws do not protect you. Find a way to offload those stocks, or keep your head on a swivel.

It runs in browsers. It… isn’t poop? I don’t know. I’m all out of ideas.

!sudo shutdown -r now. Or just :x or ZZ, but I guess those don’t fit the motif of this very tired silly joke.

This happens to me more than I care to admit. I told a coworker about a Gitlab CI issue that I’d seen a few years back and hadn’t had any action. I looked up the link to share it. Me; I opened it. Brain failing me, I had forgotten it was my issue.

I guess I’m just lucky, but I’ve gotten nothing but thoughtful support on Arch forums and Stackoverflow. If you read the article How do I ask a good question?, it works very well. It seems harsh but coming with poorly thought out questions without debugging details makes it impossible to help.

PascalCase

I’ve seen this before but don’t accept it myself. There are cases where you just wanted to cat. In this case, maybe to review the problem. Then you want to extend the command. Preserving it in the next commands where you start stacking on pipes is useful since it can be fewer strokes and maintain a habit.

Exited? Or were you just a youngin at the time?

I don’t disagree. I’m just saying the distribution of workload has an impact on what looks a good idea or too hard.

Fair.

Because it changes the risk benefit profile of the choice. Imagine that your backend is 70k hours of work and your interface is 1k hours. Managing two interfaces isn’t going to seem like nearly as big an ask so other variables may get a higher weight. Of course those numbers are contrived for the sake of explanation, but if you still don’t think there are any circumstances in which others may value the benefits of native applications over cross platform applications, that’s fine. My point is simply that it may not seem like the trouble of managing two frontends is as insurmountable as you may think.

But I have a hard time believing you don’t think it is possible that there are any situations where one might reasonably believe it worth it.

Sure. Bitwarden provides its own backend. So that backend represents some portion of their code base. In the case of Voyager, Lemmy provides the backend. So that backend isn’t a portion of your code. So Voyager is 100% frontend. Bitwarden is < 100% frontend.

Recognizing you as a PWA developer; and a damn fine one, I get your take. But surely you are aware there are limitations to using PWA’s or other cross platform libraries. Sometimes maintaining multiple UI’s is the right choice. Especially if very little of your code is actually the front end. For you, Voyager is pretty much 100% front end, so that’s 100% of your code. But for Bitwarden, the interface is a much smaller proportion.