zaarn

The original OGL very much allows video games. KOTOR is for example a game that includes a copy of the OGL. There is also several virtual tabletop softwares that ship with OGL content.

According to a different article the COP of this heat pump is between 3-4. However, Thermoaccoustic Heat Pumps have some advantages that you can also find in their press release; because there is no refridgerant, only the air medium which is Helium in this case, you can operate them down at much much lower temperatures without loosing much COP, same in reverse (they claim -15C to 50C). And because there is few moving parts (only the acoustic coupler) they can have an immensely better lifetime than a compressor that needs oiling and maintenance (Equium claims 30 years service life).

They aim for fairly small heat pumps from the looks of it, so this might be something targeted at people renting flats. Something to replace the gas burner for most of the winter.

Well, if you want to innovate then, atleast as far as Germany is concerned, you have to lay out the non-standard parts of your contract in clear and simple terms along with pointing out where to read the full text.

If I give you a software copy with non-standard license, courts here won't uphold such licenses if you don't point out it's non-standard and in what ways. Because the consumer can't be expected to read and understand every legal contract they have to sign. They aren't lawyers, after all.

I'm in Germany not France but Pet Clauses aren't generally valid.

Garage access is only an issue if you pay for it. If you pay for a garage, the landlord has to ensure you have access and depending on the type of contract, ensure you are the only one with access (re; shared vs solo garages).

The Pet Clause thing only concerns big pets. Anything the size of a normal house cat or smaller (except actual house cats and exotic/unusual pets) requires no special permission. If larger pets are banned, this is only valid if there is a contract condition to allow the tenant to get special permission to have a cat or dog. A total and general ban of all pets is considered too disadvantageous for the tenant and thus not allowed. When asking for permission, the denial must have an explanation attached. "Pet can cause damage" isn't allowed for example, since the owner could just buy a pet insurance to cover any claims. Noise and dirt aren't either, since the landlord can require the owner to take care of that. Basically the explanation of why you deny a pet has to be something that the owner doesn't have the power to change easily, such as that the landlord is allergic and living in the flat above you or similar things.

This kinda stuff is usually added at the end of the template contract, there isn'T a lot to read so they tend to be obvious.

This isn't about tech though. It's about Terms of Service. The Legal Contract between the tech company and the user. I don't see where "innovation" comes into this other than disadvantaging the user.

Yeah that would be on top of it all. For the ATC to use Linux on something, there would have to be a competing application that runs on Linux, which has to be certified and then migrated towards. That could take a decade or two.

Not all power plants can self-feed the power they need to keep generators working. Often this is a diesel generator on the plant because the only other source of power is 20MW generators that simply can't be tuned down enough to handle the few kilowatts it takes to keep the generators turning.

Almost all plants will trip from the grid if it gets bad and remain idling for some time. But if that happens, the grid is still dark and the black start generators are the best equipped to bootstrap the grid. You can't start with the big generators too, so you can initially only bring in small plants until the grid capacity is big enough to not trip out when the big generators come online in a wrong way.

There is a good chance that by the time the grid is stable, atleast some power plants will have had to shutdown entirely and spin back up from a black start with only external power.

I don't think someone being stuck with Solaris for unknown reasons is sufficient to declare that Solaris is better or equal to Linux. For the ATC, it could simply be a matter of "The application we run only support Solaris"

There is evidence of a lot of mass extinctions. The Big Five is just the biggest 5 we know off (all of them feature atleast 75% of all species becoming extinct on a relatively short timeframe, with the quickest being the KT which lasted at most a thousand years, the biggest of them, the PT event, making 95% of all species extinct). For smaller extinction events, Wikipedia lists about 30 of them. But those aren't nearly as interesting because they didn't have that much impact.

Depends on how the rest of your stack looks. I wouldn't presume.

I don't really see the maintenance issue. The rust code seems maintainable and the go code seems to be fairly lightweight overall.

This is a toy example to demonstrate a framework to build with. But I don't think it's not a cleanly solved engineering problem. Instead of reinventing xer Rust code in Go, Xe has simply taken the functional rust code and made go run it in a cross-platform and portable manner. Minimal effort from the engineer has been expended to solve this and C was not involved for FFI definitions either.

For me the big selling point is that it supports booting encrypted ZFS with zstd compression and other modern features enabled. So your boot pool doesn't have to be restricted to the GRUB set while still giving you all the goddies (and more, since you can just drop to a linux shell)

You don't really loose type safety, rather it moves to runtime. Downcasting an anyhow error to the concrete internal type is certainly possible and won't panic in my experience.

Atleast where I live, when you fire someone that's it. They're fired. Even if they still work for 60 days because that's the minimum notice period. The only way to reinstitute the contract is if both sides sign a new contract to overwrite the termination. And this can be used to amend the employment contract too.

So where I live, you'd be in a prime position to negotiate better paychecks because without both employee and employer agreeing, a termination has finality.

you can have both MBR and GPT on the same disk. GRUB explicitly supports it too, if it finds a EE00 partition type, it will parse the disk again as GPT and boot normally to boot a second stage of the ESP. A UEFI system will ignore the MBR and use the GPT table to boot directly into the ESP. The Gentoo wiki has a description how to set this up.

Most enterprise level stuff can (ie, anything that'll go into a rack, the expensive QNAPs/Synos, any supermicro I've encountered, etc.) handle the 3V3 pin issue just fine, in my experience.

If you're writing cryptographic code, panicking for every issue is not good, that's a DoS vector that could be easily exploited. It's safer to handle the error in-band and let the application higher up decide if it should panic, error or continue.

IMO you should use the fallible slice API's in any safety-critical code, such a cryptographic code.

Yes, there is more code, but it does not become a lot more complex, if you need to you can unwrap to explicitly panic. You should still insert asserts to catch issues. But if there is an issue, such as running out of memory or anything else, you can handle it more appropriately than producing a Denial-of-Service issue immediately, which is definitely not good.

It should be noted that you can simply use the fallible API's for slices in Rust, then you don't have a crash but can cleanly abort the operation and return an error.

Keep in mind that 40 cycles is the minimum. 99.9% of the plugs will be fine after 40 cycles and probably will do 400 without issue. But you're outside what the manufacturer guarantees it'll last.

And by experience, 40 is absolutely plenty. Almost all plugs in a computer are likely to only experience 10 cycles at most (and half of them only two; during setup and during EOL).

Was talking about Top OP.

Well, it would be atleast polite to use gender neutral pronouns.

OP has a page for the proper pronouns to use in this situation, in case you didn't notice it.

Higher prices on the open market yes, but not enough to offset the volume loss. A good chunk of new volume is sold to China, which buys at staggering discounts (as high as 50% over market rates).

Not serving means there is already no content. That is different to serving 100TB of 404 content from clients that will never stop.

Even then I would not do this without clearing it with a lawyer first. You could still end up at the wrong end of a lawsuit that you'll have to defend in India.

I used the current values, they should be valid for a reasonable timeframe.

Edit: only by a few percents; the distances are too large to appreciably change the visible size of the sun in the sky.

The client can just set a custom timeout and close the socket after 5 seconds of no or low activity. Then try again.

On your side note; EasyList probably does not want people to start suing for starting to distribute malicious content to users (and crashing your browser on purpose is arguably malicious).

Good luck finding the legal contact, not to mention suing, some random developer in India who apparently already abandoned the project.

I will also point out that if you fail2ban the IPs requesting the spamblock list, it could become worse if the browser just retries endlessly in the background. The traffic for a 404 page could be much smaller than the traffic of the very same devices trying again every few seconds, constantly, instead of only checking that 404 every app restart.