I just want to ask. Is there anyone coding in fucking... you know... anymore?

@ekaitz_zarraga yep, I am. Both professionally and by choice in my free time.

@ekaitz_zarraga yeah; it's a language I know well, it's easy to hack stuff together in, and it's focused on webstuff, which makes everything below HTTP entirely invisible, but still semi-available.

Basically, it's great for sketching web services, that I can later implement safely in Rust ;)


#PHP was a great idea, a language focused on web server development that sits on the http request concept which stil today makes sense, instead of trying to bend our whatever generalistic programming language to make web servers on it. I believe on having solutions designed for specific problems instead of Java clones.

Probably didn't aged well, but something with the same base idea and all the known design flaws fixed would be absolutely great.

@sirikon Yeah I more or less agree and I like what PHP did for programming, bringing a lot of young people to programming. But I was just asking: is anyone doing php nowadays?



Yo he venido a hablar de mi libro xD

I know some people in Bilbao doing PHP nowadays.

@sirikon I know, but: WHY? I mean, nowadays we have enough alternatives!

@ekaitz_zarraga I don't know a single one that:

- Makes in-memory stateful web services impossible by runtime design (making horizontal scalability always possible).
- Doesn't require recompilation to test new code.

@sirikon php still needs recompilation, but I don't get what you mean by the first.


In PHP you just reload and it's there, you don't need to generate a binary and then launch it to open the web server, it gets interpreted on demand, and that boosts productivity as it's just "write, reload, it's there, and its done fast."

The first thing is: Every request can have an execution context with its associated memory, but all that will be deleted once the request ends. This prevents having memory remaining from old requests or between requests. So, weird logic in which one request affects another, without some pretty explicit persistency mechanism like a filesystem or a database, is impossible.

There are projects that recompile programs as it changes or as a web request comes in, but many of them aren't that fast while recompiling everything, generating a binary, running it, opening network connections again, etc.

This, in PHP, is the default, everyone works like that, and everything will be designed with that workflow in mind.
Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!