วีดีโอ

probably the only good notation is s-expressions. XML,JSON or other stuff all have problems.

CGI is almost dead! Perl still used by sysadmins, but Pyton are much better. If you wanted to support web development using C, just checkout modern frameworks like an Crow.

JSON is fine. Not being strongly-typed is by design. There are alternative strongly-typed wire format if that's your use case. (e.g. protobuffer) We are on the real world -- people use different languages, run incompatible software versions, will enter garbage data, have to pay contractors to update their software -- JSON allows for sufficient leeway for that (backwards compatibility, fail-safe).

great video - thanks Gregg. This is the glue I was missing in my C studies....

I am asking myself for nearly 40 years: why I am dealing with this? so whatever

Thank you so much for the video! I really enjoyed it

i love your content. your json parser has saved my life at multiple times. hands down the best api among json c parser.

On 6:56 when you say that JSON does not understand arrays I think it is worst than that. You see, JSON does not understand anything right, it is an specification. Arrays in C and low level languages as you say are defined on your words as contiguous memory holding elements of same size to complete. But you see JSON is not a low level language it does not have to use the same definition of array. In the end JSON is just a text file with certain syntactical rules, that is structure. Literals (true; false; null) in JSON are just strings as everything That is why it is so funny to me when people use it as an example of unstructured data which is nothing besides max entropy. But I agree with you that the curse of JSON is too much flexibility and not being able to know better what to expect. On my field of work, this express itself largely as a confusion where people seem to believe that JSON can replace a data model which is a completely different concept. And here is also where constraints come in place! So, yeah agree with you that the lack of defined constraints limit a lot JSON as a data exchange format and causes a large percentage of the headache for most data engineers besides all the business loss derived by the semantic loss given the lack of constraints.

21:00 You could potentially use const char* variadic arguments. So in this case you'd call jse_get("file", "json") or jse_get("file.json") depending on whichever you need

BEST POINTER EXPLANATION ON TH-cam.

25:27 Surprised no one mentioned this yet but that file is "JSON5" and not actually JSON. Biggest change is it supports trailing commas and comments

19:09 if you want to do that in windows you need the termios.h header file and im not sure if this is even possible on dos/windows architecture

Bastante interesante el video. Gracias por la explicación.

Good Morning I am little bit curious about c language its job scope for development... Could you make video on that

How about introduce the better one.

Would love follow up to this. Great video!!

The title should be "How to create a http client GET request in C"

Thankyou I am YET to see a good C multi array string example passed by reference Integer/number are easier to handle For example Char string_array[100][10]; 100 strings Passed by reference & updated by the called function Which will be very useful for C beginners For example

Hi Gregg, fantastic video. Thank you! one question, in relation to ca. minute 13:44. How is the env executed on the browser when the c file is originally meant to be executed with command line arguments? how does one get the command line argument for free? is there a way to compile a c file as if it had been executed with arguments? I hope I made myself clear. I appreciate it, great content!

Hey!, I find your content very informative and educational for someone like me who started programming during covid. Please keep it up!

14:15 What's the magic number -12 for?

Also when you use a library (in any lang/framework) you lose control of your project recursively, because you don't control what other libraries that library calls, and what other-other libraries the other libraries call, and so on... Which is where we are today, with exponentially more computers made of expontentially better hardware, connected by exponentialialy faster networks, but still the user experience is slower than it was 20 years ago :(

Please is there any documentation on cursor code just like the color code which is documented in terminal-colors.d 5, i will be grateful if you can help me out thank you

