Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialseth aruby
10,111 PointsWhy const vs let when assigning new XMLHttpRequest() object to variable?
Noticed that when completing this challenge using the 'let' keyword for assigning XMLHttpRequest() object to the variable was failing. So had to use const instead. Wondering why? Thanks in advance...
let request = new XMLHttpRequest();
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>AJAX with JavaScript</title>
<script src="app.js"></script>
</head>
<body>
<div id="main">
<h1>AJAX!</h1>
</div>
<div id="footer"></div>
</body>
</html>
1 Answer
Steven Parker
231,186 PointsThat does seem odd. I have two wild guesses:
- they wanted to enforce the "best practice" use of "const" over "let" (but "var" also works)
- an older challenge checking mechanism was only partially updated for ES2015 syntax
seth aruby
10,111 Pointsseth aruby
10,111 PointsThanks, man.