Thanks for the clarifications and answers! Interested to see what Emacs 
integration looks like. I'm surprised most developers want web interfaces 
for this stuff but can't argue with the data if it means more licenses sold 
for you. 

On Monday, May 8, 2017 at 1:10:37 PM UTC-4, Bill Piel wrote:
>
> Thanks for the questions and feedback, Adrian.
>
> > Why is the Pro version acceptable for production use and the free 
> version is not? 
>
> I thought I addressed that well in the video, but maybe not. And I didn't 
> do much to address that in the text. The answer is that sayid stores all 
> the data that it captures in memory. It would be much too easy to take down 
> a production server by capturing too much. Sayid Pro immediately exports 
> everything it captures to a db, minimizing impact on a server. I hope that 
> makes sense.
>
> > Why then is a web interface for this necessary or even desirable?
>
> My focus with sayid has been on the emacs integration, because that's what 
> I use. For Sayid Pro, I wanted to build what the community wanted. I 
> conducted a survey and a web interface was *far* more requested than 
> anything else. If the market wants integrations with IDEs/editors, or 
> possibly other production monitoring services, I will build that. But for 
> the prototype, I wanted to show what I believed would be generally most 
> appealing.
>
> Additionally, you describe cider and cursive as being the most mature 
> *development* environments. Agreed. They are excellent. But, I wouldn't 
> describe sayid pro as a development tool.
>
> I hope that helps.
>
> thanks
>
>
>
>
>
>
> On Monday, May 8, 2017 at 12:54:23 PM UTC-4, adrian...@mail.yu.edu wrote:
>>
>> Why is the Pro version acceptable for production use and the free version 
>> is not? Is it just the UI/UX improvements? I looked for this in the 
>> Kickstarter since I assumed this would be a major selling point, but could 
>> not find the answer. Apologies if I missed something.  
>>
>> I guess I also have unrelated concerns. 
>>
>> TRACE is a facility which has been part of Lisp systems since time 
>> immemorial. Visualizing traces is common in the Common Lisp world. Like 
>> other Lisp tooling, progress on porting equivalent functionality to Clojure 
>> has been slow, but has progressed significantly. At this point CIDER and 
>> Cursive have progressed to the most mature development environments 
>> available for Clojure programming. Why then is a web interface for this 
>> necessary or even desirable? If you have a better solution than what is 
>> provided by the built in functionality of your preferred development 
>> environment, you extend it. This means plugins in the IDE world, Elisp 
>> packages in the Emacs world, etc. Why not take that approach, which will 
>> lead to a product that integrates well with a developers existing tooling. 
>>
>> On Monday, May 8, 2017 at 10:35:00 AM UTC-4, Bill Piel wrote:
>>>
>>> Today I launched a kickstarter for Sayid Pro.
>>>
>>>
>>> https://www.kickstarter.com/projects/1269641244/sayid-pro-transparency-for-clojure-production-envi
>>>
>>> Maybe you've heard of Sayid, a clojure debugger and profiler, that I wrote 
>>> and then presented at Conj 2016. After my talk, a lot of people asked 
>>> me if sayid could be used in a production environment. I strongly 
>>> discouraged that. A month later, I started working on a new tool that 
>>> brings the same transparency as Sayid, but is designed for use in a 
>>> production environment. Sayid Pro nows exists as a very rough, but 
>>> promising, prototype.
>>>
>>> If you would like to help me build a tool that will give you insight into 
>>> your production servers -- far beyond what logs or metrics could ever 
>>> deliver -- please consider supporting this kickstarter.
>>>
>>> thanks,
>>> Bill
>>>
>>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to