I was able to find how to exit vim fairly easily. I do like this though it's quite funny.

Link doesn't work for me. Interested in any correlation between airpod use and making more money than Spotify, Twitter, Snapchat, and Shopify combined.... why does that even matter in this case? Do airpods read twitter feeds to you :D ?

Not a fan of those sprawling dashboards. Drivers are distracted enough.

Well you have the option of not signing in with your facebook account. Good thing about this market is that there are other options out there and presumably more coming in the future.

Yes, I have to give credit there for allowing it to be an option at least.

I find that to be true for myself personally as well.

You're not wrong. They should have focused those monies on building the actual product first and then shipping it. At that point, once the kickstarter units are built and shipped, grow your business accordingly. To have nothing to show for the efforts is deplorable.

You know I don't normally recommend books I read or have read, but both of these books below really resonate with me:

"The Hard Thing About Hard Things: Building a Business When There Are No Easy Answers": https://www.amazon.com/s?k=the+hard+thing+about+hard+things&...

"What You Do Is Who You Are: How to Create Your Business Culture": https://www.amazon.com/What-You-Do-Who-Are/dp/B07X36GGQ7/ref...

+1 for The hard thing about hard things. Definitely the book that helped me the most when I first found myself in the position of being in change.

Personally, I don't see the need to migrate entire code bases if there is no need. I think that much is obvious. Perhaps the focus should be put onto pivoting instead. That way it doesn't leave your dev team on the hook to go back and change existing code bases in python 2.

This is true. But, I think he means syntactically you can make jumps from one dbms to another without much of a fuss. Obviously there are non-language features but, that is not what is being discussed here.

That's mostly a result of databases (kinda) converging, SQL being a declarative language and it primarily being a wrapper around relational algebra, with a bunch of flags. And of course, it's a very direct interface to the RDBMS, and you're just migrating between systems that try very hard to have the same interface.

As a language however, it's a whole lot of nonsense. Extremely inconsistent syntax, stuffing a trinary logic into a boolean system, a standard that gets extended arbitrarily, and even the tooling ecosystem is a fair bit pathetic (the lack of formatters particularly annoy me; everyone tries to support SQLs generally, and end up missing every extended feature.. if it's not a simple select query/ddl, you're not getting a decent format output)

And it most certainly is a whole lot of fuss to migrate unless your database is tiny, or you didn't actually utilize the DB except as a dumb datastore (eg you relied solely on your ORM + indexes); there's a reason no good translator exists, and those that exist only support a very limited subset of any particular SQL variant, despite programming languages having a whole array of transpilers; it's simply not at all a simple language, and the variants only superficially look the same.

"As a language however, it's a whole lot of nonsense. Extremely inconsistent syntax, stuffing a trinary logic into a boolean system, a standard that gets extended arbitrarily, and even the tooling ecosystem is a fair bit pathetic (the lack of formatters particularly annoy me; everyone tries to support SQLs generally, and end up missing every extended feature.. if it's not a simple select query/ddl, you're not getting a decent format output)"

Would love to see your point in action. For me personally, speaking strictly writing simple scripts, they pretty much translate fairly well. Regarding formatting, are you referring to the output?

Dealing with Unicode in SQL has long been a backwards-compatibility nightmare.

In all fairness, dealing with unicode in general has been a pain point for me.