viktree · HackerTrans

7 か月前議論

> What did Cloudflare do to earn this trust?

dude who wrote the article works for Cloudflare. I'd say receiving a paycheck is a pretty good way to earn trust

It's just DNS. I'd say using cloudflare DNS is a step up from whatever the ISP's default DNS is. But if you're hawkish on Cloudflare, just use something else. There are plenty of good options

viktree

2 年前議論

I think this is what the zellij terminal multiplexer uses for extensions.

It's worth mentioning that in the opposite direction, if you wanted to have an interpreted config option with fewer compile steps, there's also the option to use lua — a language for which the compiler itself is quite small and portable

See,

[1] : https://zellij.dev

viktree

3 年前議論

See

> Some think they do - but don't. (idiots)

viktree

3 年前議論

From the same link, it seems like his compensation was much higher in all the preceding years. Not sure what changed this year, but I agree it's a bit refreshing to see. Especially since he's probably made good money throughout his career

viktree

3 年前議論

This is one feature I like in the Arc Browser. Persistent tabs are bookmarks, and bookmarks are just as accessible as regular tabs.

viktree

3 年前議論

Tacking roadblocks as they come up in service, creating a better product … that sounds a lot to me like engineering except with some words twisted around?

viktree

4 年前議論

I'm curious, what's the big company you are at now?

viktree

4 年前議論

If a typical workweek is (8 hr) * (5 days) = 40hrs, I think gp is referring to (10 hr) * (4 days) = 40hrs

viktree

5 年前議論

The RMS function in Quake Source code exists in the copilot training set (see https://news.ycombinator.com/item?id=27710287) is covered under GPL which is source available (see https://github.com/id-Software/Quake-III-Arena/blob/master/c...)

viktree

5 年前議論

> How does splitting code into multiple functions suddenly change the order of the code?

Regardless of how smart your compiler is and all the tricks it pulls to execute the codein much the same order, the order in which humans read the pseudo code is changed

  01. function positiveInt max(positiveInt[] values)
  02.   positiveInt max = 0
  03.   for (positiveInt i=0; i < values.length; i++) 
  04.     max = values[i] > max ? values[i] : max
  05.   return max

  07. function positiveInt total(positiveInt[] values)
  08.   positiveInt total = 0
  09.   for (positiveInt i=0; i < values.length; i++) 
  10.     total = total + values[i]
  11.   return total

  12. function positiveInt calcMeaningOfLife(positiveInt[] values)
  13.   return total(values) - max(values)

Your modern compiler will take care of order in which the code is executed, but as humans need to trace the code line-by-line as [13, 12, 01, 02, 03, 04, 05, 07, 08, 09, 10, 11]. By comparison, the inline case can be understood sequentially by reading lines 01 to 07 in order.

  01. function positiveInt calcMeaningOfLife(positiveInt[] values)
  02.   positiveInt total = 0
  03.   positiveInt max = 0
  04.   for (positiveInt i=0; i < values.length; i++) 
  05.     total = total + values[i]
  06.     max = values[i] > max ? values[i] : max
  07.   return total - max

> Better? No?

In most cases, yeah probably your better off with the two helper functions. max() and total() are common enough operations, and they are named well enough that we can easily guess their intent without having to read the function body.

However, depending on the size of the codebase, the complexity of the surrounding functions and the location of the two helper functions it's easy to see that this might not always be the case.

If you want to try and understand the code for the first time, or if you are trying to trace down some complex bug there's a chance having all the code inline would help you.

Further, splitting up a large inline function is more trivial than reassembling many small functions (hope you got your unit tests!).

> And sometimes it does not even make sense to keep this order.

Agreed. But naming and abstractions are not trival problems. Often times it's the larger/more complex codebases, where you see these practices get applied more dogmatically

コメント