Hacker News new | past | comments | ask | show | jobs | submit | abredow's comments login

The homepage does. This link is to the release announcement.


They include an alt text on the logo image. Why not put that text into the image itself?

I see a description is in the title of the page, but that gets cut off in my browser.

"I do enjoy Pharo" is also not a very helpful quote, especially if I don't know who Kent Beck is.


What you don't know Kent Beck!! :D and yes even to me that quote is rather meaningless :P. I'll try to get the at least the ALT text updated.


We talked about this in a CPR class once. The biggest reason paramedics don't run is to avoid injury, which would obviously impede their ability to help.


That makes sense if the area around the pool is slippery. It's just that given the tremendous downside of risking the victim's life or brain damage, it seems that the paramedics wouldn't be risking much by hustling a little, rather than "walking slowly".

Unless it was really slippery, or if they thought someone was going to flip out to the point where it seriously interfered with the CPR, taking your time doesn't seem like the best thing to do for the victim.


To that I would add it gives them time to observe the scene and mentally begin work. It's not the same in seriousness, but when I was to solve an urgent IT problem I'd sit down, adjust the monitor, and roll up my sleeves before typing anything. And recently, when my baby son was falling down some stairs, I found myself calmly walking to the stairs and catching him right before he would have landed on his face. Looking back, I wondered why I didn't run since I love my son, but I realized that I might have slipped on the tile floor or dropped him in my haste.


What has happened to humans??? millions of years evolving to a truly miraculous level of efficiency and agility and we still don't think that possibly moving a little quickly to someone who's heart has stopped is a good idea? Since there were paramedics (plural) it wouldn't impede anything if they ran, and it would most certainly increase the chances of saving someone.

To me this is disgraceful, it sounds like OSHA got involved and made policy something that must surely be counter intuitive. Yes, I know the statistics of small risk- done often, but this is such a sad condition for our special to have reached when people carrying life saving equipment don't move a little faster to save someone.


There's a time to be an excited fool and leap blindly into action, and then there is a time be a professional and carefully move into place to do your work quietly and skillfully.

You wouldn't happen to use a staging server, would you?


I was going to argue the point, but I'll just point here: http://phillydan.wordpress.com/2012/03/28/good-emts-dont-run...


This was probably the best point made against running, but still...

Our professional emergency response people should be capable of hustling/running over to the people that need their help while maintaining their composure and ability to think.

It is true that exertion causes a sympathetic response, but hustling/running over to someone doesn't produce such a significant sympathetic response where people can't think straight. I know that it's inherently a stressful situation, but our professionals should be able to handle that, and the additional stress of hustling/running over is negligible.


A professional attitude and good training doesn't counter basic biological processes. What do you gain from running? A few seconds, some of which you'll have to use up recovering from the run, and irrelevant bystanders thinking you're 'doing your job'. What do you lose by running? A lot - as described in the link, which has an excellent run-down.


These guys do this often. If they're running around they will eventually slip, and who knows what equipment they'll damage on the way down. Now he can't help and the problem is much worse than if it took him an extra 10 seconds to get over there.

If you infrequently enter a situation which has a low chance of hurting you, you are probably fine. But if you frequently enter those situations then it's just a matter of time before it happens to you.


If you as a paramedic rush to every patient, before long you're going to take a pointless injury and be unable to work. For the sake of saving one patient - the trivial amount of time saved by rushing rarely affects outcomes - getting injured means that while you recover, you can no longer attend dozens of other patients at all. Hardly 'miraculous efficiency'.


It might seem like common sense for the paramedic to rush. But in practice, rushing doesn't save lives.

Rule #1 in any first-responder situation is to keep the rescuer safe. There are tons and tons of examples where rushing led to mistakes that killed the rescuer AND the patient.

So don't be upset! Moving with caution is not an OSHA rule - it is best practice learned over decades of hard-earned experience.


This looks beautiful. But I'm curious, do users no longer expect/like their platform's native dialogs for these things?


The native alert is very hard to customize and extremely bare boned.


Not to mention that the second I see a native alert my heart rate increases 10 fold.


Only thing worse are those "Are you sure you want to leave this page?" modals. Those cause me to go into fits of ctrl+w- smashing rage!!!


This is the key that I missed when I first read the article. Mixins will always be repeated when compiled. Placeholders result in combined selectors so the styles aren't repeated in the compiled CSS.

In many ways, it seems like placeholders would almost always be preferred to mixins. Though, I'm sure there are exceptions.


I have a Brother Laser that did the same thing... however, it has a setting in it's web admin called "Replace Toner" with the options of Continue or Stop. All I had to do was select "Continue" and it kept printing until the toner was actually gone. No cartridge modification required!


I think that TM probably made a big mistake by offering a free upgrade to 2.0. Especially given the apparent ambition of the rewrite.

Assuming it has some nice new stuff, I, for one, would gladly fork over more money for a 2.0 release.


Maybe it's their way of saying "sorry for the delay"? Rewarding dedicated users with a free upgrade seems like a good idea to me.


Cookies can still be read if this is set to "off."


The infinite scroll example he linked to in the presentation is very nice. Putting the max_id in the URL is a great way to save the state.

http://warpspire.com/experiments/history-api


the idea is good, but the implementation (from user perspective) is not 100% correct. try scroll somewhere, say you see text "My dad just told me I'll get my late grandfather's cornet" on top and refresh the page, you will see different stuff.


Ha, I did not know that he had a forthcoming children's book! This should be good.


This looks great. It's awesome that we can make sites like this that theoretically allow us to serve the same pages to desktop and mobile browsers. I'm curious though, is there any significant overhead to having mobile clients parse 1600+ lines of HTML, or is that a non-issue these days? Anyone have any data points on this?


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

Search: