Usually people make fun of the FSF for choosing crappy projects (see: bzr for emacs) because they are part of GNU instead of making pragmatic choices for technical reasons...
What I find interesting about this Perl rewrite is that Guile, ostensibly the official scripting language of GNU, has had excellent structured texinfo support for years now. It uses stexi which has the same structure as sxml, so you gain access to all of the really great Scheme XML processing tools, including SXSLT which is basically ideal for spitting out arbitrary formats.
Well, if an inhabited planet were only 15 or 30 light years away... there's a chance for some form of communication... a "hey we're a technological society" beacon at least. Having any evidence of another technological civilization in our neighborhood would be incredible, and might even inspire humanity to do things like colonize the solar system.
There's no evil conspiracy here (see the permissions the facebook "app" requests for example: just your name and email address); we just wanted to make it easier for people to login. I personally wouldn't use it (but I'm in the set of people who only grudgingly use facebook in the first place since everyone else is doing it), but folks immediately started using it, even without us mentioning that it existed.
Luckily, it's just an option, and will never supersede the native account system. Different strokes for different folks and insert other appropriate cliches here.
All of those minor infractions are already just bench trials, unless you lose and appeal. At least around these parts, however, you end up with around a year of continuances because the prosecution is never ready to go to trial, forcing you to appear six or more times (for up to the full court session... you can't leave until they get around to telling you they aren't ready for you, and they will purposefully make you wait there until the very end) before having your 15 minute trial. Of course, if you just plead guilty to foo, we'll recommend you only be fined bar and you won't have to suffer the shame of needing to skip out on work for a day at court every other month for a year...
You also have to pay for the jury trial, and all of your public defender time at something like $40/h if you lose. And if you lose and can't pay you are in contempt of the court...
A huge problem (at least here) is that traffic cases often escalate into new crimes... if you e.g. are ticketed for a headlight being out and fix it... to avoid paying the fine, you have to go to court! And if you miss the court date, your license is automatically suspended and you are charged with failure to appear (a warrant is then issued). And then you get pulled over again, this time arrested for driving while having a revoked license and evading an outstanding warrant, and failure to appear before the court, and you sassed that officer a bit so let's throw in resisting-delaying-or-obstructing an officer... I watched this absurd cycle dozens of times in my year waiting to be cleared for Thoughtcrime.
The emperor's legal code allows him to prosecute anyone, any time.
The big shame here is that... the reason we need Emacs is that X (well, and UNIX) sucks. All of these things should work everywhere.
A Lisp listener and UNIX shell are roughly equivalent; except the language provided by the Lisp shell is far more expressive. Instead of hundreds of blobs you call with arbitrary switches, piping around streams of bits disguised as strings... you have a library of tens of thousands of functions, with a sane calling convention, that document themselves interactively, etc. It just completely breaks down the barrier between programming and using the machine.
On most distros, openafs 1.6.x will install with $packagemanager $installcmd openafs-client. Before 1.6, installation could be a bit hairy (a few bits of manual config, kerberos needed manual local configuration), but nowadays basically everything autoconfigures through dns and you really only need to set a default realm/cell (even then, just for convenience). I hear the 1.7.x branch has made huge strides for Windows users too.
I think openafs gets a bad rap because pre-1.4 was kind of a pain to set up, and the early 1.4.x releases were pretty buggy (my cell directly inspired several of the early releases since we were just getting going and took the plunge early on). Nowadays (as in the last five years) it Just Works (tm) for the most part (certainly true of the client, and as true as it can be for a complicated UNIX server for the fileserver).
As someone who was hauled off for similar offenses ("standing in the wrong place near an object the police decided was not permitted on the ground that day" basically), I can tell you that you are wrong. If anyone is ever permitted to put up a tent in the area, anyone engaged in political protest has a right to put up a tent. You can only restrict political speech with clear regulations that are enforced universally, and serve a major public interest. Whether you like it or not, damned smelly hippies can set up tent cities and protest their hearts out, unless your state wants to ban even permitted use of tents. There are other precedents regarding spontaneous demostrations that weaken permit requirements.
Source: a year of sitting in court listening to the same trial about nine times over.
In the U.S., if you actually get access to the legal system, political speech is our most protected right.
The problem is that the moc implements something more like the Common Lisp Object System's metaobject protocol for C++; resolving symbols at runtime is a tiny portion of what it does. dlsym and analogues on other platforms are also horrendously unsafe; a one way ticket to strange segfault bugs when you cast the result to the wrong type. And since C/C++ types are not first class, you can't even construct the casts at runtime! (Ok, maybe C++11 has some new foo_cast template, I'll admit my C++ is a bit rusty). You're also ignoring issues of syntax — unfortunately C++ doesn't provide the needed tools to construct embedded grammars in the language, and performing the tasks moc automates can be incredibly awkward otherwise.
The standard xinput mechanisms have full tablet support now. You can even use use cheap knockoff tablets now thanks to digimend (I got one from monoprice and it's pretty great for messing around with handwriting recognition and I've discovered that image editing with a trackball + tablet is great). Unfortunately all tablets are kind of broken except in the latest release of X.org because of a bug with coordinate transformations (basically, the pointer jumps if you make pressure changes without moving because the code transforms the already transformed coordinates... it also left touchscreens pretty broken; the guy that fixed it caused something like a dozen ubuntu on nexus 7 bugs to be closed!).
I have some stuff at Peer1, and honestly... the reason they are there is that the main east coast trunk to europe is there. The ping times to Europe from there are limited by the speed of light alone. That, and the trading floors are in close physical proximity.
Thanks! Given that seeks and whatnot are similar to my old drive, I think I found a winner, possibly. I'm pretty sure I can just swing down to the ol' computer shop and pick this one up too instead of waiting a week for it online.
Ripping CDs is kind of a pain, mostly because of metadata. I have my owns tastes that aren't the same as the collective compromises that are freedb/musicbrainz (I'm glad they exist, since they save me a LOT of time, but consensus decision making processes...), and so I have to review the data for each cd anyway (I mean, I have my own notion of what the genres are for the albums so I at least have to enter those). Then you have the weird imports (I paid so much for the damned Mithotyn Japanese import with the extra track that was cut from release for a reason and only existed in one run, damnit!) and cds that I got here and there from bands no one has heard of (I'm not a hipster, but before bandcamp sometimes you grabbed a disc for $5 from some opening band at a merch stand, and in the early aughts you had to get metal cds shipped from Europe by sea because they took about a year more to be released in the ol' USA)... and then the whole "the collection spans over a decade of new and used acquisitions, some taken care of and some not and some perhaps pressed around the time I was born" bit with cdparanoia in never skip mode, and it ends up being a process you want to babysit.
Really, I just want to have as few intense ripping sessions as possible where I churn through a couple dozen discs until it's done. Spreading it out and doing it idly only leads to carelessness toward the end, disorder in the physical disc collection (I kept the cases + discs separate and really well organized, probably the only reason I'm able to churn through this effectively at all), etc.
I know I could tweak the tags afterward, but realistically that's not going to happen, or would take way longer. Right now I have an empty directory and a pair of binders full of discs grouped by artist (externally unsorted, internally by year, with the cases on racks matching the internal ordering), so what better time to hack together a few shells scripts, grab a good drive, and just do it right all at once? I want to have to revisit this ten or twenty years from now, not six months from now.
The worst part is that, until the mid 90s, there were architectures that made things convenient for garbage collection, heavy multithreading, type checking, etc. And then the C machine took over and... oops, now we need to speed up all of those things, but are stuck with architectures that make it difficult!
I did submit corrected data to freedb for maybe a third of them... but that lost things like the real genre of albums (and musicbrainz doesn't even pretend that anyone can agree on the genre of a piece of music). I still have my local cddb cache at least. Then there are the earlier rips in the collection where I didn't care as much, the typos, etc. I'm also changing how I store/tag multi discs albums; previously I did the usual "$TITLE (Disc $N)", but it seems the Right Way (tm) is to use the DISCNUMBER tag in one folder. And then I have a bunch of mixups between copyright years and release years in my current data.
Basically, my current data is just dodgy enough that I can't reuse it without manually checking anyway.
Luckily, virtualization requirements have led to tagged TLBs becoming available on at least x86. I think the number of processes that can share the TLB currently is fairly limited, but it's a start.
Slashdot Mirror
IGGT 1/10
Usually people make fun of the FSF for choosing crappy projects (see: bzr for emacs) because they are part of GNU instead of making pragmatic choices for technical reasons...
What I find interesting about this Perl rewrite is that Guile, ostensibly the official scripting language of GNU, has had excellent structured texinfo support for years now. It uses stexi which has the same structure as sxml, so you gain access to all of the really great Scheme XML processing tools, including SXSLT which is basically ideal for spitting out arbitrary formats.
Here's the thing with having a dozen crappy proprietary solutions: divide and conquer. Let them try, and watch them fail I say.
Well, if an inhabited planet were only 15 or 30 light years away... there's a chance for some form of communication... a "hey we're a technological society" beacon at least. Having any evidence of another technological civilization in our neighborhood would be incredible, and might even inspire humanity to do things like colonize the solar system.
There's no evil conspiracy here (see the permissions the facebook "app" requests for example: just your name and email address); we just wanted to make it easier for people to login. I personally wouldn't use it (but I'm in the set of people who only grudgingly use facebook in the first place since everyone else is doing it), but folks immediately started using it, even without us mentioning that it existed.
Luckily, it's just an option, and will never supersede the native account system. Different strokes for different folks and insert other appropriate cliches here.
It's worse than you might think.
All of those minor infractions are already just bench trials, unless you lose and appeal. At least around these parts, however, you end up with around a year of continuances because the prosecution is never ready to go to trial, forcing you to appear six or more times (for up to the full court session... you can't leave until they get around to telling you they aren't ready for you, and they will purposefully make you wait there until the very end) before having your 15 minute trial. Of course, if you just plead guilty to foo, we'll recommend you only be fined bar and you won't have to suffer the shame of needing to skip out on work for a day at court every other month for a year...
You also have to pay for the jury trial, and all of your public defender time at something like $40/h if you lose. And if you lose and can't pay you are in contempt of the court...
A huge problem (at least here) is that traffic cases often escalate into new crimes... if you e.g. are ticketed for a headlight being out and fix it... to avoid paying the fine, you have to go to court! And if you miss the court date, your license is automatically suspended and you are charged with failure to appear (a warrant is then issued). And then you get pulled over again, this time arrested for driving while having a revoked license and evading an outstanding warrant, and failure to appear before the court, and you sassed that officer a bit so let's throw in resisting-delaying-or-obstructing an officer... I watched this absurd cycle dozens of times in my year waiting to be cleared for Thoughtcrime.
The emperor's legal code allows him to prosecute anyone, any time.
The big shame here is that ... the reason we need Emacs is that X (well, and UNIX) sucks. All of these things should work everywhere.
A Lisp listener and UNIX shell are roughly equivalent; except the language provided by the Lisp shell is far more expressive. Instead of hundreds of blobs you call with arbitrary switches, piping around streams of bits disguised as strings... you have a library of tens of thousands of functions, with a sane calling convention, that document themselves interactively, etc. It just completely breaks down the barrier between programming and using the machine.
On most distros, openafs 1.6.x will install with $packagemanager $installcmd openafs-client. Before 1.6, installation could be a bit hairy (a few bits of manual config, kerberos needed manual local configuration), but nowadays basically everything autoconfigures through dns and you really only need to set a default realm/cell (even then, just for convenience). I hear the 1.7.x branch has made huge strides for Windows users too.
I think openafs gets a bad rap because pre-1.4 was kind of a pain to set up, and the early 1.4.x releases were pretty buggy (my cell directly inspired several of the early releases since we were just getting going and took the plunge early on). Nowadays (as in the last five years) it Just Works (tm) for the most part (certainly true of the client, and as true as it can be for a complicated UNIX server for the fileserver).
I don't think the poster is a native speaker and I fixed a bunch of other obvious typos... but missed that extra zero there.
"With the release of Cordova 2.2, Enyo 2.0 is now supported on webOS up to version 3.0.5, which includes the Community Edition"
I didn't manage to score a touchpad during the firesale, so I can't confirm.
As someone who was hauled off for similar offenses ("standing in the wrong place near an object the police decided was not permitted on the ground that day" basically), I can tell you that you are wrong. If anyone is ever permitted to put up a tent in the area, anyone engaged in political protest has a right to put up a tent. You can only restrict political speech with clear regulations that are enforced universally, and serve a major public interest. Whether you like it or not, damned smelly hippies can set up tent cities and protest their hearts out, unless your state wants to ban even permitted use of tents. There are other precedents regarding spontaneous demostrations that weaken permit requirements.
Source: a year of sitting in court listening to the same trial about nine times over.
In the U.S., if you actually get access to the legal system, political speech is our most protected right.
I counted three options for President on my ballot, and many states have five or nine (NC has particularly bad ballot access laws).
The problem is that the moc implements something more like the Common Lisp Object System's metaobject protocol for C++; resolving symbols at runtime is a tiny portion of what it does. dlsym and analogues on other platforms are also horrendously unsafe; a one way ticket to strange segfault bugs when you cast the result to the wrong type. And since C/C++ types are not first class, you can't even construct the casts at runtime! (Ok, maybe C++11 has some new foo_cast template, I'll admit my C++ is a bit rusty). You're also ignoring issues of syntax — unfortunately C++ doesn't provide the needed tools to construct embedded grammars in the language, and performing the tasks moc automates can be incredibly awkward otherwise.
The standard xinput mechanisms have full tablet support now. You can even use use cheap knockoff tablets now thanks to digimend (I got one from monoprice and it's pretty great for messing around with handwriting recognition and I've discovered that image editing with a trackball + tablet is great). Unfortunately all tablets are kind of broken except in the latest release of X.org because of a bug with coordinate transformations (basically, the pointer jumps if you make pressure changes without moving because the code transforms the already transformed coordinates... it also left touchscreens pretty broken; the guy that fixed it caused something like a dozen ubuntu on nexus 7 bugs to be closed!).
I have some stuff at Peer1, and honestly... the reason they are there is that the main east coast trunk to europe is there. The ping times to Europe from there are limited by the speed of light alone. That, and the trading floors are in close physical proximity.
I don't, but then again I have a quarter cab filled with servers ;)
Have you ever tried to light a bucket of diesel on fire? It isn't like in the movies.
Thanks! Given that seeks and whatnot are similar to my old drive, I think I found a winner, possibly. I'm pretty sure I can just swing down to the ol' computer shop and pick this one up too instead of waiting a week for it online.
Exactly!
Ripping CDs is kind of a pain, mostly because of metadata. I have my owns tastes that aren't the same as the collective compromises that are freedb/musicbrainz (I'm glad they exist, since they save me a LOT of time, but consensus decision making processes...), and so I have to review the data for each cd anyway (I mean, I have my own notion of what the genres are for the albums so I at least have to enter those). Then you have the weird imports (I paid so much for the damned Mithotyn Japanese import with the extra track that was cut from release for a reason and only existed in one run, damnit!) and cds that I got here and there from bands no one has heard of (I'm not a hipster, but before bandcamp sometimes you grabbed a disc for $5 from some opening band at a merch stand, and in the early aughts you had to get metal cds shipped from Europe by sea because they took about a year more to be released in the ol' USA)... and then the whole "the collection spans over a decade of new and used acquisitions, some taken care of and some not and some perhaps pressed around the time I was born" bit with cdparanoia in never skip mode, and it ends up being a process you want to babysit.
Really, I just want to have as few intense ripping sessions as possible where I churn through a couple dozen discs until it's done. Spreading it out and doing it idly only leads to carelessness toward the end, disorder in the physical disc collection (I kept the cases + discs separate and really well organized, probably the only reason I'm able to churn through this effectively at all), etc.
I know I could tweak the tags afterward, but realistically that's not going to happen, or would take way longer. Right now I have an empty directory and a pair of binders full of discs grouped by artist (externally unsorted, internally by year, with the cases on racks matching the internal ordering), so what better time to hack together a few shells scripts, grab a good drive, and just do it right all at once? I want to have to revisit this ten or twenty years from now, not six months from now.
Hey this is /., I thought we all used Linux here.
The worst part is that, until the mid 90s, there were architectures that made things convenient for garbage collection, heavy multithreading, type checking, etc. And then the C machine took over and ... oops, now we need to speed up all of those things, but are stuck with architectures that make it difficult!
RPC1! I think that's the site where I found all of the info that led to my getting the DRU-810a actually.
I did submit corrected data to freedb for maybe a third of them... but that lost things like the real genre of albums (and musicbrainz doesn't even pretend that anyone can agree on the genre of a piece of music). I still have my local cddb cache at least. Then there are the earlier rips in the collection where I didn't care as much, the typos, etc. I'm also changing how I store/tag multi discs albums; previously I did the usual "$TITLE (Disc $N)", but it seems the Right Way (tm) is to use the DISCNUMBER tag in one folder. And then I have a bunch of mixups between copyright years and release years in my current data.
Basically, my current data is just dodgy enough that I can't reuse it without manually checking anyway.
Luckily, virtualization requirements have led to tagged TLBs becoming available on at least x86. I think the number of processes that can share the TLB currently is fairly limited, but it's a start.