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

That's not what the parent comment is talking about.

Calling over the cellular network has been prohibited since time immemorial. What the parent comment is talking about is carriers also prohibiting making calls over airplane-supplied WiFi.

You can't, for example, join a Zoom meeting, or use your phone's built-in WiFi calling ability, on a typical flight nowadays, for better or for worse.


> I’ve never seen a C to Micro. Do they even exist?

They do, in spades: https://www.amazon.com/3FT-Micro-Data-Charge-Cable/dp/B0DDWH...

I look forward to the day when they're no longer necessary.


Same. It's not a good look to have happen right when they roll out a new model.

That's why nextpnr exists :)

https://github.com/YosysHQ/nextpnr

As someone actively working on nextpnr support for a fairly new FPGA architecture, it really is amazing that we have something like that in the open source world.

YosysHQ are one of my favorite companies to exist.


Nextpnr and Project X-Ray are amazing projects. Reverse engineering the physical map of, say, a 7-series FPGA is no small feat. However, I wonder if they'll ever be able to really compete with Vivado without getting access to the characterization models for timing. I would love to switch over, but the Fmax of my project routed with nextpnr is less than half of what I get with Vivado.

Fun story: I used to own a Prius, and it turns out they expose the speeds and torque values of MG1, MG2, and the engine independently on the OBDII port.

What this means it that you can set up an app like Torque[0] and add widgets that show you how fast each of the motors are spinning, live, and watch what happens when e.g. the engine starts: MG1 and MG2 both torque the engine forward, MG2 just enough to stop the car from attempting to roll backward in response to MG1's torque through the planetary gearset, and then MG1 spins up with the engine and then stops torquing it once the engine reaches idle.

Battery charging while idling is similar: MG1 turns itself into a generator, fighting the engine and generating electricity in the process. The throttle opens considerably, as if you'd pressed the accelerator halfway to the floor, but MG1 and the engine work together to keep the engine's RPM around ~1,200 so you'd never know it - it's as if you're driving up a really steep hill that stops you from accelerating even though you have the gas pressed halfway down. And then MG2 torques backward to stop the car from rolling forward any more than the Prius's normal "simulate a normal gas car's tendency to roll forward when the user lets their foot off the brake" would have it do.

It was fascinating to watch, and I kind of regret not building an app similar to the parent comment's link that showed what my car was doing in real time with the gears drawn out like that.

[0]: https://torque-bhp.com/


Because it finds the sources much quicker than I would have been able to on my own, and I can then synthesize them into data I know is correct, as correct as any human-generated data can be of course.

But what that because their search was so bad that it took you that long to find the sources?

No, it's usually because it finds sources that I would not have even thought to search for in the first place.

Agentic AI has its faults, but one thing I've found it to be very good at is surfacing the "unknown unknowns": things I didn't know I should have searched for but that are directly relevant to my problem.


Exactly.

Back when I worked at Google there was an internal page someone put up that denoted what they called "the YX problem": the observation that the XY problem, applied to a sufficiently great extent, creates an environment where more productivity is lost convincing one's interlocutor that X is in fact the correct problem to solve than would be lost by chasing X and having to later pivot to Y if that turned out to be wrong.

It's extraordinarily aggravating when it happens. I really wish it was something we talked about more.


People want the option.

There are many reasons one might prefer OrcaSlicer over Bambu Studio. One might be perfectly fine using Bambu's cloud services while preferring OrcaSlicer for different reasons; this is for those people.

Others might not want to use Bambu's cloud services at all; OrcaSlicer as it currently exists is fine for them.


this is it for me

i bought the dang thing, let me decide how I use it.


> i bought the dang thing, let me decide how I use it.

Amazing how controversial this statement is here in 2026.


there's not enough appeal with the investors and stock holders.

they're going to try to make everything you have a subscription, starting with the homes you might try to buy. they don't even live here, but there's no laws stopping them, because your representatives personally benefit from letting things go for certain corporations/people (the same thing after the Citizens United decision)


The "scheduled maintenance" thing is likely just because that's the easiest maintenance page to throw up site wide, or at least it was back when I was on the Canvas deploy rotation back at Instructure ~10 years ago.

That doesn't excuse any of their other messaging though.


Define "as they're supposed to be".

Back when I worked for Instructure ~10 years ago, Canvas was effectively a single, giant, monolithic multitenant app with one instance backed by several thousand app servers and ~100 separate Postgres database clusters that any app server could talk to.

Schools were grouped onto pools of app severs and Postgres database clusters more or less according to locality and cluster availability. I want to say a handful of the largest schools got their own clusters, but I'm not certain, and at any rate their clusters could certainly all talk to each other.

It was actually kind of neat from a technical perspective: any Rails model across the entire Canvas world could have a "foreign key" pointing to any other Rails model anywhere else. Among other things, this allowed for users who could administer multiple Canvas organizations, even if those organizations resided on different Postgres clusters. https://github.com/instructure/switchman is their gem that made that all work. (I put "foreign key" in quotes because the whole thing was implemented in software, not with actual database FKs, for obvious reasons.)

---

Of course, the massive downside to that sort of thing is that if you manage to pop one Canvas app server, you have the keys to the kingdom. I wonder if they'll sharpen the edges between clusters in response to this...

---

(Disclaimer: I left Instructure back in 2017; much could have changed since then, and my memory could be faulty about the specifics. Caveat emptor.)


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

Search: