mhenr18

> same with the front passengers, who don't have anyone reclining against them. You pay economy, you get economic space

Front-row seats and exit row seats are paid upgrades because of the extra space. They aren't paying economy - they're paying slightly more.

Hey, producing indoor maps of private spaces is an area I've been working in for the past few years and I know exactly what you're dealing with.

I'd be happy to talk more about this if you're interested - email is in my bio.

I bought a new HP Stream recently and it's been delightful to run Lubuntu on - everything worked out of the box. Even two finger scrolling in Firefox with the trackpad.

I have other machines that I use for my day job, but it's such a fun little computer to use.

I work on an app that edits and renders fairly complex indoor floorplans to SVG, all using React.

We deal with large hospitals and airports, so it's normal for us to have tens of thousands of components mounted at once - pagination isn't a viable solution for our purposes.

We've had to tap basically every optimization that React apps can do when managing large numbers of elements - however this has been worth it for us:

- We can use the same code to render interactive plans on the client, and to render to print-quality PDFs on the server - We can use the same framework in our UI and plan rendering

The downside is that it's more CPU intensive than alternatives like a WebGL renderer, but for now that's a tradeoff worth making.

It is worth noting that while it's totally possible to fly domestically in Australia without having your ID checked, you're still required to have one.

I'm actually quite happy with the facial recognition cameras at the Australian border - they make things a lot faster than they used to be from my experience.

Parking minimums in residential areas are one of the few times I think they can make sense.

Suppose there is enough on-street parking for other non-residential uses. You don't want these spaces being constantly used by car owners who are living in apartment complexes that aren't meant for them. As a local government, you have to play the game of not letting them park using parking restrictions while potentially also managing by-laws that allow residents to get parking permits that let them bypass some restrictions.

This doesn't really apply in high-density urban areas, but I could see it being tricky to manage in growing areas.

(Although, I guess from a non car-owner's point of view you wouldn't care about whether other drivers are being inconvenienced by a lack of parking, because the knock-on effects wouldn't affect you.)

Daylight saving time doesn't apply to the winter though.

Winter time is standard time, and DST is in effect during the summer months to better make use of the extra light available during summer by winding clocks an hour forward. The idea being that you get an extra hour of sun in the afternoon.

As a data point, my company is using yarn workspaces where one of the projects is an Electron app, and another has a Node server with native dependencies.

Our nohoist section currently looks like this in order to get things to behave:

  "nohoist": [
    "**/electron/**",
    "**/electron",
    "**/electron*/**",
    "**/electron*",
    "**/canvas-prebuilt/**",
    "**/canvas-prebuilt"
  ]

These are likely going to require auto-ejection due to being native and having postinstall scripts.

Would it make sense to not bother with hoisting of ejected modules when using YPnP, given that YPnP solves the same problems as hoisting in a more global way? We'd be able to get rid of the nohoist section in that case.

JS (and eventually wasm) calls the OS via requiring native modules, which is why we're concerned about keeping them around.

Wasm is designed to deal with the VM sandbox, which if you're writing a server is fantastic compared to actual native code as there's better security properties.

It's not fantastic if you're working on an Electron app where there might be one specific feature that requires a native module in order to hit an OS API that you can't do from a browser sandbox (and that Electron itself doesn't expose).

Rather than pursue total deprecation/eventual removal of postinstall/native modules, I think a package.json "allowNativeDependencies": "never" | "devOnly" | "always" option that defaults to "devOnly" if not specified is the way to go.

Their current Animate product (they renamed Flash Pro) is pretty much what you're looking for, if I'm not mistaken.

Clearly you don't live somewhere where speed limits are rigorously enforced. Setting a limiter frees you up from having to match the limit yourself and allows you to pay more attention to the road.