Sylvan VS Cursively

Compare Sylvan vs Cursively and see what are their differences.

Sylvan

A collection of .NET libraries, including the fastest general-purpose CSV parser for .NET. (by MarkPflug)

Cursively

A CSV reader for .NET. Fast, RFC 4180 compliant, and fault tolerant. UTF-8 only. (by airbreather)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
Sylvan Cursively
10 3
334 39
- -
7.5 3.2
6 days ago about 3 years ago
C# C#
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

Sylvan

Posts with mentions or reviews of Sylvan. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-31.

Cursively

Posts with mentions or reviews of Cursively. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-10-25.
  • Ask HN: Examples of Top C# Code?
    29 projects | news.ycombinator.com | 25 Oct 2022
    I was looking at the CSV parser Cursively recently, and I think it is a good simple example of a high performance C# parser and API design.

    https://github.com/airbreather/Cursively

  • The Fastest Csv Parser In Net
    2 projects | /r/dotnet | 12 Jan 2021
    Agreed, and agreed. #21 and #22 seek to address this, but these have actually been very low priority for me: as your benchmarks show, if you primarily need a bunch of objects that must be UTF-16 strings, then are other libraries out there that will do the job just fine. The main reason to use Cursively for that would be if you have some use cases where you need the unusual qualities that Cursively offers, but other use cases where you can live with something more traditional, and you don't want to have two different CSV processing libraries.
    1 project | /r/dotnet | 10 Jan 2021
    The usage instructions are in the README on https://github.com/airbreather/Cursively. The most straightforward way to get started (for now) is:

What are some alternatives?

When comparing Sylvan and Cursively you can also consider the following projects:

Sylvan.Data.Excel - The fastest .NET library for reading Excel data files.

CsvExport - Very simple CSV-export tool for C#

PdfSharpCore - Port of the PdfSharp library to .NET Core - largely removed GDI+ (only missing GetFontData - which can be replaced with freetype2)

Cinchoo ETL - ETL framework for .NET (Parser / Writer for CSV, Flat, Xml, JSON, Key-Value, Parquet, Yaml, Avro formatted files)

AlterNats - An alternative high performance NATS client for .NET.

CsvHelper - Library to help reading and writing CSV files

H.Pipes - A simple, easy to use, strongly-typed, async wrapper around .NET named pipes.

NPOI - a .NET library that can read/write Office formats without Microsoft Office installed. No COM+, no interop.

oqtane.framework - CMS & Application Framework for Blazor & .NET MAUI

RecordParser - Zero Allocation Writer/Reader Parser for .NET Core

CsvBenchmarks - Benchmarks for various .NET libraries.