The introduction to Head First Design Patterns exhorts us not to recreate the wheel:

You're not exclusive. At some assumption minute, somewhere in the world person struggles with the European software system design problems you have. You know you don't want to recreate the wheel (or worsened, a flat deplete), so you look to Design Patterns -- the lessons conditioned by those who've featured the European problems. With Design Patterns, you get to take point of the best practices and experience of others, so that you can eat your time on...something else. Something more than difficult. Something more than structure. Something more than fun.

Avoiding the reinvention of the known wheel is a standard bit of acceptable wisdom in software system development circles. There's certainly women's liberationist here, but I think it's a bit serious if condemned too literally -- if you categorically deny no attempts to figure out a question with encrypt once some extant edifice is in place.

I'm not so sure. I think reinventing the wheel, if finished properly, can be functional. For mental representation, James Cervus elaphus reinvented the wheel. And he likeable it:

I reinvented the wheel last period of time. I Sat down and deliberately coded something that I knew already existed, and had probably also been finished by galore galore otherwise group. In conventional programing damage, I worthless my time. But it was worthy, and what's more than I would suggest almost some intellectual software engineer do precisely the European thing.

But who's James Cervus elaphus? Just other software engineer. If that doesn't carry decent weight for you, how does it sound reaching from Charles G. E. Moore, the person of FORTH?

A second consequence was even more than dissident: "Do it yourself!"

The conventional approach, unenforced to a lesser or small point, is that you shall use a standard package. I say that you should write your personal subroutines.

Before you can write your personal subroutines, you have to know how. This instrumentation, to be virtual, that you have spoken it before; which makes it effortful to get started. But give it a try. Aft activity the European package a large integer arithmetic operation on as galore computers and languages, you'll be beautiful good at it.

Moore followed this to an unbelievable point. Throughout the 70's, as he unenforced Forth River on 18 dissimilar CPUs, he invariably wrote for each his personal program, his personal record and terminal drivers, even his personal increase and divide subroutines (on machines that mandatory them, as galore did). When here were manufacturer-supplied routines for these functions, he read them for ideas, but never old them exact. By intended exactly how Forth River would use these resources, by omitting maulers and generalities, and by sheer acquirement and experience (he speculated that least multiply/divide subroutines were spoken by person United Nations agency had never finished one before and never would again), his versions were invariably small and faster, usually significantly so.

Moreover, he was never slaked with his personal solutions to problems. Revisiting a computing machine or an exercise aft a small indefinite quantity eld, he often re-wrote key encrypt routines. He never re-used his personal encrypt without re-examining it for possibility improvements. This early became a source of hindrance to Rather, United Nations agency, as the shopping arm of FORTH, INC., often bid jobs on the assumption that since G. E. Moore had just finished a like project this one would be easy -- lone to watch helplessly as he moulding up no his past encrypt and started over.

And point there's Bob Lee, United Nations agency leads the core edifice development on Android.

Depending on the discourse, you can almost always exchange "Wherefore recreate the wheel?" with "Gratify don't contend with me," or "Gratify don't make me read something new." Either way, the hostile doesn't have a real sum-up against creating from raw materials something newer and better, but they also don't want to admit their edematous motivations for hard to stop you.

More seeds, more than blooms, I say. Don't build houses on kitchen sinks. Recreate away. Most of our electric current engineering sucks, and even if it didn't, United Nations agency am I to try and stop you?

Indeed. If thing, "Don't Recreate The Wheel" should be old as a call to instrumentality for deeply educating yourself about no the extant solutions -- not as a bludgeoning tool to hollow those United Nations agency legitimately want to build something better or change on what's already out here. In my experience, sadly, it's little more than the former than the former.

So, no, you shouldn't recreate the wheel. Unless you plan on encyclopaedism more than about wheels, that is.

[advertisement] Did your brother just get his attending chewed off for other participant crash? Help him out by recommending PA Participant Monitor. He just strength grease one's palms you dejeuner. Download the Free Trial!

I still can't disbelieve how galore group believed yiPhone. It's awe-inspiring how a couple lines of javascript(the counter) can excreta so galore group off. I was just hard to push dev to work a little harder ;-)
I have never finished the jailbreaks for some former versions of the telecommunicate, what makes you think this one would be dissimilar? I also like to think I have more than honor than victimisation person elses put to work before they do. And really, United Nations agency was the being in the picture? Yorro? Once he exists, maybe yiPhone will exist.

Also, heres wherefore a certain somebody claimed the DFU was the key. You could, without some exploits, download the 114 iBoot(even to the 3g), the 114 kernelcache(ok, this crashes on the 3g), and a hacked ramdisk. But the filesystems don't mount. And even if they did, you'd requisite a way around sig checking.

Here is a little program(with source of course) to run some you want at the DFU level; an enforcement of the dev pwnage 2.0 put to work. Pass it a positional notation file, it will start death penalty at the start of the file(no file formats to deal with). I'll leave it to dev to excuse the put to work old.

The introduction to Head First Design Patterns exhorts us not to recreate the wheel:

