> laravel
> but also trans
> inside the fucking routes

Ok this is it that's where I cry

KILL IT KILL IT KILL IT KILL IT KILL IT KILL IT KILL IT KILL IT KILL IT KILL IT KILL IT KILL IT

So you are transphobic?

@aviophile I wasn't until like 2 hours ago but then I found them in my route file and now I got self-diagnosed -but very real nonetheless- post traumatic stress disorder

Genuine question. What the fuck is even happening in this picture.

@Ranchonyx standard route definition for a website. "When you receive a request at url A, do X; when you receive a request at url B, do Y"

Someone decided to mix that with translations, so the routing depends on localization. Url to access a resource in England is not the same as it is to access the same resource in France; not just as in "website.com/users" vs "website.fr/users"; more like "website.com/user" vs "website.com/utilisateur".

Which, first, breaks a couple of concepts about the rest API, and the second I can't know which endpoint answers where without having open two files at the same time. I'm in a situation where some code is sending a response at a given request and IDK who tf is answering

@IHateForALiving the fuck.
so instead of
https://blablabla.com/educational_p...

https://blablabla.com/Lehrprogramme

In Germany?!

@Ranchonyx
http://mysite.com/api/...

@IHateForALiving end me.

Some people enjoy watching the world burn around them.

This reminds me of an ExpressionEngine site I had to add a chat system too once, the internal routing was bypassed - sort of, some of the standard routes still worked but the other 10,000 routes were hard coded, every, single, route, and flags added for admin/user access.

Someone spent a hell of a lot of time making this, instead of just relying on the internal routing system to do it for them, I could only assume they were being paid for LOC,

Shit what a bad ideas :O