@pitaj Having a branch for the production version with a similar dump output is actually a great idea. You can solve the conflicts during git merge (or PRs if there would be a tea working on this) and there should be no problem.
NodeBB ES6/7
-
I was wondering if (or when) NodeBB will be refactored from it's callback style to Promise/Generator/Async style.
Do you guys (nodebb developers) think this is something we'll see in the future?Regards
-
... but in all seriousness, it's on the roadmap. First step is deprecating Node v4
@pitaj is leading the charge on that front.We're happy with es5 to be honest... we'll try to take advantage of newer features but beyond
letandconstit'll be hard to get us out of our comfort zone
That said, we'll probably never use promises, I don't like them for a variety of reasons. As they're more of a stopgap between callbacks and async/await, I'll definitely give the latter a try if it is standardized.
-
@julian I used ES async/await (Node 7?), that if I remember well are based on promises, in a university project: it was really easy to use and in my opinion the code was cleaner than with callback. It kind of felt like just a way to avoid hundreds of indentations
-
Also, did you ever thought about switching to yarn instead of npm?
-
you're gonna need Node v8 if you want the async_hooks (cls stuff)
-
@bentael well I actually used it in production with babel and node 4
-
Yeah, I'm playing around with yarn for a couple repos on my own. It's definitely more fun than running
npm i ... faster, too. -
npm@5really stepped it up. It's now insignificantly different in terms of speed. -
I like the idea of keeping the codebase with the newest LTS. I think it fits in well with our philosophy of a "Modern Web". Also, all of my code is in node 6 now, it'd be a nice benefit to not have to transpile it.
-
@Giggiux i have too, with node 0.12. but it's not stable, and there are many issues with database clients and CLS
-
Thanks @yariplus ... with that statement, at least two plugin developers I know are now writing code that cannot be used in Node 4, which is the oldest LTS we officially support.
It certainly lends credence towards the eventual dropping of Node v4 support.
