Spark vs CodeBehind
When comparing Spark vs CodeBehind, the Slant community recommends CodeBehind for most people. In the question“What are the best backend web frameworks?” CodeBehind is ranked 36th while Spark is ranked 41st. The most important reason people chose CodeBehind is:
CodeBehind is a modern framework with revolutionary ideas.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Custom quick swipe features
Pro Free
Pro Robust customization options
Pro Syncs across devices
Pro Unified inbox
Pro Free snooze options
Pro Modern
CodeBehind is a modern framework with revolutionary ideas.
Pro Code-Behind
Code-Behind pattern will be fully respected.
Pro Under .NET Core
Your project will still be under ASP.NET Core and you will benefit from all the benefits of .NET Core.
Pro Get output
You can call the output of the aspx page in another aspx page and modify its output.
Pro Modular
It is modular. Just copy the new project files, including dll and aspx, into the current active project.
Pro Simple
Developing with CodeBehind is very simple. You can use mvc pattern or model-view or controller-view or only view.
Pro Fast
The CodeBehind framework is faster than the default structure of cshtml pages in ASP.NET Core.
Cons
Con Horrible privacy policy
- Sends statistical data to several services known for bad privacy policies (Google, Facebook), also there's no way to opt out.
- Automatically creates an acount with the first address entered and subscribes you to their newsletter.
- Stores credentials for your email accounts on their servers.
- Stores your emails on their servers to push them to your devices.
- Server infrastructure seems to be located in the US.
Con Doesn't support many services
Many services such as Spam filters, Pocket, and other apps are not supported.
Con Doesn't show the counts of emails next to the folders
- On the Mac platform will show +999 for the folder that contains more than 1000 emails.
- On the iPhone, the platform will not show the counts next to the folder unless they are new emails.