Hacker Newsnew | past | comments | ask | show | jobs | submit | more lambda's commentslogin

FreeBSD is targeted at x86 running on desktops and servers, and is generally considered the most "complete" distribution for those use cases, with the most packages available for that platform, widest range of features, etc.

NetBSD focuses very heavily on portability. They target lots of architectures, focus on getting cross compilation working well, and spend a lot of time worrying about doing things "right" rather than expediently (for what it's worth; this can be good or bad depending on how you look at it). Their package manager/ports system is known as "pkgsrc", and also focuses on portability, such that it also runs on other platforms like Linux, Mac OS X, and so on. If you want to try porting a BSD to your odd little MIPS-based microcontroller, NetBSD is your best bet.

OpenBSD is focused extremely heavily on security. If you are paranoid, you want to run OpenBSD. If you are not paranoid, you should be. They are out to get you. Don't let them.

And the other major BSDs that you didn't ask about:

Dragonfly BSD is a sort of next-gen fork of FreeBSD, a bit more experimental. The biggest new feature is its HAMMER filesystem, which is in the class of modern filesystems like Btrfs and ZFS, supporting things like snapshots, checksumming of data and metadata, mirroring to backups, data deduplication, and the like. It also has other features like user-space virtual kernels, better parallelism, etc.

PC-BSD is designed to be a user-friendly, desktop-oriented BSD, which manages applications as separate bundles with installers, more similar to how they work on Windows on Mac OS X, than a traditional BSD ports system or Linux package manager which tries to manage shared dependencies (a PC-BSD package comes with all of its dependencies, which are installed separately from those of other packages).

OS X is a hybrid operating system, based on combining the Mach microkernel, FreeBSD, and some NetBSD tools, along with a proprietary UI layer and applications. It runs on desktops, laptops, and ARM-based smartphones. It is well known for its user-friendliness, tight integration between software and hardware, and draconian application development policies for its package management system, the App Store. Luckily, there are alternative ports systems available, such as MacPorts, Homebrew, and Cydia.


This article has a bit more detail about the procedure itself; it mentions the flight attendants assisting, but no nurse:

http://community.seattletimes.nwsource.com/archive/?date=199...


This gives you a whole new perspective on techies who gripe about being roped into fixing the family computer over the holidays because they are "on vacation" and don't want to work!


Huh. According to the article that you linked to about the coat hanger, brandy, and rubber tube: 'The aircraft's medical kit is "quite well-equipped for having babies and people who develop urinary blockages..."'. In fact, it sounds like the tube they used to drain the lung was a catheter intended for urinary blockage. I wonder why they couldn't use such a catheter for this guy; did that kit not have one?


If it progressed to the point of a true medical emergency, I suspect the kit at least had the equipment necessary for a 'quick and dirty' suprapubic aspiration of the bladder (stick a longish needle in from the front, and use a syringe to pull fluid out).

Generally speaking, this is done with an ultrasound, but in a pinch, you could likely just palpate the bladder.


Obligatory xkcd: http://xkcd.com/208/


I have heard someone tell a story about that happening once. They said that the cabin crew announced that they would be playing a game; they would call out an item, and give a free drink to the first person who could find that in their carry on. The first couple of items were fairly standard things; "a fountain pen", "a camera", etc. Then they got to "a commercial pilots license". Someone actually did raise their hand, and the cabin crew escorted them up to the cockpit.

There was never any problem with the flight, and he never found out what happened. Probably something like the co-pilot had a problem that prevented them from continuing to act as the co-pilot, and they wanted to maintain sufficient redundancy just in case.


That's not even fair, because the commercial pilot wouldn't have been able to collect his free drink!


The flight time requirement for a commercial pilot is only 250 hours. All flight instructors are commercial pilots. They are more common than you think.


Also, isn't there a pretty big distinction (even just in terms of required flight hours) for Commercial versus Airline Transport (ATP)? ISTR that ATP required at least 1k hours.


True, but in an emergency, the FAA probably wouldn't make a fuss :)


They are pretty much killing the idea of using regexes to linkify URLs without the scheme in plain text. Given that Chrome has moved to dropping the `http://` from its address bar, and many people already skip it, they are probably going to break a lot of linkification code in comment forms and the like. Sure, people "should" know to type the `http://`, but many people just don't know about that or don't remember, and there's a lot of encouragement not to.


>Given that Chrome has moved to dropping the `http://` from its address bar

Uh, if you try to copy it, Chrome prepends the http://. It's only a visual effect, it still pastes full links.


Yes, but lots of people simply type links rather than copy-pasting. If you don't see the `http://`, you are less likely to remember to type it.


There are an infinite number of ways of solving the same problem. I have dozens of tools with which I can solve most of my problems; and I can choose to do it in many ways. Sure, there are only so many ways you can write binary search, in a given language. But that doesn't mean there is only one way to solve an actual problem.

For example, if your problem is looking up elements in a dictionary (key-value) structure, there are many ways to do it. A hash table? Binary tree? B-tree? Sorted array? Trie? Patricia trie? Linear search in a linked list? Linear search in an array? Are the arrays fixed sized, or variable sized vectors? All of these solutions may be correct, depending on other factors, and all of them have many variants.

And that, of course, assumes that you know that a dictionary structure is what you need. Maybe your problem actually would call better for a table with GiST indexes, or a quadree dividing up a two-dimensional space.

Above that level, even if your data structure needs are fairly simple or fairly well determined, there's how you structure and organize your code to minimize the chance of bugs, make it extensible, and make it understandable to future programmers. Most of my work isn't writing fresh code. It's finding and fixing bugs in existing code, and extending it to do new things it was never intended to do. Depending on how well organized it is, and how expressive the code is of its intent, that job can be much more difficult or much easier.

That's where a lot of the creativity comes in. Finding the write way to structure and express your code to fit the problem at hand. Writing code that will be adaptable to the future, easy to extend without introducing new bugs, easy to fix bugs in, but without including a lot of extra machinery for features that you will never need. It is easy to write code that does a single task, but will be fragile if someone ever tries to extend it to do something else. It is also easy to spend all of your time writing AbstractFactoryIteratorFunctionFactoryAbastractGenerators which are infinitely modular and extensible but don't actually solve any problems.

Great code is code which solves a real problem, and can be used tomorrow to solve five more problems that you didn't even know about today, but which doesn't suffer under the weight of being designed to be extended in ways that you thought might be useful later, but wind up never being so. And writing such software, and modifying in those five ways, takes a substantial amount of creativity.


Ah. That, then, changes the meaning of this quote entirely. If he's merely saying that training alone, as opposed to a combination of training and education, is insufficient, then that is much more plausible. I was reading the original post as including what he defines here as "education" in "training".


Hmm. I'm not so sure about his analogy with writing. Of course, most people who take creative writing don't go on to become great writers; that pretty much goes without saying, most people in any field don't go on to become "great" (the very definition of "great" is that it's exceptional). So that part is a tautology.

