Slashdot Mirror

Vigile writes Over the weekend NVIDIA sent out its first official response to the claims of hampered performance on the GTX 970 and a potential lack of access to 1/8th of the on-board memory. Today NVIDIA has clarified the situation again, this time with some important changes to the specifications of the GPU. First, the ROP count and L2 cache capacity of the GTX 970 were incorrectly reported at launch (last September). The GTX 970 has 52 ROPs and 1792 KB of L2 cache compared to the GTX 980 that has 64 ROPs and 2048 KB of L2 cache; previously both GPUs claimed to have identical specs. Because of this change, one of the 32-bit memory channels is accessed differently, forcing NVIDIA to create 3.5GB and 0.5GB pools of memory to improve overall performance for the majority of use cases. The smaller, 500MB pool operates at 1/7th the speed of the 3.5GB pool and thus will lower total graphics system performance by 4-6% when added into the memory system. That occurs when games request MORE than 3.5GB of memory allocation though, which happens only in extreme cases and combinations of resolution and anti-aliasing. Still, the jury is out on whether NVIDIA has answered enough questions to temper the fire from consumers.

WheezyJoe writes Responding to the FCC's proposal to raise the definition of broadband from 4Mbps downstream and 1Mbps upstream to 25Mbps down and 3Mbps up, the lobby group known as the National Cable & Telecommunications Association (NCTA) wrote in an FCC filing Thursday that 25Mbps/3Mbps isn't necessary for ordinary people. The lobby alleges that hypothetical use cases offered for showing the need for 25Mbps/3Mbps "dramatically exaggerate the amount of bandwidth needed by the typical broadband user", referring to parties in favor of the increase like Netflix and Public Knowledge. Verizon, for its part, is also lobbying against a faster broadband definition. Much of its territory is still stuck on DSL which is far less capable of 25Mbps/3Mbps speeds than cable technology.

The FCC presently defines broadband as 4Mbps down and 1Mbps up, a definition that hasn't changed since 2010. By comparison, people in Sweden can pay about $40 a month for 100/100 mbps, choosing between more than a dozen competing providers. The FCC is under mandate to determine whether broadband is being deployed to Americans in a reasonable and timely way, and the commission must take action to accelerate deployment if the answer is negative. Raising the definition's speeds provides more impetus to take actions that promote competition and remove barriers to investment, such as a potential move to preempt state laws that restrict municipal broadband projects.

MojoKid writes After last Wednesday's Windows 10 event, early adopters and IT types were probably anxious for Microsoft to release the next preview build. Fortunately, it didn't take long as it came out on Friday, and it's safe to say that it introduced even more than many were anticipating (but still no Spartan browser). However, in case you missed it, DirectX 12 is actually enabled in this Windows 10 release, though unfortunately we'll need to wait for graphics drivers and apps that support it, to take advantage of DX 12 features and performance enhancements.

An anonymous reader writes In the recent Slashdot discussion on the D programming language, I was surprised to see criticisms of Pascal that were based on old information and outdated implementations. While I'm sure that, for example, Brian Kernighan's criticisms of Pascal were valid in 1981, things have moved on since then. Current Object Pascal largely addresses Kernighan's critique and also includes language features such as anonymous methods, reflection and attributes, class helpers, generics and more (see also Marco Cantu's recent Object Pascal presentation). Cross-platform development is fairly straightforward with Pascal. Delphi targets Windows, OS X, iOS and Android. Free Pascal targets many operating systems and architectures and Lazarus provides a Delphi-like IDE for Free Pascal. So what do you think? Is Pascal underrated?

SternisheFan (2529412) writes with this story at the Verge about an approach being considered by NASA to overcome some of the difficulties in moving a wheeled or multi-legged ground vehicle around the surface of Mars, which has proven to be a difficult task. Rover teams still have a tough time with the Martian surface even though they're flush with terrestrial data. The alien surface is uneven, and ridges and valleys make navigating the terrain difficult. The newest solution proposed by JPL is the Mars Helicopter, an autonomous drone that could 'triple the distances that Mars rovers can drive in a Martian day,' according to NASA. The helicopter would fly ahead of a rover when its view is blocked and send Earth-bound engineers the right data to plan the rover's route.

theodp writes Maybe Bill Gates' Summer Reading this year will include The Art of R Programming. Pushing further into Big Data, Microsoft on Friday announced it's buying Revolution Analytics, the top commercial provider of software and services for the open-source R programming language for statistical computing and predictive analytics. "By leveraging Revolution Analytics technology and services," blogged Microsoft's Joseph Sirosh, "we will empower enterprises, R developers and data scientists to more easily and cost effectively build applications and analytics solutions at scale." Revolution Analytics' David Smith added, "Now, Microsoft might seem like a strange bedfellow for an open-source company [RedHat:Linux as Revolution Analytics:R], but the company continues to make great strides in the open-source arena recently." Now that it has Microsoft's blessing, is it finally time for AP Statistics to switch its computational vehicle to R?

An anonymous reader writes After unveiling its new Project Spartan browser for Windows 10, Microsoft is now offering more details. The company confirmed that Windows 10 will also include Internet Explorer for enterprise sites, though it didn't say how exactly this will work. Spartan comes with a new rendering engine, which doesn't rely on the versioned document modes the company has historically used. It also provides compatibility with the millions of existing enterprise websites specifically designed for Internet Explorer by loading the IE11 engine when needed. In this way, the browser uses the new rendering engine for modern websites and the old one for legacy purposes.

The company is called TrackPIN, as is the product. Its creator, Mark Hall, showed it off at CES. Timothy pointed his camcorder at Mark as he explained how his product would let you get package deliveries safely when you aren't home by giving the UPS or FedEx (or other) delivery person access to your garage, as well as letting in selected people like your maid, your plumber, and possibly an aquarium cleaner. Each one can have a private, one-time PIN number that will actuate your garage door opener through the (~$250) TrackPIN keypad and tell your smartphone or other net-connected device that your garage was just opened, and by whom. You might even call this, "One small step for package delivery; a giant leap forward for the Internet of Things." Except those of us who don't have garages (not to mention electric garage door openers) may want to skip today's video; the TrackPIN isn't meant for the likes of us. (Alternate Video Link)

ageoffri writes: When Star Wars fans learned that George Lucas was making the prequels, most were filled with excitement and anticipation. When Episodes 1-3 were actually released, many found them unsatisfying, and became disillusioned with Lucas's writing. Now, it appears Disney felt the same way. Though they bought Lucasfilm and began production on Episode 7, they weren't interested in using the scripts Lucas had already worked on. In an interview, he said, "The ones that I sold to Disney, they came up to the decision that they didn't really want to do those. So they made up their own. So it's not the ones that I originally wrote [on screen in Star Wars: The Force Awakens]." After what happened with the prequels, that may be for the best — but others may worry about Episode 7's plot being entirely in the hands of Disney and JJ Abrams.

An anonymous reader writes with news that a journalist linked to Anonymous, Barret Brown, has been sentenced. "Barrett Brown, a journalist formerly linked to the hacking group Anonymous, was sentenced Thursday to over five years in prison, or a total of 63 months. Ahmed Ghappour, Brown's attorney, confirmed to Ars that Brown's 28 months already served will count toward the sentence. That leaves 34 months, or nearly three years, left for him to serve. In April 2014, Brown took a plea deal admitting guilt on three charges: "transmitting a threat in interstate commerce," for interfering with the execution of a search warrant, and to being "accessory after the fact in the unauthorized access to a protected computer." Brown originally was indicted in Texas federal court in December 2012 on several counts, including accusations that he posted a link from one Internet relay chat channel, called #Anonops, to another channel under his control, called #ProjectPM. The link led to private data that had been hijacked from intelligence firm Strategic Forecasting, or Statfor."

StartsWithABang writes The US Senate just voted on whether climate change is a hoax, knowing full well that debates or votes don't change what is or isn't scientifically true or valid. Nevertheless, debates have always been a thing in science, and they do have their place: in raising what points would be needed to validate, robustly confirm or refute competing explanations, theories or ideas. The greatest scientific debate in all of history — along with its conclusions — illustrates exactly this.

