mlex

One factor I'd like to bring up here is that it's significantly easier for Canadians to work in the US than it is for people of other countries. Canadians have access to the TN visa, which is effectively automatic, while most other countries need an H-1B, which is lottery-based (last time I was in the lottery it was about a 1/3 chance of getting it).

As a result, I think "non-Canadians who came for their undergrad and now moving to wherever they get the best job" is a smaller set of people than you'd think, simply because they're held back by the (Byzantine) immigration system in the US.

Another related factor is that if you go to an American university for undergraduate CS rather than a Canadian one, you get the opportunity to use OPT (https://en.wikipedia.org/wiki/Optional_Practical_Training), which gives you up to 36 months to roll for an H-1B visa. Add onto that the fact that there are so many good American CS universities to choose compared to Canadian ones, I'd expect most international students to study in the US versus at Waterloo if their goal was to work in California.

As someone who graduated from Computer Science at Waterloo, this is common for anyone with the ability to do so. Pay is not competitive in Canada, and contrary to the common refrain here, taxes/rent/general CoL does NOT make up for this, not even close.

...did you take it in room DC 1350? ;)

I don't get this concern. What specifically are you worried about here, that a bad parameter will crash the program? The code is there in case you wanted to verify it's not doing anything nefarious.

This looks like just a cute script/program the author wanted to share with HN, I don't think it's a big deal if they didn't fully productionize the thing and just wanted it to be seen.

This is a pretty big fiasco for this huge of a release... I think the last time I remember blowback this hard was with No Man's Sky a few years ago. Different situations though (No Man's Sky straight up broke promises about what gameplay was supposed to be like)

That’s the idea I’ve gotten when looking around online. I figured I was in the uncommon situation of having a completely blank and ready system, so I could afford to just wait a few days.

Just built a FreeNAS system over the past couple weeks and finished doing burn-in tests of my hard drives, wonder if I should wait and see how to install OpenZFS 2.0.0 before I create my storage config.

I mostly do iOS work, and I find ADTs useful for representing UI state machines.

For example, if I have a view controller (screen) that async loads data, I can have an enum State (in Swift enums have associated values), with the following cases:

- An initial state with nothing - A loading state that contains the associated Promise that represents the network request (which I can cancel) - A fully-loaded state with the data model I got back from the network - An error state containing an error object I can display to the user

Also, the most common use case for an ADT in Swift is representing Optional, which is when you have a nullable object.

As someone who's gone through both H-1B and PERM, H-1B only needs the company to prove two things, specifically about how much you're paid:

The actual wage: This is the wage paid to other employees in the company who do the same work.

The prevailing wage: This is the wage for that occupation in the geographical area.

See: https://en.wikipedia.org/wiki/Labor_Condition_Application##1... https://en.wikipedia.org/wiki/H-1B_visa#Labor_Condition_Appl...

There's no need to speculate on "what's plausible" when it's a documented process: https://news.ycombinator.com/item?id=24703643

This is incorrect. From https://en.wikipedia.org/wiki/Labor_certification#Difference...:

Temporary work visa: H-1B, H-1B1, or E-3

"The employer needs to demonstrate that the worker is being paid at least the prevailing wage for that region and occupation, and comparable to native workers in the firm, and that employing the worker will not adversely affect current workers. The employer does not need to demonstrate that there is no qualified native U.S. worker for the job."

Compare that to:

Employment-based visa (such as EB-2 visa, or EB-3 visa) that provides a path to permanent residency (a Green Card)

"The employer needs to demonstrate that there is no qualified U.S. worker willing to do the job at a comparable wage, and needs to have made a good-faith effort to recruit a native U.S. worker."

You only need to demonstrate an effort to recruit someone when applying for a green card.

As someone who still lives in SF right now, it and NYC are still expensive relative to the rest of the country, even if people are getting better deals on rent at the moment.

Swift has Never, which is the return type of functions that don't terminate, such as fatalError().

