Haskell vs Spring: What are the differences?
Developers describe Haskell as "An advanced purely-functional programming language". . On the other hand, Spring is detailed as "Provides a comprehensive programming and configuration model for modern Java-based enterprise applications". A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.
Haskell belongs to "Languages" category of the tech stack, while Spring can be primarily classified under "Frameworks (Full Stack)".
"Purely-functional programming " is the top reason why over 72 developers like Haskell, while over 192 developers mention "Java" as the leading cause for choosing Spring.
Spring is an open source tool with 30.6K GitHub stars and 19.6K GitHub forks. Here's a link to Spring's open source repository on GitHub.
According to the StackShare community, Spring has a broader approval, being mentioned in 319 company stacks & 184 developers stacks; compared to Haskell, which is listed in 33 company stacks and 47 developer stacks.
What is Haskell?
What is Spring?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to add, upvote and see more consMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Why I am using Haskell in my free time?
I have 3 reasons for it. I am looking for:
Improve functional programming skill.
Improve problem-solving skill.
Laziness and mathematical abstractions behind Haskell makes it a wonderful language.
It is Pure functional, it helps me to write better Scala code.
Highly expressive language gives elegant ways to solve coding puzzle.
Spring is another gift rained down by the gods of Open Source Software (a.k.a. Pivotal Labs in this particular case) that just makes sense on all levels.
From Spring Boot, to SpringMVC, the configuration architecture & profile paradigm, Spring Cloud expandability, to the ease with which one can deploy Spring applets as microservices within Docker is an absolute joy.
The core of the application use Spring Stack, to provide services and structure like:
- Self contained application with spring boot
- And many others.
그냥 간단한 MVC 웹 프레임 워크 인줄 알았는데 정말 모듈화가 잘 되있고, 사용하다보면 개발자에게 정말 편리하게 만들어 놓았다. vaildation 부분은 따로 처리 할 수 있고, 파라미터 담는 변수와 디폴트 값을 인자로 설정해 주는 부분도 참 좋은 것 같다. 또 spring-data 는 jpa 활용해 빠르게 개발하는데 유용하다.
I have been study with videos and tutorials
- SpringFramework 중 MVC , AOP 등의 라이브러리를 활용하여 웹 어플리케이션 프로젝트 구성
공통 로직 구현 및 보안 처리 가능
Spring5에서 지원하는 함수형 프로그래밍 경험 있음
Used Spring Boot and its ORM to interacting with database server for web application development.
Backend logic (REST, Auth0, Redis, Postgres, functional graph library (fgl), ...)