978 karma · joined May 12, 2016
This is commonly accepted that naming convention and style convention have no place in code reviews so we invented style linters (eslint, prettier, golint...).
But what about filenames and directory names ?
Here is the reason of flint: have a consistent naming convention among your files and directories in your projects.
This is commonly accepted that naming convention and style convention have no place in code reviews so we invented style linters (eslint, prettier, golint...).
But what about filenames and directory names ?
Here is the reason of flint: have a consistent naming convention among your files and directories in your projects.
The mission of Astroflow is to provide a unique, superior experience of logging among all programming languages.
You can find the motivation and explaination here: https://kerkour.com/post/logging/
The Go version here: https://github.com/astroflow/astroflow-go
And the website here: http://astroflow.io/
The masterplan of astroflow is to provide an universally (for all languages) consistant high performance logging library without compromise on the UX.
It's true that the UX of astroflow in go is almost the same as logrus, but performances are far better (eg: for an event with 10 fields, logrus makes 54 allocs while astroflow 13 and rs/zerolog 6).
Some things are not yet implemented (like async logging), but the goal is to provide all the features of an advanced logging library (unlike logrus, like async and sampling) without sacrifices on the UX (unlike uber-go/zap, log4j...) with a clean API.
For the moment, it stands between logrus and zerolog/zap in term of speed/allocation.
For a message with 10 fields, zerolog does 6 allocs, astroflow 13 and logrus 54, but the UX is far better than zerolog (IMO).
OTH there is no cost (only 1 if comparison) if the level is not enabled.
In a near future the same mechanism as in zeolog will be implemented which enable to reduce allocations in tradeoff of writing more verbose code.
We use sequelize-cli (event if it's not our ORM) because we can script migrations using javascript which is very powerfull!
1) git push master (Gitlab CI to run tests, builds...)
2) notification received when CI pipelines finished
3) @bot deploy api production (in our messaging app)
if errors happen:
4) @bot rollback api [commit]
One question for advanced GO devs: Is it possible to refactor the Call function to accept a struct instead of a pointer for the Aggregate parameter ?
Here I wasn't able because Aggregate is an interface and gorm need a pointer. So you can't Save an interface because it's not a concrete type.
I dont know for the moment for the full development experience [0]. I hope, it's the condition for me.
[0] https://www.zdnet.com/article/linux-comes-to-chromebooks/
It's really bugs on bugs.
I will certainly change for a Chromebook (if announced linux application support is great) or a xps 13 (which I have great feedback from a friend on Ubuntu) soon
Thus my startup which require high availability use a .com domain with a domain related suffix: https://phasersec.com
But one of my side project use a .io domain (https://infosecjobs.io) because high availability is not a primary concern.
You can also mix the two, like: Mydomain.io for your website And mydomainapi.com for your api which require high availability. (Like do getstream.io)
[1] https://hn.algolia.com/?query=io%20domain&sort=byPopularity&...