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 have this web project I'm working on with a friend. However, there are problems when it comes to who should do what and when should it be done. We are using JavaScript, HTML, and CSS and we can't work on two separate computers, and ideas are always shared only when we are coding. Please help me on how or what we can use to share what to do in order to work on same project but be independent.
Using a project management tool such as https://basecamp.com/ can help you keep track of milestones and project deadlines. Its also a good way to stay in touch with your team. There are plenty of other messaging tools you can use to share ideas within a team such as https://slack.com/
When working in a team there is always the problem of stepping on eachothers toes. You might need to edit a particular file, but someone else is working on it, or has made changes to it since you last took a copy. How do you both keep up to date with the code the other has written? Well this is where you want VC (Version Control). There are a few big names out there such as SVN, but by far the most popular is a Git (hopefully you have already heard/used it).
Install git https://git-scm.com/ and you can commit your code. You can then push your code to an online repository such as GitHub https://github.com/. Using GitHub means that you can both push your code up and pull code down to ensure you both have the changes the other has commited.
You may also find a need to track bugs and features you need to implement, when they need to be done by and who will do it. You can use tools such a Jira https://www.atlassian.com/software/jira or Visual Studio Team services (Im sure theres free alternatives that are a bit more lightweight). In essence you log tasks that need to be done on a project such as fixing a bug. Then you assign it to a person and allocate it to a sprint (sprints are a period of time you are going to work before meeting with your team and reviewing priorities and work completed, typically a sprint is 1 or 2 weeks).
I hope this helps.
At the bare minimum I would suggest that you
Set up a project repository with a version control system (e.g. on GitHub)
Use a hypervisor like VirtualBox to set up independent virtual machines on the host machine. With this you can set up your own independent environments without affecting the other person's workflow.
Note: this assumes that only one person will be using the host machine at a time.
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 2 years ago.
Improve this question
I ma looking to do a course and a a tutorial form youtube.
This project more specifically as it has a lot of features I would like to learn and my back-end knowledge is very basic currently.
[Project][1]
https://www.youtube.com/watch?v=m_u6P5k0vP0&t=584s
Since the video was released firebase plans have changed and you read tales of huge bills.
Is there a way to avoid this? and if anyone knows the project will I be safe from billing whilst building it? The project will never be published anywhere, just used by me for practise and testing which seems fine as the limits for free users are quite big. I just have some fear from reading horror stories of accidental loops and the like!
Any help or advice on this is welcome
I don't think you should be worried about racking up huge bills if you're not going to publish the project anywhere and if you're on the free plan they literally can't bill you. even if you decide the project is really cool and you want to publish it you won't have to use their other plans unless for specific reasons (like cloud functions for example). So basically don't worry it's a really good platform to help with your development. I myself have done tons of projects where I used firebase in the backend and it's been great.
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 6 years ago.
Improve this question
I am trying to make a BTLE App using UWP in JS. I cannot find any examples and I cannot understand the documentations. Can anyone help me out and point me in the right direction as to from where should I begin?
In using VS2015 Community Edition w/ Windows 10 SDK Build 14393. My phone is also 14393 so is my PC. I can compile the app but I don't know from where to begin.
EDIT:
The way the docs are, is quiet confusing. Like in this page this is an example.
var bluetoothLEDevice = device;
This does not state where this this device variable came from, it took me a while to file the link between this and the BluetoothDevice Class but still it was unclear on how I am supposed to use it. There are no code blocks to liked in the page. Microsoft maintains a GitHut hub account so it will be great for NEWBs like me to see a working example or related example for all the supported languages on GitHub (I know it's a lot, but Microsoft is a big cooperation so it is possible), linked on the Class pages.
Thank you for understanding what was I trying to say #Grace Feng - MSFT.
I cannot find any examples and I cannot understand the documentations.
If you're asking for one official UWP BLE sample which is wrote in JS, I'm afraid to tell you that there is no such one.
By not understanding the documentations, you mean you don't understand the code sample in those documents? We don't know that blocks you, next time when you ask a question, you'd better share us your code the point what exactly the problem is.
I can compile the app but I don't know from where to begin.
To get started, I think it's better to stick to the official document Bluetooth GATT and the official Bluetooth Low Energy client sample, you can try to adapter it to JS code, what you need is checking the js Apis which are used in those samples, for example GattCharacteristic class.
The official Bluetooth advertisement sample has a code sample in js version, it demonstrates use of the Bluetooth Advertisement Runtime API to send and receive Bluetooth Low Energy advertisements. Maybe you can also take a look to get started.
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 am curious as to the fundamental reasons why we choose MongoDB, Node.js, Express.js, and AngularJS?
Here are the reasons I can think of:
MongoDB works well with JSON and data models, is faster than SQL;
Express and Angular gives the stack one language in Javascript;
Node.js is non-blocking, event based, and supports concurrency;
Angular is a wonderful front end framework.
Any other reasons? Also, how would you address the people who have an innate disdain for server side Javascript?
Thanks!
Well, people wanted to replace the LAMP stack (Linux, Apache, MySQL, and PHP/Python/Perl) for a very long time. When JavaScript was made possible to run on the Server side ie NodeJS, it paved way for a full development stack which is the MEAN stack.
The first advantage of the stack is the single language throughout the whole application - JavaScript. This made it easier for a person with JS knowledge to create a full on working application. This also made way for front end developers to explore more into how server side programming works.
Some startups and organizations thought that using a stack with one language will help them in limiting their resources. And easy delegation of work among the developers.
Even though MEAN stack is an awesome alternative to the traditional LAMP stack, it is still in its early stages. It is adopted only by few ambitious startups, but not by bigger organizations. They are still sticking to the legacy technologies. Also the components of the MEAN stack which is Angular, Express and Node are still in their childhood stages. There are no proven and complete use of the MEAN stack on a full scale solution.
Well organizations like Walmart etc. used Hapi.js and were successful in it, it tempts the other organizations to go forward with it , but also makes them skeptical on using it since replacing the already existing technology will be a bigger headache.
Also since a lot of the current employees are trained in Java, Python etc, developers in JavaScript are very few and JS is almost considered as an additional language to be known for a Java developer and the likes. JS hasn't been considered as a single language on its own.
Maybe few years down the line, the MEAN stack will prove itself a noteworthy alternative to the traditional stacks.
I work in the Retail Domain and a big organization. We are actually planning to use the MEAN stack for our inside projects. But no one ever gave a simple thought of using the MEAN stack in PROD.
EDIT: One more important reason these stacks are tempting is because they are all Open Source. Say MongoDB for example. Owning the software license every year is a big hit on the profits of the organizations with DB's like Oracle SQL etc. Going with an Open Source DB is a very cost effective option. But still they are skeptical on using it for Production.
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 9 years ago.
Improve this question
I have a question about the design of a web application with JavaScript: Should a web application be designed to work without JavaScript, and then later add JavaScript for users that have it? Or should I design a web application with JavaScript in mind and then add fallback functionality for user that do not have JavaScript.
I hope this question makes sense. Let me know if you need me to clarify something.
Thanks.
The terms, that describe what you are looking for are "Progressive Enhancement" and "Graceful Degradation".
Here is good article describing what you already have in your question in more detail:
A List Apart: Understanding Progressive Enhancement
An article that could help you on your decision:
Dev.Opera: Graceful degradation versus progressive enhancement (The named reasons are still valid, despite the fact that the article is marked as outdated)
I favor progressive enhancement in most cases, since it is more accessible when it comes to different output devices, software and the capabilities of the user using that website.
Answers like "there are so few people with JavaScript disabled" are just one side of the medal. Not relying on JS also could improve your site experience to non-graphical clients like search engine robots (how should they load AJAX content, when that is only accessible via JS?) or screen reader software. In fact there are many more good reasons not to rely on on JS.
At this time of age there are so few people with javascript disabled, that there is no signifcant benefit for creating a static version. Try to imagine who is your visitor and if he/she would even know how to disable it.
I suggest you to design a web application with JavaScript in mind and then add fallback functionality for user that do not have JavaScript.
Now a days everything runs on JS only. You should create some kind of services/API on server side and a separate project for UI, this is the trend being followed these days.
UI project can be based on any JS framework or it can even be a simple MVC/.net project. This approach can decouple stuff, and thereafter you can create 2 UI projects one for JS users and one for the users who do not have JS.
seems a bit of a work but, it will pay in the long run.
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 9 years ago.
Improve this question
I have just watched the meteor.js screencast and I'm quite blown away by how easy building a web application with it seems, in terms of live updates and database synchronisation. However, I am not sure of how well it would scale once it's live.
What problems (potential or real) could I have if I decide to build and deploy a web application written on meteor.js?
Well, I would advice you have a play about with meteor and make the judgement yourself. It really depends on what you wish to develop
Certain constraints I have found are
Meteor comes bundled with only mongodb. Other database support are planned for later releases
No model/object form binding (in road map)
Package system is not npm (although Meteor is built on node) and is closed to community. All meteor packages are developed by meteor themselves
Regarding performance, I found this article helpful
Here is another link to meteors roadmap
From my experience, I would say the advantages I have found outweigh any disadvantages at the moment
Having built client projects in meteor there is 2 things I immediately found hindering about the system:
1) No native support for MSSQL / MySQL or in fact any other DB than MongoDB (which jamin mentioned). That said, it sort of makes sense as to why this is the case, as a NoSQL solution with an easy to use JS api makes sense over a clunk RDMB database. However there is a plugin called Meteor SQL which supports MySQL at the moment https://github.com/drorm/meteor-sql
2) No native support for windows - Meteor is only released on linux & OSX meaning us windows users are out of the loop. There is an unofficial windows build on http://win.meteor.com but it's stuck at 0.5.9.
I probably wouldn't recommend building full sites out of Meteor yet as well due to it's various instabilities - https://github.com/meteor/meteor/issues however in a controlled environment it's perfect.
Also bear in mind Meteor have achieved an $11m funding grant - http://venturebeat.com/2012/07/25/meteor-funding/ meaning it will continue to improve and grow.
A huge problem for Application development are missing things like validation or translation.
You have todo everything on your own an include and use many external sources.
NPM support is not optimal, for backend usage ok, but in frontend a hack.