groestl

22 ms·

331.
by groestl 3y ago
Because frankly, too much quality is not necessary, in many many cases. To know when you should or should not emphasize quality over quantity and speed, to meet a certain financial objective, is actually harder than writing quality software
332.
by groestl 3y ago
;) It hardly resembles the fruit anymore though :)
333.
by groestl 3y ago
And a very ripe banana can have an ABV value of 0.4%.
334.
by groestl 3y ago
AFAIK, Java's native HMR is not built on dynamic classloaders, but using a separate technology built into the JVMs debugger support, called HotSwap. You can only replace (certain) function bodies with it. To get around these restrictio
335.
by groestl 3y ago
And I have the suspiction, this can happen with visual signals as well. See "visual snow".
336.
by groestl 3y ago
You do that by paying for better developers ;)
337.
by groestl 3y ago
> its just the default behaviour That's good from the DBA perspective, but relying on that default as a user is risky in itself, when you deal with multiple hosts and not all are set up this way.
338.
by groestl 3y ago
That, and I start the line with /*, write the where clause first, and immediately before I execute the query I check the db host. Oh, and I absolutely refuse to do anything but the most critical stuff against prod on Fridays.
339.
by groestl 3y ago
Wild guess: Could be better measurement in the US, due to litigation/insurances?
340.
by groestl 3y ago
> Every other language has had package managers for this very reason Nah. Package managers are nice, but they only solve Problem 1 (Usability). If you have any business continuity concerns, you'll at least cache and archive the dep
341.
by groestl 3y ago
You might mean that with "time", but I think recursiveness with a delay is the critical part (and to some extend, is achieved with spatiality).
342.
by groestl 3y ago
That's the point.
343.
by groestl 3y ago
Oh, "the balloon". A quite common technique.
344.
by groestl 3y ago
Because that is just not how negotiations with (or between) big companies work. There are all kinds of customizations to standard contracts for them. From tweaks to liability, to changes in responsibilities, guarantees, insurances, etc etc.
345.
by groestl 3y ago
I find it a bit shocking that there are people who think everyone paid the same fees.
346.
by groestl 3y ago
> It doesn’t make sense. Tell that to antitrust lawers.
347.
by groestl 3y ago
The next paragraph is also worth citing (it probably applies to the thermoacoustic Stirling engine as well) "It is also possible to capture the waste heat using cogeneration in which the waste heat is used for heating a lower boiling p
348.
by groestl 3y ago
Pretty much yes
349.
by groestl 3y ago
Yes, exactly, "norm" as in "legal norm".
350.
by groestl 3y ago
I'm thankful I live in a country where opt-out is the norm.
351.
by groestl 3y ago
So, clusterfuqt? On topic: KDE is great, switched from Gnome years ago and never looked back. In general, I appreciate the effort of Gnome, but it's not for me.
352.
by groestl 3y ago
You can serve to yourself whatever you want, but please don't make other people leak what you've served them.
353.
by groestl 3y ago
Because sniffing? And tampering?
354.
by groestl 3y ago
It's complex, agreed, but in general, increasing the chance of survival of the host correlates with better reproductive capabilities of the virus. This works both ways. After a particularly virulent strain has hit a population, those h
355.
by groestl 3y ago
> could already have this massive swiss army knife of different ways to fuck us up. It's exactly _because_ it just jumped, that it fucks us up. Given time, milder strains develop which are more adjusted to humans and adapt in the ri
356.
by groestl 3y ago
Aside from issues with the type system and composability, it's just an impractical idea that stops working smoothly in anything bigger than toy projects. From a caller's perspective, "res, err :=" and "throws Except
357.
by groestl 3y ago
> writing and calling functions that _don't_ return any error You are under an illusion if you think they can't fail.
358.
by groestl 3y ago
Typically, that happens at the top layer. The API, the UI, etc. All layers in between don't care, and should not care, about this, other than correctly cleaning up. But it's not "distance". Also, it makes the correct th
359.
by groestl 3y ago
There's nothing magic-like with exceptions, and no spooky distance. It's what it looks like when you _really_ assume everything can fail. Go admits that with panics.
360.
by groestl 3y ago
> Buggy "edge case handling" is the source of many critical failures[1] And to fix this, we introduce 10 places per function to improperly unwind the stack, have a chance at missing an error result, and completely ignoring that

More ›