![]() This could be my own misunderstanding or a failing of the guide. * Did I mention the dependencies? It seems like every CLI command requires dependencies to be installed. This isn't necessarily a bad thing, but I wonder if this would effect long-term flexibility. However, it seems like that in order to use them, you need to use a very specific set of libraries. What I mean by this is that the CLI tools, specifically `mix` seem awesome. * There seems to be a lot of lock-in if you want to use the CLI tools. This is rather nit-picky, but I write a lot of code, so ease of syntax is actually a very important consideration for me. I understand what it does, it's just difficult to type and I always felt like a simple `>` would make sense as well as be easier to type. That said, the one operator that always gets me is `|>`. * I've never been a fan of functional languages for one reason: Too many damn symbols in the syntax! It appears that Elixir definitely does a better job having an understandable syntax compared to say, Haskell. * Honestly, working with ecto outside of initial model creation looks kind of nasty. * I need to have a Db installed even though the application doesn't touch a the Db? Does that mean the Phoenix stores its configuration in a Db? I don't like that. * There are a lot of dependencies just to get a simple hello world app running. Though, there are some things that put me off a bit: I like how rigidly everything is organized. I decided to take a look at the official getting started guide. I do web application development for a living, so I'm interested in learning more about it. I've been hearing a lot of good things about Phoenix. There are some other cool things (like quick note sharing and dark mode) that make it a joy to use (but hey, I made the thing). Speed and minimalism are the main differentiators (whether it's creating a new note or trying to find an old one). I would rather have a small number of users that love it than try to appeal to a huge audience that's sort of indifferent.Ĥ. ![]() Even if no one else uses it, I still will. which I think makes sense., bu it's never going to be a general purpose notes app for everyone.ģ. The plan is to keep it simple so you can create/retrieve notes really quickly. My hypothesis was "NV plus web." I needed something I could use at home (on my Mac) and at work (on Windows). The creator of NV opened up an issue on GitHub ( ), which I am addressing.Ģ. It stuck and I haven't had time to think of a new one. The name was something I came up with quickly so I could focus more on making the product. Good questions! Answers below or read the note I wrote ( ):ġ. If this is just meant to be a cool demo of Vue.js (with an awesome homepage), well done, ignore my comments =) Even if they reach feature parity, their one differentiator is "well, it's real-time". Those products then go on to ignore half the reasons why the others have users. I'm not trying to be a downer here, but I feel like I see "X app but real-time" posted to HN on a weekly basis now, like it being real-time is going to be the differentiator that makes it wildly popular. Is the real-time feature the only way you plan to make this different/better than the others? How do you compete with the larger companies who offer these apps for free to their users? Google Keep, Apple Notes, etc.Ĥ. Was "Notational Velocity but real-time" your hypothesis of what would make this something people want to use/buy? If so, what about all the other very standard features that note-taking and thought storage apps have? Do you plan to hit baseline with those?ģ. If this is inspired by Notational Velocity, a very popular and real product, why is this also named Notational? I understand if you're doing a cool tech demo that it's not a big deal, but if you plan to charge money for this you probably shouldn't copy their name.Ģ. With that in mind, I have a few questions:ġ. This leads me to believe it's intended to be a real product. Is this meant to be a cool tech demo, or a real product? I noticed the author mentioned adding new features and a premium version in another comment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |