Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
peterevans
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
peterevans
9y ago
I'm pretty sure I'm not confusing it with Rust! That said, I don't think there's anything more I can say which can add to the conversation. I'm happy to allow what I have said to stand.
32.
▲
by
peterevans
9y ago
I love C. It's the language I used when I first "got" programming, and it's stuck with me, even though I don't use much professional use for it. I don't think you can count me among those who "love to bag&
33.
▲
by
peterevans
9y ago
Like I said: Go does everything C does, but better . I suppose you could write your own malloc in Go... if you preallocated a bunch of bytes in a huge chunk, and wrote some functions to use that up. But that sounds like a pain. If you re
34.
▲
by
peterevans
9y ago
Expressiveness can be good–but at a conceptual cost, because you must now understand how those fewer lines of code do the same thing as a program in another language that isn't as expressive. I'm glad it's a big win for you!
35.
▲
by
peterevans
9y ago
Go is like the Six Million Dollar Man language, compared to C. It's everything C can do, but much better. Both C and Go are very, very simple languages; there aren't many keywords, and it's pretty easy to grok both at a funct
36.
▲
by
peterevans
9y ago
Sorry—I just saw this! But, as it was, I was not saying that you should release a patch version every time you make a code change. That would indeed be pretty arduous! What you should do is test your library independently from the consume
37.
▲
by
peterevans
9y ago
I understand your point; my issue is that "serverless" as a term is a misnomer. You cannot have a serverless architecture without some servers to support it. The "serverless" distinction is a useful one to make, because
38.
▲
by
peterevans
9y ago
I was hoping the future of event-driven architecture is that we would call it "event-driven" and not serverless; alas.
39.
▲
by
peterevans
9y ago
Yeah, I sympathize—that's a tough situation. I think there's two ways you can look at your choice of configuration: ease of debugging, and ease of organization. When Google lays out why they use a monorepo, they are doing so becau
40.
▲
by
peterevans
9y ago
What does your test coverage look like? Perhaps you're missing something there that would have caught that bug? Testing is, of course, no silver bullet. Tests are written by humans, and humans make mistakes—and it's pretty difficu
41.
▲
by
peterevans
9y ago
Ideally, your library code that you're pulling in has some unit testing to demonstrate that things are working as they should be. (If not, consider adding unit testing! It's really useful!) If that is the case, then you can isolat
42.
▲
by
peterevans
9y ago
Any changes you need to make to internal libraries you install via package manager would need to be made to those separate repositories that house the libraries, and then those changes would have a release made (generally this is done throu
43.
▲
by
peterevans
9y ago
Using multiple repositories seems like the most natural workflow to have. It's easy to make a new one; it's lightweight to do, and it allows your code base to scale naturally. You can set permissions for each repository, so if you
44.
▲
by
peterevans
9y ago
My worry is that if Slack is replacing your documentation, then it may be that your organization did not have good (or any!) documentation that predated its use of Slack. As such, I'm not sure if that's a fair thing to criticize o
45.
▲
by
peterevans
10y ago
I don't think it matters as much as you suspect that one company is bootstrapped and the other is VC-funded. I'm sure you can find dozens of examples of VC-funded companies being floored by other VC-funded companies.
46.
▲
by
peterevans
10y ago
Running `go build` is a lot like running `make clean` before you compile.
47.
▲
by
peterevans
10y ago
Agreed. The sumOf function is now made more brittle by that fact, and would be unworkably so in a publicly-available API. This is easily fixed by a try-catch block if one finds that they are indeed allergic to if statements, although that t
48.
▲
by
peterevans
10y ago
I think I understand Linus' concerns. I guess I'm not sure how you conclude that I do not, but, so it goes. Languages do change, and implementations evolve. I think it's fair to temper criticism with the caveat that, hey, thi
49.
▲
by
peterevans
10y ago
Well... not to be a C++ apologist, but bear in mind that these comments were made by Linus back in 2007 and 2004. His views may not have changed, but C++ has certainly changed since then.
50.
▲
by
peterevans
11y ago
I don't think the post here is actually asserting not to use a web framework; just that you should not use a specific framework, named Revel, that aims to be Rails-esque. It brings up an interesting point for me about what is really po
51.
▲
by
peterevans
11y ago
This is no knock on you, since you aren't there to develop the Issues platform anymore. But I don't know how much private repo developers are hurt by the points made about Issues because they probably don't use it. I mean, Is
52.
▲
by
peterevans
11y ago
One of the authors, John Conway, is the inventor of the Game of Life: https://en.wikipedia.org/wiki/John_Horton_Conway .
53.
▲
by
peterevans
11y ago
You're right, and they do acknowledge this to some degree in section 5 ("Threats to Validity"). The projects they monitored were unaware of having been so, therefore the authors would have had no way to observe much nuance. T
54.
▲
by
peterevans
11y ago
It doesn't seem that any of the people who left were remote workers. I mean--maybe they had felt some solidarity with their remote-working coworkers--but I suspect that Yahoo's problems run a little deeper. The company promised a
55.
▲
by
peterevans
11y ago
Good thing the author wasn't randomly rewriting a file, then, and that the file was deleted and inferably unlikely to be used in a critical operation! Restarting MySQL is a violent operation. For large databases, it can take several mi
56.
▲
by
peterevans
12y ago
It seems like John had some technical points to make. It's hard for me to justify his post as "slamming" FoundationDB if his assertions are based on logic. Now, if you have a criticism of his points, you should feel free to r
57.
▲
by
peterevans
12y ago
I'm saying that, as someone who has read his various rants throughout the years on jwz.org, and followed his twitter feed, I can say with a great degree of confidence that a) he didn't post this to HN, and b) he really couldn'
58.
▲
by
peterevans
12y ago
If you think jwz is doing some "viral marketing", then you're really lacking in your knowledge of net.history. Ending your post with "flagged" makes it doubly foolish.
59.
▲
by
peterevans
12y ago
I think that's what Matthew meant exactly. "Nadia doing quite a bit of handholding to deal with crashes" -- Nadia is the that's doing the hand holding, rather than needing it. I think OP misunderstood when reading.
60.
▲
by
peterevans
12y ago
Actually, it's really great! Because it allows people who have an observable intolerance to gluten to eat food. That's a nice thing, isn't it? What's unfortunate is your dismissal of (scare-quoted!) gluten free food as a
More ›