hkolk

Joined 15 years ago

Karma

193

Submissions

46

Member since

Jun 22

View on Hacker News

Recent submissions

Comment · 5 months ago

What is proposed is to not have an OOM killer with a selection process, meaning that the "someone other allocates" would be the one dying.

Comment · 5 months ago

In the Netherlands the law is pretty straigtforward that this is a bad idea: > The "Nature of Employment" Rule: If you are hired as a software developer, almost any software you create (even in your own time) can be claimed by your employer.

We always advise our employees to request an exception for it. We are pretty relaxed about it, but we don't give out a blanket exception

Comment · 2 years ago

The second example given (extracting information from a web view) is also weird. The rust code has the exact same flaw as the java code, which is that they do not validate the source. I think the author didn't really understand the underlying problem here. Bounds checking was not the issue with the java (android) code

Comment · 4 years ago

From what I understand, they only have to review/audit the times a gem was yanked, to see if it was a legitimate action. I reckon there is a lot less occurrences

Comment · 4 years ago

`m` is not a legal value, should be either `min` or `mo` for minutes or months respectively.

`s` is actually one of the SI base units: https://en.wikipedia.org/wiki/International_System_of_Units#...

edit: actually, month should never be used for the case described anyway... 28-31 days?

Comment · 4 years ago

if your manager is ok with it, don't register it as a sick day. Makes it potentially more complicated with the company doctor. Just consider it a workday spend on ...whatever. Manager being ok with it means you deserved it though :) (EU based engineering manager speaking)

Comment · 5 years ago

We are using Clickhouse combined with GDPR's Data Deletion Requests. We store the user-ids in a separate system, and run the ALTER/DELETE statements once per week. Works pretty smooth, though I would prefer some more automation within Clickhouse for them.

Data for in-active users gets deleted because our clickhouse retention policy is lower than the in-active-user timeout

Comment · 5 years ago

I wonder how this will play out with https://altinity.com who have been doing enterprise support for quite some time..

Comment · 5 years ago

same kind of website but easier to remember for me: http://neverssl.com

Comment · 5 years ago

Rabobank was the one with the horrible non-native client so pretty sure he is talking about ING :)

Comment · 5 years ago

You missed the "Do you take a lot of pictures with your phone?" If the answer is yes, you won't get to the mini.

Comment · 6 years ago

Hmm.. not 100% sure but I see 2 bugs in the PHP script: 1. the src of the image in the HTML is the local path on the hosting server (it would become src="/var/www/nyt/nyt.jpg" ) 2. The v= parameter always uses current date, even if it downloaded yesterdays image. I assume it is being used to prevent caching, but thus doesnt really work. I'd use either an hash of the file or store the date used for the download in a variable and use that.

Comment · 6 years ago

There is a nice Ted talk about the same topic. Something I often link to people saying "I can eat everything I want in this diet..." The mathematics of weight loss | Ruben Meerman | TEDxQUT: https://www.youtube.com/watch?v=vuIlsN32WaE

My personal weight-loss (and now sports) is largely based on understanding how the human body works with metabolism.. carbs, fat, protein.. nice and geeky

Comment · 6 years ago

IANAL (ofcourse) but in my limited experience:

1a: Not allowed provided because of AGPL (though would be allowed if it is GPL)

1b: Allowed, provided it is purely internal (as described here: https://www.gnu.org/licenses/gpl-faq.html#InternalDistributi... )

1c: Not allowed (this is a distribution, and actually is also in violation of general GPL)

1d: Not allowed, linking against the library means using it, which means GPL violation.

2: If (x) is licenses as MIT and does not contain AGPL underneath (it shouldn't, they are not compatible), you can take X under that MIT license. Regardless of actual repository layout.

3: Penalty is a pretty grey area, and this is a civil suite, not a criminal suite. As a result it goes into damages etc

4: I reckon EFF etc. Look for "GPL enforcement" (AGPL is not very different)

5: You can try.. but I reckon only in the discovery etc for a lawsuit a judge can force them to give access to the source-code to verify your claim.

For all intents and purposes, AGPLv3 is GPLv3 with the addendum that distribution also covers "As a Service". Also.. at our company we completely banned AGPL because we simply don't want to deal with any potential violations. So I reckon 1b in your example would also not happen in a place like Facebook (I reckon all 4 companies have an AGPL ban in place :) )

Comment · 7 years ago

Ehm yeah. If it was groundbreaking. But there are 5+ other contenders in this field who are dealing with the same issues, and in some cases are fairing better. We are currently evaluating multiple NewSQL vendors, and it really does come down to the details making or breaking the case. I am not sure what potential NDAs I am on so I can't share details, but there is a sharp difference in one company and another claiming "Distributed Serializability". Cockroach for instance enforces a lot of stuff to maintain consistency, and as a result can be (or is) slower. But at least it's also predictable. In the end it's all trade-offs and I actually like the Yugabyte product a lot. I just wish they are more transparent about what choices they made and the impact of that