Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
markramm
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
markramm
11y ago
This is a great development experience for distributed software. I'm really looking forward to Ubuntu 16.10 -- a lot of things seem to be coming together there.
2.
▲
by
markramm
13y ago
I had not seen that before, thanks!. The only thing that concerns me about glog is this statement: "The code in this repo is for export only and is not itself under development. Feature requests will be ignored."
3.
▲
by
markramm
13y ago
I wonder what the differences between these two logging libraries are? I know Tim wrote loggo specifically to solve some logging problems with Juju, which as the largest open source project in go, and as distributed system management tool p
4.
▲
Loggo - Production ready logging for Go
(how-bazaar.blogspot.co.nz)
19 points
by
markramm
13y ago
|
4 comments
5.
▲
by
markramm
13y ago
Yea, it's exactly like MongoDB which is also AGPL. Using the database doesn't impose any restrictions on your software. Even hacking on juju to add API'S you for your client software doesn't impose restrictions on the cl
6.
▲
by
markramm
13y ago
LXC support in the latest Go juju landed earlier this week, and reboot persistence landed yesterday. So, yes, but it's still very new.
7.
▲
by
markramm
13y ago
I agree, we have very much approached the problem from that of service administration/management rather than the "build a PaaS"approach. But, I think the "big problem" behind building a heroku style PaaS, is not get
8.
▲
by
markramm
16y ago
Well, by some definition of legacy, that's always true. If we are learning, using better techniques, and writing better software every day what we wrote yesterday will be "legacy" code... But I don't think that matters, ther will be upgra
9.
▲
by
markramm
16y ago
As the current maintainer of TurboGears, I've been thinking a lot about the python web framework world for the last couple of years, and I have been thinking for a long time that there's too much splintering of effort. One choice to solve t
10.
▲
by
markramm
16y ago
We are definitely fixing the traversal docs, and they are already much improved over two weeks ago ;) The responsiveness of Chris and Ben to actually fixing this kind of thing is amazing, and one of the major reasons we thought teaming up w
11.
▲
by
markramm
16y ago
All both pylons and tg have thousands of users on their lists, bfg has dozens of commiters of users, and a growing users list. And between our three frameworks I wouldn't be surprised to see tens of thousands of live sites, and millions of