I chose in JS to follow Nescape 2's single-threaded callback model. Shared memory concurrency w/o preemption. Like old Unix kernel at splhi.
-
-
Replying to @BrendanEich @kragen and
No-special-form downside real: a sleep (kernel function) call buried in evolved callgraph => friend&I went to NZ/Oz in '90 to fix in field.
1 reply 1 retweet 6 likes -
Right! Did it reboot or just hang forever?
1 reply 0 retweets 0 likes -
Replying to @bahstgwamt @kragen and
SMP Unix (Irix) kernel crash - non-deterministic (race condition). PTY load factor correlated, so friend wrote test that helped. Ultimately+
1 reply 0 retweets 3 likes -
Replying to @BrendanEich @kragen and
I found the rogue sleep call by code reading, thinking, sleeping+dreaming about it, having fenced in grep-results to likely callsite subset.
2 replies 0 retweets 2 likes -
So, I've heard people say that code is easy, compared to management. Stories like this make me doubt that assertion. What do you think?
3 replies 0 retweets 0 likes -
Replying to @bahstgwamt @kragen and
I can program for 16 hours straight and not be tired, but am exhausted after 8 hours of meetings.
3 replies 1 retweet 5 likes -
Which one accomplishes more?
1 reply 0 retweets 0 likes -
Replying to @bahstgwamt @kragen and
First and foremost, many world-class programmers work at Epic, so I am unlikely to write code that someone else couldn't write better.
1 reply 0 retweets 2 likes -
Replying to @TimSweeneyEpic @kragen and
But my coding often gives me perspective and insight into the future that I could never get through meetings, and that's useful.
1 reply 0 retweets 3 likes
Also, it makes me very happy.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.