Follow Slashdot stories on Twitter


Forgot your password?

Comment Re:Atheism isn't for sissies (Score 1) 434

Atheism offers shit for consolation on the issue of death. Friends, loved ones, family, parents, children, all of them are just gonna die and turn to dirt. That is a real shit sandwich atheism gives you right there

Atheism gives you no such thing! Though that's what many atheists happen to believe, the simple belief that no gods exist implies nothing about life after death.

Piling on dogmas like that is a sure-fire way to turn atheism in to a religion in its own right.

Comment Re:Belief in science? (Score 1) 434

This belief continues to be born out by an ever-widening body of evidence, but technically it's still just a belief (with an impressive track record).

It looks like you're justifying the uniformity of nature inductively, even though induction depends on the uniformity of nature.

You've clearly read Hume, so you know this already -- and should know better!

Comment Re:I can answer that, Alex! (Score 4, Interesting) 143

Yes, computationalism is long dead. Now, can we stop using the term AI? Keeping the term around serves only to further confuse the general public and decision-makers both public and private. I'd go as far as to say that the continued misuse of the term is precisely what has kept the cranks and con artists in business!

Comment Re:Your computer will understand you... (Score 0) 143

This old chestnut? Really? My dad used to peddle this bullshit to me when I was kid, and I didn't buy it then either.

How long has that joke been going over your head?

