Are the jcl and jvcl libraries still alive?

[dummzeuch 1656]

35 minutes ago, Fr0sT.Brutal said:

Disagree.

You have every right to disagree. But so have I and Angus.

[Fr0sT.Brutal 903]

44 minutes ago, dummzeuch said:

You have every right to disagree. But so have I and Angus.

Absolutely! That's why I say "disagree" instead of "you're wrong" 😉

Anyway the complexity of Git is overestimated (especially for most usual operations). Contrary, after getting used to Git I was confused by SVN. All these awkward branches, strictly straight commit history, online-only pushing - things I never knew using Git

[omnibrain 20]

On 7/25/2022 at 1:29 PM, Angus Robertson said:

but far more complicated than SVN for projects with a small number of trusted contributors

But when you are only a handful of trusted contributors you don't have to use the Github workflow but can have them merging (perhaps with rebase and smashing) locally and then have them push the changed branches to Github.

And if you work this way with your trusted contributors you can still be open for external contributors with the Github Fork-Merge-Request-Workflow. That's really the best of both worlds.

 

We have to face, that Delphi itself is obscure enough for younger developers. Clinging to outdated tools, hosting options and workflows nobody learns anymore isn't going to help.

[Berocoder 28]

Bit late to comment this thread...
Anyway I use Starteam from Borland in the past. It was slow and not reliable.
2013 the database was corrupted so our team has to change source control system.
We choosed Git and Github as that seems to be standard even at that time.
SmartGit was choosen as client as none of us want to spend time to learn git commandline.

Yes there was some hick ups in the beginning because we didn't understand the concept.

The common solution was to delete local source folder and clone a new one from Github.
Now this never happen anymore.

Git is great both for small one man size projects and for big projects maintained by a team.
It is simple if you are the only one that change it as there can be no conflicts.
And in case your computer start burning or something you have a backup on github.

In a team conflicts can occur. Often git handle that fine but if 2 people make change in same file you have to merge changes manually.

[David Heffernan 2448]

48 minutes ago, Berocoder said:

It is simple if you are the only one that change it as there can be no conflicts.

Hardly. It's possible, indeed common, for one person to be working on multiple branches

[Die Holländer 88]