Or just have that book available in libraries.

The comment I made on reply to another comment hits here as well

We can think of weird edge cases all day, the fact is companies shouldn’t be able to hoard IP.

For fuck’s sake though, talk about strawman arguments. “Literally every doodle you make” when we’re talking about abandonware. My eyes nearly rolled out of my fucking head reading that. Do I need to start putting disclaimers on every post I make? “I am aware there is more nuance required before a law gets suggested but I sure wish companies couldn’t hoard old media without making it available, please don’t ‘um, actually’ me by suggesting I’m implying everyone must give me copies of their personal shopping lists.”

We can think of weird edge cases all day, the fact is companies shouldn’t be able to hoard IP.

You should be legally required to offer content you have on a copyright or else allow people to “pirate” it. The same way you must defend trademarks. If you don’t actually offer content you have the copyright for them you shouldn’t be allowed to prevent people from distributing it as abandonware.

Jimmy Buffett is dead

Very not solar punk, but very cool. Love the vibe of super dense living.

Then the problem is the schema being under specified. Take the classic pet store example. It says that the I’d is int64. https://petstore3.swagger.io/#/store/placeOrder

If some API is so underspecified that it just says “number” then I’d say the schema is wrong. If your JSON parser has no way of passing numbers as arbitrary length number types (like BigDecimal in Java) then that’s a problem with your parser.

I don’t think the truly truly extreme edge case of things like C not technically being able to simulate a truly infinite tape in a Turing machine is the sort of thing we need to worry about. I’m sure if the JSON object you’re parsing is some astronomically large series of nested objects that specifications might begin to fall apart too (things like the maximum amount of memory any specific processor can have being a finite amount), but that doesn’t mean the format is wrong.

And simply choosing to “use string instead” won’t solve any of these crazy hypotheticals.

grumpy and meaningless bad takes all day every day

You don’t sound grumpy at all though lol

This is what I was getting at here https://programming.dev/comment/10849419 (although I had a typo and said big instead of bug). The problem is with the parser in those circumstances, not the serialization format or language.

Can you give a specific example? Might help me understand your point.

I (think, at least) the point they’re making is that unless the API contract specifically differentiates between “present and null” and “absent” then there is no difference. (Specifically for field values.)

Just what every programming language needs, not one, but two types of null! Because nobody ever said one type was difficult enough.

If I see any of you make this distinction matter for anything other than “PUT vs. PATCH” semantics I’m going to be very angry.

I’m not following your point so I think I might be misunderstanding it. If the types of numbers you want to express are literally incapable of being expressed using JSON numbers then yes, you should absolutely use string (or maybe even an object of multiple fields).

For the love of all things pure, holy, and just, please do not use YAML in your APIs…

It’s entirely disingenuous because who the hell is throwing JSON into YAML without converting it? Oh wow, I changed the file extension and it still works. I’m so glad we changed to YAML!

Unless you’re dealing with some insanely flexible schema, you should be able to know what kind of number (int, double, and so on) a field should contain when deserializing a number field in JSON. Using a string does not provide any benefits here unless there’s some big in your deserialzation process.

Should be like 0o777 to mimic hex 0xFF

Do you actually use them?

Ah, okay, the “angle of the number” part helped. It makes sense now.

I misread it as the person on the right sending the image so it makes a little more sense as content moderation that way.