Yeah but I mean some people fear that TI will eventually manage to permanently lock the Nspire, with no way to make Ndless work anymore on it, or locking down Ndless for 3 extra years like before, and some people probably don't find it worth it anymore to bother coding in ASM/C for the Nspire as a result, since eventually their audience would shrink as low as the TI-86. There's even a post from Chockosta where he stated he was considering quitting Nspire development because of TI's action. Also to run nSDL and bFLT you need Ndless, right? If Ndless was to be killed for good by TI, then we would never be able to use nSDL/bFLT again. THat said I still think people should not give up, though.

As for Spybot I agree more stability would be nice. Its current unreliability makes it hard to get notified of new posts and IRC is often cut off from the forums again. OmnomIRC helped a lot Omnimaga activity before.

As for age, I guess you have a point, since most people turned 18 last Summer or close, so much less time or risks of interest shifts, but there seemed to be less new guys joining.

Yeah. Also there's Lua, but many people find it too slow to perform any advanced stuff. As for OS updates, sadly the issue is that retail store calcs will eventually all come pre-installed with OS 3.2 and a lot of teachers force students to upgrade.

In the worst case scenario, I expect 90% of the Nspire scene to be european developers in a few years (since in Europe teachers do not have full control of what students do with their calc).

Anyway what I think too is that it would be nice if topics were created to discuss further ideas for Ndless dev in the future. Maybe not just plain publicly state what hacks to try for Ndless 3.2 in case TI watches us, but you get the idea (kinda like the UTI topic).

Yeah. Also there's Lua, but many people find it too slow to perform any advanced stuff. As for OS updates, sadly the issue is that retail store calcs will eventually all come pre-installed with OS 3.2 and a lot of teachers force students to upgrade.

I think you're mistaken. Or at least don't understand everything going on. (nothing bad intended towards you)
Of course C/Asm is faster. We know that, we get it.
But you can do great things with Lua. Just look at awesome stuff already out even before Physics is out and before the official SDK is out.
Can you imagine how even better Lua scripts are going to be when all that is released ?
Compared to what the Nspire always had (crappy Basic), Lua scripting is infinitely better.
Another thing to note : Everybody knows that Basic is slower than native. Look at popular z80 and 68k calcs. Count how many BASIC programs there are out there. Do you think they are all crappy because it is "too slow to perform any advanced stuff". No.
So, what we have right here: a "limited" basic, but making incredible things thanks to everybody in the community.
Now, Lua on the Nspire allows us to make 9001* better things that what z80 and 68k Basic could allow us to do.
So please, stop writing again and again that Lua is so slow we can't do a thing with it. (this is not necessarily to you but to everybody in general, I mean).
And also, while you may want to compare raw computation speed, you will compare things with criteria that won't be fair for both the compared languages. For example :
  You can't make a NES Emulator in Lua. You can in native.  Native Wins.
  You can't make a GBC Emulator in Lua. You can in native.  Native Wins.
  You can't process xxxx computations per second in Lua.   Native Wins.
  You can't access USB over Lua.  Native Wins.
Clearly, Native wins right ? Lua is crappy right ?

Now let's take this point of view :
  Nspire Lua is easy to code in. Start up TINCS and open the Lua SDK. It's a mess with Native.  Lua wins.
  Lua can access the math engine. (with CAS if device is CAS).  Native can't.   Lua wins.
  Lua can interact with the already existing variables and widgets.  Native can't.  Lua wins.
  Lua is supported by TI and whenever the SDK is out, so it will have an even bigger community.  Native isn't/won't (as much).  Lua wins.
Clearly, Lua wins right ? Native is crappy right ?


As you can see, you (or any other) can't just claim that "it's too slow". For many things, Lua's better than Native. And for a lot of things I'm pretty sure it will stay that way. Except if TI radically changes its ideas and publishes some Native Resources Toolkit or whatever, but I don't see that coming soon...

