Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Primate Is the Last Great Web Framework

superarch.org

Post reply on HN
Print view View original

11–20 of 51 posts

Re: Primate Is the Last Great Web Framework

#11

Post by graypegg »

I might be missing something here, but I'm struggling to understand why the concept of mixing up implementation details by request path is desirable.

Maybe for colocating a legacy application with a new application that's slowly strangling it [0], but for a new application, this seems antithethical to using a framework in the first place. I can't say for sure why you liked Laravel, but I like Laravel/Rails/et.al. because I don't have to make decisions about the parts of the application that aren't unique to what I'm building.

This just allows you to yak shave on a route-by-route basis?

[0] https://en.wikipedia.org/wiki/Strangler_fig_pattern

Re: Primate Is the Last Great Web Framework

#13

Post by replygirl »

wredcoll wrote: post #7

The idea of the web-router "owning" the database fills me with a visceral sense of loathing. Data is always the important part of any real program.

the connection, schema, and migrations are all separated so looks pretty easy to swap in your own ORM or have another service own data

Re: Primate Is the Last Great Web Framework

#14

Post by graypegg »

ademup wrote: post #10
echoangle wrote: post #5

Last or latest? I don’t get where the title comes from.

My clients and colleagues are bragging about "headless web sites", by which they mean "sites built without WordPress (and kin)", by which they mean "sites built entirely using the English language via AI" In that sense, the author might be implying that "web framework" may soon be a thing relegated to history

Wait, is that what headless means now in the agency world!? I remember headless meaning the CMS wasn't the software serving the initial request, it just provided an API that some HTML/CSS/JS on S3 or something would consume.

Re: Primate Is the Last Great Web Framework

#17

Post by jazzypants »

wredcoll wrote: post #7

The idea of the web-router "owning" the database fills me with a visceral sense of loathing. Data is always the important part of any real program.

Yeah, this was the big red flag for me too. If you're going to try to decouple things, the last thing you should do is add more coupling.

Re: Primate Is the Last Great Web Framework

#18

Post by macintux »

brightball wrote: post #12
wduquette wrote: post #4

We used to call this “middleware”, that which sits between the client and the server.

I never understood that terminology since the middleware was always on the server too.

I thought of middleware as sitting on one server, with the database behind it typically on another.

Re: Primate Is the Last Great Web Framework

#19

Post by eithed »

wredcoll wrote: post #7

The idea of the web-router "owning" the database fills me with a visceral sense of loathing. Data is always the important part of any real program.

The only place it make sense to me is the validation = at the route level you want to ensure that the given model exists / request attributes defining relationship (pivot), are there. This is how Laravel does this. Having said that this should be responsibity of domain rather than application

Re: Primate Is the Last Great Web Framework

#20

Post by elliotec »

brightball wrote: post #12
wduquette wrote: post #4

We used to call this “middleware”, that which sits between the client and the server.

I never understood that terminology since the middleware was always on the server too.

It can be on the client side. Middleware just means something between the operations of the application on a server and operations of the application on a client. Doesn't matter where it sits, it's just the link.

But to the parent comment, yes, I agree, this is a middleware.

Post reply on HN