4,726 karma · joined April 5, 2013
These are not semantic nitpicks. They have much deeper meaning. I cannot stop you from dismissing them, but I hope you will consider them more than you have.
In a thread where you are defending a CEO being criticized as, amongst other things, childish, do you not see the irony of this?
* "Childish" and "unprofessional" are not synonyms.
* Neither are "adult" and "professional".
* Neither are "childish" and "honest".
* Neither are "adult" and "dishonest".
* PR fluff is not the same as the general concept of public relations.
* "We will not discuss this." is honest and straightforward, as are a number of alternative statements people have suggested.
* A statement made by an individual with limited power and resources may have very different implications and be perceived very differently than the same statement made by one with great power and resources.
* HN is composed of many individuals with nuanced opinions and worldviews.
* Individuals with diametrically opposed viewpoints in some areas may have very similar viewpoints in others, and sometimes the reasons for that may be subtle.
* No particular comment thread will necessarily have a representative sample of individuals participating.
* Confirmation bias exists.
Now, however, potential experienced employees who actually live in the real world will be avoiding Reddit. Why put your career at the mercy of an obviously angry, irrational CEO? There are all sorts of companies big and small where the CEO is either rational or at least kept on a short leash by a competent board of directors.
Going into ordinary damage control mode whenever somebody says something negative about your company is worse than the original damage. Any statement at all draws attention to the issue and risks making you look defensive.
But this isn't even ordinary damage control mode, this is a CEO personally attacking an ex-employee. It may even make mainstream news now (...and so it begins[0]). And worse, he's doing this right after getting another $50 million to play with and announcing a new anti-worker policy.
Before seeing the CEO's response, I would have said that responding to the thread at all was the worst possible choice. But I would have been expecting the response to at least be of a remotely responsible form. If the comment hadn't already been two hours old when I saw it, I would have thought it more plausible that the account had somehow been compromised than that anyone would actually think to respond in such a manner.
And now he's doubled down, but vaguely[1], "there's actually more, but we're pulling our punches, if you can believe it". If the original comment wasn't legally actionable, that one might be. The CEO has created a PR and potentially legal nightmare where there was originally nothing but some guy howling at the moon.
I'm reminded of the OMGPOP/Dan Porter/Shay Pierce fiasco. Troubling that the CEO of "the front page of the internet" wouldn't have learned from that...
[0] http://gawker.com/reddit-ceo-shames-ex-reddit-staffer-on-red...
[1] https://www.reddit.com/r/RedditCensorship/comments/2ifd3p/ud...
Is it satisfying? No. But it avoids exactly this situation.
And by the way, even that response is only expected when the company is directly asked. The correct response until then is to simply pretend nobody (or at least nobody in management) is aware of the issue.
Companies wasting money isn't an unusual theme, either. Even on the days I've been happiest in my employment, I could probably name you a half dozen ways in which I believed the my employer(s) were spending unwise amounts of money on things they shouldn't be.
Until the CEO responded, this was just an ex-employee with limited credibility saying pretty mild and unremarkable things few people would ever see. Now it's a CEO obviously feeling threatened and bringing wide attention to it.
I see no reason a rational executive would feel compelled to raise the profile of the issue by responding at all, much less in this dramatic fashion.
It probably wouldn't be there except I'm sure most of the expertise and code had to be developed for their imaging and partitioning products.
I think the only things I run frequently for development that don't come with OS X and aren't free or open source are Sublime Text and Paw. You can certainly use vim/emacs/TM2 and curl scripts if you want.
Were I using Linux, I'd be using Sublime Text, and, well, curl scripts again. I'd also be jumping off a cliff after about two days of dealing with desktop Linux's horrific regressions over the past decade.
OS X's native development tools (Xcode, llvm/clang) are free, and most of the tools you use in Linux are either already there, or a "brew install" away.
Like TFA says, don't roll your own crypto. GnuPG exists for a reason.
They all support general disk/filesystem encryption, too. If you're technically minded enough to be using vim and trying to encrypt files with it, and you're not using an encrypted filesystem to start with, you're pretty nuts.
The core UX for gnupg.vim is open .gpg/.pgp/.asc file, be automatically prompted for passphrase (unless file is new), edit file, save (be prompted for recipients if new). Done.
You're obviously going to have to complain to the vim maintainers about sensitive content. There's been a patch floating around for over a decade to get vim to support mlock. Its blowfish encryption is certainly no safer than gnupg.vim in that regard. gnupg.vim does turn off the viminfo/swapfile/undofile functionality.
See also, moron in a hurry.
Cleartext doesn't have to be saved to disk for a separate tool to be used. You can pretty much use GPG from vim as-is just by piping the buffer through it: ":%!gpg -e -a -r yourself" and ":%!gpg -d". The vim GPG plugins can take care of the remaining annoyances.
Edit: Seems it's still read-only. If you need write support that badly (why?), there's always Paragon: http://www.paragon-software.com/home/extfs-mac/
https://gist.github.com/anonymous/d69f5b0cee13102a9167
So, I've satisfied your request, "Try using cpan to install basic modules like MySQL". I guess that means you admit OS X "can do pretty much any Unix based task that GNU/Linux can"?
Well, that's one I can personally tell you I've had problems with in the past.
> even worked back in 2000 on Cygwin out of the box on win2k
And also this one. That's even back around the timeframe I was actively doing Perl development while using win2k.
First submission 2012-11-11 16:21:18 UTC ( 1 year, 10 months ago )
Last submission 2014-05-08 21:33:59 UTC ( 4 months, 3 weeks ago )
Sounds like a small-time vendor trying to make a name for itself by "dissecting" an old trojan. Maybe they want some extra revenue for christmas bonuses.This particular headline (which, to be fair, does not come from the linked page) uses the word "exploit", but there is no evidence of what, if any, flaw is being exploited.
"Worm" has a rather specific meaning. It's malware that self-propagates through a network. Strictly construed, the only way this can happen is if there is a security flaw being exploited. A looser definition includes things like the infamous "ILOVEYOU" "worm", that automatically distributes itself, but requires user interaction to infect a target.
In this case, neither means of distribution is in evidence.
At this point, I'm skeptical that this "worm" exists at all.
I switched to Fink, which broke occasionally but I was usually able to rescue it without too much hassle.
Eventually I stopped using Fink maybe a year (or two?) ago in favor of homebrew, and have not had any serious problems since. brew's structure combined with 'brew doctor' and a vast and frequently-updated array of available packages seem to have done a pretty good job of avoiding the "can't get there from here" problems I had with fink and macports.
If an ISP in Los Angeles transits five autonomous systems to reach an ISP in New York, but four to reach an ISP in London, and the London ISP suddenly starts advertising the New York ISP's IP addresses, oops, your packets are now headed to the UK.
Great care is taken to avoid bizarre physical routes for packets, but it still happens constantly. One DSL connection I used in Santa Clara had a propensity for routing packets through Seattle to get to Dallas for a while.
Each level of delegation must be cryptographically validated. Route announcements not signed using a certificate to which authority for that block has been delegated must be rejected.
That's from Chrome on OS X 10.9. Firefox and Safari seem identical.
I get something a little closer to yours in form from IE 11 in a Windows 7 VM, but still significantly darker: http://imgur.com/FzjsKJu
Firefox on Windows seems identical or darker.
The closest I can get is Chrome on Windows 7, which does a bad job with this font, though it's not exactly identical to yours: http://imgur.com/YwsxMhl
As I recall, Chrome does its own font rendering, and tries, on Windows, to match Windows' rendering, and does an even worse job of it than Windows does.
SNI is fait accompli. It will be adopted. It is being adopted. Without support for it, a rapidly growing number of sites will not be securely accessible, and effective regressions like the one you experienced will be encountered more and more frequently.
And in an age where interconnected systems are the default assumption and those systems change fast, I don't think it's realistic to adhere to an overly strict policy about what updates can be brought in during extended support cycles. I think Red Hat recognized this a while back. Canonical probably needs to.
The most important thing you can do for security is to decrease your attack surface, and one of the most effective ways to do that is to not run shit you don't need. Code that isn't there can't be exploited.