How do you reliably (eg legally-definable) differentiate between "stopped supporting" and "haven't released an update in a while because it works fine and there are no major bugs"?
> Just then, a bandwidth load as heavy as a pregnant elephant sits down on Manfred's head and sends clumps of humongous pixilation flickering across his sensorium: Around the world, five million or so geeks are bouncing on his home site, a digital flash crowd alerted by a posting from the other side of the bar. Manfred winces. "I really came here to talk about the economic exploitation of space travel, but I've just been slashdotted. Mind if I just sit and drink until it wears off?"
I'd say Maven is more than a dependency manager, though. It's a full build manager, with dependency management as one (major) feature. The dependency management part itself isn't very complicated, other than the verbosity of XML as the structure.
I have spent a long time as a Java dev using Maven, and the past few years floating around some other projects (C#, PHP, Python, a tiny bit of NodeJS) and continually find myself wishing to have Maven back, so I suppose YMMV.
> It’s simple to sit there behind the desk reading articles and history when you’re not one making the decisions, good or bad.
We are participants in those decisions, on both sides. We are part of the targets of those decisions (eg domestic spying, provision of military equipment to local and regional police forces), as well as tacit supporters of those decisions (or do you think an American civilian can travel the world without being blamed for those mistakes? I have heard of a lot of Canadian flags being added to travel luggage...).
Our tax money pays to kill children in deserts. Our tax money pays to destabilize governments. Our parents and children and brothers and sisters who ARE veterans directly participate in executing those bad decisions. And then many of them commit suicide. My father shot himself three years ago, near his 50th anniversary of shipping out to Vietnam, because of the mistakes he was part of there and later which stayed with him for so many decades. I don't think our second-guessing of those decisions taken in our name is at all inappropriate.
> Yeah, a lot of mistakes have been made. Many of them will continue to be made.
There must be a threshold of "too many" or "too heinous" mistakes at which point one stops trying to improve an organization and instead withdraws support, right? Otherwise it may as well be a religion.
You prompted me to go look - interesting that there are different sizes available per item (even between the tshirts). Wonder if some are sold out and they're just not showing?
The US has no requirement to carry your ID. I'm not sure there's any base requirement to have ID.
You only need your driver's license if you're driving, and ID in general is only required for certain activities that directly require identification or use the ID to confirm other information (eg age when buying alcohol).
We have a 5yo and 8yo. Most of the time, the question for whether they can handle something is less "are they capable?" and more "will someone call CPS?"
The dialog clearly warns you that if you have something to delete, it will be deleted, but it doesn't let you know if there is anything to delete.
That's not in itself a huge problem, but in this case it was compounded with the fact that the generic repo he was acting on is named inconsistently for users vs organizations, and he had just done it on his user account. If I'm reading correctly, a user's profile readme repo is `<user>/<user>`, while for organizations it is `<org>/.github`, and, crucially, `<org>/<org>` is almost always going to be the core project for that org.
So yes, the warning says you will lose all stars on the project, but in the moment it would have seemed (to a fallible human brain who was in a user-space context) that this was the right repo, whereas a "you will lose 54k stars" message would have broken the user out of that space.
There is a difference between using UI tweaks (color/size/motion) to call out information, and actually displaying that information.
Right? As in, "this will affect 0 stars" vs "this will affect 54,000 stars" is an informational difference. Calling out "this will affect all stars" (without specifying a number) doesn't break a user out of doing it to the wrong repo, since that message is the same in both cases.
The other thing they could do is make user/organization structure for that profile readme the same - as he mentioned, he had just done it on his personal account, which is of the form `<user>/<user>`, so doing `httpie/httpie` for the organization made contextual/autopilot sense in the moment.
Ignoring one-off bash scripts as needed, the standout examples of mine are a simple site for doing a specific type of date math in a bookmarkable fashion [0], as well as a webapp for my D&D 3.5 characters (pre-DNDBeyond days) [1]. As far as I know I am the sole user of both.
I used to run a couple blogs, but after 5+ years of not updating I replaced it with a basic calling card site. Just hard-coded HTML with a black-and-white Bootstrap on it.
I use a Keebio Iris [0] which is similar to a stripped-down ErgoDox. Careful part selection (especially keycaps) could have one for <$150, though you do have to solder it together yourself. I enjoyed the experience.
I find Steam to be the least-onerous (phone-based) 2FA tool I use - it pops up automatically when needed, and the codes are only 5 characters with a mix of letters and numbers, which I somehow find much easier to remember and type.
Granted, I don't know if those features involve security sacrifices, and I'm sure I'd get annoyed if I needed a separate app for every tool, but the user experience is more pleasant there for me.
Right, but they're general police (eg, they also handle non-traffic enforcement such as drugs), right?
I believe GP's point was not about "specific enforcement of traffic laws by police" but "law enforcement agencies who are specifically charged with traffic".