> Some think they do - but don't. (idiots)
> Some think they do - but don't. (idiots)
Safari introduced “tab groups” a while back, which to me is an insane mess of complexity. When I think about it though they’re just folders and each tab is a bookmark/favorite.
The vertical tabs in Brave remind me of bookmarks/favorites too.
I need to know if I would switch. But I do not want to go to smaller company.
How does splitting code into multiple functions suddenly change the order of the code?
I would expect that these functions would be still called in a very specific order.
And sometimes it does not even make sense to keep this order.
But here is a little example (in a made up pseudo code):
function positiveInt calcMeaningOfLife(positiveInt[] values)
positiveInt total = 0
positiveInt max = 0
for (positiveInti=0; i < values.length; i++)
total = total + values[i]
max = values[i] > max ? values[i] : max
return total - max
===> function positiveInt max(positiveInt[] values)
positiveInt max = 0
for (positiveInt i=0; i < values.length; i++)
max = values[i] > max ? values[i] : max
return max
function positiveInt total(positiveInt[] values)
positiveInt total = 0
for (positiveInt i=0; i < values.length; i++)
total = total + values[i]
return total
function positiveInt calcMeaningOfLife(positiveInt[] values)
return total(values)-max(values)
Better? No?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
Existing JSON/YAML/etc could be compiled to WASM that simply builds the corresponding DOM.
Funny joke?
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