The simplest cmdline I found to run it as a local server on a non-priveledged port with listings is:
$ caddy file-server --listen localhost:8099 --browse
Is there a simpler way I'm missing?3,222 karma · joined July 5, 2010
The simplest cmdline I found to run it as a local server on a non-priveledged port with listings is:
$ caddy file-server --listen localhost:8099 --browse
Is there a simpler way I'm missing?The shutdown endpoint is used for robust testing; I suppose I can hide it a bit more, like using an environment variable or something.
I maintain a somewhat related repo here: https://github.com/eliben/wasm-wat-samples/
What additional samples would you like to see in there?
> Hopefully we will be able to help with it as part of our work
That's great to hear. What are you planning here?
And Iceland doesn't even have a military, AFAIR. The country's total population is <400k
"Method calls are executed with at-most-once semantics. This means that Service Weaver does not automatically retry method calls that fail. However, you can detect and retry failed method calls explicitly using weaver.ErrRetriable. If a method call fails because of a transient system error (e.g., a component replica crashed, the network is partitioned), it returns an error with an embedded weaver.ErrRetriable."
With the following example:
// Retry the cache.Get method call up to five times.
var val string
var err error
for i := 0; i < 5; i++ {
val, err = cache.Get(ctx, "key")
if errors.Is(err, weaver.ErrRetriable) {
// Retriable system error! Retry.
continue
}
break
}
[The docs at https://serviceweaver.dev/docs.html are fairly comprehensive, kudos to the team!][https://www.songlyrics.com/baz-luhrmann/everybody-s-free-to-...]
;;; (bb
;;; x 1
;;; :db (y z) (foo)
;;; :mv (a b c) (bar)
;;; (do-something)
;;; :with open-file f "foo"
;;; (do-something-else))
And the code this replaces. This seems to me hard to understand without first digging into ergolib and grokking what bb means. It's just one simple example.I forget now where it was, but there's a famous Lisp quote which goes something like (paraphrased from poor memory): in Lisp you don't just solve problem X, you first grow a new programming language designed for solving X-like problems and then simply solve X with that.
This has its charms, for sure. But it makes the code harder to understand for folks not familiar with your "language designed for solving X-like problems"
This paragraph really resonated with me:
> All this is a reflection of the so-called Lisp curse, the fundamental problem with Lisp -- its great strength is simultaneously its great weakness. It is super-simple to customize Lisp to suit your personal tastes, and so everyone does, and so you end up with a fragmented ecosystem of little sub-languages, not all of which (to put it mildly) are particularly well designed.
I have a career-long love and admiration for Lisp, but I've never used it for "real" things because of this precise reason. I wanted my code to be understandable and modifiable by others who are already familiar with the programming language I'm using. With Lisp, it's almost guaranteed that any sufficiently large program will be written in its own dialect no one but the author knows.
Re Lisp's superiority - Lisp was certainly a superior language when it was devised many decades ago, but over time much of its comparative advantage has been absorbed by other languages. Starting in the 90s when productive, GC'd scripting languages like Python started being prominent this trend accelerated.
For a nice discussion of this see https://norvig.com/Lisp-retro.html
Or will the idea be more like "lefties should go to $SERVER1, righties to $SERVER2" and then the two servers don't federate with each other because they find each other's content distasteful?
Is the hope that just folks of a given political viewpoint will move to Mastodon and moderation will not be necessary?
We have all three on the shelf; kids first are drawn to the cute stick-figure comics, and read around a bit while they're there - the result is learning interesting bits and pieces about math.
Highly recommended! In particular the third book about mathematical games is a delight.
Parts of California produce more solar power than can be used at that time during parts of the day - could that extra electricity be used for desalination?
The bag of tricks CalISO has to lower demand at peak is fascinating - for example, there are large consumers with significant generation resources (like emergency generators) that sign in to turn the generators on and get off the grid for a couple of hours. This produces drops in demand without blackouts per-se. Distributed power generation is generally more resilient.
The IEEE Spectrum one seems independent
I'm not saying there's anything bad with Arc + Mutex - they're certainly useful tools and great in some scenarios; it's just that I wouldn't reach out to them just to "avoid fighting the borrow checker". If your code can be written without those tools, it's best to do so.