sir_eliah

I'm glad you asked! Obviously you have to check the code table and you can see that's a Greek beta, not German Eszett. \s

  In [1]: ord("β")
  Out[1]: 946

  In [2]: ord("ß")
  Out[2]: 223

There's a series of books from Petter Watts that give plenty of good reasons why this might not be the best idea:

- "Starfish"

- "Maelstrom"

- "βehemoth"

Is there a point in changing a phone so often if it's not broken?

Every day we're getting closer to the tech-world in the "Starfish" from Peter Watts.

Some time ago I also thought that no 3.5mm jack is a deal-breaker, but I bought super cheap jack-usbc adapter that is 5cm long and it works pretty well.

I think there are better ways to spend $200k than fight with deranged patent/trademark system.

I think the commenter meant that once the new syntax is approved and adopted by the community, you have no choice to not use the syntax. You'll eventually change your project and will be forced to deal with reviewing this code.

I came here to post exactly this! Maybe I have very limited imagination, but I cannot fathom how tiny propeller without internal power source could be any use for the search and rescue operations.

This sounds like a labour law horror story. I'm so happy now that I stayed on ordinary 40h/week work contract (no overtime) in the beginning of my career. Otherwise I'd end up with burnout and/or health issues pretty soon.

> If you use ctx.Value in my (non-existent) company, you’re fired

What a nice attitude.

It's one of my major pain points with Go. When can we have proper enum support with compile-time checks whether all the enum values are exhausted?

Touché!

A lot of banking/finance use cases.