fastify-type-provider-typebox
GSL
fastify-type-provider-typebox | GSL | |
---|---|---|
3 | 22 | |
137 | 5,972 | |
5.1% | 1.3% | |
6.6 | 5.9 | |
4 days ago | 2 days ago | |
TypeScript | C++ | |
MIT License | GNU General Public License v3.0 or later |
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.
fastify-type-provider-typebox
- Fastify: Support for Auto Type Inference (similar to TRPC)
-
Using Rust at a startup: A cautionary tale
My experience is that it's fine(tm). "JavaScript on server-side" does not bother me; V8 owns bones. None of my debugging output includes JS lines because I pack source maps, which TypeScript happily includes.
Multi-threading isn't complex, because there isn't multi-threading. There's coprocessing via Promises, and there indeed are a lot of Node developers who think you don't need locking functionality because it's not multi-threaded (there was an absolutely bonkers discussion a few years ago where a JS developer insisted you didn't need locks), but whatever, they think that about other languages too, use async-lock or whatever.
"Maturity" is a word that means different things to different people. There is not a consensus-best-choice framework like Spring Boot in Node. But the tools are there and they're excellent (Python is similar, FWIW--FastAPI is the closest thing to a right answer that I think I've ever used, I wish I liked Python more because that owns). Fastify is perhaps The Best web framework I've ever used, and it has only gotten better with v4 allowing you to engage with type providers to create an end-to-end, automatically typechecked route declaration framework. It lets you do stuff like this, where you specify a request schema as JSON Schema (encoded via typebox) and it'll statically derive the TypeScript type for you whilst also using it for request schema validation:
https://github.com/fastify/fastify-type-provider-typebox#exa...
The tools are there. You do have to wire them together. There's value in that, for the way I write code and the stuff I enjoy building.
Overall, I'll trade some compilation niceties and even some (but to be frank, not much) performance for a vastly better language in day-to-day use. I really like the JVM. I've been using it professionally for twelve years. I also like the CLR. I did Google Summer of Code for the Mono Project in 2008, I've been around. But the day-to-day of writing code in the dominant languages on those platforms for things other than CRUD does frustrate me, and the difficulty of using the type system to effectively encode intent makes it much harder for me to write software that can guide other people to not misuse it.
(If I ever wrote something at extragalactic scale, yeah, sure, whatever, I'd rewrite hot paths in something else. But I absolutely don't care about that.)
-
Rate my Repo for code readability and ability to write production level code
Checkout https://github.com/fastify/fastify-type-provider-typebox or https://github.com/fastify/fastify-type-provider-json-schema-to-ts for a better TS experience also.
GSL
-
60 terrible tips for a C++ developer
Already showed you how to use ranges and such above, gsl::final_action is here
-
Backward compatible implementations of newer standards constructs?
For span I would recommend the guideline support library - gsl::span
-
Hey Rustaceans! Got a question? Ask here (20/2023)!
Not sure how things are at this point so you might want to look up with those keywords, but a few years back clang-tidy was one of the suggested tools, or enabling the core guidelines checker in visual studio if you're using that. Maybe using GSL or something similar as well.
-
Hardening C++ with Bjarne Stroustrup
When I want safety guarantees, I use the original and run-time checked gsl::span, rather than std::span. https://github.com/microsoft/GSL .
-
I love building a startup in Rust. I wouldn't pick it again.
Another solution: use std::span (or some alternative implementations if the codebase doesn't use C++20).
-
C++23 “Pandemic Edition” is complete
If you ask me, the GSL [1] alone is a fairly radical departure from C++ that delivers a lot of safety. I don't know if it's gotten much popularity, though. Probably because it introduces a similar disruption like you might find from a brand new programming language.
[1] https://github.com/microsoft/GSL
-
Using Rust at a startup: A cautionary tale
> With Rust, though, one needs to learn entirely new ideas — things like lifetimes, ownership, and the borrow checker. These are not familiar concepts to most people working in other common languages ... Some of those “new” ideas are, of course, present in other languages — especially functional ones.
With C++, lifetime and ownership are just about as important but unfortunately no one's got your back. You can ignore lifetimes and ownership but you do so at your own peril. And the compiler won't tell you you're doing it wrong because the language wasn't designed for it to do so.
If you want a taste of rust's "mindset" (with respect to limitations imposed by some types) without jumping ship to a new language, try C++'s Guidelines Support Library [1]. It introduces some of the same benefits/friction as switching to rust but without a new language. Opting-in to some of these guidelines might be a gentler way to get some of the benefits of Rust. But it comes with a similarly higher bar.
[1] https://github.com/microsoft/GSL
- Passing a std:: array as a function parameter
-
I created a memory leak using smart pointers
It's also far more verbose than T* or T& (probably intentionally). If you really want a non-nullable pointer, gsl::not_null from the GSL is a good option. Writing your own version is also trivial, if you don't want to add a dependency.
-
I wanna go back to work at a car assembly plant
I instead use the GSL and the Core Guidelines, where
What are some alternatives?
json-schema-to-ts - Infer TS types from JSON schemas 📝
CppCoreGuidelines - The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
zod - TypeScript-first schema validation with static type inference
cppinsights - C++ Insights - See your source code with the eyes of a compiler
fastify-type-provider-zod
sentry-native - Sentry SDK for C, C++ and native applications.
UncivServer.xyz - An Open Source Unciv Multiplayer server, written in TypeScript. Powered by Node.js, fastify and Redis.
cpp-core-guidelines-cheatsheet - Cheatsheet for the C++ core guidelines, including a set of tried-and-true guidelines, rules, and best practices about coding in C++.
fastify-type-provider-json-schema-to-ts - A Type Provider for json-schema-to-ts
C-Golang-like-Defer - Cursed defer() method in C++ achieves similar results as Go's defer keyword.
fastify-autoroutes - fastest way to map directories to URLs in fastify
score-simple-api-2