There's only one right answer:

Nybble - 4 bits

Byte - 8 bits

Snyack - 16 bits

Lyunch - 32 bits

Dynner - 64 bits

In the spirit of redefining the kilobyte, we should define byte as having a nice, metric 10 bits. An 8 bit thing is obviously a bibyte. Then power of 2 multiples of them can include kibibibytes, mebibibytes, gibibibytes, and so on for clarity.

ಠ_ಠ

And what about elevensies?

(Ok,. I guess there's a difference between bits and hob-bits)

This is incompatible with cultures where lunch is bigger than dinner.

I don't think this has been discussed on Hacker News before, but I wonder if people have any opinions about Arvados?

Lots of people love it. I don't like CWL much so I don't like it, but it's a perfectly cromulent choice.

The primary thing with all the workflow systems is to see what is abstracted and find out if it matches your needs. Airflow would never be suitable for what I want need (diverse tools in many languages, some needing conflicting library versions), Arvados would work but I prefer WDL or Snakemake or even NextFlow. Snakemake for incrementally building up a prototype pipeline or a one-off analysis. WDL when I need a production pipeline for years. NextFlow or CWL/Arvados when I need to fit into somebody else's culture or compute infrastructure.

Edit: and something I have never seen in any workflow system is a looping mechanism that allows testing for convergence or dynamic parameter sweeps, etc. only the homegrown systems, built on top of cluster management like SLURM, have been that flexible. But these homegrown systems for managing compute clusters were never quite mature and generalizable enough to release as open source, even if the company had been willing to open source them.

CWL has a loops extension now that can he used for your example of convenging algorithms, https://cwltool.readthedocs.io/en/latest/loop.html

And most workflow systems that support loops/cycles could be used for that too (e.g. Cylc, ecFlow, Prefect, Orchesta/StackStorm, Covenant, etc.).

Thanks for the CWL pointer; the evaluation of our team either got that one wrong when it was evaluated many years ago, or CWL added it, and in either case it's good to know.

I've driven between Boston and Montreal in a 2018 Prius Prime and got something like 60 mpg despite a large part of the trip being through the mountains of Vermont. Hybrids are a fantastic technology that, in a rational world, should have completely taken over the mainstream car market 15 years ago. Momentum seems to be slowly going towards PHEVs, which actually benefit even more from ubiquitous charging infrastructure than long-range BEVs. Unfortunately having owned a PHEV for the last 5 years, charger availability does not feel like has expanded at all, despite there being 10x as many EVs on the roads as 5 years ago. So if you can even find a charger, it is probably occupied.

"Manager" is a broad category, but in my case I am deeply involved in product design and technical architecture (with lots of input from my team) so I find that being able to plan a feature together, hand if off to one of my developers to implement it, and then see them successfully execute our vision to be just as exciting as if I had written it myself.

This is possible because I have exhaustive knowledge of the product, having worked on it for many years as an IC (and watched several other people struggle to manage it before I took the wheel). I imagine I'm a scenario where a manager and team are more disconnected, and nobody is really passionate about the product, that milestones would feel a lot more muted.

Yes, my recollection of the books is that it isn't about the need to keep consuming resources, it is about the premise that it is impossible to judge if another civilization is hostile or going to turn hostile

If your civilization can annihilated in a single strike, the only civilizations that survive have the strategy to a) avoid being detected and b) destroy anyone who has detected them (which results in destroying everyone, to eliminate uncertainty).

The idea being that assuming the actual survival of your species is at the top of your moral pyramid, all kinds of atrocities in its defense are justifiable.

Well it's all a side effect of nearly unlimited energy (I.e. enough to accelerate a mile wide asteroid up to nearly light speed) which cause asymmetry in warfare favoring offense. I'm sure humans would kill anyone outside their village/city if defense was impossible and anyone that wanted to kill your city/village just had to push a button.

Been checking the #roblox hashtag on Twitter and the two main themes are addicts going through withdrawal and devs saying how they wouldn't have their llama appreciation fan site be down this long let alone your core business.

There seem to be some misunderstanding here.

CWL is intended for stringing together other programs. It is useful for reproducibility in that it attempts to provide a fairly specific description of the runtime environment needed to execute a program, and also abstracts site-specific details such as file system layout or batch system in use. CWL platforms such as Arvados also generate comprehensive provenance traces which are vital for going back and reviewing how a data result was produced.

Leibniz seems to be a numerical computing language for describing equations, which is more similar to something like NumPy or R. It seems like an apples-and-oranges comparison.

The original call-out is weird, because CWL did not exist 10 years ago so you can't yet answer the question yet of whether it facilitates running 10 year old workflows.

I use RssDaemon on Android, which had been around forever (8-9 years maybe?) is apparently so dead that the author just released a new version with major UI update.

My most used been apps on my phone are RssDaemon and Twitter. I read Hackers news though RSS. Twitter on the other hand has been getting worse.

The backlash against centralized social media platforms is building, but it is hard to say what comes next.

I was really hoping this would be structured as a set of assertions which would then be used to generate answers in response to queries.

The Pacifica plug-in hybrid is a fantastic minivan that can go up to 30 miles all electric before needing to engage the ICE, and in hybrid mode it still gets significantly better milage than a conventional ICE minivan.