[deleted]
Goro – An implementation of PHP written in Go
51–60 of 135 posts
Re: Goro – An implementation of PHP written in Go
#52One of the most "hip to hate" languages implemented in one of the most "hip to love" languages...
I thought Go was a hip to hate language also. Seems to get a bunch of grief about "missing" things. I quite like it but haven't used much beyond toy projects.
Re: Goro – An implementation of PHP written in Go
#53Re: Goro – An implementation of PHP written in Go
#54> PHP is a nice language but is having trouble keeping up with modern languages It's only "having trouble" because it can't change its API from month to month to match whatever's in vogue. A majority of the web still runs on some variant of PHP, and that guarantees that it's not dying anytime soon. More broadly, it seems the author wants to create a version of PHP that's not focussed on web requests, which is sort of…
> A majority of the web still runs on some variant of PHP, and that guarantees that it's not dying anytime soon.
The same is true of Perl, but (depending on your definition of "not dying") it's not clear that Perl isn't dying.
Re: Goro – An implementation of PHP written in Go
#55"Better caching of compiled code by allowing sharing of compiled or live objects (classes, objects, etc) between running PHP scripts" I'm a little confused on this piece, as PHP does have a cross process opcache. People also use things like apcu to share userspace things across processes (uses mmap).
I think the idea is for example creating an object in 1 PHP process, and modify it in the second. The point is there is no shared state in the running problem
Well, it mentions classes, for example. The opcache handles that already, cross process. For a live object, people tend to use apcu. It's not as nice as a shared object across 2 couroutines, but it's reasonably fast because it's using mmap and fairly fast serialization to share the object.
So, what they are proposing is helpful. But, they seem to be assuming that PHP shares nothing across processes. That's just not true.
Re: Goro – An implementation of PHP written in Go
#56Earlier quoted context omitted.
While true, there is still a tremendous amount of the web that is powered by php and not using WordPress or Magento. Facebook, Yahoo, Wikipedia, even Google.
Facebook forked PHP to make Hack to try and make PHP usable. Yahoo is yahoo. Wikipedia wouldn't have the resources to change anything. Google has a wiki page for their developers telling them to never ever use PHP for any google project.
Those facebook improvements made there way back into the core.
Google might be able to move quicker if they allowed php. Facebook killed them in social. The type of products google can offer is limited by this decision.
Re: Goro – An implementation of PHP written in Go
#57Earlier quoted context omitted.
wait for js.rs
You joke but that's very likely to happen eventually if it hasn't already. At the very least I wouldn't be surprised if Mozilla made a prototype JS engine in Rust.
Yeah buddy. https://servo.org/
Also there is already amazing work for Rust and WASM https://rustwasm.github.io/book/
Re: Goro – An implementation of PHP written in Go
#58Earlier quoted context omitted.
So you are saying that PHP is dying since 2004. That’s ridiculous. There are new languages and more alternatives today that’s it.
It just takes a long time for certain things to die.
That argument can be made from the other side about golang being artificially kept alive by Google.
The comparison isn't on equal footing.
Re: Goro – An implementation of PHP written in Go
#59> PHP is a nice language but is having trouble keeping up with modern languages It's only "having trouble" because it can't change its API from month to month to match whatever's in vogue. A majority of the web still runs on some variant of PHP, and that guarantees that it's not dying anytime soon. More broadly, it seems the author wants to create a version of PHP that's not focussed on web requests, which is sort of…
> A majority of the web still runs on some variant of PHP, and that guarantees that it's not dying anytime soon. The same is true of Perl, but (depending on your definition of "not dying") it's not clear that Perl isn't dying.
PHP is growing these days. Some of the hip crowd are coming back, small business never left and globally it is gaining as more developers come online. PHP offers so much so easily it's hard to replace.
Re: Goro – An implementation of PHP written in Go
#60Earlier quoted context omitted.
I don't understand. I have a C background. What is wrong with that?
Probably the repetition of if err != nil {} You get used to that pretty quickly in Go, but it still looks messy to a lot of people.
And so it's clear to others, this probably the worst possible way for a language to go about implementing error handling (maybe aside from just not having any mechanism outright and terminating).
But alas, those are the choices that the Go language made.