skysight-inc/HackerNews huggingface dataset:
XSLT was created to allow for document tree translation in an implementation independent manner. The main problem I have with this concept is that document translation is that 99% of the time you're doing it, it's to get the document to the format your app needs or from the format your app needs. In other words, the vast majority of translations depend on the implementation, so what's the point of an implementation independent translation language?

So on its own as a templating language, XSLT 1.0 had problems of varying size. The biggest by far was that the 1.0 spec had the absolute worst string handling of any language I've ever come across. It's erlang bad with the syntactic elegance of being an XML language. This is somewhat corrected in more recent versions but I think this is the primary reason the language has failed to gain adoption. If you're doing whole node manipulation, XSLT is adequate. It's not elegant, but it's flexible and I generally don't have problems getting the results I want in short order.

I do like a number of ideas present in XSLT, particularly the concept of templating documents as trees (guarantees well formed output) and transformation by pattern matching. Those both carry over into my preferred templating language, Python's Genshi, which some people like and some hate. To me it provides a good balance between purity and practicality.

As to your specific questions, I did one site in pure XSLT back in 2003-2004 and vowed I'd never do it again. I have a guy at work who really likes Symphony and produces good quality stuff with it. If I had to do PHP it'd actually be one of my top choices (I don't like PHP either...). I've never regretted learning xpath, since it seems to pop up regularly in unexpected places and isn't THAT complex. The complexity in xpath comes from many implementations not fully implementing the spec. HTML 5 has an XML encoding, so there's no reason that XSLT would work worse with HTML 5 than it does with XHTML.

XSLT will never be the one true path for templating, but its presence as a standard will always attract people who appreciate that sort of thing (I'm not one of those people) so it's not really a dead end either.
X-axis = dates (Jan 1st - Dec 31st)

Y-axis = price
I don't get this either or thing. I got a BSc in Computing Science when I was a kid. I'm 30 now and preparing for the GMAT. I also keep abreast of the latest on the lean startup and on the fat startup. Why not learn it all?
Also: http://en.wikipedia.org/wiki/Google_logo
Communication is important enough to have had it's own section. Communicating to future maintainers through code, comments, tests, and documentation. Communicating designs, ideas, issues with team and leaders. Communicating everything with designers, customers, testers, and stake holders.

A good engineers are good individually. Great engineers work with and elevate the team(s) they are part of. In military parlance they are force multipliers.
I liked hearing their laughter. It was never at a bad time (it did not "disturb"), and for me, the more people I hear laughing, the more I enjoy something.

(I did upvote you, because while I think a score of 0 is OK, I don't see why you should be at -1 just for expressing your opinion)
Wired meets the woman behind Sugru
Measuring API usability
Consider yourself lucky -- you must live in a nation that doesn't strictly enforce the "one carry-on item" rule (and yes, handbags or laptop bags count as a separate item of luggage, so the whole lot has to go in your carry on before processing through Security).
Craigslist diamond ad leads to deadly home invasion, police say - CNN.com
Right, not worth learning it now.
BTW Blizzard uses in-browser XSLT on most of their sites - http://extremelyxslt.blogspot.com/2008/07/world-of-xslt-craf...
Wonderful picture set, but by the the fourth slide, Heather Poole has become "Ms. Pools" and in the ninth photo drops to "Ms. Pool." Maybe the NYT needs instructions for how to proofread for 12 captions in a web browser.
When you change your Facebook password, it doesn't take 14 days for the change to go into effect. Even if Facebook does need some time to really delete all of your information from all shards, datacenters, whatever - the least they can do is immediately restrict access to your account. After all, that is exactly what you are asking for.
I'm always amazed by how bad most people are at packing. I see people going to lie on a beach for a week with a suitcase big enough that they could fit in it themselves. Sometimes two.

When I was a 13 year old Cadet they told us, after every exercise make two piles, stuff you used and stuff you didn't. Aim was for the second pile to be as small as possible. Nothing teaches this as well as everything you pack, you have to carry on your back!

If I'm on a two week business trip, I'd pack for one week and just expense the hotel laundry.
Where do you live? I just came back from a Saudi-Jordan-Canada-USA trip with a backpack and a DSLR in a separate camera pack and a bag of food as my carry-on on some very crowded and over-booked flights.

(EDIT: Backpack not Backup... damn computer terminology!!!)
resulted in the most significant intraday drop ever - this is worth spending some time looking into and understanding what happened
If you do use XSLT make sure to use 2.0 if at all possible. It has some key features like extra built in functions that make it a lot more palatable.

Personally I think XSLT is an interesting language from a theory perspective, and it taught me some interesting things about rule-based programming. However there are too many serious limitations in it in terms of everyday practical use. In addition to the verbosity problems others have mentioned, here's a good list of things XSLT can't do:

http://www.dpawson.co.uk/xsl/sect2/nono.html
If request handlers block (by calling MySQL among other things), then one instance of Tornado per core may not be sufficient to take advantage of a machine's resources.

Tornado includes optional code to fork more than one instance where the number of instances defaults to the number of cores. Tornado's forking code has issues:

- There's no code to restart dead child processes.

- It's not possible to do a rolling upgrade because all instances of the server must be restarted at the same time.

I'd stay away from the forking code in Tornado. I suspect that it's not used by FriendFeed because the forking code was added well after the initial release of Tornado.
If you're making that much money/impact due to the greater pageviews, you can afford the 10 minutes it takes to do the copy-and-paste donkey work.
In my opinion you're the ideal MBA candidate - undergrad in either engineering or a science, some work experience, then the MBA. The problem is that so many MBAs have undergrads in Business and go straight to the masters without any intervening work experience. So they don't have experience and the courses have a lot of overlap. They give the MBA a bad name, but they're the cash cow of business schools.
I never considered rolling clothes instead of folding them. I guess I can imagine how it truly would limit wrinkles if they're rolled tightly enough!
There is nothing ironic about it. His whole point is that sharing should be something the user chooses to opt-in, which is the case with that "share on" bar.
> I am saying that you should try to accomplish the task on your own first, and if you get stuck, then ask for help. Don’t simply ask for help every time without first trying to solve the problem yourself. Chances are, you’ll find that you could have figured it out on your own once you know the answer.

If you're a junior engineer and are working with and older engineer you respect. I highly recommend you try to solve the problem, make a start at it, and then ask your mentor what they think of your approach at lunch, on break, or at the end of the day. This gives you most of the benefit of actually implementing something while saving you most of the pain of having to maintain your mistakes.
No.

Ok to elaborate, there are too many walls you hit in using XSLT. You'd be better off with a templating layer with a faster language much like tenjin, mako, jinja etc in the python world but every platform has them.
This was a linux laptop. I immediately powered off and booted with a live CD. To be honest I'm not sure exactly what I did next. I might have just done "less -f /dev/sda5". I think what I actually did was make an image of the partition using dd to an external drive so I would be able to recover the file at leisure. Trying now, it seems that vim won't open a /dev block device directly, but an image is just a regular file.
Why isn't the scale on Google Maps detachable?
You're right. http://bits.blogs.nytimes.com/2010/02/02/youtubes-take-from-...

Summary: In January they rented out 5 Sundance 2009/2010 movies, available for 10 days, and got a total of 2684 views. Net revenue $10,709.16 (at $3.99 per rental).
I'm curious as to why lifestreaming never caught on: why entrust all your data to a single service (Facebook) when you can entrust specific data to specific services (photos to flickr, status to twitter, bookmarks to delicious, etc). This fragmentation produces specific competition for hosting particular data (this is already the case: Flickr, Smugmug, Picasa etc) which should keep hosts fresh and honest as they don't want to lose users.

All lifestreaming did was aggregate all of this into a discoverable point with privacy controls.

What happened?
I like it. It's simple and clean and I can access my favorites from anywhere. Put your browser's bookmarks bar in your a.. and show me your work
Google trends issues hot media: Turkey's first nudist hotel plan hits hitch
Essentially, social platform providers would be hosts to their own users and each users' respective social graph. Nodes in that graph can be native to the platform, or external.

External nodes/users can decide how much they want to share with external providers, on a provider-by-provider basis.

Each provider, thus, would have a record of how each of its hosted nodes perceives each external provider, trust-wise.

In order for a node to find a new external node, they would use their contact's email address. The provider would send a request to all providers it has on record. Depending on how the requestee perceives the requester, he can either ignore or answer the query. If he "knows" the email hash, he can prompt that node/user for permission to send data to the requester - and what level of data to send. If the requestee does not know the hash, the request recursively travels throughout the social platform providers.

One of the necessary requirements to being a part of this kind of distributed social network, of course, would be the ability for a user to download their social graph (nodes of email hashes connected to them) and easily port it to another provider. Sort of like exporting your email box contents to bring to another provider.

If we throw out the idea of users having unique IDs other than their email address, it would be possible to have different social networks on different providers - e.g., business from one provider and family on another. If a user deemed it, they could potentially also link several email addresses to the same account on one provider.

This kind of scheme would have the qualities of being:

* Robust: any platform which follows the protocol can participate; Potentially, if a platform goes AWOL, and the nodes within it had sufficient transparency to nodes outside of it, any given provider could rebuild their social graph for them.

* Trust: Based on how the nodes on a given provider dole out their social graph / user information to other providers, that provider can perceive the general level of trust its users have about that provider. It can pass this metric on to other providers who request it.

* Portability: need I say more? :)
Wasn't MW2 available for pre-order for something like six months?

edit: I can find mention of pre-ordres of MW2 being available as far back as April '09
I really liked this sentence: "It feels a lot like desktop Linux: unpolished, but covered in gloss."
You might find some more information about such architectures that the research community is currently looking at:
http://prpl.stanford.edu/ is one such.
I love Heroku but I subscribe what you are saying. It's too expensive scaling an app on Heroku. I really hope they decrease the prices.
It was a very good plug for the authors' own classes that he teaches (link in the last paragraph).
This is exactly what we are doing in toostis.com. We try to create a one-in-one tool for sharing this kind of information with your interest circles (that we call "tribes"). Currently when you log in and start attending events the recommendation algorithm learns about different social groups you belong to.

One needs to consider three approaches of forming an interest circle: shared (an explicit list of members), individual (each user maintains several lists of his friends) and automatic (extracting subgraphs of user relation according to attendance).

What we are currently willing to provide is the combination of them all. Automatic extraction is fun to play with, but you always want more control over it. We are also preparing to launch something similar to the shared model, where you could subscribe to an organizer which is basically a group of related events.
So all the On-Demand instances were free on Jan 10, and have been getting more expensive linearly since then? I doubt it.
Ask HN: Should I build this?
I want to build a service called "Treefort", "Speakeasy", "Fight Club", or perhaps "Clique". It would be a social network with emphasis on group communication and privacy.

Sweet spots for the service include teenagers with nosy parents, gay people who want to show different sides of their personality to different groups, and people who just don't like the public-default models of the current social networks.

While the basic features would be the standard status updates and photos, I think there are some interesting points of differentiation:

1) No one knows whether you have an account. There is no people search. If I want to be friends with "Joe User", I type it in, and get the response "If Joe is using Speakeasy, and wants to be friends, we'll let you know."

2) Groups/friendlists/gangs are 1st-class citizens. When you accept a friend request, you put the user in a group. When you send a status update, you send it to a group.

