You don't do row level permissions on your database. You keep it all on the application layer.
You say this as some sort of objective truth. Keeping security about data at the data layer can often be a really good idea and just as appropriate as GRANT/REVOKE at the table and column levels.
What is better, depends on what you are doing, and is not a simple choice in any way.
I'm just saying if you have the option, if the engine does support the feature, and the solution is a good fit for your problem, you shouldn't shy away from it just because some other engine doesn't support it.
Anyway, yes, SQLite lacks a series of features you get on other SGDBs, often for good reasons. In exchange it brings an entirely different set of features. If you want Postgres, use Postgres.
The only thing I have against using SQLite in production (for my needs) is the lack of at rest encryption and row level permissions by user.