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.
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 1 year ago.
Improve this question
Not only "swift-algorithms" but also "swift-collections" which is announced yesterday are so amazing library I think.
I wonder why apple didn't include that libraries in official swift.
Maybe you who will answer to me absolutely don't know too.
If you don't know, could you tell me if developer teams of each of library is different with developer team of official swift?
They're both not in the swift standard library (yet) because they haven't passed the Swift Evolution process. This is explained in the Swift Algorithms announcement:
It’s our ambition for the standard library to include a rich, pragmatic set of generic algorithms. We think the Algorithms package can help realize this goal by serving as a low-friction venue to build out new families of related algorithms—giving us an opportunity to iteratively explore the problem space and learn how different algorithms connect and interact—before graduating them into the standard library.
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
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 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?
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 5 years ago.
Improve this question
I am writing a scala app that needs to interact with DynamoDB. I see many open-sources out there. Some examples are:
https://github.com/piotrga/async-dynamo
https://github.com/bizreach/aws-dynamodb-scala
https://github.com/seratch/AWScala
https://bitbucket.org/atlassian/aws-scala
https://dwhjames.github.io/aws-wrap/index.html
Or perhaps it's better to use the official AWS SDK in Java?
Anyone have any experience with one of the above open-sources?
Check out the Alpakka project, which provides a DynamoDB connector. Alpakka connectors are built on Akka Streams and provide a way to interact with various technologies and protocols in a reactive way.