pocket VS Refactoring-Summary

Compare pocket vs Refactoring-Summary and see what are their differences.

pocket

Official implementation of the Pocket Network Protocol v1 (by pokt-network)

Refactoring-Summary

Summary of "Refactoring: Improving the Design of Existing Code" by Martin Fowler (by HugoMatilla)
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
pocket Refactoring-Summary
2 2
60 663
- -
8.7 0.0
5 months ago over 1 year ago
Go
MIT License -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

pocket

Posts with mentions or reviews of pocket. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-08-24.

Refactoring-Summary

Posts with mentions or reviews of Refactoring-Summary. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-08-24.
  • Ask HN: Where do I find good code to read?
    22 projects | news.ycombinator.com | 24 Aug 2023
    I find that reading books rather than code tends to be more helpful in terms of finding good takes on what clean code is -- more specifically books on refactoring or specific language-related features (like 'Effective Java' or 'Fluent Python'). The issue with just reading code is that many times - you'll miss out on why the author chose to use the expression or abstractions which they chose to use. Reading a book at least takes you through author's thought process. For an alternative - you could always browse repositories which contain notes on refactoring as well like this one (which does a good job summarizing some of the key principles from Fowler's book on refactoring):

    https://github.com/HugoMatilla/Refactoring-Summary

  • Is it okay to return my original List/Collection/Datastructure I'm storing my data in or is that against some OOP principals?
    1 project | /r/javahelp | 15 Mar 2021
    https://github.com/HugoMatilla/Refactoring-Summary#28-encapsulate-collection

What are some alternatives?

When comparing pocket and Refactoring-Summary you can also consider the following projects:

clara-rules - Forward-chaining rules in Clojure(Script)

glib - Read-only mirror of https://gitlab.gnome.org/GNOME/glib

retlang

sqlite - sqlite mirror

mx-chain-go - ⚡ The official implementation of the MultiversX blockchain protocol, written in golang.

htmx - </> htmx - high power tools for HTML

deno_std - deno standard modules

beanie - Asynchronous Python ODM for MongoDB

CodeView - Display code with syntax highlighting :sparkles: in native way.