Slashdot Mirror

This is incorrect. There are already a number of books and more on the way. http://search.oreilly.com/?q=iphone&submit.x=14&submit.y=13

Yes, and in Wikipedia, it is not.

Actually, it is. The only difference is that community rules lead to pressure, and the collective author ends up writing highly structured, linked documents -- most of the time.

And where's the evidence that "actually being paid" makes these articles better?

Anecdotal evidence on my part. A simple example: I've found The Rails Way to actually be a better reference -- not tutorial, but reference -- than the API docs and Google combined.

Of course, as a user, I'd rather have a publicly available, free resource, and heavily structured if it's to be a reference. Despite this, the sheer quality of that book, and the occasional sparseness of online documentation (especially concerning best practices), made it worthwhile to pay for.

Only difference with Knol is, I'd get it for free.

I find two dissenting articles much less useful than one homogenized compromise.

Sometimes. Sometimes, the homogenized compromise is simply wrong. Often, Wikipedia doesn't manage that -- you still have the two dissenting articles, but it's a lot harder to tell them apart (you have to dig through the edit history).

When I want to do an analysis, I just go to the primary literature.

Knol could be that primary literature.

But I don't think it is.

It's been out for exactly one day. What did Wikipedia have after 24 hours?

I am predicting that Knol will have some better articles than Wikipedia. But honestly, neither of us knows yet.

Because people have an interest in communicating their view of the world.

That sounds more Knol than Wikipedia -- Knol is all about a personal point of view. Wikipedia only helps you "communicate your view of the world" if that view is from a neutral perspective.

Furthermore, Wikipedia is not for original research, which is why you see all those [Citation needed] stickers.

I think Knol just misses the point of Wikipedia and why it has become so successful.

Because you've bought into the Slashdot meme that Knol is meant to be a replacement for Wikipedia. I'm not sure it is.

But I'll argue it could easily become a replacement for O'Reilly.

