Off-and-on trying out an account over at @tal@oleo.cafe due to scraping bots bogging down lemmy.today to the point of near-unusability.

  • 69 Posts
  • 3.03K Comments
Joined 2 years ago
cake
Cake day: October 4th, 2023

help-circle
  • You could also just only use Macs.

    I actually don’t know what the current requirement is. Back in the day, Apple used to build some of the OS — like QuickDraw — into the ROMs, so unless you had a physical Mac, not just a purchased copy of MacOS, you couldn’t legally run MacOS, since the ROM contents were copyrighted, and doing so would require infringing on the ROM copyright. Apple obviously doesn’t care about this most of the time, but I imagine that if it becomes institutionalized at places that make real money, they might.

    But I don’t know if that’s still the case today. I’m vaguely recalling that there was some period where part of Apple’s EULA for MacOS prohibited running MacOS on non-Apple hardware, which would have been a different method of trying to tie it to the hardware.

    searches

    This is from 2019, and it sounds like at that point, Apple was leveraging the EULAs.

    https://discussions.apple.com/thread/250646417?sortBy=rank

    Posted on Sep 20, 2019 5:05 AM

    The widely held consensus is that it is only legal to run virtual copies of macOS on a genuine Apple made Apple Mac computer.

    There are numerous packages to do this but as above they all have to be done on a genuine Apple Mac.

    • VMware Fusion - this allows creating VMs that run as windows within a normal Mac environment. You can therefore have a virtual Mac running inside a Mac. This is useful to either run simultaneously different versions of macOS or to run a test environment inside your production environment. A lot of people are going to use this approach to run an older version of macOS which supports 32bit apps as macOS Catalina will not support old 32bit apps.
    • VMware ESXi aka vSphere - this is a different approach known as a ‘bare metal’ approach. With this you use a special VMware environment and then inside that create and run virtual machines. So on a Mac you could create one or more virtual Mac but these would run inside ESXi and not inside a Mac environment. It is more commonly used in enterprise situations and hence less applicable to Mac users.
    • Parallels Desktop - this works in the same way as VMware Fusion but is written by Parallels instead.
    • VirtualBox - this works in the same way as VMware Fusion and Parallels Desktop. Unlike those it is free of charge. Ostensible it is ‘owned’ by Oracle. It works but at least with regards to running virtual copies of macOS is still vastly inferior to VMware Fusion and Parallels Desktop. (You get what you pay for.)

    Last time I checked Apple’s terms you could do the following.

    • Run a virtualised copy of macOS on a genuine Apple made Mac for the purposes of doing software development
    • Run a virtualised copy of macOS on a genuine Apple made Mac for the purposes of testing
    • Run a virtualised copy of macOS on a genuine Apple made Mac for the purposes of being a server
    • Run a virtualised copy of macOS on a genuine Apple made Mac for personal non-commercial use

    No. Apple spells this out very clearly in the License Agreement for macOS. Must be installed on Apple branded hardware.

    They switched to ARM in 2020, so unless their legal position changed around ARM, I’d guess that they’re probably still relying on the EULA restrictions. That being said, EULAs have also been thrown out for various reasons, so…shrugs

    goes looking for the actual license text.

    Yeah, this is Tahoe’s EULA, the most-recent release:

    https://www.apple.com/legal/sla/docs/macOSTahoe.pdf

    Page 2 (of 895 pages):

    They allow only on Apple-branded hardware for individual purchases unless you buy from the Mac Store. For Mac Store purchases, they allow up to two virtual instances of MacOS to be executed on Apple-branded hardware that is also running the OS, and only under certain conditions (like for software development). And for volume purchase contracts, they say that the terms are whatever the purchaser negotiated. I’m assuming that there’s no chance that Apple is going to grant some “go use it as much as you want whenever you want to do CI tests or builds for open-source projects targeting MacOS” license.

    So for the general case, the EULA prohibits you from running MacOS wherever on non-Apple hardware.





  • Yes. For a single change. Like having an editor with 2 minute save lag, pushing commit using program running on cassette tapes4 or playing chess over snail-mail. It’s 2026 for Pete’s sake, and we5 won’t tolerate this behavior!

    Now of course, in some Perfect World, GitHub could have a local runner with all the bells and whistles. Or maybe something that would allow me to quickly check for progress upon the push6 or even something like a “scratch commit”, i.e. a way that I could testbed different runs without polluting history of both Git and Action runs.

    For the love of all that is holy, don’t let GitHub Actions manage your logic. Keep your scripts under your own damn control and just make the Actions call them!

    I don’t use GitHub Actions and am not familiar with it, but if you’re using it for continuous integration or build stuff, I’d think that it’s probably a good idea to have that decoupled from GitHub anyway, unless you want to be unable to do development without an Internet connection and access to GitHub.

    I mean, I’d wager that someone out there has already built some kind of system to do this for git projects. If you need some kind of isolated, reproducible environment, maybe Podman or similar, and just have some framework to run it?

    like macOS builds that would be quite hard to get otherwise

    Does Rust not do cross-compilation?

    searches

    It looks like it can.

    https://rust-lang.github.io/rustup/cross-compilation.html

    I guess maybe MacOS CI might be a pain to do locally on a non-MacOS machine. You can’t just freely redistribute MacOS.

    goes looking

    Maybe this?

    https://www.darlinghq.org/

    Darling is a translation layer that lets you run macOS software on Linux

    That sounds a lot like Wine

    And it is! Wine lets you run Windows software on Linux, and Darling does the same for macOS software.

    As long as that’s sufficient, I’d think that you could maybe run MacOS CI in Darling in Podman? Podman can run on Linux, MacOS, Windows, and BSD, and if you can run Darling in Podman, I’d think that you’d be able to run MacOS stuff on whatever.










  • There was some similar project that the UK was going to do, run an HVDC submarine line down from the UK to Africa.

    searches

    https://en.wikipedia.org/wiki/Xlinks_Morocco–UK_Power_Project

    The Xlinks Morocco-UK Power Project is a proposal to create 11.5 GW of renewable generation, 22.5 GWh of battery storage and a 3.6 GW high-voltage direct current interconnector to carry solar and wind-generated electricity from Morocco to the United Kingdom.[1][2][3][4] Morocco has been hailed as a potential key power generator for Europe as the continent looks to reduce reliance on fossil fuels.[5]

    If built, the 4,000 km (2,500 miles) cable would be the world’s longest undersea power cable, and would supply up to 8% of the UK’s electricity consumption.[6][7][8] The project was projected to be operational within a decade.[9][10] The proposal was rejected by the UK government in June 2025.






  • I bet a lot of people didn’t have fire insurance.

    EDIT:

    Many wildfire victims didn’t have insurance coverage at all.

    EDIT2:

    https://www.latimes.com/business/story/2025-01-12/california-homeowners-are-getting-cancelled-by-their-insurers-and-the-reasons-are-dubious

    Last year, Francis Bischetti said he learned that the annual cost of the homeowners policy he buys from Farmers Insurance for his Pacific Palisades home was going to soar from $4,500 to $18,000 — an amount he could not possibly afford.

    Neither could he get onto the California FAIR Plan, which provides fewer benefits, because he said he would have to cut down 10 trees around his roof line to lower the fire risk — something else the 55-year-old personal assistant found too costly to manage.

    So he decided he would do what’s called “going bare” — not buying any coverage on his home in the community’s El Medio neighborhood. He figured if he watered his property year round, that might be protection enough given its location south of Sunset Boulevard.

    So the insurer (accurately) predicts that the rate of fire across the entire area has become extremely high, and updates prices to reflect that. They’re doing what they probably should: predicting risk and passing that information through as price information.

    The state will insure at a lower rate, but requires a lot of changes to the property to reduce fire risk to go anywhere near it. That’s reasonable (well, maybe not whatever specific numbers are involved, but providing the option of lower prices for a homeowner taking actions to mitigate that extreme fire risk).

    But that mitigation itself isn’t free, and the homeowner is so living close to their financial limits that they can’t afford the mitigation. So they gamble: maybe a fire won’t happen. A fire does happen, and so now they can only really sell the property for the land value.

    So, what went wrong there?

    Well, I’d give two suggestions.

    • The insurer assessed risk correctly — its analysis was “this place is facing extreme risk of fire” and it passed that information on as price information…but it didn’t do so as early as it could have done. If the homeowner had known that they’d be facing $18k/year fire insurance some years earlier, maybe they wouldn’t have moved into the area in the first place, that it’d be just too expensive to live there. People sign insurance contracts on a shorter-term basis than they decide where to live. The incentives created is for insurers is to analyze risk over a year long basis. The price information gets passed on to homeowners, but it may not give them enough time to act. We could restructure the insurance market by doing something like capping annual percentage rates of increase once someone has obtained a given rate. That’d establish more-conservative and longer-term risk assessment by insurers, like, what will the fire risk be in the area five years from now, or ten years from now, not just over the next year. Do that and people will tend to pay more for fire insurance on average, because insurers will have to take into account that it’s harder to predict five years or ten years out. But it also will give homeowners a longer time window to make decisions.

    • I think that in general, people should maintain a larger financial buffer. “I need to have a number of trees on my property cut down in order to reduce my insurance rates against a very large hike” is the kind of unexpected expense that’s probably a good idea to pay. But if people don’t establish and maintain liquid assets for that kind of situation, then that option goes away.

      https://homeguide.com/costs/tree-removal-cost

      How much does tree removal cost?

      $400 – $1,200 average cost

      Assuming the upper level there as his worst case, the most that removing those ten trees would have cost was $12,000. Spending $12k to reduce annual costs by $18k is an investment that pays for itself in the first two-thirds of the first year. That is an awfully good move, financially. If you maintain a 6-months-of-income emergency fund, then that should probably cover it. But…if you can’t find the $12k, then it ain’t happening.

      I would very much like Americans to maintain a larger financial buffer than they do. Here, it would have paid off in a big way for the person involved: had they done it, they’d have had an insurance payout or maybe even saved their house. But…okay, lots of people have recommended maintaining a buffer, and it certainly isn’t something that always happens. Say that doesn’t happen here. What other options are there? Maybe the person here could have taken out $12k in debt against the house, and spread out paying that back. If the California state insurance program assessment is correct as to the reduction in risk from removing the trees — and unless the lower price is just reflecting state subsidy, it should — it might make sense for the state insurance program to say “Okay, I’ll offer an all-in-one package, with financing. You take out $N in debt against your equity. You agree to a series of mitigations that that funds, like removing trees on the property, and we provide the near-term funds for it.” That’s not free, but it’s also not one big $12k bill, either. Maybe that’s something that the homeowner in question could have done. That basically permits the state to more-rapidly have fixes for high fire risk to happen.

      The homeowner in question presumably — unless he’s violating his mortgage contract — has paid off his house, because his mortgage will very probably require him to maintain fire insurance as long has he has an outstanding mortgage, to mitigate their risk. So he should have equity to secure that loan.

      Okay, but say what he actually did was to violate his mortgage contract and just have both a mortgage and run without fire insurance. What then? How do you avoid that scenario? Well, one option might be for the state to require that mortgages come bundled with fire insurance, that the mortgage lender be the one to obtain a fire insurance contract — at least on the percentage of the property that they own — which forces the price information about fire insurance to be baked into the mortgage price. That’ll make mortgages in the state more expensive; it’ll also mean that either the mortgage lender or the insurer will have to do long-term risk assessment to price in fire risk, if you’re talking about mortgages that run on the order of decades. But it makes things a lot more straightforward for the homebuyer: one up-front number attached to purchase price that should represent long-term risk.



  • I think another major factor for Linux gaming beyond Valve was a large shift by game developers to using widely-used game engines. A lot of the platform portability work happened at that level, so was spread across many games. Writing games that could run on both personal computers and personal-computer-like consoles with less porting work became a goal. And today, some games also have releases on mobile platforms.

    When I started using Linux in the late 1990s, the situation was wildly different on that front.