The real ORM is the friends we made along the way -- Our Real Mates

@NexusGamingRadical

Жыл бұрын

Nice sql comment at the end there. Very explanatory.

@peterszarvas94

Жыл бұрын

It's about the vulnerabilities we made along the way

@VikashXman

Жыл бұрын

eval(node run test)

@Y2Kvids

10 ай бұрын

And Tables We Dropped

@ZM-dm3jg

9 ай бұрын

I made friends with ChatGPT along the way

0:20 (S-Q-L), 0:31 (Squeal), 0:52 (Sequel) He pronounced SQL all three different ways so everyone is happy 😂

@jorgechristophergarzasepul3209

Жыл бұрын

Or everyone angry

@joshuapare4304

Жыл бұрын

don't tell that to @ThePrimagean, clearly only one of those is truly correct

@maheshprajapati9441

Жыл бұрын

Squirrel gang

@cristophermoreno2290

Жыл бұрын

gold

@Draghful

Жыл бұрын

I just wanted to point that out. My brain was like "dafuq am I hearing?!?" 🤣

I watched this video again to remember the differences between certain libraries and ORMs so I made a list: 1. 1:30 pg 2. 3:24 postgres.js 3. 4:11 knex 4. 5:20 kysely 5. 6:13 sequelize 6. 7:11 typeorm 7. 7:55 prisma 8. 8:51 drizzle-orm May this be helpful to someone else as well.

@heegj

Ай бұрын

+1, need those youtube chapters

The timing of this video is impeccable. Been spending the last few days looking into these ORMs

@Showmatic

Жыл бұрын

same, and I'm learning towards drizzle

@pomberorajy

Жыл бұрын

same x2

@cristinel1

Жыл бұрын

Same x3

@er3n_

Жыл бұрын

just write SQL

@LuisSierra42

Жыл бұрын

Been using sequelize and typeorm recently

MikroORM should be on this list. Has all the benefits of an ORM, but lets you easily fall back to a Knex-like query builder when needed. And crucially, it's much better maintained than Sequelize or TypeORM

@tronikel1434

Жыл бұрын

yep, really a shame that mikro orm is not well known, its superb

@nifalconi

Жыл бұрын

It’s amazing. Like the best thing ever. The only sad thing is that there’s like one maintainer/creator. The guy is amazing ❤

@EulerJr_

Жыл бұрын

I agree! And MikroORM works great with MongoDB too.

@bedirhancelayir3295

Жыл бұрын

Definetely agree

@alexnezhynsky9707

Жыл бұрын

Yes, B4nan is a superhero

This video is so well timed, I was literally transitioning from Firestore to Postgres database with a project just now.

@moyin1038

Жыл бұрын

Bro same 😂

This guy has the most useful content, without wasting any time.

Breaking world record for most useful information per second of video each time you post someting. Respect, Sir!

I can understand the Web dev community generally straying away from writing raw SQL, but as an analyst moving to Javascript from having written primarily SQL for the past 6yrs it can be a bit frustrating that the whole ecosystem is based on trying not to do what I'm most comfortable doing - it feels like my mad SQL skills are being somewhat nullified! Great vid Jeff, I haven't seen postgres js before - I will defo be using it.

@ahmad-murery

Жыл бұрын

I'm not an analyst but I used to do a lot of raw sql and still find it easier to me than using ORMs especially for complex queries where (sub-queries, CTE, aggregation with OVER clause and maybe make use of sql variables, procedures, functions and temp tables) is needed. Simply I'm more comfortable with SQL and it's easier for my to translate my ideas directly into what the Database can understand natively. I feel you

@igalklebanov921

Жыл бұрын

You should give Kysely a try. We focus on 1:1* and have CTEs, window functions, etc. But also type-safety and autocompletion.

@ahmad-murery

Жыл бұрын

@@igalklebanov921 Looks nice and intuitive for one with average sql background, I'll give it a try once I have a chance. Thanks

@matthewrutter8343

Жыл бұрын

Programmers hate being embarrassed. That's why they go to orms. It allows them to ignore the holes in their skill set while being able to goldplate over things for no reason to feel important. 100% ego.

@ahmad-murery

Жыл бұрын

