Hacker Newsnew | past | comments | ask | show | jobs | submit | victorteo's commentslogin

The text is updated on the website. And it's not next-generation anymore.


Personally I understood what the phrase "next generation" was supposed to mean, that it's a new and better way of doing things, a new paradigm. But I guess it's a bit overused, like the word "simple", that people have a cynical reaction to it. Anyway, I think the concept is refreshingly clear, it looks like it has a lot of potential. Congrats on launching!

Nit: I'd change "Working in progress" to "Work in progress", it's more common to see the latter wording.


Thanks! I update it.


Hi @hliyan, I will update the words.


Well, I just looked at Smithy. And they quite differ. Teo is just an HTTP framework like fastify, express, koa, flask and fastapi. It has a schema language and a builtin ORM, which make it quite similar to GraphQL and Prisma.


Hi @tkzed49, Teo supports custom route handlers and routing middlewares. Teo is a web framework with a builtin ORM. There are builtin permissions, too. You can use it or implement your own. Teo supports database auto migration.


I will remove the "next-generation" thing.


That makes sense. I fill fix panics and take this consideration into the next major version.


Both big projects and small projects are targeted. It doesn't sacrifice functionality while provides speed up.


Hi @e-clinton, it does have auth builtin.


Thanks! I will update the hero text.


Hi @rrgok, Teo supports builtin and extendable data validation and authentication rules. The feature is called pipeline. It supports very complicated type inference. See this: https://docs.teodev.io/concepts/components/teo-schema/pipeli...


This is fantastic.

At the same time, there's an ecosystem beyond just the web framework, where rapid iteration is helping a developer write once but leverage multiple tools.

For instance:

  - FastAPI
  - Starlette
  - pydantic
  - sqlmodel
  - postgres
Here's an example discussion for building the full stack yourself: https://medium.com/@lawsontaylor/the-ultimate-fastapi-projec...

The value comes from the sort of community-agreed data model:

Why: https://docs.pydantic.dev/latest/why/

Datamodel code gen: https://docs.pydantic.dev/latest/integrations/datamodel_code...

With this at the core, then API contract, doc, DB, test, and SDK generation are at hand, not to mention easier integration with all of these other projects. And now with

Observability: https://pydantic.dev/logfire

I find no hits on the terms `pydantic` or `openapi` in your docs. Given your choice to include Python as one of the three supported languages, do you have a plan to tie into Pydantic or implement a bridge?


Hi @Terretta, I plan to generate OpenAPI output for HTTP clients like Postman to import and read. We have things like FastAPI, Starlet, pedantic, sqlmodel and Postgres in Teo. The only thing we lack of is the debugger web interface which we could use Postman after exporting OpenAPI output is implemented.

The logfire is pretty cool and in the future, it will be implemented in Teo's way.


Thanks for the reply.

To be more clear, it's great you have a similar option for each of these, but having things similar to them isn't the same as having the actually same model that everything else in the ecosystem understands and plays well with.

Or, are you saying, under the hood, you're using literally the same? The docs make it sound as though you're reinventing all these wheels (pardon the Python pun).


They are similar things. The wheels are reimplemented to suit Teo's architecture.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: