ajamesm's comments

No, that doesn't constitute implicit moral approval. We all understand that platforms and providers can't police each individual user. That's a concern about logistics, not moral consistency.

That said -- there are products that Shopify does (and would) kick a user for selling. Shopify isn't neutral, in fact, they're saying Breitbart is acceptable.

They frame it as "imposition of morality" though the issue is broader than that, i.e. Breitbart's tendency to incitement and spreading disinformation.

Crying "free speech" over issues of incitement or violence is the bread-and-butter of the alt-right, and I'm deeply curious as to why Shopify decided to employ that tactic.

> In a way, my position is an appeal to preserve some of the gray in the world. All solutions necessarily have to come from the middle ground.

This is bankrupt, morally and intellectually.

As someone who owns a couple rental units, the prospect of being a rent-seeking gentrifier or a slumlord

Lmao, if you paid $10 you got ripped off.

Genuinely lmao at the narrative that the taxi unions all got together and conspired against greener rides

yeah, real shame that the unmitigated sexual harassment got in the way of their complete avoidance of regulations

You send a message to [the person who can prove ownership of HN username 'perfmode'].

c.f.: https://keybase.io/docs/kbfs

  Soon, you'll be able to throw data into /keybase/private/yourname,pal@twitter,
  even if that Twitter user hasn't joined Keybase yet.
  Your app will encrypt just for you and then awake and
  rekey in the background when that Twitter user joins
  and announces a key.

Companies that grant options could fix this in a heartbeat by extending exercise windows; they choose not to do that. Nothing to do with AMT here.

If AMT repeal would 'fix' stock options, companies will change the terms to 'break' them again because they are handcuffs, not payments.

Nothing says "normal demands of everyday life" like bouncing quarters off of bedsheets

You'd... know if it was him. He'd, uh, have some choice words about Bomb Man.

I was most surprised by this CEO who goes around messaging randoms on LinkedIn to start friendly conversations. Does that happen?

70x faster? If Crystal gets its own port of Ruby on Rails, oh boy.

If you're a tech company, and your stack is so tightly coupled to Amazon that it represents an existential threat to your server fleet, you were never going to make it anyway.

Wal-Mart, probably. They bought Jet.com, which is effectively Amazon retail. I've tried it and it works just fine.

Amazon's definitely the 900 lb gorilla of convenience, but the BATNA of simply not using them is not really a material concern for the normative middle-class consumer who can drive to Target.

Off the top of my head -- protobuf, thrift, avro, XML, lua tables, properties files, yaml.

Heh, people sure to use it like it's the answer to everything, and "don't use it" stops being an option if you're writing to a JSON-based interface.

JSON's fine if you don't have any requirements around data serialization and you want it to "just work" for your webapp, but there's a lot of tech debt inherent in it.

So you dump a report in JSON format and back it up to S3. S3 costs are growing faster than you thought, so you gzip deflate all of it. Everyone has to go patch their JSON deserialization to detect gzip extensions. Whatever, just growing pains.

Then another team tries to read the reports, and they're getting errors because your definition of an interface is "we'll just use JSON, the keys are human-readable".

You define a formal API for your report format and in doing so you realize the need for versioning attached to your report schema, so you wrap all your JSON objects with types and version annotations. You could define a central repository for these schemas, but it's easier to just bake them into the top-level response. Everyone agrees that this is "lightweight" and not "centralized".

Now you're storing reports where each sub-object has its own annotations, or you're defining an entire schema at the object level. Object deserialization is taking 200ms even for small payloads, because of all the validation callbacks you're firing, and developers are now "performance hacking" their components by disabling validation callbacks. Now you have all the space overhead of schematic annotations with none of the benefits.

In order to adhere to the API, either teams are writing separate serialization libraries, or you form a team to maintain them as infrastructure, which is a great idea except that the horse already left the barn 2 years ago.

Without even realizing it, you've reinvented XML and XSD. And I don't really like XML either but at least you have to be honest about what you're getting yourself into.

s/CIA/arbitrary third party/

Headline makes it sound like the Cisco routers come with a CIA SSH key baked in.

facepalm Thanks.

Yeah, private equity is a natural response to business failing in the wake of a bubble, but bubbles themselves are market distortions caused by insane valuations.

Highlighting the value of reclamation just draws the heat off of the irrationality of the tech bubble. Amazon isn't a rich ecosystem, it's oligarchic.

And, indeed, any systemic failure in a capitalist economy gets explained away by saying that some cadre of vultures will exploit arbitrage until the gap closes. No one really questions the systemic failures per se. The economy happily creates this surplus in full anticipation of it being scrapped and fed to vultures. Banks repossess cars and capitalists think "working as intended" instead of "there's so many delinquent car loans that there's an industry of repo men and maybe that's significant." This criticism extends similarly to the tech bubble.

I'd almost pay a premium just to AVOID branding associations with Bono.