https://developer.apple.com/documentation/swift/never

It's currently not implemented as a bottom type in the sense that it's not the subtype of all types (discussed in https://nshipster.com/never/).

In case you're reading the comments first, Linus isn't actually building Torvold's actual PC for him, he's building a PC with the same specs as Torvold's.

I re-negotiated my 2B2B rent down from $4700 to $4200, and honestly could've gone lower (landlord accepted our first offer).

The most important thing for me in this process was doing the research on comparable properties in the city and spreadsheeting it out (sqft, rent, location, and amenities). I presented that spreadsheet, showing there were obviously places I could move to that were much cheaper with similar to better benefits.

Ultimately all negotiation is about showing that you're willing to walk away for a better alternative, and it's pretty clear there were good alternatives given the current SF housing market.

The parent comment is referring to conditions that have changed due to COVID (most businesses close their bathrooms now), not how available bathrooms were historically.

San Francisco has great restaurants and food, and I'd argue that "from the urban core and used to it" basically just means "I enjoy having these amenities like nice restaurants to go to".

No, demand is just lower because companies have everyone working remote for the time-being, and so for a lot of people it doesn't make sense to live in the city and pay SF rent while just sitting at home.

Instead, people are just moving to lower cost-of-living cities and working from there, so there's less demand for apartments and landlords have to lower prices to compensate.

This is definitely untrue for present-day Twitch. When you're in a chat room, you're in the chat room with everyone.

This is just the wall-adapter head for Hong Kong/Singapore/UK being fragile and they're offering free replacements for affected customers. Seems like the right way to deal with this, and they've done similar replacements in the past for other power adapters.

The article seems kind of light; all of the stuff I expected to read was summarized in the "The Tech Architecture" section, then the article suddenly ended. It felt like they spent three sections on background information and only one on details about the new player.

Yeah `self.` is implicit. In Swift:

  struct S {
    var string: String
    func doSomething() {
      // These two lines are equivalent.
      print(string)
      print(self.string)
    }
  }

I don't know if anyone who can edit the blog is reading this, but the link to "SE-0186 Remove ownership keyword support in protocols" is wrong, it should point to https://github.com/apple/swift-evolution/blob/master/proposa...

They do if you want an interface that's similar but scaled up. Alien Blue for iPad was different though in that you had multiple columns open at once, which probably did require more dev time to handle. I'm thinking they wanted a more tailored experience for iPad and didn't have time to design/implement it. Too bad though.

But that's kinda the thing; how do you end up finding out about them? Unlike buttons which appear on-screen, 3D touch interfaces aren't immediately visible and require special onboarding, which isn't always great even with conventional features.

Another example, a great feature in Google Maps on mobile is the ability to zoom with one hand. You double tap and drag (tap, tap-and-hold, drag), but I only figured this out because some blog talked about it. From what I can tell there are no instructions in the app that tell you about this feature, and I see this as being in the same vein as 3D touch. Sure it's great, but if people don't know about it or can't learn about it easily, they won't reap the benefits.

The page is comically broken in Firefox, which is weird since usually Apple's product pages are fine. iPad images don't have transparent backgrounds so they show up with white boxes around them.

http://i.imgur.com/MKN2yS9.jpg

Since you seem to love nitpicking so much, it's a Leica.

I wouldn't say 3D touch is entirely a bad feature. I agree with the argument that 3D touch features are usually hard to discover (took me a while to realize you could press the keyboard to get a "trackpad"). Some of the features you get from it are nice little quality-of-life things though, like quick app switching. It will be tough getting app developers to decide to implement 3D touch features when it isn't supported by everything, of course.

More articles like this in Raymond's blog, which is full of anecdotes from his time at Microsoft.

https://blogs.msdn.microsoft.com/oldnewthing/

It's seriously so cool that the Homebrew guy (Max Howell) is behind this. Great fit for him at Apple. =P