News for hackers. Stuff that matters.
Re:The cost of forsaking C by mikejmoffitt on Wednesday October 05, 2016 @08:08AM (#12643119)
Surely Basic is not responsible for the Commodore being responsive. Java was a total dog on phones for a long time, too.
Re:The cost of forsaking C by Avshalom on Wednesday October 05, 2016 @08:23AM (#12643163)
Well C wasn't responsible for the Commodore either. And whether Java was a dog or not, thats what people went with, from your SIM card to JavaME snake games to Dalvik/ART. People looked at these resource constrained environments and went "yeah lets use Java".

ETA: it's probably worth put scare quotes around "resource constrained" when talking about Android and IOS but phones were dreta's example.

Re:The cost of forsaking C by marrs on Wednesday October 05, 2016 @10:04AM (#12643866)
and promptly went out of business when the iPhone showed up
Re:The cost of forsaking C by Avshalom on Wednesday October 05, 2016 @10:49AM (#12644251)
a phone that launched full of ObjC and Javascript with a SIM card running Java...
Re:The cost of forsaking C by marrs on Tuesday October 11, 2016 @06:16AM (#12682932)
ObjC is a native language and a direct descendent of C, and powered the phone's built-in apps. JS was provided for 3rd party developers, who incidentally rejected it. I wasn't aware of the SIM card running Java. I guess Java was good enough for that job since I never noticed any performance issues with the iPhone, unlike my Palm Pre which was plagued with them, and had a terrible battery life.
Re:The cost of forsaking C by e12e on Wednesday October 05, 2016 @11:49AM (#12644879)
I still remember the load times for Last Ninja - I'd prefer an ssd any day.