I still dislike them for having blocked downgrading to older OSes and for keeping an anti-game stance during 4 years.

Also I believe the Nspire line is harder to use than other calcs and in some cases, people might be better off with a cheaper Prizm with the addition of eventual third-party math tools.

I don't think that opening nspires to Lua means that ti is now pro-game. They can still clamp down on games by various means with still another OS.

An On-Calc text Editor, capable of programming for Lua

Official TI support of C/Asm (Since they are more capable than Lua, and faster)

On-Calc GCC (It can handle it)

Are you kidding? GCC could run on an 89. It might take 2 or 3 minutes to compile a large prog, but it takes much longer to do a proper PC link. All you really need is a small file selection GUI.

All you really need is a small file selection GUI.

And, by the way, the CX has exactly the same CPU as the original.

There are ARM9 compilations of GCC. What I meant by the gui is that GCC is a command line program, but the nspire's command line is rather nonexistent

What if the test protection mechanisms were hard-coded into the hardware itself? So they couldn't be overridden? Then they can give programmers full access to the rest of the hardware without sacrificing the testing capability.

For that matter, how many of you actually have Nspires that you can use with this?

GCC is far, far too memory-hungry to run on a 89. And even on a CX, it couldn't compile complex code: when compiling some C++, I've already seen GCC eat up 500 MB of RAM on my x86 / x86_64 computers.

ggc-min-expand
GCC uses a garbage collector to manage its own memory allocation. This parameter specifies the minimum percentage by which the garbage collector's heap should be allowed to expand between collections. Tuning this may improve compilation speed; it has no effect on code generation.

The default is 30% + 70% * (RAM/1GB) with an upper bound of 100% when RAM >= 1GB. If getrlimit is available, the notion of "RAM" is the smallest of actual RAM, RLIMIT_RSS, RLIMIT_DATA and RLIMIT_AS. If GCC is not able to calculate RAM on a particular platform, the lower bound of 30% is used. Setting this parameter and ggc-min-heapsize to zero causes a full collection to occur at every opportunity. This is extremely slow, but can be useful for debugging.
ggc-min-heapsize
Minimum size of the garbage collector's heap before it begins bothering to collect garbage. The first collection occurs after the heap expands by ggc-min-expand% beyond ggc-min-heapsize. Again, tuning this may improve compilation speed, and has no effect on code generation.

The default is RAM/8, with a lower bound of 4096 (four megabytes) and an upper bound of 131072 (128 megabytes). If getrlimit is available, the notion of "RAM" is the smallest of actual RAM, RLIMIT_RSS, RLIMIT_DATA and RLIMIT_AS. If GCC is not able to calculate RAM on a particular platform, the lower bound is used. Setting this parameter very large effectively disables garbage collection. Setting this parameter and ggc-min-expand to zero causes a full collection to occur at every opportunity.

The thing is, before we even talk about how "possible" it is to make GCC run on a calculator, we should discuss how to actually ALLOW it to run on a calculator. You can't shoot the leopard without bullets and a gun.