Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×

Comment Re:The Stupidity, It Hurts! (Score 2) 1006

I'll just leave you with this clue though. People keep money in banks. Govt could theoretically seize bank assets (look at Cyprus, doing it LEGALLY). Even if they needed cash - which they wouldn't - they could get it at any time. I'm sure you still won't understand what I'm saying, but at least I tried with you. That's all I can do.

Comment Re:The Stupidity, It Hurts! (Score 2) 1006

Sigh. Yes you're right. At some point a tank driver would find his credit card being declined at Shell petrol station, turn round to the rest of the army dudes and say "well that's it I guess guys, time to give up and go home." - The End.

I'm going to leave you alone now; you're giving me a headache.

Comment Re:The Stupidity, It Hurts! (Score 1) 1006

You were talking about funding. I replied specifically about the fact that funding is irrelevant in a war situation. If people want ammo, rations, or fuel to avoid being killed, then they'll take it by force. I didn't mention anything about motivation or allegiance, you're just trying to change the tune to dodge the issue.

Comment Re:The Apple Monoculture: (Score 4, Informative) 272

I own a Nexus 7, Nexus 10 and the latest iPad (also owned previous iPads, iPhones, and numerous other Android phones/tablets). The build quality and battery life of the iPad is certainly higher than the Nexus devices. It's pretty obvious if you've used both extensively. I've also had more glitches on the Android devices (e.g. current Google Nexus phone not ringing when people call after it's been running for a week or so, sometimes staying on lock screen when a call comes in, occasional UI quirks). Also the iPad mail app is much better than the Android offerings. Nexus 7 has terrible sound quality through external speaker - not a show stopper, but really should be addressed.

That said, I much prefer using the Android devices for day to day use. I also spend far more time developing for Android than iOS (in fact let my iOS dev license expire now) and I recommend Android to clients for the type of work I do - my apps are generally not available to the public. I hate being tethered to iTunes, forced to distribute apps via the Apple iTunes store, and Apples general lack of innovation or improvement (not adopting NFC for example).

So that's my experience; day to day I carry a Nexus 7 around with me, along with my Nexus phone. If I'm anticipating doing a lot of email, I'll either take my laptop, or the iPad2 instead. Im not a fanboi of either camp - just use what I think is most suitable.

Comment Re:I doubt it (Score 4, Interesting) 393

I would imagine that people will also look at the other options before buying one of these consoles. Sony and MS (and Nintendo I guess) are no longer the only games in town. Alongside the raft of Android kit that's in the pipeline people obviously have their phones and tablets, and PCs have never been stronger (and in fact PC players buy as many games as either XBox or PS3 players, no matter what Bungie may want you to believe.)

Hopefully this will finally wake people up to the fact that consoles are NOT a good buy, unless you really don't own a PC, and want to game with your thumbs (which I consider to be as effective as playing the piano in oven gloves.)

Comment Re:I can say, after having upgraded to mountain li (Score 1) 213

I think it's a bit unfair to bash it and call it crap because you haven't spent any time using it. It actually has a very good console, profiler and step-through debugger that's at least as good as Firebug, or the Web Developer plug-in for FF. Personally I develop with Firefox or Chrome when I'm on web projects, but I have taken the time to find my way around IE's debugging tools too.

Comment Re:Web developers hate IE (Score 1) 213

I thought I was pretty much opposing your point. If you have to do more work for a client, charge them for it. It's like any piece of software development; agreeing the deployment platform(s) is a fundamental part of the technical planning stage. If I'm working on a mobile app, I need to know whether it's Android or iOS (or both), for embedded work I need to know the hardware platforms. For web development, the server architecture and browser/device support are pretty much top of the list. I always try to find out this information as early as possible, since IE6 support can sometimes be trivial if the design of the site isn't too outrageous and the client has indicated IE6 might be on the agenda. It's always an extra cost though; and is something I'll always make clear before any development takes place. As you no doubt know, it's far easier to work on templates and structure your CSS and markup if you know you need IE6 support, than it is to try to retrofit it later!

Some clients will be aware of the additional effort required, and make a decision, others require some explanation (I will generally suggest they check any existing stats if it's a rebuild, to see if it's worthwhile). It's hard to overstress how important it is to nail this down early; preferrably in a written contract that's signed off before development begins. It protects both you and the client, as you both know where you stand and there's no "oh, I thought it would work in IE6?!" confusion at the end that leads to a lot of wasted time, or aggravation. Usually at the developer's cost.

I've been quoting separately for IE6 for at least 5 years, and also IE7 for the last few. Of course, the additional cost is growing higher. Browsers have improved, while IE6 has not, and so the gap has in some ways widened. I'm finding that far less projects these days require IE6 support (of course, I do still check the sites are functional, but any styling issues are irrelevant.)

Do want to sound like I'm preaching, just been through it for so many years that this stuff is sort of automatic now!

Comment Re:I can say, after having upgraded to mountain li (Score 1) 213

Very true - in fact IE4 was actually way more stable than NS4, and IE5 was a revelation when it came out. It wasn't that MS just used underhand practices (though they certainly did) but their browsers just had better engines. NS5 was terrible. they attempted to correct the biggest problem with NS4 which was that resizing it with JS and dynamic content would either crash the browser completely, or kill the JS engine and screw up the layout (unless you used the proprietary tag). IE4 at the time had no problem with reflow, although it was a bit slower. NS5 though was ridiculously slow, incompatible with NS4, and had so many bugs that it was ludicrous to recommend anyone use it. Netscape basically just let it stagnate.

Slashdot Top Deals

A morsel of genuine history is a thing so rare as to be always valuable. -- Thomas Jefferson

Working...