Doug Crockford recently wrote a book about this very issue of avoiding problems. It's called Javascript: The Good Parts I've been reading it (haven't finished yet) and it's quite good. He's very detailed about how the internals of the language work so you know why to use the "good parts" and a few reasons to avoid the really "bad parts". It's worth the few dollars for anyone that uses JavaScript regularly.

Are you sure? Software tends to be written by developers, and its the quality of them, their ability to work to quality standards and basically take their time to get it done right that matters. All that C code you've seen crash - it'll be because someone hacked it together, no-one tested it thoroughly enough, and no-one took the time to do it right. C is even easy to code reliably if you impose some restrictions on yourself (or use some libraries/routines that you can't easily take shortcuts with - eg if you can pass a pointer to a routine, you're going to pass a bad one one day, do some wrong arithmentic on it, etc. If you pass a strict fixed-size buffer, then you're much less likely to get an error. Just a simple example).

The point is you can write bad software in any language, the new C# stuff at work crashes all over the place and is slow. The old C code from 1984 is still working fine. Its not these languages that had anything to do with their relative quality.

eg. Spacecraft are written in C, and they've worked better than anyone expected:

The only reason I brought that up is because one of my editors said, Oh look, they have Java on this thing.

Oh, Java. Well, we have Java in the ground system not onboard the spacecraft.

Right. That's what it's starting to sound like.

That's right. Yeah. The spacecraft software is entirely in C.

C? Really? That surprises me a little bit.

Yes. It's entirely in C.

I thought Lockheed Martin was a big ADA shop for this sort of thing.

ADA is used largely in military applications, but JPL at any rate has moved away from ADA. Cassini, I believe, would be the last JPL mission that used ADA. And that was largely due to the success of the Mars Pathfinder in the mid-nineties. And as I said, these missions are to a large extent all derived from Mars Pathfinder.

After that successful mission, you say, Hey, we could do it in C now. That's not as scary as everybody thought?

Yeah. Right.

And again, that "stopping sales" tactic is a doomsday device which doesn't apply. Apple, on the other hand, can stop you and only you from selling on the iPhone for any reason they choose.

Jailbreak, Jailbreak, Jailbreak.

People are selling Jailbreak applications today. I have no doubt tomorrow they will continue to do so. Apple has no power over me if I do not wish it.

I prefer to go by what they have done (not let people into their program, not given a reason for it, not given a projected timeframe for acceptance, not given any mechanism for appeals) than by what they say they will do.

So Apple is the only company on earth to have a Beta period that gets more restrictive when it is over instead of less. Give me a break. At this point I think you are just trying to save face. Not to mention, that before Apple ever even HAD the SDK, you could Jailbreak and develop that way!

Not without jailbreaking it first it doesn't.

A tautology.

Would the PC be less open if the only legit mechanism for obtaining software was through Steam? You bet your sweet ass it would.

Now see, here is the core I think of why you are so confused. Selling Jailbreak applications IS LEGIT. ANYONE CAN DO SO. APPLE CANNOT STOP IT.

No my caps lock is not stuck, I think you need extra motivation to understand this key point that seems to elude you.

Answer me this: is the PSP an open platform or a closed platform?

Open of course, lots of homebrew there. It wasn't until that happened I thought of getting one (though in truth I still have not, I have a project for that on the back burner). Just like the DS, though both the DS and PSP are harder to jailbreak for and WAY harder to program for. Heck, you even use the same tools (XCode) for Jailbreak app development you do for SDK apps!

I will not respond further, this conversation is beyond a waste of time as obviously you will not come to your senses on this. But one last thought - consider that even O'Reilly thinks that the iPhone is open.

Are we to believe you, or freaking O'Reilly? If I were you I'd come to think that living in a world where everything is open to you is far superior to living in a world where stuff you consider to be closed, closes in all around you... the world is open to hackers my friend, and hacking is getting casual. Open your eyes to the practical reality instead of the veils manufacturers throw over things.

I was lucky enough to hear this talk.

FireEagle is a service that allows decoupling location information consumers from location information providers. It handles metadata on how the this information was obtained as well as user rights.

It's not a blogging service. Actually, I don't think it will be of interest to a lot of end-users at all.
It's more of a service to application developers. It can be a very useful service if adopted widely. May be compare it to OpenID for location or something. It shouldn't be seen as another geo-blog thing.

I'm not sure, but this O'Reilly guide to setting up a PPP connection in Win95 sounds a lot like what you describe. At the bottom of the page there is a graphic of the Connection Terminal Window, where you enter your username and password.

I recall using a dialer that the isp provided, but I'm pretty sure I had to set up tcp/ip manually (for Win 3.11 at any rate).

At that era, I also connected a couple of times to a BBS with Telix :)

Yeah, thanks for mentioning that. I have fond memories of Telix, too, but have to admit I thought Procomm Plus was the cat's you-know-what.

I've thought about recreating old setups in a vm, but unfortunately I didn't save much of my old software and I didn't do much to record what we did to get things working. I really took things for granted. I'm more diligent about documenting things now, but still waste too much time on Google searching for solutions to problems I solved a while ago but never documented ;)

Have fun with qemu.

The question of whether a computer can think is no more interesting than the question of whether a submarine can swim. ~Edsger Dijkstra

Also, for understanding recommendation systems and pattern recognition in volumes of data, I found Collective Intelligence to be a great resource.

Safari has been very good to me, if you can stand reading from the screen.

http://oreilly.com/pub/a/oreilly/news/languageposter_0504.html

http://www.levenez.com/lang/

An instructor at my college has those running along the hallway outside his office.

Might do better as a paid subscription service online.

Which is exactly what Pogue does with his books. They're on Safari. While not perfect - the site's a bit slow and clunky and it's really too expensive to justify ($40 / month for unlimited access, $20 / month for access limited to, I believe, 10 books) it is a useful reference site for computer related stuff.

It is more how I use his, and others, reference books. It's pretty rare that I want to read a reference book cover to cover and it's rare that any given computer reference book is really valuable for more than a year or two. If O'Reilly cut their subscription prices down a bit and sped up and cleaned up the site a bit, it would really be a great model for authors like Mr. Pogue, assuming he gets some sort of cut on the subscriptions.

Actually you have it mostly right, but slightly off. The GP had it right. Corroborating link

A lot of noise comes up about these various flash in the pan languages periodicallly, but if you look at a chart of language uses, even python that has been around for 10 years or more has only a few percentage points marketshare.

Meanwhile, Java is the most widely used programming language ever, at around 20%.

http://radar.oreilly.com/archives/2006/08/programming-language-trends.html

Whereas C and C++ hover around the 10 or 20% range.