Now, I wonder about how many people who go on to be "great writers" received training in writing? Of course, "creative writing" as an academic discipline is rather new, but English has been around as a discipline for years. From a quick poll of the authors mentioned in http://en.wikipedia.org/wiki/20th_century_in_literature and http://en.wikipedia.org/wiki/21st_century_in_literature, almost every one had at least a college education, mostly in the humanities (which generally require a lot of writing, and train you in writing). And most of them have worked at lower-level writing jobs before becoming great writers; copy editors, journalists, corporate writers, and the like. Several of the more recent "great writers" of the late 20th and 21st centuries have indeed gone through creative writing programs.

So his analogy, at least, seems to be false.

How about in writing software? Well, as I mentioned, it's pretty much tautological that no training program can produce entirely great programmers. The purpose of training is to turn lousy programmers into mediocre. Mediocre into passable. Passable into good. Good into very good. And very good into great. You are not likely to train all of your lousy programmers into great; so claiming that training does not produce great programmers is attacking a strawman.

I have seen plenty of people who have gotten a degree in computer science who are lousy programmers. And I have seen great programmers with no formal education. But on the whole, when I've looked at programmers with equivalent amounts of experience, but where one had formal training and the other did not, I would prefer the one who had some formal training. People who have not had formal training tend to not have much experience with reasoning about algorithms, or invariants, that can make their code a lot better.

While its true that nowadays we have many libraries and tools that mean that the average programmer can just use built-in data structures and do a pretty good job, I've seen enough code that was so horribly inefficient that even a little bit of algorithmic analysis upfront would have been helpful. Or a lot of code where someone just hacked away at a problem until they had something that worked, rather than trying to formulate a model that would underly it and keep the code well-organized and understandable.

And among those programmers who are self-taught but great, they have put in deliberate practice, and deliberate study, even if its on their own.

So sure, there are some people who are just untrainable; I've worked with some of them. And there are some people who are naturally brilliant and able to study independently. But all else being equal, I think that deliberate training definitely has value in improving the quality of programmers as a whole; and so yes, training will lead to more great programmers.


"Eat a bullet" is slang which means being shot. As in, the update kills certain fonts. It's also a pun, because fonts contain a character known as a bullet: "•".

Yes, the Reg is an IT tabloid; they do an entertaining, sarcastic, and pun-filled take on IT news. I wouldn't call it blogspam in general; they do real reporting, and provide more than the usual blogspam "link, quote, and one sentence summary." In this particular case, the source they quoted probably would have been a better article to post, as it is longer and contains more information.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: