xearl

the copy on OP's pages is so full of claude-isms that it quickly became unbearable, for me. the claude-ism you quote above at least made me laugh.

Maybe get an E-MTB instead?

> while DuckDB effectively appeared on the scene two years ago.

duckdb is ~7 years old by now. it was quite popular long before it became 1.0. heck, even motherduck has been founded 4 years ago.

Did they ask the original authors of Radix why it's the way it is?

TIL, thanks a lot!

> For example, switching to another branch automatically checks out the active commit of that branch.

    git switch $BRANCH

> I would love something like that too use as a macro pad: keys that have arbitrary meaning you can reference. Keys that behave differently depending on context, and show you the context in real-time. That would be incredibly useful.

You might want to have a look at Elgato's Stream Decks.

(2017)

> Bonus: I now have zero interest in buying a Steamdeck.

It's still an absolutely amazing piece of hardware. So definitely play around with it, if you ever come across one.

These are single-sided, the Steam Deck requires a single-sided M.2 2230. Agreed that frame.work should mention that in their shop listing.

they (starlabs) charge via usb-c and have two usb-c ports.

Is there any chance to get this faster sync algorithm into rsync itself?

Your "different approach" sounds almost exactly like the approach proposed in the fine article for the "ESP too small" case (a case which you assume as a given).

> It was public doctrine in textbooks, taught at university.

Which book(s), at which university? Genuinely curious.

was flashbots a thing back in aug-2020? i think they only launched a few months later.

i regularly use K (an APL descendant) as "pseudo-code".

in fact, i regularly _think_ about problems in an array-programming fashion, heavily inspired by K. when jotting them down, i often use K. when turning them into actual code to run, it's mostly immaterial if i then use K, J, numpy, julia, etc. the general approach translates well into a multitude of array programming varieties.

as such, i don't believe your point 5 holds. this way of thinking is certainly off mainstream, as is, e.g constraint programming, but there are niches where people use it highly productively. you won't necessarily glean that from the output coming from those niches, though.

That page you linked to is for the Pro-1. The OP is about the newer Pro-1x.

FairEmail does support POP3 accounts.

chibicc is actually written by Rui Ueyama.

Github: https://github.com/rui314/chibicc

Previous HN: https://news.ycombinator.com/item?id=24676851

you can order 10g uplinks for most of hetzner's dedicated servers (for ~€45/m).

worth noting, at the end of christine's update mentioned above:

"I do not plan to make any future update posts about the V programming language in the future. The V community is something I would really rather not be associated with. This is an edited-down version of the post that was released last week (2020 M06 17).

"As of the time of writing this note to the end of this post and as far as I am aware, I am banned from being able to contribute to the V language in any form. I am therefore forced to consider that the V project will respond to criticism of their language with bans. This subjective view of reality may not be accurate to what others see."

for anyone considering getting involved, read christine's three articles on the topic first: https://christine.website/blog/series/v

14U colocation in Germany with 1 Gbps is EUR 100/m + power: https://www.hetzner.com/colocation

You can download all your Keep notes via Google Takeout.

And there's an unofficial Python API, that works well and is actively maintained: https://github.com/kiwiz/gkeepapi

The growth rate of infected deaths and the measurable mortality displacement makes that hypothesis extremely unlikely.

As does (albeit in a weaker form) the testing of the full population of Vò.

As does the testing in at least a few European countries, where the growth rate of tests outpaces that of confirmed infections. And/or where the number of tests administered vastly exceeds the number of confirmed infections.

Sure, once we have anti-body tests widely available, the data will become better.

Red requires Rebol 2, which is proprietary; Red does not require (and, in fact, does not work with) Rebol 3.

However, Rebol 3 (and it's active descendant Ren-C) bootstraps itself; it does not require Rebol 2.

"Screenshot": water.css (https://kognise.github.io/water.css/) + the following HTML snippet, per link:

  <p><a href="$url" title="$txt">$url</a></p>

These HTML snippets are what's saved, one per line, in the mentioned plain text file ("links.txt"). The webpage is a dump of this file plus HTML/CSS boilerplate.

The rule headlines:

  1: Be welcoming
  2: Help potential contributors evaluate if the project is a good fit
  3: Make governance explicit
  4: Keep knowledge up to date and findable
  5: Have and enforce a code of conduct
  6: Develop forms of legitimate peripheral participation
  7: Make it easy for newcomers to get started
  8: Use opportunities for in-person interaction—With care
  9: Acknowledge all contributions
  10: Follow up on both success and failure

> Or then I just couldn't find the document you mentioned in the previous post.

There you go: https://github.com/google/AFL/blob/master/docs/QuickStartGui...

The naming strikes me as quite unfortunate. Kdb+ is a (time-series) database that supports the languages K and SQL. Naming a product in a similar space KSQL was already a questionable idea. Jumping through the hoops of renaming only to choose ksqlDB (which, arguably, is even more confusing) is, well, unfortunate.

but even in this reply you describe the standoff very well yourself: after k8s replaces all amazon bloat to become the default AWS api, k8s has effectively commoditised AWS. i think that's precisely the point OP is also making.