@@matthewrutter8343 Maybe you have a point regarding the skill holes, but maybe it's the other way around as I myself find it very hard to memorize ORM methods, in the same time I can easily do what I want using raw SQL, this caused me some embarrassment in a project I was a member of, so to the others this was a hole in my skills. I'm a programmer with bad memory😎

Best ORM is either no ORM or one that auto-generates the access layer based on the structure and types you've already defined in the database. Anything in between is just excess heat and trauma.

Awesome job Jeff. Thanks for creating such a concise and entertaining video.

I was less inclined to watch this earlier but, hey man, you rocks. Lots of clear and concise stuff in the video.

Awesome video! And amazing that you're giving a free consultation, people should flock for that!

Hours of research without real outcome and then one video and I know what to choose. You're my favorite KZreadr for a reason. 😋

Rails, Django, Laravel, and Phoenix developers: Yay!! We don't have to deal with this JavaScript madness.

@sushantjain3360

Күн бұрын

then they face problems in scaling

Great video. I'd enjoy an overview of ORMs in other languages too, such as SqlAlchemy, Entity Framework, etc.

Thank you. Perfect timing, that exactly what i'm looking for.

I prefer writing raw sql queries. Orm tend to make simple things simpler and hard things harder

@igalklebanov921

Жыл бұрын

You should try Kysely. Its all about trying to be 1:1* to compiled SQL (WYSIWYG design principle) and aims at supporting advanced functionality ORMs just don't bother going into or can't.

@lechi_2002

Жыл бұрын

I agree with you. Also debugging raw queries is much easier as you copy the sql string and execute it manually.

@MinibossMakaque

Жыл бұрын

Absolutely. Plain SQL with prepared statements all the way. ORMs solve one problem while making a giant headache of everything else, other than maybe migrations. I don't know why the most widely adopted approach to a vulnerability was to abstract away the entire language.

@ba8e

Жыл бұрын

@@MinibossMakaque I will never fucking understand the insanity of ORM. Literally makes everything worse, a useless abstraction.

@LuisSierra42

Жыл бұрын

Except when you have tons and tons of complex queries and that sometimes occupy and entire file

Have a lot of projects in production. Some of our codebase accesses MySql, PG and SQLite, so Knex is our definitive tool. Also it handles transactions like a charm.

The two reasons to use an ORM such as Prisma and TypeORM is so you get types for your code and so you don't have to update every single query when you update a column to a table.

@furycorp

Жыл бұрын

In my experience with anything beyond a todo list both of those fall apart and have a lot of oversights that are a pain in the ass.

@Slashx92

Жыл бұрын

@@furycorp I agree. It's more of a "pick your poison" issue with orms vs querybuilders vs sql clients although I would argue the last one is the less scaleable by far

@ooogabooga5111

Жыл бұрын

prisma is okey for hobby simple projects but will fall out of hands when it gets complex with logic. Also there is no native joins.

@ooogabooga5111

Жыл бұрын

prisma won't scale up

@clingyking2774

Жыл бұрын

TypeORM is the only ORM that actually makes sense because Java uses a similar pattern and Java is Holy.

If you need advanced postgresql like views, materialized views, PostGIS I would recommend to use pg, choosing the right ORM depends on your project requirements so you must study first what features you will need and do research for the best of your needs

I'm currently using pg + postrgrator for migrations + sql-ts to generate types from DB. Works like charm. Type checking of sql is done by my IDE (intellij) anyway.

MikroORM is awesome and deserve more love. It does what all these ORM do and is battle tested, fast, and well maintained.

@nicky-hajal

Жыл бұрын

I have been looking into MikroORM and confused why it doesn't get much attention and review by the community.

When using pg, run your migrations and then use schemats to dynamically generate typescript types from the db itself for great type safety.

Long live typesafe query builders (aka Kysley and Drizzle ORM)

@SogMosee

3 ай бұрын

yassssssssss

lol, the ending was perfect :D well done Mr Fireship

Snuck in a video in response to the codedam issues with Prisma. Like your approach here - mentioning all pros and cons, going over each option. Great work!

sequelize has been my go to for small project for about 5 years.

this is gonna be very useful for my typescript api, living and leaning...

A video about correct ways to hande migrations for multiple teams would be very handy!

@rajeevkl6966

Жыл бұрын

use rails/laravel/django everyone can do their own migrations & it rarely conflicts