I use python for some small utilities, and in fact I do expect python's usage to increase over time. However, expecting java or c++ to die, is like expecting English and French to die, and some Esperanto to take over.

It doesn't even *matter* that much if there's some language out there that's so much better than C++ or Java (which is debatable, but functional programming fanatics will scream so loudly about it so I'm not going to bother to argue the point), but that fact that such a vast volume of existing code is written in c++ and java, and there are so many tools and libraries written to support c++ and java development, makes it a *huge mistake* to start some kinds of large software development projects in some other languages, where all of these things will need to be written from scratch at enormous expense.

Projects written in non mainstream languages tend to either fall into a specific program domain the language was designed for, or tend to be very small scale, and usually both. There are very few good *general purpose* langauges that scale up and have good library and tool support. Read: There are *two* of them.... well, three if you consider c#, which I don't, because it is proprietary.

> it frequently fails to explain the fundamental
> Ruby concepts and structures that it's using.

David Black's Ruby For Rails is a great book for this; David explains the way Rails leverages all sorts of Ruby techniques to do what it does. Another good one is Advanced Rails, which has an excellent section on the changes that Rails makes to various Ruby core classes - e.g., Symbol.to_proc.

Here's a link O'Reilly's "Head First C#."

http://www.oreilly.com/catalog/9780596514822/

Best C#/Visual Studio book from what's in my opinion the best series of teaching books around right now.

Here's the link to free download of Visual C# Express.
http://www.microsoft.com/express/vcsharp/

That's not a trial. It's a free reduced feature version of Visual Studio 2008.

Refer to Microsoft maps about this. This has always been an issue. You will not get the same maps on http://maps.live.com/ as you will on http://ditu.live.com./ Satellite imagery has been a problem as well with Chinese map sites. Check out http://www.ditu.net/ to see how they got around that.

Here is a brief explination: http://radar.oreilly.com/archives/2007/12/live-maps-in-china-an-intervie.html
Was the data allowed to leave China? What other restrictions were placed on the data and its use? [vt] The map data is not allowed to leave the border. Some other countries also have the same regulations (Korea for example). In China, maps can only be provided by the licensed map data providers. Also the on-line publishing maps need to go through a âencryptionâ(TM) process whereby map coordinates are transformed to an unknown coordinate system (not in Lat/Long). This is mainly for the national security reason as far as I know.

I was almost sure I had gotten this link from slashdot, but after googling around, I just can't find where.

Anyway, here is an " interview with Sun's CEO. For those lazy enough to not click the link:

JesseStay: does he anticipate a fallout of original MySQL users or fork in the mysql code and how will they handle that if it does happen?

JonathanSchwartz: I'm not anticipating a fork - Marten Mickos (SVP, Database Group at Sun, former CEO, MySQL) made some comments saying he was considering making available certain MySQL add-ons to MySQL Enterprise subscribers only - and as I said on stage, leaders at Sun have the autonomy to do what they think is right to maximize their business value - so long as they remember their responsibility to the corporation and all of its communities (from shareholders to developers). Not just their silo.

I think Marten got some fairly direct and immediate feedback saying the idea was a bad one - and we have no plans whatever of "hiding the ball," of keeping any technology from the community. Everything Sun delivers will be freely available, via a free and open license (either GPL, LGPL or Mozilla/CDDL), to the community.

Everything.

No exception.

I just hope it's true.

when you go to the Linux section and look for "How to Program Linux" you're not gonna find it, because it doesn't exist.

That's funny, my copy of Linux System Programming must be a figment of my imagination, then.

I can just look at the pile of books in my office to call bullshit on that one...I've got 2 O'Reilly's and one "Essential" book that I can see just from where I'm sitting.

Checking my "Safari" account and searching for "Linux" I get 171 books. Searching for "Unix" I get 51.

He really is just nucking futs.

when you go to the Linux section and look for "How to Program Linux" you're not gonna find it,

Is replying to your own post bad form? Meh, who cares.

Interestingly, I just came across this relevant article on OReilly: http://radar.oreilly.com/archives/2008/04/when-authors-ask-us-about-the-consequences-of-piracy.html

Ok, there's a comment on the "user product" clause here: http://radar.oreilly.com/archives/2007/03/gplv3-user-products-clause.html

