Has no-one else yet commented to point out that Opera has run plugins in a separate process for years now? Then I guess I have to.
Not to minimize the accomplishments of the Firefox developers, I mean, and getting this feature to the Firefox userbase is valuable in and of itself, and so on. But there is precedent.
If you're going to go there, might as well go all the way: Bingo Is Not GO. Except that sounds too much like a certain other search engine concern... and LINGO is probably taken... so maybe Ringo Is Not GO?
The system used in the roguelike Linley's Dungeon Crawl (and its currently-maintained fork, Stone Soup) mostly takes care of that: when you get XP, you also get an equal number skill points; whenever an action practices a skill, some number of points from that skill pool are transferred into the skill, and eventually the skill levels up. If the pool is empty, you don't gain skill. (Also, in the skill screen, skills can be set to not be actively practiced, which greatly reduces the skill points consumed by using them; this is for things like if you're using a given type of weapon but don't plan on specializing in it.)
In practice, there's still some incidence of "victory dancing" --- after a big kill, standing around repeatedly casting some spell to make sure that the points go into some particular magic skill(s) --- but not much, and because the points would have gone into something useful anyway, it's more a question of whether the player actually wants to do that kind of powergaming.
No need to redact that. It's a link-local, non-routable address []
The lower 64 bits almost certainly contain the interface's MAC address; while it's not as bad as a globally reachable network address, some people still might not want to post it openly on/.
The thing you read somewhere is wrong. There does exist the XGrabServer call, which some window managers use in some cases (mostly older WMs, I suspect), but the documentation strongly recommends using it as little as possible. In no case is anything like that inherent in X11.
It'll be deprecated in NetBSD 5.0 (which will be out Real Soon Now; it's well into the release candidate stage), and removed in 6.0; it's already been removed from -current (the CVS HEAD). 5.0 is also the first release to have WAPBL, the new journaling scheme.
The idea is that programs are written in a heavily restricted subset of x86 that can be proven safe, where "safe" here basically boils down to not being able to make system calls or otherwise interact with the world without going through the sandbox library. The program might still be compromised by a third party if it's badly written, but then the attacker won't be able to escape the sandbox either.
And one person (i.e., me) to mention drum storage from back in the old days (i.e., before I was born), just like every other time it's come up and I've seen it and been bothered to comment, and probably with a link to multicians.org.
You can't do lambda calculus in Python. I tried, it gave me idiotic syntax errors. Something about the lambda keyword being a crippled piece of shit.
No, you can still use the lambda calculus. You just have to Church-encode all your data types, use beta-redexes for variable binding and the Y combinator for recursion (and thus loops), and so on for any language feature you want to use which is "supposed to be" a statement.
Only problem is that you'll run out of stack eventually, as Python lacks proper tail calls.
Given Apple's tendencies lately with the mechanics of their keyboards, I find it hard to get all that excited about the idea of such a keyboard from them.
(Sigh. I remember when Apple took out a two-page ad for the PowerBook line where (among other things, of course) they boasted about employing dedicated "keyboard engineers" to get the action of the keys just right. Those days are clearly no longer.)
They allocate the memory in a way that OS takes the memory when needed.
I don't know of any OS that provides such a facility.
Some flavors of Unix allege to support this, through madvise(), with MADV_FREE; this isn't standardized, though, and I don't know how well it actually works.
Slashdot Mirror
Has no-one else yet commented to point out that Opera has run plugins in a separate process for years now? Then I guess I have to.
Not to minimize the accomplishments of the Firefox developers, I mean, and getting this feature to the Firefox userbase is valuable in and of itself, and so on. But there is precedent.
Hail, hail, fire and snow.
Call the dolphin; we will go.
Far away, for to see,
friendly dolphin, come to me.
No, that'd be Craigslist.
If you're going to go there, might as well go all the way: Bingo Is Not GO. Except that sounds too much like a certain other search engine concern... and LINGO is probably taken... so maybe Ringo Is Not GO?
Good grief. Homophone insanity. We've got Clojure [...] "closures" [...] And now Google jumps in with "Closure"
It's worse than that; there's also Clozure Common Lisp.
The system used in the roguelike Linley's Dungeon Crawl (and its currently-maintained fork, Stone Soup) mostly takes care of that: when you get XP, you also get an equal number skill points; whenever an action practices a skill, some number of points from that skill pool are transferred into the skill, and eventually the skill levels up. If the pool is empty, you don't gain skill. (Also, in the skill screen, skills can be set to not be actively practiced, which greatly reduces the skill points consumed by using them; this is for things like if you're using a given type of weapon but don't plan on specializing in it.)
In practice, there's still some incidence of "victory dancing" --- after a big kill, standing around repeatedly casting some spell to make sure that the points go into some particular magic skill(s) --- but not much, and because the points would have gone into something useful anyway, it's more a question of whether the player actually wants to do that kind of powergaming.
The lower 64 bits almost certainly contain the interface's MAC address; while it's not as bad as a globally reachable network address, some people still might not want to post it openly on /.
The thing you read somewhere is wrong. There does exist the XGrabServer call, which some window managers use in some cases (mostly older WMs, I suspect), but the documentation strongly recommends using it as little as possible. In no case is anything like that inherent in X11.
Greg Egan's website has a little Java applet to visualise what happens to light around a black hole, dated 2001.
He's got a bunch of other fun stuff there, explaining/"demonstrating" the strange physics (real and theoretical) used in his books and stories.
It'll be deprecated in NetBSD 5.0 (which will be out Real Soon Now; it's well into the release candidate stage), and removed in 6.0; it's already been removed from -current (the CVS HEAD). 5.0 is also the first release to have WAPBL, the new journaling scheme.
The idea is that programs are written in a heavily restricted subset of x86 that can be proven safe, where "safe" here basically boils down to not being able to make system calls or otherwise interact with the world without going through the sandbox library. The program might still be compromised by a third party if it's badly written, but then the attacker won't be able to escape the sandbox either.
Smalltalk did this in the '70s, and the idea goes back to APL in the early '60s.
And, perhaps more to the point, Multics, also in the '60s.
You're looking for RFC 1924: A Compact Representation of IPv6 Addresses, which uses base 85. Note the publication date.
Opera, at least on Unixes, does this with all plugins.
And one person (i.e., me) to mention drum storage from back in the old days (i.e., before I was born), just like every other time it's come up and I've seen it and been bothered to comment, and probably with a link to multicians.org.
Also done 35 years ago by Multics, where it was called "page multilevel". Somewhat different storage technologies in that case, but with similar characteristics.
You can't do lambda calculus in Python. I tried, it gave me idiotic syntax errors. Something about the lambda keyword being a crippled piece of shit.
No, you can still use the lambda calculus. You just have to Church-encode all your data types, use beta-redexes for variable binding and the Y combinator for recursion (and thus loops), and so on for any language feature you want to use which is "supposed to be" a statement.
Only problem is that you'll run out of stack eventually, as Python lacks proper tail calls.
No need for administrative action; a simple call to mlock(2) should do.
I wrote an X11 display manager (in the sense of xdm) with Perl/Tk. What do I win?
Given Apple's tendencies lately with the mechanics of their keyboards, I find it hard to get all that excited about the idea of such a keyboard from them.
(Sigh. I remember when Apple took out a two-page ad for the PowerBook line where (among other things, of course) they boasted about employing dedicated "keyboard engineers" to get the action of the keys just right. Those days are clearly no longer.)
No, not beers; bears.
Or you could use a 36-bit word-addressed architecture, like the PDP-10 and the Multics hardware did.
Some flavors of Unix allege to support this, through madvise(), with MADV_FREE; this isn't standardized, though, and I don't know how well it actually works.
Do the movie studios have private lines for their UDP-based bulk transfers, or do the protocols actually do some kind of congestion control?
It's also a lot like old-fashioned drum memory.