I'll have to look into PAR3. Thanks!
I'll have to look into PAR3. Thanks!
Multiple copies may be one solution, but it introduces another problem that doesn't have an elegant solution... you need a tool that can verify the integrity of your data (across the multiple copies). How do you choose which one is "correct" when you migrate and copy to a new system? In addition, how are you sure that any given copy is actually complete? What if you want to permanently delete a file from your archive?
I mitigated some of these problems for my photo library by using version control software. But they're not really designed for this purpose. Git runs into memory issues when you have repositories that run up to tens of GB. Subversion works, but you end up with a duplicate copy of all your files in your work tree.
There really isn't a very good archival solution I've found so far that allows you to be sure about the integrity of your data in the long term when talking even at the 100GB level, let alone the multi TB level.
FYI, Apple's languages/tools (like GCD, Swift, and OperationQueues) make it very easy and manageable to take advantage of concurrent programming. (At least compared to other systems I've see )
Wait, does Oculus have the same Michael Abrash that worked on Doctor Dobb's Journal? And author of numerous graphics programming books? That guy's pretty awesome! I remember reading his stuff when I was just in high school. In fact it may have been one of his articles where I *really* started to understand derivatives (way back when I was in high school studying calculus).
Not to mention testing. And we're back to the whole buggy/deficient driver mess of PC's. It's true that smartphones are basically like computers. But the one key difference is that I'm far less tolerant of buggy software/hardware on my phone than on my desktop.
GNOME 1.x was really great. It was fairly configurable while still being relatively easy to use and did what I (as a developer) needed. Current day GNOME looks like it borrows from the worst of Windows (the stuff even the Windows folks don't even like), and only recently adopted a few things that the Mac does (possibly because Windows copied some of it) but in some weird way that lost all of the intent behind the actions. So we end up with something that's simple but still not understandable because it's confusing and weird, and consequently useless to just about everyone. I managed to get by fortunately because they had an alternate window manager that was a bit more traditional.
Don't get me wrong, I still think the Linux community is amazing and love the fact that it all exists. But for GUI, not only have they lost sight of the Unix Philosophy, they also don't really have a good view of who their
This is also why the GNOME's insistence on designing for (what I call) "the mythical grandmother" was always flawed.
Same way we get young men interested interested in the cosmetics industry?
Actually, I would contend that *all* infrastructure-based resources will be natural monopolies. As such, I think the way we handled it before was correct.. it was just the way we divided it wasn't quite right... Governments shouldn't run the services/technologies/etc. They should regulate a single local company to manage the it (ie. the government regulated monopoly). In this case, we're talking about the physical cable/fibre/etc into the home. Services on top of that, then can be a free market.
That's a very good point. Bug tracking systems (public and even private) should also have a way to track the reliability of submitters. I've been with the open source community since before "open source" was a phrase, and sadly from what I've seen, the community still seems to lack an understanding of the human side of things at pretty much all levels. And from how GNOME has been shaped through the years, it only seems to be getting worse.
There really needs to be a software engineering major too. Where I went to school, the CS curriculum really didn't cover how to break problems large problems down into logical structures and pieces manageable by small teams, or how write maintainable code, etc. And from talking with others, I gather this is pretty true for most colleges. So don't feel bad..
I actually think it's fine to discriminate in this case. Women and men *are* different and have different needs, especially when it comes to child birth. However, child care is entirely different, and what you suggest makes sense... there should be "primary care" leave as well that's equal between the two.
On the other hand, I think businesses get into this kind of trouble because they try too hard to classify people's personal time. Just give everyone X number of days off and let them manage their time off. I mean you could argue that maternity/paternity leave is also discriminating against single people. I mean why the heck should someone get more days off just because they're giving birth? Shouldn't I be given just as many days in order to find a girl to impregnate in the first place? Who's to judge which one is more important than the other?
I have a ScanSnap as well, but just use their Mac software. What type of paper are your documents and how many pages do you do at once? I've found for really thin paper or for many pages it helps to simply fan them out a bit. But if you're doing many pages (like over ~20 or so) you might need to feed them in batches... Unfortunately it's a bit of baby-sitting, waiting for it to reach near the end of one batch, then putting the next batch in. But I manage to avoid the multi-page problem most of the time this way.
There was an old saying that C++ will make every project late over budget. I'll be curious to see how this affects the gcc project.
Oh, lol... That article makes sooo much more sense now. Clearly I need more sleep.
Honesty is for the most part less profitable than dishonesty. -- Plato