Amazon AWS Reviews

1. macloughlin

   · AV engineer · about 3 years ago
   The best cloud platform out there

   You could say a lot of things about AWS, but among the cloud platforms (and I've used quite a few) AWS takes the cake. It is logically structured, you can get through its documentation relatively easily, you have a great variety of tools and services to choose from [from AWS itself and from third-party developers in their marketplace]. There is a learning curve, there is quite a lot of it, but it is still way easier than some other platforms. I've used and abused AWS and EC2 specifically and for me it is the best.

   Pros:    Great documentation|Website structure visualization|You have control over everything|Flexibility

   Cons:    Learning curve|A lot of dashboards for different things

GitHub Reviews

1. proka

   16 days ago
   The Essential Platform for Modern Development

   GitHub is an essential platform for modern software development. It makes it easy to host, manage, and collaborate on code while providing powerful tools for version control, project management, and team collaboration. Its large open-source community is another major strength, offering developers access to countless projects, resources, and opportunities to learn. Overall, GitHub is a reliable and professional platform that has become a fundamental part of the developer ecosystem.

2. Reinhard

   · Boss at CLOUD Meister · over 5 years ago
   perfect 4 open Source

Amazon AWS mentions (486)

• Cloudflare Workers vs AWS Lambda: Real-World Performance Benchmarking

  In conclusion, Cloudflare Workers and AWS Lambda are two popular edge computing solutions that offer a range of benefits, including reduced latency, improved performance, and enhanced security. By understanding the key differences between these solutions, businesses can make informed decisions about which one to use. Whether you're building a real-time analytics application or a serverless API, Cloudflare Workers... - Source: dev.to / about 1 month ago

• Postgres rewritten in Rust, now passing 100% of the Postgres regression tests

  > but it's still a singleton instance, so where do you run it? Most hardware doesn't give you enough uptime for what you need here, because what you actually needed was a re-architecture for distribution / failover / whatever, and while you could ask your LLM to do that you aren't going to run your bank on the result. If only we had a way to solve these issues with tools capable of running Rust programs in that... - Source: Hacker News / about 2 months ago

• My Experience Moving from AWS to Sevalla

  Not because infrastructure isn't important. It is. Not because Amazon Web Services (AWS) is a bad platform. It isn't. - Source: dev.to / 2 months ago

• How to Use Pre-Signed S3 URLs for Direct Browser-to-Storage Uploads

  The AWS S3 documentation covers all of these in detail. The configuration takes about an hour to get right the first time and rarely needs changes after. - Source: dev.to / 3 months ago

• Why Your File Upload Endpoint Times Out at 4GB

  The first pattern is direct-to-storage. The client uploads chunks directly to an object storage service like Amazon S3 using pre-signed URLs. The application server creates the upload session and grants permission but never sees the file bytes. This pattern scales well because the application servers do not handle the upload bandwidth. - Source: dev.to / 3 months ago

GitHub mentions (2483)

• Your success message is not keyed on the thing that would make it false

  1228 push attempts died with fatal: could not read Username for 'https://github.com' — an https remote with no credential helper and no stored Credentials. First one 2026-07-21T20:48:03Z, still failing as I write this. Thirty-nine Days. - Source: dev.to / 2 days ago

• Pnpm 12.0

  They can include the protocol, it’s that regardless of what’s put in there it’ll use https, which is explained with examples both in the following sentences and then in more detail in a linked doc. > For repositories on GitHub, GitLab, and Bitbucket, a specifier now names a repository rather than choosing a transport. github:owner/repo, owner/repo, git+https://…, and git+ssh://git@… all resolve through the host's... - Source: Hacker News / 5 days ago

• Understanding the Git Workflow: Working Directory, Staging, Commit and Push

  First things first, and this case, we had to understand what git and git hub really is. From the lesson, Git is basically a version control systems installed on the computer that tracks changes made within a project. On the other hand, git hub refers to an online platform allowing users to store their git repositories and this could be easily accessed through [https://github.com/]. Apart from just storing... - Source: dev.to / 4 days ago

• Using Multiple GitHub Accounts: Automatically Select the Correct `gh` PAT Based on Repo Owner

  [credential] useHttpPath = true [credential "https://github.com/"] helper = helper = "!f() { \ [ \"$1\" = get ] || exit 0; \ account=''; \ while IFS='=' read -r k v; do \ [ \"$k\" = path ] && account=${v%%/*}; \ done; \ [ -n \"$account\" ] || exit 0; \ token=$(gh auth token --user \"$account\") || exit 0; \ printf... - Source: dev.to / 6 days ago

• Understanding The Git Workflow: Working Directory, Staging, Commit and Push

  This has now created our repository. This repository contains a link which we can share to other users, and this is the link that we need to link our local folder with the newly created repository. To do this, simply access it once you scroll down in the page you are in the simply copy the http link. This is what we shall use. The link usually looks like this http://github.com//. - Source: dev.to / 9 days ago