JavaScript - Yahoo News Search Results

118.7 ¥/$ (5 p.m.)

Sorry, but your browser needs Javascript to use this site. The number of visitors to Japan is likely to exceed 13 million in 2014, according to Japan Tourism Agency Commissioner Shigeto Kubo.

118.48 ¥/$ (3 p.m.)

Sorry, but your browser needs Javascript to use this site. WASHINGTON – More U.S. teens are trying out e-cigarettes than the real thing, according to the government’s annual drug use survey.

118.5 ¥/$ (2 p.m.)

Sorry, but your browser needs Javascript to use this site. SAN FRANCISCO – Scientists say the three prisoners who escaped from Alcatraz in one of the most famous and elaborate prison breaks in U.S. history could have survived and made it to land.

117.41 ¥/$ (5 p.m.)

Sorry, but your browser needs Javascript to use this site. LONDON – Britain thwarted a Sydney-style “lone wolf” attack just days before it was due to happen, London’s top policeman said on Wednesday, saying his force had foiled five terror plots in the last four months alone.

In Programming Language Landscape, Dart Remains a Work in Progress

Google released the latest version of its Web development language and potential JavaScript rival, Dart 1.8, in late November, adding some new features to the language and its supporting libraries. What remains uncertain is the overall role Dart will play in the broader development language ecosystem. Managed service providers (MSPs) have a major stake in Web development and the programming ...

QuaggaJS offers JavaScript-based barcode scanning

JavaScript, more commonly known for its dominance in client-side Web application development, is being extended to the realm of barcode scanners. With QuaggaJS, a developer in Austria is developing a barcode scanner written in JavaScript and supporting real-time localization as well as decoding of barcodes like EAN and Code128.

Facebook's Flow could help JavaScript programmers spot elusive bugs

Easing what has traditionally been a difficult programming task, Facebook has released as open source a debugging tool for JavaScript, called Flow, designed to highlight problems caused by the misuse of data types. “Flow improves speed and efficiency so developers can be more productive while using JavaScript,” Facebook engineers said in a blog item posted Tuesday. Facebook has used Flow for ...


recent bookmarks tagged JavaScript

Matthew Mueller

Posted on 18 January 2038

Microsoft Ajax Content Delivery Network - ASP.NET Ajax Library

Posted on 14 April 2018

loading overlay demo - JSFiddle

Posted on 18 December 2014

Social Share Privacy

Posted on 18 December 2014

Posted on 18 December 2014

Amritsari Tawa Macchi – Pan Fried Fish – Sinfully Spicy

Posted on 18 December 2014

Posted on 18 December 2014

Angular js SEO

Posted on 18 December 2014


Posted on 18 December 2014

Doi Mach Non Vegetarian Recipe | fromKhazana of Indian Recipes by Master Chef Sanjeev Kapoor.

Posted on 18 December 2014

Questions About JavaScript (programming language) on Quora

Questions About JavaScript (programming language) search results

I've plateaued. How do I change from a decent JavaScript programmer to a great JavaScript programmer?

I've been programming for about three years and have been a web developer for two. My language of choice has been JavaScript ever since I was introduced to it.

I'm a decent programmer. If somebody needs something that does X, Y, and Z, I can hack away and produce some code that will do X, Y, and Z. I've gotten to the point that I'm confident that I can implement almost anything -- given an infinite amount of time. But I feel I've reached a plateau.

I see other programmers, the good ones, ones that are creating and working on large projects and their code just... makes sense. Whereas my code just kinda looks thrown together. The good programmers are writing code that creates a coherent structure of the entire codebase instead of just implementing stuff.

I want to be like that. I want to be able to conceive of a large scale app and give it a good infrastructure -- something that's testable, maintainable, and extendable. I want the pieces to fall together instead of getting mashed together with duct-tape and glue.

How do I change from a decent JavaScript programmer to a great JavaScript programmer?

EDIT Thanks guys, your help has been immense. I gotta learn design patterns, really let them sink into my brain.