3) Group management is made easy via good ui, intelligent defaults, and machine learning. The dropdown box to select the group receiving your status update defaults to your most recently messaged group. The dropdown box that asks you which group to put a new friend in defaults to the group with the most social-graph overlap with the new user. You may occasionally receive intelligent suggestions to add a user to a group. Imagine that you are using Speakeasy to share class notes in college, and one of your friends is taking the class, but isn't in your group. If enough other people in your group added him, then you might receive the suggestion that you should allow him in.

This service would be in many ways more email-like than social-network. It's something I wish existed. I'm not entirely sure how much money there is in this, but I think the overhead of running it would be relatively low.

Thoughts?
Most airlines I know of allow a carry-on and one personal item (purse, laptop bag, backpack). Where do you live that you can only bring one item with you on the plane?
That's still way too much stuff. Maybe this is a girl thing. A man might take one suit in addition to the one he's wearing, and just a fresh shirt and underwear per day, a pair of jeans and a couple of t-shirts. Once you've done it a few times, you realize how much stuff you don't need to carry, the hotel will have it. Or you don't need a wide selection of clothes if you know what you're going to wear. If it's business, suits, if it's a vacation, no-one's going to care if you wear the same board shorts or whatever twice. Or all week, if you're going in the sea every day. Check the weather forecast before you go (and if you get it really wrong, hell, you can just buy something).
Thx. Glad u like it. We are working hard on the recommendation engine.
Meetup.com has some of this though may not allow totally secret/private groups/events.
Thanks for the comments. It looks like Node.net should port to any of those Javascript implementations. The basic requirements are the ability to use functions as delegates for callbacks from the host platform and thread sync primitives to serialize access to the event dispatch queue.
The Castle Fight crashiness appears to be the result of a file format hack the map author's used to "protect" the map -- custom unprotected versions work fine.
I use rackspace hosted email as well. Very happy with it.
Can anyone provide context for this? I know this is the presidential plane crash, but what am I supposed to understand from looking at this? Some conspiracy to kill survivors?
I'm having the same problem. I searched the code for "semantic-load-enable-code-helpers" and it isn't in any of the .el files in any of the directories under "lisp". Would be nice to try this out, but I'm too busy to get this going today (I'd love it if someone else solves this tho :-)
My problem is shaving cream in the no liquids-gels-aerosols world. As far as I know you can't get it in a small enough package to be allowed through security.

I realise that theoretically I could buy an electric razor, though they don't work well on my beard. Alternatively I could just buy a new can of shaving cream every time I travel.
Exactly.

I don't think I need 3 pairs of shoes even when I'm at home.
scammy =/ innovative
Can I please request lots of videos and someone posting a complete account on a blog?
I suppose you could say it's 'brave', though, in the same way that trying to swindle someone and hoping they don't notice is brave.
Good review. I personally prefer the HTC keyboard. Whereas I couldn't stand typing on the Android 2.1 stock keyboard, the HTC_IME keyboard pictured is great.
Their strong usage of both Memcached and Memcachedb makes me think of my favorite 'all-in-one' solution: Redis.
There is quite a long discussion about it here: http://en.wikipedia.org/wiki/Talk:2010_Polish_Air_Force_Tu-1...

There is a lot of healthy skepticism and some debunking of wrong translations
In which case this would be bad luck for any individual who happened to have their life's savings in Accenture stock with a stop-loss order placed on it. I doubt this covers too many individual investors, though.
Quite the opposite. If you did not hold the shares past that window, then you'll end up in a short position.
That's illogical. We could design a system that works exactly like brakes do now — never engaging on their own — and it would get an enormous number of false negatives. By your logic, it probably gets a lot of false positives too.

