GravityWell

Thank goodness! Looking forward to the Pluto close-ups, which will hopefully include the dark spots.

Care to share some examples of dark energy evidence? If the evidence is a measurement of expansion, then it doesn't necessarily support the existence of dark energy.

> The number of compiler bugs is a bit scary.

I see similar lists for GCC when a branch is underway. I'm actually impressed with the number of active contributors, and I find the design very compelling. I'll be keeping an eye on this project.

This is extraordinarily useful and unique. My compliments to Backblaze for making this available. This is the type of empirical data I would love to have for as many things as possible: SSDs, monitors, TVs, kitchen appliances, tablets, cars, etc.

I just fired up a NodejsConsoleApp project in VS 2013, created a few simple functions, set a breakpoint, and started stepping through. To be fair, I assumed Edit and Continue would work like it works for other .Net or Native projects, or like the old VB or even VBA.

1) "Set Next Statement" doesn't work, which is a pretty big part of E&C

2) I could change code and literals without stopping and restarting the debugging session. Each change causes the current statement to jump to the top of the current function, or to the first line if modifying code outside of any function. Local variables are reset, but globals retain their state.

3) Interestingly, I could change code in a function that does not have the focus, and nothing is reset, then step into that function.

I remember seeing something similar when V8 was being demoed and showed a "live edit" capability, so I guess NTVS has similar functionality.

It short, it sort of works, but it's not the same as E&C for .Net (C# or VB), C/C++ native code, or Office VBA.

Note for those visiting the thread, I found one of the big things with this release is the support for Edit & Continue:

http://nodejstools.codeplex.com/releases/view/104141

https://www.youtube.com/watch?v=ZAroJmb6XY4

It was in the original title, but has been edited out.

I'm hardly an MS fanboy, and I'm not sure what announcements you're referring to, but it's hard for me to see a downside to this.

I had to see it to believe it, but here it is. https://www.youtube.com/watch?v=ZAroJmb6XY4

Interesting move by Valve, and another positive step in support of Linux.

The fact that #1 and #2 are Chromebooks is worth mentioning. I found that surprising.

One of the mysteries of HN and how stories do and don't make it to the top. It seems to me there is more attention to tabloid type stories lately.

From the article:

"..It turns out that far from being a minor initiative to keep MariaDB alive, Google is actively patching and upgrading MariaDB 10.0 to be fit enough so that Google can migrate all of its thousand-plus MySQL instances onto the technology."

It doesn't. In this context, "...that I believe all living things", the words "I believe" can be directly converted to "I have faith without any evidence".

Aptly named or not, a google search for sigil shows the epub editor as the first result. The project has been around a long time: https://code.google.com/p/sigil/

"Navigant Research forecasts that autonomous vehicles will gradually gain traction in the market over the coming two decades and by 2035, sales of autonomous vehicles will reach 95.4 million annually, representing 75% of all light-duty vehicle sales."

Not sure what the objective is, but using the "before" example 475kb lena pic, a subsequent jpg at 61k looks very close to the original, and much better than the 61k blurred png.

There is a reason why jpg has survived the test of time. It delivers a good balance of quality, performance, and is well supported. Challengers like JPEG 2000 have not gained much traction because jpg gets the job done. http://en.wikipedia.org/wiki/JPEG_2000

I'm not sure why MySQL seems to have received more attention over the years. PostgreSQL might be more robust.

One point about PostgreSQL that bothered me was the apparent lack of case insensitive collation. Where SQL Server, Oracle, and MySQL default to case insensitive, PostgreSQL defaults to case sensitive, and there was no built in way to change this, so you have to do things like "WHERE LOWER(namecol) = 'jdoe'" to work around it. At least that was the situation last time I checked.