I am guessing this point is totally unnecessary based on how overall well-informed your comment was, but in case you weren’t aware, it is frequently helpful to run a wifi analyzer of some sort to figure out which channels are heavily utilized in your area so you can set your router to one with less interference. I used to use the Mac network utility that I think may have been deprecated, but it worked like a charm. I do this for my friends all the time and it dramatically improves their network performance in 90% of cases. The only places I found it was pointless were in the middle of nowhere and my own apartment not too far from MIT’s campus, where I assume I was surrounded by equally (probably much more) knowledgeable nerds so the neighboring networks were surprisingly evenly distributed across the available channels.
It’s the lack of notifications and an inbox showing new replies to your comments. I miss 90% of the replies to my comments until it’s way too late to reply in turn.
The earliest that sunrise happens in the continental US is around 5AM during DST, so the earliest it would go is 4AM. That is in the extreme north of the country (excluding Alaska, which I'd say is not worth including in the conversation given its unique circumstances), on the eastern edges of time zones. So I don't know what you're talking about. If you read the article linked above, it specifically points out that there are measurable, concrete negative health effects from DST but not from standard time. So no, the sun rising early doesn't really stress you out the same way getting up before sunrise does. Not at all.
Yeah, this is what makes me mad about this debate. Permanent DST proponents talk about how they like having daylight at the end of the day after work. Well, weigh that mild preference against the very real physiological harm it causes. They want to enjoy their afternoons. I want to work a normal 9-5 job without getting heart disease because of the stress of waking up before sunrise eight months out of the year.
That doesn’t really make sense. It wouldn’t necessarily or even likely have crashed at its destination as it should have returned to base once it reached those coordinates and completed its mission. And even if it were programmed to loiter until it was out of fuel (which… why?), the drones are supposed to land with a parachute so it wouldn’t have just crashed and exploded. The name coincidence is only interesting if you assume it crashed in a specific place of interest as opposed to randomly along its course. It’s much more likely and common for someone to fat finger in coordinates with a small, random error like flipping a sign or swapping digits. Flipping the sign on latitude or longitude fools the drone’s GNC system into targeting a destination that is on the opposite side of the planet and the system just flies in a straight line in that direction until it runs out of fuel. It’s the same failure mode as googling the wrong coordinates but a more commonly occurring category of user error.
Assuming this is all true, I wonder if this is how wild dolphins feel when they have an encounter with friendly human beings? It almost feels like playful behavior. Like the UAPs are flying alongside the fighters the way we might swim with dolphins. Tweaking our noses a bit too. "Look how much faster than you we are. Look how we know your secret little patrol point." It would be sinister and deeply threatening if paired with any demonstration of ill-intent, and perhaps it should be read as such. But it doesn't feel that way to me. It feels very much like the brief fun little games people play during incidental encounters with non-dangerous wild animals sometimes. Imagine a man hiking along a trail in a line with a dozen friends, who notices an interesting lizard on a log and stops to look as his friends continue on without him. The man pokes the lizard a little, to see how it reacts, and it predictably scurries off. He then follows his friends, soon disappearing into what is an impossible-to-reach distance from the lizard's perspective, and he never gives the little lizard another thought. We are lizards compared to any intelligence capable of achieving these levels of power output (1100GW in seconds!), if this study's estimates are correct. Maybe we just got poked in passing.
> We deny people waiting for organ transplants medical treatment regularly. there simply aren't enough organs to go around.
Yeah. There is no shortage of pig organs which is kinda the whole point. Rationing limited care is different than denying perfectly available care simply out of retribution. I thought the context made that distinction rather self-evident.
Seems pretty damn simple to me. If you wouldn’t put someone to death for a crime, you shouldn’t deny them medical care in a manner that will kill them for the same crime. It’s functionally and legally the same as putting them to death. Withholding necessary medical care is the same as withholding food, water, air, or shelter.
IIRC you can install the guac site as a PWA in your browser and sometimes the browser then allows more keyboard events to bubble up from the OS to the javascript layer where guac lives. Doesn't fix everything, but it can help.
Yes. And many corporate and government networks deny list all traffic on ports other than 80/443, so RDP just is not an option in many cases. VDI over HTTPS also means users don't need a separately installed RDP client and can just access the VDI via their browser.
It ensures separation of concerns is at least minimally applied in order to support two separate presentation layers (GUI & CLI). CLIs are also much more testable in general, so usually it’s easier to write e2e tests if a CLI is present. It might not cover 100% of the code because it doesn’t test the GUI, but does often get you something substantial like 90% of the way there.
I think I vaguely recall the explanation from a classics course many, many, many years ago, but I can't find a source without investing a ton more effort, so take this with a grain of salt: IIRC, Plutarch wrote the sayings in intentionally archaic (for his time) Greek. He lived hundreds of years after Sparta had disappeared as a power in the ancient world, so he could have intended it to demonstrate the great antiquity of the quotations, or he could have done so to paint the Spartans as rough-around-the-edges rustics. The translation attempts to mimic this effect by translating the archaic-sounding Greek as archaic-sounding English.
I can echo these concerns having been a contractor working on applications in more than one of the DoD cloud platforms, including CloudOne (a subset of PlatformOne, for readers not familiar with the flurry of DoD cloud offerings that have sprung up over the last few years). I recently changed jobs in no small part because of the massive incompetence on the USAF side. It’s really quite stunning. My entire schedule was eaten up by unnecessary meetings where wholly unqualified USAF officers (current and retired) in PM or similar roles would pontificate endlessly about just absolute nonsense concerns. Like hours of arguing about how to label a button on a form. Constant bike shedding. No users involved meaningfully in the feedback cycle. And I swear all these old USAF guys just straight up hate their users. They will suggest the most user-abusing possible design because they think their users are stupid and need 10000 confirmation dialogs to avoid making mistakes.
And on the legacy non-cloud side of things… it’s a horror show. No CI/CD. No testing (a lot of my job was bolting awkward test harnesses on to existing legacy software to compensate). Inconsistent and ever changing project management systems (they switched from TFS to Jama to Azure DevOps to Jama again and then when I left were talking about moving to JIRA. Our cocontractors were insanely unqualified. They were really proud of how cutting edge they were for adopting git for VCS. In 2019. It’s crazy how bad all of this software is, but at least it wasn’t on some internet connected server before.
I somewhat disagree with that comment. It’s mostly reasonable, except there are other explanations for why they only show up over training exercises.
First of all, these training exercises have the highest concentration of military-grade sensors in the world. In the history of the world. And I don’t mean that in the cliche way that military-grade sensors are good per se. Just that civilian sensors designed to detect hiding aircraft don’t really exist.
And you only get these concentrations in training exercises because the world’s most cutting edge military hasn’t had a war against a technologically advanced opponent in decades. Decades during which those sensors have become increasingly sensitive and networked with a greater quantity of supplementary data sources and somewhat complex algorithms for blending data from many sensors. All of which means of course it’s a military detection, and of course it’s a training exercise (DOD would also almost certainly not release operational information, even in summary, so we can safely assume any detections in an operational environment remain classified).
Personally I have not. I have only had one particularly weird use case where I really needed to deliver a Python executable alongside an Electron app, and made it work with Pyinstaller. We’re actually reworking things to use Pyodide to compile the Python to WASM so we don’t have to deliver any separate Python code at all. It’s a real Rube Goldberg machine of an application, but we had a lot of weird constraints we had to meet (eg, we couldn’t use sockets to communicate between Python and Node, so had to package the Python as an executable). It works beautifully but it was a mess to get running.
Yes, but if you sign the executable with an acceptable certificate (the company’s cert or some other trusted CA), you can install an arbitrary executable usually. Docker would typically be blacklisted, however. In most corporate IT environments, it’s much easier to get a small, focused executable white listed or code signed than to get something with such a huge attack area as docker approved for regular, non-technical users.
Desktop/local usage, especially for non technical users or people working in environments where they can’t install docker (eg locked down corporate machine). There isn’t a great way to pass around a single executable or installer for a Python app. There’s pyinstaller, but it’s finicky and doesn’t quite work cross platform (you have to build the executable on the target OS).
On the other hand, OP’s setup makes it very easy to publish packages. So you can create a tarball and have a user pip install that, then run your app with a simple CLI. Or publish to pypi if you want it public. The downside is you assume the user has the right version of Python and knows how to switch versions if need be and all the weirdness that comes with that. But for web apps, packaging your app also makes it easy to wrap in a simple dockerfile that basically just installs the package and then runs it.
I am a bit suspicious of how this result is being presented in the media. The overwhelming bulk of the diagnoses are for anxiety and depression. Which seem like pretty typical reactions to an extreme emotional trauma like hospitalization during a pandemic, and are fairly common reactions to long term recovery from a major illness even during less desperate times where treatment is more readily available.
The elevated rates of stroke and dementia are more concerning, but are a less startling 7% and 2% respectively of the observed population. I’m not sure if the authors controlled well for confounding conditions either.
VNC/RDP via Guacamole or some other VDI solution can provide this with relatively little effort. But it sort of defeats the point. Using your local IDE to connect to a container allows for a snappier, more responsive development experience than a VDI can provide. Plus remote containers is basically just ssh. So a lot less bandwidth and general overhead than a full on VDI solution, and you don't need to have a full VNC server set up on your containers.
This has been my experience as well. It can be extraordinarily difficult to design a consistent OO type system to represent things like quantities with units and references, alongside quantities with just units and neither units nor references. For example, altitude is a quantity plus a unit of distance plus a reference (eg above ground level). Except some references require different data to convert. So AGL requires elevation for conversion to mean sea level, for example. Designing an OO system to represent that and constrain against invalid operations gets super complex and the developer ergonomics rapidly degrade in most languages. I’ve only ever successfully done it in C#, and even then I’ve found maintaining the unit conversion code annoying.
In well designed software, data ingestion should be easily separable from the core logic of the application. Which is the point the parent comment is making. Some basic best practices would allow you to share your core code without implicating HIPAA. Even if it’s just basic stats, sharing the code makes it easier to reproduce your results and to check your logic.
Although I agree with your analysis that enabling competitors in science is not common, it really, really should be. That’s kinda the point of publication, at least in theory. Sharing knowledge and methods.
Regarding web pages, some people work in highly controlled environments where you only have access to the man pages because you are working on a limited intranet designed for sensitive data, e.g. defense contractors or people working with sensitive health data. So having colocated resources can be extremely valuable for a small subset of users and shouldn't be completely discouraged. Although I agree with your assessment that command help and web pages are where the priority should be, since that meets the needs and expectations of a much larger proportion of CLI users.