FluentResults
swc
Our great sponsors
FluentResults | swc | |
---|---|---|
10 | 139 | |
1,643 | 29,984 | |
- | 1.4% | |
0.0 | 9.9 | |
5 months ago | 2 days ago | |
C# | Rust | |
MIT License | Apache License 2.0 |
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.
FluentResults
-
The Monad Invasion - Part 1: What's a Monad?
FluentResults
-
FluentResults: Simplificando el Manejo de Resultados y Errores en Aplicaciones .NET
altmann/FluentResults: A generalised Result object implementation for .NET/C# (github.com)
-
TypeScript Is Surprisingly OK for Compilers
Or maybe just start using Results as return type and get ValueOrDefault :) But when it comes to handling exceptions, I think it explodes there with ifs and processing IENumerables: https://github.com/altmann/FluentResults
But then again, simpler Results wrapper may be used perhaps. But it is a different way of coding and takes some mental shift on how to think about errors and distinguish between error results and true exceptions.
https://github.com/altmann/FluentResults
-
Exception handling between controller and service
Yep, it's called result pattern, aforementioned above. There was two highlighted implementations - OneOf, FluentResults.
-
Communication - library for Results
What does this library do better or differently than something like Fluent Results?
-
Why is using Exceptions is controversial in low level languages (like C++) but not in C#?
For C# particular - this project https://github.com/altmann/FluentResults
-
Knowledge of generics: isn't it pretty common?
For example https://github.com/altmann/FluentResults is excellent if you want generic results
-
The Operation Result Pattern
It's worth noting that there's also a library called FluentResults as an alternative to this one.
-
Introducing Cranks.Result
Interesting... I just found out that your first intention was to improve FluentResults but your PR got rejected which is a pity. PR: https://github.com/altmann/FluentResults/pull/80. I guess I will have a look at your library in hopes of removing some boilerplate code. Thanks!
swc
-
Storybook 8 Beta
First, we switched the default compiler for new projects from Babel to SWC (Speedy Web Compiler). SWC is dramatically faster than Babel and requires zero configuration. We’ll continue to support Babel in any project currently using it.
-
What is JSDoc and why you may not need typescript for your next project?
SWC
-
Implementing auth flow as fast as possible using NestJS
As the reference explains “**SWC** (Speedy Web Compiler) is an extensible Rust-based platform that can be used for both compilation and bundling. Using SWC with Nest CLI is a great and simple way to significantly speed up your development process.”
-
Ruby Outperforms C: Breaking the Catch-22
This is specifically about breaking the myth that performing expensive self-contained operations (e.g, parsing GraphQL) in a native extension (C, Rust, etc.) is always faster than the interpreted language.
The JS ecosystem has the same problem, people think rewriting everything in Rust will be a magic fix. In practice, there's always the problem highlighted in the post (transitioning is expensive, causes optimization bailouts), as well as the cost of actually getting the results back into Node-land. This is why SWC abandoned the JS API for writing plugins - constantly bouncing back and forth while traversing AST nodes was even slower than Babel (e.g https://github.com/swc-project/swc/issues/1392#issuecomment-...)
-
Building a Minimalist Docker Image with Node, TypeScript
Why Speedy Web Compiler ?
- TypeScript Is Surprisingly OK for Compilers
- Speedy Web Compiler: Rust-Based Platform for the Web
-
FTA: Fast TypeScript Analyzer
FTA is a TypeScript static analysis tool built on the speedy foundations of swc. FTA is fast; capable of analyzing more than 150 files per second on typical hardware, it offers a powerful addition to your code quality toolkit.
-
Show HN: Ezno, a TypeScript checker written in Rust, is now open source
Very cool! I'm curious, is this intended for dev tooling?
For example, I could see this (or something similar) being useful as the engine for a typescript language server that would be faster than the standard one
But if it's not aimed at 1:1 with tsc, would it be intended more for something like swc[1]?
Or what would you expect people to use this for, besides just being a cool project to learn from?
[1] https://github.com/swc-project/swc
-
TypeScript team released an explorer for performance tuning
This is... good news, but I still cannot fathom using the default Typescript compiler for regular development. Seriously, leave the type-checking to your IDE and CICD chain, and switch to using tsx (https://www.npmjs.com/package/tsx) or swc (https://swc.rs/) and you will _immediately_ notice the difference in speed and productivity.
What are some alternatives?
Result - A result abstraction that can be mapped to HTTP response codes if needed.
esbuild - An extremely fast bundler for the web
Cranks.Result - A simple, strongly typed and boilerplate poor implementation of the Result pattern.
vite - Next generation frontend tooling. It's fast!
tweetinvi - Tweetinvi, an intuitive Twitter C# library for the REST and Stream API. It supports .NET, .NETCore, UAP (Xamarin)...
ts-loader - TypeScript loader for webpack
sendgrid-csharp - The Official Twilio SendGrid C#, .NetStandard, .NetCore API Library
tsup - The simplest and fastest way to bundle your TypeScript libraries.
excepticon-dotnet - Excepticon SDK for .NET
vitest - Next generation testing framework powered by Vite.
CSharpFunctionalExtensions - Functional extensions for C#
ts-node - TypeScript execution and REPL for node.js