Top all-time · #2366
J
John Resig
Personal blog · johnresig.com · on HN as jeresigprogrammingweb
John Resig's personal blog at johnresig.com covers programming and web. Since 2017, 35 different Hacker News readers have linked it 38 times, most often “Learning Advanced JavaScript (2008)”. No feed was found, so read it on the site itself.
No feed foundVisit the blog
38mentions?
35HN people?
2017–2026first – last linked?
Most-linked posts?
- Learning Advanced JavaScript (2008)4 people · 5 mentions · first linked 2017-07-31
- /blog/re-securing-json/4 people · 4 mentions · first linked 2017-05-06
- Write Code Every Day (2014)4 people · 4 mentions · first linked 2019-03-11
- Programming Book Profits (2008)3 people · 3 mentions · first linked 2018-05-07
- /blog/javascript-performance-rundown/2 people · 2 mentions · first linked 2019-08-30
- John Resig – ECMAScript Harmony (2008)2 people · 2 mentions · first linked 2021-02-01
- Accuracy of JavaScript Time2 people · 2 mentions · first linked 2018-08-23
- /blog/web-workers/2 people · 2 mentions · first linked 2017-05-30
What Hacker News says?
The point is Mozilla, Apple and Adobe did enormous work on JS before Chrome was released. nbody and Fannkuch are meaningless for real world performance on a client side JS app. V8s benchmarks were widely considered to be unrepresentative of what browsers actually do. Sunspider and derivatives were the most realistic tests at the time and Chrome wasn’t a dramatic improvement. https://johnresig.com/blog/javascript-per…
Comment linking /blog/javascript-performance-rundown/
on “Ask HN: A New Decade. Any Predictions? (2010)”Submitted Programming Book Profits (2008) as a story · 75 points
HN discussionThis type of exercise doesn't quite help me. When I was learning Go, I couldn't find one that suited me, so I wrote one as I learned: https://github.com/hliyan/learn-golang/blob/master/day-01/he... For learning JS internals, I used this: https://johnresig.com/apps/learn/
Comment linking /apps/learn/
on “Exercises to Learn Rust”Submitted JavaScript: Search and Don’t Replace (2008) as a story · 42 points
HN discussionI found https://webkit.org/blog/8685/introducing-the-jetstream-2-ben... , with a graph at the end, but of course that is written by Webkit (JSC) developers. Then there is https://johnresig.com/blog/javascript-performance-rundown/ from 2008. https://www.railsmine.net/2017/12/browser-benchmark-safari-1... from 2017, similar results to the JetStream 2 post.
Comment linking /blog/javascript-performance-rundown/
on “The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70”Submitted John Resig – ECMAScript Harmony (2008) as a story · 4 points
HN discussionThe John Resig post linked by TFA indicates that this was originally dealt with by locking the constructor altogether: function Array(){ alert("hello, I found something of yours!"); } // ERROR: redeclaration of const Array But it appears that the restriction now applies only to literals, as I can do this in at least Chrome and Firefox: function Array() {console.log("hope")} undefined var x = new Array(3); hope undef…
Comment linking /blog/re-securing-json/
on “Why does Google prepend while(1); to their JSON responses?”Submitted Twitter vs. Mastodon as a story · 2 points
HN discussionNote that these protections are only needed because Google supports every imaginable browser version even outdated ones. You most certainly do not need to do the same. Array and object globals cannot be overridden now (since 2007) for literals [0] and for ambient authority problem with CORS just check the Origin header. [0]: https://johnresig.com/blog/re-securing-json/
Comment linking /blog/re-securing-json/
on “Why does Google prepend while(1); to their JSON responses?”Submitted getBoundingClientRect Is Awesome (2008) as a story · 2 points
HN discussionAbsolutely yes. jQuery selector engine was developed before the official Selector API, which ended up being almost exactly the same. Except for a few exceptions which John wasn't too sure about when they asked for feedback: https://johnresig.com/blog/thoughts-on-queryselectorall/
Comment linking /blog/thoughts-on-queryselectorall/
on “jQuery v4.0 Beta”Submitted Write Code Every Day as a story · 2 points
HN discussionReally useful, thank you! I had saved this post of John Resig's from 10 years ago (!), which also gives some numbers: https://johnresig.com/blog/programming-book-profits/ (I'm not sure if my expectation is reasonable, but I would have thought that a book the most popular JS framework author would have sold more / made more in profit.) I know you said you weren't planning to write another book, but I wonder if in ret…
Comment linking /blog/programming-book-profits/
on “The Economics of Writing a Technical Book”Submitted Write Code Every Day (2014) as a story · 2 points
HN discussionSome people had to wait four years. The MEAP was released in 2008. Three years later Manning brought in a second author to finish the book. It was released in 2012. A couple of quotes from https://johnresig.com/blog/secret-omens/ : > ...I got caught up in coding and stopped focusing on writing. I had to prioritize my time and I chose to prioritize doing more development and focusing on my personal life. > ...I would…
Comment linking /blog/secret-omens/
on “John Resig: Introducing the GraphQL Guide”Submitted Learning Advanced JavaScript (2008) as a story · 1 points
HN discussionFetching time in the browser isn't accurate because a lot of trackers exploit timing in order to fingerprint users. A lot of browsers now purposefully reduce the precision of the clock. See: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... https://johnresig.com/blog/accuracy-of-javascript-time/
Comment linking /blog/accuracy-of-javascript-time/
on “PyPy.js: Python in the web browser”Submitted 10th Anniversary of jQuery (2016) as a story · 1 points
HN discussionFrankly, I think we're seeing the results of the new era of Python paradox. Except it's not Python 3, it's TypeScript, VS Code, and React. If you look at the education space, many of the deployments are either Chromebooks or iPads. Back in 2012, the "learn to code" sites (like Khan Academy or Code.org) ended up building their lesson plans around JavaScript. https://johnresig.com/blog/introducing-khan-cs/ People who…
Comment linking /blog/introducing-khan-cs/
on “The Rise of Microsoft Visual Studio Code”Submitted Write Code Every Day (2014) as a story · 1 points
HN discussion>I'm not so sure. Static, printed 2D paper isn't nearly so limiting as you'd think. The real benefits of e-textbooks aren't little interactive animations, but substantive learning-by-doing. For example, having a real interpreter or simulator built into the learning software. A good example of this concept is Resig's advanced javascript tutorial ( https://johnresig.com/apps/learn/ ), but you could easily see somethin…
Comment linking /apps/learn/
on “Students learn more effectively from print textbooks than screens, study says”Submitted Accuracy of JavaScript Time as a story · 1 points
HN discussionA problem with learning JS is the old versus new. The language has evolved enormously. Callbacks vs async, functions and arrow functions, and "this" are a few examples. So learning JS perfectly and completely, is a bit like learning not only English, but old English as well. There is very little (if any) JS that is no longer accepted, but there are many parts that are no longer best practice. I have found that under…
Comment linking /apps/learn/
on “Ask HN: How do I learn JavaScript?”>JS of the past was the wild west. You want to add a bookmark? Go for it! You want to trigger a print dialogue? Why not! Yeah. People forget that in the bad old days you could even do things like redefine the global Array constructor[0]. [0] https://johnresig.com/blog/re-securing-json/
Comment linking /blog/re-securing-json/
on “JavaScript: The Modern Parts”rems don't work either because there are instances where you need to have things line up exactly. For example, if you have 3 columns. You will be one pixel out. There are no good ways to fix this. See [0] https://johnresig.com/blog/sub-pixel-problems-in-css/ CSS should only be used to appease those ppl in your org that read/write more blog posts than code. Use JS if in doubt. You're welcome.
Comment linking /blog/sub-pixel-problems-in-css/
on “Incomplete List of Mistakes in the Design of CSS”John Resig (inventor of Jquery) has written books across a variety of publishers. He has also written extensively about how he fared financially. These are worthy counter points to the discussions here about "only 10%." https://johnresig.com/blog/programming-book-profits/ https://css-tricks.com/so-you-want-to-self-publish-books-and... TL;DR: for a person as Internet famous as John, discoverability and getting a full…
Comment linking /blog/programming-book-profits/
on “Writing a book for O'Reilly”Well to nitpick your nitpick. Internet Explorer did allow you to use vbscript to manipulate the DOM. http://www.herongyang.com/VBScript/IE-Browser-DOM-API-Docume... Also you can use XSLT to create a new DOM tree in a browser from an XML document. http://www.informit.com/articles/article.aspx?p=24032&seqNum... EDIT: I forgot about JScript vs JavaScript vs ECMAScript. https://johnresig.com/blog/versions-of-javascript/…
Comment linking /blog/versions-of-javascript/
on “What people in tech had to say about JavaScript when it debuted in 1995 (2017)”Uh - woah! This is incredibly unexpected. I'm really glad people are interested in my database and in Japanese prints! From a technical perspective there've been a lot of interesting open source projects that I've made to support this site: https://johnresig.com/projects/ukiyoe/ I've also written a number of papers and given presentations on the work that I've done here (and elsewhere in the digital humanities). htt…
Comment linking /research/
on “Japanese Woodblock Print Search”If you truly want to grok JavaScript, I can recommend no better tutorial than this: https://johnresig.com/apps/learn/ It is how I finally grokked JS and it is the same tutorial that I put all new additions to my team through...
Comment linking /apps/learn/
on “Ask HN: Resources for learning advanced JavaScript and React”The biggest pain point in these security guidelines is context. For example this Array override issue has been fixed in major browsers 11 years ago [0]. Unless someone codes for IE6 I'd consider this not a real problem. [0]: https://johnresig.com/blog/re-securing-json/
Comment linking /blog/re-securing-json/
on “OWASP Cheat Sheet Series”
