jacobparker

16 ms·

91.
by jacobparker 9y ago
Skimming, but it doesn't look like these optimizations are relevant to .NET standard (which is a formal specification of a set of APIs - not a particular implementation.)
92.
by jacobparker 9y ago
> I recently watched your video citing all the mathematical evidence that correctness may not decompose For myself and others, are you referring to the video here: https://pron.github.io/posts/correctness-and-comple
93.
by jacobparker 9y ago
https://www.amazon.ca/Elements-Pizza-Unlocking-Secrets-World... I've been reading this book and it has a good mix of history/context, technique and recipes. It is aimed at folks with a regular oven. Its process fo
94.
by jacobparker 9y ago
I really like stuff like this. This tool is amazing for C++: https://godbolt.org/ It's really handy for popular architectures and it's nice that it has "real" compilers (GCC vs. clang vs. ICC.) I find it
95.
by jacobparker 9y ago
Wasn't expecting to see the reference to the 9p file system!
96.
by jacobparker 9y ago
Yeah, I wasn't being very generous. However, naming the function "qsort" is pretty dishonest. I agree that the proper quick-sort implementation is going to look pretty imperative (and involve mutation) which is why I get a bi
97.
by jacobparker 9y ago
It isn't. Perhaps you're missing the recursion (which, at each step, does two of those list appends.) Write this algorithm in an imperative language and it'll pretty clear that this is best/expected case O(n^2).
98.
by jacobparker 9y ago
On the slides for quick-sort, the author asks: > Why don’t they teach it like that in the algorithms course?) I'm sure they do sometimes. However, it is incorrect because quick-sort is an O(nlogn) in-place sort. This is a best-case
99.
by jacobparker 10y ago
This page is awesome. It's so much easier to read vs. AWS. The pie chart explaining why they are cheaper is well-designed (the use of layering to group the breakdown, numeric labels, aligning the important segment to 12 o'clock) a
100.
by jacobparker 10y ago
I'd give this a look: https://github.com/GoogleCloudPlatform/cloud-builders/tree/m... (unfortunately key links to Bazel docs are 404'ing.) Bazel is a general purpose build system that focuses on rep
101.
by jacobparker 10y ago
I get that, but I most users don't.
102.
by jacobparker 10y ago
It's tricky: how is a user supposed to distinguish between "this site doesn't support HTTPS at all" and "a MitM is making the HTTPS site slow so I give up and use the HTTP version"? What if it's their bank
103.
by jacobparker 10y ago
If all instructions complete within some constant deadline independent of N/the input then it does hold even if they take different amounts of time.
104.
by jacobparker 11y ago
(Off-topic) what do you think about marshalling for continuations from await? So the issue where on one hand it's confusing/surprising if you don't default to marshalling the continuation back to the thread (etc.) that create
105.
by jacobparker 11y ago
Yes and it doesn't even protect the password appreciably either. User logs in with HTTPS, gets redirected to HTTP site and the MitM throws up the "Incorrect password try again" page. User types their password and transmits it
106.
by jacobparker 11y ago
> It's also what they've been saying about iPhones for the last few years, even though it's now been shown to be untrue. Well, the model of phone in that case (5C) is 2.5 years old using a 3.5 year old version of their CPU
107.
by jacobparker 11y ago
Some modern tools to mitigate XSS/make XSS virtually impossible: - Content-Security-Policy https://developer.mozilla.org/en-US/docs/Web/Security/CSP/In... - The sandbox attribute on iframes: h
108.
by jacobparker 11y ago
There's also a 48 hour window and touch ID doesn't work initially after booting. https://support.apple.com/en-us/HT204587 Great design.
109.
by jacobparker 11y ago
You've missed Paul's point I think. Even running trusted code is unlikely to work as desired (and could still have negative consequences due to what isn't included in the "sandbox") for anything other than trivial p
110.
by jacobparker 11y ago
Er, I think you should re-read it :) > Unikernels are unfit for production not merely as implemented but as conceived: they cannot be understood when they misbehave in production — and by their own assertions, they never will be able to
111.
by jacobparker 11y ago
and always leaves from this neighborhood to this office on weekday mornings... gonna need a big blockchain to hide that.
112.
by jacobparker 11y ago
> There's no way to whitelist inline code That's not completely true - the nonce attribute (specify a nonce in the CSP header, have nonce=that on every script tag) or by sending the hashes of the inline scripts upfront in the C
113.
by jacobparker 11y ago
Here's a simple related tool I made: https://github.com/j3parker/hijack It's like tee but also creates a named pipe that gets hooked into stdin. It's pretty gross but in a pinch its been useful.
114.
by jacobparker 11y ago
I should have been more clear - I agree that its more complicated. My point was that regardless, it seems to resonate. I believe its because the complications look useful at a glance and layering a rigid model on top of git frees you from h
115.
by jacobparker 11y ago
> I thought it was a weird, over-engineered solution to a non-existent problem. To be fair, its a cookie-cutter approach that resonates with people unfamiliar with git but not ready/willing to invest the time to understand it deeply
116.
by jacobparker 11y ago
Damn, that was cool. Really liked the in-source 3d models and map.
117.
by jacobparker 11y ago
> This generation checks Wikipedia > Lee Siegel (born December 5, 1957)
118.
by jacobparker 11y ago
The 256 bit advice is golden if only to encourage people to not use GUIDs in these scenarios. GUIDs are unique--not necessarily unguessable. Any implementation may be using a CSPRNG but in general you shouldn't rely on that (unless its
119.
by jacobparker 11y ago
http://linux.die.net/man/3/exec Not a Go thing. "Shelling-out" is different.
120.
by jacobparker 12y ago
You store the salts with the hashes. The basic idea is that salts force attackers to actually do a hash ("slow") instead of pre-computing hashes for common passwords and doing a dictionary lookup ("fast".) All that is to

More ›