Yes, but curiosity is a rover.
It's a dog, then?
Yes, but curiosity is a rover.
It's a dog, then?
I've completely disassembled one to replace a cracked chassis, and securing that ribbon cable takes a bit of a steady hand, but nothing too tedious.
Thanks for bringing us back to the Core of that joke.
...then it's moving too fast.
Linus has won what, exactly?
If it's about who's making the most money, which is certainly what Microsoft is trying for, let's examine the details. Microsoft receives royalties for every Android phone sold. Linus receives nothing. Microsoft wins. Given the demand for Office, Microsoft would have no trouble generating revenue by releasing a suite for Android. They've already proven they have no problem releasing their software for competing platforms if it's profitable. They've proven this with Office for Mac. Cha-ching, Microsoft wins.
But if this isn't about money? Suppose it's about principals, or getting Microsoft to bend its knee to the open source community. I won't be the first nor the last to say that Microsoft will not release an open source Office suite. So that can't be it. Their acknowledgement of other operating systems? They've developed software for Apple platforms for decades, so that can't be it either. Their acknowledgement of a product using Linux? They've had Linux virtualization solutions in place for a very long time, so that can't be it.
Again, I ask. Linus has won what, exactly? A bet?
So they may claim, but alas for them, they do not actually own that trademark.
Don't you mean Sky.NET?
Yeah, it has been a couple hours since the last article about RT's failure. Slashdot was about due to post another one.
Yeah, that solution makes the best sense to me. As the manager of those repositories, you'd have to make them available to every major distro out there to keep everyone happy, meaning you'd have to generate packages for every perl module in each of their differing formats, which could become an unruly pain in the arse.
Compare this to the easy solution: releasing one package per distro, your own package manager. I'm no expert on the subject though I'd imagine this is why things are the way they are.
Different users have their own reasons, but I like to be able to remotely connect via SSH to edit files directly. No need for FTP, VNC, X11 forwarding, etc.
For web development on a remote server, this has proven to be very handy for me.
Ah yes.... still using Emacs in 2013 is elitist. Of course.
It would be more accurate to generalize that and say that there exist people who use this kind of software and develop an "elitist" or "purist" attitude. I've seen it happen with all manner of TUI and CLI software. Also with *nix operating systems in general. Basically anything with a steep learning curve.
Even in 2013. The statement is "I prefer more complicated software than what you use, so that makes me smarter than you." Of course not everybody has this attitude, but there are some who do.
It has its pros and its cons. On one hand, I really like the idea of only having one package manager handle everything. No need to keep track of different utilities and all their different syntaxes.
On the other hand, a distro-specific package repository is never as fresh as an application-specific repository. Debian is a prime example of this. It has many but not all perl modules, and not all of them are up to date. CPAN, by comparison, tends to have the latest, and of a fuller variety. But CPAN doesn't necessarily handle dependencies with finesse so I've had to fall back on installing perl packages from the distro. So the RHEL machine I've been expected to develop with at work is using an ungodly combination of CPAN and YUM packages to give me everything I need.
Trying to get off of that system as soon as I can...
I believe the proper term is "clowder."
Script kiddies don't hack.
This is actually a very interesting observation. When it comes to having software made available for multiple architectures, the open source community is way ahead of everybody else.
Even if the author of an open x86 application is lazy/busy/indifferent about releasing for other architectures, somebody else may already have taken the liberty. And if not, you can crank out a binary yourself.
I was interested in replacing a personal x86 Debian server with something lower-power but was avoiding ARM for the longest time because I was afraid I would lose a lot of the software I use regularly. I didn't figure ARM was good for anything more than smartphones and game consoles. Then I took a look at Debian's ARM repository and found that every single Linux program I needed was already there. So, $35 and a few apt-get's later, and I had a Raspberry Pi running all of my same applications on a completely different architecture.
The point of all this? It was no hassle for me to switch to ARM while sticking with the same OS and applications.
"Spock, did you see the looks on their faces?" "Yes, Captain, a sort of vacant contentment."