Not sure if their POP ingest servers are on it though.
534 karma · joined June 23, 2018
Not sure if their POP ingest servers are on it though.
I bet yakuza, katana, and bushido could all be picked up watching Kill Bill & playing some Call of Duty set in WW2.
The first example: https://www.typescriptlang.org/play?#code/GYVwdgxgLglg9mABMO...
Unreachable code detected
Along with some typos since `i` isn't declared. function f() {}
if (f) {}
produces: This condition will always return true since this function is always defined. Did you mean to call it instead?(2774)
https://www.typescriptlang.org/play?#code/GYVwdgxgLglg9mABMA...Also no asyncio isn’t great in this day and age.
Plain django, without DRF, just using JsonResponse is pretty great TBH, has all the batteries for things like auth and testing. Although having it be async would be a huge plus.
I recommend checking out pydantic and using that to enforce a schema for endpoint responses. Also much easier to understand (imho) than DRF’s serializers and you get static typing for free!
And tests hitting the database can be fast: https://www.brandur.org/nanoglyphs/029-path-of-madness
Firebase has some bespoke config that is dependent on all your data being in a key value mapping. I wonder how that would translate to a relational store.
Also building on clojure / datalog seems interesting and maybe risky.
[0]: https://typelevel.org/cats-effect/ [1]: https://zio.dev
but https://glean.software and https://reactjs.org aren't
Totally agree this is better to be in the language proper so we don't need this extra tooling.
Testing with Postgres, a 2000 char random sequence doesn't result in TOASTing, but a 4000 random sequence does get TOASTed
And for kicks, 4000 chars that aren't random compress well enough that they don't end up in TOAST.
My understanding was PG only uses TOAST when the data is too large to fit in the row, and since PG compresses data before inserting wouldn't user messages be fine?
Nothing stuck out to me when perusing through the code
Edit: seems pylance can figure it out but mypy can't, maybe pylance is special casing something?
from typing import Optional
from sqlmodel import Field, SQLModel
class Hero(SQLModel, table=True):
id: Optional[int] = Field(default=None, primary_key=True)
name: str
secret_name: str
age: Optional[int] = None
reveal_type(Hero.__init__)
# pylance: Type of "Hero.__init__" is "(self: Hero, *, id: int | None = Field(default=None, primary_key=True), name: str, secret_name: str, age: int | None = None) -> None"
# mypy: main.py:18:13: note: Revealed type is "def (__pydantic_self__: sqlmodel.main.SQLModel, **data: Any)"