Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
Back for a limited time - Get 15% off sitewide on Slashdot Deals with coupon code "BLACKFRIDAY" (some exclusions apply)". ×

Comment Bad Summary (Score 1) 174

Before you start yelling OMG FASTER WHO CARES??? you might want to read the fine article:


In order to achieve our goals we decided to start with a fresh architecture that would support modern multi-threaded programs, handle debugging symbols in an efficient manner, use compiler based code knowledge and have plug-in support for functionality and extensions. Additionally we want the debugger capabilities to be available to other analysis tools, be they scripts or compiled programs, without requiring them to be GPL.

This is about better code analysis and integration, not faster debugging.

Comment Re:Won't Switch From Safari Yet (Score 1) 197

The biggest difference that I've noticed btw. Chrome and Safari is about 1GB free memory when using Chrome. No exaggeration. Safari has gotten INSANELY bloated. I've been using a Chromium nightly for about two weeks and it's like night and day. Safari is beach-balls galore, while Chromium (and now Chrome) is just speedy and compact.

I quit a Safari session I was running this morning with TWO TABS and it freed 750MB. That is so wrong.

At the source of every error which is blamed on the computer you will find at least two human errors, including the error of blaming it on the computer.