From what I read from you elsewhere in these comments, though, subscribing to an RSS feed in Prismatic does not (currently) mean you will see 100% of the content in them - correct?
... If you are indeed changing it to include 100% of the feeds of my choosing, that's great to hear.
What I ALWAYS want + 'a little extra I might like' is something I can appreciate.
Right on all counts. On the upside, we're smarter than an RSS reader for high-volume feeds currently, and sort things based on how much we think you'll like them (based on topics, social information, and more) rather than just by time. Support for the 100%-of-feed use case is in the works, stay tuned.
If by 'that feature' you mean the sort by perceived importance vs. time, I hope they make that possible to configure.
If you instead mean the suggestion of additional content into your feed - that's really the core point of Prismatic. I wouldn't expect to see that configurable / given an "off" switch ever. In fact, I'm pretty sure that's how they'll monetize the product - slipping in pay-for-placement content that's relevant to what you're reading.
If it can I could never find it. I tried the service out twice and both times found it to try and show me a lot of stuff I didn't want to see and never improved on that front.
I'm getting a 400 error when I try to complete the 'choose a username' screen.
No visible reaction to pushing the continue button at all, but the error shows up in chrome's console.
"Uncaught SyntaxError: Unexpected token O"
Chrome 25 on windows 7.
I just tried again from scratch, without going through the google oAuth page, and its worked this way. No idea what went wrong the first time around.
You can add both feeds and topics - it'sa bit of a whole new world :) give it a go and see how things work out for you. we are always actively listening on twitter and feedback@getprismatic.com
Awesome to hear feedback like this! We have so far to go with the product though. We can't wait to ship the next big redesign. What do you think we can do to make the experience better?
I'm not the OP but I have some stuff I want. I really like the service but don't use it that much because there isn't an Android app. Is that in the works?
As far as the website goes, the home page feels way to cluttered and it's not always clear what the elements do. For example, the purpose of the bar on the right isn't immediately obvious, and interaction with it isn't very intuitive - it looks like it scrolls vertically because of the cut off suggestion at the bottom but actually slides horizontally using buttons.
When it comes to discovering new topics I think a more interactive and transparent method than the suggestions box would be useful. I would love to have a graph/web of topics clustered around my interests that I could browse. I would also like to search for topics and see how they fit into the graph and related searches.
Don't worry about how anything compares to frameworks, because they don't matter anymore.
We think traditional frontend frameworks - whether of the rails/django variety or the backbone variety, are generally rubbish in a nearly infinite number of ways. It's a style of programming based on wrapping weak mutation oriented idioms behind monolithic APIs and design patterns. We think default functional style and fine grained composability is the future, and mutation + oo design patterns + frameworks is the past.
It may be the future for very skilled developers that have already familiarised themselves with frameworks and design patterns and are capable of moving past them. The majority of software developers benefit enormously from the conventions encouraged in a framework like Rails. If Clojure is going to be adopted widely (if that is a goal of the project at all), the community needs to work on better communicating best practices to make up for the lack of framework 'guidance'.
Eh, even the least charitable would have to admit that frameworks enforce style. On a large project, this matters hugely. I don't care how good your devs are they DO have different opinions re: style.
I disagree -- frameworks enforce structure (especially of callbacks), not code style.
Unity of code style is something you can solve with standards, style guides, pairing with new developers, and following conventions from surrounding code.
Clojure is nice because the community, while having different opinions about how often you should use X technique vs Y, generally has core sensibilities about what makes for good, simple code that composes well and doesn't tangle concerns. (This is largely due to the influence of Rich Hickey.) This (and not "perfectly uniform code style") makes for an effective large team.
Actually, we do our numerical work in clojure too and make heavy use of mutable java data structures - and it's a joy to program in Clojure for these tasks.
