oh how I'd love to see a gitlab GitHub like infrastructure and culture for scientific publication. let them have the repo private/authors and reviewers only until publication.
but all flaws are issues, later reported issues are right next to the paper, heck there could even badges for publication and review status...
there is a calibration marker on the glass and the liquid has to be filled up to that line, the froth on top is extra. so on the continent we get more, not less. so from where we stand it looks rather like the islanders are ripped off ;-)
I'm not denying this, but I do remember a jug of beer being ordered and me being asked to pour it into several glasses without noticeable markings, and me trying to end up with about a 1/4 inch of head as I would in the UK and my Dutch friends yelling "more head" or something even less than polite.
Mostly in the NL I drink bottled beer. And I'm a Yorkshire man, at least by birth.
I really liked working in the NL, but their food and drink I could not get used to. I did a bit of consultancy at KLM, and what was offered for lunch in the cafeteria turned my stomach - artificial meat, artificial bread. I complained about this to one of the KLM staffers I was working with - "We know, We know, and of course the bosses never eat here"
Also, the Dutch idea of Chinese food is very strange (basically some sort of Indonesian thing - and I like Indonesian, but not that).
Anyway you in no way requested a critique of Dutch cuisine, but I'm glad I got it off my chest. So, apologies.
* in the ICE world, California and EU norms created a tight barrier to entry. the patent portfolio protected the old automotive industry. they only built their patent protected ICEs, and they bought everything else from suppliers.
electric circumvents that barrier and that enabled dozens of new automotive OEMs: the first big disruptor
* automotive has created amazing r&d processes for the mechanical vehicle design. they are centered around early decomposition, isolated component engineering and then composition. integration in that world men's: screwing and plugging the pets together. if the hinges and flanges are to spec things integrate nicely.
too bad the hard part for software instead is system integration. consistency cross all components.
all the great hardware engineering processes are completely ND utterly misguided for software system engineering.. integrate rely, often, continuously vs clearly specified interfaces and isolated component engineering with expensive and thus relatively rare integration.
that's IMHO the second disruption for automotive.
ah that reminds me of when small startup SUSE was acquired by Big Corporation Novell. German engineers saying "no" and "yes" and "the F word! in meetings!" met very polite Corporate Americans who had twenty supportive soundings ways of saying no.
like
"this is an interesting idea" -> no
"we need to discuss this further" -> no
"can you help me better understand?" -> no
the only yes was "I do it, by such and such date"
so the jargon created a culture clash which only accelerated the decline.
and it also works for me when working with ai. that produces much better results, too, when I first so a design session really discussing what to build. then a planning session, in which steps to build it ("reviewability" world wonder). and then the instruction to stop when things get gnarly and work with the hooman.
does anyone here have a good system prompt for that self observance "I might be stuck, I'm kinda sorta looping. let's talk with hooman!"?
when does golang create the final dynamic dispatch tables? isn't that the one thing that in golang needs real compute at final link time, beyond what a C linker would do? and where C++ has all information at compile time, while golang can only create the dispatch tables at link time?
Yes, there is some information that is written by the linker in the final data section of the binary, the itab, that is the interface table for the dynamic dispatching. AFAIK, it is done there because you need to know other packages structs and interfaces to have the whole picture and build that table, and that happens using the build cache.
yes, the interface tables! that was the word I didn't remember. and that is some computation going on there not "just" merging sections, and, in a normal static linker, wiring exports to imports, and not pulling in unneeded definitions (dead code elimination).
the interface table computation is a golang speciality, a fascinating one.
and the implementation of interface magic is disturbingly not mentioned in the article.
but all flaws are issues, later reported issues are right next to the paper, heck there could even badges for publication and review status...
a woman may dream...
reply