Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Comment Re:Contributory infringement (Score 1) 96

Napster was shutdown by a court in the country in which it operated.

Which also happens to be the country in which Slashdot operates.

Likewise just because one judge in the UK made one decision doesn't make the software illegal in any other parts of the world.

Yet.

Both the USA and Great Britain agree about the illegality of a copying service with no substantial non-infringing use. What makes you think courts in other countries that have signed the same copyright treaty won't reach the same conclusion when the MPA (the MPAA's foreign division) goes into those countries?

Comment Daikatana for GBC (Score 1) 104

The Game Boy Color version of Daikatana actually didn't suck. So perhaps what they needed to do was repackage the GBC game and wrap it up in one of those newfangled hi-res emulators that replaces each of the game's 8x8 pixel tiles with a redrawn high-res 32x32 pixel tile. (See "HiSMS".) This would blow the game up to a 640x576 window.

Comment People have been talking about this for years. (Score 4, Interesting) 434

The Android fragmentation boogeyman.

What nobody's ever explained to my satisfaction is why I should give a flying f*ck. As far as I can see "fragmentation" is simply the result of users and developers not all being forced to upgrade to the latest and greatest when the platform vendor demands it. This is actually a *good* thing.

It means I can find a $40 Android tablet running KitKat, which is perfectly fine for things I want to use a $40 tablet for. I'm out of the developer business now, but I still dabble to keep up with developments, and far as I can see the Google tools do a really nice job of allowing developers to target a range of platforms and still look up to date on the latest and greatest. So I don't have to shut out people who bought a smartphone last year if I want to use Material Design (which is cartoony for my taste but does a nice job setting out consistent UI guidelines).

If this is fragmentation hell, all I can say is come on in, the the lava is fine. Sure it would be *nice* if the adoption rate for the latest and greatest was higher, but as a long time user and developer I have to say that not being pushed over the upgrade cliff on the platform vendor's orders is nice too.

Comment Re:I cut my teeth on the ARPANET. (Score 1) 553

Go really retro and have token ring and round robin instead of ethernet....

No, that's for after I've sold them all ThickNet. Then I'll have them bying STP-A cable by the spool to run to the MAO. Maybe I'll package a whole concentrator rack inside a vintage Frigidaire unit so that anytime anyone wants a Pabst they'll see you're more retro than thou.

Comment Accessing the data being deserialized (Score 1) 230

If you had a hard requirement such as "has to be ASCII-based" or "char must be 8 bits wide", then I'd wonder where it comes from.

The fact that Internet protocols use 8-bit bytes and either ASCII or its superset UTF-8.

For requiring char to be of some specific width, there's hardly a reason, unless you're improperly (de)serializing.

Last time I checked, the C standard offered no facility for networking, graphics, or even enumeration of the files in a directory. This means most nontrivial interactive programs will need to use POSIX or Windows functions, which are defined in the POSIX and Win32 specifications but are undefined behavior from the perspective of the C standard, in order to access the data that the program is (de)serializing in the first place. Or is there a portable way to do this that I'm somehow missing?

Comment Quick summary of the papers involved here. (Score 5, Informative) 328

The summary conflates two papers, a review paper in Science which summarizes the state of knowledge about fracking the Marcellus Shale (Vidic et al. 2013), and a study of an individual incident published this month in PNAS in which researcher purport to have found a single instance of minor contamination from a fracking well (Llewellyn et al. 2015). Neither paper is particularly damning or inflammatory, so at first blush it's not immediately obvious why the fracking PR flacks have gone to DEFCON 3 on this. The key is to read the review paper first. This is almost always the best way to start because review papers are supposed to give a full and balanced overview of the current state of scientific knowledge on a topic. TL;DR, I know, but stick with me for a few paragraphs and I think I can make the problem clear.

Vidic paints a rather favorable picture of the fracking industry's response to problems that have arisen during the fracking boom in the Marcellus shale. It absolves them of any responsibility for the infamous "burning tapwater" we've all seen in Youtube videos. It states they have been quick to respond to wastewater leaks and well blowouts before contamination could spread. It says the industry has redesigned wells in response to concerns that they might leak fracking water as they pass through the aquifer. And it says that fracking water that returns to the surface ("flowback") is treated and re-used for more fracking -- an expensive environmental "best practice".

Vidic does raise some important concerns, however, and the most important is this. At present recycling flowback into more fracking water is practical because production is booming. But at some point production will level off and begin to decline, and when that happens the industry will be producing more flowback than it can use economically. In Texas, where fracking was pioneered, flowback was disposed of in deep wells -- a process not without its drawbacks, but better than leaving the contaminated water on the surface. Pennsylvania doesn't have enough disposal capacity to handle today's flowback, which helps make recycling fracking water attractive at the present time.

