Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
User Journal

Journal Journal: a return which is long overdue (plus achievements!) 17

I've lurked at /. without posting for ages, mostly because I just don't have the time to interact like I used to.

But I've been clicking through the old RSS feed more and more lately, and when I saw the PAX Plague thread today, I came over to comment, since I'm kind of affected by the whole damn thing. I thought I'd take a look around since I haven't been here in awhile, and I saw that there are freaking ACHIEVEMENTS associated with our accounts. It's silly, and I'm sure it's been here forever, but I thought it was awesome and I was delighted when I read it.

I didn't realize how much I missed Slashdot until I spent some time here today, and I bet that anyone who joined in the last 2 years doesn't even give a shit about my stupid comments or anything, but it felt good to come back here, and feel safely among my people again.

User Journal

Journal Journal: Nintendo Announces DSi and Wii storage solution

Earlier this morning, Nintendo made several major announcements in a press conference in Japan. Ranging from a new Nintendo DS to a Wii storage solution. Nintendo's first announcement was a brand-new handheld in the Nintendo DS line of consoles. This revision of the DS brand will be a significant break from the previous DS Lite console. It will be named "Nintendo DSi". (Nintendo DS-Eye, get it?) Nintendo also announced a solution to the Wii storage problem. Unfortunately, it sounds like players will be able to download to their SD Card, but not actually play games directly from the card.

Firehose Link: http://slashdot.org/firehose.pl?op=view&id=1225579

(Still trying to figure out if the firehose does anything.)

User Journal

Journal Journal: Announcing the release of my new book 22

This feels like a mega-spam entry, and I'm very self conscious about posting it, but I'm excited about this and I wanted to share . . .

I just published my third book, The Happiest Days of Our Lives. I mention it here because it's all about growing up in the 70s, and coming of age in the 80s as part of the D&D/BBS/video game/Star Wars figures generation, and I think a lot of Slashdot readers will relate to the stories in it.

I published a few of the stories on my blog, including Blue Light Special. It's about the greatest challenge a ten year-old could face in 1982: save his allowance, or buy Star Wars figures?

After our corduroy pants and collared shirts and Trapper Keepers and economy packs of pencils and wide-ruled paper were piled up in our cart, our mom took our three year-old sister with her to the make-up department to get shampoo and whatever moms buy in the make-up department, and my brother and I were allowed to go to the toy department.

"Can I spend my allowance?" I said.

"If that's what you want to do," my mom said, another entry in a long string of unsuccessful passive/aggressive attempts to encourage me to save my money for . . . things you save money for, I guess. It was a concept that was entirely alien to me at nine years old.

"Keep an eye on Jeremy," she said.

"Okay," I said. As long as Jeremy stood right at my side and didn't bother me while I shopped, and as long as he didn't want to look at anything of his own, it wouldn't be a problem.

I held my brother's hand as we tried to walk, but ended up running, across the store, past a flashing blue light special, to the toy department. Once there, we wove our way past the bicycles and board games until we got to the best aisle in the world: the one with the Star Wars figures.

I'm really proud of this book, and the initial feedback on it has been overwhelmingly positive. I've been reluctant to mention it here, because of the spam issue, but I honestly do think my stories will appeal to Slashdotters.

After the disaster with O'Reilly on Just A Geek, I've decided to try this one entirely on my own, so I'm responsible for the publicity, the marketing, the shipping, and . . . well, everything. If this one fails, it will be because of me, not because a marketing department insisted on marketing it as something it's not.

Of course, I hope I can claim the same responsibility if (when?) it finds its audience . . . which would be awesome.

User Journal

Journal Journal: WiiCade Open Sources Flash API

Slashdot doesn't seem to get much news about Wii Homebrewing, so I thought I'd throw out an article on the latest updates to the popular Wii Web Gaming site WiiCade.

