nice - didn't know about this - i am using bigcache https://github.com/allegro/bigcache as drop in replacement instead of redis in my go app - i shall give this a try
Yes and written by some of the people involved in the original net package. Brad used to be one of the maintainers of net/http and net packages in go. I'm glad they are so conservative about changing the standard library though, even if it does mean warts like this persist.
Our crypto banking software development solution provides all the necessary banking functions that your customers expect from their core banking platform. It is designed to handle all your customers’ needs with secure API, intuitive front-end, and banking modules. To get complete information, visit our website today and get a free white label software demo.
Thanks for posting, this looks really interesting. The main problem I suppose would be deliverability, so you'd have to set up reverse DNS, SPF etc. use a rented server, and perhaps warm up the ip for a while.
Yes. I'm interested in this? Any links and research you want to share? Most localization is done with js and these guys localizejs.com even put it in their domain :) But if there is any Golang solution for this I wouldn't know.
It's good to see that more community members are working on similar products. We hope to make Excel work as best as possible too. Keep up the good work.
Thanks, this looks really interesting - people don't think enough about how to keep code running for years in the face of constant change and complexity.
The article does link to that blog post, and points out some problems with it.
I'm not a fan of this design either personally, in particular requiring a v2 suffix, I think it makes assumptions about versioning which don't withstand scrutiny, e.g. that major versions are always used for major breaking changes. In my experience they are more often used to indicate major feature releases.
I'd really rather go kept the culture of no breaking changes rather than explicitly encouraging them if you move past 1.x.
Looks like there's been a bit of work put in. I especially like how there's multiple sql drivers supported. Instructions on how to add slack were especially nice, I'd been somewhat stuck on the legacy keys (now deprecated).
Hm, at least the handling of interface definitions seems very unidiomatic to me, specifically implementation packages also containing the interface definitions. At least those interfaces are not returned, but structs instead.
Usage of the internal/ package would make sense too. All in all this seems as it would benefit from some go specific patterns.
Options would be nice and i still do not understand the benefit of build tag based config compared to env or flag based approaches.
Indeed, the build tag approach here seems to be just config in code (and thus in version control), switched with compile time flags. Functionally very similar to using a flag when running to do the same thing. ENV or flags for every config option does get quite complex quickly, and you also need defaults so you end up with some config in code and some config passed in (thus keeping state outside the app). I prefer a config file myself, one file per environment, and you can keep them out of version control. Another option is a config service on the private network which apps communicate with to pull configs securely.
On the database side, I simply wouldn't use mongodb, and prefer sql migrations as they're simple and portable. I also prefer using the db for testing where required rather than faking behaviour with mocks.
Agreed interfaces really must be defined at the point of use.
Overall there is far too much abstraction here in pursuit of arbitrary structure borrowed from other people (Bob Martin,12 Factor).
Being boring really is what I love most about Go. It doesn't change much and there is a culture of simplicity, so it's quick to onboard new devs and there isn't a lot to get your head around. That also makes it good for building large projects, as the complexity is in the domain and the application, not clever uses of the language itself.
I almost wish they'd make it more boring and take a few things out, but it's probably too late now to change the language much and people would complain vociferously. Things I never use and wish it didn't have: panic, goto, labels, struct tags, executable comments, even arrays.
The only things I'd like to see improved significantly are enums, errors, and user-space generic collections (coming soon!).
amazing!
agree! I used it in my project go-stash, and it's much faster than encoding/json.
Is that ok for remote from China?
US and Canada only unfortunately.
what's advantages over x/ratelimit?
I've used it for a while, it's awesome!
I'm wondering how to get points.
As of today TinyGo supports more than 60 different boards!
Also the list of supported devices in the drivers repository is fast growing. Find them here: https://github.com/tinygo-org/drivers
Thanks for sharing. Is the build caching behavior still the same today?
Nicely explained.
Most important takeaways (for me) are: Use table driven tests AND use interfaces, so you can mock stuff :)
Nicely explained! This also had some new insights for me, even though i'm working with go for some years now :)
This has been retracted because they compared different versions of their code so the binary comparisons were wrong. link to a breakdown here
A truly practical approach to learning Go
Interesting
Really cool.
A great deep dive into the internals. Thanks for sharing :)
Thanks.
nice - didn't know about this - i am using bigcache https://github.com/allegro/bigcache as drop in replacement instead of redis in my go app - i shall give this a try
Hi, How one can earn some points to be able to post interesting golang project?
Nice tool.
It is relevant to Israel? We have now a Tesla sales office here.
Great video!
This has been one of the most frustrating things about developing Go network code. IP addresses are a mess. This is interesting.
Yes and written by some of the people involved in the original net package. Brad used to be one of the maintainers of net/http and net packages in go. I'm glad they are so conservative about changing the standard library though, even if it does mean warts like this persist.
I've edited the title to the one from the repo to make this more descriptive.
Looks good!
Our crypto banking software development solution provides all the necessary banking functions that your customers expect from their core banking platform. It is designed to handle all your customers’ needs with secure API, intuitive front-end, and banking modules. To get complete information, visit our website today and get a free white label software demo.
nice post
very nice blog
Thanks for sharing.
Very well and helpful. Thanks
Very well and helpful. Thanks
Go 1.16 (which is in RC this month) does embedding natively.
A nice article.
In one word: spam. The article is absolutely not related with Golang or Go developers.
Agreed, flagged a little late I'm afraid
The tricky bit here is picking the right abstractions, there's nothing worse than the wrong abstraction that would take too much work to remove.
Thanks for posting, this looks really interesting. The main problem I suppose would be deliverability, so you'd have to set up reverse DNS, SPF etc. use a rented server, and perhaps warm up the ip for a while.
Crazy!
It does look significantly faster on most benchmarks, and apparently the crypto has a lot of hand-rolled assembly for x86.
A great article! All the pieces put together making a good introduction to DDD in golang
Up and Downvote dont work
You need more points.
very cool video
Nice library!
I'm using your repository!
Like it!
Nice Post
Good post
Go is not boring mate :)
Yes. I'm interested in this? Any links and research you want to share? Most localization is done with js and these guys localizejs.com even put it in their domain :) But if there is any Golang solution for this I wouldn't know.
It's good to see that more community members are working on similar products. We hope to make Excel work as best as possible too. Keep up the good work.
have been waiting for this for a long time :)
cool!
Awesome!
I can’t upvote. How many karma points do i need to upvote?
Looks good. Need to get my hands on it.
It was an amazing podcast. Specially that html bit. I can’t stop laughing.
Hey, first time commenting here
Link incorrect
Thanks, I've fixed it now, I think it requires a trailing slash
Shouldn't people use the new asset bundling coming in the standard library?
Thanks, this looks really interesting - people don't think enough about how to keep code running for years in the face of constant change and complexity.
Nice you guys. hope you also helps others too
nice to read your articles
Sure think in this way keep going nice
Definitely think the way the Go developers think about versioning is very different from the way others tend to use it.
What sets you apart from other freelancing shops?
Really dislike the way this hides updates to modules, but I guess that's the price of stable imports
It would be nice to have some kind of wrapper on websockets
got 404 page.
Thanks, the repo seems to have been taken down so removing.
All informations about this here : https://blog.golang.org/v2-go-modules
However, In my opinion it's an unfamiliar and tedious design
The article does link to that blog post, and points out some problems with it.
How can we earn karma without ability to upvote or submit? Comments don't seem to be rewarded
I've given you an upvote. I might reduce limits again soon, they are in place to prevent spam.
A pretty impressive climb :O
Very interesting project!
👏🏻 Really good reading
This is an incredibly useful library. Took me a while to find what I needed in the docs just because of the sheer amount of what can be done.
That is really cool. cross-platform for something like that is pretty impressive.
Looks like there's been a bit of work put in. I especially like how there's multiple sql drivers supported. Instructions on how to add slack were especially nice, I'd been somewhat stuck on the legacy keys (now deprecated).
Really great article..Thanks for sharing...
Informative article
Very useful Golang calling convention
Nice release
Very nice MysQL Tutorial...
Thank you
Indeed, great article..
Helpful step-by-step guide!!
Very helpful Packages..thanks for sharing
Might be worth reserving posts for big milestones, as they're unlikely to get much attention otherwise.
Why not define the interfaces where they are used?
Hm, at least the handling of interface definitions seems very unidiomatic to me, specifically implementation packages also containing the interface definitions. At least those interfaces are not returned, but structs instead.
Usage of the internal/ package would make sense too. All in all this seems as it would benefit from some go specific patterns.
Options would be nice and i still do not understand the benefit of build tag based config compared to env or flag based approaches.
Indeed, the build tag approach here seems to be just config in code (and thus in version control), switched with compile time flags. Functionally very similar to using a flag when running to do the same thing. ENV or flags for every config option does get quite complex quickly, and you also need defaults so you end up with some config in code and some config passed in (thus keeping state outside the app). I prefer a config file myself, one file per environment, and you can keep them out of version control. Another option is a config service on the private network which apps communicate with to pull configs securely.
I had no idea about `goto` in Go.
Ditto on that last line.