frogulis

Driving in Melbourne -- I won't generalise to the wider Australia -- is often much the same.

Comparing to the experience of being a passenger on a bike in Saigon, the level of cooperation there is way higher, possibly due to a sort of necessity. I had this feeling while observing traffic there, that, while the latency and throughput of the roads during high traffic times are still kinda awful, at least for bikes there's a slow continuous progress that simply wouldn't exist without cooperation.

Funnily enough, my experience driving in Los Angeles was distinctly not terrible. Traffic was usually good enough to drive in, though there was very little regard for the speed limit on the freeways! I suspect I may have just been lucky to miss the worst of the traffic.

First class functions and iterators are probably examples of what they mean, in terms of language features that obsolete (GoF) design patterns

It occurred to me at some point that what many "fine" foods have in common is fermentation. Tea, coffee, chocolate, cheese, alcohol, cured meats, dry aged meats, others I can't think of right now. Makes sense, as the complex biological processes are of course going to lead to the culinary complexity and variety that is necessary for connoisseurship.

Is there any reason today to use RSS over Atom? Atom sounds like it has all the advantages, except maybe compatibility with some old or stubborn clients?

Tangential question: what's an "armory gym"? Google gives me a specific gym (in Australia) called "The Armoury".

My read is: it's saying that if your executive compensation (etc.) is capped to a portion of the cost of care, and if your execs want to be paid more (etc.), then the required change is for the cost of care to increase.

Nothing special about the 20% proportion, just that it's proportional to a number which results in perverse incentives.

Which is funny, because my mind filled in the word "social media" and I thought it was a fair point, until I got to the word "Cable".

> I found the thesis of this article difficult to nail down

By the sounds of it, the author would be okay with that!

Been a while since I've watched/read it, but I remember the ideas in Maybe Not being quite interesting.

To me, the really important idea wasn't a criticism of static types in general.

Instead it was the idea that static typing in most (all?) mainstream implementations conflates concepts that should be separate, specifically the shape of the information that we have (e.g. what fields of what types), and whether a particular bit of information is available and required (e.g. nullability).

He contends that the former belongs in our usual "type definition", whereas the latter relates instead to a given context. For example, my PassportForm type always has a date-of-birth field in its _shape_, but whether it's statically required/present to exist depends on whether we're at a HTTP API boundary, an internal domain function boundary, writing into a database.

It sounded like that kind of "nullability masking" was intended as a feature of Spec, but I don't get the impression it was ever implemented.

Can't speak for the UK, but in Australia at least, "paracetamol" is the most commonly used non-brand name.

Even spoken aloud, there's a natural-sounding stress pattern that is ambiguous. Love it.

Thanks, that's gotta be one of the best talks I've ever watched. A passionate speaker, talking about fascinating, useful tech, giving specific real world examples of utility, AND showing how to actually apply it for interesting "dirty" situations.

Aw man, I was nodding along with the "most examples suck" section and then... it ended :(

In a classic case of the Baader-Meinhof phenomenon, I recently read "The Truth" by Terry Pratchett, which repeatedly makes reference to that phrase, and I am now noticing it everywhere, whereas previously I can't recall being aware of it at all.

I get the impression that Fennel is intended as a different/better interface for Lua.

In contrast, Clojure is intended as the language Rich Hickey wanted for writing the sort of applications he wrote, and the JVM happened to be a powerful (and already existing) platform that was suitable for doing that.

While I think this view is probably apt in other situations -- and to be clear, I don't know much about the company -- all of the specific techniques mentioned on the candidate's CV and in the article are fairly "garden-variety".

The pagination example seems like a perfectly reasonable thing for both sides to want to talk about, and which becomes relevant at a level of scale much smaller than Google.

What's different about the eastern part of the state? Is it as simple as having less rain and clouds to block out what sunlight there is?

A few colour changes and it would look fine. I don't know if it's the same software as lobste.rs, but it looks almost identical apart from the colours.

> I don't pretend that posts are evergreen by hiding their dates.

I didn't realise that hiding dates for the illusion of evergreen-ness was a desirable thing!

On my personal site I added dates to existing pages long after they were uploaded for the very reason I wanted it to be plenty clear that they were thoughts from a specific time.

For example, a bloggish post I wrote where, while I still think it's right, it now sounds like linkedin wank. I'm very happy for that one to be obviously several years old.

The GP commenter (ryeguy_24) is the original poster of this article, leaving additional information about what they posted.

Easy enough to write in some languages... as long as you only need to support addition and multiplication, or a very limited set of numbers.

Anybody correct me if I'm wrong -- in Pascal these subranges can specify the size of the variable in memory and check compile-type assignment to a literal value, but don't (can't) do much else.

There's the concept of dependent types in e.g. Idris which lets us correctly do this sort of range check throughout the program (not just on literal assignment) but it comes with strict requirements on what the compiler can allow, such as no unbounded recursion, because checking dependent types is roughly equivalent to running the program.

The "attrishing" in your comment made me go looking, and Wiktionary [0] says the verb form "attrit(e)" exists and is likely a quite old backformation that has fallen out of common use.

[0] https://en.m.wiktionary.org/wiki/attrit

Hopefully not a silly question: in the original example, even if we had enough log data coming from `tail` to fill up the first `grep` buffer, if the logfile ever stopped being updated, then there would likely be "stragglers" left in the `grep` buffer that were never outputted, right?

I infer from the wording in your comment that you consider Brainfuck to be a non-esolang. Your mind must operate on a different plane to mine!

I think you've taken it backwards. The comment you were replying to is listing features that lead to robustness (many of which appear in strongly-typed functional languages in the ML family), not essential aspects of functional programming languages.

That's a pretty incredible improvement. Was that from ongoing therapy over years, or did it gradually improve by itself after your childhood treatment?

Very similar to https://100r.co/site/ronin.html

Has anybody used both in anger?

I've been using tiny dried shrimp (bought from a Vietnamese grocery) and a little extra fish sauce as a sort-of substitute and I've been very happy with the final product.

I think the main difference between the two is, as someone reading and debugging the code, will probably eventually check even those methods that I assume I know roughly what they do. In contrast, I may not even think to check an overloaded operator unless I _already know_ that it's overloaded.

Maybe a good analogous method would be an overloaded `.ToString()` in C# that has side effects or returns the full text of the Magna Carta or something.