While I feel like the video is great, you are able to tell cool things and being interesting. But there are some issues: I also implemented a JSON library myself - multiple times, in C, C++... - I use JSON for describing data in some of my projects (in OSDEV, gltf parsing...). The power of JSON is its simplicity, and generally, the size of the parser. - 3:41 when you say that you would love to have beginning and end markers, we already know when the file is expected to end: when the depth is 0 after parsing the first element. I mean, if you start to see the '{' token, you know that the file has not ended until you have seen the corresponding closing bracket. Also, the error handling should not be inside the JSON data, but should rather be placed outside the management of the standard. I mean, if you open a nonexistent file in an OS, the error is returned in another place, rather than using a fake file that contains 'null'. JSON is used to store errors in an API because it's a whole another abstraction. It's not the JSON parser that returns an error, but the API. I explain later why the degenerates' case makes sense. The beginning and end markers are also placed outside the JSON standard, for example, in a file system, we already know the length of the file, in a request, we know its length... - 5:40 The key isn't the only way to access an element, generally it's like a map, you explore it by its key or by exploring each element by itself. Nothing restrain you from using JSON map for storing things in the form of {name}: {data} and so, using UTF-8 seems logical. Also, for a text based data format, it's not a specific part of the document that is UTF-8 but the whole document. - 7:00 JSON arrays, are implemented in a way that it's easy to implement a recursive JSON parser, for each entry, it's like parsing a whole new JSON document for the current entry. It's just that enforcing a single type for all arrays entry would be slower, because you would have to check each entry type. (for example, A parser that I help to implement a long time ago: (GitHub) brutal-org/brutal/blob/main/sources/libs/json/parser.c ). It seems like you want to map a JSON array structure to a C struct perfectly, and you can do it with the help of unions: struct JsonValue { JsonType type; union { JsonMap map; JsonArray array; float floating; ... }; }; Then you would use everything as a JsonValue, also your document. That's why a document could have just a value (3:23, 3:16), and why an array could have multiple types. It's meant to be implemented that way because a 'Value' could be a literal, an object, an array... You say that it's slower because it doesn't have constraint, but it's false, First, if the speed is the most important component, you should not use JSON but rather a binary format. (But binary formats have their own disadvantages). JSON is aimed at being simple to implement as a recursive parser, and still being easy to edit. And JSON is already fast enough, I mean, at the end, the bottleneck that you encounter isn't your library but the file system/disk itself. --------------- - 11:46 The standard should not contain a minimum value, because it's specific to each implementation. JSON is meant to be used in other specification, or your own. For example, it's used in Javascript. It's used in the GLTF specification, and so on. This means that those specifications may be able to put a value to the JSON limit. Your JSON file is meant to target things it knows in advance (you would not write a JSON file without knowing where it would go ?). The C standard puts a limit on thing (like the variable name length) because it's meant to be used by multiple compilers. But JSON is only generally used to abstract data for another standard. For example, a GLTF file may be massive, (10M +), so a high limit is important, but for a config file, having a 1M+ limit seems overkill. So it's implementation dependent. (same things for 2, 3, 4). -------------- - 14:30 I feel like the comparison is a little bit unfair, because your code doesn't have error handling. Technically, the code on the right doesn't handle it, but the library that he uses does. Have a nice day ! Great work.

I really appreciate this video. I came across it trying to find out how to understand the gobbledegook that is, e.g., "\x1B[0;31m," as I came across similar formats to do a platform-agnostic screen clear. What does all of that represent? It reads to me like an escape sequence, but I'm not sure what exactly it's doing.

can you please make the text smaller ?

hmm ... your header relocation doesnt seem to work for me ... but i tryed just Location: %s and it worked

Nice job. I have done something simlar such as input and rectangle routines but not as organized as this. You have inspired me to update and refactor my code!

I tried it in Windows, discovered that there are some includes from the SYS directory which obviously Win doesn't have. But thank you for the lesson!

Pl post more content like this.. very few people look at C for web programming..

Awesome fella!

Neat. Awesome. Good vid. Totally agree with statements regarding independence and familiarity with the tools and language one would use to develop, and the terminal is inescapable (even in Windoze afic). The varied examples and use case scenarios are brilliant, common concerns and illustrated concisely; fantastic work!

very interesting content; thank you for the time you took to give those detailed and clear explanations; subscribed :)

why are you including pthreads, I don't see it used in the code

it is almost like the standard was written by programmers who anticipated writing json parsers, and wanted the "freedom" to change the criteria of there implementation

you actually saved me so much time. I was just going to write a json parser for the same reasons (all libraries I have found are overly verbose), didn't think the standard was so loose, although it is something derived from Javascript so ....

So JSON would be so much better if it only supported American English ? The American Standard Code for Information Interchange? Maybe get a globe - there's a whole world out here that isn't in the USA.

7:51 perfect explanation, now I understand C arrays much better

about ascii keys, it's cool and pretty understandable you don't want emojis in there but it breaks down if you wanted keys written in a language with non-ascii letters. Contrary to popular belief, not all APIs are in English

amazing work thanks

I appreciate the effort but I cannot read that text

You can make functions static in a header file to make it "local" to that file. meaning any file that includes that header, it wont be able to use that static function. This might be slightly better instead of the prefixes in your function names.

Is there a slight possibility that the owner of the AI may steal your copyright claims by saying his AI was the actual creator of the art instead of you who used the AI to create it? I mean is there any possibility of such claims actually become a law or precedent?

in other words , if you want to write actual useful commands , you are going to need to know the kernel source code

nad what about if i make my own server in bare bone hardware

The first video that clearly explained the multibyte codepoint. Thanks!

Im kind of stupid. So does this mean any AI art created by anyone ever is up for grabs to be used by anyone else with no consequences?

So far, the approach states take varies. Some recognise copyright of ai generated works. While others don't. The EU recently made recognition of ai generated work possible. This is in contrast to the old traditional view. Whether one approach is better than the other is up to each. However it is likely that the new approach may prove to be detrimental especially to people whose occupation is dependent on their skills, as their works may now be massed produced through AI generations.

First comment pin pls

Keep Going 💪