We've been successfully using locust for automated performance and load tests for a couple of years now. Locust is very flexible, the community is great and python-based test implementations are big win for engaging our quality engineers in test design and implementation.
Since our platform (Appian[0]) has a pretty heavy/complex client, we built a thin abstraction library [1] to empower both our quality engineers as well as some of our more advanced customers to write simple automated performance tests.
So if I understand you correctly, you deem the price for the annual license too high? Could you elaborate on what you mean by 99% open source and how that relates to your perception of the price?
Because is mainly using Jupyter Notebook, Python and Pandas.
In this times is normal for companies to create their own products using open source products, but to some people is not very good seen.
In my case I think is not worth it a tool that only works in some specific environment, that doesn't have many functionalities, and it costs more than all the products of Jetbrains. I don't like either that is a tool built on top of open sources projects trying to charge a big amount while it does not have almost any functionality.
> Because is mainly using Jupyter Notebook, Python and Pandas.
I really don't think that is correct. It integrates into those / builds on them, but those projects absolutely do not have the features that I can see playing around with this product.
Hmm, would putting labels work? That could include the chapter number, section number, and keywords. I usually go with topic and include the page number.
This is a great question though. What features could one add to a hypothetical PDF viewer that could help us? Sometimes I feel like having a separate text file is not sufficient, or not convenient enough. Most of the books I read do have a summary per section, perhaps I could take a screenshot of them. Additionally I could use the PDF viewer to highlight sentences, and add a feature to this PDF viewer that would allow me to cycle through them. Thoughts and/or ideas?
I and many others spent basically all day there yesterday. It's fun to look through all of these manuals. It takes a lot of concentration picking out the unique copies and leaving the many copies behind. Especially HP.. arg so, so many revisions of the same manual.
The kindness requirement is awesome and refreshing. I was shocked just how much vitriol gets spewed in an average workplace, directed at customers, fellow employees, inanimate objects. I gravitate towards the people I work with that aren't like that, so specifying 'kindness' right up front is great.
Thanks for your concern, but we don't see a point in just removing it in git because it doesn't really help. the key is in several branches, in our iso file, every rockstor rpm in our yum repo and not to mention lot of users who have downloaded rockstor.
We changed the key in our live demo, but for our users we'll roll out the fix in the next update. As part of that fix, we'll also remove the key file from git.
I think that's a reasonable plan. Hope I am not missing something.
I keep wondering whether they still have something up their sleeve, but judging by them dropping the price, its not the case. This is the pinnacle of Mark Shuttleworth's "convergence" dream, I wonder whether he will carry the rest of this campaign if it looks like it will not get funded in the end? Also if it does fail, it is going to look mighty bad for Canonical.
> Also if it does fail, it is going to look mighty bad for Canonical.
I also thought about this, but I'm not sure that's the case. At the very least, they managed to collect close to $10 million in a a two week period, without much of an advertising budget and only some vague on-paper specs and a few renders.
I think that gives them some leverage when negotiating with manufacturers to show that there is at least some demand for high-priced smartphones running their software stack.
Why is it going to look mighty bad for Canonical if it fails? For one, this was a self-claimed experiment. And two, these phones are priced the same as a decent laptop. If anything it proves people aren't willing to shell out $800 for a phone 9 months from now. However, I think it also shows that people do in fact want an Ubuntu phone.
Since our platform (Appian[0]) has a pretty heavy/complex client, we built a thin abstraction library [1] to empower both our quality engineers as well as some of our more advanced customers to write simple automated performance tests.
[0] https://www.appian.com [1] https://pypi.org/project/appian-locust