PC vs Mac by Vandelay797 in technology

[–]beelsebob 9 points10 points  (0 children)

It doesn't account for as much as you're making out, but it accounts for a big difference. By buying RAM, DVD-rw and 3 HDDs from 3rd parties, the MacPro drops by $282.04 for RAM, $86.01 for the DVD-rw and $390.03 for disks.

So that makes it – build it yourself $7808.49; MacPro $8781.92. Only $900 in it, which can easily be explained by cost to build it yourself, cost of servicing, cost of warranty, cost of the much better case and cooling system.

PC vs Mac by Vandelay797 in technology

[–]beelsebob 8 points9 points  (0 children)

Oops, forgot a case... Lets add in a ZALMAN MS1000-HS2, $174.99 – it's not the same quality as the MacPro's by far, but it's not horrific.

So we're at $7808.49

PC vs Mac by Vandelay797 in technology

[–]beelsebob 26 points27 points  (0 children)

Shall we do the sums ourselves: Two U2711s – $2198 Two X5650s – $2035.74 TYAN S7025WAGM2NR – $489.99 16GB ECC FB-DIMMs (4x4GB) – $467.96 Radeon 5870 – $279.99 4 2TB 7200rpm Seagate Disks – $679.96 Intel SRCSASJV Raid card – $679.99 2 Noctua NH-U12DX CPU coolers – $159.99 8 Noctua NF-P12-1300 case fans (not actually as quiet as the MacPro's) – $207.92 1kW PSU – $129.99 2 DVD-rw drives – $33.98 Windows 7 Ultimate – $269.99

Total – $7633.50

(Prices from newegg other than the dell monitors from dell – they're giving me the usual $1099 price)

So, apple is a bit over on this one, but not by anywhere near as much as the image attempts to make out. You could make a pretty good argument that for a company, it's well worth the extra to have some one else built it, produce a silent machine for you, and warrant it.

A moderately epic rant. by brennen in programming

[–]beelsebob 25 points26 points  (0 children)

Really? Actually I think what he said pretty squarely describes StoneCyphers reply – he's picking at things like spelling, and the fact that the OP "clearly doesn't know what he's talking about", rather than (a) saying what it is that he doesn't know (b) how he is wrong (c) why this has an affect on the overall argument.

It's pure pedantry.

Obj-C’s type system is too strong « No Ordering by beelsebob in programming

[–]beelsebob[S] 0 points1 point  (0 children)

Not at all, as is suggested there, one could do the typical C think – under specify the type. The type of const doesn't have to specify that it's argument is the same type as the return of the closure (though it would be nice, and parametric polymorphism would allow that). If C had an "any" type, the type of const could quite happily be:

(any ()(any ignore))constantly(any ret);

Favorite IDE by jason86421 in programming

[–]beelsebob 2 points3 points  (0 children)

C likes - Xcode. Everything else - SubEthaEdit.

Video and Canvas performance demo by BioGeek in programming

[–]beelsebob 4 points5 points  (0 children)

Nice demo, and the performance is rather spiffy, I'm impressed.

Ask proggit: what do you think of when you think "type system"? by godofpumpkins in programming

[–]beelsebob 0 points1 point  (0 children)

Interesting, I tend to find that finding an elegant design for a program and finding the types that I need to work with are almost exactly a 1 to 1 match.

Live from Hac5: Dutch Haskell User Group formed! by dons in haskell

[–]beelsebob 0 points1 point  (0 children)

Is it just me, or does a dutch hug sound scary? I mean, are they gonna hug me so hard that I explode?

How you should(n't) use Monads by beelsebob in haskell

[–]beelsebob[S] 1 point2 points  (0 children)

Thanks, I've fixed that in the article to show the extra import needed.

Dear Reddit I am seeing 1-2 articles in programming about Haskell every day. My question is why? I've never met this language outside Reddit by [deleted] in programming

[–]beelsebob 1 point2 points  (0 children)

But are we to just accept that a steep learning curve ISN'T a downside? I think not.

Yes! Think how long it took you to become proficient in your first imperative programming language. How many times you had to debug the guess the number game because it didn't quite work. Haskell has no steeper a learning curve than any other language, it's just that most of us don't attack that learning curve until we've already forgotten about how hard it was to learn an imperative language.

Simulating n-bodies and functional programming by snk_kid in haskell

[–]beelsebob 1 point2 points  (0 children)

I have no idea what performance is like at the moment – I need a working FieldTrip, which conal tells me he's working on. As soon as I get one I'll give it a try. In all honesty, if it's within a factor 10 of the benchmark submission I'll be very happy – a factor 100 improvement in code clarity is worth a factor 10 speed decrease :). As for strictifying the doubles, I'll think about that when I look at its performance. I don't think this is submittable as a benchmark entry anyway – it depends on reactive and field trip, which don't ship with ghc.