weiming

A good friend actually used June Advisors Group mentioned in the article a couple of years ago. The firm (really a sole attorney) sounded very helpful and got his business set up with a residence card pretty easily. IIRC it took a couple of months end-to-end.

What me and my family talked about today is that, as immigrants, we are so sad how much the "native born" people of the US hate their own country. They seem to never waste an opportunity to remind others of their disdain and it is more and more visible these days e.g. in big news media or on Twitter.

Makes me sad and I hope this can change.

Nitpick but I hope the overtly (about 10px) rounded corners of running app windows aren't there to stay. Looks heavy/dated.

Curious question as I am not a compiler expert.

I have to do front-end iOS work from time to time and it's surprising how bad auto-complete can be in Xcode with Swift even after all these years: still randomly sluggish, randomly stops working inside closures including completely losing syntax highlighting inside the closure, and even Cmd+clicking to see the definition is a hit-or-miss as it sometimes opens up a blank editor and just spins. I would have thought that Swift having a strict type system would have made the IDE experience better, not worse. Don't know if the grammar is too complex or if it is the bridging with ObjC stuff or something else that made it difficult to build a robust solution. Can anyone shed light on this?

My points of reference are rust-analyzer, or just VSCode with Typescript, both very snappy although of course the languages are very different. If anything I'd expect Swift to be closer to Rust experience-wise since they both have pretty strict grammars.

Twitter has been indispensable for on-the-street/real-time video reporting (just search for city name). Even reached normally quiet Portland.

ﱞ

And so I use create-react-app anytime I need to start a front-end JS/TS project, even if I am not using React at all. Basically avoiding dealing with troubleshooting the soup of build time dependencies and mismatching package versions, which unfortunately comes with the modern JS (or node) ecosystem.