Slashdot is powered by your submissions, so send in your scoop


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

Comment Re:Why the animosity? (Score -1, Flamebait) 202

I used to use amigas since 1989, and develop on them (I even released a few things on aminet and participated in community events and such), and to my great shame it took me until 2001 to come to my sense and realize that amiga and its community are a pointless waste of time.

People who still haven't realized that in the year of our lord 2012? They are fucking morons, and deserve all the mockery they receive.

Comment Re:Great! (Score 1) 84

I heard of a great website to find such things easily:

But basically they are filters that makes contemporary shitty photos taken by smartphones look like 70s shitty photos taken by polaroids, which are considered not shitty anymore because well I don't know, hipsters I guess

Comment Re:C++ has had its day (Score 1) 375

If C# is more cumbersome, then perhaps there's a way to make it less so while keeping flexibility and power.

I only can see two clear advantages to c# over c++: garbage collection and reflection. Everything else boils down to syntactic preferences or minor features. And there's a lot of useful things that c# is missing compared to c++.

I'm sure in time both things will make their way into C++ in a way or another (garbage collection is half-way there).

I don't think that D is a good answer to the shortcomings of C++. I'm not a fan of the "let's add in everything and the kitchen sink" approach.

Comment Re:C++ has had its day (Score 1) 375

And yet despite all the hype I find C# incredibly more cumbersome and verbose and when I'm at work I truly can't wait to get home to work on my c++ hobby project. Part of it will be in javascript too, because it is better for some of the parts of my project.

There is no such thing as an universally simpler and better language, and some of c++ features that people love to hate such as RAII, templates (not those half-assed generics that c# offers) and operator overloading permit to make some complicated things much simpler than anything you can achieve in most of those more recent languages.

Comment Re:My first question. (Score 1) 375

It's easy to wrap std::list to do that yourself. What you propose would mean that if you get a list passed from some other opaque part of the code you have no way to predict whether size will be O(1) or O(n), because it may or may not be the result of a splice.

Plus like it is now allows the spec to make simple and clear complexity promises (list::size() is O(n), splice is O(1)) without having to specify how the implementation should work in too much detail.

Comment Re:You gets what you pays for . . . (Score 1) 218

So merely opening the box should turn a brand new item into a used one? It doesn't really make sense, because for all intent and purpose it is still brand new when the store sells it to another customer.

It's covered by warranty just the same, and they make sure it's in pristine condition (except occasional mishaps like what might have happened in TFA) before repackaging it and putting it back on the shelves.

If they had to sell returned items as used, then they wouldn't bother having a return policy in the first place. This is the "price" you pay for being able to return items.

Comment Re:You gets what you pays for . . . (Score 2) 218


3 - someone brought the computer, returned it and got a refund for whatever reason, and they omitted to wipe the drive when they repackaged it.

People often don't realize that as a downside of the ability to return items, the stuff they purchase might actually have been previously sold and then returned.

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.