They didn't say that HN is turning into Reddit, they said that the conversation quality has gone to shit.
I don't agree with that statement universally, but I have to say I do when it comes to this article. I came here hoping for substantive discussion from those who'd had a chance to try it out; instead what I got was a seemingly endless stream of venting. There's a place for venting - and plenty to vent about with the state of AI nowadays - but to borrow from the HN guidelines you linked, it does very little to gratify my personal intellectual curiosity.
> it will also make it more difficult to identify who to invite to join the priesthood
The point that this announcement is trying to make is, of course, that AI has already made that particular signal approximately worthless for that purpose.
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.
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.
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.
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.
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.
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.
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.
In the 99% of cases where this status page is used, it is in fact the truth: we'd throw it up when we had e.g. data migrations to do as part of a rollout that wouldn't allow for our normal zero-downtime deploys.
So no, lies are not always quicker than the truth.
There's plenty to criticize Instructure about; let's not go reaching for straw men in the process.
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.