Reduce rune ambiguity through renaming and signature changes

[clearfram3]

I came across this thread on reddit. Here is what is says if you can't open the link:

// instead of $effect and $effect.pre, just:
$effect(() => {
    // Runs before DOM updates
}, { timing: 'pre',
     dependencies: [color, size] // this is another idea to make it more explicit, could be called "deps"
   });

Instead of $effect.tracking ----> $isTracking() or $effect.isTracking()

$state.raw ----> $state.immutable or $state.readonly

Drop $derived.by and make $derived accept an expression or functions.

I think Rich has said that $effect should not be the first thing reached for. Requiring timing and deps would ensure that doesn't happen while also making it very clear what is happening and too what when it is used. Thoughts?

[brunnerh]

Drop $derived.by and make $derived accept an expression or functions.

Overloads are usually a bad idea, and this is no exception.

$state.raw ----> $state.immutable or $state.readonly

It's neither immutable nor readonly, so those names don't capture what it does.
If anything it is very shallow.

Instead of $effect.tracking ----> $isTracking() or $effect.isTracking()

Does not really change much, primarily a matter of style/taste. Some consider the prefix redundant, i'm inclined to agree.

Regarding the $effect stuff:
Putting anything after the callback is harder to read, so I don't think it's a good idea.
Some people want explicit dependencies, issue for that is here:

• Allow opt-in explicit dependency tracking for $effect #9248