According to GoNintendo, they have released a new version of their Wii Remote API under a combination of the GPL and LGPL licenses. To sweeten the pot, this new version offers cool new features like IR-Based Motion Sensing, 4 player support, control over zooming, and partial Nunchuk support.

To celebrate, WiiCade released 5 new games that use these features. These games are Icy's Droplet Gathering Adventure, Space Shooting Mania, Asteroid Falldown, Bumper Car Madness, and Catch a Falling Star. It looks like someone has already released another game called WiiCade Snake. And for you Bush lovers/haters out there, they also have a Make Your Own Bush Speech "game". If you're into that sort of amusement, that is.

I personally recommend Bumper Car Madness. It's a rather crazy and fun arcade game that has you competing to see who can get the most tokens. It offers three control schemes, two which allow you to steer by twisting the remote, one which follows the cursor. It's tons of fun, especially with friends.

It looks like they also got a new look to go with the upgrade. Decide for yourselves if it's better or not. I like it, though. :-)

User Journal

Journal Journal: Interesting Misconception 4

Today's lesson on taking things out of context. Here's a post I made today:

How is Science any different from groupthink? Scientists are no where near as impartial as they claim to be. The only checks and balances in place are reviews by scientific peers!

Think about it.

Shocked yet? Frightened at how I could possibly say such a thing? Clamoring for the mods to continue my fall to oblivion? I even got this response from an AC:

You're usually more level headed than this. I think you're just being silly.

Interesting thing, though. No one read the context. Here's the post I was replying to:

How are they different from groupthink? or the political bias at times that persists in Wikipedia?

Their top level admins are no where near as impartial as they claim to be. Obvious subjects to avoid on Wikipedia are those which are based on religious, political, or environmental, concerns. People have taken "maintaining" those types of entries to ridiculous levels that whole pages of discussion exist behind the page where the various factions bitch at each other. The best way to see the bias is to watch what they require to have accredited links and what they do not, let alone what sites they consider credible sources for disputed information.

While it has much useful information there are just certain subjects to avoid

Now let's re-read my text in context:

How are they different from groupthink? or the political bias at times that persists in Wikipedia?

Their top level admins are no where near as impartial as they claim to be.

How is Science any different from groupthink? Scientists are no where near as impartial as they claim to be. The only checks and balances in place are reviews by scientific peers!

See it? Still want my head on a platter?

An interesting experience.

Editorial

Journal Journal: iPhone: Why So Negative? 4

I just got back from reading the Chicago Tribune's various stories on the iPhone. The reviews were very positive, if not a bit reserved. Sales may have topped 500,000 units. And sales have been so good that the AT&T activation servers have been overloaded. All in all, a very good launch for the iPhone. Not perfect mind you, but nothing ever is.

So imagine my surprise when I checked Slashdot this morning to find that the only story on the launch is Activation Problems in iPhone Paradise. No mention of the 500,000 unit estimate. Nor is there mention of the strongly positive reaction by the market. The only thing discussed is the activation problems, which are blown incredibly out of proportion. From the "long-wait-short-celebration" department tag, to a link to an engadget poll that won't let you see the results unless you vote (There's no "I don't have an iPhone option?" WTH?), all the way to using a random blog of one guy's experience as the basis for what all ~500,000 users (estimated) are experiencing.

Maybe it's just me, but this has gone way too far.

Slashdot is a place where intelligent people tend to hang out to converse. Because these people know a lot, they easily become jaded. I know that I personally have struggled a great deal with becoming unintentionally negative. And it's not necessarily the problem of dealing with people who know less. That's a reasonable excuse for tech support reps, but it doesn't hold up for professionals. In fact, I often find that I can become so indoctrinated in a certain way of thinking (because I know quite a bit about it) that anything that seems to violate that doctrine must be wrong.

Of course, this is a very dangerous trap. There are always clever ways around problems without violating the laws of physics. In fact, the solution presented often solves the problem in a very unique way that requires a dramatic shift in thinking.

