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 4 years ago.
Improve this question
There is a DataTables CPAN module. It is for datatables version 1.6.
In the meantime, there is datatables 1.10, with a different interface. A lot of things changed, e.g. the option names.
I wonder: how could the module be extended to cover the old stuff as well as the new datatables 1.10 interface?
Is there a common name for this issue?
Is there a best practice for it?
Is there a good reference module I could have a look at? I assume that others did face the challenge as well.
From my own author's point of view, best practice is to
keep latest master with latest API.
keep minor version of module with major version of API.
recommend module users to
3.1. upgrade API together with module, or
3.2. keep its module minor version untouched with version requirement (I did with cpanfile or cartonfile).
May You need more concrete answer?
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
If I use cats in my scala project, would it make migrating to dotty easier or difficult?
I'm not too sure of the ramifications of using a library like this and how hard it will be to eventually migrate over to dotty.
Using any library at all will force you to wait until it is released for Dotty.
For many libraries it will be a smooth migration if they don't use type system intensively, some will have to make some adjustments to provide support for new types, and all macros will need a total rewrite.
AFAIR Cats are making preparations for Dotty (you can see that they even have tests for it). But there is also the rest of TL ecosystem and each part of it will have to prepare for migration individually (while depending on its upstreams).
Personally, I wouldn't expect to migrate to Dotty in production for the first half a year. I would give some time to library author to migrate and test their changes. For now some attempts are being made, but since, not everything is set in stone yet, some libraries prefer to wait till right-before-the-release before they start migration.
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 4 years ago.
Improve this question
Our current Development and Production systems are PHP v5.3.10/Ubuntu 12.04 environment. We Our new environment will be PHP Version 7.0.30/Ubuntu 16.04.
Is there a way to analyze our current PHP5.3 code and determine the scope of how much work would be needed once we port current code into our new PHP7.0 environment?
This will help give us a feel for how much work will be required to migrate from PHP5.3 to PHP7.0.
The performance is the big plus in PHP7, but the effort to migrate to it depends from your time/money and the traffic in the website, if it is heavy you should consider the migration as a real option.
For security reasons, maintenance, lots of important deprecated function, and the new cloud hosting services, I recommend to not use PHP5.3. Migrate to PHP5.6, can be a sooner solution for future problems. In the last days I have been experimenting hosting problems with mysql_connect(This extension was deprecated in PHP 5.5.0) function used in PHP5.3, and this is just an example
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 4 years ago.
Improve this question
I want to go with Xamarin.Forms project. Now, I am bit confuse for consuming Rest API for this project. Performance matters.
There are many available but can any body please suggest me which should be best for Xamarin.Forms(.Net Standard)?
Microsoft Http Libraries or third party libraries like Refit, RESTSharp, PortableRest, etc.
Please suggest
All of these options are viable. I think the performance differences between these libraries will be marginal. So, it mostly comes down to what you feel comfortable with.
I like to use Refit because it will take a lot of redundant code out of your hands and you just have to focus on the contract. All the code for the actual calls is generated at compile-time (and thus won't impact your performance at runtime).
Also have a look at how well the library is maintained and if it's active. If you choose one that is already inactive for a while, chances are that you will start relying on older software versions which might not be what you want.
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
On the Migration guide from Akka 2.2.x to 2.3 I noticed the following brief mention:
Deprecated STM Support for Agents
Agents participating in enclosing STM transaction is a deprecated feature.
I googled to find out about the reasons for this choice and I could not find any discussion about it.
Why was this feature deprecated (and eventually will be removed) from Akka?
Is there a newer approach to the achieve similar results?
Akka Essentials, by Munish K. Gupta, dedicates a whole chapter to the topic so, being a recent adopter of Akka, I would be surprised if the feature was just dropped...
Thanks for any clarification.
The main reason is that transactors won't make much sense in a clustered environment. Since akka tries to offer location transparency, this features has fallen out of favor.
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 10 years ago.
Improve this question
Are there any open source projects any of you would recommend to follow or contribute toward, including those already documented among the zf contributors, to add zend framework scaffolding of crud functionality for rapid development as found in most competitors frameworks?
As a contributor of not only the language and framework, but also as a user of zf on a daily basis, I know this is a topic of interest and I feel professional developers like you would find here would have something to contribute toward my question and finding a library that is underway that can be contributed to.
Still pointing out one Repo that generates a new module with folder structure, config and module class
Inforbiro / ZF2-Code-Generator
While personally i feel this to be more troublesome than doing it by hand, it's a first step only. Though it appears development already has stopped, for now.
If ever (and i'm pretty sure) there will be a ZF2-Tool, you'll find it at the zf-commons repository
ZF-Commons
Sorry, apparently this is not an appropriate question to ask, i've learned, at stackoverflow. Didn't realize this kind of question wasn't allowed since it doesn't have code I guess.