couchand

61 ms·

781.
by couchand 7y ago
You're right in that a lot of policy debate these days is folks talking past each other, ignoring their irreconcilable fundamental assumptions. But a discussion artifically limited to discussing those in the abstract will go nowhere. M
782.
by couchand 7y ago
You are clearly not the target audience for Signal. There of course is a space for the type of app you're describing, but saying that the tradeoff that Signal has chosen was a mistake is to misunderstand the goal there.
783.
by couchand 7y ago
Yes, the difference being that a phone number is an established identity mechanism and you likely already know it.
784.
by couchand 7y ago
At the expense of being practically unusable for most people. It's a trade off. EDIT: This proposal also suffers from a bootstrapping problem. You have to already have a secure channel to communicate the ids.
785.
by couchand 7y ago
A big part of practical security is usability. It's hard enough getting most people to adopt Signal or other encrypted messaging services. If they couldn't "just send a message to a number" it would be that much more dif
786.
by couchand 7y ago
Perhaps Rust, using Pin? I'm not entirely clear on the guarantees made there, perhaps an expert could weigh in on if that's a viable option?
787.
by couchand 7y ago
Previous discussion: https://news.ycombinator.com/item?id=18703245
788.
by couchand 7y ago
Is your parser general-purpose? Is it template-based? Is the performance variance due only to the impact on the processor's cache or are there other factors? Is the code open-source, maybe I could just look myself?
789.
by couchand 7y ago
I also would much rather write code that doesn't quite do what it's supposed to if it's easier to do and I can take an extra day off. However, that's not my job.
790.
A New Clue to How Life Originated(theatlantic.com)
77 points by couchand 7y ago|3 comments
791.
by couchand 7y ago
> horizontal nav bars often used bar/pipe characters to separate links, and still probably do in footers and dusty corners... You mean like in the HN footer?
792.
by couchand 7y ago
"You may well ask: 'Why direct action? Why sit ins, marches and so forth? Isn't negotiation a better path?' You are quite right in calling for negotiation. Indeed, this is the very purpose of direct action. Nonviolent di
793.
by couchand 7y ago
It needs to not just be better. It would need to be better in ways that aren't achievable with the alternative, and sufficiently better that it justifies the cost in terms of space and management requirements imposed.
794.
by couchand 7y ago
There's a significant practical difference between importing the complexity at build time versus as part of the running application. Building on top of a compiler is not the same thing as importing external code.
795.
by couchand 7y ago
I doubt there will ever be a language that doesn't have its own conventions and patterns. The practical question here is the risk when the convention is missed. In Rust, the object cannot be half-initialized when the pattern is missed.
796.
by couchand 7y ago
> Check if the value different than the default, e.g., empty string which is a worse version of the GP's > explicitly encode an empty/null state in your values
797.
by couchand 7y ago
A library version with unfixed security vulnerabilities absolutely should be classified as "shouldn't use".
798.
by couchand 7y ago
To be fair, in this case the linked page is a subdirectory of the main Puppeteer project.
799.
by couchand 7y ago
You just reminded me that slate.com frequently tells me I'm offline after clicking the back button.
800.
by couchand 7y ago
> But I have tremendous power to protect against far more likely causes of harm like diabetes and heart disease and obesity. Not to mention cars, guns, and drowning.
801.
by couchand 7y ago
> the lifetime needs to be 'static only as the task starts to execute. It would seem the lifetime needs to be coerceable to the lifetime of the executor, but as far as I can tell never really should need to be 'static. > Mos
802.
by couchand 7y ago
I had not seen that particular example, thanks for providing the citation. Perhaps I'm just being stubborn here, but allow me a moment. Isn't the core issue there that the executor requires the future to have a lifetime of '
803.
by couchand 7y ago
My working theory is that async/await syntax causes more problems than it solves. I've read through the RFC and many of the comments, but I don't see anywhere a cogent argument why the syntax is needed -- that seems to be ta
804.
by couchand 7y ago
I'd like to hear about the distinction between promises/futures and async/await. The former is absolutely a useful abstraction, requires no special features to implement, and thus is already widespread. The latter adds synt
805.
by couchand 7y ago
Well, the "official rules" depend on which side of the Great Schism you fall on.
806.
At Work, Expertise Is Falling Out of Favor(theatlantic.com)
3 points by couchand 7y ago|1 comments
807.
by couchand 7y ago
Seems like a pretty classic case of second system syndrome to me.
808.
by couchand 7y ago
> It is still floating point, which means you still need to really watch what you are doing, but it's very high precision. The key difference between a decimal type (in any language) (regardless whether it's fixed-point or fl
809.
by couchand 7y ago
If you are thinking about a Waldorf school (or any private school, for that matter), make sure to check out the vaccination rates first.
810.
by couchand 7y ago
I appreciate the general sentiment in having a reproducible work environment. But I must ask if the complexity of running and tunneling X is needed -- what desktop software are you running in this environment?

More ›