More on go in backend readme
This commit is contained in:
parent
1586ed22ef
commit
5c73ef922e
1 changed files with 4 additions and 0 deletions
|
@ -2,6 +2,10 @@
|
|||
|
||||
This is the root of the backend. It contains the main server and the database logic. The structure might look confusing at first, given that go conventions (which I followed to the best of my ability) uses a rather goofy structure with the `cmd` and `internal` directories.
|
||||
|
||||
Golang does not support classes, but it does support structs. These are practically synonymous, with the important distinction being that structs does not support traditional inheritance. Instead, go uses interfaces to achieve polymorphism. This is a rather interesting way of doing things, and it's a bit of a learning curve if you're coming from a language like C++ or Java. Having a good understanding of [Composition over Inheritance](https://en.wikipedia.org/wiki/Composition_over_inheritance) will help you understand the go way of doing things.
|
||||
|
||||
An [interface](https://golangdocs.com/interfaces-in-golang) is functionally similar to an interface in Java, or an abstract class in C++. It simply describes how an object can behave.
|
||||
|
||||
An important note is that go, unlike C, handles its own dependencies. A simple `go get` command will fetch all the dependencies for you. The `go.mod` file is the equivalent of a `package.json` file in Node.js, if you're familiar with that.
|
||||
|
||||
To run the backend, you can use the `go run` command. For example, to run the server, you can use `go run cmd/main.go`. This will start the server on its default port (8080, at the time of writing).
|
||||
|
|
Loading…
Reference in a new issue