HN user

beokop

124 karma
Posts0
Comments67
View on HN
No posts found.

There’s no reason to believe they won’t have an online copy of the 2020 snapshot too. Isn’t that kind of the point? For future generations to be able to use it?

Then why have the option to delete public repos at all? Public tweets? If we had the means, should the web as a whole be append-only?

There’s a big difference between “public” and “stored in a glacier forever”.

Is there a way to opt out of this? I’m not sure I want my code to be stored forever in a glacier with no way of deleting it.

It’s pretty clear that the author isn’t using the technical definition of big O but rather is using it in a descriptive way. It’s not ambiguous in any way so what’s the harm?

Thanks for the tip. I’ve tried that before, without success, but someone else reading this might have better luck.

For what it’s worth this happens both with a 15” and a 13” MBP from different years.

I haven’t thought of it this way before but I think you’re right. External monitor support does break randomly and hardware support through dongles is extremely flakey.

A small excerpt from my personal list of woes:

- Using a USB-c <-> DVI cable gives the monitor a purple hue. An HDMI cable does not. Also, this isn’t an issue in bootcamp.

- Can’t use the serial debugger of a Particle Photon because it can’t use the dongle’s USB-A interface directly.

- Sometimes the Touch Bar goes completely unresponsive for ~10s. Sometimes, after a reboot or after waking from sleep, it just doesn’t start at all.

- At one point the speakers started blasting white noise at the loudest volume for no apparent reason. Closed the lid, opened it, same thing. Rebooted the machine and never encountered that problem again.

- If a certain kind of network error occurs when setting up Time Machine then System Preferences will hang completely for ~5 minutes.

In many ways the experience is what I would expect if I could run Linux on this machine: Hardware kind of works with lots of random bugs.

This might be true, however, I’m of the opinion that the prize should go to people that are making hard choices to de-escalate actual armed conflicts.

While you’re at it, why not sue for emotional distress? Or lost income for the time reading this instead of billing clients?

I’m all for GoDaddy being held responsible but advocating this kind of copyright abuse is as ridiculous as it is scary. Are we going to start suing CDN’s for setting custom HTTP headers now?

That’s not how this works. The actual books/movies/cartoons that Batman appears in will eventually be public domain — you’ll be legally allowed to copy, edit and distribute these without restrictions. However, “Batman” (the idea, the concept) is still protected by trademark laws making it illegal to produce new (non-derivative) Batman books/movies/cartoons without the trademark holder’s consent.

I do like the article but it sounds like they’re in over their heads, this whole (very risky) project could have been avoided if they just brought in someone that knew what they were doing.

Clocks are important – don’t lock down your VPC so much that NTP stops working.

Automatically generating database indexes on application startup is probably a bad idea.

Database management is important and hard – and we’d rather not be doing it ourselves.

This is true of any database infrastructure with redundancy/scalability requirements.

What they did was take a technical problem and solve it by buying an off the shelf solution. Which is fine, of course, but I’m a bit surprised by the reaction here on HN.