smhinsey

That's interesting, I didn't get the WWAN option so it's probably just dead space. Thanks!

I have had 3 other ThinkPad T models and I actually kind of prefer the keyboard. It's pretty subjective either way.

I just recently got an x230 with the IPS option. The display is great and really comparable to my 11'' Air except for the coating. Overall, I love the machine. It lacks the size advantage of the Air (they are generally similar, but the x230 is several times thicker) but I was able to swap out the drive with a 256 SSD and upgrade the RAM to 16 GB which has left me with a machine that is way more capable than I anticipated. I also am really surprised by how much I like the keyboard.

That said, the ultrabook market is still in a weird state. I looked at all of the major vendors and no one really had the ideal combination of components yet. Once you can get the x230 with higher res display and a multi-core CPU, it'll be an ideal machine.

It tends to naturally revert to gchat or aim, which are not awful, but they seem to make it easier to accidentally exclude people.

I set Grove up for my distributed team but it didn't stick. I still think team-level chat is a problem worth solving, but nothing I've tried has gotten any real traction.

I think the reason this happens is because no matter what people say, the idea that if you can't finish a story within a sprint it will simply slide into the next one is anathema.

People spend more time on estimation when the consequences of mistakes are higher. If you can't realize that a story is larger than you thought and reprioritize mid-sprint without it being equivalent to missing a deadline in your old model, it's not going to work. In my experience this is the key failure mode of scrum.

I think part of this is also that no one really wants to admit that a lot of content that goes out under a given columnist's name is not actually written by them. The byline is more about branding than authorship these days.

I haven't installed it yet, but I am pretty sure I read that this was something you could disable.

I can't wait until the page title trick makes its way to the next revision of the Azure Management Portal.

ClickPass is effectively this, although they were OpenID. I don't think it worked out too well for them but it was several years ago, so they may've been too far ahead of the curve. HN used to use them as a sign in provider.

I was really hoping for a Hollow Mars diagram when I saw that "speculation" link.

Alaska is also the location of a whole lot of cold war military installations. It was an anchor of Strategic Air Command during its heydey. It wouldn't surprise me if some of this redundancy was for weapons control systems.

A fairly large number of them in my area (I'd say like 80%+) are associated with things like schools or hospitals, so I bet a lot of them are going to stick around.

It's still sad though. Weather.com doesn't have anything that works as well as the WunderMap, and certainly nothing I can leave running 24/7 in a browser unless I want to restart it every few hours.

It might be better to say that it's free of control flow structures[0]. This is my preferred approach but it can definitely take some adaptation if you're used to doing a lot more in your views.

[0] I wonder if partials count? I don't know that all of the moustache derivatives have them anyway.

First of all, I'm not an insider, I'm just a weather nerd who came across this story awhile back and was really curious about it so I did some research.

That said, my understanding is that they are basically going towards a widespread mixed-mode setup now, but they haven't yet for historical and budgetary reasons.

The system they'll be replacing is largely the result of tragedies like the Andrea Doria and countless less famous weather-related accidents that were caused by faulty communication of important weather bulletins. Because of this there was a pretty significant investment in designing and deploying a really robust system, and it was rolled out extremely widely, including far flung and remote weather stations, and was adopted elsewhere as a standard as well.

Fast forward to today and the aging system does the job but is in a rather precarious state because everyone who designed and built it is long dead, and in the face of shrinking budgets, like the NYC subway system and the national air traffic control systems, for most of its history it was maintained just enough to keep pace but rarely upgraded.

Only relatively recently has there been momentum behind modernization and the big driver behind that has been the increasingly deadly tornado seasons we've been experiencing over the past decade or so. The need to be able to push out more geographically precise bulletins as well as to make them more impactful (they recently started using phrases like "you will die if you do not seek shelter" in select tornado alley locations) in the hope of decreasing casualties has been a major driver behind this change.

The ALL CAPS nature of weather alerts is due to the constraints of a very old but extremely widely deployed alert broadcast system. In the US, at least, the NWS is upgrading their alert broadcast systems so that this will no longer be the case, but this will definitely not happen quickly.

Ah, you know what, I just figured out what the issue was. I was using the "metal" TST skin and when I switched it to another one, the 150px-tall-tab problem went away.

It's purely the visual component I mentioned, the functionality seems to be okay, although it's reported as broken in the add-on manager. I have the tab bar docked on the left vertically and the tabs are ~3x taller than they should be.

I'm the same way about switching to Chrome, by the way. I would love to but I just can't picture life without TST after so many years.

It seems to have subtly broken TreeStyleTabs on OS X, which is a shame because I am addicted to it, but at least it's still usable (the tabs take up ~150 pixels of vertical space). Hopefully this will resolve itself with a TST update.

That said, wow, the OS X improvements are huge. Previously I could only force quit if I wanted to shut down to free memory or whatever, but now it closes normally. I'm also not seeing the same kind of memory usage, but it's early so I'm not sure how long that will last.

Homesite was the first thing I thought of, which was definitely one of those trips down memory lane that leaves you thinking "wow, that was how long ago?!"

I think the fact that this system doesn't take account age into account is problematic. My PayPal account is who knows how old, but somewhere in the neighborhood of 10 years. I'm just now hitting that limit after years and years of small transactions. This is probably going to make me stop using them because I don't trust them with my bank account and I don't need any credit. This seems like a really stupid way to lose a long time customer.

To me, it's all about the composition of the asteroid that you choose to mine.

In these early days, I think we'll probably be more focused on targets of opportunity, but once the technology base exists to be picky, if you could locate a body full of precious metals, say gold and platinum, it could easily dwarf the earthbound supply.

I think the most interesting opportunities lie not with traditional methods of exploiting these materials, but with the methods we will discover once previously rare materials become abundant and cheap.

Of course, devaluing gold to the point of aluminum is going to cause political upheaval and that will have to be dealt with, and while this conjures images of chaos and serious trouble, it doesn't seem like all that big of a deal compared to what will happen when a private entity starts talking about bringing a dinosaur-killer-sized body near the earth.

It is also a good example of cooperation. The Huygens probe was done by the ESA.

I'm sure there is a whole huge debate here that I'm unaware of, but it seems like a largely aesthetic choice to me, and on that basis, I find it really jarring as someone who is not an everyday JS author.

Funny, I was just checking out Derby and noticed that their examples follow this style.

I think the project itself just hit a nerve. Twitter has released plenty of code in the past that hasn't become this popular. Personally, Bootstrap fills a very valuable niche in my work, and a large part of that had to do with the polish and completeness it had out of the gate (you can use it as a self-documenting style guide, e.g.), so maybe this can be ascribed to Twitter in terms of resources. Despite this, I think it's more "right time, right place" than anything else here.

I have a G2, which has a pretty decent physical keyboard as well as Swype. I can see how you might get pretty quick with Swype, but if you're a good typist, I think the keyboard wins out every time. If you are used to it, you get a sort of psuedo-touch typing ability going with it that I don't think you can yet duplicate on a soft keyboard.

I think you got the cooling problems backwards. In vacuum it's a lot harder to get rid of excess heat than it is inside an atmosphere. Latency might be a bit of a bummer.

There is actually a similar FiOS xbox app as well. I am not familiar enough to say if it gets preferential treatment on the network, but you can stream a subset of live TV channels and use it as an alternative to the cable box, although I don't think it has had enough polish to inspire a full time switch.

I think when done right (a subjective measurement, to be sure) the only URI you care about for a RESTful API is the root, because the API's resources are defined, along with how they can be manipulated, in the root response or can be transitioned to from there in some way that is defined there.