Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jjnoakes
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
79 ms
·
871.
▲
by
jjnoakes
10y ago
If you are traversing a tree in constant stack space, the closures your continuations are holding on to must be O(ln) in space and representing what would have been on the stack, right?
872.
▲
by
jjnoakes
10y ago
With rust you don't need to rewrite though. Just integrate it a little at a time.
873.
▲
by
jjnoakes
10y ago
Whoops, right you are!
874.
▲
by
jjnoakes
10y ago
I don't think the parent is talking about problems with shadowing.
875.
▲
by
jjnoakes
10y ago
I don't find rust verbose unless I am dealing with complex situations though; that was my point. Move-by-default, elided lifetimes on many parameters, etc, are all verbosity-free.
876.
▲
by
jjnoakes
10y ago
Can you give examples of C++ code which would not require you to keep the ownership or borrowing straight in your head, and which a port to Rust would cause you unnecessary verbosity? I usually find that if my C++ code required little to no
877.
▲
by
jjnoakes
10y ago
Accounts have to be created at some point, right? What is the issue?
878.
▲
by
jjnoakes
10y ago
No. He is saying he uses rust to avoid GC, but not just to avoid GC.
879.
▲
by
jjnoakes
10y ago
It isn't better. I don't think it was claimed to be. But if you really understand C, it should also not be a surprise that it works this way.
880.
▲
by
jjnoakes
10y ago
I think it more explains that you can do a lot without fully understanding what it is you are working with. Which can be good or bad.
881.
▲
by
jjnoakes
10y ago
If you start thinking about two dimensional arrays, you'll probably get close quickly.
882.
▲
by
jjnoakes
10y ago
If the macro is named appropriately, you don't have to go look up anything. And even if you do, you do it once (per project perhaps). No big deal. I mean, you don't go look up the definitions of every function that gets called, ev
883.
▲
by
jjnoakes
10y ago
Think more about two dimensional arrays.
884.
▲
by
jjnoakes
10y ago
> or use "they" instead, even though you mean a single person Using 'they' to mean a single person is valid though. https://en.oxforddictionaries.com/definition/they
885.
▲
by
jjnoakes
10y ago
With caching in front I wonder how big the risk is.
886.
▲
by
jjnoakes
10y ago
Appreciated.
887.
▲
by
jjnoakes
10y ago
> Here's another article you can argue with: > http://www.2uo.de/myths-about-urandom/ Which backs up my point that using /dev/urandom blindly without knowing about some of the edge cases isn't
888.
▲
by
jjnoakes
10y ago
> lots of articles about best practice leave out very rare edge cases I don't think that's an argument in support of leaving out edge cases, and even if you disagree in general, I think security articles should be more diligent
889.
▲
by
jjnoakes
10y ago
Unless no programs ever need to worry about that case (which is untrue), why not mention in a security gist purporting to be a list of crypto implementation suggestions? Why not be complete and list the caveat, instead of incomplete and pos
890.
▲
by
jjnoakes
10y ago
I said the article mentioned reasons one might want to use /dev/random (or be careful about blindly using /dev/urandom), not that the article recommends using /dev/random. But since you wrote the article you sh
891.
▲
by
jjnoakes
10y ago
The reasons I know about for using /dev/random are quoted in the article you yourself just posted here... https://sockpuppet.org/blog/2014/02/25/safely-generate-rando...
892.
▲
by
jjnoakes
10y ago
> It seems the root cause of traffic is a mismatch between jobs and housing Which I suspect is quite natural, because it is driven by a mismatch between where people want to be when they are working (commercial districts) and where peopl
893.
▲
by
jjnoakes
10y ago
You should post these reasons in your gist. As I thought, there are a few reasons one might want to use /dev/random. Blanket "don't use X" statements are much more useful with context and information about why not t
894.
▲
by
jjnoakes
10y ago
The "Avoid /dev/random" recommendation, can you elaborate on that?
895.
▲
by
jjnoakes
10y ago
I wasn't able to use either though, as I said above. My retail 2FA TOTP failed for my retail account, but my AWS 2FA TOTP worked for my retail account (and for my AWS account). So something shady is going on.
896.
▲
by
jjnoakes
10y ago
Did Amazon recently merge the retail 2FA TOTP setup and the AWS 2FA TOTP setup? My normal retail 2FA TOTP code failed, but my AWS code worked for getting me into the retail 2FA settings (and also into the AWS settings). Which seems really o
897.
▲
by
jjnoakes
10y ago
Tcl commands are lists, not strings. Or more precisely, they are coercible to strings or lists, but a well-formed Tcl command string is always coercible to a well-formed Tcl list (not all Tcl strings are coercible to lists).
898.
▲
by
jjnoakes
10y ago
Some think the level design and mechanics (different blocks and timings) are important. After all, pick any side scrollers or any first person shooters and you could say the same about those categories too, if you ignore the art, design, an
899.
▲
by
jjnoakes
10y ago
He said 3 platforms, but he meant (and listed, so the meaning was obvious) 3 languages, some of which are indeed portable to a very large number of platforms.
900.
▲
by
jjnoakes
10y ago
Why wait until 3 tries? Why not just require 1 second between all attempts?
More ›