Out of every ORM I've ever used, my favorite experience was using Ecto [Elixir programming language]. Note that this language, and also ORM, have a pretty steep learning curve, so it can seem obtuse at first. Other ORMs I've used include Django, SQL Alchemy, ActiveRecord, and a couple JavaScript ones.

@c0ldfury

10 ай бұрын

Quarkus reactive is pretty sweet. But for sheer performance Go and Elixir libraries seem unbeatable.

I also like what Supabase did with their new CLI, although not exactly an ORM. It generates typescript types for you based on the tables that you make inside of the dashboard, which you use with the SDK to make safe queries. One of the easiest ways to get a great DX with SQL in my opinion.

The issues that you've mentioned using raw SQL queries can be solved by using SafeQL. Zero abstractions, zero runtime code.

@RasmusSchultz

Жыл бұрын

Yes, please. The best ORM is no ORM 🙂👍

After experience with most of orms, Objection has the best developer experience with great performance

@igalklebanov921

Жыл бұрын

Have you tried Kysely? koskimas is the author behind both of them. :)

Thank you man. This is really helpful.

First 20 seconds of this video, the story of my life! :D Great job making these videos fun, so we can all have a bit of a laugh and not take ourselves too seriously, especially when it comes to the technology stack used. I've also made a video on this topic on my channel recently.

For Postgres PgTyped is an awesome project. You write bare SQL and it typeschecks agains the databse and generates query methods that are comletely typesafe, even with complex joins or recursive queries.

@simonboddy7415

9 ай бұрын

This is how god intended us to use databases. Its so simple, so powerful, such superior performance. It's just amazing how long this approach took to surface, and how little known it is.

@EDemircivi

5 ай бұрын

damn. I just learned about PgTyped, thanks to this comment. it is a gods gift.

I was gonna try typeORM a year ago, but found many articles warning not to use it because it wasn't maintained and had lot of issues. I have tried sequelize, it's great but it needs a lot of setup and it doesn't fully support typescript. I was gonna try Prisma recently, but then someone said that it had issues too with the Rust engine and that there being too much "overhead" and that it was bad for joins. Not to mention that your code would be third party dependant, as Jeff stated. Would really like a video about the underlying structure and flow in ORMs and their tradeoffs, not just about syntax. Appreciate your work :)

@WolfrostWasTaken

Жыл бұрын

Prisma only gives issues with the Rust backend if you plan on deploying it on a lambda function or using serverless in general. And you can still solve all of these issues, it just requires more work and it's not "out of the box".

@buzz1ebee

Жыл бұрын

Typeorm is actively maintained at the moment. There was a year or so where things were stable, but since v0.3 it's been fairly regularly updated.

@h3nry_t122

Жыл бұрын

the only issue with Prisma is when using server less. thats the only problem. if you're not using server less then you're perfectly fine.

bests one mentioned at 9:45 ~ saved you some time !

The first 20 seconds are the most accurate stuff ever. I start with MSSQL and then switched to MongoDB and I was like "Yeah this is the best, I will never go back to sql" yeah but ... years later I'm now working only with MySql and I like it way more then mongo ... Currently using sequelize and the work is so easy to do.

Nice to have Eloquent ORM baked right in the Laravel Framework providing all of these and more features out of the box.

At my dayjob the application teams write raw SQL queries because they can't replace the ancient ORM that came with the framework. Some developer wrote an abstraction library over the database connector that is actually quite nice. You construct a Query object. For example new GetUserById(id); And then do $q->result($db); which yields you the User object you were looking for. Or null.

Using intellij sql intellisense in the code is way better than every orm can ever been.

@omri9325

Жыл бұрын

🤮

@h3nry_t122

Жыл бұрын

well damn.

@gawwad4073

Жыл бұрын

ORMs are cancer

Hey there fireship, sequelize doesn't support typescript but there's a new sequelize-typescript that does, it would've been nice if you did that.

@Ke5o

Жыл бұрын

Sequelize does actually support Typescript if you look through the docs, but it's annoying to set up and mostly scuffed in my experience. It's not an easy drop in.

@daleryanaldover6545

Жыл бұрын

@@Ke5o it was so scuffed that they need to re-write most of the features when releasing v7

Drizzle for the next Project.

Thank you so much for this was struggling to choose an ORM to use till now