submitted by phnglui_mglwnafh to javascript
[link] [63 comments]

Posted on 28 October 2014

I'm making an RPG in JavaScript! Without canvas! Yes, I'm an idiot!

Update: I got a test version of the current build up and running if anyone wants to check it out!

Controls: Up/W, Down/D, Left/A, Right/D, Enter/Spacebar

Hello there! I am a budding JavaScript developer looking to make a name for himself (read: find employment), and so I decided making an RPG might be a fun way to test out my skills. It's far from finished, but I think I'm far along enough that I can share with people, and hopefully get some feedback!

The GitHub repo:

I'm also getting into the habit of making write-ups of the process:

I don't have screenshots, but here's a really quick video I posted just recently:

I'm posting in /r/javascript primarily to get some constructive criticism on the code aspect of it, not so much the game design aspect. Also, this is technically my first GitHub repo, so if I messed up the setup instructions in any way, let me know.

Any and all feedback is welcome!

Edit #1: A clarification! I work primarily as a front-end developer and UI/UX designer. Hence, my DOM-only approach. I'm using this project as a way to hone my DOM manipulation skills, and have a little bit of fun while doing it!

Edit #2: After some of your feedback, I'm definitely going to refactor some of the code to stop relying on jQuery as a kind of framework.

Edit #3: Thanks for all the support, everyone! There's a lot of really good advice on this thread, and I'm gonna do my best to put it to good use!

submitted by robobeau to javascript
[link] [127 comments]

Posted on 12 August 2014

Do JavaScript app developers typically use object-oriented javascript?

I'm a Java Developer and i'm about to learn JavaScript and AngularJS. Do folks that make full-blown enterprise apps with things like AngularJS tend to use a lot of object-oriented JavaScript or not? I don't find the object oriented features of JavaScript to be very intuitive (i.e. prototypes etc). Do folk actually make a lot of prototypes and use inheritance etc?

submitted by vt97john to javascript
[link] [57 comments]

Posted on 14 July 2014

Turns out you can write cross-platform drivers in JavaScript via Chrome

I have a medical device that requires a real, honest-to-God Windows machine to download data from. Not even a VM will do it. Some enterprising folks have written a driver that'll run on an Android phone. 2 weeks ago I heard you can write USB drivers in Chrome Applications. A little poking and fiddling and I've ported theirs to Javascript.

It's been an interesting exercise. Despite being a big Javascript fanboi, a month ago, I had no idea this would even be possible.

submitted by altintx to javascript
[link] [15 comments]

Posted on 20 June 2014

Javascript Interview Question

What are some common Javascript and problem solving questions that are asked on interviews. Any level of difficulty questions you have been asked? It would be great to have some links and posts about this. Thank You well in advance, anything will help

submitted by arcoboy to javascript
[link] [71 comments]

Posted on 14 June 2014

Why do so many Javascript libraries get this wrong?

And why does no one notice?

All too often I see a promising Javascript library follow this approach to creating classes:

function Library(a, b) { this.publicMethod = function() { return a + b; }; ...etc... } 

Instead of the superior prototypical way:

function Library(a, b) { this.a = a; this.b = b; } Library.prototype = { constructor: Library, publicMethod: function() { return this.a + this.b; } }; 

For those of you who don't understand the difference, in the first (non-prototypical) approach, every time you initialise a new Library object you also unnecessarily recreate every single method. If your class is instantiated a lot and/or has a large number of methods, this will lead to much heavier memory consumption. The other approach only creates the Library methods once to be reused in different contexts (the typical inheritance model), which is much better for memory.

Now the average jQuery plugin isn't going to see a whole lot of decrease in memory consumption by using the prototypical approach, but how has it not been the standard this whole time? It's clearly the intended way of creating anything like a class in Javascript.

I remember years back when I first started learning Javascript, every tutorial I found taught the former approach. I didn't even hear the word prototype until years later. Yet after all these years with Javascript maturing as it has I still run into recent GitHub projects that base it around the obviously inferior design approach. And no one even mentions it in the issues, even on ones with thousands of users and hundreds of contributors.

