Launch HN: Creo (YC W24) – Build Internal Tools with React/NextJS

Re:Launch HN: Creo (YC W24) – Build Internal Tools with Reac... by samuelstros on Tuesday April 02, 2024 @04:39PM (#39910624)

What's the value to users if you are NextJS based?

- internal tools rarely (never?) need SEO

- the complexity of NextJS rings alarm bells as infra product. A look at your docs confirms my suspicion https://docs.trycreo.com/core-concepts/server-and-client-com...

[ Parent | on HN ]

Re:Launch HN: Creo (YC W24) – Build Internal Tools with Reac... by solias99 on Tuesday April 02, 2024 @04:41PM (#39910649)

Mainly their implementation of React Server Components, which is a far simpler set of APIs to work with compared to traditional React. (Also very LLM friendly)

[ Parent | on HN ]

Re:Launch HN: Creo (YC W24) – Build Internal Tools with Reac... by aerhardt on Tuesday April 02, 2024 @05:20PM (#39910966)

Why are RSC more LLM friendly that traditional React?

[ Parent | on HN ]

Re:Launch HN: Creo (YC W24) – Build Internal Tools with Reac... by solias99 on Tuesday April 02, 2024 @05:25PM (#39911020)

1. Very clean, easy to understand APIs.

2. Easy to make API calls.

3. Easy to reason about server/client component boundaries

Makes it easy for an LLM to write code without all the cruft/boilerplate.

[ Parent | on HN ]

Re:Launch HN: Creo (YC W24) – Build Internal Tools with Reac... by otabdeveloper4 on Wednesday April 03, 2024 @06:04AM (#39915439)

I'm guessing NextJS because internal tools need to make requests inside the DMZ without authorization.

(The huge mental disconnect between people who only ever make websites and people who make business tools is amazingly huge.)

[ Parent | on HN ]

Re:Launch HN: Creo (YC W24) – Build Internal Tools with Reac... by siborg on Wednesday April 03, 2024 @12:28PM (#39919478)

I agree with these points. Nextjs, from my understanding, is primarily aimed at websites. I also worry about lock-in.

[ Parent | on HN ]