lnguyen

56 ms·

781.
by lnguyen 15y ago
How exactly do you define "traditional unices"? Based on what you've posted,you'd have a hard time calling anything that. And I'm including AIX, SunOS/Solaris, HP-UX, etc. What you want is a UNIX or UNIX-like OS that comes pre-installed wit
782.
by lnguyen 15y ago
I never use fink, macports or homebrew to install on my Mac. It's pretty much download source, take a look at the README/INSTALL and go from there. The main issue is that Mac is probably not the usual target system for these builds (in comp
783.
by lnguyen 15y ago
Macs aren't configured from the start as a development system. And if you start from a UNIX or Linux distro that isn't either, you'll encounter into the same issues (or worse) with trying to run "./configure && make && make
784.
by lnguyen 15y ago
It's the same as any recommendation engine: Because you've bought x , based on similar patterns from other customers you're probably likely to buy y . The fact that it's pregnancy-related makes for a good (and slightly controversial) news
785.
by lnguyen 15y ago
They've already been in services ala IBM for a number of years.
786.
by lnguyen 15y ago
If you have the money, you might as well buy a company that already has product and data. Time is money. As far as only date-based info, this is data that they can't automatically get from within their system (aka matching purchases with
787.
by lnguyen 15y ago
You're already working in the multiple repository approach (project and local). It's (almost) impossible not to with git.
788.
by lnguyen 15y ago
It doesn't affect how you use git for moving files/versions around. What it does affect is how you communicate with one another. You both are seeing the same thing and aren't wasting time trying to explain how to get the same info in the di
789.
by lnguyen 15y ago
Treat it like a citation in a paper. Add comments acknowledging and saying where the code came from. If nothing else, it'll help refresh your memory on why you needed it. Also be aware of the original licensing for the code. If it's any mor
790.
‘Cloud’ Data Center Closes Because Federal Agencies Prefer Earth(wired.com)
6 points by lnguyen 15y ago|0 comments
791.
What Beer Can Teach Us About Emerging Technologies(slate.com)
5 points by lnguyen 15y ago|0 comments
792.
by lnguyen 15y ago
You do realize that the tools have to be created based on some underlying process. If you have an understanding of that process you'll have a better understanding (and appreciation) of that tool. And maybe be able to come up with a better o
793.
by lnguyen 15y ago
The issue is whether you learned the actual skill (graphing, factorization, etc.) or just learned how to get the calculator to do it for you. In many cases, the end results appear identical. However, I'd rather the upcoming engineers, scie
794.
by lnguyen 15y ago
It's not only that it might be cheaper, it's because it takes out the uncertainty that would be involved in trying to defeat a patent. You have no idea how long the fight will take to wind it's way through the courts or even if you'll ultim
795.
by lnguyen 15y ago
It probably would help if they had an outside auditor to verify the actions that were taken. Still wouldn't be final proof to anyone who believes that they might still be hiding something but is a step further than just saying "trust us".
796.
by lnguyen 15y ago
Right now it sounds like he's just trying to see what the possible solutions for his issues are. If he can provide additional benchmarks, etc., great. But he's under no obligation to provide any more than he has. Once there's a solution, th
797.
by lnguyen 15y ago
I don't think Facebook is claiming to be. And as much as I'd like being truly open as an ideal, it falls apart when you're dealing with competition (not cooperation) and money. At best you try to keep things open enough.
798.
by lnguyen 15y ago
I'm pretty sure that cloning a repository of that size can't be all that fun. You tend to split repositories based on team responsibilities. I doubt that every developer needs access to update all million+ files. What this comes down to is
799.
by lnguyen 15y ago
It's intentionally vague but with enough details that if you're actually in a position to help, you'll recognize what's going on and actually directly contact to get more information. You don't spill internal processes and configurations wi
800.
by lnguyen 15y ago
There's two issues: the width of the repository (number of files) and the depth (the number of commits). Since "status" and "commit" perform fairly well after the OS file cache has been warmed up, that probably can be resolved by having bac
801.
by lnguyen 15y ago
I'm pretty sure the mod community would disagree. id, epic, etc. wouldn't have released editing tools if they didn't expect modifications to be made. But the expectation is that you're going to make that available back to the community. If
802.
by lnguyen 15y ago
They've trained the public for generations to not use their imagination and creativity. The withdrawal is probably painful enough to keep them going for a while even past that point.
803.
by lnguyen 15y ago
It's not just innovation but how they're executing and winning market/mindshare.
804.
by lnguyen 15y ago
There's already been a rich culture of mods, re-contextualization and remixing. You've been able to do all of the above before this release of the source code.
805.
by lnguyen 15y ago
What happens if/when an issue comes up that the managed service can't/won't resolve? If you can move to another provider that will, you'll have some leverage. But there's always headaches associated with any move/migration and a possibility
806.
by lnguyen 15y ago
The underlying systems don't magically build and support themselves. Basically you're just offloading the sysadmin responsibility to someone else and paying for that privilege.
807.
by lnguyen 15y ago
Feed on existing space junk and simultaneously solve another issue
808.
by lnguyen 15y ago
Rebase works great when you need/want to preserve he revision history. It's probably the ideal process to put in place if you can mandate it. One thing to keep in mind is that it might lead to a number of merge conflicts that may be difficu
809.
by lnguyen 15y ago
Something I wrote up nearly three years ago that should explain rebase vs merge http://gitguru.com/2009/02/03/rebase-v-merge-in-git/ I really should go back and start making new blog posts... I'd dropped the ball because I ended up on a f
810.
by lnguyen 15y ago
The strategy isn't the issue. It's whether it fits with the process you've set up. If you do code-review on the contributions/pull requests then I can see where the merge-often strategy causes issues. The auto-generated merge commits don't

More ›