You're not exclusive. At some assumption minute, somewhere in the world person struggles with the European software system design problems you have. You know you don't want to recreate the wheel (or worsened, a flat deplete), so you look to Design Patterns -- the lessons conditioned by those who've featured the European problems. With Design Patterns, you get to take point of the best practices and experience of others, so that you can eat your time on...something else. Something more than difficult. Something more than structure. Something more than fun.

Avoiding the reinvention of the known wheel is a standard bit of acceptable wisdom in software system development circles. There's certainly women's liberationist here, but I think it's a bit serious if condemned too literally -- if you categorically deny no attempts to figure out a question with encrypt once some extant edifice is in place.

I'm not so sure. I think reinventing the wheel, if finished properly, can be functional. For mental representation, James Cervus elaphus reinvented the wheel. And he likeable it:

I reinvented the wheel last period of time. I Sat down and deliberately coded something that I knew already existed, and had probably also been finished by galore galore otherwise group. In conventional programing damage, I worthless my time. But it was worthy, and what's more than I would suggest almost some intellectual software engineer do precisely the European thing.

But who's James Cervus elaphus? Just other software engineer. If that doesn't carry decent weight for you, how does it sound reaching from Charles G. E. Moore, the person of FORTH?

A second consequence was even more than dissident: "Do it yourself!"

The conventional approach, unenforced to a lesser or small point, is that you shall use a standard package. I say that you should write your personal subroutines.

Before you can write your personal subroutines, you have to know how. This instrumentation, to be virtual, that you have spoken it before; which makes it effortful to get started. But give it a try. Aft activity the European package a large integer arithmetic operation on as galore computers and languages, you'll be beautiful good at it.

Moore followed this to an unbelievable point. Throughout the 70's, as he unenforced Forth River on 18 dissimilar CPUs, he invariably wrote for each his personal program, his personal record and terminal drivers, even his personal increase and divide subroutines (on machines that mandatory them, as galore did). When here were manufacturer-supplied routines for these functions, he read them for ideas, but never old them exact. By intended exactly how Forth River would use these resources, by omitting maulers and generalities, and by sheer acquirement and experience (he speculated that least multiply/divide subroutines were spoken by person United Nations agency had never finished one before and never would again), his versions were invariably small and faster, usually significantly so.

Moreover, he was never slaked with his personal solutions to problems. Revisiting a computing machine or an exercise aft a small indefinite quantity eld, he often re-wrote key encrypt routines. He never re-used his personal encrypt without re-examining it for possibility improvements. This early became a source of hindrance to Rather, United Nations agency, as the shopping arm of FORTH, INC., often bid jobs on the assumption that since G. E. Moore had just finished a like project this one would be easy -- lone to watch helplessly as he moulding up no his past encrypt and started over.

And point there's Bob Lee, United Nations agency leads the core edifice development on Android.

Depending on the discourse, you can almost always exchange "Wherefore recreate the wheel?" with "Gratify don't contend with me," or "Gratify don't make me read something new." Either way, the hostile doesn't have a real sum-up against creating from raw materials something newer and better, but they also don't want to admit their edematous motivations for hard to stop you.

More seeds, more than blooms, I say. Don't build houses on kitchen sinks. Recreate away. Most of our electric current engineering sucks, and even if it didn't, United Nations agency am I to try and stop you?

Indeed. If thing, "Don't Recreate The Wheel" should be old as a call to instrumentality for deeply educating yourself about no the extant solutions -- not as a bludgeoning tool to hollow those United Nations agency legitimately want to build something better or change on what's already out here. In my experience, sadly, it's little more than the former than the former.

So, no, you shouldn't recreate the wheel. Unless you plan on encyclopaedism more than about wheels, that is.

[advertisement] Did your brother just get his attending chewed off for other participant crash? Help him out by recommending PA Participant Monitor. He just strength grease one's palms you dejeuner. Download the Free Trial!

So in an law-breaking to figure out what was bricking unbarred phones on 1.1.1, I upgraded my unbarred telecommunicate to 1.1.1. Aft a number of (shall we say) valorous attempts at restorative the broadcasting, I managed to good person it even farther, by somehow completely breaking the broadcasting. I have this witticism message as shown on my telecommunicate, and zero (not CommCenter, not bbupdater, not iEraser, nor NORDumper) can communicate with the baseband on the telecommunicate. No restores fail because they can't talk to it.

So it looks like if I want to continue experimentation with 1.1.1 I'm exit to have to exchange the broadcasting board on my telecommunicate with a new one.

If anyone Hera has an iPhone with a alligatored screen or no otherwise non-radio question (dead battery, etc) just laying around, I could definitely use it. I'll send you an assembled Time Fountain for it, if you'd like.

This is a post I wrote a long time agone, when this communicate was first formed. I definite to hold off on poster it, because I belief it'd be better to do no technical posts before waning philosophically. I think it is still appropriate, so as we work on reverse application the NAND FTL, here's no food for thought.

