> Any Smart Hold events created by Clockwise (such as Focus Time, Travel Time, Meeting Breaks, and Personal Calendar synced events) will be removed from your calendar. Flexible Meetings will stop moving and the green Clockwise sparkle will be removed.

Doesn't really sound like it.

Numa did try to name and consolidate the winter months, but it wasn't very popular.

The months were for productive seasons, winter for everything else.

Also French revolutionaries ;-)

I'm French and occasionally like to (re)read about the revolution period and every time I come to the calendar stuff I can't help but think "Really? This was stuff we wanted to spend time on?"

Hebrew is a reconstructed language. Whilst some roots will predate the Torah, most won't.

Several words, like the infamous "shibboleth" won't be inherited, or their meanings may wildly differ.

A record is not necessarily unique. Name changes, address changes, phone number changes, can all create "new" records in dumps like these.

Only if the generated text has no inherited copyright from the source data.

Which it might. And needs to be judged on a case-by-case basis, under current copyright law.

There is a difference between the liquor store checking your ID, and every store you even walk passed, checking your ID just in case you're on the way to try and buy liquor.

Likely due to trade agreement, with a geological neighbour.

Pigs are adapted to singular survival. A stressed sow will often eat the piglets. And that stress can be being a mother for the first time.

There are a lot of environmental factors, like snuggling for warmth being unsafe.

But by and large... Pigs give birth in numbers. They can afford for half to die, and still proliferate. They don't need to be 'good parents'.

How's Gleam's IO story today? Still need to go via OTP?

Under the hood you're still calling into BEAM/OTP but most operations are covered in gleam, at least I've very rarely needed to FFI into Erlang (couple times to extend what a library provides with a custom edge case).

gleam/io, mist, gleam/otp, sqlight, gleam_pgo, etc.

gleam/io doesn't actually support file IO, though, does it? Only printing to stdout.

So you'd need to use FFI just to write to disk, right?

There’s simplifile

Clauses existing, have very little to do with it being enforceable.

Vader might say he can change the deal at any point, but consumer law generally requires that what is purchased reflects what is advertised.

If you don't agree to a new set of terms, because the service is changed from what you purchased, then both parties generally should still be party to the previous.

Notification alone, is not enough. Agreement is required.

> Clauses existing, have very little to do with it being enforceable.

You cannot cancel a contract for "any reason". In most jurisdictions that will be an unenforceable term.

Usage here being consent, is an unpublished ruling. It does not set precedent, it refers only to these specific circumstances, where clients sought to understand terms before choosing to continue usage.

Legally, usage with foreknowledge, is consent. Usage where you already agreed to terms implicitly, because you sought and understood them beforehand.

It will not always be an agreement to new terms.

> This disposition is not appropriate for publication and is not precedent except as provided by Ninth Circuit Rule 36-3

The OP and I both explicitly cites their source for "usage + knowledge = consent", and it comes from fairly basic contract law. Are you saying this ruling cites another unpublished ruling or something?

I quoted the article. The article itself claims to be an unpublished ruling.