Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am preparing to do some open-source development that I have been thinking about for some time. It will ultimately be a cloud-based web service that interrogates other web services. As one of the joys of this work, I can call the shots and return to my 90s-era Smalltalk roots. I've settled on Pharo and (at least initially) Seaside. But it has been almost 15 years since my last real Smalltalk work. So I am unfamiliar with the current ecosystem. Which versions of Pharo and Seaside are stable enough for real work? And where and what else do you suggest a returning Smalltalker explore before beginning? Thanks!
Well, the stable version is Pharo 2.0 and Seaside 3.0.9.
(Both pharo 3 and seaside 3.1 are already a lot better, but since they are development versions, I wouldn't recommend them for production yet).
You will probably need Zinc to interrogate web services: https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild/artifact/Zinc/Zinc.pier.html
I can only encourage you to join the Pharo users mailing list and IRC channel.
You may also want to have a look at the books: http://www.pharo-project.org/documentation/tutorials-books
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I have experience with Sequelize and TypeORM. LoopBack looks like a good alternative, so I tested it. But it looks like LoopBack 4 is not a finished product; it barely has the needed features for a production application.
My question is: why the LoopBack team decided to publish an unfinished product?
there are a lot of companies and products on live using Loopback4.
Which features you missed from the new version?
I mean, the product is free, open source and built off of previously released, finished products. Releasing it allows them to both test functionality and be provided with feedback and aid in building the actual application. Lots of products are released before they are finished for these important reasons. If you read the documentation, it is a community built product.
Most frameworks are constantly being updated to add functionality, so 'finished' is not really a word that can be thrown around for a framework
While it is not finished, to say it barely has the needs to support a production application is very dependent on the type of application being built.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Aspnet vnext is still in beta version, and we are about to start a new application, and we considering to using aspnet vnext, i would like to know if it is a good a idea, someone is already running application in production with vnext?
Depends on whether you can wear the risk of implementing a project on an unfinished framework. Items that affect this risk include;
Expected size of your application
Other libraries you intend to use
Platform you intend to target
Whether you can afford the learning curve (there are changes)
Whether you are happy to spend time upgrading when its finally released
Whether you want to deal with implementing workarounds when you find features that are not working as expected.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I'm having a hard time understanding the big picture of GemStone for Smalltalk. I am aware of GLASS as an application server using Linux, Seaside and Apache. But I want to know if it is an usable environment for non-Seaside applications.
I'm also having trouble to finding some basic questions:
It is not clear to me if GLASS or GemStone/S is independent of the VM used. For example if I'm using a VM which supports black threads, does that mean that the GemStone/S will work transparently?
For what I've seen also it is not useful for 3D applications. For example, if my application developed in Pharo or VisualWorks uses OpenGL, may I consider GemStone/S for scaling up?
I've read that you may have objects in VisualWorks and objects in GemStone/S, but this confuses me a lot. How do I know if the object I've just created it is already persisted or in "client" side? In which case I need GemBuilder?
To get an understanding of the big picture of Gemstone/S, you can read Gemstone 101.
Many of your questions should be answered and some of them are also not applicable. For example, Gemstone/S is a complete Smalltalk implementation with its own VM. It also does not have a visual interface like Pharo, Squeak or Visualworks.
Suggestion: You need to split the question into several ones.
For example:
Is GLASS or GemStone/S independent of the VM used?
No, as far as I understand the question. GemStone needs its own VM. You cannot run GemStone on a VM of another Smalltalk.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I know what Mono is but I don't understand why it exists. Why do Novell sponsor the project? I ask the question because I would like to use Mono but I have concerns over its future/commitment. If I better understood why the projects exists I'd feel better about using/recommending it.
How else would any .NET code run on Unix/Linux/iOs?
It exists because Miguel De Icaza saw .NET, liked it and wanted to have it available on Linux. Knowing that Microsoft will probably not port the platform, he decided to do it himself.
Since the code is open source, it is not going away anywhere.
I don't have any inside dope, but I'm not aware of a story other than an interested party that knew Microsoft was unlikely to port .NET to *nix platforms took on the task. It started as open source and picked up Novell sponsorship after it achieved some measure of success.
I don't believe a "better" story would help you feel more comfortable about recommending it. No one knows the future, and Novell's sponsorship isn't a guarantee of success.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am looking to get a comparison between stress testing tools that are available today. The options put forward to us are either VSTS or Loadrunner.
As of now, the inclination is towards Loadrunner, but we are looking to see if there is any better option today.
Depends on what you're testing. Static HTTP or simple JSP pages, use something free like jmeter. If you're testing ASP.net, silverlight or other MS technology stack apps, then VSTS is your best bet. For almost anything else LR works well, including newer Rich Internet Web 2.0 type pages including AJAX and Flex.
Loadrunner licenses are prohibitively expensive, if you're looking at a one off test, it isn't worth acquiring a license.
For .NET Apps you can rely on VSTS. They help you simulate
Web Services Performance Testing
Coded UI for functional testing
Xpath Testing
patterns & practices: Performance Testing Guidance
http://perftesting.codeplex.com/wikipage?title=How%20To%3A%20Use%20Data%20Binding%20in%20Load%20Tests%20in%20Microsoft%20Visual%20Studio%20Team%20System&ProjectName=perftesting