This is compounded by the lack of effective centralized management tools for SSH key access
It works both ways. Precisely because there *is no* centralized control of SSH keys, my workplace cannot implement crazy password aging schemes, or demand at least one digit in each passphrase. End result: I take much better care of my ssh keys than of my plain login passwords.
There's plenty of us here watching from afar with large grins on our face. Hello from FreeBSD, NetBSD, DragonflyBSD, and OpenBSD.
And some of us Linux people are happy that you are there. But it is not a good idea for you to gloat -- if Linux fails to keep the Unix legacy alive, your support base dwindles too.
Office has excellent interconnectivity. I don't think that any users really perceive MS Office as being a simple suite of unrelated programs.
I do. I'm aware that there's some weird embed-an-excel-table-in-a-word-document thing you can do (isn't that where OLE came from?) but I haven't seen it *used*. Not for a decade at least.
They use Powerpoint heavily at my workplace, and Word/Excel a lot too. The usage is very crude and primitive, though.
RedHat makes much of its money from companies that are moving to open-source because they are sick of the downsides of commercial software, which go from quality issues to vendor lock-in.
To me, quality issues and vendor lock-in sounds an awful lot like the downsides of RedHat (and the other for-profit Linux vendors I have seen).
We have at this point taken control of our own evolution in terms of intelligence and are developing it seperately from the law of the jungle, constructive rather than destructive evolution.
That does not make any sense at all, in several ways. (a) We have in no way taken control of our evolution; we don't even have control of our technology or economy. (b) the term "destructive evolution" is as meaningless as, say, "purple evolution".
1) characterise the traffic. could be from a range of ip, targeting specific ip, targeting protocol x or y or having some id characteristic you can 'lock' onto.
2) install filter for such traffic UPSTREAM of you, at the isp. blocking once its crossed the wan to your site is obviously useless
Not obvious to me. The cost of a single packet increases immensely at each step as it
hits some NAT/state tracking device of yours
hits an actual server
hits the IP stack of said server
hits userspace
makes userspace do heavy things like processing, database access
PETA will demand a monument to the billions of microbes that died when the pools dried up.
Seriously, there are rare and unusual ecosystems around hot springs. This incident might be a significant loss of biodiversity, unless hot springs are common in the area.
Minor quibbles: it's friggin blog post, not an "article." And it's not about "navigating an ocean of open source" in any sense that you might imagine. It's more along the lines of an About.com "Here are ten tips for using Open Source in your business" page.
Not even that, really. It's about integrating obscure open source components in the software you're writing. The article doesn't make sense if you try to apply it to running a stock Linux server or desktop.
Question: If Canonical announced tomorrow "We are going broke, either we have the Amazon search or we close our doors" which would you choose? Frankly most of the improvements on usability on the desktop can be traced back to Canonical and like it or not if they go under there is nobody lining up to take their place.
IMO the Unix "desktop" was good enough for average users in 1992 or so, so I'd choose a world without Canonical. I don't quite understand what these usability features *are*, anyway. I have to use Windows at work, and see nothing remarkably usable there. Keymap switching is nice, but everything else is comparable with my plain X11 desktop.
Of course, now someone will name me "part of the problem", mutter things about "the year of the Linux desktop" and so on
Actually one could make the argument that Java is worse, since at least C++ voodoo can allow a highly trained programmer to accomplish some really cool and unusual things.
Cool and unusual things are *not* something to strive for, and it's not what C++ is for.
More on topic, C++ at least doesn't have the "everything is a class and each class is one file" paradigm Java used last time I checked. I imagine it's slightly harder to work with Java using a normal text editor because of that. On the other hand, you should structure your code in a natural way, not write 50 kloc files just because you don't know how to navigate between files.
Of course that doesn't change the fact that at least in Java tiny changes in whitespace won't result in two valid but entirely different meanings...
Did you change the topic to Python now? I don't recall any such problem in C++.
I could see some thinking "recent" technology means "good", but my personal experience provides little evidence to correlate "new technology" with good. I could even make a case that it's a red flag.
Yes. An euphemism for "this software used to be Joe's personal playground until he quit" or "all the developers are fresh from school and do what their teacher told them to".
On the other hand an organization can easily be too backwards, too.
FWIW Anyone using X over a network for any kind of serious remote management has rocks in their head. It is a horribly inefficient protocol because of it's age, compared to modern protocols such as VNC and NX.
X over ssh works very well for me. If it's horribly inefficient like you say, it doesn't show on the 100Mbit networks where I use it all day long. But then I use old, properly written applications, without bling and dancing hamsters.
And yes, I don't care about single thread performance as I care about multithread performance. Single thread performance has been good enough for desktop for almost a decade, and the only CPU intensive task I do is running those pesky `make -j X` commands.
You don't mean multithread, exactly. Make isn't multithreaded; it uses real processes.
As usual with all other topics, check out what Debian has been doing for more than a decade. Pretty much every release this century has some dedication to devs who died since the last release.
That's different: that's a dedication inside the very thing the deceased was working on, made by and for the community she was a member of. You don't see Debian releases dedicated to some member's grandparent, although we can be sure the members have loved ones and sorrows like everyone else.
So here's another vote for not doing anything like that.
Halloween is not relevant to everyone inside the US either, as I found out when I lived in an apartment. No one at all ventured into the apartment complex for treats. I thought surely kids who lived in the apartment complex would visit, but no, didn't see any of them either. A grand total of zero people came to my door. It wasn't regional either-- that held for apartments on the east and west coasts. It was one of the many little things that drove home the point that in the US, apartment dwellers are 2nd class citizens. Apartment dwellers are more likely to be child molesters, candy poisoners, thieves, and that sort of ilk.
That's not just the US. Same thing in Sweden. 30 years ago it was ok to live in a rented apartment; now it's kind of not, unless it's on a fashionable address. Still ok to use public transportation, though!
Real Programmers don't eat quiche. They eat Twinkies and Szechwan food.
