Hacker Newsnew | past | comments | ask | show | jobs | submit | mikepurvis's commentslogin

If this white Canadian woman traveling to California can be jailed for two weeks, then it can absolutely happen to anyone: https://www.theguardian.com/us-news/2025/mar/19/canadian-det...

As a Canadian, I'm refusing to travel to the US right now, despite working remotely for a US-based company.

It's not fear mongering, it's real. But my motivation isn't even just fear; staying home or choosing to travel elsewhere (Europe, Asia, Mexico) is standing with my countrymen against a regime that doesn't respect our sovereignty or even its own laws.


That sounds like US immigration has always been, during the GW Bush and Obama and Biden administrations.

It can be argued that a lot of this is falling into the slippery slope fallacy.

Also the media doesn’t always report the full story. Often the people arrested have some small/medium offense from years ago.

Unlikely to happen to legal immigrants.


Nonetheless, I will continue to choose to spend my travel dollars elsewhere until the US administration is crystal clear that Canada is a sovereign country, due process is a thing, and vanning people off of street corners (regardless of their skin colour or immigration status) is not the way.

Many of them have a small offense that would justify them being turned away from the border, but not an offense that justifies detention.

That’s fair. And if they can be turned away from the border, then they can be deported too.

I'm also pretty happy with my iPhone 13 mini and loathing having to upgrade to something much larger.

For reference, the 13 mini has a 5.4" screen, and the new-gen iPhones are 6.3", 6.5", and 6.8". Pixel 10 is 6.3" as well.

iPhone 5 was the most perfect size ever and was about 0.3" shorter than the 13 mini, though it had a much smaller screen due to the bezel: https://www.gsmarena.com/size-compare-3d.php3?idPhone1=5685&...


Exactly in the same boat.

Apple offering is underwhelming to say the least and way too expensive for my use case.

I want to go Android anyway, I'm too disillusioned with Apple currently, I'm tired of dealing with their predatory behavior. But there aren't a lot of decent options there as well but at least you can get it much cheaper, so that's something, I guess.

Previously Apple was the provider of hardware which made the right compromise to allow specific/focused use case, they called it "taste" in a sea of nonsense with bullshit "features". But now it feels like Apple has joined in on the nonsense and is actually leading the pack; which is why the price feels bad. If you are going to make the same crap as everyone else with the same set of bad compromises, I'm not going to overpay for it.

I think this is why Apple "AI" got so much backlash. If they didn't make it or at least market it as heavily as they, did it would have been fine, but it was just the same crap as everyone else, just worse and more expensive. They could have released the exact same phone, just shaving a 100 dollar and have been acclaimed and made more money that way I believe.


Me too, will probably keep the 13 mini for like a decade

I like how SkillUp handles it in the This Week In Videogames show when talking about release days; basically says "northern summer" which acknowledges that the publisher said summer while clarifying whose summer it actually is (eg, not his, since he's Australia-based).

Regarding controls, I have to play precise 2D games with a d-pad or I get immediately frustrated— that said, it was odd playing most of Celeste that way and then having to switch back to the thumbstick for the section at the end with the bubble comets.

Precision platformers are generally _much_ easier with the d-pad. Since hitting some such parts in Silksong, I've exclusively switched over to it.

Meanwhile I'm still pushing with thumb stick and sometimes miscasting skill or doing a side slash instead of downward.

It would take many hours to get used to dpad so I'm sticking to what I know, but it's definitely not ideal.


I don’t know of an easy way to fix that on the Switch. The keys are where the keys are.

Yup, Hunter's March converted me to d-pad.

Been a fan for a long time and use it on my Archer C7, but I had to disable hardware switching in order to use SQM, and now the switching performance is <200mbps. Having recently upgraded to home fiber, I'm probably going to get a native Unifi router.

Maybe have a look at Intel n100 boxes (Aliexpress -> Topton). They often have 4-5x 2.5GE Ports with high quality Intel cards. They are very cheap (100-200€) and suck not too much current (5-15W).

You can run OpenWRT on them using the x86 build.

We usually have 5-10x of them around for emergency network tasks if everything burns down in a building.


Honestly it is tempting. I do have an old Haswell-era industrial motherboard that would manage the task just fine, and I've definitely considered this path.

That said, I'd probably spend about as much on a power supply, case, and NIC for that machine as I would on just buying a Unifi gateway, and theirs comes with an integrated UI for the APs. I'm past the stage of life where I find joy in tinkering with the infrastructure I need to do my job (WFH) so I'll probably still just go off the shelf.


I bought a Fujitsu Futron S920 second hand for like 30 euros. Put a dual NIC PCI in there and now have a low watt router running very fast. Can easily run 1Gbit up and down

I feel this some days, but honestly I’m not sure it’s the whole answer. Every piece of code has some purpose or expresses a decision point in a design, and when you “abstract” away those decisions, they don’t usually go away — often they’re just hidden in a library or base class, or become a matter of convention.

Python’s subprocess for example has a lot of args and that reflects the reality that creating processes is finicky and there a lot of subtly different ways to do it. Getting an llm to understand your use case and create a subprocess call for you is much more realistic than imagining some future version of subprocess where the options are just magically gone and it knows what to do or we’ve standardized on only one way to do it and one thing that happens with the pipes and one thing for the return code and all the rest of it.


Is that what people do is test/develop primarily with local mocks of the services? I assumed it was more like you deploy mini copies of the app to individual instances namespaced to developer or feature branch, so everyone is working on something that actually fairly closely approximates prod just without the loading characteristics and btw you have to be online so no working on an airplane.

There are many paths. Worst case, I've witnessed developers editing Lambda code in the AWS console because they had no way to recreate the environment locally.

If you can't run locally, productivity drops like a rock. Each "cloud deploy" wastes tons of time.


Mocks usually don’t line up with how things run in prod. Most teams just make small branch or dev environments, or test in staging. Once you hit odd bugs, serverless stops feeling simple and just turns into a headache.

Yeah, I’ve never worked at one of those shops but it’s always sounded like a nightmare. I get very anxious when I don’t have a local representative environment where I can get detailed logs, attach a debugger, run strace, whatever.

SST has the best dev experience but requires you be online. They deploy all the real services (namespaced to you) and then instead of your function code they deploy little proxy lambdas that pass the request/response down to your local machine.

It’s still not perfect because the code is running locally but it allows “instant” updates after you make local changes and it’s the best I’ve found.


Yes to all of this with the provisos that a) there’s enough meat in terms of business logic and validation to justify the indirection of a separate object and b) you’re under a language or CI regime that can validate the boundary between the two classes for basic flubs like function misnames or bad arguments.

There's an analogue here with programming language iteration— Python, Ruby and friends showed what the semantics were that were needed, and then a decade or two later, Go and Rust took those semantics and put them in compiled, performance-oriented languages.

Electron has been a powerful tool for quickly iterating UIs and plugin architectures in VSCode, Brackets, Atom, etc, now the window is open for a modern editor to deliver that experience without the massive memory footprint and UI stalls.


I don't know if modern cameras are better for this, but a big one historically was getting a clean, realtime HDMI output so that high quality cameras can be used with a capture card for broadcast purposes as a replacement for a webcam. Manufacturers understand that that's a "pro" level need/feature and have intentionally segmented the market so that lower-tier devices can't do it even though the hardware is obviously all present.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: