JavaScript at 20

Post by frik » Fri, May 15, 2015, 6:28 PM UTC

wwweston wrote: post #19

Dirlewanger wrote: post #4

Cool presentation, but holy shit, taking ~2 minutes to load on FF and freezing the browser is not.

Anecdote, but I've got 30 tabs open in Chrome and I'm using a Macbook Pro that's over 7 years old and it loads in less than 3 seconds. Also, I can open it in Lynx. The un-alt'd images mean there's a bit of inaccessible content, but it's actually more or less coherent, which might be useful to those whose machines are struggling with the content or even (potentially) to those rendering opinions on whether the web just…

Post by eldude » Fri, May 15, 2015, 6:30 PM UTC

    async function someAsync(list) {
      let ret = [];
      try {
        for (let item of list) {
          let res = await asyncFn(item)
          ret.push(res)
        }
      } catch(e) { /* ignore */ }
      return ret;
    }

    async function someAsync(list) {
      let promises = [];
      try {
        for (let item of list) {
          let promise = asyncFn(item)
          promises.push(promise)
        }
        return await Promise.all(promises)
      } catch(e) { /* ignore */ }
      return [];
    }

Post by swsieber » Fri, May 15, 2015, 6:32 PM UTC

arbsn wrote: post #131

knightofmars wrote: post #40

"Haters gonna hate." Anyone claiming that JS is the "worst thing to happen to the web" and/or that some other language would miraculously solve all of the problems present in JS should do the following, "Go create it." Don't whine about the barriers and how a new language would never be adopted because "JS is already everywhere." There are plenty of people already trying to solve this problem by actively doing someth…

I don't believe that someone needs to have a solution in order to observe that there is a problem. The resources available to an individual for creating and reasoning are finite, and as long as one is able to give good reasons why they know that there is a better way, "there is a problem" may still be valuable information.

Post by manish_gill » Fri, May 15, 2015, 6:38 PM UTC

TazeTSchnitzel wrote: post #129

TazeTSchnitzel wrote: post #84

Earlier quoted context omitted.

> Just let me know when browser vendors are going to break down the two-tiered system, and let us run the legion of alternatives alongside -- instead of under -- JavaScript. Just let me know when Intel, AMD and VIA are going to break down the two-tiered system, and let us run the legion of alternatives alongside -- instead of under -- x86 assembly language.

14paninta replied to this, but their comment's dead (shadowban?) - anyway, I'll repost it here and respond to it. > What does that even mean? It's nonsensical. What it means is that the situation with browsers is not much different from the situation on native platforms. CPUs support one language, the browser supports one language. And yet I don't see anyone complain about CPUs only supporting one language, because y…