Tag Info

New answers tagged

1

A couple of suggestions that might make this easier to handle by changing your project structure a bit. First, you are right that managing this in three different repos is probably too much work. Generally I have found that splitting different software components that all seem to make sense to a general project by folder in a repo is a good way to ...


0

Can anyone think of a reason not to do this ? Some very, very big ones: For one thing, browsers will not be able to effectively cache all of these files if your pages don't reference them at the same absolute URI. That is to say, if you have: page1/ index.htm -- references script.js as "/page1/script.js" script.js page2/ index.htm -- ...


1

I'm assuming that this isn't the best practice as the smart but naughty user could loop through all the possible combinations of the PIN code and wait which one will give him true as a response. This is called a "brute-force" attack. In principle, it is impossible to prevent brute-force attacks. There is simply no way to set up a password scheme that ...


9

Since the history is preserved in version control, there is absolutely no reason not to remove code you don't need. By the way, this applies as well to commented code within the source: don't comment blocks of code, just remove them; if you'll need them later, version control is your friend. Later may be even in an hour. The common sense may dictate that if ...


4

The problem with deleting is that they are "out of sight" and therefore "out of mind". The problem with archiving is that links or relative references will no longer apply. Tricky... Personally I would delete them, and tag the revisions that these were deleted. This allows the dead projects to be easily retrieved, in place, yet also be hidden but still ...



Top 50 recent answers are included