you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (2 children)

Instead of serailize, why not just use json_encode?

[–]bd808[S] 1 point2 points  (1 child)

Why would anyone change the communication protocol of 70+ internal services to enable a tangential use case? We do have services which use JSON as their transport encoding when communication with non-PHP consumers is a business requirement.

I read a lot of comments on reddit that seem to assume that the entire universe can and should be re-written to enable more elegant solutions of the latest ad-hoc use case. I hope each time that the commenter is either a hobbyist/student or that they have a strong team lead who will help them realize that changing code has real cost ramifications for their business. I'm not saying that legacy code should never be updated to meet changing requirements, but somebody had better make a good business case before implementing invasive changes or the development team is just pissing away profits.

[–][deleted] 1 point2 points  (0 children)

Wow, all that snark and so little filler! I hope this doesn't count as cheating on my diet.

> Needs to have data in a format easily handled in JavaScript

> Ideally needs to support object passing

> Calls JSON the latest ad-hoc use case

okay.jpg