ASP.NET Javascript frameworks now [closed] - javascript

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
Im new in Web development and i try to improve as much as possible in ASP.NET MVC. Right now Im looking for good javascripts frameworks, that I can use in my projects and I found two options :
angular - right now we waiting for version 2.0
knockout
Already I know how to use jquery, bootstrap and materialize.
Could someone help me, which one framework should I choose to learn right now? Is knockout still worth learning or should I learn 1.x angular version and wait for 2 or maybe should i learn another javascript framework?
Thanks for every answer!

A quick google search gave me this,
Angular.js is the front-runner of the JavaScript frameworks, and is one of the most popular JavaScript frameworks out there.
Angular.js was released in 2009 by Google, and no one would have guessed that it will become so popular in the near future. Angular.js gives the power in the hands of the programmer and lets them build single page web apps.
Backbone.js is minimalistic JavaScript frameworks that aim to provide the necessary backbone to a web application. The framework is open source in nature and is available under the MIT license.
React.js is one of the most popular front-end JavaScript framework.
Why Front-end? Becuase it can easily used to create the UI part of your project. In simple words, it acts as the V in MVC. The magic is achieved by using a virtual DOM and it can also be rendered on the server side with the help of the node.js.
Knockout is a MV (Model – View) Javascript Framework which specializes in easy declarative bindings, automatic UI updation (on change in the model state) as well as powerful templating features. Knockout is built on pure Javascript, without any external dependencies. It also happens to work on most browsers.
there are many other great names in this list,
First of all It all depends on your project requirements to use any framework
but for learning purpose i would suggest starting from jquery
You can start your learning from jquery and then you can extend it to Angular or Knockout these two are very much popular these days and are very helpful for developers.

Related

Should I use UI framework with three.js or vanilla-js to create an dynamic UI? [closed]

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 5 years ago.
Improve this question
I am trying to develop a 3d-editor with three.js. I know javascript and three.js but I am not familiar with web-dev in depth and never tried UI frameworks. While mrdoob's editor uses plain javascript for UI elements, I am not sure which method will be more beneficial for me? To use a framework like react.js or vue.js; or go with plain javascript for UI elements.
Project owner planning to have dynamic and complex UI elements like a tutorial wizard, a console or fields that will be dynamically change with data coming from server.
So what are the benefits and drawbacks of using pure js or frameworks, considering it will be a three.js project.
And should I use library's like react-three or vue-threejs, or start with integrating three.js scene to framework for the sake of stability?
First you need to understand what is those framework trying to do for you
React, Vue, Angular is abstracting DOM manipulation when state changes. And they are mature enough to adopt in production
react-three, vue-threejs is abstracting Canvas/SVG/WebGL manipulation away when state changes.
In theory it is possible to build every product without any framework. But using them will save lots of time and give huge benifit for maintainability. But you need to put effort to learn it first.
So my answer is that for
Small/POC project - If you are not familiar with those frameworks, go ahead with plain javascript, jQuery to manipulate DOM and canvas directly. But highly recommended to learn and use these frameworks in the future. It will increase your dev speed insanely
Large/Long-term project - Do use React/Vue/Angular. Leverage your risk in adopting react-three/vue-threejs
UI frameworks are great, they have done a lot of the hard work for you. Personally I really like VueJS, it's very lightweight but extremely powerful when it comes to creating SPAs. And from what you have said someone has already created a vue-three plugin

Which forms of JavaScript for intermediate-level Rails developer, only dev on team? [closed]

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 am acting as web developer for a small startup, taking over as the only in-house developer to maintain and adapt the application that was initially put together by a team of contractors. I would consider myself to be at an intermediate level with Ruby on Rails. I know enough about front end technologies like HTML and CSS to use Bootstrap or Foundation effectively and write my own tweaks when necessary. However, I only can read the JavaScript code of other developers well enough to make small modifications to what's already in place.
I would like to become proficient in JavaScript to help round out my skillset but there seem to be a lot of JavaScript "options" out there and I'm not sure what's on the way in, what's on the way out, what's popular, what's most useful, easiest to start with, best fit for Rails applications and so forth. And by "options" I mean "regular" Javascript, jQuery, Node, Angular, etc etc.
In hopes that my question will meet SO terms as "answerable" I'd like to focus on the question of what kind of Javascript fits best with Rails and which technologies are the most generally relevant today (i.e. not on the way out of popularity already).
Your choice should depend on what you're doing. One case might be using Rails primarily on the back-end, pulling data from it, and then generating your markup and displaying content primarily on the front-end with JavaScript. In that case, you should look into a JavaScript framework like Ember.js or AngularJS. If you're going to be generating your markup primarily on the back-end with Rails, having that markup being pre-populated with content before being sent to the user, you might be better off using jQuery for DOM manipulation and the occasional AJAX request to your Rails back-end.
In the case you're looking for a framework: Yehuda Katz is a leading voice in the Ruby on Rails core team, and has a similar role inside of the Ember.js project. While this isn't strictly objective, I'd say that Ember is the JavaScript framework that most closely matches "The Rails Way". That said, any framework will integrate well if you're using Rails as a backend, and AngularJS is currently more popular and might be easier if you're looking for examples and helper libraries.
I'd like to point out that Ember is just a framework, just like jQuery is just a library. Knowing JavaScript from the bottom up is a very helpful thing when working with anyone's code. I highly recommend checking out the Learn JavaScript page on MDN, and maybe picking up a copy of JavaScript: the Good Parts by Douglas Crockford. The former has a bunch of free information about getting up to speed on JavaScript. The latter is a dense, and somewhat controversial book, but (in my opinion) is one of the best books about dealing with the language's rough edges.