Maybe I'm missing something here...

EDIT: It seems I've stumbled upon quite a controversial topic in the Javascript community. A lot of really great points here, let's just try to not downvote comments only because we don't agree with them.

EDIT 2: It seems the general consensus is that they each have their appropriate uses. My views have definitely been challenged and I recognise that my opinion was a little flawed. This has been an excellent discussion, thank you!

submitted by poisondwarf to javascript
[link] [116 comments]

Posted on 2 April 2014

[Discussion] Is it just me or are people trying to make Javascript more complicated than it needs to be?

Without starting a flame war, it seems like libraries/frameworks like Backbone, Require, Flight just trying to turn Javascript into a MVC/MVVM nightmare?

[edit] Couldn't a decently coded OOP piece of code be just as efficient and readable?
Also, isn't there far too many libraries and frameworks?

I'm only after a discussion :)

submitted by neurofluxation to javascript
[link] [86 comments]

Posted on 17 October 2013

Advanced Javascript

I've been working in javascript for 5 years, and I understand prototypal inheritance, scoping, call / apply, and the usual concepts that people consider "advanced". However, I feel like there must be more to learn about vanilla js. What are some hidden features about the language that even the advanced user may not know about?

I'm not very interested in external libraries or upcoming versions of JavaScript, but practical things that I could use (with an optional shim) all the way back to IE7.

Any thoughts?

submitted by pirateNarwhal to javascript
[link] [52 comments]

Posted on 13 August 2013

Is the option to disable Javascript in browsers outdated?

Do you think the option to turn Javascript off in most browsers is outdated?

It seems like more and more of elements of the user experience that users really like and find really useful, necessary, are dependent on Javascript. AJAX is the best example.

All of that gets bollixed up if someone shuts Javascript off. Yes, the programmer can detect if Javascript is enabled, but it seems out of date for browser makers to give the users the ability to shut off a major.....close to being a defacto standard technology, s/he may need.

submitted by cyanocobalamin to javascript
[link] [99 comments]

Posted on 12 August 2013

What are your vanilla JavaScript knowledge standards that every JS developer should know?

I have an interview coming up for a front end position. I have used JavaScript while at uni for the last 2.5 years and am familiar with Modular JavaScript and other design patterns. Also am familiar with scoping in JavaScript and ...inheritance.

What other things would you recommend I brush up on? Your help would really be appreciated!

submitted by js_coder to javascript
[link] [230 comments]

Posted on 7 August 2013

My javascript game as native application for Android, Windows / Linux / OSX

I will be writing some "How to" articles soon but for now I would like to share what I consider finished work - and spawn a few initial thoughts on different platforms / systems.

Quick vine/video of the game if you are wondering is it worth reading.

Link to the game is at the bottom of post - because I mostly want to share my bitter-sweet joy after spending 500+ hours on this title.

Technical details:

  • Done with canvas - supported by my unfortunately named library Canvas Query
  • No DOM/CSS rendering
  • Sound based on Audio element (no WebAudio API)
  • GamepadAPI - w3c/chrome specification

Windows / Linux / Osx - node-webkit

Very pleasant to work - absolutely nothing has to be tweaked. Managed to do both windows and linux packages under Ubuntu (using WINE). Unfortunately for Mac you need OSX. Also you need special build for OSX < 10.7 - alsooooooo your app will not get accepted in Ubuntu Store for Ubuntu > 12 because of some dependencies craziness

Android / IOS - CocoonJS

Everything goes rather smooth if you are creating the game with cocoon in mind from the start - no DOM, first canvas element is screen, some traps like audio.load - pros is that it is WAY faster (thanks to OpenGL) than PhoneGap and other solutions - also you don't need OSX, nor developers account in development process. Cons are that you will loose your hair searching for bugs that are not in your code.

I have failed to make port for IOS because imageData related functions are not working properly - also it kill the app randomly for some reason - also context.arc is broken on IOS.

CocoonJS will support Gamepad API which makes it possible to make OUYA games. If you can't get your game working on IOS - ejecta is an alternative.

Firefox OS

Deploying application is the easiest of all platforms - you just upload some manifest file and voila - no porting at all. However the OS is still too slow to render more complex games like QbQbQb - tho I've been able to run different one in built-in browser (which performance is no-different from native apps) with promising results (but that's not the topic).


Currently my game is available on Humble (bundle) Store and Google play store, Newgrounds, Kongregate. Pending approval for Desura. Rejected by GOG and Rovio stars. Will be trying greenlight. However this is marketing - I am failing hard in this field so won't play wise guy :)

One advice: do not put DEMO in title on Kongregate - even if it is true :) They like/ask to be cheated by disguising demo as a normal version - and then full game is called "SUPER" or "HD" despite it has all the same assets.

I will be trying to find time to reveal little by little details on publishing on different platforms - especially how to build packages for android, ubuntu or making windows installers because this is something that javascript programmer may find extremely repulsive (I DID... it breaks the whole idea of HTML5 portability with browser as a vessel - and I am not yet sure was it the best business decision).

Also to show you a glimpse of how many twists are there check my distribution/ folder structure

The game:

|~o Click this o~|

Also - if you are currently porting html5 game and got stuck on something - ask - maybe I have encountered the same problem and managed to go through.

I will announce articles on /r/javascript but you can follow me on twitter or tumblr

submitted by rezoner to javascript
[link] [60 comments]

Posted on 4 August 2013

Javascript != Java

3rd-party contractor came to visit office yesterday, who has "decades" of experience. Conversation came up about JavaScript in one of our products. He says, "Our product doesn't use Java." After an awkward moment with someone who works on the knowledge base nodding in agreement with him, I speak up and delineate the difference between Java and JavaScript.

Later on in the conversation, the same 3rd-party guy followed up with this jewel: "besides, what would anyone even use JavaScript for on the web?"

I proceeded to disable Javascript in my browser and show him.

tl;dr: lasers, dinosaurs, & drums made a guy's head explode

[edit spelling]

submitted by raiderrobert to talesfromtechsupport
[link] [364 comments]

Posted on 22 May 2013

I'm trying to learn JavaScript, and all of the books I've looked at begin with a heavy dose of binary and memory allocation - is it really necessary to learn this??

I fully understand that in order to be a fantastic, brilliant programmer learning about how the computer converts your code and how much memory it takes to process it could be of benefit, but as a beginning programmer, I feel like it is a great waste of my time (for now) to know that the number 114 is made up of 64 bits. I'm feverishly trying to up my skill set so that I can move out of my horrific tech support job and into the world of programming, and in order to maximize my time, is it okay to skip over this or will it haunt me further down the line?

edit: Thank you for all the feedback, insight, and encouragement! I have ordered Professional JavaScript for Web Developers and The Definitive Guide from Amazon. They won't be here for another week, so in the meantime, I am 25 pages into homoiconic's book JavaScript Allonge (a very clever and informative read!) and I'm pressing on :)

submitted by have_u_restarted_it to javascript
[link] [131 comments]

Posted on 1 February 2013

If JQuery is so easy to implement, why learn vanilla javascript?

So im learning front end development as i go along, and i've been asked by some clients to include things like accordian and datepicker UI elements of JQuery. Im really struggling with the code academy exercises and am beginning to ask myself 'do i really need to learn vanilla javascript if everyones using libraries anyway?'. What possible use could vanilla have these days?

Also, should i be doing more than just doing the exercises on code academy? i.e read books on jscript/work on some sort of basic project?


Edit : Why downvote? I've been doing front end coding for 2 months now so i really dont know that much. Help a guy out!

Edit 2 : Some great posts here guys. Thanks for you input. In hindsight I maybe should have stated my aspirations ; I dont desire to be a programmer. I don't find writing code for the sake of it fun, HOWEVER, I do get inspired by browsing and seeing beautiful websites with such interactivity and fluidity. I want to be able to make visually stunning websites as opposed to soley being a 'programmer' in the traditional sense if you understand. Thanks again.

