Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
fmstephe
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
61.
▲
by
fmstephe
11y ago
"I'm relieved to hear that at least it doesn't pollute beyond module boundaries." This isn't true, it is easy to come up with an example where lack of safety spreads past module boundaries. impl Vec<T> {
62.
▲
by
fmstephe
11y ago
This is good advice. I am totally confused by the Rust vs Go debate. They occupy such different spaces.
63.
▲
by
fmstephe
11y ago
Can you clarify those statements. I have seen that segment and would be interested to know about misinformation in it. Or are you talking about a different segment?
64.
▲
by
fmstephe
11y ago
Go supports this, I think. I am not quite sure what is meant by object relative layout. In Go: A struct is laid out as you declared it, with possible compiler added padding. A struct value field (not a pointer) in another struct is laid out
65.
▲
by
fmstephe
11y ago
(A great thing about HN is getting to talk with the authors directly) I didn't recognise that you were talking chiefly about javascript. It is true that my example doesn't apply here. Ok, then I would make one comment (and edit my
66.
▲
by
fmstephe
11y ago
EDIT: The article is about javascript. Everything below does not apply to javascript. You need more than one thread, at least, for any of these problems. I strongly suspect that combining async streams will prove to be a problem in practice
67.
▲
by
fmstephe
11y ago
My understanding is that it is both. This really is a real breakthrough in quantum computing. Specifically for an approach called 'quantum annealing' which is one of many (there is at least one other) possible approaches to quantu
68.
▲
by
fmstephe
11y ago
When reading any articles about psychology now I always have in the back of my head the question "How many of these studies have been reporoduced?" There are a lot of valuable insights from this kind of research but right now it&#
69.
▲
by
fmstephe
11y ago
I suspect that you have had very similar experiences to the author. The author is quite clear that education is no indicator of ability to program. I think the author would be very happy admit your hard working very good developer friends i
70.
▲
by
fmstephe
11y ago
I would love to read an updated version of this. The fundamentals won't have changed much. But the details are changing and Urlich went into a lot of detail in this doc. Great Read.
71.
▲
by
fmstephe
11y ago
Can you elaborate about your experiences writing soft real-time in Go. Is your project open source?
72.
▲
Go and Polymer, so happy together
(medium.com)
3 points
by
fmstephe
11y ago
|
0 comments
73.
▲
by
fmstephe
11y ago
If you like Go I have written a ringbuffer library here https://github.com/fmstephe/flib have a look in queues/spscq. spsc here stands for single producer, single consumer. I gave a talk in London about these que
74.
▲
by
fmstephe
11y ago
I am curious about the limitations around memory layout. Go provides a fair amount of control to the programmer. Fields appear in the order declared in a struct (although potentially padded), structs declared as values, not pointers, are lo
75.
▲
by
fmstephe
11y ago
Great paper, I am building a red-black tree at the moment (well, rebuilding one I wrote earlier), so I will try test out some of the techniques described here and see if I can get any speed out of it. If I get any clear results, I'll p
76.
▲
Confessions of a Private Space Rocket Engineer
(popularmechanics.com)
44 points
by
fmstephe
11y ago
|
9 comments
77.
▲
Confessions of a Private Space Rocket Engineer
(popularmechanics.com)
1 points
by
fmstephe
11y ago
|
0 comments
78.
▲
by
fmstephe
11y ago
I'm glad I commented on your comment. You certainly were describing much more that out-of-order execution. Good food for thought :)
79.
▲
by
fmstephe
11y ago
Modern CPUs do exactly this right now. If you are using a powerful x86 (not an old atom), it will process your software out of order. Both your compiler and the CPU itself are aggressively trying to execute as many LOADs as possible before
80.
▲
by
fmstephe
11y ago
This can be done now with hyper-theads. It is discussed in Ulrich Drepper's excellent 'What every programmer should know about memory' in section 6.3.4. http://www.akkadia.org/drepper/cpumemory.pdf To be
81.
▲
by
fmstephe
11y ago
Zing's ReadyNow is useful but really highlights some of the problems with JITs (in some domains). I think that ReadyNow is very interesting because its existence points to some interesting consequences of JITs in performance sensitive
82.
▲
by
fmstephe
11y ago
Keep sending your long emails. I have butterflies in my stomach. Very excited.
83.
▲
by
fmstephe
11y ago
It is really good to see Go's garbage collector claims backed up in the real world. In my experience GC pauses are a real problem, I hope this really works. As a niggle, it's a shame when people report averaged latencies. Since la
84.
▲
by
fmstephe
11y ago
Good point :)
85.
▲
by
fmstephe
11y ago
Digital Ocean is (I believe) a virtual machine hosting service. You get a VM with some OS and an ip address. Google App Engine is a very tightly controlled, and very inflexible, system for deploying applications which use google's App
86.
▲
by
fmstephe
11y ago
Thanks for this post. That is very interesting. It seems like a shame, because a project like this is a long road. If they haven't built a place where work can continue it will likely fade away. I would love to see a sustainable, non-v
87.
▲
by
fmstephe
11y ago
That is very exciting. I am glad to hear about fairly substantial amounts of money being granted for this kind of project. I wish them well, but I won't be jumping on board this bus for a while.
88.
▲
by
fmstephe
11y ago
>... another important dimension to consider. That's it, right there. One crucial point is that the elegant simplicity of the 'programming language power' rating is in fact full of messy bits and a multitude of dimensions.
89.
▲
by
fmstephe
11y ago
I would expect it to be very hard to distinguish between a temporary crash and a long term price movement. Prices are moving all the time and often for good reason. This strategy would have bought up large amounts of Nokia stock shortly bef
90.
▲
by
fmstephe
11y ago
It must be a sign that I am getting old, but your story of considered pragmatic compromise warms my heart. :)
More ›