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
A word-processor has most if not all the features of a version control software without the gobbledegook and the complexity. You can set a word-processor to always keep history and probably save as versions every time you save. You could have an online word-processor- if one doesn't exist then it sounds like a great opportunity- with general access to allow multiple users to access it. Git and others are acknowledged to have multiple issues but I can't see a word-processor having big issues so why the preference for version control software?
Word processors, as far as I know, do not track versions of directory structures (trees) of files as a whole... .they only track single files. A version control system treats a "snapshot" of a whole tree of files as a single unit.
Online word processors do not support multiple authors working on the same file independently... instead they assume that multiple authors are collaborating in real time, working on exactly the same thing, which is not the usual workflow for software development.
Word processors do not support the concept of branches, which are a powerful tool for many software development use cases
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
Do you know any good tools to support the translation of .arb files?
It's a standard for Flutter and since Google Translator Toolkit will be sunset soon (https://support.google.com/translatortoolkit/answer/9462068) we're searching for a good solution to translate/gather our translations
Edit (June 2020): There's great new open source project called Arbify. This is a self-hosted tool to manage multiple translation projects focused on Flutter. You can edit arb files and fetch them via Dart package tool.
Aside from that some services like POEditor have announced basic support for ARB too.
At the moment the best support for arb files is on Localizely. However, this is a paid service and has strict limits on a free version. It allows to export arb translation files with plurals and placeholder support. It doesn't support genders, though.
There is also one simple web editor and one desktop editor (Babel) that support arb files.
Crowdin supports .arb:
https://support.crowdin.com/supported-formats/
It is also able to pull the data from a Git repo and send Pull Requests on GitHub.
However, when I used it in 2018 there was a problem of ##last_modified attribute being updated without any other changes to the translation files, causing lots of churn in PRs. By that time, they were reluctant to improve the situation (based on email conversation with their support), so we resorted to manual edits.
https://localise.biz/ allows 2000 translations. Which I assume are 1000 strings in 2 languages or ~666 strings in 3 languages and so on. Which is more than https://localizely.com/ 150 strings
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
We're evaluating ITextSharp (now known as IText) for producing pdf documents. This will be used in our websites which will be published across a load-balanced solution amongst several servers.
According to Itext, this will require a production license per server (we're not open-source) in our load balanced configuration, as well as uat and developer licenses. This is obviously a considerable investment.
Could anyone recommend any alternatives to reduce the costs?
Also, is there a pattern we could adopt to minimise the migration effort of the existing website prototype if we were to use another product?
You could change your architecture a bit and have a dedicated PDF generation server. You'd then need to boil your requests down to something that could be sent between the servers. Depending on your goals, that could be something relatively simple, such as a user ID and a report name, or complex (text layout, that image there).
As far as distancing yourself from the commercial iText, there are two options.
1) Use the older MPL iTextSharp. It won't have all the latest features and bugfixes, but it's hard to beat the price.
2) The "wrapper" design pattern. Build a relatively generic interface, and have your current implementation of that interface sit atop iText. If you later need to swap it out, you're rebuilding the glue code, not your whole app.
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
So I'm curious about this. I assume the building of operating systems is a monumental task, especially with all the back end stuff that an os involves. I was curious if I wanted to rework the front end of an operating system, but take advantage of existing architecture/backend, what would be the best resources to use? Also, can you guys point to any examples of well designed front ends of operating systems that aren't really mainstream? It seems like everyone uses pretty large well known OS.
Yes, you can. But like you said, it's a huge, huge task. I am not sure of windows or mac, but in Linux you have options to do so. You can download a Kernel from https://www.kernel.org/ and write applications around it.
If your goal is to make applications around the kernel, then look at linux application development resources. Check out linux desktop environments https://en.wikipedia.org/wiki/Desktop_environment#History_and_common_use to see which one is good.
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
For the past several years, I've been making small (single file, 1-500 line) scripts (mostly bash & python) to automate random tasks (usually scientific data analysis). Most of these end up being one-offs, but sometimes I want to go back and revisit/change something, or end up with a rather unwieldy script that could benefit from some sort of version control. I should note that all of these scripts are done solely on my own, and don't necessarily need to be share-able.
Which type of versioning (SVN,CVS,git,Mercurial..) Has the simplest command structure/syntax for my use case? More importantly, the machines I connect to are behind rather finicky kerberos walls, so I'm not looking for any sophisticated server-based implementation.
I found this thread from 2010 asking a similar question, though it didn't really talk about specific options, just whether or not I should be using a single repository.
In short, which versioning system allows for simple same-directory approach with minimal bells & whistles (only checkouts and commits needed)?
Should I set up some sort of subversion/CVS/git repository and just throw everything in?
Yes.
For your use-case, I suppose, SVN can be best choice (with URL-based access to every object in repo you can easy and fast get access to any single file any revision of file and for your linear history "not the best" merge in SVN isn't problem). Local file:///-based repository will require minimum of maintenance. You can use single-repository, flat tree (all files in /trunk)
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am building a system that will allow users to upload Word, PDF, and Zip files.
Sometimes, they will review those files and upload newer versions. I will need to keep the older versions too, as they would also like to have the ability to download them.
Instead of storing all versions in full, I would rather store the first versions, and diffs for the successive versions. Basically, I need to store all versions of a document in the smallest possible space. (Maybe it can be done in a different way, without diffs?).
There is no need for merging changes, multi-user, distributed, or any advanced features that typically come with version control systems. All use of the tool will be made through my application.
Is there an easy-to-learn, lightweight, open-source package, with good JVM (or REST) interoperability, that I can use for this purpose?
No needs for reinventing the wheels.
JavaHL or SVNKit will allow you to work with Subversion repositories from Java