i wish to make a toy version of that on an esp32, with a RPL system on top (of course)
NumWorks: An open-source graphing calculator (with Python and Rust support)
11–20 of 41 posts
Re: NumWorks: An open-source graphing calculator (with Python and Rust support)
#12I think the creators do legitimately want to build a truly open source calculator. The problem is getting the calculator registered for exams - the examiners naturally want to make sure that the calculator isn't being used for cheating. And any method to replace the firmware, add custom applications, etc. can and should be viewed as a way to cheat on exams.
Personally, I'm hopefully never going to take another standardized exam in my life - I'd like to see a graphing calculator that doesn't attempt to get certified for exams or school use, since this seems to be such a significant hurdle. But I know I'm in the 0.1% of graphing calculator users who don't care about AP/IB/the SAT/whatever.
Re: NumWorks: An open-source graphing calculator (with Python and Rust support)
#13I think the creators do legitimately want to build a truly open source calculator. The problem is getting the calculator registered for exams - the examiners naturally want to make sure that the calculator isn't being used for cheating. And any method to replace the firmware, add custom applications, etc. can and should be viewed as a way to cheat on exams. Personally, I'm hopefully never going to take another standa…
> I think the creators do legitimately want to build a truly open source calculator.
Somewhat like Google legitimately wants to "do no evil"?
Sometimes it is said that deeds, not words is what matters. But in this case even the words are missing, so I don't really get what you're trying to say.
Re: NumWorks: An open-source graphing calculator (with Python and Rust support)
#14These calculators are very popular in France.
I know of a lot of teachers who use them for teaching.
Re: NumWorks: An open-source graphing calculator (with Python and Rust support)
#15It doesn't support Rust at all. There's just a GitHub repository with a toy example in Rust, that uses nothing but direct unsafe calls to five C functions. But Python, yeah, definitely. That's the beauty of this calculator.
> But Python, yeah, definitely.
Well, it's a forked MicroPython. It doesn't actually support Python, just something similar to Python.
Re: NumWorks: An open-source graphing calculator (with Python and Rust support)
#16I have one. It's great. It's quite an amazing bit of tech.
I wish they would split out the market, though, one for the educational market for tests and the like, and one for the professionals with wireless and more open capabilities.
I would like for instance to ship images of graphs to use in a web page. Or to use it as a keyboard to type equations and calculations into documents. Or to have it connect to PyPI say to grab programs that can calculate complex equations.... etc.
Re: NumWorks: An open-source graphing calculator (with Python and Rust support)
#17I think the creators do legitimately want to build a truly open source calculator. The problem is getting the calculator registered for exams - the examiners naturally want to make sure that the calculator isn't being used for cheating. And any method to replace the firmware, add custom applications, etc. can and should be viewed as a way to cheat on exams. Personally, I'm hopefully never going to take another standa…
> I think the creators do legitimately want to build a truly open source calculator.
Then making one that wasn't certified for exams is exactly what they should have done. As it stands, they're just another TI.
Re: NumWorks: An open-source graphing calculator (with Python and Rust support)
#18I have one. It's great. It's quite an amazing bit of tech. I wish they would split out the market, though, one for the educational market for tests and the like, and one for the professionals with wireless and more open capabilities. I would like for instance to ship images of graphs to use in a web page. Or to use it as a keyboard to type equations and calculations into documents. Or to have it connect to PyPI say t…
I have long believed that there is a huge market for some sort of rudimentary TI-style CAS system, with a caveat. Something that works on embedded arm devices, but is screen aware enough to be ported to a desktop.
If you include bluetooth in your calculator hardware, you now have an excellent input device for an onscreen CAS - or maybe something more like a screencast.
Extend this concept far enough, and we're talking about something like OP is describing - easy to sync and share small programs and tools. Further integration with excel and other tabulated data sources, and you've got a real killer on your hands.
Re: NumWorks: An open-source graphing calculator (with Python and Rust support)
#19There’s a forked version of the OS called Omega that’s really nice: https://github.com/Omega-Numworks/Omega And apparently a jailbreak for Epsilon 16+: https://phi.getomega.dev/
and a symbolic algebra system for Omega,
https://www-fourier.univ-grenoble-alpes.fr/~parisse/numworks...
(it's a port/adaptation of https://en.wikipedia.org/wiki/Xcas )
Re: NumWorks: An open-source graphing calculator (with Python and Rust support)
#20I think the creators do legitimately want to build a truly open source calculator. The problem is getting the calculator registered for exams - the examiners naturally want to make sure that the calculator isn't being used for cheating. And any method to replace the firmware, add custom applications, etc. can and should be viewed as a way to cheat on exams. Personally, I'm hopefully never going to take another standa…
> I think the creators do legitimately want to build a truly open source calculator. Somewhat like Google legitimately wants to "do no evil"? Sometimes it is said that deeds, not words is what matters. But in this case even the words are missing, so I don't really get what you're trying to say.
My point is that ultimately it was more important for them to make a calculator that students could actually use - which is a perfectly reasonable goal. And it's a shame that that's fundamentally incompatible with FOSS.