Our great sponsors
rust-asn1 | json | |
---|---|---|
1 | 93 | |
95 | 40,239 | |
- | - | |
8.1 | 7.7 | |
2 days ago | 3 days ago | |
Rust | C++ | |
BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rust-asn1
-
Weird architectures weren't supported to begin with
> I feel like this really only makes sense if pyca/cryptography had planned on adding the Rust dependency from the very beginning (or from very early on). Is there any indication that was the case?
I am sure this idea surfaced several times in IRC or possibly in the mailing lists. Certainly, the authors have been toying with handling ASN.1 in rust since 2015 [1], which I guess will be the next logical step.
I do agree that this is mostly a political stance. pyca/cryptography is a wrapper sandwiched between a gigantic runtime written in C (CPython/PyPy) and a gigantic library written in C (openssl).
The addition of Rust as dependency enables the inclusion of just 90 lines of Rust [2] where the only part that really couldn't be implemented in pure Python is a line copied from OpenSSL [3] (i.e. it was already available), and which is purely algebraic, therefore not mitigating any real memory issue at all (the reason to use rust in the first place).
The change in this wrapper (pyca/cryptographic) does not move the needle of security in any significant way, and it is really only meant to send the signal that adding Rust in all other Python packages and especially in the runtime itself will now come at no (political) cost.
[1] https://github.com/alex/rust-asn1
[2] https://github.com/pyca/cryptography/blob/main/src/rust/src/...
[3] https://github.com/openssl/openssl/blob/OpenSSL_1_1_1i/inclu...
json
-
Learn Modern C++
I have not done a "desktop" program in 25+ years and never using C++ (or C), since then I'm mostly a web developer (PHP,Elixir, JS, Kotlin etc).
I'm currently doing a C++ audio plugin with the Juce framework.
This website has been a good resource, alongside https://www.learncpp.com
But I was actually close to give up before using those two things:
- https://github.com/nlohmann/json : my plugin use a json api backend and the Juce json implementation is atrocious (apparently because of being born in previous c++ version), but this library is GREAT.
- ChatGPT 4. I'm not sure I would have "succeeded" without it, at least not in a reasonable time frame. ChatGPT 3.5 is slow and does not give good results for my use case but 4 is impressive. And I use in a very dumb way, just posing question in the web UI. I probably could have it directly in MSVC?
Also I must say, for all its flaws, I have a renewed appreciation for doing UI on the web ;)
- JSON for Modern C++ 3.11.3 (first release since 473 days)
-
What C++ library do you wish existed but hasn’t been created yet?
https://github.com/nlohmann/json works well for me
-
[CMake] Can't include external header in .h file
cmake_minimum_required(VERSION 3.15) project(xrpc++ DESCRIPTION "C++ AT Protocol XRPC library" VERSION 1.0.0 LANGUAGES CXX) include(FetchContent) FetchContent_Declare(cpr GIT_REPOSITORY https://github.com/libcpr/cpr.git GIT_TAG 2553fc41450301cd09a9271c8d2c3e0cf3546b73) # The commit hash for 1.10.x. Replace with the latest from: https://github.com/libcpr/cpr/releases FetchContent_MakeAvailable(cpr) FetchContent_Declare(json URL https://github.com/nlohmann/json/releases/download/v3.11.2/json.tar.xz) FetchContent_MakeAvailable(json) add_library(${PROJECT_NAME} SHARED src/lexicon.cpp src/xrpc.cpp ) target_link_libraries(${PROJECT_NAME} PRIVATE cpr::cpr) target_link_libraries(${PROJECT_NAME} PRIVATE nlohmann_json::nlohmann_json) set_target_properties(${PROJECT_NAME} PROPERTIES VERSION ${PROJECT_VERSION}) set_target_properties(${PROJECT_NAME} PROPERTIES SOVERSION 1) target_include_directories(${PROJECT_NAME} PUBLIC include) set(CMAKE_BUILD_TYPE debug)
FetchContent_Declare(json URL https://github.com/nlohmann/json/releases/download/v3.11.2/json.tar.xz) FetchContent_MakeAvailable(json)
-
It is either a clever technique or a sad failure
Here is one popular C++ library (nlohmann/json) removing its use.
-
How to compile project to separate files to prevent having single large executable as a result?
Before going into binary serialization I suggest you to get comfortable with serialization to text. You can try to write your data to text files and read them in again. Then after you get an idea of how this works you can try to use a library that writes to XML or json, e.g. nlohmann json
- What are some ways I can serialize objects?
-
C++ that allows tracking peer to peer multimedia streaming connections using a Flat File - NOT MySql
Download the single header file json.hpp from https://github.com/nlohmann/json/releases and place it in your project directory or an include directory.
-
C++ Reflection for Component Serialization and Inspection
Exemple of a JSON library: https://github.com/nlohmann/json (For XML, there's tinyxml)
What are some alternatives?
serde - Serialization framework for Rust
RapidJSON - A fast JSON parser/generator for C++ with both SAX/DOM style API
json - Strongly typed JSON library for Rust
JsonCpp - A C++ library for interacting with JSON.
virgil - A fast and lightweight native programming language
ArduinoJson - 📟 JSON library for Arduino and embedded C++. Simple and efficient.
mrustc - Alternative rust compiler (re-implementation)
Boost.PropertyTree - Boost.org property_tree module
urllib3 - urllib3 is a user-friendly HTTP client library for Python
yaml-cpp - A YAML parser and emitter in C++
cJSON - Ultralightweight JSON parser in ANSI C
json11