herbs-cli VS Vapor

> higher level paradigms, DSLs or a language that provides such capabilities out of the box for these reasons

Based on exactly this arguments that we created HerbsJS [1], a domain-first library to build microservices. While the essential complexity can't be removed [2], we should put effort to remove the accidental complexity as much as possible.

BTW, great to see this kind of discussion here and congratulations to the team responsible for Cell Lang.

[1] https://herbsjs.org/

Great article!

Given the absence of libs / frameworks to help in the domain part of the architecture, we created Herbs [1], where our proposal is to shift the focus of developing a microservice from the infrastructure (http, DB, logs, etc) to the domain , with an emphasis on use cases [2] and entities [3].

It may seem small but it changes a lot where you put energy into developing your software, especially maintaining it.

[1] https://herbsjs.org/

[2] https://herbsjs.org/docs/usecase/getting-started

[3] https://herbsjs.org/docs/entity/getting-started

Being productive while following the best software development practices has been one of the greatest challenges for developers. Today I can say that with HerbsJS this challenge becomes much friendlier.

Herbs CLI

Botter works in tandem with Vapor, which handles the server-side functions of your project. This powerful combination allows you to focus on what matters most - creating an engaging and effective chatbot.

// swift-tools-version: 5.8 // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: "MyServer", platforms: [.macOS("12.0")], products: [ // Products define the executables and libraries a package produces, and make them visible to other packages. .executable( name: "MyServer", targets: ["MyServer"]), ], dependencies: [ .package(url: "https://github.com/vapor/vapor.git", .upToNextMajor(from: "4.70.0")), // Dependencies declare other packages that this package depends on. // .package(url: /* package url */, from: "1.0.0"), ], targets: [ // Targets are the basic building blocks of a package. A target can define a module or a test suite. // Targets can depend on other targets in this package, and on products in packages this package depends on. .executableTarget( name: "MyServer", dependencies: [ .product(name: "Vapor", package: "vapor") ]), .testTarget( name: "MyServerTests", dependencies: ["MyServer"]), ] )

Otherwise there's https://github.com/vapor/vapor

The Swift/Vapor project is a relatively easy way to do it.

Opening this webpage (https://vapor.codes) cranks my CPU (5800x3d) to 100% instantly. Why?

Vapor is the most popular non-Apple-ecosystem Swift project. There have been a few others, but none particularly popular.

Server-side apps (typically via Vapor)

My first option other than PHP was using Swift and Vapor. I have made some projects with iOS and Objective-C, maybe I could also learn Swift and create both native iOS apps and backends with the same language.

StreamCam is written 100% in Swift, SwiftUI & Combine. The serverside is handled with Vapor.