Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I'm gonna develop an e-commerce website, and also I need to develop a mobile app for the same. Which language is preferable for both the front end and back end for this development. Initially, I planned to develop using react.js, node.js and MongoDB for the web app, and react native for mobile app. But I did some research, I got confused. FYI I have good knowledge in html, css, JS and dot net.
I agree with #FelDev. Your question is basically begging for opinionated (and possibly biased) answers.
To avoid an opinionated answer, what I would do in your situation is to think farther ahead.
I would ask myself questions like... if this store ends up being popular, will so and so features offered by this framework/language be good when it comes to performance? how about scalability? also maintenance?
For a more opinionated answer, I think I would agree with you (assuming this is for a company you are working with). ReactJS is very popular on the frontend so future employees will most likely be easier to find. If not, just use whatever you like that gets the job done. If it's for educational purposes to enhance your capabilities, why not try something new by letting this be a chance to learn a new framework? etc.
I hope this helps sort of :).
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I have a really really big question which is how to write a social networking website like facebook? I want to know which language should I use and why. And also the relationship of them or the whole structure of website. Only a general idea of blue print will be all right. However I don't mind if u can tell me things in detail. Thanks in advance.
Simply put: You can't realistically without a huge team of experts and lots of money. If you're a full-stack developer I'm sure you can pull off a website that has user profiles and a commenting system just with HTML, CSS, javascript, AJAX, and something like PHP/MySQL on the backend (lots of options here). Facebook is obviously a lot more complicated than that though, especially with all the asynchronous features going on such as the chat system.
Extended answer: https://www.forbes.com/sites/quora/2013/05/20/how-is-a-facebook-like-site-actually-created-from-scratch/#71ee985bdd2d
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I see a lot of Javascript frameworks created recently since I've been learning web development (http://www.infoq.com/research/javascript-frameworks-2015). Do you know what kind of knowledge you need to know in order to create a Javascript framework in particular or any framework in general?
Creating a JS (or any other kind of) framework isn't something done easily, but some of the steps include:
Find a niche where no framework exists yet or doesn't cover a specific use-case, and where you have good knowledge of the problem space
Design and implement an easy to use (and, if required, future-proof) API
Publish it, e.g., on GitHub and advocate for it with a website or through blog posts
Maintain it
Hence, you'll need to know how to design good APIs, reasonable JS knowledge to build them and patience.
Note: while the initial fun starts with building out something, releasing and maintaining an actual framework is far more complex and requires time and effort - especially to build a community and once these users start requesting additional features, or your initial design considerations fall short of the new use-cases imposed by real-world usage. You can always build something and publish it to NPM, but be aware that maintaining a project in the open source community involves more than "writing code", and deprecating or deleting a framework/package can yield surprising results.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
We are starting a greenfield React.js project and are overwhelmed by all the options to use to "put it all together". There is Fluxxor, Fluxible, react-router, Baobab, Delorean, Marty, Reflux, just to name a few. We want to utilize the concept of unidirectional data flow and thus are not keen on using something like ember or angular in conjunction with React.
Our data will come from a Restful API we are building using Hapi.js so this is just a client application that will pull from the API.
Here are some other criteria we are considering:
Relatively minimalistic - things are changing so fast in this area
that if there's a big shake-up with React or if Relay suddenly drops
next week we should be able to either adopt the new way of doing
things, or come up with our own solution to it.
Well documented - speaks for itself
Technically sound - not prone to race conditions, preserving uni-directional flow, no glaring errors, solid code base
Active community - frequent checkins, responses to bug issues people post in git, etc
Any thoughts would be welcome!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I've got a site which isn't REST based and I'm auditing my front-end and planning on re-writing it. I enjoy using Backbone, but not taking full advantage of Backbone (since my site isn't a single page app and I'm not necessarily consuming or bootstrapping any data on page load with fetch or updating with sync.
Does it make sense to keep Backbone around or should I be looking elsewhere? Or on top of that, should I make my back-end more RESTful?
I still like using it for non-REST projects because it helps me organize my code.
If your codebase is easier to understand and easier to maintain when you use Backbone than when you don't, there's no shame in using it. Same goes for any of the other frameworks out there.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Should/does this role get recognized by the software development community?
In my mind, someone with this position would make high-level decisions on coding standards, design choices, tools and frameworks for HTML, CSS and JavaScript.
Maybe there's a better name for it? I'm trying to better state my career goals, and I need some perspective. Thanks in advance!
Yes. sufficiently complex RIAs are almost completely independent applications, and thus they need their own experts/teams.
If you have developers who are familiar with both server and client side development, then they might be able to participate in the development of both tiers of the application. However, a complex RIA can easily be as or more complex than the server, so if the app is big enough you probably need dedicated resources for both the server and the RIA, as well as possibly the DB.
Yes, the role of a software architect includes design choices, coding standards, etc. so a front-end architect would naturally make decisions regarding front-end web technologies like HTML/CSS/JavaScript, etc.