The TI-Nspire CX CAS II, Casio ClassPad fx-CP400, and HP Prime G2 are the main CAS-enabled calculators available these days. The TI-89 Titanium and HP-50G are also options, albeit older models (with the HP-50G being discontinued).
Basically any scientific calculator will do proper infix with correct operator precedence, no need for a graphing one (or even one that displays the entered formula, the original Casio fx-82 for example only shows the number currently being entered, yet still does proper infix with correct operator precedence).
This is something the CHERI architecture[0] (an extension to ARM and RISC-V that implements a capability memory model) can allow this performantly with compiled code (without needing to context switch). This PhD dissertation from Cambridge[1] implements this for C/C++ under CheriBSD (their fork of FreeBSD that supports CHERI).
illumos on RISC-V with CHERI would be the ultimate. There is another variant of RISC-V that is spectre immune. I have also recently heard of approaches at compile-time, such as RESPECTRE, that remove the spectre problem.
Yeah this looks to be the case. All of this change was prompted by the fact that malicious software was triggering prints over the network. So now they have locked it down so the printer can verify prints came from the actual account owner.
Printing directly from SD cards via the little touch screen is unchanged since networked computers can’t do that.
> So now they have locked it down so the printer can verify prints came from the actual account owner.
This is inaccurate, the printer already required authentication using an 8 digit code. What they're trying to do now is verify that the print has been started using official Bambu software, i.e. software-only DRM.
I really really hope people saying this is a nothingburger is actually right, because I do have a P1S, use orcaslicer, and would like it to continue to work. Hoping this is just a miscommunication.
Bambu Connect is explicitly about allowing you to continue to use your favorite slicer. They make it less convenient (instead of pressing print you now have to save, load the file in Bambu Connect and then press print), but they don't prevent you from doing it.
Once the update actually rolls out to the P1S obviously. Which may not even happen with the current backlash
> Bambu Connect is explicitly about allowing you to continue to use your favorite slicer.
For now. They're putting themselves in the middleman position where they get the final say over what we can print on the printers that we supposedly "own".
It's naive to think that they won't try to extract revenue from that privileged position, they wouldn't have spent R&D resources on it otherwise.
> Parallels notes that these operating systems currently run "really slow" due to the overhead required for translation. Windows takes between two and seven minutes to boot, depending on the speed of your Mac, and "the responsiveness of the operating system is low." Rather than attempting to multi-task, Parallels says you should close the app you're using before trying to open another one.
I tried to run x86 Windows using UTM a while back (I was trying to test something that was x86-only and used a kernel driver, so couldn't run under ARM Windows). I had to give up on it because it was taking too long to boot (i.e. way longer than 7 minutes). So this sounds like an improvement.
On the other hand, we've had success using UTM for students with Apple Silicon Macs to run our x86 Linux VM that we use in our 2nd year University operating systems course. It's terminal-only (no desktop environment), but we do use VS Code's Remote SSH with it (which runs the VS Code backend in it).
RUCs existed well before EVs were a thing. They apply to diesel vehicles (as unlike petrol, diesel doesn't have a road tax on it). EVs were temporarily exempted from RUCs (partly as an incentive, and partly because RUCs on light vehicles are a lot higher than what an equivalent fuel-efficient vehicle will pay in road tax through petrol usage). The current government removed this exemption (without adjusting the RUC rates to a sensible level for EVs), causing BEVs to pay significantly more road tax than an equivalent fuel-efficient non-EV does and removing their advantage of lower running costs (which has massively hurt the EV market). They "justified" this with their vague plans to move petrol vehicles to RUCs at some point in the future.
Yep. Good chance it's clogged up with earwax or something. I have similar issues with mine (a high-pitched whine on when in any of the ANC modes on my current AirPods Pro 2's right AirPod, and a lower-pitched rumbling in my old AirPods Pro 1's as well).
Well that explains the faint noise I've been hearing at night lately just after putting my AirPods away.
Speaking of the sounds you're meant to hear, I'm familiar with the low battery ones (both the AirPods themselves and the case if you put the AirPods in it when the case is low on charge) as well as the chime the case makes when it's put on charge. But every so often the case plays one when I open the case. Any ideas what that one's meant to be?
reply