Need advice about which tool to choose?Ask the StackShare community!
Common Lisp vs JSON: What are the differences?
- Syntax: Common Lisp uses a Lisp-like syntax with s-expressions, while JSON uses a lightweight, human-readable format for data interchange.
- Data Types: Common Lisp supports a wide range of data types including lists, arrays, structures, and symbols, whereas JSON primarily deals with key-value pairs and arrays.
- Functions: Common Lisp is a full-fledged programming language with support for defining functions, macros, and objects, whereas JSON is limited to representing data structures and does not have built-in functions.
- Expressiveness: Common Lisp offers a high level of expressiveness with its macro system, object-oriented programming features, and support for advanced programming paradigms, while JSON is simpler and primarily used for data serialization.
- Literals: Common Lisp allows the use of symbols, strings, and numbers as literals in its code, whereas JSON only allows strings, numbers, boolean values, arrays, and objects.
- Usage: Common Lisp is typically used for developing complex applications, AI systems, and symbolic manipulation tasks, while JSON is commonly used for storing and transmitting data between web servers and clients.
In Summary, Common Lisp and JSON differ in syntax, data types, functions, expressiveness, literals, and usage.
Hi. Currently, I have a requirement where I have to create a new JSON file based on the input CSV file, validate the generated JSON file, and upload the JSON file into the application (which runs in AWS) using API. Kindly suggest the best language that can meet the above requirement. I feel Python will be better, but I am not sure with the justification of why python. Can you provide your views on this?
Python is very flexible and definitely up the job (although, in reality, any language will be able to cope with this task!). Python has some good libraries built in, and also some third party libraries that will help here. 1. Convert CSV -> JSON 2. Validate against a schema 3. Deploy to AWS
- The builtins include json and csv libraries, and, depending on the complexity of the csv file, it is fairly simple to convert:
import csv
import json
with open("your_input.csv", "r") as f:
csv_as_dict = list(csv.DictReader(f))[0]
with open("your_output.json", "w") as f:
json.dump(csv_as_dict, f)
The validation part is handled nicely by this library: https://pypi.org/project/jsonschema/ It allows you to create a schema and check whether what you have created works for what you want to do. It is based on the json schema standard, allowing annotation and validation of any json
It as an AWS library to automate the upload - or in fact do pretty much anything with AWS - from within your codebase: https://aws.amazon.com/sdk-for-python/ This will handle authentication to AWS and uploading / deploying the file to wherever it needs to go.
A lot depends on the last two pieces, but the converting itself is really pretty neat.
I would use Go. Since CSV files are flat (no hierarchy), you could use the encoding/csv package to read each row, and write out the values as JSON. See https://medium.com/@ankurraina/reading-a-simple-csv-in-go-36d7a269cecd. You just have to figure out in advance what the key is for each row.
This should be pretty doable in any language. Go with whatever you're most familiar with.
That being said, there's a case to be made for using Node.js since it's trivial to convert an object to JSON and vice versa.
Pros of Common Lisp
- Flexibility24
- High-performance22
- Comfortable: garbage collection, closures, macros, REPL17
- Stable13
- Lisp12
- Code is data8
- Can integrate with C (via CFFI)6
- Multi paradigm6
- Lisp is fun5
- Macros4
- Easy Setup4
- Parentheses3
- Open source3
- Purelly functional3
- Elegant3
- DSLs1
- Multiple values1
- CLOS/MOP1
- Clean semantics1
- Will still be relevant 100 years from now1
- Still decades ahead of almost all programming languages1
- Best programming language1
- Simple syntax1
- Powerful1
- Generic functions1
- Can implement almost any feature as a library1
- Formal specification, multiple implementations1
Pros of JSON
- Simple5
- Widely supported4
Sign up to add or upvote prosMake informed product decisions
Cons of Common Lisp
- Too many Parentheses4
- Standard did not evolve since 19943
- Small library ecosystem2
- No hygienic macros2
- Inadequate community infrastructure1
- Ultra-conservative community1