I guess you can choose to see it as a RMS plot, as you did, or you can see it as a question of practical issues. I would tend to the latter, and I would think a company buying stuff from another company needs less protection than consumers, who usually don't have a legal department to negotiate contracts. But YMMV.

In the case of wanting a reference book instead of something like the two I seconded the recommendations of above, I would have to recommend UNIX in a Nutshell. There is no better printed UNIX reference out there. Some of the chapter topics include the commands themselves, various shells, editors (this is super important), pattern matching, make, and more.

While there are plenty of books out there on Unix, not all of them cover all flavours of Unix. Sometimes you are better off getting something that covers one flavour well, or be happy with one that is a good compromise of all of them. The book I have is Essential System Administration. It is a good book, but there are are certainly times that I would like a bit more depth on certain subjects, but when that need arises I usually head off to the internet.

Definitely take a look at the second edition of O'Reilly's LPI Linux Certification in a Nutshell. The table of contents shows great overlap with the topics you're interested in.

First off, you can't go wrong with Essential System Administration, 3rd Edition by Aeleen Frisch. Really, really excellent book.

But just as important as the specifics of Unix, I'd argue, is the general question of how to be a good sysadmin. ("Start by installing Linux" is my usual smart-ass answer, but I'll skip that for right now...) The Practice of System and Network Administration, 2nd Edition, by Tom Limoncelli, Christine Hogan and Strata Chalup, is a truly excellent book about how to be a good sysadmin in the general case. I can't recommend it enough. (BTW, the link for the book comes from the authors' website, so I presume it throws them a few nickels if you buy it that way.)

Death caused by an electric shock is referred to as electrocution. Maybe you want to look up your vocabulary a bit more before you keep repeating this. because you were seriously not electrocuted.

Maybe you should realise that word meanings change and the dictionary definition of a word is by no means definitive. Here is some evidence that about 80% (at least) of people (based on a sample of about 420) would include non-lethal electric shock in the definition of electrocution. If you say they are 'wrong' that is meaningless; in English, words mean what people take them to mean, and if a significant number of people 'misuse' a word then the new meaning is an alternative definition of the word and will generally appear in the dictionary eventually.

If I had MOD points, and hadn't already commented in this article, I'd give them to you! Thanks for the link. I've added it to my bookmarks and will probably be reading over lunch(es). It also linked to this Tim O'Reilly book: http://tim.oreilly.com/sci-fi/herbert/ which is available free, online.

Free as in Freedom may also be found online for free (as in beer) ...in case anyone didn't know already.

As for software patents, I personally object to the very concept of granting individuals exclusive rights to ideas. Software patents are an abomination and should be abolished all together. I fail to see why it should change anything that the applicant is an open source business.

I'm tired of hearing "let the market decide" in general. Nowadays it's almost always used in defense of companies that prey on consumer ignorance, the very definition of something that the market will never solve. At the very least, if the market is to select a solution, someone has to start campaigning for one instead of just sitting on our asses. It's really a justification for inaction, nothing more.

I'm tired of replying to people defending lock in for various reasons, so I'll just suggest that those posters reread the book about one of the greatest people of our time:

"Although previous events had raised Stallman's ire, he says it wasn't until his Carnegie Mellon encounter that he realized the events were beginning to intrude on a culture he had long considered sacrosanct. As an elite programmer at one of the world's elite institutions, Stallman had been perfectly willing to ignore the compromises and bargains of his fellow programmers just so long as they didn't interfere with his own work. Until the arrival of the Xerox laser printer, Stallman had been content to look down on the machines and programs other computer users grimly tolerated. On the rare occasion that such a program breached the AI Lab's walls-when the lab replaced its venerable Incompatible Time Sharing operating system with a commercial variant, the TOPS 20, for example-Stallman and his hacker colleagues had been free to rewrite, reshape, and rename the software according to personal taste.

Now that the laser printer had insinuated itself within the AI Lab's network, however, something had changed. The machine worked fine, barring the occasional paper jam, but the ability to modify according to personal taste had disappeared. From the viewpoint of the entire software industry, the printer was a wake-up call. Software had become such a valuable asset that companies no longer felt the need to publicize source code, especially when publication meant giving potential competitors a chance to duplicate something cheaply. From Stallman's viewpoint, the printer was a Trojan Horse. After a decade of failure, privately owned software-future hackers would use the term " proprietary" software-had gained a foothold inside the AI Lab through the sneakiest of methods. It had come disguised as a gift."