in my opinion they are all good options and I would just look at what saves me the most time and works good with typescript. So I usually go with prisma :) Having said that if you are just a beginner you might wanna go with the orm's that you have to use raw SQL so you know how everything works.

@ooogabooga5111

Жыл бұрын

prisma won't scale up

@nithin3476

11 ай бұрын

@@ooogabooga5111 hey what about drizzle

@IDOLIKIofficial

10 ай бұрын

@@ooogabooga5111 How is that so? I use prisma on applications with 3M MAU. Loads pretty fast for everyone

“joist-ts” is an awesome option for graphql + Postgres - has dataloader built in so any graph queries are N+1 safe. Reminds me a lot of ActiveRecord for Rails

Absolutely love intro!!!!

Joist is also interesting. It really focusses on great Typescript and lazy loading support while also automatically solving n+1 problems.

@ooogabooga5111

Жыл бұрын

@@beyondfireship.. lmao

My conclusion is that as long as you use raw SQL with the chosen ORM's raw method, you will have control over the performance. However, when you start using their innerJoin built-in methods, you may encounter performance issues. Nonetheless, using raw SQL for complex queries defeats the purpose of using an ORM. This raises the question of which ORM to use that provides a good migration tool and a well-defined schema with types. I believe ORMs are suitable for simple projects, but when it comes to large projects with complex queries and performance optimization requirements, they may not be ideal. Therefore, you will most like be using the ORM for defining schemas and migrations and writing raw SQL for most queries.

@igalklebanov921

Жыл бұрын

You should try a query builder like Kysely instead of going raw SQL in complex queries. We're trying to be 1:1* with compiled SQL and go deeper than ORMs usually do - as long as it can be implemented in a type-safe way.

Been using sequelize, and typeorm and typeorm is the most comfortable to me

Man That Ending !!! Super

I'm developing a webapp and used MongoDB Atlas for it and Mongoose makes my life easier. But then I realized I'm better off with a relational database because there's a lot of relational data on my backend. I chose Postgres and studied Sequalize and I like how Sequalize is very similar to Mongoose. However, I also came to the conclusion that Supabase will make my project easier to maintain. So I signed for Supabase only to notice that there's no ORM for it. Everything is interfaced through the Supabase API. To manipulate data before they get stored in the database, you would need to write database functions, edge functions and triggers. Creating schemas, constraints, indexes, and RLS policies need to be written in SQL (though some of these can be done through the UI). Supabase was supposed to simplify a lot of stuff, but I'm finding it time-consuming to set up a lot of things. Why can't it be as easy a Sequalize?

@foreach1

Жыл бұрын

Supabase is a normal Postgress db. You can use any orm you want with it

@tj_mora

Жыл бұрын

@@foreach1 You can only use these ORMs if you have a server-side middle layer between the client and supabase. But obviously if you do that, then why not just use a self-hosted Postgres cluster? We use Supabase for the ability to remove the server-side middle layer. So it's just Supabase and client-side. And you can't really use any ORM for any of these sides. I actually like that approach and I can see it being easier to maintain in the long run. But damn the set up is hard. Migration is hard. Supabase docs are garbage. And Supabase tutorials on KZread doesn't really cover the very specific database needs/designs that I have. Though I'm pretty sure if I study this more for several more days I can finally get the hang of it.

@IlllIlIlllIIIllIl

11 ай бұрын

oh my god ..mongodb..........

I love the "Data Suppository". :D

Love the ending :)

being a laravel developer feels like a ghoast or a stranger when you watch these videos

I really wish you mentioned joist, it’s TS backed and has facebooks data loader baked in at its core, allowing you to bundle similar queries together each event loop tick to reduce amount of queries you make to the db!

That snoop dogg line was absolute gold.

Alright, now just to figure out how to shove a frickin' matress into my backend so my project won't fail. Thanks for the advice!

I personally love supabase‘s approach best - you have a GUI to create and update tables or columns

that clifhanger man, still waiting for the final result :D :D lol

0:38 using libraries & ORMs to access SQL to: * get IDE language server completions * migrations * connect to db * handle security * madelling relationships in data

I can just tell you are a boyscast listener by some of your phrases and I love it.

Prisma internally has large overhead because of all these abstraction layers, a regular SELECT query took over 100 ms while an identical query in TypeORM took 10 ms or so

Prisma for migrations (ddl), Kyseley for interactions (dml)

