4 ms·
I think therein lies the problem: yapache. It's their own version of (modified) Apache. So when these bugs like shellshock come out, it's harder to patch your o
by discardorama 12y ago
I think therein lies the problem: yapache. It's their own version of (modified) Apache. So when these bugs like shellshock come out, it's harder to patch your own home-grown version.
- jmathai 12y agoNot sure that's the problem though. yapache and yphp solve a very important need and probably saved Yahoo!'s ass on multiple occasions with engineers making lazy or common mistakes. There might have been a better way to implement it but with a company the size of Yahoo! I think they'd have the resources to maintain/patch such critical flaws. So the idea of a home-grown (really it's more of a patched version of apache / php than anything else) isn't entirely crazy. Just looks like this one slipped through the cracks.
- monokrome 12y agoThe idea of still using Apache / PHP nowadays is pretty crazy if you ask me.
- sudowhodoido 12y agoI could say the same about most of the supposed superior replacements. Everything is dangerous in the hands of idiots. The technology is almost entirely irrelevant to the discussion.
- jmulho 12y agoHalf the world must be crazy. What is better and why?
- currysausage 12y agoNginx, Node.js … and Twitter Bootstrap, obviously. (scnr)
- deleted 12y ago[deleted]
- ambrood 12y agoNobody was really working on yapache when I worked there around 2 years ago.