It's ironic to post to an Amazon link, when the book is also free as in freedom.

The only safe way is to run the machine without a GUI. Is this possible on a Mac?

Ofcourse it's possible.

Either you can disable the gui entirely, booting straight into text-mode console:
http://www.oreilly.com/pub/h/348

Or you can boot to a console + gui mode, where it doesn't load the full gui, but you can still launch individual gui apps:
http://forums.macosxhints.com/showthread.php?t=24259

The architecture of OS X is not that different from other unices, except that instead of running X for the graphics, it runs Aqua, and instead of using init and a collection of shell scripts, it uses launchd and a collection of xml files.

Another way to express it would be to say it was sigmoidal.

I don't know why TFA encouraged users to look at the TOC and didn't link to it. (Even Amazon doesn't bother to include it.)

Looks like most of the sections are obvious to anyone experienced with Apache (as I am, I support it at work). But a few things in there may be worth getting my hands on a copy.

For a minute there I thought this was about Safari

Nevermind...

...if you're doing Rails apps is Advanced Rails by Brad Ediger. It's got a ton of helpful hints on all sorts of things - sessions, memcached, how Rails uses Ruby's dynamic features, how plugins work, how to do complex associations, details on REST, etc etc.

The nice thing is that he doesn't fool around with explaining the simple stuff that you know already if you've done even one Rails app; he gets right down to business. Of course there are always interesting gotchas, but this is a book every Rails developer should have.

Thanks for the kind review Slashdot! Thanks, Brian!

You can browse the table of contents of the book and read the beginning of each section at O'Reilly's website.

You can find another review of the book at rubyinside.com

On-line != public access. The trend is to make them available on-line for a fee. My library card doesn't get me access to Safari from home and I very much doubt it ever will. I can't see on-line public libraries happening, because that would completely destroy the business of every publisher which would result in far, far fewer books being written. Nobody wants that to happen. Perhaps all the books will be electronic, but you'll still have to go to the library to access them, because the library's terminals will have access to the electronic copies and the subscriptions.

Vista: The Missing Manual

http://www.oreilly.com/catalog/9780596528270/?CMP=ILC-MMh0me

That's the power of voice over IP, and it must be scary enough for big/old telcos when people can bypass them.

I just installed Asterisk (http://www.asterisk.org/) on a server, and created a SIP account for my mobile and my fix phone on it. Additionally, I connected Asterisk to different VOIP providers like FWD, Free, Gizmo, Pfingo...

For outbound calls, and depending on the price of each provider, I can configure Asterisk dialplan like let's say:
        Singapore +65XXXXXXXX route to Pfingo (0$/min)
        France +33XXXXXXXX route to Free (0$/min)
        UK +44XXXXXXX and US +1XXXXXXX route to Gizmo 0.02$/min
        etc...

For inbound calls, when a call is received from Pfingo or Gizmo telephone numbers, Asterisk rings both my fix and mobile phones through SIP. If my mobile is not connected to Asterisk (eg when 3G connection is down), Asterisk last attempt is to place a call to my "real" mobile number. When this also fail, Asterisk will redirect the call to the voicemail application, and I will get an email containing the sound file of the message.

Personally I hate receiving bills every month, or pay premium for making oversea calls. I really like to buy prepaid minutes online from VOIP providers, and spend them when and how I want.

I suggest you read "Asterisk, the future of Telephony" http://downloads.oreilly.com/books/9780596510480.pdf which is available for free. Also you can check different VOIP providers websites and see what they can offer to you. I've been playing with Gizmo since long time, service is great, and you can buy numbers in many countries. Minutes are cheap. Sound quality is good, but I remember few times where it was bad (toward China in particular).

The old management bought the product.

Not possible, as the University of California had significant IP in System V (going back to the 70's) and they've never transferred/assigned their rights to any entity other than BSDi. You can read here how AT&T/USL's attempted lawsuit against BSDi/UC over BSD Networking Release 2 made this pretty clear:
http://www.oreilly.com/catalog/opensources/book/kirkmck.html

So, SCO's argument changed mid-trial from "Linux violates UNIX System V IP" to "IBM violated license terms," and even that was shot down by Judge Kimball.

By the way, you can see a copy of UC's license to AT&T over contributed code/IP and documentation here:
http://cm.bell-labs.com/cm/cs/who/dmr/bsdi/bsdisuit.html

I try hard not to just summarize the book. Or just go over stuff that's really easy to get - I think you might find that this page has a lot of what you want - the toc will give you a great idea of what the book covers.

The subjects are covered thoroughly as I mentioned, with coverage of command line as well as gui tools and the appropriate config files. There is also some explanation as to why things work the way they do and nice ideas/examples of various ways that those options can be implemented.

I think the importance in regards to audience is not level of experience but rather desire. That's why I addressed this issue the way that I did. A person who doesn't care how X works - as long as it does, probably would not be too interested in this book or implementing what it has to offer. A person who is new to systems that use X or is experienced but hasn't played with X a lot would find it useful. I don't think it would bewilder a newbie. Things are explained thoroughly and I guess all they would need is some level of familiarity with the command line. Nothing extreme though. They could probably even get by without vim, as easy as it is to use things like Kate or other options. I guess I also assumed that anyone who would buy this - would in all likelihood know enough to work through it.

I can't really put the cost in the review - I mean I guess I could tell you what O'Reilly has suggested for the price - but if you are paying that, you aren't being a smart consumer. Every book review is accompanied by a link directly to the book at Amazon (or whoever slashdot links to at the time). And the ISBN is up there too - if cost is a consideration I'd use that to find your best option.

You could read it cover to cover. I did. It was almost all new to me so that worked out well. With any technical book - I think a good index is really important so that it can serve as a decent reference. This book has a good index and would work well as a reference. If it didn't have a good index, I guess the detailed breakdown of the toc would help - but it would still be tough to go back and hunt down specific bits. This is, in my opinion where Safari shines. Searching the electronic version is nice.

I didn't have any real problems with the book beyond the Linux orientation. If I had, I'd have mentioned them.

No bad information to my knowledge. There was one typo - they used the word depreciate instead of deprecate. I filled out the form on the book's O'Reilly page. It wasn't too big a deal, I knew what the author meant.

Aimed at Linux to the degree that it's pretty much always Linux he's dealing with when he moves outside of generic X stuff. I'm not sure what you want beyond that. That I thought I was pretty clear on, but I guess not. Now - in the case of the flavor of Unix I work with, AIX - a lot of Linux stuff is available on it now. But it would have been cool to know if AIX keeps something somewhere different from most Linux distros that he would mention that. But he didn't really deal with Unix that way. I'm assuming this is in large part due to the fact that it isn't as easy to get one's hands on Unix. I never worked with AIX until my current job - because my employer has it. I don't own any p-serires machines or anything myself. It's not a deal breaker though - because a lot of X stuff is pretty standardized across all platforms.

I wrote the review at Panera, on a Sunday morning after I finished the book. It's kind of a hobby, writing reviews and submitting them to Slashdot. I find myself often pulled to just regurgitate what's in the book. That would be more of a book-report than a review. With a review, my understanding is that I want to convey more why I think the book is worthwhile or not, as opposed to listing what's in the book. But maybe I pulled a little too far that way this time. The nice thing is, I think, if

Didn't understand how to use the library? The problem is, there are a ton of XMPP libraries out there for every language (the one you used is for javascript) and there must be an unwritten agreement that it's no use for each library to re-explain the workings of XMPP...

The best way, I'm afraid, is to read the RFCs (mostly 3920 and 3921. There are updated, clearer drafts, 3920bis and 3921bis, a link away from that page) and XEPs (XMPP Extension Proposal). There's also a book, but I heard that it's a bit outdated.

They also have Linux Annoyances for Geeks and Mac Annoyances book. What that says about Linux that specifically geeks are annoyed is unclear.

They also have Linux Annoyances for Geeks and Mac Annoyances book. What that says about Linux that specifically geeks are annoyed is unclear.

I hope you realize O'Reilly also wrote a book, "Fixing Windows XP Annoyances." http://www.oreilly.com/catalog/windowsxpannoy/index.html Also, Vista has very little to no resemblance of Windows ME. I can't help but think people who make this analogy haven't used both of them.

O'Reilly publishes quite a few books in the "Annoyances" series (Windows XP Annoyances, Mac Annoyances, etc.) This is just the next one in the series.