Become a fan of Slashdot on Facebook


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Comment Re:4k? (Score 1) 159

There are two ways a game can respond to screen resoloution changes. One is to keep the view the same but draw it in more detail. That works pretty well for realtime-rended 3D games but for 2D tile based games like starcraft it would mean having extra copies of all the artwork or using ugly scaling.

The other is to give players with higher resolution screens more stuff on-screen at once (like how most desktop environments worked). The difficult thing with that is especially in a combat-focussed game seeing more at once gives you an obvious advantage.

Or they can just choose to design for a fixed resolution. Starcraft was fixed 640x480.

Comment Re:It's not ideas. (Score 1) 542

Portal itself was a great little game but afaict it didn't try to be a standalone "AAA" title. It was an "extra" bundled in as part of the orange box. It was relatively short, had little in the way of graphics (indoor pristine test chambers are real simple from a graphics perspective), little in the way of story,

It was only four years later after the original had proven itself that they released the sequel which extended the concept into a much larger and more varied game.

Comment Re:"...disabled by default." (Score 1) 307

On skylake you already need either a PS2 keyboard or a modified windows DVD to install win7 because intel changed how the USB controller worked. The new controller needs XHCI drivers to work at all (while the old controller only needed them to get USB3 speeds).

Comment Re:Uber may be in trouble but no self driving cars (Score 1) 334

Once there is self driving cars, the taxis will be as cheap as private cars on per mile basis when averaged over entire year.

I have my doubts.

Firstly there is the question of how much the self-driving equipment will cost, both initially and in maintiance. My feeling is that to make self-driving cars safe will require a far more rigourous approach to maintiance than cars get today.

Secondly people respect their own stuff more than they respect other people's stuff and tolerate thier own filth better than they tolerate other people's filth. So I would expext taxis even self driving ones to need more cleaning and interior maintaince than owned cars.

Thirdly the taxis even if self-driving will have to clock up significant empty milage getting from one job to the next.

Fourthly the lifetime of a car is limited by miles as well as years.

I think there is likely to be a transition but I expect it to be a slow one. People who already own and drive cars will continue to do so but people who don't currentlyhave a driving license will be less likely to go out and get a license and car. At least where I live starting to drive is considerablly more expensive then continuing to drive.

Comment Re:Using SHA-1 in this day and age is just lazy (Score 1) 203

As far as I can tell, this is a non-cryptographic use of hashing.

Git uses sha1 hashes to identify everything.

A (possiblly signed) tag references a commit by hash
A commit references a tree by hash
A tree references a list of files and subtrees by hash

If a commit you fetch references hashes you already have the files for in your local git tree they will not be re-fetched, the existing ones will simply be used.

The whole point of git is to be distributed, so it should be safe to fetch commits from untrusted sources, inspect them and throw them away without worrying that they will change the meaning of commits you later fetch from trusted sources. It should be safe to download commits over an insecure connection and then verify the commit hash (either by a signed tag or by checking out of band) to ensure that the commit hasn't been tampered with.

The latter part of linus's mail is quite a well-reasoned argument as to why the current attack on SHA1 isn't too big a deal for source code repositories.

If a "distinct chosen prefix" collision attack shows up then the risk gets much higher. For MD5 it took about 2 years to go from a basic collision attack to a distinct chosen prefix one.

Comment Re:For the US, not for a political party (Score 1) 895

googling " const int one = 65536" turns up some C sharp graphics code as the first result, c sharp has a 32-bit int so it's not an overflow.

It looks to me like the constant is being used to implement 16.16 fixed point maths inside a 32-bit int. One of those things that makes you go wtf at first but makes perfect sense when you understand it in context.

Comment Re:zerocoin? What is that? (Score 1) 88

The absoloute value of one "coin" is not a useful comparision. It doesn't really matter whether you have lots of "coins" with a low value per coin or fewer with a higher value per coin.

More interesting as a measure of the relative importance of cryptocurrencies is the "market cap". The value per coin times the number of coins in circulation.

By that measure dogecoin's significance is about 0.1% of bitcoin's

Comment Re:Show me the code. (Score 1) 88

A one character bug? Really?

"one character typo" can cover a wide range of things. Using = instead of == is probablly the most famous but also generally one of the easiest to spot (modern compilers usually have a warning for it). Using the wrong variable is a big one (not helped by the fact that mathematicians love one-character variable names). Using the wrong logical or comparision operator can be another.

Unfortunately TFA doesn't say what the "one character typo" was and looking at their github I don't see any one character typos being fixed recently. I do however see a "two character" typo being fixed though ("||" vs "&&"). I also see some == being change to >= but I *think* that is just a case of making a test more paranoid.

What about the tests?

It takes extreme discipline to carefully create test cases that cover every failure case. All too often people only test that the normal case works as it should and fail to test the error handling.

Comment Re:Until (Score 1) 374

No, with std:: string each time you write something like "a =b" the compiler has to either mess with reference counts (most implementations of c++03 and earlier) or copy all the data (c++11 and later). You can work around that by using references but then you lose the safety advantages of automatic memory management and add an extra level of indirection to accesses .

Slashdot Top Deals

Every little picofarad has a nanohenry all its own. -- Don Vonada