NateDad

10 ms·

31.
Mage: a make/rake-like build tool using Go(github.com)
10 points by NateDad 9y ago|1 comments
32.
by NateDad 9y ago
Toml is far superior for hand editing. This is why yaml is terrible (aside from significant white space): foo: 80:80 bar: 22:22 baz: 22.22 What's the value of foo? It's the string "80:80". What's
33.
by NateDad 9y ago
Yaml is terrible. The fact that there are so many optional and different ways to format things and the fact that it has significant white space means it's horrible to hand edit. I'd much rather hand edit json. At least it won&#x27
34.
by NateDad 9y ago
Meaningful whitespace is horrid. I speak from 3.5 years of working on s project that exclusively used yaml as configuration. Yaml is horrid. Toml is way better. Yes, multilayered objects in toml are ugly. Don't make your users created
35.
by NateDad 9y ago
We use gin. It's mostly fine. If I were starting a new application, I'd probably use stdlib by itself.
36.
by NateDad 9y ago
we use https://github.com/jackc/tern for migrations. It's pretty nice.
37.
by NateDad 9y ago
Generics don't solve immutability.
38.
by NateDad 9y ago
That has never happened in my experience, and I've been through a lot of layoffs. It's usually the exact opposite. They lay off all the peons and keep the few high level experts. They're a lot harder to replace.
39.
by NateDad 9y ago
I've worked remote for about 5 years (and about 18 years total). When I lost my last job, I resolved to only look for remote work. Commuting is a giant waste of time, which is the most precious resource we all have. I could live nea
40.
by NateDad 10y ago
tl;dr: because it was designed for a weirdly shaped parcel of land, but then it wasn't put there, but they stuck with previous designs anyway, because the president thought it was a neat design .
41.
by NateDad 10y ago
How many people maintain their own email servers vs. use gmail? Slack doesn't prevent you from accessing your data, in fact they explicitly built exporting features. We're talking about open source, so reading your stuff shouldn&#
42.
by NateDad 10y ago
That puts the onus on every single person to maintain the history of the project. Lots of people delete mail (not me, but lots of people). Also, you can't retain history of what was sent before you joined. Also, emailing individual
43.
by NateDad 10y ago
To have all the features you get for free out of slack, you have to do a lot of work and maintenance to get out of IRC and mailing lists. Mailing lists by themselves are terrible, because there's no history. You can't scroll up to
44.
by NateDad 10y ago
No, email is terrible. There's no history. You can't "scroll up" to see what people were talking about. You can't link to another specific email to reference it (yes, there's archive services, but then you ha
45.
by NateDad 10y ago
"log in to slack" vs. "deploy 3 services in the cloud by yourself and force everyone to use a specific irc client (good luck)" There's a reason people like slack so much. It does a ton of stuff out of the box with
46.
by NateDad 10y ago
TIL I learned about godeps -N.... a month too late :) Cool, though, that definitely would help with that problem.
47.
by NateDad 10y ago
I really want to learn Rust. It's been on my next-to-learn list for a while now. I have limited time because of young kids and getting embroiled in politics (actual politics). Someday :)
48.
by NateDad 10y ago
I agree, I wish + wasn't string concatenation either.
49.
by NateDad 10y ago
<_< >_> No. Go was a good choice. The project benefited from it, both from a hiring perspective and from a technical perspective. If I were in charge, I would make the exact same choice again. Juju lives exactly in Go's
50.
by NateDad 10y ago
To be fair, you'll never see me compare Go to Haskell :)
51.
by NateDad 10y ago
This is about what the Windows API reports when you ask it what the path is of a file. Sure, inputs work with slash. Comparing outputs, which was the example I gave, does not.
52.
by NateDad 10y ago
That works for input, not output. If you ask what the path of a file is on Windows, it'll give you the backslash version.
53.
by NateDad 10y ago
one of the things that go eschews is operator overloading. a := b + c What's the runtime complexity of this statement? How much memory will it cause to be allocated? In go there's only two possibilities for what this co
54.
by NateDad 10y ago
To actually answer the question - yes it holds true, yes it scales (in my experience). There are a lot of abstractions that we built for Juju. And we absolutely tried to ensure there was only a single source of truth for everything. It w
55.
by NateDad 10y ago
Yes, sorry, wasn't saying that either Go or Rust were an exception, just trying to forestall the inevitable "but what about X thing that was used by everyone and is still 0.9" :) For Go vs. Rust, I think a comparison of 1.0 r
56.
by NateDad 10y ago
I worked in C++, C#, and Java for 15 years before my work in Go. I've used generics. I will freely admit to not having a lot of experience in functional or ML style programming languages a la Rust. I'd love to spend some time
57.
by NateDad 10y ago
functions and methods are the original abstraction. Interfaces allow you to abstract implementations of sets of methods. I fail to see how that is saying that abstraction and usability are overrated. They're not. They're import
58.
by NateDad 10y ago
Comparing 1.0's is a much better comparison, except in cases where there was huge adoption before 1.0.
59.
by NateDad 10y ago
That's not exactly true, Rog. If two people have changed the file, which causes a conflict, then you have resolve the conflict manually. Recreating the file with godeps would populate it with whatever commit happens to be in your gop
60.
by NateDad 10y ago
42 seconds. Just tried it with go 1.8 and a clean gopath (after downloading). That's on a 3 year old quad core i7 laptop w/ SSD. That's `go install github.com/juju/juju/...` which actually builds two binaries

More ›