fresh spring grass erupting fast

the distant engine purr comes

ouch goes the lawnmower

Beautiful. How did you come up with that? It's strangely captivating.

Just a normal haiku pattern and waiting for tests to finish, 5-7-5.

Could be 'wrong' since erupting is "technically" 3 syllables - but I think it sounds better said fast. Becomes a 7-7-5 that way. Same issue with 'lawnmower.'

At least with npm, you can have a .npmrc per-repo

I think this is useful in answering the grandparent comment's question:

stars : uniq(k)

1 : 14946505

10 : 1196622

100 : 213026

1000 : 28944

10000 : 1847

100000 : 20

each line (mostly) being equal length provides me an odd comfort

power law distribution ~1/x I think

Zipf's law?

only 80 more repos need 100000 stars and all lines would be equal! e.g.

1 : 14946505

10 : 1196622

100 : 213026

1000 : 28944

10000 : 1847

100000 : 100

you would lose 80 repos from "10000 : 1847" also in that case.

interesting that you only need ~150 stars on a project for it to be in the top 1%

Let's establish a roving band of ~150 GitHub users that go around 1% things.

Just finished it, 8/8. I mostly approached it by winging it and shuffling things around that looked good and like it was approaching the goal, since there's plenty of time to finish.

I still don't quite understand the exact mirroring rules at play.

You control the mirroring by moving the axis, they're what reflects your shapes. So my first move was always to identify the symmetries in the target shape, and position the axis accordingly.

This is the correct strategy for this particular game (center the mirrors between the yellow squares, move the black squares). I didn't realize it until about round 6 or 7.

I got stuck on 7/8 for a good while because I learned the rules wrong. I thought every bracket square needed to be lit.

A lot of that was due to LGA, yes. However, that doesn't stop those airports from being affected. Getting tons of traffic rerouted is inevitably going to cause delays across the whole airspace. Very useful to know.

Boarding is hard because it's at the discretion of the airlines, yeah. Departure time is easier because of https://www.fly.faa.gov/edct/showEDCT

> Departure time is easier because of https://www.fly.faa.gov/edct/showEDCT

If you're in the US!

True. I think you'd have to scrape it from sites that expose it or pay for an API for a country like the UK.

If you fly a lot, you might also be aware of the National Airspace System Status: https://nasstatus.faa.gov/

It also has links to a lot of other information useful for people in the airline industry.

I find the Airport Arrival Demand Chart to be good for seeing a big picture of all the flights: https://www.fly.faa.gov/aadc/

The equivalent for Europe is probably https://www.public.nm.eurocontrol.int/PUBPORTAL/gateway/spec... (at least what I use when there is major disruption).

And here's Canada's: https://spaces.navcanada.ca/workspace/ois/

I've never seen the nasstatus page, but I have seen the OIS page, which I use frequently when experiencing delays to find out what's going on: https://www.fly.faa.gov/ois/?legacy=true

The links on the NAS page are also really good. nice share!

What's wrong with React Native? I don't quite get your point there.

Speculating - but an iOS app that's build on React Native is not really a 'native iOS app'. Which might have some performance implications etc.

Just speculating, I've not done mobile development since before RN was even a thing.

Funny enough this was my first mobile app ever, I figured it out doing it. Expo helped a lot. The Apple review process on the other hand… that was a whole learning experience on its own.

God I feel you here, that first review is always brutal.

RN does use a lot of native code. It’s not based on a webview like Electron is. Most of the builtin components are native views and there’s no CSS. The JS engine is also simpler. It’s more akin to the lua runtime in Neovim.

Ah, I did not know that. I thought it was more Electron-like.

It’s a fair assumption. The React part is more about copying JSX and other React concepts (declarative UI etc) but it all boils down to native binaries. The toolchain is also pretty nice. It does hot reloading so you don’t have to recompile the app while building locally. The downside is you get less for free compared to SwiftUI. But SwiftUI also has many footguns and bugs. No free lunch!

Quite a lot. Enough that it isn't realistic to ask this in good faith

That's why we call it the US Customary System.