In general, false negatives aren't a sign that the system is buggy, but that a heuristic is tuned to avoid false positives.

Also, this wasn't a false negative — the system wasn't turned on in the first place.
I'd love to see a wiki aimed at HN newcomers, with a page on frequent topics and a list of the most relevant threads on that topic. Of course, in order for such a resource to really be useful, newcomers would have to be made aware of it. That is, it would have to become "official" and be linked to prominently from HN.
You want this: http://www.shave.com/shave/?tab=oil
Indeed: http://www.youtube.com/watch?v=KWaLPqrZI1E
Try shaving oil. It's fantastic, and a 1.5 oz. bottle is enough for near 100 shaves.

Alternatively, a bar of shaving soap and a brush work well. More space than the oil though.
Found in a related video:

http://www.youtube.com/watch?v=3ReZ0C_UF-8&feature=relat...

This is why an F-150 is still a pretty good place to be in a real-world accident where you're more likely to hit another car rather than a thick concrete wall. Conservation of momentum says that when a big heavy thing meets a much smaller thing the big heavy thing comes off looking much better.
The UK. Where, after the liquid bombing thing, they not only brought in the 3 x 100ml of liquid rule, they insisted that passengers only carry ONE bag through security (because ramping up to actually check each bag properly was taking too long).

This isn't the airlines, it's the government. There is no work-around and it's a rule they've relaxed only at a handful of airports with additional screening equipment. Beware -- if you visit the UK, you may well only be allowed to take a single carry-on item when you fly out again!
Journalism has different rules. But in general in the US the law deals with "Expectations of Privacy." If the party in the picture has a reasonable expectation of privacy then yes, consent would be required.
If I had a thick beard, I'd just grow it. Since I don't, I don't actually need shaving cream. I gave up on shaving cream around age 17 or so and haven't looked back.
I love http://www.onebag.com the site design may be a bit outdated, but e information is great. I especially recommend reading the bit on packing clothes. I always use his method of "bundle wrapping".
Presumably you put it under CC-BY-SA, not one of the noncommercial-use-only CC licenses, or Wikipedia wouldn't be able to use it. The hotel could have used your photo legally in their ad if they had properly attributed you.

