1,356 karma · joined August 24, 2013
It's just that people tend to use specialized tools for encoding and decoding it instead of like ",".join(row) and row.split(",")
I have seen people try to build up JSON strings like that too, and then you have all the same problems.
So there is no problem with CSV except that maybe it's too deceptively simple. We also see people trying to build things like URLs and query strings without using a proper library.
There is no faster way to make a fork the de facto standard version than to break everyone's CI builds.
[1] https://luajit.org/download.html
Nobody can stream 2x 4K to my Apple VR headset. I can barely get a single 4K stream to my TV!
It needs very high-res video streams which basically no internet provider/CDN can offer at scale. 40Mbps+ HEVC just isn't scalable. So the only content is whatever can be downloaded to the device itself. A few games? A cool screensaver experience? It's all cool, but mostly novelty tech.
> The Android team has observed that the rollback rate of Rust changes is less than half that of C++.
I've been writing high-scale production code in one language or another for 20 years. But I when I found Rust in 2016 I knew that this was the one. I was going to double-down on this. I got Klabnik and Carol's book literally the same day. Still have my dead-tree copy.
It's honestly re-invigorated my love for programming.
For one, it's enormous. Now you have to copy that 128bit int to every side of the relation.
Two, in most cases it's completely random. Unless you had the forethought to use something other than UUIDv4 (gen_random_uuid). So now you just have a bunch of humongous random numbers clogging up your indexes and duplicated everywhere for no good reason.
Use regular bigserial (64bit) PKs for internal table relations and UUIDs (128bit) for application-level identifiers and natural keys. Your database will be very happy!
Anyway. I just use Postgres.
> > And they're always lazy, so you never really know when the N+1s are going to happen.
> There are tools to detect this. Please use them regardless. Even if you're writing queries but hand, enough functions on the stack can hide an N+1
I don't want to have to use a tool to "detect" anything. I want my queries to return exactly what they're expected to return, or my code will fail. No surprises.
Just write SQL. I figured this out when I realized that my application was written in Rust, but really it was a Postgres application. I use PG-specific features extensively. My data, and database, are the core of everything that my application does, or will ever do. Why am I caring about some convenient abstractions to make it easier to work with in Rust, or Python, or whatever?
Nah. Just write the good SQL for your database.
I lost my phone, though. There's no prompt they could send me.
> I believe Google can send a similar prompt to YT or GMail apps
There was no phone, anymore. No way to prompt.
I forgot my backup code, so now I can just never use Uber again.
Lesson learned!
(you see how ridiculous this is, right?)
Uber accounts are tied to phone numbers. Should I get a new phone number just because Uber's support bot is incapable of helping me recover my account?
Or at all?
It was fun to play with it for a couple months. But there's no business here. Twitch.tv is also finding that out.