For example, hydrogen cars are often criticized for requiring grid power to generate the hydrogen. Thus many discount the option because it "doesn't provide an alternative fuel source". Which is true, but it misses the point. Hydrogen provides a shift in the way that our infrastructure works. Rather than having millions of inefficient, dirty, smog-inducing, portable combustion engines on the road, we could generate all the power from relatively clean and efficient sources like Nuclear power plants then distribute that power to a "vehicle grid" using hydrogen as the storage and transmission device. From that perspective, hydrogen suddenly becomes a lot more appealing. (Without diving into the logistics issues of converting fueling stations, of course.)

Thus I can't help but wonder, is Slashdot getting too negative for its own good? I've been noticing a sharp increase in stories that are either overblown or outright inaccurate. From PopCap Distressed Over 'CopyCat' Games (the original interview states that PopCap is distinctly unaffected by clones), to W3C Bars Public From Public Conference (the newsie apparently couldn't understand English), to Judge Orders TorrentSpy to Turn Over RAM (Judge ordered web logging to be turned on), I'm beginning to wonder if the general status of the Slashdot users and editors isn't taking a turn for the worse. I'm seeing fewer and fewer stories with a positive slant. Those that do have a positive slant are either overblown claims (which results in a negative reaction) or misreported claims (which results in the same negative reaction, except that all of Slashdot is barking up the wrong tree).

While I understand that much of the confusion and negativity is pouring out of the press, it's important to keep a cool head on our shoulders and think critically about every piece of information we see. While I don't directly blame the Slashdot editors or the readers, I do think that all of us can make a contribution toward positive reenforcement on Slashdot. We readers can do two things:

1. Try to make sure that the stories we submit are correctly stated and reflect the true issue at hand.

2. Keep our replies civil. It's so easy for all of us (myself included) to get mad at the other guy thinking he doesn't know what he's talking about. Yet sometimes he actually does. So please be gentle when correcting each other. You'd be amazed at the smart people you'll develop a rapport with!

For the editors, I can offer one major suggestion: Apply critical thinking before smacking that "Approve" button. I know you guys see an absolutely incredible number of submissions day in and day out. The catch is finding the submissions that are worth posting to the front page of Slashdot. As of late it seems like submissions are being chosen more for their yellow (read: inaccurate) headline rather than their substantiveness as news. So please be considerate when choosing submissions.

Thank you all for listening! :-)

User Journal

Journal Journal: Did you open your eyes? 34

In a recent post on the topic of altruism being hardwired into the human brain, I challenged others to think about the theological implications of this. As the article suggested, many people jump to the conclusion that science is disproving the existence of a higher being. I used the exact opposite extreme to point out how silly that is.

Here it is again, but this time with the bolding reversed:

I figured it would be fun to respond with a similarly goofy argument:

It seems to me that if man is hardwired with an sense of altruism and a desire to believe in a super-being, there can be no other answer to this question than the existence of a Creator.

The question is, how many of you got the message? How many of you jumped to disprove a statement that did not need to be disproven in the first place?

Slashdot is composed of some of the smartest people in the world. Yet sometimes the smartest people can close their minds. The truth is that science does not prove or disprove religion. It cannot do that as it only concerns itself with the universe at hand.

Faith-based religion is not science. Let's not treat it as such. But science is not faith-based religion. Let's not make the mistake of mistreating it, either.

User Journal

Journal Journal: How I Slashdotted Google 15

It's not every day that you get someone from Google showing up to check on the spreadsheet you shared out using the Google Documents site. But that's exactly what happened after I posted such a spreadsheet in a Slashdot comment and accidentally created an impromptu chat room.

Someone over on Google must have been curious about all those server spikes, because a viewer with the address of google@google.com showed up shortly after the user traffic peaked. In fact, I had never expected that the discussion feature of the spreadsheet would attract so much attention. I figured that people would simply look at the sheet and discuss it on Slashdot. Perhaps even make a copy, modify it, and share it out.

