Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
TakeBlaster16
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
61.
▲
by
TakeBlaster16
4y ago
> And its caller would need to be generic, and so on. My point though, was that it's extremely similar to code you already write. Zig encourages you to write `fn foo(allocator: Allocator, ...)`. That would just become something like
62.
▲
by
TakeBlaster16
4y ago
What's the alternative? Should he choose to risk dying in a crash for the nebulous greater good of lowering the average size of vehicles on the road? This problem will not be solved by individual drivers acting against their own self-i
63.
▲
by
TakeBlaster16
4y ago
Zig already encourages you to pass the allocator around as a value. Passing it as a type would be about the same amount of typing. Instead of this: var list = ArrayList(u8).init(my_allocator); you do this: var list = ArrayList(u8
64.
▲
by
TakeBlaster16
4y ago
Re: Comptime interfaces I wonder why Zig didn't decide on the convention of making the allocator type comptime-known. It would make code faster by eliminating a runtime indirect call, and it would let you lower memory usage if you choo
65.
▲
by
TakeBlaster16
4y ago
Huh, looks like you're right. I distinctly remember getting an error for emoji domains but not normal ones. I might have made an incorrect assumption from that. Either way I've accepted I'm never getting that domain back.
66.
▲
by
TakeBlaster16
4y ago
I bought the punycode domain {emoji_rabbit}.to (i.e. "hop to") intending to build a url shortner. But I never did anything with it and let it expire. And now it doesn't seem like .to even lets you buy emoji domains anymore. I
67.
▲
by
TakeBlaster16
4y ago
Maybe it would work, but I can't see myself ever using a font without lowercase letters.
68.
▲
by
TakeBlaster16
4y ago
There is a spectrum from obvious breaking changes (removing a method), to non-obvious ones (trait methods, glob imports), and beyond ( https://xkcd.com/1172/ ) Before adding methods to a trait, they test the change again
69.
▲
by
TakeBlaster16
4y ago
You could paraphrase this submission as, "The title is not the article"
70.
▲
by
TakeBlaster16
4y ago
Here's the full interview https://www.youtube.com/watch?v=GjENnyQupow The quote at is 11:10
71.
▲
by
TakeBlaster16
4y ago
Nice to see you here. I'm not much of a twitch guy, but I'm glad this is on your radar and I'll read about it afterwards! If you're talking about the `zig fmt` idea, I'd like to draw your attention to a possible pit
72.
▲
by
TakeBlaster16
4y ago
> It's funny you say that when [member of group] just [did something once]. It's not a sweeping generalization! They always do this!
73.
▲
by
TakeBlaster16
4y ago
"Optimizing for incorrectness" is a funny way to describe the practice of enforcing lint checks as part of a CI pipeline.
74.
▲
by
TakeBlaster16
4y ago
Strawman. Incremental compile times don't hit 2-5 minutes in either language, otherwise it obviously wouldn't be viable for real-world use. And juggling variables was an ongoing ordeal when I tried. I can't imagine how you wo
75.
▲
by
TakeBlaster16
4y ago
That's just going to result in people committing unused vars to their repos. People are already doing that now after adding '_'s by hand. https://news.ycombinator.com/item?id=32753079 It's going to get e
76.
▲
by
TakeBlaster16
4y ago
Yes. If Zig takes 100ms to compile, and Rust takes 2s, but you just spent 20 seconds commenting unused vars in your Zig code, then the slow compiler comes out ahead. It's a great example of how good UX can be more important than raw pe
77.
▲
by
TakeBlaster16
4y ago
The patch works, but it's not efficient to have every user patch their own compiler on every release (and forgo the system package manager for upgrades). I was also envisioning adding a warning system, changing the checks to warnings i
78.
▲
by
TakeBlaster16
4y ago
Zig is the new HN clickbait, taking over Rust's spot. That's a good sign for the language, honestly
79.
▲
by
TakeBlaster16
4y ago
That's the one thing keeping me from considering Zig for new projects right now. If some enterprising young developer is reading this and wants to make a name for themselves, you should fork the Zig compiler and change those errors to
80.
▲
by
TakeBlaster16
4y ago
I understand wanting to protect real-life children, but I'll never understand why we need to protect drawings of fictional bears
81.
▲
by
TakeBlaster16
4y ago
What if they ran official Microsoft servers with moderated chat, but also let you join custom servers after showing a scary warning message (and maybe checked your account birthday or something too). Would that not be enough to free them of
82.
▲
by
TakeBlaster16
4y ago
If I had to bet, I'd say it's 3. the C-suite not understanding what they do. Borrowing from the old IT truism: "We've never had a security breach, what am I paying you for?" "We're having a security breach
83.
▲
by
TakeBlaster16
4y ago
No, but I have paid Stripe 3 cents on the dollar for pretty much all of the above. To be fair our business was much smaller than Patreon
84.
▲
by
TakeBlaster16
4y ago
I had the same thought. I guess you and I are talking about the same Order? If so, I'll see you tomorrow evening!
85.
▲
by
TakeBlaster16
4y ago
I've always felt bad about 133% and this thread is putting things in perspective for me
86.
▲
by
TakeBlaster16
4y ago
Maybe he should have said, "I encourage readers to skip any interview that discusses views not listed on this 3x5 card"
87.
▲
by
TakeBlaster16
4y ago
All our problems would be solved if we simply jailed everyone who put the wrong kind of mushrooms on their pizza
88.
▲
by
TakeBlaster16
4y ago
I wish there was a showroom or something I could visit to try them all out and see what fits my hands. I don't mind dropping $300 on a keyboard once, but I don't want to buy 10 different keyboards just to try them and then have to
89.
▲
by
TakeBlaster16
4y ago
Yeah I agree with you! Most new compilers these days are built with these kinds of diagnostics baked in from the start. Since the compiler is doing analysis anyway, it's well-positioned to expose that information to the user. The one t
90.
▲
by
TakeBlaster16
4y ago
That's hilarious, I had no idea! I'm glad I didn't embarrass myself by proposing an RFC. Thanks for the links!
More ›