submitted by jsthrow to javascript
[link] [114 comments]

Posted on 8 November 2012

r/javascript is not Stack Overflow

I don't know how other users of r/javascript feel about this, but I think this should be a forum for discussion of Javascript itself and sharing interesting examples.

Every day new threads hit the top of the page which are just asking for help with, or critique of code. IMO, these kinds of posts belong in a different forum, preferably Stack Overflow, a link to which is posted right over there --->

Am I being a fusspot? How do other people feel about this?

submitted by mitchellrj to javascript
[link] [115 comments]

Posted on 23 October 2012

Suggestions for attacking tech debt in the javascript?

Like many developers, I'm on a team with a lot of people interested in the back-end. What I've noticed is that tech debt accumulates more quickly in our front-end than anywhere else. It is here that devs seem more likely to let mediocre code slide and have the least expertise. Most of us have read 'Javascript: The Good Parts' and have years of experience writing javascript. The problem is, we've been writing it second-class, and we haven't accumulated the expertise I feel is necessary to write a decent FE component.

I know that's all rather vague, but I hope it gets at the what I'm trying to ascertain. If not, here are some specific questions:

  • What practices are critical to writing better javascript?
  • At this point in our education, would adopting a framework like backbone.js facilitate or inhibit our growth?
  • How have you succeeded in legitimizing javascript at work? How have you failed?

Thank you.

submitted by Carnilawl to javascript
[link] [31 comments]

Posted on 18 June 2012

What program do you use to write Javascript?

I hope you guys don't get this a lot. Currently I'm using Dreamweaver code mode, but there's got to be a better tool out there for OO Javascript right?

Edit: Thanks for the advice guys, I'm going to give a couple of these a shot.

Also, I was going to ask for some up-votes, so that this would be more prominent on /r/javascript, but then I remembered it was /r/javascript. 2 is enough.

submitted by 90yoboy to javascript
[link] [139 comments]

Posted on 9 August 2011

Recommendations for mastering JavaScript.

I'm making it a goal of mine to master JavaScript and was hoping someone else had done the same and wouldn't mind sharing their regime.

EDIT: ** **I've created a new post to host all the references from this post. Find it here.

EDIT: Thanks guys. I've compiled a list of references mentioned here. I appreciate all your contributions.

  1. Anything written by Douglas Crockford. This includes: JavaScript: The Good Parts and YUI Theater
  2. Read other people's code, jQuery source, Node's source, etc.
  3. Understand JavaScript before becoming dependent on libraries (eg. jQuery, Prototype).
  4. Addy Osmani's Javascript 101 audio course
  5. Build Things - "think of something cool, and try and build it."
  6. Participate at StackOverflow.
  7. References -o- plenty: Gecko DOM Reference, HTML and DHTML Reference, Yahoo! YUI Theater, HTML DOM Tutorial, Annotated ECMAScript 5.1, JavaScript, JavaScript Blog

  8. And finally, Lord loves a working' man, don't trust whitey, and see a doctor and get rid of it.

submitted by fl0at to javascript
[link] [93 comments]

Posted on 21 February 2011

Javascript is NOT a bad language

Venting here. I'm sick of hearing that Javascript is a bad language. It's not perfect (what language is?) but it is quick and easy to write clean, flexible and reusable code. It's extremely well documented. It has some sweet debugging tools (these days). I love the powerful dynamic nature of it, and the event driven programming that it enables. Occasionally I sit down with people that "used to do some Javascript back in the day", people who were left with a bad taste in their mouth. Together we (ok, mostly me) hash out some clean, concise, and readable Javascript... and I laugh as they slowly realize that they don't know as much about it as they thought they did.

I love Javascript. It's the web browsers that I usually have issues with.

submitted by spiderworm to javascript
[link] [83 comments]

Posted on 29 December 2010