Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Comment Re:No cashier needed (Score 2) 145

But then I wouldn't get to chat to the attractive cashier while they took my order. Seriously though, I can see the advantage if you're getting a coffee to go and can simply go straight to the collection point, but if I'm going to sit down its nice to have someone say hello and smile as you give your order, ask how you are and comment on the weather.

Comment Re:Just because of speed? (Score 1) 330

It's not the rapid release cycle by itself that bothers me - if everything continued working I wouldn't care if there was a weekly update. As I said in my post it's the loss of usability that concerns me most - plugins not working, memory problems and the ever changing layout for no obvious benefit. Although I've only used Chrome intermittently since its first public betas it's UI feels far more stable and consistent than FF. And yes FF is becoming more Chrome-like, but not in a good way.

Comment Re:Just because of speed? (Score 0, Troll) 330

So true. I switched to Chrome at the weekend for exactly this reason. I can't remember when JS or render speed were an issue for me, but useability just keeps going down with FF.

Let's stop with the posts anouncing the latest release and wake me up when the Firefox devs are listening to their users once more.

Submission + - Global Software Development Over Unreliable Networ

AmIAnAi writes: We have two software teams on different continents developing separate products from a common code base. Currently each team has a their own copy of the source code and use CVS for change tracking. These repositories are infrequently synchronised by exchanging copies of the source.

We would like to use a common source repository but network latency and low bandwidth through the VPN makes it impractical to share a CVS repository.

What solutions have others devised for distributed development over unreliable networks. Paying for a premium connection with reduced latency is not an option and the source is owned by a third party, so security is paramount.

Comment Re:This isn't a Mozilla problem... (Score 5, Insightful) 683

The problem is with Mozilla, and every other open source developer who thinks their way is best and to hell with the users and add-on developers. An established user base requires stability and consistency, not this months idea of what a web browser should look like. Sure, let users customize and tweak if they want to, but leave the underlying experience the same.

The Slashdot crowd may be vocal and anti the new Firefox, but the Mozilla developers need to sit up and take note. The vast majority of their current user base don't care enough to complain - they just switched to Chrome or IE. A significant number of friends and family who I converted to Firefox over the years have switched to Chrome in the past six months.

Comment Re:Comments on the browser itself? (Score 1) 415

Maybe I missed the big whooshing sound as your comment went over my head, but I suspect there wasn't one. If "everyone bitched" then the developers got it wrong. This isn't some obscure utility that is put out by a tiny dev team, this is a workhorse tool and people expect to be able to update and continue working as before - nothing broken, nothing missing and certainly no requirement to go reading through documentation to get back to where they were 5 minutes earlier. If the Firefox dev team were saying 'here's something we wrote for ourselves, use it if you like' then sure, they're free to make whatever changes they like, but when they start evangelising and actively courting users for their product they need to stop listening to their egos and listen to the end users.

Slashdot Top Deals

2.4 statute miles of surgical tubing at Yale U. = 1 I.V.League

Working...