Basically my story is that I've decided to dedicate my life to developing a casual text editor and then branch it towards a different niche such as novel writing/outlining/to-do lists.
Despite my lack of coding knowledge, I get nightmares when I read posts like this:
nvALT’s fast note creation and retrieval got me hooked years ago and it didn’t wear off. >The application didn’t slow down even a bit when my archive grew to 3000 notes. I know >that ResophNotes coughed heavily at 1000 notes when I tried it.
A bit of context for those who don't know the app. nvALT is an alternative to Notational Velocity which is a Markdown outliner on a Mac as far as I can tell. Resophnotes is a windows program that just syncs the notes.
Fear #1: How do I get the intuition to know that I'm not headed (learning-wise) towards a software design that would choke. It's like that question about scale for websites only I fear it's extra hard especially if I someday decide to move onto desktop version of a web application.
I know there's got to be a coding specific question to this but looking at the state of open source software, I just don't see how baby stepping into a coding language would get me to figure this out by stumbling into it. After all, most open source software on text inputs are either basic or memory hogging and there's been more innovation done in text editors like WriteMonkey and Sublime Text but equally these software aren't focused on casual usage.
Fear #2: The Mac/Apple effect
I just don't get how there are more casual to-do and note software for the Mac and IOS than there is for Windows.
I primarily use Windows so there's that fear that I might somehow end up with an end program design that's limited like the Windows version of Scrivener instead of something full like the Mac edition
Fear #3: Feature un-creep
The thing with a casual audience is it's tricky to pursue a feature. For example: Some like markdown, others don't. Then there are innovations now focusing on variants of the same feature.
My worry is that I don't know how to research the future of text and I'm worried that I just don't know how to figure the coding paths to get to those features.
There's only 1 Outliner 4d and I don't know it's development history.
There's only 1 Scrivener and I don't know it's development history.
There's only 1 Workflowy and I don't know it's development history.
The conscious part of my brain says I shouldn't ask until I get to know how to code but the concept part of my brain screams:
If these were answers I would eventually learn as I dig deep into coding then why aren't there copycat features of these programs considering the bulk of programmers out there?!