Difference / Benefits of the below React methods?
I'm fairly new to ReactJS and have been learning a bit and JSX. I'm converting my personal website from HTML/JS to React.
What is the difference in using for example:
React.createElement("div", {className: "row"}, ------)
and in JSX (with a corresponding component of "LayoutRowDiv.js" doing the exact above, really.
<LayoutRowDiv> ------------- </LayoutRowDiv>
Which would be best practice? I've coded a bit of my homepage using both methods and to be honest, the first version looks cleaner?
Just looking some opinions and thoughts as maybe I'm misunderstanding something.
I've attached both the snippets.
javascript reactjs react-native jsx
asked Nov 22 '18 at 11:38
93Alan93Alan
2310
add a comment |
I'm fairly new to ReactJS and have been learning a bit and JSX. I'm converting my personal website from HTML/JS to React.
What is the difference in using for example:
React.createElement("div", {className: "row"}, ------)
and in JSX (with a corresponding component of "LayoutRowDiv.js" doing the exact above, really.
<LayoutRowDiv> ------------- </LayoutRowDiv>
Which would be best practice? I've coded a bit of my homepage using both methods and to be honest, the first version looks cleaner?
Just looking some opinions and thoughts as maybe I'm misunderstanding something.
I've attached both the snippets.
javascript reactjs react-native jsx
asked Nov 22 '18 at 11:38
93Alan93Alan
2310
add a comment |
I'm fairly new to ReactJS and have been learning a bit and JSX. I'm converting my personal website from HTML/JS to React.
What is the difference in using for example:
React.createElement("div", {className: "row"}, ------)
and in JSX (with a corresponding component of "LayoutRowDiv.js" doing the exact above, really.
<LayoutRowDiv> ------------- </LayoutRowDiv>
Which would be best practice? I've coded a bit of my homepage using both methods and to be honest, the first version looks cleaner?
Just looking some opinions and thoughts as maybe I'm misunderstanding something.
I've attached both the snippets.
javascript reactjs react-native jsx
asked Nov 22 '18 at 11:38
93Alan93Alan
2310
I'm fairly new to ReactJS and have been learning a bit and JSX. I'm converting my personal website from HTML/JS to React.
What is the difference in using for example:
React.createElement("div", {className: "row"}, ------)
and in JSX (with a corresponding component of "LayoutRowDiv.js" doing the exact above, really.
<LayoutRowDiv> ------------- </LayoutRowDiv>
Which would be best practice? I've coded a bit of my homepage using both methods and to be honest, the first version looks cleaner?
Just looking some opinions and thoughts as maybe I'm misunderstanding something.
I've attached both the snippets.
javascript reactjs react-native jsx
javascript reactjs react-native jsx
asked Nov 22 '18 at 11:38
93Alan93Alan
2310
asked Nov 22 '18 at 11:38
93Alan93Alan
2310
asked Nov 22 '18 at 11:38
93Alan93Alan
2310
asked Nov 22 '18 at 11:38
93Alan93Alan
2310
asked Nov 22 '18 at 11:38
93Alan93Alan
2310
2310
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The JSX is just a syntatic sugar over React.createElement with no added functionality. Its is more of a developer preference on which should be used. Apart from the fact that you would be saving a few babel modules and steps during build time which is close to negligible impact to performance if you chose React.createElement, I would say both fare the same.
Read more here
answered Nov 22 '18 at 11:43
EaswarEaswar
7598
1
This is brilliant - Exactly what i wanted to hear. I thought I was going crazy thinking which I should use. I obviously understand that some Elements would be better as a component to reduce code duplication. Thank you for your answer, completely set my mind at peace now!
– 93Alan
Nov 22 '18 at 11:46
@93Alan Happy to help. Please accept the answer if it clarifies your doubt.
– Easwar
Nov 22 '18 at 12:04
1
done! Thanks again
– 93Alan
Nov 22 '18 at 12:06
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430168%2fdifference-benefits-of-the-below-react-methods%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The JSX is just a syntatic sugar over React.createElement with no added functionality. Its is more of a developer preference on which should be used. Apart from the fact that you would be saving a few babel modules and steps during build time which is close to negligible impact to performance if you chose React.createElement, I would say both fare the same.
Read more here
answered Nov 22 '18 at 11:43
EaswarEaswar
7598
1
This is brilliant - Exactly what i wanted to hear. I thought I was going crazy thinking which I should use. I obviously understand that some Elements would be better as a component to reduce code duplication. Thank you for your answer, completely set my mind at peace now!
– 93Alan
Nov 22 '18 at 11:46
@93Alan Happy to help. Please accept the answer if it clarifies your doubt.
– Easwar
Nov 22 '18 at 12:04
1
done! Thanks again
– 93Alan
Nov 22 '18 at 12:06
add a comment |
The JSX is just a syntatic sugar over React.createElement with no added functionality. Its is more of a developer preference on which should be used. Apart from the fact that you would be saving a few babel modules and steps during build time which is close to negligible impact to performance if you chose React.createElement, I would say both fare the same.
Read more here
answered Nov 22 '18 at 11:43
EaswarEaswar
7598
1
This is brilliant - Exactly what i wanted to hear. I thought I was going crazy thinking which I should use. I obviously understand that some Elements would be better as a component to reduce code duplication. Thank you for your answer, completely set my mind at peace now!
– 93Alan
Nov 22 '18 at 11:46
@93Alan Happy to help. Please accept the answer if it clarifies your doubt.
– Easwar
Nov 22 '18 at 12:04
1
done! Thanks again
– 93Alan
Nov 22 '18 at 12:06
add a comment |
The JSX is just a syntatic sugar over React.createElement with no added functionality. Its is more of a developer preference on which should be used. Apart from the fact that you would be saving a few babel modules and steps during build time which is close to negligible impact to performance if you chose React.createElement, I would say both fare the same.
Read more here
answered Nov 22 '18 at 11:43
EaswarEaswar
7598
The JSX is just a syntatic sugar over React.createElement with no added functionality. Its is more of a developer preference on which should be used. Apart from the fact that you would be saving a few babel modules and steps during build time which is close to negligible impact to performance if you chose React.createElement, I would say both fare the same.
Read more here
answered Nov 22 '18 at 11:43
EaswarEaswar
7598
answered Nov 22 '18 at 11:43
EaswarEaswar
7598
answered Nov 22 '18 at 11:43
EaswarEaswar
7598
answered Nov 22 '18 at 11:43
EaswarEaswar
7598
7598
1
This is brilliant - Exactly what i wanted to hear. I thought I was going crazy thinking which I should use. I obviously understand that some Elements would be better as a component to reduce code duplication. Thank you for your answer, completely set my mind at peace now!
– 93Alan
Nov 22 '18 at 11:46
@93Alan Happy to help. Please accept the answer if it clarifies your doubt.
– Easwar
Nov 22 '18 at 12:04
1
done! Thanks again
– 93Alan
Nov 22 '18 at 12:06
add a comment |
1
This is brilliant - Exactly what i wanted to hear. I thought I was going crazy thinking which I should use. I obviously understand that some Elements would be better as a component to reduce code duplication. Thank you for your answer, completely set my mind at peace now!
– 93Alan
Nov 22 '18 at 11:46
@93Alan Happy to help. Please accept the answer if it clarifies your doubt.
– Easwar
Nov 22 '18 at 12:04
1
done! Thanks again
– 93Alan
Nov 22 '18 at 12:06
1
1
This is brilliant - Exactly what i wanted to hear. I thought I was going crazy thinking which I should use. I obviously understand that some Elements would be better as a component to reduce code duplication. Thank you for your answer, completely set my mind at peace now!
– 93Alan
Nov 22 '18 at 11:46
This is brilliant - Exactly what i wanted to hear. I thought I was going crazy thinking which I should use. I obviously understand that some Elements would be better as a component to reduce code duplication. Thank you for your answer, completely set my mind at peace now!
– 93Alan
Nov 22 '18 at 11:46
@93Alan Happy to help. Please accept the answer if it clarifies your doubt.
– Easwar
Nov 22 '18 at 12:04
@93Alan Happy to help. Please accept the answer if it clarifies your doubt.
– Easwar
Nov 22 '18 at 12:04
1
1
done! Thanks again
– 93Alan
Nov 22 '18 at 12:06
done! Thanks again
– 93Alan
Nov 22 '18 at 12:06
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430168%2fdifference-benefits-of-the-below-react-methods%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
