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.

Every so often, posts from Bruce Dawson's blog get posted here - one such post was about using Event Tracing for Windows to diagnose an issue with an NTFS lock being held causing 63 cores to idle while 1 does all the work.

https://randomascii.wordpress.com/2019/10/20/63-cores-blocke...

A few months later, some other people in my team were struggling to diagnose an issue in production where a legacy webapp was struggling to scale up and fully use all 64 cores of the server we needed it to run on. I stepped in to help and remembered that post I'd seen on HN. We used ETW (through Windows Performance Recorder and Windows Performance Analyzer) to profile our app and I looked into the Wait Analysis. Turns out that Entity Framework 6 uses a ReaderWriterLockSlim to guard a cache, and that particular lock performs extremely poorly under heavy contention. Heavy in our case meant that for a single page build of one of this app's "hot path" pages, this lock would be taken a few hundred thousand times. We weren't the first to discover this:

https://github.com/dotnet/ef6/issues/1500

What some other people in my team were struggling with for about two weeks was resolved in a single day thanks to me goofing off and reading HN. (We ultimately used a fork of EF6 that didn't suffer from this issue to solve our problem)

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.

I couldn't resist trying this and making some more detailed instructions for getting better images out of iOS. Turns out that you can get fairly good results without any fancy software.

https://mhenr18.github.io/improvised-document-camera/

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.

I hope by smooth you're referring to the graphics being vector vs bitmap, because Flash performed really badly once you added any kind of complexity to a scene. (edit: simple things worked brilliantly though, and often that was enough.) The key innovation of Flash was and still is the creation side of things in Flash Pro rather than the runtime.

My main experience was with Line Rider. I didn't create it, but I became involved in the community and started making tweaked versions with tools that made it easier to create tracks (as opposed to versions that let you do things like change the physics or the rider).

Every line you added to a track caused a new MovieClip to be added to the scene that had a line drawn in it. By the time you had around 3,000 lines or so you'd start to get reduced framerates. 3,000 lines sounds like a lot, but is tiny when you consider tracks that have accompanying artwork.

A few years ago, we released a JS + WebGL rewrite of Line Rider that has a physics engine that's bug-for-bug compatible with the original (you can play it at https://www.linerider.com/ if you're interested - sorry if that's too self promotional). With access to WebGL and a massively faster ECMAScript runtime, the JS version runs multiple orders of magnitude faster than the original Flash version.

It's now possible to work with tracks that have hundreds of thousands of lines without experiencing frame rate drops as opposed to just a few thousand lines. So as for web platform tech underperforming from a runtime point of view, I disagree.

The problem is that all the ingredients are there to make something great, but the developer effort required is monumental in comparison to how fast it was to make something work with Flash Pro.

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.

It's worth pointing out Qantas is the exception to your point. More incidents on Qantas flights are due to causes outside of the crew's control than due to human error. Even then, Qantas hasn't lost an airframe or had any fatalities since the dawn of the jet age.

It's more that you can't tell the difference between 30C and 30.5C. No one ever forecasts temperatures using decimal degrees here in Australia.

You only need decimals for highly accurate measurements, but at that point you'd need decimals for Farenheit as well.

> You tell Europeans

Erm, how about the rest of the world?

Australia. It's all covered under the Sex Discrimination Act.

https://www.humanrights.gov.au/our-work/sex-discrimination/p...

No.

At least in my country, all of the ways that females can be discriminated against in the workforce that are usually brought up are illegal.

(Pay gaps for the same work, promotions, sexual harassment, etc)

Yet people still complain they are problems. At this point, the onus is not on the rest of society to continue to try and make things easier for literally more than half the population. The onus is on the people being discriminated against to actually stand up for themselves and aggressively puruse legal action if they are the victims they claim to be.

For me personally, I find it quite ridiculous to hear people talking about all the gender stereotypes that exist today (and the discrimination that comes alongside them) and how we need action action action to solve them as if they are still problems.

My dad cooked more than my mum. I was picked on by girls at school. The girls always were told it's fine if they wanted to play a sport more dominated by guys, but god forbid a guy try to play sport with the girls. Rather than being discriminated against, the girls I know who went into software got given hugely preferential treatment over the guys and are routinely given better opportunities.

In everyone's effort to undo gender discrimination, they've forgotten that the aim is not to swing the pendulum to the other side, but instead to bring it back to the middle and treat people on their own individual merits.

Not until Windows HiDPI support stops being a disaster.

The definition of Retina varies based on viewing distance. The DPI needed for Retina in VR is a heck of a lot higher than what's needed for a smartphone.

IMO we need to go through at least two resolution quadruplings on the Vive to get it to be crisp enough for the screen-dooring to not be noticeable.

It isn't?

It's fairly common in Hong Kong's denser parts like Central. I was able to get around much of the heavily trafficed areas without needing to be at street level.

I noticed this behaviour in the smaller streets of Hong Kong as well. Makes a ton of sense to me.

It's interesting that a lot of people act like living in those big cities is a necessity rather than the luxury that you've pointed out it really is.

If people aren't running make with -j, do you think they really want their build to take advantage of all cores in the first place?

My argument is not specific to telemetry, it's a general one. If you have an option to do something that's not a default and it's not part of the software's core functionality, most people aren't going to consider it even if it would be to their advantage. For example, make -j.

It's for that reason that I don't think the "if they aren't turning it on then they don't want it" argument holds as much water as you think it does. That argument groups together three groups of people: people that know about the setting and don't want it on, people that don't know about the setting and don't want it on, and people that don't know about the setting and would be happy if it was on.

Ironically, if you had good telemetry you'd be able to figure out how many people fall in to each group and make decisions about settings based on accurate data. Without that, you're forced to work on assumptions.

> Your entire argument essentially boils down to, "I'm sure I can get away with taking my users' information by making it the default behavior with a buried notification and I can placate people who care about privacy with an opt-out."

I think you're making the assumption that telemetry has to violate your privacy in all kinds of heinous ways and therefore only be a bad thing. If that's your mindset, of course you're going to think that I'm the kind of person that's out to trick and fool people and betray their privacy. And in all fairness to you, it's reasonable to be jaded when companies like Microsoft have horrible things like P2P software update distribution enabled by default. It's reasonable to be jaded when you don't get told exactly what kind of data is being sent back as telemetry. There's a fine line between "this is good" and "you're just relying on people not knowing how to change the defaults in order to try and get away with horrible things" and all too often that line is crossed.

But I'm an idealist. I see the good things that can come out of having telemetry. I want to know if my software has started getting popular in locales that I haven't written translations for yet so I can commission a translation to improve the experience for people in that locale. I want to know if there's a setting many people turn off so that I can consider turning it off by default to match user expectations. I want to know if my users are sticking to older OS versions because if they are I need to keep older hardware around in order to test and provide them the best possible experience.

I don't think anyone would have an issue with software sending back that data (and only that data) if you clearly tell them that's happening, and I also think that most people would be perfectly fine with that being a default behaviour. Of course, there is always going to be a group of people that will have an issue with sending back that data and that's why I made the point about keeping it as an option.

That group isn't just "pesky users who I only care about for promotion" (perhaps I was too flippant about saying that in my original comment). They could be trying to harden a machine so that it only uses the network under known circumstances. At the same time, you'd hope that software intended for use by people who need comprehensive privacy like whistleblowers wouldn't have telemetry at all.

Given that OS X isn't 100% free software, no one should be using brew in that kind of comprehensive privacy situation and so having telemetry isn't inherently bad.

It's the "clearly tell them that's happening" bit that's the issue here. If you have software that has been around for a long time that doesn't do something and then in a new release it starts doing that thing, you need to let people know that! It doesn't matter whether that's telemetry or anything else - if it's something that violates existing expectations you need to tell your users loud and clear.

Let's assume that 90% of people don't bother to turn off telemetry and 10% do. That also means that in your preferred scenario, 90% of people wouldn't bother to turn it on and the 10% also wouldn't turn it on either. If you can't be bothered to turn something off, why would you be bothered to turn it on?

That means that you'll either get something close to 0% telemetry if it's default off, or 90% if it's default on. So, it makes sense to be default on if you want your telemetry dataset to be big enough to be worth it.

But then we get to your question - why bother with an opt out? Well, if the decision is either to use the product and send telemetry or not use the product, that 10% of people aren't going to use your product. They care about not sending telemetry that much.

At that point, as a dev you just have to ask yourself is it really worth losing 10% of your users to an always-on telemetry policy or is it OK to make the concession of allowing an opt out in order to grow your user base?

Personally, I'd rather make the concession and get that 10% of people on board. If they're vocal enough to complain the shortcomings of my product they're probably vocal enough to also talk about the good things and give me free advertising.

I've never seen right wingers talk badly about Clinton due to her gender. I've heard plenty of talk on almost every single other one of her traits, but I think the progressives in the US are a bit to quick to pull out the sexism/racism card.

Don't forget that the people working in said public services also need to open holes in their schedules to access the services that other companies provide.

What kind of hour staggering were you thinking about to try and solve the scheduling problem?

Actually I can't use Win + direction anymore because on Win10 it immediately nags me to pick what other window should fill the other half when I don't want to do that.

I use Windows more than OS X these days.