So what could I do when the Google lurker was noticed? Quickly yank the spreadsheet from the public eye? Close my account and hope Google never traces it back to me? No, I went for hollering out an apology for the Slashdotting over the aforementioned discussion feature. This must have satisfied the lurker, because he then exited the sheet without saying so much as a word.

Then again last night, the sheet received a chat from a person with the gmail name of "google". The message was simply, "A chat room through the spreadsheet discussion? Who would have thought?"

While there's no concrete proof that these users were indeed from Google, it does seems likely given how Google tends to control its name inside its own system. Thus I have to wonder, will there be any repercussions from this? Will Slashdoters regularly create impromptu chat rooms with spreadsheets? Will Google use this as an example of how well their collaboration features work? Or will the whole thing simply blow over?

Who knows? But I can say that this little spreadsheet gone haywire was a fun experiment. And if we want to keep Google on its toes, we can always do it again!

Editorial

Journal Journal: A Day Without Mono is like a Day Without a Bullet in my Head 7

I have to admit, I think I owe Miguel de Icaza an apology. When we last butt heads, I believe I accused him of choosing .NET over the existing Java projects out of a case of "Not Invented Here" syndrome. And after the Silverlight announcement (which he wants to name fad-da daw'), I was even starting to buy into the idea that he might be a blind Microsoft follower.

But after spending a few days with Mono, I have changed my mind. It is quite obvious to anyone using the platform that the Mono team is not in bed with Microsoft. In fact, it would seem that the Mono team is explicitly trying to warn you away from .NET technology. Otherwise, why would they make it SO GODDAMN HARD TO DEVELOP FOR?

Excuse my outburst, but I'm just about at my wits end. Allow me to explain.

The whole thing started when I was working on a side project that required ASP.NET. As much as I might want to get around this requirement, it was non-negotiable. So, I looked into Mono and found that they had a special development server capable of running ASP.NET pages. I thought, "Great! Now I can develop on my Mac on the go!"

So I downloaded the Mono for OS X package and installed it. It compiled the requisite "Hello World" program with no issues. (Though it spat out Hello.exe for a binary. WTF?) The XSP server also ran a simple ASP.NET page without any problems. Great! Now all I needed was some documentation.

Before I get to that part, however, let me take a moment and address Microsoft documentation. I've heard plenty of programmers beam about how wonderful Microsoft documentation is, and how they absolutely love Microsoft documentation. If they had it their way, every program would have Microsoft documentation. Personally, I've always wondered what these people are smoking.

My experience has been that Microsoft documentation is poorly organized, lacking in detail, designed to run you around in circles, and packaged in a proprietary format that makes it non-portable and generally quite useless. The only positives to Microsoft documentation is that their docs are very pretty to look at and there is a LOT of it. (Which is what happens when you try to document every possible use rather than how to use the technology.)

Back to my story. Here I am thinking that I will simply download an HTML class reference and be about my business. After all, I'm an experienced programmer. Just tell me the library calls and I'll be good to go.

A quick check of the official Mono site produced the necessary HTML documentation. But only online. Nowhere could I find a download that I could take with me. The more I looked, the more I realized that the Mono folks want you to use a GTK# MonoDoc Browser. Oooook....

MonoDoc browser is (unsurprisingly) not shipped with the Mac OS X Mono package. So I went and downloaded the only package available: The sources. Of course, the MonoDoc browser requires GTK#, so I download those sources as well. It's all cross-platform code, so it should be easy to compile, right? *sigh*

When I untarred the source archives, what do I find? Something incredibly simple and reliable like ANT? Nope. The same old configure/make scripts that have been giving me nightmares for the last decade or so. No problem. I can do this. It's CLR code, so it MUST be a simple compile, right?

First thing that happens is that the configure script can't find Mono. Wait, what? How can it not find mono? It's in the path! After some checking around, I find that the build script is using pkg-config and pkg-config doesn't know about mono. Ok, so I create a mono.pc file in the /usr/lib/pkgconfig directory. Still can't find it. I move the mono.pc to /usr/local/lib/pkgconfig. Still can't find it. I set the PKG_CONFIG_PATH to the folder containing mono.pc. STILL CAN'T FIND IT!

As you can imagine, my blood pressure is getting dangerously high at this point.

I go back to the configure scripts to see if I can simply route around the check. No, it's pretty integral. But I do manage to find that the pkg-config it's pulling is an older version in /sw/bin. Mono apparently installed its own copy in /usr/bin. Ok, I can see that. So I switch the path around (making certain it's exported to the environment) so that /usr/bin will get checked first. It still finds the older copy. I struggle with it a bit more. It still finds the old copy. Finally, I rename the older pkg-config to pkg-config.old.

Eureka! It finds mono! Just to fail on GTK+!

Wait... what?

According to the configure script I don't have GTK+ or Pango. Yet I know they're both installed because of a few other OSS apps I compiled a while back. Finally, I give up. This is a dead end that's already sapped too many hours of my time. The craptacular Linux build process bests me again.

Let's try another tack, shall we? The mono package contained a pre-compiled (thank God) tool called monodocs2html.exe. All I need to do is feed the documentation sources into the tool, and voila! Instant HTML docs! Or so I hoped.

Unfortunately, I couldn't make heads or tails of the process. The documentation on generating documentation seems nice and all, but is a bit difficult to understand without some experience with the platform. And since I can't get any documentation on how to use the platform, I'm kind of stuck with a catch-22 there.

In theory, I just point the tool at the "assembled" documentation and it works. In practice, it keeps telling me that I need index.xml. Yet there's no index.xml anywhere in the lib/monodoc/sources directory. Not even inside the Mono.zip file. Rats, foiled again!

At this point I've resigned myself to wearing the ball and chain of an ethernet cable. After all, why would anyone possibly want to take HTML documentation on the go? Not that I've been too impressed in the online docs themselves. In Java, you tend to document API methods as you go. But with Mono, they separate out the docs from the sources, ensuring that no one ever documents anything! Documentation is handled entirely by online volunteers in a Wiki-like fashion, leading to a great deal of the library being documented with "Documentation for this section has not yet been entered."

So here I am now. My laptop useless in the face of such incredible resistance to using Mono. My blood pressure at all time highs. My patience long ago exhausted. For an instant, Google gives me hope that someone else has shared their generated docs! Yet it's nothing more than an apparition of a carrot dangling in the air as if to mock me.

I really do owe Miguel an apology. His team has been making wonderful strides in ensuring that the platform is completely inaccessible to new users. Thanks, man! We always knew you were secretly anti-Microsoft.

Supercomputing

Journal Journal: i need a new computer - advice? 29

Simple tasks like switching between Firefox and Thunderbird are driving the load on my machine up over 4, and if I'm trying to run Amarok at the same time, it drives it up to 8. In fact, my machine frequently climbs up into the 7-9 range, bringing my apps to a crawl and frustrating the hell out of me.

So I've decided it's time to buy a new computer. I'm going to replace my aging Sony Vaio desktop machine (which runs Linux) with something newer that has more RAM, a faster processor, and a bigger hard drive.

The thing is, I'm not entirely sure where to start looking. A quick walk through Circuit City a month or so ago lead me to believe I can get a rather "big" computer for as low as five hundred bucks, which further leads me to believe that if I were to buy something online, I can get a huge pile of RAM, a fast processor, and a big honkin' hard drive for even less.

I run Kubuntu, and use KDE as my desktop (though I occasionally switch to Gnome when I get bored) and I mostly use Firefox, Thunderbird, OpenOffice.org, Amarok, and run PokerStars in wine. I'm looking for something that can do all of that without slowing my machine to a crawl.

Anyone have any suggestions on where to start looking?

Edit: I don't think I have the patience to build my own machine out of individual parts. I also don't have any real loyalty to any particular company or architecture. New Egg has lots of machines with AMD processors, and though I've always had Intel processors because more things seemed to run on x86, that's not as much of an issue as it once was, right?

User Journal

Journal Journal: The Commodore 64, now on OSNews! 2

It looks like my most recent article has made it to the front page of OSNews. As usual, the comments got off to a rocky start with the requisite grouch making half-baked arguments. Other than the political sub-thread he started, the comments have otherwise been very positive.

All in all, I think the coverage is kind of cool. Wouldn't you agree? :)

Edit: Almost forgot! One poster was kind enough to provide a link to this little hack. (And I do mean *little*!) Smitty, I think that one is for you? ;)

User Journal

Journal Journal: Are You Keeping Up with the Commodore? 8

In an accidental followup to David Brin's article Why Johnny Can't Code, I share my own experiences with introducing my son to a Commodore 64. The experience convinced me that older machines are just plain better at teaching than modern software and computers. Which would be sad, except that the Commodore 64 is perfectly positioned to make a comeback as an educational toy!

Editorial

Journal Journal: Oil Industry-sponsored FUD at Slashdot? 12

I am absolutely stunned that Slashdot's editors would give credibility to a completely false story, pushed by a paid industry PR professional. As Rugrat said,

The "article" is not an article, but a press release written by an employee of a public affairs company.

"Tom Harris is mechanical engineer and Ottawa Director of High Park Group, a public affairs and public policy company."

For a website that spends so much time and energy combating FUD from Microsoft, and the MPAA and RIAA, it is baffling that FUD that was paid for and is pushed by the oil industry would make the front page here.

Come on, Slashdot. You can do better.

Debian

Journal Journal: So, About Dapper . . . 24

For the last year or so, I've been happily using Debian, with a mixture of sources so I was stable, but current, just like nearly everyone who uses Debian.

Then I tried to upgrade or something insane like that, using aptitude, and the whole thing went tits up on me. No amount of cussing, kicking things, or actual tinkering with the software could save my machine.

I thought about asking for some advice in the Debian forums, or on one of the lists, until I ran out of fingers in my entire family tree to count the times someone said some variant of, "Shut up, noob! Your stoopid and not leet leik I am! Go back to Winblows! Ha! HA! HA!!!1"

Yeah. Guess I'm not venturing into those waters, so I figured I'd just have to grab my network install CD and start over (luckily, I set up /home on its own partition a long time ago, so if I fuck something up really bad, I don't lose all my porn very important data.

The day I planned to reinstall Debian, I read that Dapper Drake had been released, and everyone loved it so much, they totally wanted to marry it. A friend of mine, who is wise in the ways of science and the air speed velocity of unladen swallows has also been singing the praises of Ubuntu for a long, long time, so I grabbed a Live CD to see what all the fuss was about.

Holy shit. What an awesome bit of work it is! It's the first Linux distro to find every single bit of hardware on my old Sony Vaio desktop machine, including all the USB ports. It looked great, too, and was the most "Mac-like" Linux I've ever used.

I realize that a lot of you are mocking me right now, but listen for a second: I'm not interested in hacking on my kernel to make sure something is detected during boot, or modifying all sorts of settings in a text editor just so I can make the damn thing find my camera . . . and don't get me started about CUPS. I love technology, and I love and fully believe in "free" as in speech, and I'm grateful for free as in beer. But also really into "works," as in just does. And on my machine here, Dapper Drake just works, and it's awesome. This is the Linux distro that I can take to my parents, and to my friends who are drowning in a sea of FUD, and convince them that they don't really have to be part of the Borg if they don't want to.

And ultimately, I believe that has to be our goal if we're going to convince people to give Linux a real, serious try as an alternative to Windows. We need to be able to tell them, with confidence, "Put this CD in your machine, and give it a try. I think you'll like it, because it just works."

Slashdot Top Deals

Understanding is always the understanding of a smaller problem in relation to a bigger problem. -- P.D. Ouspensky

Working...