Today, the conclusion of my talk with Jim Blasko (here's part 1), who encourages you to go start your own crypto currency, because it's a fun exercise and because every entrant adds new ideas to the mix. As you'd expect, he's bullish about both his own Unbreakable Coin and cryptocurrencies more generally; how any given given currency performs, though, is an open question: U.S. dollars, Euros, or Yen may not go experience any meteoric rises, but their stability, even with inflation, is a nice feature, and so is their worldwide convertibility.

Regulation, speculation, fraud, and cultural fashions all play a role in making new currencies risky; reader mbkennel yesterday asked an insightful question: "Are you up to loaning bitcoin or something less popular for 10 years?" Confidence in any given currency can be tested with the terms current holders are willing to accept to make loans payable in that same currency. (On the other hand, if large companies will accept it in payment, they've probably got an idea that a given currency will be around next month or next year.) If you've bought any form of crypto currency, what's been your experience, and what do you expect in 10 years? (Alternate Video Link)

Today, the conclusion of my talk with Jim Blasko (here's part 1), who encourages you to go start your own crypto currency, because it's a fun exercise and because every entrant adds new ideas to the mix. As you'd expect, he's bullish about both his own Unbreakable Coin and cryptocurrencies more generally; how any given given currency performs, though, is an open question: U.S. dollars, Euros, or Yen may not go experience any meteoric rises, but their stability, even with inflation, is a nice feature, and so is their worldwide convertibility.

Regulation, speculation, fraud, and cultural fashions all play a role in making new currencies risky; reader mbkennel yesterday asked an insightful question: "Are you up to loaning bitcoin or something less popular for 10 years?" Confidence in any given currency can be tested with the terms current holders are willing to accept to make loans payable in that same currency. (On the other hand, if large companies will accept it in payment, they've probably got an idea that a given currency will be around next month or next year.) If you've bought any form of crypto currency, what's been your experience, and what do you expect in 10 years? (Alternate Video Link)

Today, the conclusion of my talk with Jim Blasko (here's part 1), who encourages you to go start your own crypto currency, because it's a fun exercise and because every entrant adds new ideas to the mix. As you'd expect, he's bullish about both his own Unbreakable Coin and cryptocurrencies more generally; how any given given currency performs, though, is an open question: U.S. dollars, Euros, or Yen may not go experience any meteoric rises, but their stability, even with inflation, is a nice feature, and so is their worldwide convertibility.

Regulation, speculation, fraud, and cultural fashions all play a role in making new currencies risky; reader mbkennel yesterday asked an insightful question: "Are you up to loaning bitcoin or something less popular for 10 years?" Confidence in any given currency can be tested with the terms current holders are willing to accept to make loans payable in that same currency. (On the other hand, if large companies will accept it in payment, they've probably got an idea that a given currency will be around next month or next year.) If you've bought any form of crypto currency, what's been your experience, and what do you expect in 10 years? (Alternate Video Link)

Today, the conclusion of my talk with Jim Blasko (here's part 1), who encourages you to go start your own crypto currency, because it's a fun exercise and because every entrant adds new ideas to the mix. As you'd expect, he's bullish about both his own Unbreakable Coin and cryptocurrencies more generally; how any given given currency performs, though, is an open question: U.S. dollars, Euros, or Yen may not go experience any meteoric rises, but their stability, even with inflation, is a nice feature, and so is their worldwide convertibility.

Regulation, speculation, fraud, and cultural fashions all play a role in making new currencies risky; reader mbkennel yesterday asked an insightful question: "Are you up to loaning bitcoin or something less popular for 10 years?" Confidence in any given currency can be tested with the terms current holders are willing to accept to make loans payable in that same currency. (On the other hand, if large companies will accept it in payment, they've probably got an idea that a given currency will be around next month or next year.) If you've bought any form of crypto currency, what's been your experience, and what do you expect in 10 years? (Alternate Video Link)

Today, the conclusion of my talk with Jim Blasko (here's part 1), who encourages you to go start your own crypto currency, because it's a fun exercise and because every entrant adds new ideas to the mix. As you'd expect, he's bullish about both his own Unbreakable Coin and cryptocurrencies more generally; how any given given currency performs, though, is an open question: U.S. dollars, Euros, or Yen may not go experience any meteoric rises, but their stability, even with inflation, is a nice feature, and so is their worldwide convertibility.

Regulation, speculation, fraud, and cultural fashions all play a role in making new currencies risky; reader mbkennel yesterday asked an insightful question: "Are you up to loaning bitcoin or something less popular for 10 years?" Confidence in any given currency can be tested with the terms current holders are willing to accept to make loans payable in that same currency. (On the other hand, if large companies will accept it in payment, they've probably got an idea that a given currency will be around next month or next year.) If you've bought any form of crypto currency, what's been your experience, and what do you expect in 10 years? (Alternate Video Link)

mikejuk writes: Atlas is a humanoid robot, one of the most advanced in the world. But it's always had cables that provided it with power and made it look a little like a dog on a leash. It was designed to provide a hardware platform for teams competing in the DARPA Robotics Challenge — a competition designed to encourage the construction of an effective disaster response robot. DARPA now says the finals of the challenge later in the year will require that the robots be completely wireless.

Power will be supplied by an onboard 3.7 kilowatt-hour lithium-ion battery. That battery will drive a variable-pressure pump which operates all of the hydraulic systems. The pump makes ATLAS much quieter, but introduces a complication for the teams: it can be run at low pressure to save power and then switched to high pressure to get harder work done. Managing power consumption will be a very difficult task, but DARPA has also upped the prize money to $3.5 million in total.

MojoKid writes: Dell has been strategically setting-up their new Venue 8 7000 tablet for cameo appearances over the past few months, starting back at Intel Developer's Forum in September of last year, then again at Dell World in November and at CES 2015. What's interesting about this new device, in addition to Intel's RealSense camera is its Atom Z3580 quad-core processor, which is based on Intel's latest Moorefield architecture. Moorefield builds upon Intel's Cherrytrail Atom feature set and offers two additional CPU cores with up to a 2.3GHz clock speed, an enhanced PowerVR 6430 GPU and support of faster LPDDR3-1600 memory. Moorefield is also built for Intel's XMM 7260 LTE modem platform, which supports carrier aggregation. Overall, Moorefield looks solid, with performance ahead of a Snapdragon 801 but not quite able to catch the 805, NVIDIA Tegra K1 or Apple's A8X in terms of graphics throughput. On the CPU side, Intel's beefed-up quad-core Atom variant shows well.

mdsolar sends this report from Bloomberg: Lawmakers in France want to create military zones around its 58 atomic reactors to boost security after this month's Paris terror attacks and almost two dozen mystery drone flights over nuclear plants that have baffled authorities.

"There's a legal void that needs to be plugged," said Claude de Ganay, the opposition member of the National Assembly spearheading legislation to be considered by parliament on Feb. 5. The proposals would classify atomic energy sites as "highly sensitive military zones" under the control of the Ministry of Defense, according to an outline provided by de Ganay.

AmiMoJo writes: On Friday, developer and doxing victim Zoe Quinn launched an online "anti-harassment task force" toolset, staffed by volunteers familiar with such attacks, to assist victims of a recent swell of "doxing" and "swatting" attacks. The Crash Override site, built by Quinn and game developer Alex Lifschitz, offers free services from "experts in information security, white hat hacking, PR, law enforcement, legal, threat monitoring, and counseling" for "victims of online mob harassment."

They have already managed to preemptively warn at least one victim of a swatting attempt in Enumclaw, Washington. As a result, the police department's head e-mailed the entire department to ask any police sent to the address in question to "knock with your hand, not your boot."

New submitter Solandri writes: When Mt. Vesuvius erupted in A.D. 79, it destroyed a library of classical works in Herculaneum. The papyrus scrolls weren't incinerated, but were instead carbonized by the hot gases. The resulting black carbon cylinders have mostly withstood attempts to read their contents since their discovery. Earlier attempts to unfurl the scrolls yielded some readable material, but were judged too destructive. Researchers decided to wait for newer technology to be invented that could read the scrolls without unrolling them.

Now, a team led by Dr. Vito Mocella from the National Research Council's Institute for Microelectronics and Microsystems (CNR-IMM) in Naples, Italy has managed to read individual letters inside one of the scrolls. Using a form of x-ray phase contrast tomography (abstract), they were able to ascertain the height difference (about 0.1mm) between the ink of the letters and the papyrus fibers which they sat upon. Due to the fibrous nature of the papyrus and the carbon-based ink, regular spectral and chemical analysis had thus far been unable to distinguish the ink from the paper. Further complicating the work, the scrolls are not in neat cylinders, but squashed and ruffled as the hot gases vaporized water in the papyrus and distorted the paper.

Las Vegas seems an appropriate place for cryptocurrency businesses to emerge, both because the coins themselves are so volatile that some gambling instinct may be required, and because Vegas is a high-tech outpost with lower taxes and lower rents than many other West Coast hot-spots, well-suited to risky startups with ambition but without huge venture backing.Jim Blasko moved there to work on low-voltage engineering for Penn & Teller, and is a qualified Crestron programmer, too (useful in a town that looks from the air like one giant light-show), but has shifted to a quite different endeavor, or rather a complex of them — all related to cryptocurrency. I ran into Blasko during this month's CES, at a forum with several other cryptocoin startups, and the next day we met to talk about just how hard (or easy) it is to get into this world as an entrepreneur.

Blasko has some advice for anyone who'd like to try minting a new cryptocurrency. Making your own coin, he says, is the easy part: anyone can clone code from an existing entrant, like Bitcoin, and rename the result — and that's exactly what he did. The hard work is what comes after: making worthwhile changes, building trust, and making it tradeable. Blasko's done the legwork to get his own currency, which he's bravely called "Unbreakable Coin," listed on exchanges like Cryptsy, and is working on his own auction site as well. He's also got an interesting idea for cryptocoin trading cards, and had a few prototypes on hand. (Part 1 is below; Part 2 to follow.) Alternate Video Link

jones_supa writes: The beta test phase of Steam Broadcasting feature has been completed. It is now available to everyone by updating the client to the newest version. The feature allows users to watch and stream games to and from users on your friends list. Right-clicking the name of a friend who is in-game offers the option to "Watch Game." This will send a request which needs to be accepted by the player so that the spectator can hop in. A chat is also included. Steam Broadcasting was first announced late last year as an alternative to third-party streaming services like Twitch, Ustream and Hitbox.

Bunnie Huang's Novena laptop re-invents the laptop with open source (and Free software) in mind, but the hackability that it's built for requires a fair amount of tolerance on a user's part for funky design and visible guts. New submitter dopeghost writes with word of the nearly-funded (via Crowd Supply) Librem laptop, a different kind of Free-software machine using components "specifically selected so that no binary blobs are needed in the Linux kernel that ships with the laptop." Made from high quality components and featuring a MacBook-like design including a choice of HiDPI screen, the Librem might just be the first laptop to ship with a modern Intel CPU that is not locked down to require proprietary firmware.

Richard M. Stallman, president of the FSF, said, "Getting rid of the signature checking is an important step. While it doesn't give us free code for the firmware, it means that users will really have control of the firmware once we get free code for it." Unlike some crowdfunding projects, this one is far from pie-in-the-sky, relying mostly on off-the-shelf components, with a planned shipping date in Spring of this year: "Purism is manufacturing the motherboard, and screen printing the keyboard. Purism is sourcing the case, daughter cards, memory, drives, battery, camera, and screen."

schwit1 writes: Shuji Nakamura won the 2014 Nobel Prize in Physics (along with two other scientists) for his work inventing blue LEDs. But long ago he abandoned Japan for the U.S. because his country's culture and patent law did not favor him as an inventor. Nakamura has now blasted Japan for considering further legislation that would do more harm to inventors.

"In the early 2000s, Nakamura had a falling out with his employer and, it seemed, all of Japan. Relying on a clause in Japan's patent law, article 35, that assigns patents to individual inventors, he took the unprecedented step of suing his former employer for a share of the profits his invention was generating. He eventually agreed to a court-mediated $8 million settlement, moved to the University of California, Santa Barbara (UCSB) and became an American citizen. During this period he bitterly complained about Japan's treatment of inventors, the country's educational system and its legal procedures. 'The problem is now the Japanese government wants to eliminate patent law article 35 and give all patent rights to the company. If the Japanese government changes the patent law it means basically there would no compensation [for inventors].'"

There is a similar problem with copyright law in the U.S., where changes to the law in the 1970s and 1990s have made it almost impossible for copyrights to ever expire. The changes favor the corporations rather than the individuals who might actually create the work.

mrspoonsi sends up an update on the investigation into Autonomy, a software company acquired by HP in 2011. HP paid a staggering $11.7 billion in the deal, then later wrote off $8.8 billion and claimed Autonomy's management intentionally defrauded them. The UK Serious Fraud Office opened a case on the matter in 2013, but that investigation has now been dropped. According to the Office's press release, they felt there was "insufficient evidence for a realistic prospect of conviction," given the information they had to work with. Autonomy is not off the hook, however — the case has now been entirely ceded to U.S. authorities.

Saint Aardvark writes If, like me, you administer FreeBSD systems, you know that (like Linux) there is an embarrassment of riches when it comes to filesystems. GEOM, UFS, soft updates, encryption, disklabels — there is a *lot* going on here. And if, like me, you're coming from the Linux world your experience won't be directly applicable, and you'll be scaling Mount Learning Curve. Even if you *are* familiar with the BSDs, there is a lot to take in. Where do you start? You start here, with Michael W. Lucas' latest book, FreeBSD Mastery: Storage Essentials. You've heard his name before; he's written Sudo Mastery (which I reviewed previously), along with books on PGP/GnuPGP, Cisco Routers and OpenBSD. This book clocks in at 204 pages of goodness, and it's an excellent introduction to managing storage on FreeBSD. From filesystem choice to partition layout to disk encryption, with sidelong glances at ZFS along the way, he does his usual excellent job of laying out the details you need to know without every veering into dry or boring. Keep reading for the rest of Saint Aardvark's review. FreeBSD Mastery: Storage Essentials author Michael W. Lucas pages 240 publisher Tilted Windmill Press rating 9/10 reviewer Saint Aardvark ISBN 0692343202 summary FreeBSD Mastery: Storage Essentials takes you on a deep dive into FreeBSD’s disk management systems. Do you need to know about GEOM? It's in here: Lucas takes your from "What *is* GEOM, anyway?" (answer: FreeBSD's system of layers for filesytem management) through "How do I set up RAID 10?" through "Here's how to configure things to solve that weird edge-case." Still trying to figure out GUID partitions? I sure was...and then I read Chapter Two. Do you remember disklabels fondly, and wonder whatever happened to them? They're still around, but mainly on embedded systems that still use MBR partitions — so grab this book if you need to deal with them.

The discussion of SMART disk monitoring is one of the best introductions to this subject I've ever read, and should serve *any* sysadmin well, no matter what OS they're dealing with; I plan on keeping it around for reference until we no longer use hard drives. RAID is covered, of course, but so are more complex setups — as well as UFS recovery and repair for when you run into trouble.

Disk encryption gets three chapters (!) full of details on the two methods in FreeBSD, GBDE and GELI. But just as important, Lucas outlines why disk encryption might *not* be the right choice: recovering data can be difficult or impossible, it might get you unwanted attention from adversaries, and it will *not* protect you against, say, an adversary who can put a keylogger on your laptop. If it still make sense to encrypt your hard drive, you'll have the knowledge you need to do the job right.

I said that this covers *almost* everything you need to know, and the big omission here is ZFS. It shows up, but only occasionally and mostly in contrast to other filesystem choices. For example, there's an excellent discussion of why you might want to use FreeBSD's plain UFS filesystem instead of all-singing, all-dancing ZFS. (Answer: modest CPU or RAM, or a need to do things in ways that don't fit in with ZFS, make UFS an excellent choice.) I would have loved to see ZFS covered here — but honestly, that would be a book of its own, and I look forward to seeing one from Lucas someday; when that day comes, it will be a great companion to this book, and I'll have Christmas gifts for all my fellow sysadmins.

One big part of the appeal of this book (and Lucas' writing in general) is that he is clear about the tradeoffs that come with picking one solution over another. He shows you where the sharp edges are, and leaves you well-placed to make the final decision yourself. Whether it's GBDE versus GELI for disk encryption, or what might bite you when enabling soft updates journaling, he makes sure you know what you're getting into. He makes recommendations, but always tells you their limits.

There's also Lucas' usual mastery of writing; well-written explanations with liberal dollops of geek humor that don't distract from the knowledge he's dropping. He's clear, he's thorough, and he's interesting — and that's an amazing thing to say about a book on filesystems.

Finally, the technical review was done by Poul Henning-Kamp; he's a FreeBSD developer who wrote huge parts of the GEOM and GBDE systems mentioned above. That gives me a lot of warm fuzzies about the accuracy of this book.

If you're a FreeBSD (or Linux, or Unix) sysadmin, then you need this book; it has a *lot* of hard-won knowledge, and will save your butt more than you'll be comfortable admitting.

You can purchase FreeBSD Mastery: Storage Essentials from amazon.com. Slashdot welcomes readers' book reviews (sci-fi included) -- to see your own review here, read the book review guidelines, then visit the submission page. If you'd like to see what books we have available from our review library please let us know.

Saint Aardvark writes If, like me, you administer FreeBSD systems, you know that (like Linux) there is an embarrassment of riches when it comes to filesystems. GEOM, UFS, soft updates, encryption, disklabels — there is a *lot* going on here. And if, like me, you're coming from the Linux world your experience won't be directly applicable, and you'll be scaling Mount Learning Curve. Even if you *are* familiar with the BSDs, there is a lot to take in. Where do you start? You start here, with Michael W. Lucas' latest book, FreeBSD Mastery: Storage Essentials. You've heard his name before; he's written Sudo Mastery (which I reviewed previously), along with books on PGP/GnuPGP, Cisco Routers and OpenBSD. This book clocks in at 204 pages of goodness, and it's an excellent introduction to managing storage on FreeBSD. From filesystem choice to partition layout to disk encryption, with sidelong glances at ZFS along the way, he does his usual excellent job of laying out the details you need to know without every veering into dry or boring. Keep reading for the rest of Saint Aardvark's review. FreeBSD Mastery: Storage Essentials author Michael W. Lucas pages 240 publisher Tilted Windmill Press rating 9/10 reviewer Saint Aardvark ISBN 0692343202 summary FreeBSD Mastery: Storage Essentials takes you on a deep dive into FreeBSD’s disk management systems. Do you need to know about GEOM? It's in here: Lucas takes your from "What *is* GEOM, anyway?" (answer: FreeBSD's system of layers for filesytem management) through "How do I set up RAID 10?" through "Here's how to configure things to solve that weird edge-case." Still trying to figure out GUID partitions? I sure was...and then I read Chapter Two. Do you remember disklabels fondly, and wonder whatever happened to them? They're still around, but mainly on embedded systems that still use MBR partitions — so grab this book if you need to deal with them.

The discussion of SMART disk monitoring is one of the best introductions to this subject I've ever read, and should serve *any* sysadmin well, no matter what OS they're dealing with; I plan on keeping it around for reference until we no longer use hard drives. RAID is covered, of course, but so are more complex setups — as well as UFS recovery and repair for when you run into trouble.

Disk encryption gets three chapters (!) full of details on the two methods in FreeBSD, GBDE and GELI. But just as important, Lucas outlines why disk encryption might *not* be the right choice: recovering data can be difficult or impossible, it might get you unwanted attention from adversaries, and it will *not* protect you against, say, an adversary who can put a keylogger on your laptop. If it still make sense to encrypt your hard drive, you'll have the knowledge you need to do the job right.

I said that this covers *almost* everything you need to know, and the big omission here is ZFS. It shows up, but only occasionally and mostly in contrast to other filesystem choices. For example, there's an excellent discussion of why you might want to use FreeBSD's plain UFS filesystem instead of all-singing, all-dancing ZFS. (Answer: modest CPU or RAM, or a need to do things in ways that don't fit in with ZFS, make UFS an excellent choice.) I would have loved to see ZFS covered here — but honestly, that would be a book of its own, and I look forward to seeing one from Lucas someday; when that day comes, it will be a great companion to this book, and I'll have Christmas gifts for all my fellow sysadmins.

One big part of the appeal of this book (and Lucas' writing in general) is that he is clear about the tradeoffs that come with picking one solution over another. He shows you where the sharp edges are, and leaves you well-placed to make the final decision yourself. Whether it's GBDE versus GELI for disk encryption, or what might bite you when enabling soft updates journaling, he makes sure you know what you're getting into. He makes recommendations, but always tells you their limits.

There's also Lucas' usual mastery of writing; well-written explanations with liberal dollops of geek humor that don't distract from the knowledge he's dropping. He's clear, he's thorough, and he's interesting — and that's an amazing thing to say about a book on filesystems.

Finally, the technical review was done by Poul Henning-Kamp; he's a FreeBSD developer who wrote huge parts of the GEOM and GBDE systems mentioned above. That gives me a lot of warm fuzzies about the accuracy of this book.

If you're a FreeBSD (or Linux, or Unix) sysadmin, then you need this book; it has a *lot* of hard-won knowledge, and will save your butt more than you'll be comfortable admitting.

You can purchase FreeBSD Mastery: Storage Essentials from amazon.com. Slashdot welcomes readers' book reviews (sci-fi included) -- to see your own review here, read the book review guidelines, then visit the submission page. If you'd like to see what books we have available from our review library please let us know.

Saint Aardvark writes If, like me, you administer FreeBSD systems, you know that (like Linux) there is an embarrassment of riches when it comes to filesystems. GEOM, UFS, soft updates, encryption, disklabels — there is a *lot* going on here. And if, like me, you're coming from the Linux world your experience won't be directly applicable, and you'll be scaling Mount Learning Curve. Even if you *are* familiar with the BSDs, there is a lot to take in. Where do you start? You start here, with Michael W. Lucas' latest book, FreeBSD Mastery: Storage Essentials. You've heard his name before; he's written Sudo Mastery (which I reviewed previously), along with books on PGP/GnuPGP, Cisco Routers and OpenBSD. This book clocks in at 204 pages of goodness, and it's an excellent introduction to managing storage on FreeBSD. From filesystem choice to partition layout to disk encryption, with sidelong glances at ZFS along the way, he does his usual excellent job of laying out the details you need to know without every veering into dry or boring. Keep reading for the rest of Saint Aardvark's review. FreeBSD Mastery: Storage Essentials author Michael W. Lucas pages 240 publisher Tilted Windmill Press rating 9/10 reviewer Saint Aardvark ISBN 0692343202 summary FreeBSD Mastery: Storage Essentials takes you on a deep dive into FreeBSD’s disk management systems. Do you need to know about GEOM? It's in here: Lucas takes your from "What *is* GEOM, anyway?" (answer: FreeBSD's system of layers for filesytem management) through "How do I set up RAID 10?" through "Here's how to configure things to solve that weird edge-case." Still trying to figure out GUID partitions? I sure was...and then I read Chapter Two. Do you remember disklabels fondly, and wonder whatever happened to them? They're still around, but mainly on embedded systems that still use MBR partitions — so grab this book if you need to deal with them.

The discussion of SMART disk monitoring is one of the best introductions to this subject I've ever read, and should serve *any* sysadmin well, no matter what OS they're dealing with; I plan on keeping it around for reference until we no longer use hard drives. RAID is covered, of course, but so are more complex setups — as well as UFS recovery and repair for when you run into trouble.

Disk encryption gets three chapters (!) full of details on the two methods in FreeBSD, GBDE and GELI. But just as important, Lucas outlines why disk encryption might *not* be the right choice: recovering data can be difficult or impossible, it might get you unwanted attention from adversaries, and it will *not* protect you against, say, an adversary who can put a keylogger on your laptop. If it still make sense to encrypt your hard drive, you'll have the knowledge you need to do the job right.

I said that this covers *almost* everything you need to know, and the big omission here is ZFS. It shows up, but only occasionally and mostly in contrast to other filesystem choices. For example, there's an excellent discussion of why you might want to use FreeBSD's plain UFS filesystem instead of all-singing, all-dancing ZFS. (Answer: modest CPU or RAM, or a need to do things in ways that don't fit in with ZFS, make UFS an excellent choice.) I would have loved to see ZFS covered here — but honestly, that would be a book of its own, and I look forward to seeing one from Lucas someday; when that day comes, it will be a great companion to this book, and I'll have Christmas gifts for all my fellow sysadmins.

One big part of the appeal of this book (and Lucas' writing in general) is that he is clear about the tradeoffs that come with picking one solution over another. He shows you where the sharp edges are, and leaves you well-placed to make the final decision yourself. Whether it's GBDE versus GELI for disk encryption, or what might bite you when enabling soft updates journaling, he makes sure you know what you're getting into. He makes recommendations, but always tells you their limits.

There's also Lucas' usual mastery of writing; well-written explanations with liberal dollops of geek humor that don't distract from the knowledge he's dropping. He's clear, he's thorough, and he's interesting — and that's an amazing thing to say about a book on filesystems.

Finally, the technical review was done by Poul Henning-Kamp; he's a FreeBSD developer who wrote huge parts of the GEOM and GBDE systems mentioned above. That gives me a lot of warm fuzzies about the accuracy of this book.

If you're a FreeBSD (or Linux, or Unix) sysadmin, then you need this book; it has a *lot* of hard-won knowledge, and will save your butt more than you'll be comfortable admitting.

You can purchase FreeBSD Mastery: Storage Essentials from amazon.com. Slashdot welcomes readers' book reviews (sci-fi included) -- to see your own review here, read the book review guidelines, then visit the submission page. If you'd like to see what books we have available from our review library please let us know.

samzenpus (5) writes "Alexander Stepanov is an award winning programmer who designed the C++ Standard Template Library. Daniel E. Rose is a programmer, research scientist, and is the Chief Scientist for Search at A9.com. In addition to working together, the duo have recently written a new book titled, From Mathematics to Generic Programming. Earlier this month you had a chance to ask the pair about their book, their work, or programming in general. Below you'll find the answers to those questions." Early Soviet Computing?
by eldavojohn

Alexander Stepanov, I have never had a chance to ask someone as qualified as you about this topic. I grew up on the opposite side of the Iron Curtain and have constantly wondered if (surely there must have been) alternative computing solutions developed in the USSR prior to Elbrus and SPARC. So my question is whether or not you know of any hardware or instruction set alternatives that died on the vine or were never mass fabricated in Soviet times? I don't expect to you to reveal some super advanced or future predicting instruction set but it has always disturbed me that these things aren't documented somewhere -- as you likely know failures can provide more fruit than successes. Failing that, could you offer us any tails of early computing that only seem to run in Russian circles?

If you can suggest references (preferably in English) I would be most appreciative. I know of only one book and it seems to be a singular point of view.

Alex: I'm not sure I have any unique knowledge, but can only describe my own experience. The first computer I used was a mainframe called M-20 (or one of its derivatives). My first programming exam was pass/fail, but I had to take it several times before I passed. I had no idea how to write code -- I didn't attend lectures or participate in labs, and thought I could just study the book and take the test. But programming isn't like that; the only way to learn is to do it.

Then in my first job, I participated in the design of a minicomputer called TA-100 used to control hydroelectric power stations. I was one of thekey designers of the realtime operating system, a contributor to the instruction set, and the lead designer of the programming tools (debugger, assembler, linker, etc.) -- all written in assembly language. The fact that I started at a very low level -- gates and instructions -- continues to be useful to my work even today. About that time, the Soviet Union started copying American designs, but I was very fortunate to be able to design something original from scratch. The head designer of the TA-100, Aleksandr Gurevich, was a great mentor to me. Two of my senior colleagues, Ilya Neistadt and Natalya Davydovskaya, also spent a lot of time trying to teach me all the things I didn't know.

Despite my personal experience (many details of which I've forgotten), I'm not actually an expert on the history of Soviet computing. But there is a good website containing many articles in English about early Soviet computers. One radically different approach was the "Setun" ternary computer. Unfortunately, there is no detailed treatment of Soviet-era computing at the level of detail and insight found in the second ("Computer Zoo") volume of Computer Architecture by Blaauw and Brooks, which provides an exhaustive treatment of Western designs. In general, computer history is an important field and requires great dedication. My friend Paul McJones does a fabulous job on history of programming languages and other software artifacts. See, for example, his history of FORTRAN site. (He also created sites for Lisp and ALGOL.) Sadly, there is no comparable effort on Soviet computing.



Successor to C++
by Anonymous Coward

I remember you wrote that STL has nothing to do with C++, it was a framework for generic programming and that C++ was chosen for its first implementation because it was less deficient for that purpose compared with other commercial programming languages. That implies you'd like to develop a programming language from scratch. Is that so? If so, how is it going?

Alex: In my first experiments in building a component architecture, I tried to design a language from scratch, called Tecton, with Deepak Kapur and Dave Musser. Tecton was my second system (i.e. it suffered from The Mythical-Man Month's "Second System Effect"). It was an extremely high level language indeed, and had concepts, but was unusable for anything practical. Then I implemented a version of the library in Scheme (together with Aaron Kerschenbaum and Dave Musser), and then another version in Ada (with Dave Musser). I was hired by Bell Labs to join their C++ library team in 1987, which was my first exposure to C++. My C and C++ mentor was Andy Koenig, who helped me understand the overall logic of the language. Unfortunately at that time, C++ was not ready for STL.

I returned to the library work in 1993 at HP Labs, together with Meng Lee. C++ had just gotten templates, and we were able to create a large generic library. At Andy Koenig's suggestion, we submitted a version of it for inclusion in the C++ language standard. This became STL.

After STL was accepted into the standard in 1994, I started thinking about designing a minimal programming language that will allow even more intimate access to hardware than C/C++ and also provide support for concepts and generic programming. I was hoping that somebody would fund such an activity. I interviewed with several companies, proposing such a design, but there was no interest. A senior VP at Microsoft told me: "We are not interested in innovating in the direction you suggest." They were "innovating" in the direction of C#, trying to displace Java. The situation now is not any better. There might be some interest eventually, but it will happen after my retirement: I am no longer in the game.



STL
by serviscope_minor

I'm a huge fan of the STL, and I think the design has stood the test of time amazingly well. That said, you now hae a bunch of hindsight. What would you do differently knowing what you know now. Also if you were doing it today and using today's languages, how do you think it would differ?

Alex: STL is the result of many compromises. There was a tension between my research goals for generic programming and getting something approved by the different constituents of the standards committee with diverse technical, business, and personal agendas. Such compromises are inevitable in real life.

Having said that, here are some of the things I would have preferred were different:

As we discuss in From Mathematics to Generic Programming, my original name for iterators was "coordinates" (or more specifically, "linear coordinates"). The standards committee people told me that there was already a name for this concept, "iterator," so I should use that term. They were wrong -- they were confusing my coordinates with heavyweight stateful iterators found in languages such as CLU and Alphard. This unfortunate terminology still often leads to misunderstanding about the concept of iterator in generic programming. Furthermore, as far back as 1987 I knew that linear coordinates (i.e. iterators) were only one kind of coordinate structures, data types that allow one to navigate through data structures. There are coordinate structures that deal with multidimensional arrays, trees, graphs, etc. (See, for example, chapters 7 and 8 of Elements of Programming.)

Also, there are many different types of containers and STL provided only a rudimentary classification. Moreover, containers with ownership semantics constitute only one way of dealing with data structures. There are others. A properly designed library would be based on a far larger set of data structures than what I could include into STL. There are also simple mistakes in algorithmic interfaces. Partition should place non-satisfying elements before satisfying elements. Copy_n should return a pair. I should have included algorithms dealing with integer concepts. I should have resisted the pressure to include allocators.

It would make perfect sense to redesign STL from scratch when they put concepts into C++. I would recommend that a person who decides to do it, should carefully study both Elements of Programming and From Mathematics to Generic Programming. Both of these books expand on these issues.



Re:STL
by Pseudonym

Related question: C++ was originally conceived as "C + Simula", but something that is interesting about the STL is how non-object-oriented it is, in particular using no inheritance. If we were designing a new "better C" today, one that you'd be happy to implement a STL-like system in, knowing what we know now, would we bother with Simula-style objects at all?

Alex: I am still convinced that Simula/C++/Java style inheritance is unsound. I do believe, however, that there is sometimes a need for run-time dispatch. But run time dispatch should be done as a run-time concept dispatch. Imagine, say, writing code in terms of a pointer to forward iterator. One should be able to obtain affiliated types at run time. Eventually languages will unify object-orientation and generic programming, but nobody seems to work on it now.

Dan: Bjarne Stroustrup describes C++ as a multi-paradigm language. The features that support object-oriented programming and the features that support generic programming are, for the most part, independent. That doesn't mean that both sets of features are not useful. Could Alex have designed STL for a language that doesn't have object-oriented features? Sure. But as a programmer, I'm happy that both sets of features are available. Just because object-oriented features are not needed to implement STL doesn't mean they provide no value in the language.

Alex: C++ has evolved over many years, and many of its features (inheritance, templates, exceptions, namespaces, etc.) were incorporated based on other work. As a result, they don't always work well together, and even when they do, it's in a baroque way. Now that we as a community have many years of experience with these features, we could design a minimal language from scratch that incorporates these features in a more concise and elegant way.



Hardware evolution
by jonkalb

The STL is about three decades old. In that time, we've seen both OS and hardware evolution. What is the impact of these changes on how the STL should be used? How would the STL be different if it where implemented targeting modern environments?

Alex: STL is "only" two decades old, but yes, there have been important changes during that period that would lead to some different decisions. STL was actually designed on a Leading Edge PC with no cache and 640K memory. (Our group at HP Labs didn't have enough money in the budget for an HP PC. When HP CEO Lew Platt came to visit me, HP Labs' director rushed in beforehand to hide the Leading Edge PC.)

One of the biggest changes since then has been the growth of caches. Cache misses are very costly, so locality of reference is much more important now. Node-based data structures, which have low locality of reference, make much less sense. If I were designing STL today, I would have a different set of containers. For example, an in-memory B*-tree is a far better choice than a red-black tree for implementing an associative container.

Another change is the increase in pipeline depth and support for unaligned reads. Today it is cheaper to read extra data rather than to have a branch.

Most processors today also support SIMD instructions. Libraries should take advantage of them whenever they can.

Modern applications such as search engines and databases also use lots of collections of very small data items that can be stored compactly without an extra level of indirection by using variable-sized encodings. It is essential that the libraries provide support for these variable-size entities. Dan and I, together with colleagues at A9, worked on this. Sadly enough, we were not able to finish our work, although you can see some relevant code snippets using variable-sized types and a new data structure called "tape" here.



Search seemingly getting worse over time
by TWX

This is more for Daniel Rose, but to what do you attribute the seeming decline in the quality of search results? I used Digital's Alta Vista search engine when it was fairly new and it seemed revolutionary and seemed to provide me with exactly what I wanted. Over time that declined and Alta Vista as it was ceased to be, and Google initially also seemed to provide me with exactly what I wanted. Now it seems like I have to put a whole lot of thought into faking Google into performing a somewhat-boolean-style search for me, and normal boolean expressions themselves no longer seem to work.

Is this the result of attempting to dumb-down the interface for tailored results, or something else or more insidious? Obviously the amount of content on the Internet is growing, but the computing power to process through all of it is growing too, so I would expect it wouldn't be getting this much worse, this quickly.

Dan: This is a huge question, which could be the subject of a whole book by itself. But the short answer is that there are several factors that have made the search experience be (or at least seem) worse. Here are a few:

1. Size of the problem. In the early days of AltaVista, there were around 100,000 web sites. Today there are around a billion. Assuming the number of web pages has grown proportionally to the number of sites, that's a factor of 10^4. Search ranking algorithms have actually been improved a lot -- they might even be 10x better than they were in 1995. But they haven't improved by 10^4x.

2. Complexity of the problem. Originally, web search engines dealt with static HTML pages. Now they are expected to work with many different types of documents in different formats, with users having a much wider variety of search goals. At A9, which provides the search engine for Amazon.com, we optimized the system specifically for product search. Web search engines have to work for all kinds of search.

3. Adversarial relationship between sites and engines. In the early days of web search engines, most web sites were purely informational, and many were run by nonprofit organizations like universities. Even when for-profit companies put up web sites, most were offered as an informational service to their customers -- it was a cost to the company, not a source of revenue. Obviously, all that has changed. Now it's in the interest of most web site providers to drive traffic to their sites. To do that they want to rank higher in search results -- often even for queries where their content is not relevant. So there is basically an arms race between search companies, which want to accurately rank results by relevance, and so-called search engine optimizers, who want their clients' pages to rank higher regardless of relevance. This leads to all kinds of spam.

4. Business model. The invention of search advertising by Overture, and its adoption by Google and others, meant that it was more profitable to show an ad than an organic search result. I know of specific instances where search engine companies chose not to deploy relevance improvements, because that would reduce revenue (more people would click on the results, and fewer on the ads). Even if a company tries to have a separation between their relevance and advertising teams, it is very hard to serve two masters.

Regarding the use of boolean expressions, there is evidence both from cognitive psychology and from information retrieval research that most people don't understand boolean logic, and that this misunderstanding leads to worse results. So I claim that Google's decision to stop interpreting certain words and symbols as boolean operators is good user-centered design, not "dumbing down" -- but I wish they still provided an advanced search option for those who want it.

If you're interested in learning more about search user issues in particular, here's a lecture I gave at UC Berkeley about 10 years ago on that topic.



Re:Search seemingly getting worse over time
by MouseTheLuckyDog

I was wondering something similar. Often times recent news tends to overshadow search results.

Let me give a practical example. Grand Jury. proceedings have undergone serious reform since the 70s. In some states a target can demand to appear before the Grand Jury. In some states a No Bill precludes the State from representing the case. In others there must be clear new evidence before a case can be represented. I know one state has a three strikes rules for GJ proceedings ( sorry don't remember which).

The day before the Michael Brown shooting, a search on Grand Jury Missouri would have found several articles on the specific laws to Grand Jury proceedings in Missouri. The day the DA announced he would present the case to a Grand Jury, the same search gets hundreds of articles on news story about Michael Brown and Grand Jury proceedings, but it becomes impossible to find those same scholarly articles about the peculiarity of Missouri Grand Jury proceedings. Not even the relevant statutes from the state website. What can be done to mitigate this effect?

Dan: This is a good illustration of what a complex problem search is. There are two issues here: First, should search results change in response to news events? I think so; in your example, it's almost certainly what the majority of users are looking for.

Second, how can the search engine make sure that *other* relevant results are also findable? One way is to make sure that the results address a diversity of user intents. When I was at AltaVista and Yahoo, we did some research on how to identify different user intents and how to make sure the results were not dominated by just one. The query "grand jury Missouri" has at least two obvious intents: "give me information about the grand jury system in Missouri" and "tell me what is going on with the particular grand jury investigating Michael Brown's death."

There are techniques that can do this diversification, and some search engines use some of them. But perhaps a better approach is to recognize that information-seeking is a process, not a magic oracle. Search engines should be designed to facilitate a kind of dialogue with the user. At AltaVista, we had a feature called "Prisma" that would show 12 related queries right below the search box -- not just queries that shared substrings with what the user has typed (like autocomplete), but queries that were about the range of different topics discussed in the actual pages. So for the query "grand jury Missouri," one suggestion might be "Michael Brown news" and another might be "grand jury statute Missouri".

My advice to intelligent search users is to to imagine what terminology would be used in a hypothetical good result on your intended topic, and use those words. If you want to find information about the legal basis of the grand jury system in Missouri, don't just type "grand jury Missouri," type "grand jury statute Missouri." When I do that query today on Google, I get a 2009 publication from the state of Missouri explaining the grand jury process, and the text of the actual statute, both on the first page of results.



What's your time like?
by mlheur

How much of your time do you dedicate to computing vs doing other things; what are your other hobbies or is the work you do also your play time?

Alex: Over the course of my life I have gradually narrowed my focus to spending time on the few items that, to me, are the essential examples of their category. These are things that stood the test of time; I re-read the books I already have read; I listen to music I have listened many times before; etc, etc. Yes, there is a chance that I will miss a new Mozart or Euclid, but it is a chance I am willing to take. Also, like the Pythagoreans of old, I view these as part of a unity: music reflects mathematics, literature is connected with history, etc. My work and my play and my life are inseparable. This unity is also reflected in From Mathematics to Generic Programming, which blends math, programming, history, and sometimes philosophy and art. Here are some of my favorites:

Literature: Greek and Roman classics: Homer, Plato, Ovid, Seneca; Bible; "modern" novels from Swift and Sterne to Dickens and Anthony Trollope. Math and science classics: Euclid, Euler, Gauss, Poincare. I still use printed books, not e-books.

Music: Bach, Mozart, Beethoven, Schubert, Wagner, and Mahler. I tend to listen to many different interpretations of the same piece. I do not use MP3s or streaming music, but CDs and, recently, SACDs.

Movies and TV: Chaplin, Marx Brothers, Kurosawa, Satyajit Ray, Kenneth Clark's Civilization, Peter Brook's Mahabharata, Brideshead Revisited, Royal Shakespeare Company production of Nicholas Nickelby, Maigret with Bruno Cremer. I am a blu-ray enthusiast. I do not use Netflix or Amazon Instant Video.

I love dogs, especially Welsh corgis; I spend 1-2 hours a day walking my dog Maxwell. I no longer eat meat or milk. I have been very happily married for 45 years; my wife Helen is my closest friend. We are practicing Roman Catholics, go to church on Sundays and holidays of obligation and try to keep the commandments. Our political views are in line with Pope Francis: we believe in having an economically just society.

Dan: Ironically, during much of my career as a researcher and engineering manager, I had fairly little time for programming. But now that I am not currently working full time, one of the things I've been doing for fun is programming -- learning iOS development and writing a musical iPhone app. I also enjoy playing very basic guitar and piano, reading, and lately, writing fiction. I try to alternate between reading nonfiction and fiction. The last books I read are The Swerve: How the World Became Modern by Stephen Greenblatt (about how the rediscovery of an ancient Roman poem helped spur the Renaissance) and Dave Eggers' novel The Circle (a cautionary tale about social networking and privacy, which should be required reading for everyone who works at Facebook, Google, and Apple).



Re:ack-nak
by blue trane

When will programming evolve to use subject-predicate syntax, rather than function-argument? Function-argument goes back (at least) to Frege, and his prejudices against subject-predicate syntax (which dominates natural languages). But isn't changePassword(a,b) more ambiguous than "change the password from a to b"? Don't we get an "information gain" effect from using a syntax we are familiar with outside of programming? When you first come to a function-argument command such as (in Oz, which is used in the Paradigms of Computer Programming MOOC) {Push S X}, there is maximum entropy as to whether S is pushed, or pushed onto. "Push X onto S" has no entropy; you know immediately, from the syntax alone, what is pushed onto what.

Dan: I think you need to decouple your argument about entropy with your argument about subject-predicate syntax. IIRC, stack-based languages like Forth and Postscript (and old HP scientific calculators) had completely unambiguous syntax. You either push something on the stack or perform an operation on the required number of arguments at the top of the stack. But these are not subject-predicate syntax languages. So there is more than one way to have what you call no-entropy syntax. Another way to avoid ambiguity is to require that argument names be part of the function name, as Smalltalk and Objective-C do. Then instead of your function call being changePassword(a, b), it's [foo changePasswordFrom:a to:b] (where foo is the object getting the message).

Separate from the entropy issue, is there a cognitive benefit from having programming languages use syntax familiar from natural languages? Perhaps, but which natural language's syntax will you use? Many languages (e.g. Japanese) use a subject-object-verb syntax, while English uses subject-verb-object. Romance languages use SOV some of the time (e.g. with pronouns) and SVO the rest of the time. Talk about ambiguous argument order!

Furthermore, natural languages have evolved to convey all kinds of nuances and deliberate ambiguities that make it hard to specify anything precisely. As a small example, the English meaning of "and" and "or" is quite different from their Boolean interpretation. (If the waiter says that breakfast comes with juice or coffee, getting both is not an option.)

The business application language COBOL (the most popular language of the 1970s) was supposed to have "English-like" syntax, with expressions like "add 1 to x." I'm skeptical that this syntax made programming any easier, but it did lead to this old joke: "Did you hear about the new version of COBOL? It's called ADD 1 TO COBOL."

My opinion is that we will always have different languages with different styles of syntax, to meet the needs of different communities of programmers.



Why is Generic Programming often second class?
by Anonymous Coward

We see many programming languages with at least some support for Generics, but usually as a second class citizen, and often added as an afterthought in later releases, and subordinate to some other programming paradigm. Java is primarily OO, with generics added later. C# is also primarily OO, though with generic support. It took C++ several iterations to get generics, and C++ is "multi paradigm". Go doesn't have generics, and doesn't seem like it will not a while.

It seems to me like generic programming is sufficiently powerful as a paradigm to not need other paradigms like OO in the same language. In fact, in many ways, OO, which ties together data and algorithms, seems antithetical to generic programming. So, do you see a possibility of a programming language whose primary paradigm is generic programming? Why do language designers not get generics into the first releases of their languages, even now, when the issues would seem to be well known? What would such a language look like?

Alex: To design a language for generic programming, one needs to learn to program generically. One has to write lots of code before things become clear. In the Appendix B of Elements of Programming, Sean Parent and Bjarne Stroustrup outlined a minimal language needed for programming. The appendix is about 8 pages long. To make it real, it probably needs to grow by a factor of 3. So, something like 25 pages should be sufficient. I am too old to do it, but I wish that someone would try.

A more difficult problem is not to design the language: C++, after all, contains most of the things needed. The problem is to teach programmers to think abstractly. And that is a very difficult task. I do not know a single university where one could even learn the preliminaries: understanding the machine, and understanding abstract mathematics. Our new book, From Mathematics to Generic Programming, is an attempt to sketch what is needed. Hopefully some school will try to teach both assembly level programming and abstract algebra.

An even harder problem is to convince the software industry to build software out of carefully designed components. What I see, however, is the movement in the opposite direction. Hand-crafted, one-off, undisciplined code is impossible to replicate. Adobe did a fabulous job specifying Postscript; that allowed Peter Deutsch to single-handedly produce Ghostscript. Now Adobe is not going to specify Photoshop's behavior. Let the Gimp guys try to replicate it. While Linus Torvalds was able to replicate Unix from the carefully written System V interface definitions, no one could replicate Windows: being nonstandard creates barriers to entry. There are grave economic reasons making any progress unlikely while undisciplined programmers generate huge amount of capital. It's analogous to the programmer whose terrible spaghetti code gives him job security, since no one else can understand it.

Dan: The idea that object-oriented programming and generic programming are competing paradigms is, in my opinion, mistaken. They are really orthogonal approaches. As we discuss in our book, generic programming is really an attitude. This attitude is useful whether you are using an object-oriented approach or not.

I would love to have a real-world, efficient, popular language that supports generic programming -- including concepts, in particular -- as first-class features. But I see no reason why this language shouldn't also support OOP.

MojoKid writes You have to hand it to Elon Musk, who has occasionally been referred to as a real life "Tony Stark." The man helped to co-found PayPal and Tesla Motors. Musk also helms SpaceX, which just recently made its fifth successful trip the International Space Station (ISS) to deliver supplies via the Dragon capsule. The secondary mission of the latest ISS launch resulted in the "successful failure" of the Falcon 9 rocket, which Musk described as a Rapid Unscheduled Disassembly (RUD) event. In addition to his Hyperloop transit side project, Musk is eyeing a space-based Internet network that would be comprised of hundred of micro satellites orbiting roughly 750 miles above Earth. The so-called "Space Internet" would provide faster data speeds than traditional communications satellites that have a geosynchronous orbit of roughly 22,000 miles. Musk hopes that the service will eventually grow to become "a giant global Internet service provider," reaching over three billion people who are currently either without Internet service or only have access to low-speed connections. And this wouldn't be a Musk venture without reaching for some overly ambitious goal. The satellite network would truly become a "Space Internet" platform, as it would form the basis for a direct communications link between Earth and Mars. It's the coming thing.

MojoKid writes You have to hand it to Elon Musk, who has occasionally been referred to as a real life "Tony Stark." The man helped to co-found PayPal and Tesla Motors. Musk also helms SpaceX, which just recently made its fifth successful trip the International Space Station (ISS) to deliver supplies via the Dragon capsule. The secondary mission of the latest ISS launch resulted in the "successful failure" of the Falcon 9 rocket, which Musk described as a Rapid Unscheduled Disassembly (RUD) event. In addition to his Hyperloop transit side project, Musk is eyeing a space-based Internet network that would be comprised of hundred of micro satellites orbiting roughly 750 miles above Earth. The so-called "Space Internet" would provide faster data speeds than traditional communications satellites that have a geosynchronous orbit of roughly 22,000 miles. Musk hopes that the service will eventually grow to become "a giant global Internet service provider," reaching over three billion people who are currently either without Internet service or only have access to low-speed connections. And this wouldn't be a Musk venture without reaching for some overly ambitious goal. The satellite network would truly become a "Space Internet" platform, as it would form the basis for a direct communications link between Earth and Mars. It's the coming thing.

theodp writes Some of the world's leading Data Scientists are on the payrolls of Microsoft, Google, Facebook, Yahoo, and Apple. So, it'd be interesting to get their take on the infographics the tech giants have passed off as diversity data disclosures. Microsoft, for example, reported its workforce is 29% female, which isn't great, but if one takes the trouble to run the numbers on a linked EEO-1 filing snippet (PDF), some things look even worse. For example, only 23.35% of its reported white U.S. employee workforce is female (Microsoft, like Google, footnotes that "Gender data are global, ethnicity data are US only"). And while Google and Facebook blame their companies' lack of diversity on the demographics of U.S. computer science grads, CS grad and nationality breakouts were not provided as part of their diversity disclosures. Also, the EEOC notes that EEO-1 numbers reflect "any individual on the payroll of an employer who is an employee for purposes of the employers withholding of Social Security taxes," further muddying the disclosures of companies relying on imported talent, like H-1B visa dependent Facebook. So, were the diversity disclosure mea culpas less about providing meaningful data for analysis, and more about deflecting criticism and convincing lawmakers there's a need for education and immigration legislation (aka Microsoft's National Talent Strategy) that's in tech's interest?

theodp writes Some of the world's leading Data Scientists are on the payrolls of Microsoft, Google, Facebook, Yahoo, and Apple. So, it'd be interesting to get their take on the infographics the tech giants have passed off as diversity data disclosures. Microsoft, for example, reported its workforce is 29% female, which isn't great, but if one takes the trouble to run the numbers on a linked EEO-1 filing snippet (PDF), some things look even worse. For example, only 23.35% of its reported white U.S. employee workforce is female (Microsoft, like Google, footnotes that "Gender data are global, ethnicity data are US only"). And while Google and Facebook blame their companies' lack of diversity on the demographics of U.S. computer science grads, CS grad and nationality breakouts were not provided as part of their diversity disclosures. Also, the EEOC notes that EEO-1 numbers reflect "any individual on the payroll of an employer who is an employee for purposes of the employers withholding of Social Security taxes," further muddying the disclosures of companies relying on imported talent, like H-1B visa dependent Facebook. So, were the diversity disclosure mea culpas less about providing meaningful data for analysis, and more about deflecting criticism and convincing lawmakers there's a need for education and immigration legislation (aka Microsoft's National Talent Strategy) that's in tech's interest?

gurps_npc writes: As most people know, the US has for quite some time let police seize pretty much anything they wanted to, forcing you to go to court to get back your stuff (at significant expense). Most of the problems came about because the Federal government let the local cops keep most of what they took.

Eric Holder, the U.S. Attorney General, has changed the rules of that program, making it more difficult for the police to do it under the federal program. They can still use local state programs, but that accounts for only about 57% of the cash taken. Holder did not end the program entirely — he left in some exceptions for things like explosives, weapons, and items related to child pornography, which all together amount to about 1% of the current federal program. Still, with this action he will have struck a serious blow to a despicable practice that serious newspapers and comedy TV shows decried as nothing more than legalized theft.

gurps_npc writes: As most people know, the US has for quite some time let police seize pretty much anything they wanted to, forcing you to go to court to get back your stuff (at significant expense). Most of the problems came about because the Federal government let the local cops keep most of what they took.

Eric Holder, the U.S. Attorney General, has changed the rules of that program, making it more difficult for the police to do it under the federal program. They can still use local state programs, but that accounts for only about 57% of the cash taken. Holder did not end the program entirely — he left in some exceptions for things like explosives, weapons, and items related to child pornography, which all together amount to about 1% of the current federal program. Still, with this action he will have struck a serious blow to a despicable practice that serious newspapers and comedy TV shows decried as nothing more than legalized theft.

We all love 'The Internet of Things.' Now imagine appliances, such as your refrigerator and hot water heater, getting radio messages from the power grid telling them when they should turn on and off to get the best electricity prices. Now kick that up to the electric company level, and give them a radio network that tells them which electric provider to get electricity from at what time to get the best (wholesale) price. This is what e-Radio is doing. They make this claim: "Using pre-existing and near ubiquitous radio signals can save billions of dollars, reduce environmental impact, add remote addressability and reap additional significant societal benefits."

Timothy noticed these people at CES. They were one of the least flashy and least "consumer-y" exhibitors. But saving electricity by using it efficiently, while not glamorous, is at least as important as a $6000 Android phone. Note that the guy e-Radio had at CES speaking to Timothy was Scott Cuthbertson, their Chief Financial Officer. It's a technology-driven company, from Founder and CEO Jackson Wang on down, but in the end, saving money is what they sell. (Alternate Video Link)

An anonymous reader writes: Last week, SpaceX attempted to land a Falcon 9 rocket on an autonomous ocean platform after successfully launching supplies to the ISS. It didn't work, but Elon Musk said they were close. Now, an amazing video has been recovered from an onboard camera, and it shows just how close it was. You can see the rocket hitting the platform while descending at an angle, then breaking up. Musk said a few days ago that not only do they know what the problem was, but they've already solved it. The rocket's guiding fins require hydraulic fluid to operate. They had enough fluid to operate for 4 minutes, but ran out just prior to landing. Their next launch already carries 50% more hydraulic fluid, so it shouldn't be an issue next time.

An anonymous reader writes: Just days after Google angered Microsoft by releasing information about a Windows security flaw, they've now released two more. "The more serious of the two allows an attacker to impersonate an authorized user, and then decrypt or encrypt data on a Windows 7 or Windows 8.1 device. Google reported that bug to Microsoft on Oct. 17, 2014, and made some background information and a proof-of-concept exploit public on Thursday. Project Zero is composed of several Google security engineers who investigate not only the company's own software, but that of other vendors as well. After reporting a flaw, Project Zero starts a 90-day clock, then automatically publicly posts details and sample attack code if the bug has not been patched." Microsoft says there's no evidence these flaws have been successfully exploited.

An anonymous reader writes that Elon Musk wants to speed up the development of his proposed 800-mph tube transport. "Billionaire and entrepreneur Elon Musk is getting more hands-on with the Hyperloop. Musk, who heads up both space transportation outfit SpaceX and electric-vehicle maker Tesla Motors, casually announced via Twitter on Thursday that he's decided to help accelerate development of his vision for near-supersonic tube transportation, first outlined in August 2013. Musk said he will build a five-mile test track for the still-theoretical system for students and companies to use. A possible location would be Texas, he added, where presumably there is plenty of flat land to go around."

malachiorion writes If you're into robots, AI, you've probably read about the open letter on AI safety. But do you realize how blatantly the media is misinterpreting its purpose, and its message? I spoke to the organization that released letter, and to one of the AI researchers who contributed to it. As is often the case with AI, tech reporters are getting this one wrong on purpose. Here's my analysis for Popular Science. Or, for the TL;DR crowd: "Forget about the risk that machines pose to us in the decades ahead. The more pertinent question, in 2015, is whether anyone is going to protect mankind from its willfully ignorant journalists."

itwbennett writes The story began a few months ago when it was reported that both Verizon and AT&T were injecting unique identifiers in the Web requests of their mobile customers. AT&T has since stopped using the system, but Verizon continues. Now, Stanford computer scientist Jonathan Mayer has found that one advertising company called Turn, which tracks users across the Web when they visit major sites including Facebook, Twitter, Yahoo, BlueKai, AppNexus, Walmart and WebMD, uses the Verizon UIDH to respawn its own tracking cookies.

itwbennett writes The story began a few months ago when it was reported that both Verizon and AT&T were injecting unique identifiers in the Web requests of their mobile customers. AT&T has since stopped using the system, but Verizon continues. Now, Stanford computer scientist Jonathan Mayer has found that one advertising company called Turn, which tracks users across the Web when they visit major sites including Facebook, Twitter, Yahoo, BlueKai, AppNexus, Walmart and WebMD, uses the Verizon UIDH to respawn its own tracking cookies.

Bennett Haselton writes: They would never admit it, but your high school admins would probably breathe a sigh of relief if all of their sexting-mad students would go ahead and install Snapchat so that evidence of (sometimes) illegal sexting would disappear into the ether. They can't recommend that you do this, because it would sound like an implicit endorsement, just like they can't recommend designated drivers for teen drinking parties -- but it's a good bet they would be grateful. Read on for the rest.

Five teenagers at Warren Township High School in Gurnee, Illinois were arrested in November in conjunction with a girl's topless photo being distributed throughout the school. Last Thursday, in Rochester Hills, Michigan, a prosecutor announced that contemplating filing child pornography charges against "dozens" of students for distributing explicit pictures to other students at Rochester Adams High School. In Portland, Oregon, police are investigating a group of Grant High School students for making videos of each other having sex at the school and off campus. (And, of course, these are just the incidents that police found out about.) Naturally, schools everywhere have been falling over themselves to institute strict anti-cyber-bullying and anti-sexting policies (not to mention that sending and forwarding sexually explicit pictures of children under 18 is a federal crime as well).

Schools have rules for reasons that are a mixture of cynical protection against lawsuits and sincere concern for the students. When education system teach students not to smoke cigarettes, they're presumably doing that out of genuine concern for students' welfare, since it would be hard to sue the school for not teaching about the dangers of smoking. When a school installs a railing by the side of a walkway to keep students safe from passing cars, they're probably motivated by a mixture of concern over being sued, and legitimate concern for students' safety. When the school installs software on their computers to block Facebook and Reddit (even outside of class time, when computers are sitting idle and students have nothing else to do), they're probably motivated entirely by liability concerns - because they know virtually all of those students can get on those websites at home, so they're not affecting the students' long-term welfare by keeping them off of those websites, but they just don't want to be liable for anything if the students access those sites at school.

In the case of anti-sexting policies, I'm not cynical enough to think that schools are motivated entirely by liability concerns. There are actual risks to sexting pictures of yourself, even if you're never charged with violating child pornography laws: the embarrassment of your picture being forwarded around the school, or ending up in the archive of a porn site. On the other hand, worse things happen to dozens of high school students every month, but only a handful of schools get dragged into the national spotlight as a result of a child porn investigation. So let's call it about 25% due to legitimate concern for students and 75% due to liability reasons and concern for adverse publicity.

But sexting students could vastly reduce schools' concerns about both issues, by sending pictures using an app like Snapchat, which automatically deletes photos after the recipient has viewed them -- in order to greatly reduce the chance of a picture being saved or forwarded after it's sent. Please note, I'm not saying the photos can't be saved anyway, or recovered by computer forensics. And take heed: I'm not saying you should do it either way! But if you greatly reduce the chances of an image being saved, you greatly reduce the chances of it leading to a scandal that engulfs the school, or leads to a federal child pornography charge.

Of course there are cases where teens were arrested for sending child pornography through Snapchat as well. But these high-profile stories don't address the relevant question, which is: Are you less likely to get arrested (or expelled, or humiliated) for sending these pictures if you do it through Snapchat, even if the likelihood doesn't drop to zero? Obviously, yes.

Now even someone with no phone-hacking knowledge can figure out that if they receive an image over Snapchat, they can "save" it by taking a photo of their screen with another phone or camera, and the sender won't know. (You can also take a normal screen shot with the phone, but that will notify the sender that you took a screen shot, unless you download a third-party app or try some other hack which may or may not even work by the time you read this.) However, this assumes that the trust relationship between the sender and the recipient is already broken at the time the message is being sent, if the recipient is saving the message without the knowledge or consent of the sender. Some of these sexts are presumably being sent in the context of a relationship in which some (sweet, naive, misguided) trust still exists, so that if the sender sends the message and the recipient doesn't use some sneaky workaround, the picture will get deleted on schedule. If trust only falls apart later, then the recipient won't have a copy of the image any more if it was sent by Snapchat, but they will if it was sent via text.

Actually, it may be possible for the recipient to recover a snapchat image after their smartphone Snapchat app has supposedly "deleted" it -- a company called Digital Forensics offers Snapchat image recovery as a service, but they charge $300-$500 per incident, and even they haven't figured out how to do it on an iPhone yet.

So, in terms of boolean logic, if you send an explicit photo via Snapchat, it might end up being saved permanently and forwarded if:
(
the recipient is already being dishonest with you (saving pics without your permission) at the time that you send the picture
AND
the recipient is smart enough to figure out how to save Snapchat pictures without notifying you -- not that hard, but eliminates some people
)
OR
(
you later go through a nasty breakup with the recipient and they're determined to humiliate you or get you in trouble with the law
AND
they don't mind the fact that they could also get in trouble with the law, for saving or forwarding the picture
AND
they're willing to spend $300 to recover the image
AND
they don't have an iPhone
)

Whereas if you send a photo via regular text, all it takes to get in trouble is either (a) the recipient going through a nasty breakup with you, that puts them in a vindictive frame of mind, while they still have a copy on their phone, or (b) the recipient's family member snooping through their messages.

Your high school would never tell you so out loud, but between Snapchat and texting, you can guess which they would prefer you to use.

Of course, this advice wouldn't have done much good for the Portland students who made and distributed their own sex videos, since creating the illegal permanent recording was their entire goal. Snapchat can help protect people from mild levels of stupid, but it's a barrier you can overcome if you aim high and truly believe in yourself.

Got something to say about privacy, technology, or other topics of interest? Long-form submissions are welcome.

An anonymous reader writes I'm in the camp that doesn't trust systemd. You can discuss the technical merits of all init solutions all you want, but if I wanted to run Windows NT I'd run Windows NT, not Linux. So I've decided to migrate my homebrew router/firewall/samba server to one of the BSDs. Question one is: which BSD? Question two: where's some good documentation regarding setting up a home router/firewall on your favorite BSD?
It's fine if the documentation is highly technical, I've written linux kernel drivers before :) (Got a question? You can Ask Slashdot, too.)

gurps_npc writes "Marriot Hotels had been illegally blocking Wifi hotspots in Nashville. They thought they owned the airwaves inside their hotel and wanted to charge guests for using them. They claimed to be 'surprised' they were breaking the law. Other hotels have complained to the FCC, asking for permission to do it legally. The FCC had fined Marriot $600,000 for their actions, among other things. They have stopped their illegal blockage, in part because of public backlash and in part because the government told them they were criminals.

gurps_npc writes "Marriot Hotels had been illegally blocking Wifi hotspots in Nashville. They thought they owned the airwaves inside their hotel and wanted to charge guests for using them. They claimed to be 'surprised' they were breaking the law. Other hotels have complained to the FCC, asking for permission to do it legally. The FCC had fined Marriot $600,000 for their actions, among other things. They have stopped their illegal blockage, in part because of public backlash and in part because the government told them they were criminals.

An anonymous reader writes "Facebook unveiled its rumored "at Work" service to a handful of partners today. Facebook at Work puts co-workers into a standalone social network and allows them to share posts and images appropriate for the workplace but looks and acts just like regular Facebook. "We have found that using Facebook as a work tool makes our work day more efficient," Lars Rasmussen, Facebook's director of engineering, tells WIRED. "You can get more stuff done with Facebook than any other tool that we know of, and we'd like to make that available to the whole world.""

HughPickens.com writes: Reuters reports that Elon Musk, speaking at an industry conference in Detroit, said Tesla may not be profitable until 2020 but that Tesla plans to boost production of electric cars to "at least a few million a year" by 2025. Musk told attendees at the Automotive News World Congress that "we could make money now if we weren't investing" in new technology and vehicles such as the Model 3 and expanded retail networks.

Musk does not see the Chevrolet Bolt as a potential competitor to the Model 3. "It's not going to affect us if someone builds a few hundred thousand vehicles," said Musk. "I'd be pleased to see other manufacturers make electric cars." On another topic, Musk said he was open to partnerships with retailers to sell Tesla vehicles, but not until after the company no longer has production bottlenecks. "Before considering taking on franchised dealers, we also have to establish (more of) our own stores," said Musk adding that "we will consider" franchising "if we find the right partner." Musk did not elaborate, but said Tesla "is not actively seeking any partnerships" with other manufacturers "because our focus is so heavily on improving our production" in Fremont. Last year, Tesla delivered about 33,000 Model S sedans and said the current wait for delivery is one to four months. Tesla has already presold every Model S that it plans to build in 2015. "If you ordered a car today, you wouldn't get it until 2016."

mpicpp points out a report that Apple has been awarded a broad patent for gesture control of a computer interface (8,933,876). The company inherited the patent after their acquisition of motion-sensor company PrimeSense in 2013. (PrimeSense's technology is used in Microsoft's Kinect gesture control system.) Here's the patent's abstract: A method, including receiving, by a computer executing a non-tactile three dimensional (3D) user interface, a set of multiple 3D coordinates representing a gesture by a hand positioned within a field of view of a sensing device coupled to the computer, the gesture including a first motion in a first direction along a selected axis in space, followed by a second motion in a second direction, opposite to the first direction, along the selected axis. Upon detecting completion of the gesture, the non-tactile 3D user interface is transitioned from a first state to a second state.