Amusing, this article was submitted 2 weeks ago and got no comments.
Enough with the JavaScript already
91–100 of 231 posts
Re: Enough with the JavaScript already
#92JavaScript is a tool. Once it becomes trendy idiots will always abuse a tool. It's not JavaScript's fault people are bad at web design and development. If it wasn't fucked up JavaScript these people were contacting you about it'd be something else, be glad you have a job.
We are all abusing the technologies originally developed for hypertext documents (HTTP, HTML, CSS, JavaScript) for building applications. If you today started working on a set of standards for handling what people currently build on the web proposing those technologies would be completely ridiculous, so ill suited are they for this job. And JavaScript is probably the worst of all, it is designed badly enough that the…
Amen!
The fact that it's still insanely easier to write desktop apps, using one or two languages and a layout manager vs. dealing with two decades of WTF! web programming makes me sad.
Re: Enough with the JavaScript already
#93I wonder if there'll ever be an alternative to Javascript. I'm not talking about those things that eventually get translated to Javascript, I'm talking about a native platform well thought-through and based on a typed language that isn't a mess. Yeah, I know: it's not Javascript that's broken, it's the DOM. I'd argue that both should be replaced by something else, otherwise the future will be 90% native mobile apps,…
I develop applications that skip the browser(s) and HTML. But it's not totally cross platform. But then again I don't develop for Joe Public most of the time either....
Re: Enough with the JavaScript already
#94This slideshow lost all credibility when it said to put your analytics in the tags. Sure some analytics providers might recommend you do that, but that is wrong and only serves to A) Slow your site down B) Introduce a single point of failure into your webpage All scripts should be loaded either async or at the end of the dom.
If you load the analytics script anywhere other than the head, you potentially miss user input while the page is loading. For a slow-loading page, this could make you lose out on useful data. I realize that this argument is somewhat circular.
Re: Enough with the JavaScript already
#95Earlier quoted context omitted.
I like to think of it this way: Some languages allow you to shoot yourself in the foot easier than other languages, given the context and environment. Abuses and problems precisely show Javascript's defects. The more easily abusable a language is, the more defective it is. A lot can be said about familiarity with the language. Many examples in wtfjs.com boils down to (mis)understanding the language itself. Let's call…
You are 100% wrong. C allows you to shoot yourself in the foot much more easily and much worse than JavaScript. JS is a far more "safe" language to code in. No pointers, no memory allocation. Yeah JS isn't typed but the problems that you get into with that are nothing by comparison. And again, I'm not saying JS doesn't have problems, it does. But the problems this presentation is complaining about are not results of…
>> No pointers, no memory allocation.
There are definitely both of those things, they just aren't explicit in the same way.[1]
[1]: http://point.davidglasser.net/2013/06/27/surprising-javascri...
Re: Enough with the JavaScript already
#96It's not really an either or thing. You can go too far with client side rendering. But progressive enhancement can only bring you so far in delivering an interactive experience - it's typical that his example is a simple tabs implementation - of course that's easy to do without much js. That's why I like knockoutjs - it makes it easier to sprinkle in the data-bound rich interactive UI to the pieces of your page that…
have you actually done this? I was wondering if this is a feasible and good way to use knockout!
Re: Enough with the JavaScript already
#97Earlier quoted context omitted.
IE8 usage is under 8% so it's possible for some people/organizations to stop supporting it. In another year, I would expect market share to be under 5%. http://gs.statcounter.com/#browser_version-ww-daily-20130615... IE10 has more usage. Hopefully, Win 8.1 is successful for Microsoft and XP usage drops significantly.
There can be many markets where IE usage is much higher than the worldwide average. My previous job had IE as a whole with ~60% share. You can't just decide to ditch a browser because of averages, you need to look at your own data.
Corporate Intranet: within epsilon of 100% IE 8, at the moment. My current job and the last one always had some outdated version of Internet Exploder as the desktop standard (which I ignored for running anything other than in-house junk -- no way I'm taking MSIE out into the wild)
Re: Enough with the JavaScript already
#98Earlier quoted context omitted.
People don't use javascript because it's a beautiful, well thought out language. They use it because it runs everywhere .
Here's the painful part: Douglas Crockford wrote a book called Javascript, the Good Parts. If Javascript were limited to The Good Parts alone, it has the potential to be a beautiful well thought out language. It would be quite close to a beautiful well thought out language
What's stopping you from only using the "good parts" in your own code? How is JS a bad tool? It runs reasonably fast, works everywhere, is a small, simple language that's surprisingly powerful. What if Eich had been influenced by C instead of Lisp when creating JS?
All things considered, it could have been way worse than it is, and the truth is JavaScript lets you get in there and do good stuff. Not sure why we are still hating on this environment.
Re: Enough with the JavaScript already
#99This deck is really hard to flip through on an iPhone. Nothing a little JavaScript couldn't fix.
Re: Enough with the JavaScript already
#100I wonder if there'll ever be an alternative to Javascript. I'm not talking about those things that eventually get translated to Javascript, I'm talking about a native platform well thought-through and based on a typed language that isn't a mess. Yeah, I know: it's not Javascript that's broken, it's the DOM. I'd argue that both should be replaced by something else, otherwise the future will be 90% native mobile apps,…
Google were planning to do some interesting experiments with JS and the DOM - they're hinted at in the Blink announcements but can't remember seeing any more about them yet