"SQLite says that the following query returns false: SELECT 1='1'; It does this because an integer is not a string. Every other major SQL database engine says this is true, for reasons that the creator of SQLite does not understand. " Gotta love SQLite docs
@@CentreMetreyes, more or less. Irl though data points you want to join are often inconsistent from table to table. Leading zeros in a character column being joined to an integer column without them will only match on those characters without zeros. I was recently at a job with databricks that seemed to work around this but I still didn’t trust it. I would lpad() the integers to match every time anyway.
I vividly recall when SQLite was released and support was added in PHP back in the early 2000's. People were confused why you would ever use SQLite over MySQL and for who and what use case this database was for. Truly ahead of its time.
The drawback mentioned in this video is the same drawback for any DB that replicates or shards data, it's not a libsql problem. You can only choose 2 out of 3 from the CAP theorem so you have to work around the missing 3rd.
SQLite is for when it makes sense to store application data in a SQL-like table format locally, rather than an over-complicated JSON file. The per-user DB concept is its bread and butter, what libSQL does is it lets you query across those databases. So it's effectively something between MongoDB, where all data is stored in a document for every user but on the server side, and regular SQLite.
I’ve used a similar approach where each user’s device maintains a SQLite database to store and persist any entered data locally, because it needs to work in the middle of nowhere with no internet, and then when the user returns to a location, such as the office, with a stable connection, it syncs the local SQLite DB with the main server to transfer the data over. If they happen to be in an area with good internet anyway, it just auto-syncs upon completing an entry.
Nice. That is the kind of stuff my boss didn't let me do because he considered 'a waste of time', but would then complain because the app was not reliable enough.
funny thing, I heard that specific requirement of "while offline still commit to local db, but then when online sync with main db" so many times so far in my 5 years working as software dev! And I agree with it, it takes reliability much far, specially if the app is a sorta "operations assistant"
How is security handled? That is, if they have read access to some records but not write access within the app, but they can use some other tool to write to the local database...?
noticed that too, definitely AI - that's exactly how all the "premium" Speechify voices sound - like they're trying to fit 10 sentences into a breath taken for 5.
Those sponsorships typically take a few different takes and are recorded on different days to the actual video - so it’s more a problem of his voice changing day to day
Definitely AI generated. Remember his video ages back about how he fed his videos into a voice service and now he can generate his voice? Using it for sponsorships is fine because I stop listening anyway.
Mhh. We already have so many DB systems, not sure if this one is really needed. SQLite is just so perfect. Its small, consists of just one C file, ressource friendly. Its main feature is that its almost the smallest possible way to get an (almost) complete SQL database. Most people dont use SQLite because of its featureset, but because its simplicity (and, at least I do, because its really easy to upgrade to a "real" SQL dbms later on - compared to various non-standard ways of managing the data like linked lists, tables etc.)
I really love how you refer to sharding. I attended a talk on sharding years ago and i remember talking about how unfortunate the naming is which a lot of my fellow devs didn’t pick up on right away. Glad I’m not the only one
Tell me about it. A guy was excitedly telling me about MongoDB and 'sharding' years ago before it was really popular and I said : "I need to go and shard right now" and he thought I was talking about MongoDB
Thanks. It's vital information to tell people you use Arch. If you haven't done so lately, just remind people at social gatherings. They will always appreciate this information. Also don't forget to explain further why arch is superior in a lengthy monologue at these gatherings. People will be stunned and impressed by your deep understanding of technology. Many girls will flock to your side as well.
@ “I live in my mom’s basement and I know nothing so I need to fight with someone online”. Under-appreciated because in every professional discussion anywhere in the industry it’ll be disregarded, or sometimes developers would use json based “db” on client devices, which is an absolute stupid move, or people would use something like MSSQL for an app which would at most have 1-2M rows. It is widely used yet in the professional forum, it’s under appreciated, and you’d see that in every conference etc.
@@everyhandletaken I guess but at the same time if you're going to take the time to setup a server why wouldn't you go with a proper solution like Postgres?
@ valid point & I would also agree with you there too. Maybe if it is considerably lighter weight, then there is a stronger argument for it.. not too sure. It's probably not a strong selling point, but I still do think it is pretty cool to have both options together, that is unique.
SQLite is awesome and for sure underappreciated. One of the best and easiest databases for production. iOS and Android mobile devs know this well, it really is a cool piece of tech.
I think I can speak for us all, when I say that we really appreciate that you go the extra mile to add all the humorous elements to your videos. This was one of your best.
How well your data factors into isolated silos is highly problem dependent. This works great for cross-device user settings but runs into the problems called out in the video, e.g. if you shard something like discord servers into individual databases. That's why they call it edge :) More critically though, you can paint yourself into a corner. Evolving your product, adding new uses-cases that require aggregations becomes hard to prohibitive. I find it more intuitive to start with a more central approach and then introduce caching, read replicas, on-device along the way when and where appropriate.
Based Richard Hip denying their feature creep. But to be serious I'm glad sharding hasn't been added to SQLite and I'm glad someone is making their own database that does do it.
Really cool stuff. Reinvents the wheel for what I see as minimal benefits, but everyone ought to take technologies to extremes like this at least once.
I've used SQLite for a lot things from just app data storage to using it as a front-end for other databases and file formats . I wrote a module to support Geospatial queries which opened up a lot of uses. It's really a versatile library but I'm not sure what the fork was about.
You can shard with SQLite. But nobody does because it doesn't come with this feature out of the box. SQLite has several APIs and even an entire package system that exists outside of the main database project. One of the external APIs (maintained by the author) is a live replication API for copying files while reads happen to the database. Writes are a different matter but you can fix this with caching. So you can shard with SQLite but nobody does because you'd basically need to implement the logic on your own.
Having worked extensively with SQLite I can safely say it's one of the best open source projects I've ever used. But _boy_ can you get yourself in trouble with it if you don't know what you're doing.
This seems like it'll make performing queries on (all / set of) users a nightmare. Will it need to make a whole round-trip around Earth to hit all of those databases, stream that data to a central system and then perform the query? Is this just used as an edge cache? Why a whole database to one user? Why not a table? I have so many questions, too small a video.
วันที่ผ่านมา +6
How am I supposed to absorb the content of your video when I can't stop laughing :D
I literally just interviewed with Joe Mishtachkin (one of the three dev maintainers) and at the end of the interview he mentioned he's known to be an asshole in the workplace lol. Crazy seeing this video come out just afterwards
SQLite's way of open-source is the best. Not everyone creates PR to scratch their own itch, some people create features for features, because they like everything complex, I guess. Or some create an issue that no one other has, and act like you own them the fix.
And if anything happens to the lone developer everybody who depends on that software are left with a project with no maintainer. Collaboration is great and can build great software together like Linux which would be impossible to build alone.
It's only really possible because of how insanely small SQLite is, and how few features it implements. It doesn't even have relations on by default - last time I used it it let me define foreign keys and said nothing when the relation was invalidated.
@@fred.flintstone4099 that's why in the opensource licenses is the part about warranty. No one owes you anything, bug fixes, maintenance... Feel free to fork it, or use as it is. Don't mix opensource with free labour
If you have three devs and you don't take outside contributions you don't need a CoC. Because CoCs are ways for people to get rid of contributors to a project they don't like. Well, there's three devs and no outside contributions, so if you don't like someone writing it, use something else. …and somehow I think these place locations were not random.
Considering that things such as MySQL, MariaDB, SSH, Git, Linux and probably quite some more little industry-standard tech have Finnish origins (like this one), it inspires confidence this could be successful too.
I used to think I like big databases and I can not lie. You other brothers can’t deny. Now I know I like big ideas and I can not lie. You other brothers can’t deny.
Jeff, this is how to do ads! Keep the main video untouched, switch to ad with a proper joke and show ad at the very end and let me decide if I want to watch it. This doesn't make the ad annoying and sometimes I actually want to watch it, like in this case. Ads can be useful when they're not annoying, good to learn more about Clerk.
You missed a crucially great feature: embedded replicas. You can actually have one of those read replicas not just on an edge location near the user, but literally on the user's device.
Dang it! It was hard to focus on what you were saying after that Dilbo and Tittybong. I am laughing my as* off. Now I had to replay after calming down.
I think that if some other features are required, I'd rather go with rqlite. It's based on SQLite but doesn't modify the core. All the while offering an HTTP API and clustering (even multi master!). Has been around for 10 years and MIT licensed, that's the way to go!
I love how Jeff just drops random shit in his videos that make it super risky to eat/drink while watching. Like, when he mentioned dildo the first time, I almost actually dowsed my macbook screen in coffee through my nose. Always gotta keep your audience guessing, I guess.
My only single problem with SQLite is that it doesn't support simultaneous writes. It is only okay to use SQLite for single user, as you can make sure to write sequentially. SQLite stands for Sequential-Lite it seems, not from Structured Query Language. Does libSql solve this issue? Can I write simultaneously?
"One database per user" is the most bizarre idea I have ever heard in tech. It goes against the very concept of a database. I'm curious to see how it will work in practice.
Put the database on the user's computer, and now you don't need a server! It works well when most of the user's actions only involve their own data, like personal finance
The DB per user works well for multi tenant systems like airtable. It doesn't go around the practice/concept of databases, but acknowledges the fact that users just want strict isolation of data and may have arbitrary schemas for some odd reason. This usecase covers less than 1% of apps and turso's pricing implementation only makes the usability feasible for a select handful of clients
Everytime I watch Fireship videos I try to convince myself that I know what he's talking about.
i don't think he even knows what he is talking about when he makes videos full of misconceptions
literally me
With AI do you even have to know?
@@Paulo-c3n He's talking about SQL lite, what misconceptions are you talking about?
@@Paulo-c3n Name 1
"SQLite says that the following query returns false:
SELECT 1='1';
It does this because an integer is not a string. Every other major SQL database engine says this is true, for reasons that the creator of SQLite does not understand. "
Gotta love SQLite docs
SQLITE if you don't add strict to the schema, you can use it ALMOST like a NOSQL DB, but implicit type conversions are a no go for some reason.
Im curious, why is it that other say it is true? is it just for general easy of usability of databased without having to take into account types?
I see lack of implicit type conversions to be a good thing in many contexts.
@@CentreMetreyes, more or less.
Irl though data points you want to join are often inconsistent from table to table. Leading zeros in a character column being joined to an integer column without them will only match on those characters without zeros.
I was recently at a job with databricks that seemed to work around this but I still didn’t trust it. I would lpad() the integers to match every time anyway.
@@samiraperi467i think im braindead but does this mean no defined types is good in many contexts or that defined types are good in many contexts
0:45 unauthorized backdoor penetration is wild😭
the whole video is wild XD
Pfft, try living in dildo 😉
I have not laughed that hard in a long time.
Man knows how to turn me on 🥵
Jesus Christ.
I vividly recall when SQLite was released and support was added in PHP back in the early 2000's. People were confused why you would ever use SQLite over MySQL and for who and what use case this database was for. Truly ahead of its time.
Pieter Levels making millions with all his companies all on only SQLite convinced me. SQLite is awesome.
I was definitely confused
I'm more confused as to why anyone would use PHP
@@T-Ball-o because it is good at making web applications without any fuss especially nowadays
SQLite is so nice exactly because it doesn’t have all those fancy extra features. Simple, compact, efficient. It’s perfect.
Authentication would be nice though
@@74GeeI feel like authentication is out of scope for an *embedded* DB vs a *client-server* DB
@@74Gee It doesn't make sense for it's use case
Exactly. When he said that libSql supports triggers, it was a PTSD trigger for me.
@@74Gee chmod + chown db file then :/
The drawback mentioned in this video is the same drawback for any DB that replicates or shards data, it's not a libsql problem. You can only choose 2 out of 3 from the CAP theorem so you have to work around the missing 3rd.
And there's no such thing as a true relational database, enforcing the 13 rules of Codd!
@@iAPX432 the 13 rules of what? A fish?
@@NathanBrownisawesome Boyce Codd
@@iAPX432still very hard to keep with all the kcid requirements when you only have the sllab to work with on the pit
@@iAPX432 not familiar with Codd, but what do you think of Graph databases? In my opinion, those are the true relational databases.
"...big win for the Dildo user." lol... I died.
Tell me about the last video you watched… “I watched a video about dildo users.”
hey that's me
The Dildo tourism board lmao
Bad Dragon or GTFO.
Also with the intonation on “user” lol
Back-door penetration 😂
by Dildo user.
@ 😅
Just as sweet as St Lucia!!
Brian.. brian!... hes.. hes knockin on the back door!!! Should I let him in?? Im scaarreddddd!!!!
SQLite is for when it makes sense to store application data in a SQL-like table format locally, rather than an over-complicated JSON file. The per-user DB concept is its bread and butter, what libSQL does is it lets you query across those databases. So it's effectively something between MongoDB, where all data is stored in a document for every user but on the server side, and regular SQLite.
i use sqlite a lot and the libSQL cross feature sounds amazing
I’ve used a similar approach where each user’s device maintains a SQLite database to store and persist any entered data locally, because it needs to work in the middle of nowhere with no internet, and then when the user returns to a location, such as the office, with a stable connection, it syncs the local SQLite DB with the main server to transfer the data over.
If they happen to be in an area with good internet anyway, it just auto-syncs upon completing an entry.
Nice. That is the kind of stuff my boss didn't let me do because he considered 'a waste of time', but would then complain because the app was not reliable enough.
funny thing, I heard that specific requirement of "while offline still commit to local db, but then when online sync with main db" so many times so far in my 5 years working as software dev!
And I agree with it, it takes reliability much far, specially if the app is a sorta "operations assistant"
Did the same thing myself. Just name the sqlite file per user.
How every database should be.
How is security handled? That is, if they have read access to some records but not write access within the app, but they can use some other tool to write to the local database...?
> They don't even have a CoC
They have Code of Ethics. Very sufficient.
What are those means?
@@TheVirtualArena24 Clash of Clans
@@TheVirtualArena24code of conduct
@@_hoaxx ok kiddo
@@infinitespace1982 ik full form I mean what they are exactly?
3:08 Nice town names for the example
3:51 your voice changes. Are you getting sick or you actually started using voice synthesizers now?
AI generated Fireship
noticed that too, definitely AI - that's exactly how all the "premium" Speechify voices sound - like they're trying to fit 10 sentences into a breath taken for 5.
Those sponsorships typically take a few different takes and are recorded on different days to the actual video - so it’s more a problem of his voice changing day to day
He said years ago on his second channel he has many mics
Definitely AI generated. Remember his video ages back about how he fed his videos into a voice service and now he can generate his voice? Using it for sponsorships is fine because I stop listening anyway.
1:20 SHARTING! have been thinking about this ever since I’ve learnt about sharding
Mhh.
We already have so many DB systems, not sure if this one is really needed.
SQLite is just so perfect. Its small, consists of just one C file, ressource friendly.
Its main feature is that its almost the smallest possible way to get an (almost) complete SQL database.
Most people dont use SQLite because of its featureset, but because its simplicity (and, at least I do, because its really easy to upgrade to a "real" SQL dbms later on - compared to various non-standard ways of managing the data like linked lists, tables etc.)
I really love how you refer to sharding. I attended a talk on sharding years ago and i remember talking about how unfortunate the naming is which a lot of my fellow devs didn’t pick up on right away. Glad I’m not the only one
Tell me about it. A guy was excitedly telling me about MongoDB and 'sharding' years ago before it was really popular and I said : "I need to go and shard right now" and he thought I was talking about MongoDB
*sharting
I woke my wife laughing when you chose your second random location :-D
Based 🗿
Data based
programmers don't have wives
Saddest shit I have ever read lmao you're alone in this bruh@@kaustubhkadam1083
Correct. They have husbands instead.@@kaustubhkadam1083
cool but i use ARCH, btw
TempleOS is better; it even lets you with God!
unrelated
Thanks. It's vital information to tell people you use Arch.
If you haven't done so lately, just remind people at social gatherings.
They will always appreciate this information.
Also don't forget to explain further why arch is superior in a lengthy monologue at these gatherings.
People will be stunned and impressed by your deep understanding of technology.
Many girls will flock to your side as well.
Gentoo, by the way!
NixOS user laughs in
“SQLite is under-appreciated” so true, can hold so much data for any medium sized project, without all the extra resources.
How can the most commonly used DB in history be under-appreciated? That's an absolute oxymoron.
@ “I live in my mom’s basement and I know nothing so I need to fight with someone online”. Under-appreciated because in every professional discussion anywhere in the industry it’ll be disregarded, or sometimes developers would use json based “db” on client devices, which is an absolute stupid move, or people would use something like MSSQL for an app which would at most have 1-2M rows. It is widely used yet in the professional forum, it’s under appreciated, and you’d see that in every conference etc.
Turning SQLite into a daemonised SQL server seems like the opposite of what it's going for
For sure, but it is pretty neat to have both options in one here
@@everyhandletaken I guess but at the same time if you're going to take the time to setup a server why wouldn't you go with a proper solution like Postgres?
@ valid point & I would also agree with you there too.
Maybe if it is considerably lighter weight, then there is a stronger argument for it.. not too sure.
It's probably not a strong selling point, but I still do think it is pretty cool to have both options together, that is unique.
SQLite is awesome and for sure underappreciated. One of the best and easiest databases for production. iOS and Android mobile devs know this well, it really is a cool piece of tech.
SQLite doesn't just power pocket base it's used by everything that needs a local database including web browsers
I’ve never expected Newfoundland to make fire ship, you have to now start a cod kiss as a service
bro finally took a break from the AI shit 🙏🙏🙏
Mentions ai some way in
That’s what he wants you to think. Listen to the audio change starting at 3:50
He still managed to reference AI a few times.
Been using this with turso to implement per-user db's in our application and it works like a charm. Headache on migrations though😅
I think I can speak for us all, when I say that we really appreciate that you go the extra mile to add all the humorous elements to your videos. This was one of your best.
love the image at 0:45 for "unauthorised backdoor penetration"
4:13 Jeff banning himself.
3:19 when you start laughing so hard you're no longer listening.
If you was laughing that hard at dildo and tittybong then you’re either really young or really high. Or…both
@@Coopek4 or he is not numb to these jokes like you. Laughing doesn't mean he's young or high. Don't be an idiot
Oh boy I love the examples given on this channel... 😂
I'm sold on the sponsorship, will add the town to my bucket list
i have no idea what you are talking about, but i keep watching your videos hahaha
Here for the sense of humour
This episode was about dildos.
did you use AI voiceover from 3:50 onwards?
Lol I also noticed
Sounds like he got a sore throat all of a sudden.
The voice is somewhat painful to listen to. I think it's the manic speed and cutting away everything vaguely resembling silence between words.
I'm gonna guess he recorded it at a different time, then edited it down more agressively
CoC's have caused more fighting than they've prevented. Change my mind.
No I won't. Fite me.
How well your data factors into isolated silos is highly problem dependent. This works great for cross-device user settings but runs into the problems called out in the video, e.g. if you shard something like discord servers into individual databases. That's why they call it edge :)
More critically though, you can paint yourself into a corner. Evolving your product, adding new uses-cases that require aggregations becomes hard to prohibitive. I find it more intuitive to start with a more central approach and then introduce caching, read replicas, on-device along the way when and where appropriate.
Based Richard Hip denying their feature creep. But to be serious I'm glad sharding hasn't been added to SQLite and I'm glad someone is making their own database that does do it.
Really cool stuff. Reinvents the wheel for what I see as minimal benefits, but everyone ought to take technologies to extremes like this at least once.
There is also rqlite based on the raft protocol.
It's not a fork but still a very interesting approach to a distributed DB.
0:04 now that video is a blast from the past, hot damn
I've used SQLite for a lot things from just app data storage to using it as a front-end for other databases and file formats . I wrote a module to support Geospatial queries which opened up a lot of uses. It's really a versatile library but I'm not sure what the fork was about.
My biggest gripe with sqlite is... people still calling it under-appreciated when it clearly isn't. :D
Buddy from the video you solved my biggest problem of my product thanks
You can shard with SQLite. But nobody does because it doesn't come with this feature out of the box. SQLite has several APIs and even an entire package system that exists outside of the main database project. One of the external APIs (maintained by the author) is a live replication API for copying files while reads happen to the database. Writes are a different matter but you can fix this with caching.
So you can shard with SQLite but nobody does because you'd basically need to implement the logic on your own.
I didn't know this existed. I appreciate the introduction, and laughs.
Having worked extensively with SQLite I can safely say it's one of the best open source projects I've ever used. But _boy_ can you get yourself in trouble with it if you don't know what you're doing.
1:35 the thing that real inspired me was this add by clerk
This seems like it'll make performing queries on (all / set of) users a nightmare. Will it need to make a whole round-trip around Earth to hit all of those databases, stream that data to a central system and then perform the query? Is this just used as an edge cache? Why a whole database to one user? Why not a table? I have so many questions, too small a video.
How am I supposed to absorb the content of your video when I can't stop laughing :D
Hahahaha I lost it in the "MySQL / OurSQL" Meme. You are the best Jeff. I love you
I commented too soon! Dildo and Tittybong got me harder! LOL
I wonder how much time was spent finding the best cities names for the videos
He said they were chosen at random
@@mihailkondov4773 "random" takes time to be sure
I was adament that the members of Muff Diving Club, Donegal Ireland would make it to this video. Disapointed
I literally just interviewed with Joe Mishtachkin (one of the three dev maintainers) and at the end of the interview he mentioned he's known to be an asshole in the workplace lol. Crazy seeing this video come out just afterwards
Well that's super exciting. So many possibilities. I just started toying with sqllite and this would be an amazing tool. Thank you.
SQLite's way of open-source is the best. Not everyone creates PR to scratch their own itch, some people create features for features, because they like everything complex, I guess.
Or some create an issue that no one other has, and act like you own them the fix.
And if anything happens to the lone developer everybody who depends on that software are left with a project with no maintainer. Collaboration is great and can build great software together like Linux which would be impossible to build alone.
It's only really possible because of how insanely small SQLite is, and how few features it implements. It doesn't even have relations on by default - last time I used it it let me define foreign keys and said nothing when the relation was invalidated.
@@nestwr not every opensource is Linux or Kubernetes
@@fred.flintstone4099 that's why in the opensource licenses is the part about warranty. No one owes you anything, bug fixes, maintenance... Feel free to fork it, or use as it is.
Don't mix opensource with free labour
that's freaking awesome dude! I didn't know all that data about libSQL and definitely gonna check clerk, peace
What a coincidence, I just used it for the first time yesterday. Great video!
I love that my favorite DB solution is getting some love on my favorite tech clickbait.
You are the best content creator for me now, thank you
I love SQLite. It's so simple and easy to deploy. I use it whenever it's possible.
If you have three devs and you don't take outside contributions you don't need a CoC. Because CoCs are ways for people to get rid of contributors to a project they don't like. Well, there's three devs and no outside contributions, so if you don't like someone writing it, use something else.
…and somehow I think these place locations were not random.
I was absolutely dying by the end of this one. What a video!
"Make your sqlite available over the network" -- how to make your security engineers cry
I smell a lawsuit 3:05
At this point, bro can start a comedy stand-up.
This was one of the funniest vids from fireship.
Considering that things such as MySQL, MariaDB, SSH, Git, Linux and probably quite some more little industry-standard tech have Finnish origins (like this one), it inspires confidence this could be successful too.
I used to think I like big databases and I can not lie. You other brothers can’t deny. Now I know I like big ideas and I can not lie. You other brothers can’t deny.
I love the AI chalkboard: "for all lambdas in the functional group R"
Jeff, this is how to do ads! Keep the main video untouched, switch to ad with a proper joke and show ad at the very end and let me decide if I want to watch it. This doesn't make the ad annoying and sometimes I actually want to watch it, like in this case. Ads can be useful when they're not annoying, good to learn more about Clerk.
It's great actually instead of relying on too costly cloud APIs, one can use SQLite web version for study, and start-up projects.
You missed a crucially great feature: embedded replicas. You can actually have one of those read replicas not just on an edge location near the user, but literally on the user's device.
Dang it! It was hard to focus on what you were saying after that Dilbo and Tittybong. I am laughing my as* off. Now I had to replay after calming down.
Truly one of the databases of all times
I think that if some other features are required, I'd rather go with rqlite. It's based on SQLite but doesn't modify the core. All the while offering an HTTP API and clustering (even multi master!). Has been around for 10 years and MIT licensed, that's the way to go!
We need random locations in every future video
I was in AU last year. I can't believe I never knew about Tittybong. I guess I need to go back like rn...
Is "OurSQL" out yet?
No because we're living in a capitalist world
Excellent choice of locations. $GENDER of culture!
Past the d*ldo time mark, I didn't hear anything you said. 😂
Fun and informative! Thanks!
I was listening to this walking around the supermarket and looked like a lunatic laughing to myself
SQLite has its tradeoffs, like write locking. You have to implement queuing by yourself. It's just a file after all
Fireship's voice in the ad section sounds different from his voice everywhere else in the video
Why was there a flamboyant Justin Trudau when you brought up Dildo Newfoundland lol?
Dildo user
Clerk is a very proud business partner
I love how Jeff just drops random shit in his videos that make it super risky to eat/drink while watching. Like, when he mentioned dildo the first time, I almost actually dowsed my macbook screen in coffee through my nose. Always gotta keep your audience guessing, I guess.
1:56 i felt that one
Fireship a secret Newfie? Awsome
Great example of how the best softwares are unknown because they don't mess up
Woo! Newfoundland mentioned!
My only single problem with SQLite is that it doesn't support simultaneous writes.
It is only okay to use SQLite for single user, as you can make sure to write sequentially.
SQLite stands for Sequential-Lite it seems, not from Structured Query Language.
Does libSql solve this issue? Can I write simultaneously?
The 1 database per user thing is probably useful if each user is a company. Lets you sell the same thing over and over again to different clients
I couldn’t focus on the example scenario because I was wondering the whole time was this means for users in Ramtown, NJ
Can you do a video on Flock sometime?
This video made laugh so hard my family got worried about my sanity
Getting SQLite is worth every cent of military industrial complex contracts ever given.
Under a mintue review .... Woah !!!!
Was that an AI Jeff in the sponsor read?
this is the future, now users need to learn how to control their own database
Now i can add 3 years experience of libSQL to my resume
"One database per user" is the most bizarre idea I have ever heard in tech. It goes against the very concept of a database. I'm curious to see how it will work in practice.
Put the database on the user's computer, and now you don't need a server! It works well when most of the user's actions only involve their own data, like personal finance
The DB per user works well for multi tenant systems like airtable. It doesn't go around the practice/concept of databases, but acknowledges the fact that users just want strict isolation of data and may have arbitrary schemas for some odd reason. This usecase covers less than 1% of apps and turso's pricing implementation only makes the usability feasible for a select handful of clients
I think the idea is to eliminate the backend? Just the app/frontend and the db connection of all the data a user could need
Butt it depends
@@upsidedowntree9431 Synchronization between devices will be a pain