sswu

The TypeScript example does feel a little weird. I've used this library successfully with React + TypeScript with the following pattern:

  const mesh = useRef<THREE.Mesh>(null); // mesh has type RefObject<THREE.Mesh | null>
  ...
  useFrame((): void => {
    if (mesh.current != null) {
      mesh.current.rotation.x += 0.01;
    }
  });
  ...
  return <mesh ref={mesh} ... />

As others have mentioned, the ref will typically attach by the time a `useEffect` hook is called, but for safety it's nice to have the null check.

I took this bus twice, and would happily take it again, but probably because it just happens to fill my niche. From Santa Monica, taking rideshare to/from LAX would easily cost an extra $30 each way, not to mention the traffic on Friday evenings. Sometimes it takes longer to get to the airport than the flight itself.

Cabin is nice because the total time I spend awake (< 30mins at each end) is less than that of taking a flight (at least a 3 hour contiguous block). It's also less stressful not having to worry about luggage, security, when to leave for the airport, etc.

If I couldn't sleep like a rock, or didn't live in Santa Monica, or wanted to go to south bay instead of SF, I would get a flight instead. I agree this is not for everyone, whether it be comfort-wise or location-wise, but I do hope this new tech helps people sleep more peacefully, and that they expand to more locations.

I ran into a similar issue applying for Global Entry. Luckily an appointment at 3am on Saturday suggested the times were in UTC. Nevertheless this was unnecessary uncertainty and anxiety - what about those who aren't familiar with UTC time?

How can we design datetime libraries to prevent these issues? Or at least make it so that error-prone behaviors must be very explicit?