“Experts who reviewed the exposed secrets said the commit logs for the code repository showed the CISA contractor disabled GitHub’s built-in protection against publishing sensitive credentials in public repos.”
This makes it seem more intentional to me. Regardless of what the ultimate purpose were use of the repository was it says to me, the person knew what they were doing and it wasn’t just an innocent oversight like anybody could’ve made.
> needlessly complicated because they wanted to be backwards compatible with an old bad design.
It's not really needless complication of there is a reason for the complication. Obvioudsly in this case the need to be backward compatible with an old design made the implemtation more complicated than if they didn't need to do that. There were very, very strong business reasons why backward compatibility was a design requirment.
The Blue Angels are the Navy's demonstration team. This accident happened at an airshow on an Air Force base. The Air Force's demonstration team is named The Thunderbirds.
I have been looking into the Concurrent DOS 286 and FlexOS lineage. Since there is still some level of commercial usage of it, it seems like people are a big more reluctant to talk about it in any capacity.
Most of my software development career was spent working at a small company that sold a product that emulated the operating system developed and sold by a much, much larger company. The work was interesting and when you had a breakthrough or a small victory, it sure felt good. The challenge of keeping up was exhilarating and kept folks motivated to keep pressing forward.
But eventually it wears you down. It's nearly impossible to keep up in the long-term. Normal product evolution, the sheer size of the behemoth and sometimes even malice on their part to thwart the little guy make it really tough to stay current.
Think of Wine vis-a-vis Windows. They will never catch up.
Except they did with Wine, in a way. They got to the point where sufficient number of third party software developers target the common base between Wine and Windows (Steam/Proton), electing to have broader compatibility rather than catching all the newest Windows-only APIs.
I wonder how much similar behavior influence other buying choices. I’ve been eyeing an upgrade from M1 for a while - so far punting on it, mostly because of Asahi.
I guess I wasn't aware that Wine pivoted from trying to be a general purpose, drop-in replacement for Windows to being a platform for games that only supports a subset of Windows functionality.
It's much more difficult to keep current and support the full functionality of a much larger competitor's offering when you have to support everything. In my experience it was an all or nothing proposition. Either you emulated it 100% or you had nothing. I think Asahi is more in this realm maybe than Wine. It really needs to support all the hardware, 100%, or it's value is greatly diminished.
> I guess I wasn't aware that Wine pivoted from trying to be a general purpose, drop-in replacement for Windows to being a platform for games that only supports a subset of Windows functionality.
Or „just enough” for the subset of users that is „enough” to ensure product viability. The absolutism of „all or nothing” is rooted in the strictly-better mentality for replacing something.
For Wine/Proton, the core demographic is essentially gamers, who tend to overlap heavily with engineering population later on, and thus core population for Microsoft to capture and retain. Once Steam removed that vendor lock-in, the corporate discussion became more flexible.
For Asahi (proud Asahi user for 4y now), the added value of „most powerful Linux/Arm64 laptop on the market” outweighs the few things that don’t work on Asahi (HDMI out is probably the only one that occasionally matters for me, but screencasting works well enough). Yes, there are gaps, but they are smaller than things from Linux that are missing on OSX or Windows for me.
There was a PR for Adobe products a few weeks ago (https://github.com/ValveSoftware/wine/pull/310), though it seems like they're redirecting it to the main Wine repo now since it makes more sense there
I really don't mind boilerplate nearly as much as most people here on HN seem to. To me it's really no biggie if it helps structure things and make them explicit. I think it kind of goes along with the idea that typing code is not what takes the largest amount of time when you're doing software development. But the fact that I prefer explicit over implicit is another area where I think I diverge from the HN herd.
The ad was deceptively inlined in the article IMO. I read most of the ad before I realized it was an ad. I don’t begrudge anyone who wants to monetize with ads but I do think it should be clear what is sponsored. I felt fooled and I stopped reading right now.
This makes it seem more intentional to me. Regardless of what the ultimate purpose were use of the repository was it says to me, the person knew what they were doing and it wasn’t just an innocent oversight like anybody could’ve made.
reply