However, under the Federal Circuit precedent set by Jacobsen v. Katzer, I think they're still liable for copyright infringement, and you're still entitled to monetary damages.
> I'm always amazed by how bad most people are at packing.

It is truly extraordinary. I frequently do two week trips overseas (e.g. connecting two conferences with a weekend in the mountains) with a 30 liter backpack (no separate laptop bag). I've also done 4-day technical alpine climbs with a 26 liter pack. And somehow people need 4 times that much for a week in a different city. I blame the wheeled bags, they encourage people to bring more than they can comfortably carry and produce kinematic waves at every transition (stairs, escalators, curbs).
COS - The C Object System (ObjC + CLOS inspired)
Your contrast between "software engineer" in one sentence and "programmer" in the next is interesting. Did you mean to imply that there really is only one set of characteristics that define a great programmer, or were you assuming that software engineers and programmers are the same thing? (I disagree in either case, but I'm not sure how to parse your post to debate the point you intended to make.)
Right, but then you still have all of your data off somewhere in someone else's control. It'd possibly even be worse than Facebook, because an open "provider" that doesn't do anything except host data for Facebook & co. wouldn't be bringing any revenue, and thus would be tempted just to sell all the data you upload.

The point shouldn't be to cut out Facebook, it should be to keep the user in complete control of their data. You can transfer control to an arbitrary entity but what are they going to do to make money, and are they going to become corrupt or not? And if you asked yourself the same thing about Zuckerberg the day after Thefacebook went online, what would your answer be?
Alternatively this may be a prototype with airbags disabled for some reason. Frinstance if you're going to remote-control a car you'd probably wind up fitting something over the steering wheel, so you'd probably disable the airbags for that.
Three bathing suits...three nightgowns! I can pack for 10 days in a small backpack if I don't need smart clothes.
All cars in recent years are designed to crumple well under offset frontal crashes. It's sort of an industry standard.

Even big old Volvos don't fair well in an offset with a tiny new Renault:

http://www.youtube.com/watch?v=qBDyeWofcLY
For Ubuntu, With Love.
Get some old style shaving soap - it is neither a liquid, nor a gel nor an aerosol and it would properly be great for your beard.

Of course then you have to get a straight razor through airport security.