simplify web front-end development [closed]

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 have developed some web projects, to me, the back-end part is clear & easy, but the front-end part is complex & time assuming, because make a page dynamic & smart need write a lot javascript & css, especially when need to make some components like grid / tree / form validation.
I hope to simplify the process of front-end development, I have used jqueryUI/extjs, extjs is very powerful but heavy & complex, jqueryUI is simple but not enough. I also checked angularJs a little, but it feels defined a new language, and I like it because it makes html grammar like a jsp/php file.
Currently, for management system I use extjs, for web system that face users I use js/css/jqueryUI, but I still don't feel it's simple enough, especially when I write js/css, there are too much code.
So what is your solution?
I would definitely recommend AngularJS for your solution. Jquery is not enough for building complex web applications.
I would argue against feel boring & stupid when using it. Angular JS is a very powerful framework for building scaleable webapps. Its learning curve is steep though that might explain you feel bored and stupid.
For CSS, go for either LESS or SASS pre-processors.
http://lesscss.org/
http://sass-lang.com/
All of this should be coupled with grunt.js to minify and build all your artifacts.

SAP UI5 versus other Javascript frameworks? [closed]

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 9 years ago.
Improve this question
Just wanted to understand where does SAPUI5 stand as a framework.
(1)Is it like jQuery (library with host of utility functions, effects, animations etc)
or
(2)Is it like a MVC library like Backbone,Angular,Ember etc?
If 1, then how could it possibly supersede jQuery?
If 2, then what advantages & disadvantages would it have over these
other frameworks.
Apart from the fact that it's SAP's proprietary framework what really i would like to know is the principles & philosophy behind this framework, and how does it stand the test of time in front-end regarding-
MV* philosophy of building applications
building single-page applications
learning curve along with other frameworks like Backbone, Angular
(I mean if i learn SAPUI-5 does my learning curve for other
frameworks increase or decrease or how can it affect that)
And lastly can (if there is!) I create an ecosystem of SAPUI5 with other frameworks.
This is rather a large question that is in danger of having a very long answer, one which is also subject to opinion as well as fact. But I'll have a go.
First there's the "which toolkit" question. There's SAPUI5 which is the name of what the toolkit originally took (and still has), and this is subject to certain SAP licence restrictions. Since December 2013 there's also OpenUI5 which is the Open Sourced version of the same toolkit (minus a few things currently, but for the most part the same). And when people refer to UI5 they're collectively referring to both SAPUI5 and OpenUI5.
So while "SAPUI5" is proprietary, its sibling "OpenUI5" is very much Open Source.
UI5 is a full featured toolkit that includes, amongst other things:
MVC
data binding with support for JSON, XML and OData out of the box
module loading and management
support for component-based app creation
internationalisation (incl. RTL support)
routing
different libraries of controls e.g. rich desktop-specific controls in the sap.ui.commons and sap.ui.table namespaces, plus responsive controls for smartphone/tablet/desktop in the sap.m namespace (on which the SAP Fiori application suites are built)
To your question on jQuery - it uses jQuery and many other libraries, and builds upon them, so it's not a competitor for jQuery or a replacement for it. In fact, from personal experience, I'm not a jQuery expert but I build apps with UI5 just fine.
To your question on advantages and disadvantages vs other MV* frameworks, I don't think there's space in this answer to tackle such a wide-ranging question.
Not sure what you mean by standing the test of time regarding MV*; MVC has been around as a concept since almost the beginning of time, so I guess that has stood the test; UI5 is relatively young (2-3 years) so still has to prove itself in terms of years, but it's doing rather well so far if you consider the large scale of app development that's happening with it in the SAP world.
Learning curve? I'm traditionally a backend / integration developer and I picked up UI5 without too much bother. Difficult to answer the question without knowing your skillset and desire to embrace it.
Ecosystem inside SAPUI5? Not sure I understand that question.
Hope that helps a bit.

Deciding between: dojo, backbone.js, knockout.js (or other) for Rails 3.1 app [closed]

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
We have an existing Rails 3.1 consumer-facing web app and are reworking the UI to be far more interactive, snappy, app-like.
We have a modestly complex data model, but there's only a modest need for form-based user input.
We use jQuery now, with plugins to do nice effects, but overall, our JS skills are weak.
Our primary objective is to find a framework that helps us structure and organize our JS code and simplify the cases where we do have data bindings, AJAX, etc. in our Rails 3.1 world.
We'll learn how to do JS properly, but while we do, is there a clear framework we could learn and work within?
I don't know Dojo, but Backbone vs Knockout is a bit like comparing apples to oranges.
Backbone provides a structure for a web application + synchronization with the backend, whereas Knockout drives UI updates. There is some overlap between the two, but it doesn't mean they are actual competitors. There is even a project that tries to combine both - Knockback.
Last but not least, there is a great discussion on Bb vs Ko.
EDIT: I've just found this: http://addyosmani.github.com/todomvc/ - a comparison of different approaches to creating the same TODO app.

Categories