The code example is very similar to Ray.

Monarch:

  class Example(Actor):
     @endpoint
     def say_hello(self, txt):
         return f"hello {txt}"

  procs = this_host().spawn_procs({"gpus": 8})
  actors = procs.spawn("actors", Example)
  hello_future = actors.say_hello.call("world")
  hello_future.get()

Ray:

  @ray.remote(num_gpus=1)
  class Example:
      def say_hello(self, txt):
          return f"hello {txt}"

  actors = [Example.remote() for _ in range(8)]
  hello_object_refs = [a.say_hello.remote("world") for a in actors]
  ray.get(hello_object_refs)

Nice. Another aspect of the ternary operator is conditional evaluation. Beyond parenthesis, in a?b:c, only one of b and c get evaluated.

Agreed. I was skeptical at first, but I've worked at several companies with unlimited PTO and they all specifically encouraged people to take time off. One place was explicit that the reason they switched to unlimited was to get people to take vacations: "PTO is not meant to be a bonus when you leave the company. We want you to rest and recharge."

My current company recently made a rule that you have to apply for time off through the HR software. Not make it harder to take PTO—all requests are auto-approved-just so HR can track it. At the next all-hands the CEO said something like "You guys work really hard... we're, uh, worried." My manager has been bugging me to take a proper vacation instead of my usual day off here and there.

There are certainly awful, exploitative workplaces out there. But there are also great companies run by good people.

Reading a comment is exactly the same thing as scraping the internet, you just stop sooner.

If I read your comment, then write a reply, is it a derivative work?

I got a ZSA Voyager split keyboard and then spent weeks exploring custom layouts. The first question was QWERTY vs something better. Then there was layers and layer navigation. And should I swap out the key switches? And Keyboard Maestro.

Now I'm trying to abandon 30 years of muscle memory and typing at 4 wpm while I learn Colemak-DH. Maybe what I should really do is build a custom 34-key board...

Sure. There are undoubtedly a lot of config formats that are overly complex.

But sometimes the complexity is irreducible. Kubernetes is one such case. The model is very well thought out, and just about as simple as it could get without removing functionality. It has sensible defaults, built-in versioning, well-defined schema etc. But if you want to describe a complete installation of a distributed system with many heterogenous processes, spread across many hosts, communicating in specific ways, with specific permissions, persistence, isolation, automatic scaling, resilience, etc, there are a lot of details. I've worked with systems that have thousands of lines of configuration, and honestly that's not extraordinary. Many people on this site will rightly scoff and say, "psshh, that's nothing."

Configuration languages are a really important area of research in the tech industry right now, and every time someone posts one on here, there are a huge number of dismissive comments. Fine. Not everyone has this problem, but it's a real problem, and solving it represents a real advance in the state of the art.

Sounds like the case where a picture is worth a thousand words

/me sighs

The board has not been consistently candid in its communications with... anyone.

That have also given different opinions on an employee (sama) to different people, by seemingly acting to bring him back and replace him at the same time. And, they have acted to give the same project (CEO of openai) to different people at the same time... Hmmmm

This.

This is the most baffling piece of the whole saga. Board writes itself on the wall.

I'm not sure it is baffling.

They thought that this would be easy. Many things in their lives have been easy, blame someone of something, the person scurries away and they win.

This time, the person/people they blamed had a great reputation, a lot of influential friends, and had engendered a lot of loyalty. This caused pushback and they have never had to deal with that in their lives.

It's a theory.

Take a letter down, pass it around...

I'm curious if literally anyone (the board, the CEO(s), Microsoft, Twitter, etc) knows the full story or knows whats actually going on lol. I assumed initially it was just fog of war, but this just seems like pure incompetence and "purple monkey dishwasher" tier misinformation.

Everyone who sat in the meeting with the board ousting Sam knows enough of the reason as to why he was ousted. They all voted Yes, and even if some of them regret it now that they see it didn't unfold as just a simple "we now have control"-play, they all had reasons to vote him out. But those reasons obliviously aren't grounded in anything they can reveal to the public.

Yeah. This is how Squeak changed the license from SqueakL to Apache and MIT. That code has a lot of history, so it was a pretty big effort, but worth it in the end.