Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
couchand
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
28 ms
·
361.
▲
by
couchand
4y ago
Not only had the WTC previously been bombed, it was the same group who did it! Their goal to destroy that particular symbol of American commerce wasn't exactly secret. The success of the plan is what's shocking. The visual symbol
362.
▲
by
couchand
4y ago
The article describes strategies to help when developing in weird languages. But they're helpful ideas for other contexts, too. When working with external systems or unfamiliar configuration formats, the same forces are at play. For i
363.
▲
by
couchand
4y ago
What's nice about an ADT is that you can actually prove you didn't mess up the tag union. The trust you get from that is a force enabler.
364.
▲
by
couchand
4y ago
> If you cannot say certain things easily, then write a function to factor the common stuff in a layer that you can then build upon. This is the basics of programming, and from what I've seen this is already where it fails in most r
365.
▲
by
couchand
4y ago
You're telling me kids won't chase a tiny ball around a yard or convince each other to consume things that are gross?
366.
▲
Why Rust is good for your car
(medium.com)
7 points
by
couchand
4y ago
|
0 comments
367.
▲
by
couchand
4y ago
I don't think I agree that we need three different things to handle them. We already have a general mechanism to convert an Option<T> to a T and panic on None, a method which shall not be named. So we just need get and get_unch
368.
▲
by
couchand
4y ago
But in real code you never want unwrap, so why provide sugar for it?
369.
▲
by
couchand
4y ago
I've come to believe ergonomics is a siren song here, mostly because recently I've been considering panics as forbidden as memory unsafety is... it's never okay for your embedded system or web server to panic, so don't a
370.
▲
by
couchand
4y ago
let innocent_var = operation_that_panics_but_returns_something_random_instead(); unsafe { do_something_assuming_validity(innocent_var); }
371.
▲
by
couchand
4y ago
Yes, Wrapping and Saturating very neatly provide behavior you might want in some context. I use them a lot in embedded contexts. Since indexing is nearly always fallible, it should be fallible!
372.
▲
by
couchand
4y ago
No, I'd rather it not compile!
373.
▲
by
couchand
4y ago
> Also it's worth noting that arithmetic is only checked against overflow when building in debug mode by default. Yes, the default behavior in release mode is even worse!
374.
▲
by
couchand
4y ago
> Crucially, by grepping for `unwrap` and `expect` you can find the panics very easily. I write Rust code up and down the stack, and this is the thing that ticks me off more than anything else. You can get most of them looking for this s
375.
▲
by
couchand
4y ago
In Rust code, if you're not able to locally reason that an array index is valid, it should be written with .get() and the None case handled appropriately. It's impossible to claim there's "no actual memory safety issue&q
376.
▲
by
couchand
4y ago
I'd agree that often with new features and subsytems recent LWN articles are the best documentation around.
377.
▲
by
couchand
4y ago
I've never seen an EDI implementation that required nothing custom. The claim is oft-repeated but based on little substance.
378.
▲
by
couchand
4y ago
It's really amusing how people addicted to rich text assume plain text suffers the same limitations.
379.
▲
by
couchand
4y ago
"my responses in red" assumes a lot about the visual abilities of the reader. I'm sure there's a better way to express this idea.
380.
▲
by
couchand
4y ago
The comment you're replying to describes how they wish the world would be, after recognizing the reality of the world as it is. Tipping should be illegal. Tipping is necessary currently most places. Both can be true.
381.
▲
by
couchand
4y ago
It's definitely not complete, if it were basically the whole lower half of the island would be highlighted.
382.
▲
by
couchand
4y ago
> a predictable and reliable monetary system. Now that's funny!
383.
▲
by
couchand
4y ago
This project from the NYPL has pretty good information: http://spacetime.nypl.org/the-changing-shoreline-of-nyc/
384.
▲
by
couchand
4y ago
Yubikeys can be stolen... I take it from the GP's description the access is sensitive enough to require more assurance than that.
385.
▲
by
couchand
4y ago
That being said, if instead of "use our custom app you've never seen to record a video" it's "just talk to a person with some standard video chat" then maybe it makes things a whole lot easier? But I don'
386.
▲
by
couchand
4y ago
A simple workaround for the implementation is to redirect you to a URL with the code hashed as a query parameter.
387.
▲
by
couchand
4y ago
If you're tending such a site as pure art project, fine. However, I suspect the site is there because you envision a community of potential users in this world. You are not "forced to register". You are asked by your commun
388.
▲
by
couchand
4y ago
> Let's allow simple harmless things to stay around. On private networks only, please. Otherwise, they will not be harmless for long. > For static http pages with permanent content, encryption is not really necessary. Unless you
389.
▲
by
couchand
4y ago
Yes and misusing simple allegories and therefore misunderstanding the situation is very common.
390.
▲
by
couchand
4y ago
Well this isn't exactly a currently-standing fence, so the metaphor falls down. It's more like someone coming upon their neighbor complaining about a mutual neighbor and their fence and offering them advice for the next confrontat
More ›