Gender is not a monolith, and treating it as such leads to discriminatory indictments lobbed carelessly in both directions (I'm looking at you, feminists).

Oh, you're one of those people. Why am I not surprised?

Comment Re:That explains things (Score 1) 91

It was a joke, in case you didn't notice. You felt the need to tell me how long you've been doing web development; which I immediately quoted. It's not an uncommon gag. It's particularly funny as you made an obviously absurd statement, to which one would assume that you were new and simply didn't know any better.

Without things like jquery you would be stuck with whole page refreshes just because you wanted to add a row to a form.

See how absurd that statement is? It's not even a tiny bit true! Rather than tell you what I presume you already knew, I made a lighthearted joke. Should I not have done that? Should I have just assumed you were a moron and explained in detail why your statement was foolish?

since you have just gone though all my posts replying to them all seperately

I should reply to them as a group? I don't even know what your expectations would be!

What's your objection anyway? You don't think that jQuery Mobile is too slow for real-world use? You really like jQuery and think that its performance problems aren't a big deal? Or is it that you just like jQuery and think everyone should ignore all the problems?

Comment Re:I'm going to assume that was hipster irony. (Score 1) 91

Whatever else you may say you cannot possibly miss that jquery let you do the same thing but with far few characters being typed.

Savign a few seconds worth of typing isn't exactly a good reason to use a library! If the physically typing code is a bottle-neck in your development process, I'd love to know where you hire!

Most users know fuck all, and even if they do they don't pay the bills in web development, the client does.

They know when an app is slow and clunky. That's why you don't use jQuery Mobile. Of course, it looks like you hate users, so I'm not surprised that you're not concerned about their experience. I'll let you work out the ethics.

I have never had any performance issues with the stuff I have been creating

You'd be the first. Well, or you just haven't noticed.

Maybe if you were having Jquery performance issues it was with very old versions or you were not writing decent code?

I do have objective data to support that assertion. Very simple tasks take significantly longer in jQuery vs. vanilla JS. You can find any number of performance tests online, or even test for yourself with a profiler. You do use a profiler, don't you? If not, start using one!

Comment Re:That explains things (Score 1) 91

Seriously though, most people love jquery as it means we don't have to do basic animations in flash any more and can do ajax type stuff. Without things like jquery you would be stuck with whole page refreshes just because you wanted to add a row to a form.

Surely, you're new to web development.

I have done this sort of stuff in raw JS (I have been a web dev for almost 10 years) and it was just not worth the effort making it cross browser without doing whole page reloads that were slow for the average user.

You were probably just doing it wrong. I dug up an old ajax project of mine from 2006 not long ago and, well, it wasn't pretty. jQuery doesn't offer any real simplicity, once you know what you're doing -- I'd even argue that (vs xhr2) the jQuery equivalent is harder to read.

Really, I haven't found a single case in recent years where jQuery has made development easier. In the few places you can make a legitimate case, you usually can't justify the extra weight and performance penalty.

Comment Re:I'm going to assume that was hipster irony. (Score 1) 91

If you need to do some more massive JavaScript/DOM manipulation and querying then calling getElementByID and the others repeatedly will lead to extremely long code. It will also lead to unmaintainable code if you just put everything in one big code block. To keep your code short and to enable easy reuse, you'll need to encapsulate this code into functions.

You do realize all of that applies when you use jQuery as well, right?

Maybe you don't...

. Once you start making functions whose purpose it is to manipulate the DOM in a similar way across many different browsers, you are better off going with jQuery.

In the context you're trying to support the use of jQuery, it very obviously offers you no benefits what-so-ever. But you know that, right?

Well, I can't blame you for trying to make such a non-argument. It's VERY difficult to defend the use of jQuery. See, what this all boils down to is that you're comfortable with jQuery, not so comfortable with JavaScript, and already know that jQuery has long outlived any utility that it may have had in the past. You don't want to see your favorite "tool" die, so you feel the need to protect it from reality.

jQuery has promised, but never safely delivered cross-browser support. With 2.0, it gave up on that goal entirely. Besides, once you drop support for IE6, there's very little you need to do to maintain cross-browser compatibility. So little, in fact, that using jQuery actually *increases* the amount of work you need to do as you get to deal with cross-browser problems in jQuery and cross-jQuery problems with your plugins!

Recently, I decided it was (long past) time to upgrade so I reviewed our code, upgraded jQuery little by little, fixing things as they broke

For some reason, you mentioned writing reusable functions as a benefit of using jQuery. Using jQuery guarantees that your code will not be reusable. Sure, you can refuse to upgrade and artificially extend the life of your code, but you'll inevitably end up maintaining multiple jQuery versions, eventually loading multiple versions of jQuery on the same page! (If you use a lot of plugins, things will go to hell even faster...)

Think I'm joking? It's such a common problem that jQuery includes features to help you cope with it's instability (see: noConflict). There are a host of tools (like jQuery Quarantine) to help you manage the hell that you created because you swallowed a load of nonsense about a crummy library back in 2006. Er, sorry, read that as "thought you could save some time by using a popular library."

You could wind up essentially rewriting it, but chances are it won't be shorter/more efficient.

That's just absurd. jQuery primarily consists of functions that are common across browsers, wrapped in an incredibly inefficient library. It's primary (and only useful) feature was its selector engine, but that hasn't been an advantage for a very long time now. Once you learn more about JavaScript and the DOM, you'll realize how little jQuery actually offers you.

This is all off-topic. My original point was that jQuery Mobile is best avoided as it's too slow. (No surprise, no one is willing to defend THAT mess!) This turned in to "defend jQuery against the unbelievers!" thread, which I'm rapidly losing interest in.

Comment Re:I'm going to assume that was hipster irony. (Score 2) 91

Once you start having to create elements of the dom tree on the fly JQuery comes into its own in terms of writing less code and hence developers producing quicker results.

Looks like it takes the same amount of code to me. Also, the pure JS version is significantly faster as you can see from any one of several tests online.

Let's not forget about maintenance. The unreadable mess that jQuery forces you to write (to try to compensate for its absurdly poor performance) coupled with the ever-shifting API dramatically increases maintenance costs.

Nobody cares about efficiency any more

Your users care. They care a lot. The host of slow laggy UI's and the associated user complaints are a strong testament to this. The "computers are getting super fast" line has always been the cry of lazy and incompetent developers. Don't fall in to that trap!

Writing super efficient code is just not worth wasting time

That's why you should AVOID jQuery! You get a massive performance boost simply by avoiding it! You waste tons of time and effort already trying to get acceptable performance out of jQuery -- which ultimately leaves you with slower, less readable, and less reliable code in the end.

In short: Cutting out jQuery will ultimately save you development time, improve the overall quality of your code, and significantly improve performance. Why would you even bother with jQuery in the first place?

Comment Re:I'm going to assume that was hipster irony. (Score 2) 91

Smart programmers don't reinvent the wheel just because they can.

Then why are you using jQuery?

For the bulk of real-world jQuery use, you can use getElementById, querySelector, and querySelectorAll. Take a look around the web. It's disturbing.

Moving on, for stuff like animations, smart programmers use lightweight special purpose libraries rather than slow, bulky, buggy general purpose library like jQuery. Even better: When they can, they use CSS instead! Instead of jQuery + some heavy-weight plugin for a dropdown menu, you could do the same thing very quickly with some simple CSS. The result will be faster, lighter, and easier to maintain. (If you don't understand CSS, there are tons of generators online.)

What about Ajax? Again, vanilla JavaSript is the clear winner. A few lines of simple and easy-to-maintain code is all it takes. As a bonus, your code will be infinitely more readable, and won't break when jQuery makes it's regular set of breaking changes.

Aside from the obvious performance benefits you get from dropping jQuery, you also get MUCH more readable code. Nothing is worse than "optimized" jQuery as far as readability is concerned. Under the unlikely assumption that you actually save time during initial development, you'll easily lose it all maintenance.

What about supporing old browsers? Well, jQuery is dropping support for IE6, 7, and 8. Have fun with that.

Comment Re:That explains things (Score 1) 91

No kidding. JQuery Mobile is ridiculously slow.

You'd be crazy to use an inefficient and over-weight library like jQuery anyway. Adding jQuery mobile to that is just asking for trouble.

Let's face it: jQuery has long outlived it's utility. It's not even viable for dealing with old browser compatibility issues on the Desktop.

Just learn JavaScript. Your users will thank you. I'll bet that you'll even ultimately save time and effort as you'll spend less time trying to squeeze acceptable performance out of Resig's cludge -- and less time trying to debug the nasty one-liners you're forced to write to get those tiny improvements.

Comment Re:I can't imagine this is worth it (Score 1) 146

I figure they intend to profit on the documentary, not whatever they manage to unearth. Prices are up right now (thanks to the AVGN movie and the documentary project) but you used to be able to pick-up a pristine copy of E.T. (with box and manual) for less than $5. They'd have to be crazy if they thought they could profit from that.

There may be a small market for E.T. carts actually unearthed from the legendary landfill. The history would make the piece much more interesting.

Slashdot Top Deals

It is impossible to enjoy idling thoroughly unless one has plenty of work to do. -- Jerome Klapka Jerome