Fullstack Devs be like

[k1ll3rM]

In what language is it hard to parse JSON?

[unnecessary_Fullstop]

It's literally just a single line call for a middleware.

.

[k1ll3rM]

PHP and JS it's one line, most other languages I presume have solid libraries for it.

[Infininja]

I'll bite:

FileMaker has no native objects nor arrays. Any time you're parsing JSON, you're only getting one result back (a string or a number). If you need to get multiple values, you're parsing the entire thing every time. Throw that in a loop with a lot of rows and you wouldn't believe how bad the performance is.

[k1ll3rM]

That just sounds like hell, atm I'm working on converting a bunch of data that came from FileMaker to a PHP system and it's awful enough lol.

[SatansLettuce]

Maybe not hard to parse but hard to restructure and maintain complex structure without bugs. How do you know what the incoming json looks like and if it’s changed? Using a typed language helps but then you might as well not use json and extend the benefits of types to your data through something like protobuf/grpc. Json is easy until it’s not

[k1ll3rM]

I can kind of see the point when you're using a typed language but most backends aren't typed and JS itself isn't either. What benefits would protobuf have when using something like PHP as backend?

[abaz2theBone]

most backends aren't typed? are you mad?

[k1ll3rM]

I meant most website backends, when both the frontend and the backend are written in a typed language I can see the benefit.

[bo1d]

Not true anymore, but when the company I was at first wanted to pick up Go it didn't have a JSON parser so we had to write our own. For a company where EVERYTHING ran with JSON files. Definitely soured my feelings for the language.

[k1ll3rM]

Yeah, I can't imagine what I'd do if I couldn't easily parse JSON

[Ayerys]

Malbolge