groestl

17 ms·

271.
by groestl 3y ago
I guess that makes the point of: perfect abstractions vs leaky abstractions.
272.
by groestl 3y ago
Isn't that a felony in the US? Where I live, this is a felony.
273.
by groestl 3y ago
I'd do it for CYA purposes in case smt goes wrong and my commit is involved.
274.
by groestl 3y ago
That's actually quite funny, especially because Germany almost has portrait DIN format.
275.
by groestl 3y ago
> assuming English is your first language You're wrongly assuming. It's German, and we have the word "Kulturlandschaft" (cultural landscape). Today, 60% of Europe's landscape is "Kulturlandschaft".
276.
by groestl 3y ago
It's actually the first association for me, when I hear "damage valuable cultural artefacts", so I personally find it quite fitting. And I agree with you, both actions can be (and IMHO are) bad.
277.
by groestl 3y ago
> It’s the incidence that is important here But that's my point: the incidence of cervical cancer in women and throat cancer in men is in the same order of magnitude, but the incidence of cervical cancer is stable or even declining
278.
by groestl 3y ago
5-year survival rate of throat cancer is 82%, 5-year survival rate of cervical cancer is 92%, and incidence of HPV-related throat cancers among men is higher than cervical cancer on it's own and rising (probably due to changes in sexua
279.
by groestl 3y ago
You lose flexibility though. On the JVM, application containers are basically the same idea, so we started out that way. But the industry arrived at an embedded model, where the application would ship with the servlet engine and be responsi
280.
by groestl 3y ago
Please, I did not want to offend you personally. It just took me by surprise. I understand your points, even though I'm with your direct reply, all things considered.
281.
by groestl 3y ago
> Wait, so you're saying that code that subtracts an offset from a child node to get to a parent node is clearer and less complex than alternatives? Parent made me laugh out loud on this.
282.
by groestl 3y ago
What actually happens is with 3DS: a merchant gets liability shift. Liability resides with the issuer then. Whether you as a customer can be held liable for damages depends on your jurisdiction and when you report your devices / crede
283.
by groestl 3y ago
> Sadly hardly anyone uses it. It would be great if Chrome's Developers would use something similar to run Chrome itself.
284.
by groestl 3y ago
Interesting, thanks for sharing.
285.
by groestl 3y ago
I think Folders are more an example where neither the technical implementation nor the mental model fit the real world particularly well (in the general case).
286.
by groestl 3y ago
Exactly
287.
by groestl 3y ago
Unique Selling Proposition. If the thing the library implements does not substantially differentiate your company from others, it's a candidate to be maintained as open source project. For example, just become an expert ffmpeg user if
288.
by groestl 3y ago
Open source is different, in that you as a company can become maintainer and therefore expert of that component _and_ profit of other work being upstreamed. In case the library is not your USP, I think it's not that clear cut.
289.
by groestl 3y ago
"Now look what you've done, Marjory Stewart-Baxter! You're grounded!"
290.
by groestl 3y ago
Can't wait for my 5 year old to start a sentence with "However, it's important to note that ..." ^^
291.
by groestl 3y ago
> You must have misspoke as that would be the dumbest idea ever. Have you ever developed, operated and maintained a distributed system?
292.
by groestl 3y ago
> Exceptions are raised when the process enters an undefined state. Exceptions are raised _before_ a process enters an undefined state. A thread that's unrolling the stack is still in a well defined state. > age < 18 In real c
293.
by groestl 3y ago
> Java does not acknowledge the existence of errors. It believes that every fault is a programmer mistake Oh, you're distracted by the stack traces, of which you have a strong opinion, but it's exactly the opposite. What modern
294.
by groestl 3y ago
> why the languages newer than Go, including Rust, also keep a clear division between errors and exceptions. There are also languages older than Go that make this distinction. Java for example. Like Rust (and in contrast to Go) they even
295.
by groestl 3y ago
> it could've written said sufficiently advanced compiler itself. They couldn't, because that compiler would need to solve the halting problem.
296.
by groestl 3y ago
> Lacking a needed API is programmer error. Whoa, easy there. We're talking about standard libraries, and the designers of those are not complete morons. The API is lacking because the runtime environment already provides a safe and
297.
by groestl 3y ago
> and have to write a lot of additional code to do so. And most importantly: you have to read a lot of code like this, and understand it's assumptions, failure modes, runtime behavior and bugs, which are different every time. Instea
298.
by groestl 3y ago
> exceptions are failures that a sufficiently smart compiler would have been able to catch at compile time Would love to see your proof of this for stack overflow exceptions. You could become very famous.
299.
by groestl 3y ago
> The minimum available stack space is a known quantity. It is. Tracking and erroring out on it to avoid the exception means replicating your runtime environment's mechanism for tracking and erroring out on stack overflow (system in
300.
by groestl 3y ago
> Exceptions happen in response to conditions that occurred when the code was written. Huh? Stack overflow? Out of memory? > It is highly unlikely that you want to handle an exception It is very likely that I want to handle an excepti

More ›