JSX is no longer my friend
medium.com
JSX is no longer my friend
1–10 of 144 posts
Re: JSX is no longer my friend
#2I very much like how the recommended Hyperscript looks, but the package was last updated last December, and it doesn't even list React 0.14 in the compatibility list: it stops at v0.13, which was released in May 2015. Half a year before the last update of Hyperscript.
It's arguably a small package that you could just rewrite if things go wrong, but is it a smart idea to base any project on semi-abandoned code?
Re: JSX is no longer my friend
#3I very much like how the recommended Hyperscript looks, but the package was last updated last December, and it doesn't even list React 0.14 in the compatibility list: it stops at v0.13, which was released in May 2015. Half a year before the last update of Hyperscript. It's arguably a small package that you could just rewrite if things go wrong, but is it a smart idea to base any project on semi-abandoned code?
That's what I don't like about a lot of bleeding-edge web development. You end up depending on a half-dozen abandoned pet projects. Somebody had an itch, scratched it, got bored.
I swear half of the gulp eco-system is just that - half-abandoned, half-working little cute plugins that someone did because someone else's plugin, even though 99% identical, didn't do the one thing they wanted, so they wrote their own and then abandoned it, instead of maybe contributing to the other one. Sometimes, web development frameworks and libraries just feel like a giant software ghetto - a giant web of dependencies that someone combined into something with little thought given to long-term maintainability.
One of my team members refuses to incorporate a dependency that is by "some guy" and hasn't had any commit activity in the last month.
Re: JSX is no longer my friend
#4The thing that the author misses is that JSX is very natural for designers. If you properly encapsulate any logic into methods on the component rather than having it all inline in the render return, even designers with mediocre technical skills can productively work with JSX files. This can be a huge productivity win, and beyond that honestly I don't know many engineers that enjoy translating designer mock-ups.
Re: JSX is no longer my friend
#5The thing that the author misses is that JSX is very natural for designers. If you properly encapsulate any logic into methods on the component rather than having it all inline in the render return, even designers with mediocre technical skills can productively work with JSX files. This can be a huge productivity win, and beyond that honestly I don't know many engineers that enjoy translating designer mock-ups.
JSX is also very natural for people who've written HTML for years.
I wasn't a fan when I started, but now I love it to bits.
Re: JSX is no longer my friend
#6JSX always looked like an abomination to me. Don't know a single person who uses it
Re: JSX is no longer my friend
#7JSX always looked like an abomination to me. Don't know a single person who uses it
Know several teams using it personally, and am "internetically" aware of thousands upon thousands of programmers than use it. Maybe do a GitHub search?
It's nothing more than a DSL for a templating language that finally puts the template for a component where it belongs -- along with the presentation logic.
Re: JSX is no longer my friend
#8no offense to the author, seems like hyperscript has achieved what it hopes... but the benefits of not having to learn some confusing piece of JSX-ness do not seem to outweigh the cost of h('strong','uglify')-ing everything from a legibility standpoint.
disclaimer: only read the README, didn't try actually using hyperscript.
Re: JSX is no longer my friend
#9This article includes a tweet which demonstrates a very contrived example of a for loop using JSX. If you're ever writing code like this, please reevaluate your career in software development.
As an aside, we recently moved from Nunjucks templates to React / JSX at work and the frontend team couldn't be more pleased. Components reflect improvements made to them across the board and provide a happy medium between designer and JS dev. I have also found a lot of power in refs by implementing superclass functions that provide reusable logic for elements based on the key of the ref when certain functions are implemented on the corresponding component. This can be used for state persistence in forms, analytics or anything else the developer imagines.
Context switching has not been an issue but all of our frontend devs also do work on the backend. This may be an issue to consider for teams that don't embrace cross disciplinary roles.
Re: JSX is no longer my friend
#10This article includes a tweet which demonstrates a very contrived example of a for loop using JSX. If you're ever writing code like this, please reevaluate your career in software development. As an aside, we recently moved from Nunjucks templates to React / JSX at work and the frontend team couldn't be more pleased. Components reflect improvements made to them across the board and provide a happy medium between desi…
"If you're ever writing code like this, please reevaluate your career in software development."
That's a pretty nasty comment to make about anyone in this industry over a simple for loop.