lubutu

I initially read "the order of files in /etc/ssh/sshd_config.d/" to mean the order of files in the underlying directory inode, i.e. as returned by `ls -f` — and thought, "oh god"... But the lexicographical order, that's not too surprising.

lubutu

昨年議論

I mean, no. If you work on a codebase that's been going for more than a few years, the author likely doesn't even work there anymore. The commit is the important thing.

lubutu

2 年前議論

C23 has constexpr, albeit only for objects, not functions. The code also uses namespaces, as in `std::aligned_alloc(P, T)`.

lubutu

2 年前議論

Meanwhile, Kerberos (also Project Athena) has been at version 5 since September 1993.

lubutu

2 年前議論

There has been recent work on RPC-with-TLS (RFC 9289), xprtsec=mtls.

lubutu

2 年前議論

> NFS still sucks (IMO it sucks more than it used to)

Any chance you could elaborate?

lubutu

2 年前議論

The distinction I suppose is that what you really mean is "the difference in [necessary] skill level between a burger flipper and an accountant".

lubutu

2 年前議論

I suppose such feedback could be used for reaching a fixpoint. Suppose you have a build system that reads targets to be built from stdin and outputs to stdout targets that are dependent on that target and must now be rebuilt. With an ouroboros, the build system will continue to run, even if the dependency graph is dynamically cyclical, until the fixpoint is reached and the build terminates.

lubutu

2 年前議論

I mean, learning Haskell has made me a better programmer even if I've never used it at work.

Perl I have used. I wouldn't say the same about that...

lubutu

2 年前議論

It does make sense — the Unix debugger has always been *db, with no bridges in sight.

https://en.wikipedia.org/wiki/Advanced_Debugger

lubutu

2 年前議論

You can do...

  <access.log head -n 500 | grep ...

... though that's less familiar to many, I'm sure.

lubutu

2 年前議論

> So the idea is really "what's the point of having a history full of broken state?".

I rebase commits so they don't break the build but the history remains clean and incremental. Selective fixups and so on isn't the same as squashing everything into a single commit.

> This would be a hint that your PR was too big and addressing more than one thing.

I don't think so. Sure, that can be true, but squashes can also simply lose vital history. Suppose you remove a file and then replace it with code copied and modified from another file. If you then squash that, all Git will say is you made a massive edit to the file.

lubutu

2 年前議論

You're not the only ones, but I can't understand this approach. Do people never then read the version history? It must be impossible to understand commits' diffs with the changes all squashed together.

lubutu

2 年前議論

It's not by the same person — sta.li was by Anselm R Garbe. It's more like a spiritual successor.

lubutu

3 年前議論

Thanks for sharing!

  ; these produce an error, since `b` isn't defined when the body of `a` is compiled
  let a = \x -> (b x * 3),
      b = \x -> (a x / 2)

It surprised me when this was called out, given that both a and b are defined in the one 'let'. Was there a specific reason you decided not to treat it as a 'letrec'?

lubutu

3 年前議論

Lurrus into Dead Weight — that's a nice start.

lubutu

3 年前議論

I think this is the one thing I feel BitKeeper does better than Git. Git can get confused about where a file came from, for moves but especially for copies, and so the version history ends, even if you ask it to try and follow along. BitKeeper, on the other hand, keeps the moves and copies as part of the history, so you can always trace it through to the origin of the file, no matter how circuitous.

lubutu

3 年前議論

I looked around and found an AMA [1].

> Python, using the Twisted framework for networking.

> Omegle runs on just one server: a Linode 2880. It used to be on a 720, which was very close to sufficient. No database at the moment, but if it never needs one, I'll most likely use PostgreSQL.

[1]: https://www.reddit.com/r/IAmA/comments/9vbd7/i_made_omegleco...

lubutu

3 年前議論

When I was looking for work back in 2016 there was a company who advertised their way of working as "infrared", if I remember correctly. It was all about total openness and autonomy. For example, they asked one employee to decide how many hours everyone should work per day, and they decided on something, which was then applied company-wide. This was apparently "democracy in action". Quite odd. I think they've since dropped that whole thing.

lubutu

3 年前議論

You know another project with much of its source files in the top-level directory? https://github.com/git/git

投稿

An introduction to the UTF encodings

An Introduction to Condition Handling for Non-Lispers

The Linguistic Interface

ParaSail: A Pointer-Free Path to Object-Oriented Parallel Programming

There Is A Horse In The Apple Store

One Hundred Years of Laziness

On Structural Regexes – the theory behind multi-editing

On Profiling, And Google’s Big Double-Cross

The Weave

Guarded Continuations

Ivo – a reimagined Unix terminal system

コメント