Porting UNIX to the iPhone is an difficult project. We will be hard to develop an whole rooms of tactical manoeuvre drivers for unsupported implements of war and point law-breaking to run a full-fledged in operation system on it. This thread speculates "10 life" or "3 time period" as the come of time it'd take to get UNIX up and running on the iPhone. Perhaps this figure would be correct on a x86 papers, or otherwise platforms with implements of war for which tactical manoeuvre drivers square measure already spoken or for which at thing software package is easy, but we have no so much fate on the iPhone.

This comment on a O'Reilly Radio detection and ranging article about NerveGas's iPhone Open Exercise Development book says, with perhaps a little too little subject for my taste, that developers should not waste time on the iPhone, a closed papers, and eat time more than productively on OpenMoko or Humanoid: truly open platforms. Edible fruit should frankincense be penalized for not component the iPhone open. His point is well-taken though. Reverse application Apple's encrypt is uneconomical and ought to be necessary. Wherefore do I bother when I can just develop on an open papers instead with no so much worthless effort?

Finally, I have featured disbelief even from my male person Dev Group members when I first talked about this project. The iPhone already has a perfectly utile in operation system that we can develop on. Wherefore does it requisite other one? Sure, UNIX strength be cool, but what virtual use would it have? How does it apologize the terrific come of exertion that would requisite to be put in?

So. Wherefore do I bother? Wherefore should we bother?

Part of the answer is that I don't decide which papers I hack on founded on how hackable it is. I decide it founded on how little I like it. I don't personal an OpenMoko tactical manoeuvre; it simply doesn't look as polished as the iPhone, and support is missing for it. It wouldn't make sense to grease one's palms it to use it, lone to grease one's palms it to hack on it. Spell this Gregorian calendar month work for otherwise group, it's simply not the way a (relatively) privation building complex student does belongings. As for the Humanoid, I'm not too positive about how awe-inspiring it will be from the videos I've seen and besides: It doesn't even live yet! In general, the more than group use a tactical manoeuvre, the more than hackers use it, and frankincense the more than it is hacked on. Utility frankly trumps hackability.

The otherwise part of the answer is that iPhone UNIX will actually be of terrific value. Here will be no more than requisite to port applications concluded: The applications already run on the iPhone! Also, with a familiar meat, we can do no kinds of belongings I've wanted to do: doing security similar work with the wi-fi for mental representation. Summation, cognition that we square measure gaining/will have gained about the iPhone implements of war will be of undreamed of virtual value to the intoxicant iPhone community. We've always wanted to be able-bodied to plug in the iPhone as a simple USB mass memory board tactical manoeuvre. With USB and NAND FTL drivers, we can actually compel this ourselves.

Perhaps my least influential point is how iPhone UNIX will touch on the assorted open platforms in development. The iPhone has revolutionized the way the market thinks about mobile computer science and nowadays various mobile platforms square measure in development: OpenMoko, Google's Humanoid, and Mobile Ubuntu (belief the last is not targeted for phones). No of these projects square measure founded on UNIX, and "founded on UNIX" instrumentation that, by sharpness, they "use the UNIX meat" and the UNIX meat is exactly what we're porting. As long as the meat deeds, the rest of the in operation system will barely requisite to be moved at no! (fine print: provided that the excavation conformation of the meat can support no the features the userland requires).

Envisage OpenMoko on the iPhone. Humanoid on the iPhone. Ubuntu Mobile on the iPhone. Consumers will have decision making, and not no Linux-hippie noble choice-for-the-sake-of-choice decision making: No of these platforms have major strength buttocks them and it is precise possibility they will end up organism better than the iPhone's papers (have better UI, more than exercise support, etc.). Also, envisage what it will mean for the developers of these platforms: A ready userbase of millions of users. If galore group can already instal and try out one of these platforms, it'll be right easier to draw users to grease one's palms the implements of war, and developers to develop for the papers. Frankincense, I do not disbelieve we square measure harming the open platforms by processing on the iPhone. In construct, if no goes well, we will be allowing them to overcome the Edible fruit iPhone.

Of course, I know the response to no of this. "That sounds good, nowadays show me the encrypt." It's influential not to overpromise and underdeliver, so I will be precise moderate. What I have just same is the hope, the best possibility consequence. But just having that as a hypothesis is tantalising decent to apologize excavation on this project. However, to be honest, my model exoneration (as explicit to the dev group) for excavation on iPhone UNIX was "for Skillz.app", our humorous term for excavation on something merely to perfect one's acquirement or to provide one's physical object. But honestly, what did you reckon from a "coder"? :)

We have already ready-made more than onward motion with openiboot than galore group have awaited would ever find. Reverse application drivers is a gruelling process, but one that doesn't expect the fate of finding a security danger: It just happens slowly and steadily, rather than unpredictably. Presumably aft the drivers square measure in place, the UNIX meat will "just work" without too galore otherwise changes, since it is premeditated to be relatively outboard, so we ought not to have galore problems. Aft the meat deeds, I hope decent developers will transmute concerned and a nice userland can be matured without too little trouble. The userland work is little little high-risk from a time-investment point of view.