Как DVCS может помочь научному программированию?

Существуют различные проблемы, связанные с этой ошибкой. Известна ошибка с обновлением webpack-dev-server с версии 2.9.7. Самым быстрым решением было бы понизить его до v2.9.7

npm install webpack-dev-server@2.9.7 --save-dev

Кроме того, проверьте версию vuejs в вашем проекте и версию webpack, поскольку они должны быть совместимы с правильной версией wepack-dev-server тоже.

12
задан 5 revs, 3 users 49% 23 May 2017 в 11:54
поделиться

3 ответа

One big problem with DVCS for scientific programming is binary data. It is often the case that scientific programming requires input/output of gigantic files, and that kills performances very quickly on every DVCS I know of (bzr, hg, git). That's one area where svn is much better currently.

I think DVCS can be quite useful for papers as well, but that means that your collaborator knows the DVCS as well.

1
ответ дан 2 December 2019 в 23:08
поделиться

Regarding your main points:

  • "obvious advantage of DVCS": it bears repeating that, especially in an academic environment with potentially strict IT rules for not allowing external connection, the DVCS allows working with a local repository. That means you do not have to be "connected" to one central repo to access the full history of a project, and that right there could be the main contribution of DVCS to scientific programmers.

But that also mean you must have some kind of policy in order to allow any given work to "come together" and be consolidated into one repository, which does not mean there will be only one "central" base: one could imagine several central repos for several big projects. Still, that require administration (not to be under-estimated).

And that "consolidation" process can be quite difficult due to your main first point:

  • branching: the student need to branch carefully (since it is so easy). I saw my share of branch named 'toto', 'Monday', 'myName', ...: once published into another (more central) repo, what are we supposed to do with those ? If 20+ branches are to be merges in order to finalize one common code,... the process can become error-prone very quickly.

Quick comments on your other points:

  • deployment (what you call "pushing to server"): yes DVCS can be used for some kind of deployment, but that means you have organized your repo to include some kind of "release component" (the set of file you want to push on the server) and you have versionned them. And release management includes many other steps which cannot be all memorized in the DVCS, like for instance the de-variabilization process where you replace variable within configuration files with actual values adapted to the target server (port numbers, local paths, ...). You can attempt to manage those configuration files directly valued through branches, but in my experience it becomes quickly too complex to follow.

  • collaboration: that is not reserved to DVCS. (VCS offer them too). Note that for some format (Word Document), their internal revision system could be more efficient.

2
ответ дан 2 December 2019 в 23:08
поделиться

Обучение - это серьезная проблема. Я знаю немало физиков элементарных частиц (большая наука с большими проектами в области программирования), чьи общие знания об управлении исходным кодом заключаются в том, как запускать наивные версии cvs checkout , cvs update и cvs commit .

Да, CVS. Я знаю лидера группы программного обеспечения, который отложил переход на Subversion из-за этих людей.

На следующем уровне навыков они также знают команды diff и stat и как указывать ветви или теги, но можно избежать создания или объединения ветвей.

Если вы планируете внедрять DVCS, планируйте интенсивную, постоянную программу обучения и поддержки. Ученые (или, по крайней мере, физики) обычно мало формально обучаются информатике, и может иметь только смутную концепцию программного процесса.

4
ответ дан 2 December 2019 в 23:08
поделиться
Другие вопросы по тегам:

Похожие вопросы: