HNHacker News
TopNewBestAskShowJobs

pdeuchler

3,337 karma · joined September 2, 2011

Philip Deuchler. Nothing Special. Former Wantrepreneur, Wannabe Ski Bum.

pbdeuchler (at) gmail (dot) com

submissionscomments
pdeuchler··on Go hits the concurrency nail on the head
This is correct, but they quickly pivoted to targeting the Python codebases. Rob Pike has a talk where he talks about how Google used C++ and C to rewrite hot Python paths and how they wanted Go to be able to completely replace that whole pattern. Russ also has a blog post (maybe? it also could have been a comment in a github issue, tbh I can't remember) where he mentions converting python programmers was orders of magnitude easier within Google, as the C++ programmers often had rose colored glasses about their own abilities and the tradeoffs of C++.

It's interesting, as I don't think Go would have been successful without the pivot, but I also don't think it would have been as successful if they had started off trying to replace Python.

pdeuchler··on Bloomberg’s ‘The Big Hack’
The Newsweek that published that article and the Newsweek that built the brand reputation are entirely separate entities.

The current Newsweek is no more formal journalism than Gawker is, which is to say occasionally they'll get big scoops but most of the time they're in the mud trying to get clicks/eyeballs.

pdeuchler··on Go hits the concurrency nail on the head
I don't think most of this is true... the Go core team is at least 20ish people, and that's just engineers not PMs, Managers, or other support staff. Plus the tools and kubernetes/gcloud teams. It's also kind of disingenuous to call any team lead by Rob Pike and Ken Thompson "small"... yeah they might not have hundreds of people but they can certainly wield a hell of a lot of influence.

Google also spends quite a decent amount promoting Go and donating to OSS that promotes Go.

You're not wrong about the comparison to Ericcson/Erlang though, or most of the reasons for Go's success, but you can't discount the Google factor.

pdeuchler··on Go hits the concurrency nail on the head
Nothing you're saying is wrong, but your perspective is totally off.

For someone experienced with C++, or say, Rust (ahem), obviously Go is a bit backwards when it comes to concurrency and race conditions. Obviously you can mimic go's goroutine stacks, obviously you can obtain fast thread switching.

But Go isn't targeting C++ or Rust, and it's not targeting the domains those languages are best at (although admittedly there are some overlaps between Go and Rust). Go is trying to replace Ruby, Python, and JS. For programmers who only know those languages, or haven't had the opportunity to work in more "heavy" languages, Go makes it dead simple and intuitive to do things that previously would have been completely out of reach. All you're arguing is that if you go farther "down" the stack so to speak you can accomplish everything Go does, which of course is true, since it's turtles all the way down.

The fact of the matter is, if someone boots up a brand new linux laptop goroutine switching _will_ be faster than thread switching. That doesn't mean Go is super crazy performant, or better than C++ or Rust, it means someone who's only programming experience is Rails apps can now write performant multi threaded code with orders of magnitude less domain experience. Same with race detectors. Multithreaded Python is a complete minefield for race conditions. Sure, you might not segfault, but you have to think if you use fork() or spawn() depending on the OS, you have to install libraries to detect races, you have to write special tests. With Go all of that comes out of the box and it makes it _easy_.

Go does nothing new, and a lot of languages do things a lot better. Erlang is mentioned in other comments, Erlang is a fantastic language for concurrency and a fantastic language in general. It's also incredibly hard to find programmers who code in it, or are willing to learn it. It's also incredibly hard to sell to the business people higher up. It's also very hard to find Ops people who can competently support an Erlang stack. C++ gives you the power to build formally correct real time systems, but it also gives you the power to blow your whole leg off if you don't know _exactly_ what you're doing. I can go even further down the stack with C and assembly but I think you get the point, it's all about tradeoffs. Go allows programmers to reason and think about concurrency without having to worry about linux kernel PRs, without having to worry about how to share memory, without having to worry about stack performance.

*edited for clarity

pdeuchler··on Prepare for changes to macOS Server 5.7.1
Jumpcloud can help with those things, we're an entirely cloud based directory and our system agent is OS agnostic. We also integrate with Jamf and other MDM solutions if you need more complexity.

Disclosure: Jumpcloud employee. My email is in my profile if you want to get in touch.

pdeuchler··on Facebook Network Breach Impacts Up to 50M Users
I am extremely imperfect and a hypocrite on many levels. I never practice what I preach, and if I'm being honest I can't say what I'd do if I had an offer from a company like Facebook or Google that promised to completely change my financial situation. I don't pretend to be better than anyone who has been in that situation and decided that the money was worth it. I'm not better than people who took the job because of the career opportunities, the social cache of working at a FAANG, or the chance at working with one of the world's richest datasets on the world's most powerful computers with some of the world's brightest minds. It would be a fair critique to say that my pronouncement smacks of self-righteousness borne of a moral framework that's never been challenged. Like a rich man who chastises the poor for stealing to feed their families, it's easy for me to moralize.

But, I do know that working for companies that are funded by advertising makes me feel uneasy. I know because I've worked at one or two. I also know that the company I currently work for charges our customers for the services provided, and I know there's a consensual quid pro quo in every customer agreement. I also know we don't track our customers beyond their consent. I would hope if my company ever started doing that I'd speak up, and if things didn't change I would hope to have the fortitude to leave and continue to speak up outside of the company.

I also have no doubt that my day to day work is automating away someone's job, somewhere. Where someone used to make a good living, my code will run instead. People might not get overtly laid off because of my code, but there's no doubt people who use my company's services hire less people... it's kind of the point. I definitely think about the moral implications of that. Sometimes I'm not super comfortable with the hypothetical effects of my code over a long time period. Even if I contribute less than 1% to my company's service, if my company's service saves our customers on average the equivalent of one salary a year I've been responsible for the, at best, lack of creation of hundreds of jobs. In a different world someone fed a family, bought a house, and lived a life with one of those salaries, and now that opportunity is forever gone. Sometimes that's a hard thing to grapple with, and I really hope that I'm not contributing to negative economic trends that hurt a large majority of the world's populace while enriching myself. Chances are I probably am, though.

However I am certain of a couple things. The mass collection of billions of people's information is putting upon yourself an incredible responsibility that I find hard to justify. This wasn't by accident, this wasn't dumb luck, this was a purposeful attempt to amass and control power. This power isn't inherently good or evil itself, but even in a vacuum one has a right to be suspicious of such power. Fortunately we don't live in a vacuum and over time Facebook has shown itself to not be a good steward of the power it's created. I have no doubt there are plenty of ethical people that work at Facebook, and there are definitely plenty of ethical, smart people who work in Facebook infosec. I don't blame them for the data breach. I blame the creator of this Pandora's box, I blame those who willingly continue the abuse of this power, I blame those who purposefully profit off the abuse of this power, and I blame those who refuse to realize that they will not change an organization that refuses to change. Until the use of Facebook's data is no longer rewarded with massive amounts of money Facebook will continue to collect and sell this data. The incentives are very clearly aligned. Working there, no matter your intentions, cannot change these incentives. I'm not saying everyone at Facebook is evil, but if the hiring reputation is true they are too smart to not understand these things for much longer. Facebook will continue to be morally bankrupt until its power is abolished or democratized, and since a Pandora's box cannot be closed I'll settle for democratized.

pdeuchler··on Facebook Network Breach Impacts Up to 50M Users
Said this yesterday in the other Facebook thread, and I'll say it again.

Working for Facebook is a morally bankrupt position. If you are an engineer you have plenty of job opportunities available to you and there is no excuse for you to continue contributing your labor and time to a wholly malignant organization. At a certain point one has to ask how we as an industry will start dealing with those who continue to take a paycheck from Facebook even in the face of constant and horrific evidence of wholesale ethical violations and negligence.

pdeuchler··on Facebook Is Giving Advertisers Access To Your Shadow Contact Information
A reminder that if you work for Facebook you are fully complicit. Especially if you're an engineer, there should be no shortage of jobs available to you at this time. There is no excuse to work for a company that's sole focus is exploitation of its users.
pdeuchler··on SEC Sues Musk and Seeks Ban for His Tweets on Go-Private Deal
> I promise you, Elon legitimately thought there would be an opportunity to go private again.

According to the hard facts the SEC is presenting this is patently false, there was absolutely no reason for Musk to "legitimately" think that.

> even has said they never wanted to go public, but were left with no choice.

Also just not even close to true. Elon would have been canned and Tesla would have been bankrupt by now if they didn't go public. If by "left with no choice" means "structured the company so that only a public IPO could sustain it and allow for the path he wanted" then I guess you're right?

See: https://www.bloomberg.com/view/articles/2018-08-17/elon-musk...

pdeuchler··on Chrome 69: “www.” subdomain missing from URL
I, for one, cannot wait until this is exploited somehow by phishers
pdeuchler··on Maybe adding generics to Go is about syntax after all
As someone who just went to gophercon I'm still confused why they're tackling error handling first, and then generics. I would imagine tackling errors in Go 2.1 with the help of generics would make for a much much cleaner solution... if we even need one (i'm not fully convinced verbose error checking is as bad as people say it is)
pdeuchler··on The Places in America Where Most Income Goes to Rent
For large, sprawling cities like Denver, Orlando, Nashville, Omaha, etc etc mean rent is almost useless.

In Denver $1800 will get you a studio in desirable places to live, and will only get you a 2 BR out in deep suburbia or developments that come with 45 minute commutes. You're also going to have widely varying incomes between those two areas... i'd be willing to bet the after rent take home in the fringes of Denver sprawl is much worse than downtown due to ridiculous prices pushing low income workers farther and farther away from the city center while rent decreases at a much slower rate.

Also did they get their salary data from BusinessStudent or from Indeed? And where did they get their real estate data from?

pdeuchler··on Grand Jury Indicts Russian Officers for Hacking Related to the 2016 Election
replace "computer" with "IP address" and all the sudden that evidence becomes much less convincing
pdeuchler··on Things I Regret About Node.js [video]
Except javascript's design is completely antithetical to those use cases. It has no type system, its performance is hard to profile and reason about, single threaded (unless you want to start forking and managing threads in javascript...), weird edge cases, piss poor numeric computation, etc etc.
pdeuchler··on Spend analysis of 6 years, 686 rides, and $12k spent on Uber (2017)
I don't mean to be a downer here but you're essentially saying that paying for someone else's asset depreciation costs is cheaper than paying for your own asset depreciation costs plus the remaining value on a car.

The reason it's more expensive to own a car is because you also own the asset. And sure, cars depreciate ridiculously fast and are horrible stores of value, but your solution is mostly saving money by offloading some risk to another party.

pdeuchler··on Getting Google to ban our entire company
I don't disagree with most of the takeaways here, but to be clear that email ban was entirely TPM's fault. They even admit to the cardinal sin of email sending: using one address for everything:

>Many of you know that we have one company email address here at TPM. It’s the one linked at the top of the site. It’s the lifeblood of the whole operation.

I also know from personal experience they used to send newsletter/marketing/transactional email from the same address, which you should never do. They probably got a little spammy with some marketing or newsletter emails and got their domain blocked by Spamhaus or another intermediary, and like every other ESP google has automated systems to blanket ban when they see you pop up in a spamhaus list. Pretty simple.

pdeuchler··on Pyre: Fast Type Checking for Python
>> (We also collectively decided that Microservivces were another solution to our woes though that cargo cult is being questioned)

I wouldn't really say that, I think it's more that we all discovered huge monoliths don't work in an "agile cloud" environment where you have 10 teams deploying on their own cadences with no coordination (which you have with on premise binary delivery, or waterfall, or when you have implicit coordination by operations because they have to build out the physical infra). Further, I think modularity has become much bigger in the past 15-20 years as more and more people contribute to open source, more problems become "solved", and languages/domain spaces mature. Whether microservices are the best solution to those observations is still up for debate, but cargo cult or not I doubt many engineers these days would use a magical wand to go back to monoliths even if they live in microservice hell right now.

pdeuchler··on Blowing in the wind: Plutonium at former nuclear weapons site
Neither do nuclear power plant meltdowns. Fukushima is habitable, Chernobyl is habitable. Most of the concerns around nuclear waste are almost entirely limited to military use. Storing spent fuel rods is a generally solved problem. Most nuclear waste when generating energy can be re-used in other contexts as well... military use creates the nasty by-products that can't be reused.
pdeuchler··on Being frugal is for the rich
This is, of course, because technology has brought those costs down. Or in the case of education, government subsidies have made college "free". Not because living wages or the economy have improved.
pdeuchler··on A Proposal for Package Versioning in Go
environment namespacing != dependency management

Regardless of your setup at the end of the day you're using pip to solve your dependency graph, and have been for over a decade.

pdeuchler··on A Proposal for Package Versioning in Go
>> But I am very happy, that they did not pick a random management system, just because they "had to have one"

But they have, multiple times? First it was just giving people links to godep when people complained in github issues. Then it was a tacit "we like this" about gps and glide. Then it was a pretty-much-official-blessing of dep. Now it's a super-official-now-we-mean-it implementation of vgo. I recognize this as a pattern because I do it all the time, software engineers constantly re-write things from the ground up when they don't care about actually solving the problem and just want to play around with cool new ideas.

As far as the vgo spec, I'm not against it per se... I like most of the general conclusions, but none of it is new. We've had these ideas in the Go world for a while. Most of them have even been implemented! Why can't we just slowly transition an existing tool? Or maybe implement a common library that individual tools can use to solve the problem in their own way? Oh wait we already did that and it got abandoned. Until we see a tool with a stable API that solves the 80% use case and lasts for over a year I'm not going to get excited about the new flashy thing.

pdeuchler··on A Proposal for Package Versioning in Go
Agreed. Dep had its warts (20 minutes for a very simple dep ensure...), but it solved the 80% use case in a way that was least objectionable for the majority. The fact that they can't (won't?) even refactor dep to suit their new ideas or try and revitalize the gps project just tells me that they don't really care about solving this for end users and just want to have fun writing a fancy dependency graph solver. Which is cool and all, but at least give me a stable API first.
pdeuchler··on A Proposal for Package Versioning in Go
I've been hearing this argument for about 4 years now. Pointing out that .NET has terrible dependency management does nothing for me when Google's main languages (Python, Java, C++) all have solved dependency management for their own use cases. If the Golang team has had enough time to cherry pick the best ideas and lessons learned to build a language they've had enough time to do so for dependency management.

At the very least they could have continued their hard core hands off approach of allowing the community to solve it. But instead they half-assed it and started capriciously anointing chosen solutions and honestly we're probably in a worse spot than we were before dep came along.

Plus, lets be honest here, there's no excuse for constantly changing APIs and binaries. If this was truly about getting the best ideas and lessons learned we'd just see refactors of existing tools with slow migrations to new concepts, but instead we've seen multiple complete rewrites, despite multiple efforts to build common libraries that should prevent such events!

pdeuchler··on A Proposal for Package Versioning in Go
How many iterations of this do we have to go through? Go hasn't had mature dependency management since its inception and this constant thrash is really starting to make things difficult.

For all practical purposes dependency management for programming languages is a solved problem, with many open source examples. The only explanation for this constant re-invention that I can come up with (and that's shared among others I know) is that Google doesn't care/need a dependency tool because of their mono repo. Which is rather frustrating since we get features (cough aliases cough) forced down our throats when Google suddenly finds a need for them.

pdeuchler··on Zuckerberg and Sandberg can't be trusted to handle data leak fallout
Can we stop calling this a data leak? This was business as usual. What Cambridge Analytica did is SOP for almost every organization that's large enough to do their own ad targeting. I know personally of several information brokers that are actively buying and selling these kind of data sets on exponentially larger scales, not to mention hundreds of middlemen in the advertising industry that each have their own databases. I'd be willing to bet at least half the users of HN work at companies with splunk databases that could be used to infer a lot of the same data CA used. I made a Facebook app in college that was used by under a thousand people and I remember being able to scrape email addresses from friends of friends. Am I crazy or does everyone just have their heads in the sand?

Framing this as a "Facebook data leak" makes it seem like the problem was people we don't like got a hold of our precious data, not that our entire industry is funded by the mass harvesting and reselling of personal information.

pdeuchler··on Ask HN: What stack you use to build websites?
Same but DotNetNuke
pdeuchler··on Google helps Pentagon analyze military drone footage
I know many people who work for large multi-national defense contractors that definitely have "souls" as well, but hiding behind moral relativism won't save you from the fact that in the real world moral bright lines exist within societal contexts. And that said, I'm fairly confident how history will see our current drone program.
pdeuchler··on Google helps Pentagon analyze military drone footage
Most companies are run by people with souls, so I doubt this. Most corporations though, there you might have a point.
pdeuchler··on Tech company Lanetix fired software engineers seeking to organize, union claims
> and to hire non union employees without the unions approval

> socialist countries like India

Stop trolling

pdeuchler··on U.S. Income Inequality Hits a New Threshold
I'm not quite sure what you're saying here, but there are direct causal links between the Gilded Age and robber barons causing huge harms, like union busting using bullets, and absolutely no causal links between robber barons and global decreases in poverty.

Put another way, it's very easy to prove that without robber barons we wouldn't have had many of the terrible abuses during the Gilded Age, and also very easy to prove we would have had worldwide improvements in the human condition even without the robber barons.

← PreviousPage 2 of 21Next →