ahacker15
Ask HN: Is Ruby on Rails still worth it?
Golang Proposal: Just Use GitHub
When to use STDERR instead of STDOUT
If you're working with inexperienced programmers (and some experienced but bad programmers), you should be certain that they WILL let that code garbage there if the compiler allow it.
[1]: https://github.com/tdewolff/minify/tree/master/cmd/minify
Is this open source? So we could see how it was made?
Utility of Go plug-ins diminished by vendored dependencies
DBeaver – Open Source SQL Management Tool/Editor That Supports All Major DBMS
Show HN: Task, a simple task runner / 'Make' alternative
Make files not war
There's a lot a legacy application written in Delphi here. Some old programmers, that only know to program in Delphi, may even build new apps with it.
It may not be that modern today, but there's the "pay the bills" mindset.
I think Delphi will die, but only because it costs a fortune today. If it had a resonable price, many people would continue to use it indeterminately.
Dep: Pre-Alpha version of Go's official package management solution
For fast questions and talking there's a Gitter chat room: https://gitter.im/go-gitea/gitea
For feature requests and bugs go to https://github.com/go-gitea/gitea/issues
Golang: Proposal of the Must operator
Even this is the case, Gitea has a lot a bug fixes that are still pending on Gogs.
This is not the reason of the fork. The reason is that he refuses to give more people write access to the project to keep it going.
Before the first time he went AFK, he even removed write access from the 2 or 3 other people that had it.
This time, the community patience ended, and Gitea will continue on its own way.
The Saga of Go Dependency Management
Build Golang projects properly with Makefiles
I love VueJS. I found it very easy, specially when you aren't building a SPA, but want something more powerful than jQuery without being overkill like React.
(I've tried Glide but it slowness and few bugs made me move to Govendor. Nothing personal, it just didn't work out that well for me.)
A few questions:
- Is the intention desincentive the use vendoring?
- Is the intention to make a single solution, and then deprecate existing tools (Glide, Govendor and like)?
- Do you have the intention to make a central registry for Go packages? Or the solution will use GitHub and like, as it does today? It would be not backward compatible, but the document don't make this clear.