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
If you have 2 applications that share a lot of code. What is the general guideline before splitting the 2 applications into two different repositories?
Say they share about 80% of code and forms etc. Is it a good idea to split them or keep them together?
If they share 80% of the same code, then yes, split them into three repositories:
the common code becomes a library
first application, including the library
second application, including the library
https://en.wikipedia.org/wiki/Don't_repeat_yourself
Related
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 days ago.
Improve this question
I happen to know purego from a mailing list. It claims to use C code without CGo, which is very interesting. I would like to know if we can get rid of C entirely in Go, why the Go team does not adopt this way? In another word,
what things can CGo do while purgo can't? What's the pros and cons of purego?
I am purly interested in comparing purgo with cgo, and see if this project is worth tracking, and further more could it be adopted into future version of Go?
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
As I am interested in the concept of graphql I want to understand the benefits of graphql and when to use it?
There are many excellent online resources on this subject, for example https://philsturgeon.uk/api/2017/01/24/graphql-vs-rest-overview/
Main points from this article:
REST and GraphQL are totally different
GraphQL isn't a magic bullet, nor is it "better"
You can definitely use both at the same time
GraphQL is dope if used for the right thing
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 6 years ago.
Improve this question
I have come across both the following approaches.
To my understanding the Model and the View doesn't communicate with each other and all communications should be done through controllers thus Method 1 is the proper way. But I have come across both approaches on various articles online.
What is the proper way to implement the MVC Architecture?
Thank You
i think the 1st diagram is actually an MVP (model view presenter). see this question which eventually links here and contains this diagram for an VMP pattern with a passive view:
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
Scheme lists are slow for random access, which is a common operation in many applications such as image processing. Does this make it naturally handicapped for that kind of application?
If performance is a concern, then you should definitely consider using fixed-access-time structures. Fortunately, Scheme has lots of these, too. The "vector" is the simplest one; it's a close match to what most languages call an "array".
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 6 years ago.
Improve this question
I have a question in my exam that I don't know how to answer it:
Consider that you have a machine for personal use and you are developing various programs. Before going to lunch you want to leave five large programs to compile. In this scenario justifies what / which of the following scheduling algorithms would select: First Come First Served, Shortest Job First, Round Robin or Priority scheduling.
I'd honestly chose Shortest Job First for the simple reason that when I come back from lunch I want to have as many programs available to debug and test as possible.