gonesurfing

What services is Cmux calling? The usual "updates" things or something more?

Not that I can see. I just tried it and get the same issue you describe.

Just as an FYI for anyone on iOS that is still tolerating this egregious dark pattern example, I successfully used Distraction Control in Safari to block this popup. Details here https://support.apple.com/en-gb/120682

My 2p's worth is that the whole of F# is more than the some of its parts. When you say in your previous comment "All the good stuff has been pirated from F#" it misses the point of what it's actually like to use F#. The problem is, it's almost impossible to communicate what it's like. You have to try it and you have to keep going until you get over the initial "WTF!?" hump. There will be a WTF hump.

For example, C# may have cribbed the language features, but F# is expression based and immutable by default. Try using the same features in this context and the whole game changes.

This sounds very similar to the approach prescribed in the book Digital Minimalism. I just finished it and can’t wait to join you with a somewhat similar approach!

I’ve been thinking about the local notes use case, but know zero about doing it. Do you have a good setup you could point me at?

Your advice about not listening to your tinnitus is spot on, but easier said than done. I found the guidance in the book Rewiring Tinnitus really helped me in this respect https://www.amazon.co.uk/Rewiring-Tinnitus-Finally-Relief-Ri...

I don’t know, but I think this GitHub issue will probably give you the current status and background on this point https://github.com/fsharp/fslang-suggestions/issues/243

Update: the issue is tagged await-csharp-alignment, which is probably the relevant status.

Stylish F# is a good book to go with all of Scott’s works https://www.apress.com/gp/book/9781484239995

In the spirit of leveraging the type system, you could try doing some type-first development. If possible, carve a logical module or sub-system out of your existing code base and then attempt to represent the data and functions for that module in F# types. Don't implement any of the functions, just see if you can describe the data and operations using the type system. Tomas Petricek describes this approach really nicely in his post "Why type first development matters".

This has a the following benefits:

  - It helps you review and clarify what the existing code does.
  - It will force you to name the data and operations explicitly.
  - You won't be distracted by actually implementing the operations.
  - You have a succinct description of the module that you can discuss with other developers.
  - It divides the migration into manageable chunks.

You could challenge yourself to educate team members, through the type system.

You may also find some of the techniques from the book "Working Effectively with Legacy Code" useful.

Updated: Removed links as comment was not posting.