Also, some other things :
- I think the community needs to make some kind of all-in-one-included Native SDK, where you could just select the target device, and everything would be so you just have to code your thing, and it would compile with the latest ndless toolkit available (or the one you want if you want to override that), etc. so that people who aren't really geeky enough to setup properly their toolchain onto their system (or just dont want to mess with it too much, or for any other reason), could finally be able to program in C for their device ! If it was easy enough to code in Native (as much as in Lua with the SDK, for example), there would be a heck of a lot more people involved, and thus, the community would be way more active, including here at Omnimaga, but also at TI-Planet etc.

- While you can think 3.2 is blocking ndless (it will most probably do), there will probably be flaws like in every other OSes, so don't worry too much I guess

In the worst case scenario, I expect 90% of the Nspire scene to be european developers in a few years (since in Europe teachers do not have full control of what students do with their calc).

Maybe I haven't understood correctly, but how is that bad ?
I mean, 90% of the "underground" scene is European ?
on the Nspire, 3.2 does also mean Lua physics stuff, so even more content...
And that could be from anywhere in the world

You're too pessimistic here ;-)

Just wait & see !

Move on to what? Casio?

TI has again defeated Ndless

We have no proof that ExtendeD can't go through OS 3.2

If it was easy enough to code in Native (as much as in Lua with the SDK, for example), there would be a heck of a lot more people involved, and thus, the community would be way more active, including here at Omnimaga, but also at TI-Planet etc.

TI is boneheaded about limiting the functionality of their calculators (and screwing with basic user rights of doing whatever they see fit with the hardware they own), instead of taking advantage of the possibilities of native code, and their resulting attempts to "protect" themselves, is a very powerful deterrent for the open development communities. That's why even a much improved SDK would hardly help people getting involved...

You're too pessimistic here ;-)

Not so sure, because the fact is that hardly anybody gives a damn about the Nspire platform...
Did anybody do for the Nspire what was done for quite a number of closed platforms (starting with gaming consoles), i.e. port Linux mere weeks after the release of arbitrary code execution on the platform ? No, and more than two years later, we're not remotely close to that state.
Do we have a chain of ready to use exploits, and wait for TI to close the hole of the day to release a new version, by a dozen days (often two or three days) after the release ? Not at all.
Do we have a usable graphical library (a need which was identified from the beginning) ? Several weeks ago, the answer was "no".
Do we have a program loader with relocation support (another need identified a couple years ago) ? Again, the answer used to be "no" until very recently.
This list could go on. And yes, I'm criticizing myself (as being part of a community that does a relatively bad job, compared to a number of other communities throughout the history of computing), even if I tried to do something about the math stuff, the document system, the program loader, the graphical library, etc.

Why is it that hardly anybody cares about the Nspire platform ? I don't know, but it's a fact. Another fact is that TI is (relatively) safe is a consequence of the fact we (collectively) are not trying (yet), rather than being a consequence of the fact they're making a decent job protecting their platform...

Just wait & see !

We'll probably see, indeed, because there always are holes. But even more than Ndless, I can't wait to see TI's dangerous strategy backfiring
It's not like they weren't warned about the potential consequences of their incompetence. The gloves have long been off, and so far, the only thing that saved them from facing the consequences of the infuriating war they've been waging against users for five years, is that nobody got over their moral bounds. But sooner rather than later, as I predicted, people are going to become interested in destructive matters (the most damaging attack venues are public knowledge)... and TI will lose, just like Sony lost, to the resent and hatred they created (and also to the false promises incompetent people at TI made to incompetent people at standardizes test regulation authorities - trying to prevent native code is in no way a requirement for certification, it's only willful and lucrative collaboration with the authorities - en français, collaborationnisme). And yet, they were warned in advance, but willfully chose not to take that into account. Their loss.
OSLauncher was perfectly harmless (and yet, it freaked out TI and the woefully incompetent standardized test regulation authorities); '2012 stuff is unlikely to be as gentle as '2010 and '2011 stuff...


One thing is sure, Adriweb: you'll have to take sides at some point. Either TI, or the open development community - but not both, because TI's actions are making them exclusive.