←back to thread

How and why GraphQL will influence the Sourcehut alpha

(sourcehut.org)
153 points michaelanckaert | 1 comments | 11 Jun 20 04:46 UTC | HN request time: 0s | source
Show context
xvilka ◴[11 Jun 20 05:45 UTC] No.23485548[source]▶
Does this mean that SourceHut will become completely written in Go? Amazing news if so!
replies(1): >>23485670 #
CameronNemo ◴[11 Jun 20 06:10 UTC] No.23485670[source]▶
Why? I am currently converting a Flask/SQLAlchemy application to Go and gRPC. Go has not been that much of a win from my perspective. Lots of rough edges and missing functionality in libraries available, a lackluster type system that does enough to get in the way but not enough to properly express programmatic intention, and an atypical non-ideal error handling model have left me with little reason to champion Go. Not that it is a terrible language, I just do not see the value add compared to even Python (let alone Kotlin or Rust).
replies(3): >>23485708 #>>23486612 #>>23487224 #
zapf ◴[11 Jun 20 08:54 UTC] No.23486612[source]▶
Had a similar experience.

Typed languages are great for systems development, and I think, not so good for writing web applications.

I also think, Ruby, Python, JS have dominated web dev world largely cause they don't come in the way of the developer having to constantly convert HTML (untyped) and JS (untyped)into types for the backend programming language.

Remember how ActiveRecord (not sure about SQLAlchemy) simply took away the pain of managing types? You didn't have to explicitly parse or cast "0.001" into 0.01.

replies(1): >>23487017 #
1. square_usual ◴[11 Jun 20 09:56 UTC] No.23487017[source]▶
ActiveRecord is parsing those types, you just don't do it explicitly. IME, a dynamic language may not get in your way when you need to go between JS and the backend, but it also certainly won't get in your way when you're about to shoot yourself in the foot in a large-ish project with errors that could've been caught at compile.