Thread

My temporary PHP fix from 2014 has nearly 20M installs. Today I'm deprecating it

341 points · 107 comments · jakeasmith

jakeasmith · 1789505909 · focus · HN ↗
Author here, happy to answer any questions. I never imagined a polyfill for http_build_url would gain so much traction. After 12 years, deprecating it feels like the right move, especially given the new options from the community and PHP itself.
1. HackerThemAll · 1789634602 · focus · HN ↗
  The JavaScript world is littered with stuff comparing to which your patch seems like a complex project. See those examples:
  <a href="https://www.npmjs.com/package/is-odd" rel="nofollow">https://www.npmjs.com/package/is-odd
  <a href="https://www.npmjs.com/package/is-even" rel="nofollow">https://www.npmjs.com/package/is-even
  <a href="https://www.npmjs.com/package/left-pad" rel="nofollow">https://www.npmjs.com/package/left-pad
  <a href="https://www.npmjs.com/package/is-whitespace-character" rel="nofollow">https://www.npmjs.com/package/is-whitespace-character
  <a href="https://www.npmjs.com/package/isarray" rel="nofollow">https://www.npmjs.com/package/isarray
  1. JaggerJo · 1789635398 · focus · HN ↗
    what a broken ecosystem.. The crazy thing is not that the package exists, but that it is used by JS devs.
    junon · 1789636596 · focus · HN ↗
    I feel like I have to remind people of this quite often, but the history is such that npm was lightweight at one point, bundling wasn't a thing, and while `isodd`/`iseven` are of course silly, things like `isarray` were not functions that existed back then (we didn't have Array.isArray). `typeof [] === 'object'` in JS, so e.g. my package `is-arrayish` checked for a similar structure to an array (whereas Id guess `isarray` checked for the prototype). `isarray` failed for the `arguments` keyword, which was needed for variadics before argument spreads were added to the language I believe in ES5.
    So of course they don't make sense now. But they were created for a reason. Before even Markov chains were a fad - let alone LLMs - we were trying to be as efficient as possible and maximize code reuse I stead of writing the same helper functions over and over again. That's what you're seeing.
    IncreasePosts · 1789662775 · focus · HN ↗
    You want to implement your own is-odd in your code - simple, right? isOdd = (x) => x % 2 == 1
    Ut oh, your code is broken for negative numbers now since % isn't a true modulo operator...
    Fine then, isOdd = (x) => x % 2 != 0
    Ut oh, your code is broken because isOdd("hi") returns true now...
    Fine then, isOdd = (x) => if(!isNumber(x)) throw... else return x%2 != 0
    Ut oh, your code is now broken because isOdd(2^55+1) returns true now...
    rtkwe · 1789667126 · focus · HN ↗
    Ut oh? I've never seen that, is it variant on uh oh or something else?
    IncreasePosts · 1789670647 · focus · HN ↗
    It's something I'm fighting for in my own little way.
    Everyone does a glottal stop between the "uh" and "oh", so I'm trying to align the spelling
    Unlike the guy on him who writes all years with 5 digits like 02026, I have good reasons for my idiosyncracies.
    luplex · 1789671291 · focus · HN ↗
    Hm, I would not spell it with a "t" then, but maybe with an apostrophe instead.
    "Uh'oh" is more readable in my opinion and won't be mispronou in ced

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.