"@" on Twitter • Hacker News Board

Re: "@" on Twitter

#141

Post by pmarreck » Mon, Apr 30, 2018, 2:28 AM UTC

osrec wrote: post #128

pmarreck wrote: post #109

Earlier quoted context omitted.

I just read at least half that page and this idiotic design confirms exactly why I feel PHP should be considered harmful

I don't think it's harmful. You just need to know what you're doing. PHP gets a bad rep round here unfairly. It's actually a very useful language which has proven itself over and over again in the wild. I wonder what you think of JavaScript?

It's harmful exactly because it's ridiculously complex. And because it forces a Map/Dict to conform to an Array/List protocol, making it actually worse than both (it loses the O(1) or O(N) access time of the array/list, plus adds a bunch of complexity)

Re: "@" on Twitter

#142

Post by pmarreck » Mon, Apr 30, 2018, 2:34 AM UTC

rayascott wrote: post #136

pmarreck wrote: post #110

Earlier quoted context omitted.

I bet they had a backup, it was just never tested... pretty common mistake

Nope, no backups were even created when Dorsey was in charge: “Oh, and while he was in charge, there was no backup of Twitter’s database.” From the Fortune article “Let's remember why Jack Dorsey was fired as Twitter's CEO” http://fortune.com/2015/09/30/jack-dorsey-twitter-ceo-fired/

what... the fuuuu

Re: "@" on Twitter

#143

Post by igravious » Mon, Apr 30, 2018, 5:39 PM UTC

pmarreck wrote: post #141

osrec wrote: post #128

Earlier quoted context omitted.

I don't think it's harmful. You just need to know what you're doing. PHP gets a bad rep round here unfairly. It's actually a very useful language which has proven itself over and over again in the wild. I wonder what you think of JavaScript?

It's harmful exactly because it's ridiculously complex. And because it forces a Map/Dict to conform to an Array/List protocol, making it actually worse than both (it loses the O(1) or O(N) access time of the array/list, plus adds a bunch of complexity)

Disagree, it doesn't force anything to be anything else. It is what it is and it's pretty intuitive. PHP never claimed that arrays behave O(C) when accessing members†. It actually reduces complexity because there's only one container type. "Harmful" is ridiculous hyperbole, that's how the language is designed, you may not like how it's designed but not liking something doesn't make it harmful.

† btw, have you seen this? https://stackoverflow.com/questions/2473989/list-of-big-o-fo... pretty detailed investigation of big-O for PHP arrays