@igalklebanov921

Жыл бұрын

❤from Kysely.

After 15 years of backend development (on the JVM though), I'll take a query builder over an ORM every time. Also: Migrations "down" are usually not worth your time (how to roll back a dropped column or table anyway?)

@F38U

Жыл бұрын

Eloquent is not that bad tbf

@IvanRandomDude

Жыл бұрын

Same. I used Spring Data JPA back in the day until I discovered jOOq.

Lol the first bell curve is literally me right now. I'm heading down the other side.

Enjoying using Prisma along with Redwood JS at the moment, but the lack of support for PostGIS and spatial types is a bit of a drawback at the moment. Hopefully that support comes soon.

Might check Mikro-orm as well.

I worked extensively in one of the ORM that’s Eloquent which Laravel uses which is a PHP framework

Laravel's built in ORM, Eloquent is pretty good too!

I made a similar research a while ago, I ended up using Prisma, it's a grate tool, great CLI, Fantastic Types if the DB is structured well, but I think you lose some performance specially when you do joins. I was thinking of using Prisma only for TS and migrations. and for complex queries, I might using raw SQL. I also faced an issue learning the Prisma schema file, but I used another way to evade learning new markup language. so first I write my sql changes in the DB, run "prisma db pull" , then drop/delete db changes, then run "prisma migrate dev"

@KellenBricks

11 ай бұрын

i use prisma for migrations only and write raw sql for all the queries. pgtyped helped me to type all the queries automatically. highly recommend using this setup.

I worked at a company that did everything with raw sql. We had a about 100 tables and it worked great. This is not a typical apparently.

@igalklebanov921

Жыл бұрын

Until you need to do some things dynamically, conditionally or repetitively, and end up maintaining your own query builder. Just use a query builder. :)

@dexterantonio3070

Жыл бұрын

@@igalklebanov921 I agree with that. I had some code that involved string concatenations to form an and string for an internal data science application. I began using a query builder right before I left to replace that annoying and unsafe code.

@aurelianspodarec2629

6 ай бұрын

@@igalklebanov921 NextJS 13 exists

"With great abstraction, comes great dependency." - Uncle Ben

I'm convinced this is the kind of stuff Fireship does for fun when he's bored.

Entity framework + LINQ, saves you a ton

ORMs are one of those things that aren't worth the trouble in the long run. They can be nice in a quick prototype, but for an app that lives for at least a few years, you'll inevitably start bumping into performance issues or weird ORM behaviour that costs a lot of time to resolve. The first time I encountered an ORM I thought it was magic, but after 15+ years in the business, I no longer find them worth the trouble. Writing raw SQL isn't that hard and as long as you use parameterized statements, much less likely to bite you in the end. Save your future self the headache and start with a low level library.

Is the one and only .... that works for you best !

just what i needed

Lool man really knows his audience... also was that knex huge security problem patched

slonik sees no love, I see how it is

@beyondfireship

Жыл бұрын

Trying it out now, disappointed i overlooked it

Hi! I just wanted to add another perspective regarding ORMs. My experience is that they should be considered anti-pattern and I can outline the reasons why: 1. they won't excuse developers from having to understand good database design and proper querying and, most often, introduce N+1 problem through that naivete 2. they encourage direct table access with what amounts to adhoc SQL which ties the hands of database developers when the need arises to reorganize data for scale and performance 3. most relational databases offer things like functions, stored-procs and prepared statements which parameterize queries to solve things like: a. combating sql injection b. providing an access layer tier above base tables which: i. provides API-like access and ii. grants the freedom to re-org base tables as needed iii. simplified access-level authorization Those are the main points (there are others). Whether an ORM is used or not, there is no escape from getting to know your serialization (storage) layer well. You should be using functions or stored-procs as access points to your database regardless. Which then begs the question, why do you even need an ORM?

When the nextjs 13 course is ready, please add it to udemy too

Once you started using prisma you never go back ❤

@abhinavadarsh7150

Жыл бұрын

Unless you started having serious performance issues.

@abdirahmann

Жыл бұрын

@@abhinavadarsh7150 and a big pocket once your business grows cause you'll have to foot that bill for those terrible SQL it generates to make all that magic possible!

