Scarf Tech Stack: Relude
Scarf Tech Stack: Relude
At Scarf we love highlighting and using awesome open source projects. This blog post will talk about Relude, a project we use in the majority of our Scarf tech stack. For more information on the overall architecture we use to develop Scarf see our previous Scarf Tech Stack post.
At Scarf we write functional programming in Haskell. Relude is one alternative to Prelude, a standard module, in Haskell. It is widely known as a safe, performant, and user-friendly Haskell standard library.
Their ReadMe details all the reasons why other developers might choose Relude for their tech stack. In this post we will talk about why and how Scarf uses it.
Using and adopting a new library can be difficult. Often projects lack proper documentation. Fortunately, Relude has extensive documentation that is beginner friendly.
The Relude community is also inviting and works to keep good communication between their maintainers and users.
The community put a lot of effort into their content, including helpful blog posts by the maintainers on their site, Kowainik.
Other reasons we use Relude include:
Relude is used in a majority of our codebase, including the main app server we use for our website, `scarf-server`, our data processing pipeline, and beyond.
We made the decision to use Relude as our base library instead of the default Haskell base library because it has good defaults that cue users when they are using unsafe functions. This is important because the default library doesn’t flag the unsafe functions which can lead to runtime errors.
To learn more about Relude:
Do you know what companies are using your open source project? Learn more about how Scarf can help you see a project’s impact, identify potential customers, and understand growth without sacrificing your end-user’s privacy:
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
Unordered list
Bold text
Emphasis
Superscript
Subscript
At Scarf we love highlighting and using awesome open source projects. This blog post will talk about Relude, a project we use in the majority of our Scarf tech stack. For more information on the overall architecture we use to develop Scarf see our previous Scarf Tech Stack post.
At Scarf we write functional programming in Haskell. Relude is one alternative to Prelude, a standard module, in Haskell. It is widely known as a safe, performant, and user-friendly Haskell standard library.
Their ReadMe details all the reasons why other developers might choose Relude for their tech stack. In this post we will talk about why and how Scarf uses it.
Using and adopting a new library can be difficult. Often projects lack proper documentation. Fortunately, Relude has extensive documentation that is beginner friendly.
The Relude community is also inviting and works to keep good communication between their maintainers and users.
The community put a lot of effort into their content, including helpful blog posts by the maintainers on their site, Kowainik.
Other reasons we use Relude include:
Relude is used in a majority of our codebase, including the main app server we use for our website, `scarf-server`, our data processing pipeline, and beyond.
We made the decision to use Relude as our base library instead of the default Haskell base library because it has good defaults that cue users when they are using unsafe functions. This is important because the default library doesn’t flag the unsafe functions which can lead to runtime errors.
To learn more about Relude:
Do you know what companies are using your open source project? Learn more about how Scarf can help you see a project’s impact, identify potential customers, and understand growth without sacrificing your end-user’s privacy:
Tools and strategies modern teams need to help their companies grow.
At Scarf we love highlighting and using awesome open source projects. This blog post will talk about Relude, a project we use in the majority of our Scarf tech stack. For more information on the overall architecture we use to develop Scarf see our previous Scarf Tech Stack post.
At Scarf we write functional programming in Haskell. Relude is one alternative to Prelude, a standard module, in Haskell. It is widely known as a safe, performant, and user-friendly Haskell standard library.
Their ReadMe details all the reasons why other developers might choose Relude for their tech stack. In this post we will talk about why and how Scarf uses it.
Using and adopting a new library can be difficult. Often projects lack proper documentation. Fortunately, Relude has extensive documentation that is beginner friendly.
The Relude community is also inviting and works to keep good communication between their maintainers and users.
The community put a lot of effort into their content, including helpful blog posts by the maintainers on their site, Kowainik.
Other reasons we use Relude include:
Relude is used in a majority of our codebase, including the main app server we use for our website, `scarf-server`, our data processing pipeline, and beyond.
We made the decision to use Relude as our base library instead of the default Haskell base library because it has good defaults that cue users when they are using unsafe functions. This is important because the default library doesn’t flag the unsafe functions which can lead to runtime errors.
To learn more about Relude:
Do you know what companies are using your open source project? Learn more about how Scarf can help you see a project’s impact, identify potential customers, and understand growth without sacrificing your end-user’s privacy:
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.svg)
.svg)
.svg)
.svg)