Comments by "LoneTech" (@0LoneTech) on "Theo - t3․gg" channel.

  1. Fun fact: Haskell has otherwise defined as True, to make series of pattern guards read consistently.
    1
  2. Option is exactly the same feature as a nullable column, and SQL in particular has had the distinction essentially forever. These people specialize in handling other people's SQL databases and don't bother with column constraints (in this case, a unique foreign key).
    1
  3.  @appelnonsurtaxe  Is there a point arguing when you're talking to a straw man that believes assigning a value is magic? In your list, the point that related to SQL's capability was that nulls don't nest. That's because there's no obvious meaning to half-having nothing. The point where you claim fundamental data structuring (whether you spell it Maybe, Option or Not Null doesn't matter) has no relevance to a data breach in a database specialist's data handling... yeah, it may be irrelevant to your crusade on the word null. Not to the subject.
    1
  4. So, a database vendor didn't bother to have a primary key constraint. And their whole thing is centralizing all your data for an SQL engine with the specialty of don't do that. And the big "scale to zero" innovation? That's inetd.
    1
  5. Unit test? This is the job of a unique database column constraint. What's their specialty again?
    1
  6.  @doc8527  You know, beyond full disk encryption, there are computers running full speed encrypted RAM. It's a standard feature with rather low power requirement and negligible latency. Intel calls the feature "enclaves" and it's exactly designed for this scenario.
    1
  7. Not really. Using it to outsource the role of database manager is insane.
    1