Trust me, you don't want to bother with sequelize if you're using typescript. It just causes so many weird bugs, is not documented as well as it looks at first glance (many options objects are not specified in the api documentation, at least when i last used it), and forget it if you want to write a complicated query.

@tristan7668

8 ай бұрын

But TypeORM has a lot of bugs, Prisma is not a good choice for complex app, now we have only MikroORM (which some programmers recommend as a great choice), but I don't see large companies in real life using this ORM. And finally, we have query builders like knex or database drivers to write raw SQL queries.

@igalklebanov921

8 ай бұрын

@@tristan7668 You should try Kysely. It's inspired by Knex, but is type-safe first, immutable, predictable, extensible, and probably more expressive at this point.

I’m interested in buying your full Next 13 course, just wondering, does it teach Next 13 for those that already know Next 12 and below, or is it for people completely new to next. I am the latter and found a lot of tutorials tend to assume your coming from previous versions of next so am feeling a bit lost. Thanks

That @Entity based schema defining is also done in Android Room Db

Been playing with Prima and GORM (Go). The amount of time I’ve spent setting them up and tweaking them instead of just working on my MVP with the few CRUD statements I actually need is…not great. I guess I like the idea cause for some reason I think I need to be able to change my database on a whim.

Typeorm doesn't give full type safety. Even when you pass selective columns in select option for find method, the return type will still be array of entity and not array of those selective columns.

@tambourinedmb

6 ай бұрын

Yes that is the advantage of prisma. Also for joins you get whatever type you defined in your entity

I'm currently interested in Orchid Orm.

I kinda prefer Knex because it gives me control and everything still looks and feels like SQL. Very transparent in its use. No need to figure out how joins work in an ORM or if it does expensive sub-queries. I'm responsible for optimizing it, and... ChatGPT is also familiar with it.

@igalklebanov921

8 ай бұрын

You should try Kysely. It's inspired by Knex, but is type-safe first, immutable, predictable, extensible, and probably more expressive at this point.

Prisma has a very good documentation and developer experience. I recommend it over the others. It is very easy to setup and to use.

@LuisSierra42

Жыл бұрын

It looks pretty interesting

@md.redwanhossain6288

Жыл бұрын

It has no sql joins. Horrible

@fallout__boy1130

Жыл бұрын

@@md.redwanhossain6288 of course it has support for joins. Rtfm.

@chess4964

Жыл бұрын

prisma so slow

elixir's ecto 'toolkit for data mapping and language integrated query' is easy to use. it's kinda with js because phoenix liveview is a good and safe abstraction on js. and ecto is a good and safe abstraction on postgres.

@landscapesandmotion

11 ай бұрын

Glad someone mentioned elixirs ecto.

The worst thing of being a developer is choosing the right stack. IDK why we treat it like a marriage

@locim9201

Жыл бұрын

As long as you’re not so responsible (like marriage), it won’t be the worst thing, you can’t just choose and then leave the company when you think it’s a good fit 😎

@intwominds1943

Жыл бұрын

We treat it like a marriage bcz it is legit a huge commitment lol

@Slashx92

Жыл бұрын

Because when you are making products for clients (internal or external), changing something like your tool for querying the database is not a simple thing, and there's a lot of anxiety around "making the right choice" right await. Although most tools have pros and cons. If you pick a querybuilder and then you see yourself limited by it, an orm will have limitations in other departments. I agree we should just build but the issue is real lol

Jeff And Ozzyman are my most favourite Australians ❤️

TypeORM is pretty decent too. I use it at work. But I think Drizzle looks fun.

@thisismustakim

Жыл бұрын

what type of application did you use TypeORM for?

i knew that one was the best! i told yall

DROP DATABASE;

@hermankapange4756

Жыл бұрын

My favorite command of all time 😂

@nicolaetaban790

Жыл бұрын

It's just a JIRA P1 Ticket Generator when written in the correct terminal 😂

Prisma also support MongoDB which is a huge W considering it also supports types (which are basically strictly typed jsonb embedded in the documents, making denormalization much nicer)

@vladislavstepanov7591

11 ай бұрын

typeorm is a buggy piece of software. I was in a projects with typeorm and i don't want to repeat that experience

@WolfrostWasTaken

11 ай бұрын

@@vladislavstepanov7591 typeorm is a library. But I generally agree yeah it's not a good ORM (I also have experience with it). You need to be aware of a ton of gotchas while using it.