We now have enough context to understand Llewellyn, and why Llewellyn is so upsetting to the industry. Llewellyn's paper documents a single instance of minor contamination which matched the chemical fingerprint of flowback from a nearby well. This contamination was well below a level that would be cause for any concern. Llewellyn concludes the most likely cause was a small spill from the flowback holding pit, although it can't rule out the possibility that the contamination occurred inside the well. Taken with the picture Vidic paints of an industry that is generally on top of stuff like this, the occurrence of a single mishap with negligible consequences is hardly damning. So why has the fracking industry unleashed its flying PR monkeys on this?

Because the fracking industry apparently has made no plans for when the day comes it can no longer recycle all the flowback it uses, and it doesn't want the public to think about that.

It would be sensible for them to prepare for the flowback problem now on the upswing of the boom, for the same reason the industry has been able to be so responsive to date: these are good times for the industry in the Marcellus Shale. They're flush. Although preparing for the problem now would be expensive, it wouldn't slow the boom appreciably, and it would add jobs. But... if the industry can kick the flowback can far enough down the road, we'll have to ask it to fix the problem while production and probably the regional economy is in decline. Doing something about the problem then will cost jobs and require money nobody will have.

  So if the industry isn't forced to do something about the looming problem soon, it will become politically if not financially impossible to make them do that ever. That's why the industry is allergic to the very mention that surface contamination from flowback is even possible. In the scheme of things the Llwewllyn incident is negligible, but when fracking starts producing more waste than the industry can use surface contamination is going to become a lot more common and a lot worse.

Vidic raises some other serious long term concerns. Nobody knows where most of the fracking water used goes. The geology of the area is complex enough, but it is further complicated by many old gas and oil wells, quite a few of which are not fully documented. Contamination of the aquifer is a quite plausible possibility that needs further scientific study -- study that has been hindered by lack of research funding and industry transparency. More research might lay this concern to bed; or it may require changes in the industry's operation. We don't know. But we do know that some day we'll have a wastewater problem, and if we wait to address that it will be politically impossible to do anything about.

CITATIONS

Vidic, R. D., et al. "Impact of shale gas development on regional water quality." Science 340.6134 (2013): 1235009.

Garth T. Llewellyn, Frank Dorman, J. L. Westland, D. Yoxtheimer, Paul Grieve, Todd Sowers, E. Humston-Fulmer, and Susan L. Brantley. "Evaluating a groundwater supply contamination incident attributed to Marcellus Shale gas development." PNAS 2015 ; published ahead of print May 4, 2015,

Comment Asserting implementation-defined behavior (Score 1) 230

You're not making it better by actively promoting horrible, non-portable, implementation-dependent and error-prone coding practices.

What's wrong with making assumptions about implementation-defined behaviors and using static assertions to verify them? For example, would it be poor form to assume (and assert) things like 8-bit bytes or that the character set is ASCII, and if so, why?

extern char assert_8bitbytes[(
    CHAR_BIT == 8 && sizeof(uint32_t) == 4
) ? 1 : -1];
extern char assert_ascii[(
    'A' == 0x41 && 's' == 0x73
) ? 1 : -1];

This way, the compiler will fail and kick out a diagnostic if the environment doesn't match the assumptions.

Comment Contributory infringement (Score 1) 96

you're not infringing copyright by creating Popcorn Time.

You're only infringing once you USE it, unless a court deems otherwise, and so far only one court in one jurisdiction has.

I'd be interested to see where you get the idea that "one court in one jurisdiction" recognizes the legal theory of contributory infringement. Napster, Aimster, Grokster...

Comment Re:Underestimate. (Score 2) 51

37% of wives and girlfriends are likely to cheat on you too. But what you gonna do about it? Dump your cheating girlfriend and just end up with another cheating girlfriend? What's the point of that? So most people just stay with their lousy operating system or girlfriend. Really it is all pointless anyway.

Er... presuming that the cheating is important to you, you have a 100% chance of having a cheating girlfriend if you stay with the current one but only a 37% chance if you switch to a new, randomly chosen girlfriend.

But... if you don't instinctively see that, then I have to conclude that on some level you want abuse from your girlfriend/software vendor. In fact given your track record of past choices it seems likely that your choice will perform worse than chance, although a probably bad new choice remains a better strategy than staying with the devil you know.

If you don't have the confidence in your discretion to improve upon chance, a randomly chosen girlfriend/OS is a reasonable next step. You should try *anything* that meets the obvious superficial criteria (e.g., is biologically female, has companies providing professional support services). In fact studies suggest that while attractiveness makes a huge difference in who people ask out on a date, it has no effect on their satisfaction with that date once it takes place. What we think we want and what will make us happy are often two different things.

Slashdot Top Deals

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?

Working...