Other Software > Announce Your Software/Service/Product

Bvckup 2 is in open beta !

<< < (7/20) > >>

TaoPhoenix:
Personally I think there is definitely a use case for one-way sync used as backup, and I commend you for sticking to doing one thing really well, instead of adding all the features other backup software has :up:.
-Jibz (October 22, 2013, 02:02 PM)
--- End quote ---

Plus I "chain" programs. So it might be okay if this dev doesn't burn say 1000 hours putting in Restore if any of 3 other programs can do it.

I put a separation when "this dev is available" and puts in a *custom feature* that *no one else has*. Then that makes the program special! That is why I do ask for context how hard a feature is - if he can do it in like 20 hours that's one thing, vs "let's invent this entire thing called an automobile from scratch" ... well, okay, that wish doesn't get filled today!

:-*

apankrat:

You misunderstand what the delta copying is and I guess the explanation I have in the Backup Config window should be reworded -
 (see attachment in previous post)
Delta copying doesn't copy deltas and store them in a separate file. It copies them into the existing backup copy. Think of it as a selective, per-block update of the backup copy. Performance-wise it makes no difference on the first run, but on the second run in vast majority of cases it delivers significant speed up (over copying file in its entirety).
-apankrat (October 22, 2013, 11:50 AM)
--- End quote ---

I'm not so sure that I am. Copy Files In Full creates "snapshots" in a point in time, right?-TaoPhoenix (October 22, 2013, 01:19 PM)
--- End quote ---

Correct, but so does the delta copying.

Say you have C:\Temp\file.ext and you set it to be backed up to X:\Backup.
You run the backup first time, it creates X:\Backup\file.ext. An exact copy.

Then you go and edit C:\Temp\file.ext, change something in it.
You run the backup second time. It updates X:\Backup\file.ext and again it becomes an exact copy of C:\Temp\file.ext.

This happens regardless of whether you are using the full or the delta copier. The "full/delta" differences affects *how* the file is updated, but the net effect is the same - the backup copy becomes an exact replica of the original. Think of it as a performance optimization that allows the backup complete faster, but doesn't affect what's actually being done to the backup.

Does this make sense?

apankrat:
@apankrat: the logs look so nice and easy compared to your average log :-*
-tomos (October 22, 2013, 01:24 PM)
--- End quote ---

I agree :-)

Query (similar to one in previous post) -
does it do versioning? (with apologies if stated above - have been following the events, but not very closely...)

--- End quote ---

It doesn't do versioning, but here are my thoughts on this.

I firmly believe that versioning needs to be done in a way that doesn't lock file history to specific software. This means that the version archive format needs to be open and documented. This in turn means that I should either invent and document such format (but then someone else will need to code alternative tools to work with it) -or- I can adopt an existing format.

Can you guess where this is going? ... 3,2,1 ... That's right - it should use Git :-)

So the plan as it stands is to get the V2 on the road first and then to tackle file versioning.

apankrat:
It's a matter of terminology really. To each his own. For example, I disagree that compression is an expected part of backup. Nor do I think that Restore should be a built-in app's function, especially if it"s essentially a thinly veiled basic file copy. I hear you that many people were led to believe that a backup without compression is not a "proper" backup, but that's not a reason enough for me to play along. This tendency to compete on the length of a feature list is very unfortunate.
-apankrat (October 22, 2013, 01:03 PM)
--- End quote ---

I think this is a trickier topic than it sounds. It chains a bit to your earlier remark about my theme.
"Submit a bug report for an unreleased theme to Microsoft - do I expect them to do anything? No."
-TaoPhoenix (October 22, 2013, 01:31 PM)
--- End quote ---

Just to close this particular issue - you are using a theme that wasn't released or is supported officially, that causes a common control not to be painted correctly and then somehow it should be me working around this issue in my program. Sorry, this makes little sense. Admittedly, in certain cases devs do work around other people's problems, but these are singular high-impact cases (like having a setup package mis-detected as a trojan by Symantec) and they are rare exceptions.

But for these smaller apps, having the dev put in features feels to me like an important process, because it can change a user's opinion of the developer.

--- End quote ---

I made a lot of changes in 5 months that the app sat in private beta. But I never add features just because they are easy to do and somebody asked for them. This is a design by a committee and it is a ROAD TO HELL. Retaining app's focus is really hard and it involves both (a) knowing what it is and (b) saying No on a regular basis.

apankrat:
Personally I think there is definitely a use case for one-way sync used as backup, and I commend you for sticking to doing one thing really well, instead of adding all the features other backup software has :up:.-Jibz (October 22, 2013, 02:02 PM)
--- End quote ---

Commendation well received, thank you :-)

Navigation

[0] Message Index

[#] Next page

[*] Previous page