Comment by KronisLV
2 years ago
> Symbian was the biggest problem with Nokia phones.
I actually miss it, those were simpler times where your phone didn't spam you with ads or notifications or didn't get outdated every 2 years. No constant data collection or surveillance to the scales we deal with now.
More so, I actually miss the feeling of how new everything was, in the sense that is you wanted to play some games you'd sometimes scour WAP sites for the game files (or pay exorbitant fees through magazines).
There was a certain charm to games back then, too, seeing what people could knock together with Java on such a limited platform. Games like Gravity Defied, Galaxy on Fire or Gish, or even Doom RPG.
I'm kind of nostalgic, admittedly, maybe for a time when not everything was so well optimized towards monetization. And before Wirth's law became so present on our devices.
The problem with Symbian was not the usability but the developer experience.
SDK available only for Windows and really awkward to install and use? Check. Pre-11 C++ but without exceptions and something called cleanup stack and ELeave macro instead? Check. Ok, a whole periodic table of string classes instead of std::string (which would still have been terrible because it was before C++11)? Check. GUI API that was designed for a Psion handheld (Uikon) and implementation for Psions (Eikon) and Series 60 UI implementation (Avkon) piled on top of that? Check. App architecture that doesn't really have a concept of standalone app but works on the idea that apps are views and controllers that handle files? Check. What about making every single phone model slightly different so that apps are not portable between Symbian phones by default but you have to actually test and port with every model? Check. And there was a lot more at deeper technical level that I never had to reach.
I understand that the developer experience was better for the last Symbian versions but at that point it was already late, iOS and Android were taking over and Symbian had a reputation to fix.
My definitive memory of Symbian development having a lunch at a Nokia cafeteria, a week after starting the job and all the dreams about having a computer in your pocket that could run anything as long at it didn't need huge amounts of CPU power, memory or screen area crushed, and complaining with a friend who was in similar situation. An older engineer had heard us, told us that we don't know anything about how bad S60 is and continued with a hour-long rant that as far as I know was all pure facts.
All true, and then there was also the schizophrenic S40 or S60 development too.
I was told by someone who had developed for both that S40 was much better for developers. Of course it was completely closed ecosystem except for J2ME apps so it didn't have much of future in competition with low end Android. I'd really like to know what Meltemi was like.
And a whole bunch of phoned under that s30
That you couldn't develop for at all.
All of that is true, and that's why Nokia acquired Trolltech: Qt solved all those problems on Symbian, and provided an easy, mostly OS-independent, way to rebuild the apps for Maemo/MeeGo.
I must live in simpler times then, with an iPhone from 2017 that has notifications set where I want them to be.
I do have a newer one, that's because the camera is something I care about, not because an X isn't fast enough or whatever, it remains a capable phone.
I get nostalgic for the HipTop, personally. Probably because I never had one, by the time I was done with flip phones the slab-o-glass was the obvious winner. Seriously cool little gizmos though, I don't think a better typing experience has been made for a pocketable jeejah to this day.