url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://peps.python.org/topic/ | Topic Index | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » Topic Index Toggle light / dark / auto colour theme Topic Index PEPs are indexed by topic on the pages below: Governance PEPs Packaging PEPs Release PEPs Typing PEPs Contents | 2026-01-13T08:49:06 |
https://dev.to/t/help/page/7 | Help! Page 7 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Help! Follow Hide A place to ask questions and provide answers. We're here to work things out together. Create Post submission guidelines This tag is to be used when you need to ask for help , not to share an article you think is helpful . Please review our community guidelines When asking for help, please follow these rules: Title: Write a clear, concise, title Body: What is your question/issue (provide as much detail as possible)? What technologies are you using? What were you expecting to happen? What is actually happening? What have you already tried/thought about? What errors are you getting? Please try to avoid very broad "How do I make x" questions, unless you have used Google and there are no tutorials on the subject. about #help This is a place to ask for help for specific problems. Before posting, please consider the following: If you're asking for peoples opinions on a specific technology/metholody - #discuss is more appropriate. Are you looking for how to build x? Have you Googled to see if there is already a comprehensive tutorial available? Older #help posts 4 5 6 7 8 9 10 11 12 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu 🚀 The New TypeScript Compiler in Go: Fast AF, but Should You Trust It? hmza hmza hmza Follow Jul 8 '25 🚀 The New TypeScript Compiler in Go: Fast AF, but Should You Trust It? # help # typescript # compiler # review 1 reaction Comments Add Comment 3 min read I realy need help, it can make my life better. shaheen amjed shaheen amjed shaheen amjed Follow Jul 6 '25 I realy need help, it can make my life better. # help # webdev # api # saas 17 reactions Comments 8 comments 2 min read How to Troubleshoot AWS ACM Certificate CAA Errors with Third-Party DNS Providers amalkabraham001 amalkabraham001 amalkabraham001 Follow for AWS Community Builders Jul 5 '25 How to Troubleshoot AWS ACM Certificate CAA Errors with Third-Party DNS Providers # help # certification # aws # acm 4 reactions Comments Add Comment 4 min read Any idea what web s Alex Simpson Alex Simpson Alex Simpson Follow Jun 1 '25 Any idea what web s # discuss # webdev # help Comments 1 comment 1 min read 🚀 Fixing Tailwind Init Error in React (Vite) Projects Khushalsarode Khushalsarode Khushalsarode Follow May 26 '25 🚀 Fixing Tailwind Init Error in React (Vite) Projects # help # react # tailwindcss # webdev 1 reaction Comments Add Comment 2 min read Hello, World! Google User Google User Google User Follow Jun 13 '25 Hello, World! # discuss # help Comments 1 comment 1 min read Heyy i am new here can you tell me what to do Harshit Singh Harshit Singh Harshit Singh Follow Jun 27 '25 Heyy i am new here can you tell me what to do # help # codenewbie # welcome # discuss Comments Add Comment 1 min read Trying to integrate Clerk for auth info Loavable application hollysanders hollysanders hollysanders Follow May 22 '25 Trying to integrate Clerk for auth info Loavable application # discuss # help # beginners # authentication Comments Add Comment 1 min read New here , know nothing about programing, eager to learn. #help the beginner Naheed Aziz Naheed Aziz Naheed Aziz Follow May 20 '25 New here , know nothing about programing, eager to learn. #help the beginner # help # beginners # tutorial # discuss Comments Add Comment 1 min read How to Secure a Segment of TCP Tunnel with TLS Using Gost? Davis8988 Davis8988 Davis8988 Follow May 19 '25 How to Secure a Segment of TCP Tunnel with TLS Using Gost? # help # go # networking # security Comments Add Comment 1 min read I'm a self-taught dev from a small town in India. I need help getting a laptop/PC — can't afford one. Robert Macwan Robert Macwan Robert Macwan Follow May 17 '25 I'm a self-taught dev from a small town in India. I need help getting a laptop/PC — can't afford one. # help Comments Add Comment 2 min read Day 1) Sai Pooja Reddy Palle Sai Pooja Reddy Palle Sai Pooja Reddy Palle Follow May 17 '25 Day 1) # help # programming # java # tutorial Comments Add Comment 1 min read Erro de política de execução npm Caio Caio Caio Follow Jun 10 '25 Erro de política de execução npm # help # npm # programming # webdev 16 reactions Comments 2 comments 2 min read Hello guys, I'm Jameel I'm glad to be here. Jameel Star Jameel Star Jameel Star Follow Jun 16 '25 Hello guys, I'm Jameel I'm glad to be here. # help # codenewbie # android # ui Comments 1 comment 1 min read APIs Asante Todd Asante Todd Asante Todd Follow May 1 '25 APIs # help # api # backend # debugging Comments Add Comment 1 min read [Career Advice] 6 years in frontend (React / React Native) - confused about future Mayank Mayank Mayank Follow Apr 30 '25 [Career Advice] 6 years in frontend (React / React Native) - confused about future # help # frontend # programming Comments Add Comment 1 min read How to Handle Automatic Logout Due to Inactivity in MySQL Arman Rahman Arman Rahman Arman Rahman Follow Apr 30 '25 How to Handle Automatic Logout Due to Inactivity in MySQL # help # phpmyadmin # webdev Comments Add Comment 1 min read Configure Kubegreen to Sleep Pods on Weeknights and Shut Down on Weekends Sanket Arali Sanket Arali Sanket Arali Follow Apr 30 '25 Configure Kubegreen to Sleep Pods on Weeknights and Shut Down on Weekends # help # kuberenetes # devops # discuss Comments Add Comment 1 min read The Biggest Career Mistake in 2025: Thinking AI Doesn’t Apply to You Hasanul Mukit Hasanul Mukit Hasanul Mukit Follow May 31 '25 The Biggest Career Mistake in 2025: Thinking AI Doesn’t Apply to You # help # ai # career # beginners 2 reactions Comments Add Comment 3 min read Can Roblox Be the Future of Gaming Programming❔ Joao Dalbem Joao Dalbem Joao Dalbem Follow May 30 '25 Can Roblox Be the Future of Gaming Programming❔ # help # gamedev # ai # discuss Comments 4 comments 1 min read Efficient Progress Aggregation in a Deeply Nested Task Hierarchy with Real-Time Sync (PostgreSQL + PowerSync) murat murat murat Follow Apr 25 '25 Efficient Progress Aggregation in a Deeply Nested Task Hierarchy with Real-Time Sync (PostgreSQL + PowerSync) # help # database # powersync 2 reactions Comments Add Comment 2 min read Site do meu casamento (Alguém me ajuda?) Ryan Gwalchmei Ryan Gwalchmei Ryan Gwalchmei Follow Apr 24 '25 Site do meu casamento (Alguém me ajuda?) # help # webdev # opensource # github Comments Add Comment 1 min read 🚗 I Built a Bot That Automatically Books ICBC Road Tests in BC (6+ Month Wait Times Next Week!) Ivan Vedenin Ivan Vedenin Ivan Vedenin Follow Jun 15 '25 🚗 I Built a Bot That Automatically Books ICBC Road Tests in BC (6+ Month Wait Times Next Week!) # help # icbc # programming # python 2 reactions Comments 1 comment 1 min read Execution Policy Error in npm Caio Caio Caio Follow Jun 10 '25 Execution Policy Error in npm # help # npm # programming # webdev 16 reactions Comments 2 comments 2 min read Toggle Menu not working on iPhone Nick Scott Nick Scott Nick Scott Follow Apr 23 '25 Toggle Menu not working on iPhone # help # webdev # softwaredevelopment # ios Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://peps.python.org/pep-0761/ | PEP 761 – Deprecating PGP signatures for CPython artifacts | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 761 Toggle light / dark / auto colour theme PEP 761 – Deprecating PGP signatures for CPython artifacts Author : Seth Michael Larson <seth at python.org> Sponsor : Hugo van Kemenade Discussions-To : Discourse thread Status : Active Type : Process Created : 08-Oct-2024 Python-Version : 3.14 Post-History : 25-Sep-2024 , 09-Oct-2024 Resolution : 06-Nov-2024 Table of Contents Abstract Motivation Rationale Preserve expectations across a Python release Release managers, not releases Gordian knot of signing methods and verifiers Specification Deprecation and discontinuation of PGP signatures Delaying discontinuation of PGP signatures Backwards Compatibility Security Implications How to Teach This Rejected Ideas Continue publishing PGP signatures indefinitely Removing previous PGP signatures Appendix Support for offline verification Support for a pre-compiled executable for verification Copyright Abstract Since Python 3.11.0, CPython has provided two verifiable digital signatures for all CPython artifacts: PGP and Sigstore. PGP’s design requires the maintenance and protection of long-lived private keys by trusted parties. PGP’s security and ergonomics have been criticized by security practitioners for many years now, with the biggest issue being that there were few alternatives for “artifact signing” being proposed or adopted. Sigstore’s design philosophy has focused on the ergonomics of signing and verifying and uses short-lived keys with strongly-bound human-readable identities via OpenID Connect . Sigstore has both development and adoption momentum, seeing adoption by PyPI, NPM, Homebrew, and GitHub, among other ecosystems. This PEP proposes to move CPython to using Sigstore exclusively for signing artifacts through a deprecation and eventual discontinuance of providing PGP signatures with new release managers. Motivation CPython’s releases are release-manager-centric, where a single person maintains multiple CPython releases from pre-release to end-of-life over the course of many years. Requiring release managers to maintain and protect PGP private keys for seven or more years is an unnecessary burden in the new age of ergonomic and ephemeral signing keys. Comparatively, Sigstore only requires release managers to click a button during the release process to OAuth sign-on to their identity provider. Maintaining the integrity of accounts on identity providers like GitHub is already an expectation of being a Python release manager or core team member, such as through multi-factor authentication and strong unique passwords. Rationale Preserve expectations across a Python release To avoid breaking downstream verifiers, the expectations for verification materials availability SHOULD NOT be changed during a feature release’s lifecycle. Release managers, not releases The discontinuation of PGP signatures doesn’t necessarily have to happen on a “release manager boundary”; a new Python release could be a potential boundary. Because the primary motivation for deprecating PGP is ergonomics, deciding to drop PGP for one release while a release manager still has obligations to provide PGP signatures for other releases for multiple years isn’t much savings of effort. A new release manager also represents a new PGP public key that downstream verifiers need to adopt. By choosing to make the change during this period, this minimizes the breakage to a place in downstream maintenance where a change will already be necessary. Gordian knot of signing methods and verifiers CPython providing both PGP and Sigstore signatures concurrently creates a “ Gordian knot ” where verifiers are disincentivized to migrate to a new signature method due to the continued and expected availability of an existing signature method, thus propagating the apparent demand for maintaining the existing signature method. This situation slows down the adoption of new signature methods like Sigstore for both signature-producing projects and signature-verifying ecosystems by not creating a “need” to automate and integrate the signature method into verifier tooling. By changing the expectation of what future signature methods will be available, the incentive-knot can be broken by spurring the adoption of the new signature method in downstream tooling . This change to verifier tooling also makes other upstream projects able to migrate to publishing only Sigstore signatures, resulting in a positive feedback loop of adoption. Specification Because PGP keys are tied to a release manager identity, the change to availability of PGP signatures will be tied to release managers instead of individual releases (3.13, 3.14, etc). This PEP both deprecates and proposes a discontinuation timeline for PGP signatures. Deprecation and discontinuation of PGP signatures This PEP deprecates PGP signatures for future CPython releases and recommends verifiers to adopt Sigstore to verify CPython artifacts as an alternative to PGP. This PEP also removes the expectation that PGP signatures be published by future release managers that don’t already maintain a stable Python release. At the time of writing this would be Hugo van Kemenade, as 3.14 is the next Python version without a stable release. Releases which already have a stable release (3.13, 3.12, 3.11, etc) are not affected and will continue to provide PGP signatures for artifacts until they are end-of-life. All existing PGP signatures will continue to work as expected. Delaying discontinuation of PGP signatures This PEP provides a mechanism to delay the discontinuation of PGP signatures from active and upcoming CPython releases in case of extraordinary circumstances. Deprecation of PGP signatures can’t be changed without a superseding PEP. The Steering Council MAY at a future date after this PEP’s acceptance decide to delay the discontinuation of PGP signatures to a future CPython release. If the Steering Council decides to delay the discontinuation of PGP signatures then all active release managers MUST provide PGP signatures for their covered CPython artifacts for the remainder of their tenure as a release manager. This includes all steps required to do so, such as generating a new PGP key and publishing their identity to python.org. The discontinuation of PGP signatures then is automatically scheduled for the next release manager without a stable release, to be highlighted in the Steering Council decision. Backwards Compatibility This proposal would remove the ability to verify future CPython artifacts using PGP. Any downstream verifiers using PGP for CPython artifacts would need to either start using Sigstore, verify their source code of CPython through other means, or stop verification altogether for future CPython releases. Security Implications PGP and Sigstore have different security models, so by removing PGP signatures this means that all users only have the option to rely on the security model provided by Sigstore. In general, the security model required for artifact signatures is being able to detect whether a given artifact is from the expected source and hasn’t been modified, regardless of the security or integrity of the hosting service (in CPython’s case: python.org/downloads). Sigstore’s security model depends more on centralized infrastructure compared to PGP, such as the “public good” signature transparency log (Rekor), certificate authority and transparency log (Fulcio), and the security of OpenID Connect identity providers like Google and GitHub. CPython’s development already depends on the security of some of these services and the others are better resourced than any individual release manager to provide long-term public key management. How to Teach This CPython already documents how to verify artifacts using Sigstore based on the pre-published identities of release managers. Documentation will be updated to indicate the deprecation and future expectations of PGP signatures. Verifying signatures of CPython artifacts isn’t something we should expect from new Python users. Instead, Sigstore is more likely to be a part of a downstream integrator’s build pipeline such as a Linux distro, Homebrew, pyenv, or others that programmatically fetch and build CPython from source. Rejected Ideas Continue publishing PGP signatures indefinitely Being a release manager is already a difficult, time-consuming, and long-term commitment that is typically done on a volunteer basis. Thus we see removal of PGP key management duties as a step towards reducing burnout and stress of future release managers and improving the sustainability of CPython. Removing previous PGP signatures This PEP doesn’t intend to break any infrastructure built around existing Python versions, instead only changing the expectations around future Python versions. Thus all PGP signatures that are already available on python.org will continue to be available even after PGP discontinuance. Appendix Support for offline verification During the pre-PEP discussion , there was a question of whether offline verification was supported by Sigstore. Using a Sigstore bundle ( .sigstore ) file, Sigstore clients support verifying the artifact completely offline . Using offline verification with Sigstore requires disabling root of trust updates and “pinning” a root of trust in a file to use during verification. Pinning a root of trust means signatures made after a new root of trust is established would no longer be able to verify using a “pinned” previous root of trust. New roots of trust are expected to be rare events, such as when the root of trust is compromised, and in this case verifiers would want signatures to fail to verify. Offline verification also makes revocation checks impossible, but this is similar to PGP’s model where revocation of keys requires an online lookup. Barring rare events like root of trust compromise, using offline verification with Sigstore doesn’t impose additional operations requirements to verifiers. Support for a pre-compiled executable for verification During discussion there were requests for a pre-compiled executable that could be used for verifying Sigstore bundles without needing to either install a Go build toolchain to build sigstore-go from source or already have a working Python installation for sigstore-python . Cosign is another Sigstore project that provides pre-compiled standalone binaries and supports verifying bundles offline: # Download Cosign wget https : // github . com / sigstore / cosign / releases / download / v2 .4.1 / cosign - linux - amd64 # For offline verification, also need the Root of Trust. Can be grabbed # from GitHub at: https://github.com/sigstore/root-signing/blob/main/targets/trusted_root.json wget https : // raw . githubusercontent . com / sigstore / root - signing / refs / heads / main / targets / trusted_root . json # Download CPython artifacts wget https : // www . python . org / ftp / python / 3.13.0 / Python - 3.13.0 . tgz wget https : // www . python . org / ftp / python / 3.13.0 / Python - 3.13.0 . tgz . sigstore ./ cosign - linux - amd64 verify - blob \ -- new - bundle - format \ -- certificate - oidc - issuer 'https://accounts.google.com' \ -- certificate - identity 'thomas@python.org' \ -- bundle ./ Python - 3.13.0 . tgz . sigstore \ # --offline and --trust-root optional for offline verification -- offline \ -- trust - root ./ trusted_root . json \ ./ Python - 3.13.0 . tgz Copyright This document is placed in the public domain or under the CC0-1.0-Universal license, whichever is more permissive. Source: https://github.com/python/peps/blob/main/peps/pep-0761.rst Last modified: 2024-11-06 19:20:02 GMT Contents Abstract Motivation Rationale Preserve expectations across a Python release Release managers, not releases Gordian knot of signing methods and verifiers Specification Deprecation and discontinuation of PGP signatures Delaying discontinuation of PGP signatures Backwards Compatibility Security Implications How to Teach This Rejected Ideas Continue publishing PGP signatures indefinitely Removing previous PGP signatures Appendix Support for offline verification Support for a pre-compiled executable for verification Copyright Page Source (GitHub) | 2026-01-13T08:49:06 |
https://docs.python.org/3/license.html#expat | History and License — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents History and License History of the software Terms and conditions for accessing or otherwise using Python PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION Licenses and Acknowledgements for Incorporated Software Mersenne Twister Sockets Asynchronous socket services Cookie management Execution tracing UUencode and UUdecode functions XML Remote Procedure Calls test_epoll Select kqueue SipHash24 strtod and dtoa OpenSSL expat libffi zlib cfuhash libmpdec W3C C14N test suite mimalloc asyncio Global Unbounded Sequences (GUS) Zstandard bindings Previous topic Copyright This page Report a bug Show source Navigation index modules | previous | Python » 3.14.2 Documentation » History and License | Theme Auto Light Dark | History and License ¶ History of the software ¶ Python was created in the early 1990s by Guido van Rossum at Stichting Mathematisch Centrum (CWI, see https://www.cwi.nl ) in the Netherlands as a successor of a language called ABC. Guido remains Python’s principal author, although it includes many contributions from others. In 1995, Guido continued his work on Python at the Corporation for National Research Initiatives (CNRI, see https://www.cnri.reston.va.us ) in Reston, Virginia where he released several versions of the software. In May 2000, Guido and the Python core development team moved to BeOpen.com to form the BeOpen PythonLabs team. In October of the same year, the PythonLabs team moved to Digital Creations, which became Zope Corporation. In 2001, the Python Software Foundation (PSF, see https://www.python.org/psf/ ) was formed, a non-profit organization created specifically to own Python-related Intellectual Property. Zope Corporation was a sponsoring member of the PSF. All Python releases are Open Source (see https://opensource.org for the Open Source Definition). Historically, most, but not all, Python releases have also been GPL-compatible; the table below summarizes the various releases. Release Derived from Year Owner GPL-compatible? (1) 0.9.0 thru 1.2 n/a 1991-1995 CWI yes 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes 1.6 1.5.2 2000 CNRI no 2.0 1.6 2000 BeOpen.com no 1.6.1 1.6 2001 CNRI yes (2) 2.1 2.0+1.6.1 2001 PSF no 2.0.1 2.0+1.6.1 2001 PSF yes 2.1.1 2.1+2.0.1 2001 PSF yes 2.1.2 2.1.1 2002 PSF yes 2.1.3 2.1.2 2002 PSF yes 2.2 and above 2.1.1 2001-now PSF yes Note GPL-compatible doesn’t mean that we’re distributing Python under the GPL. All Python licenses, unlike the GPL, let you distribute a modified version without making your changes open source. The GPL-compatible licenses make it possible to combine Python with other software that is released under the GPL; the others don’t. According to Richard Stallman, 1.6.1 is not GPL-compatible, because its license has a choice of law clause. According to CNRI, however, Stallman’s lawyer has told CNRI’s lawyer that 1.6.1 is “not incompatible” with the GPL. Thanks to the many outside volunteers who have worked under Guido’s direction to make these releases possible. Terms and conditions for accessing or otherwise using Python ¶ Python software and documentation are licensed under the Python Software Foundation License Version 2. Starting with Python 3.8.6, examples, recipes, and other code in the documentation are dual licensed under the PSF License Version 2 and the Zero-Clause BSD license . Some software incorporated into Python is under different licenses. The licenses are listed with code falling under that license. See Licenses and Acknowledgements for Incorporated Software for an incomplete list of these licenses. PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 ¶ 1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using this software ("Python") in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative version, provided, however, that PSF's License Agreement and PSF's notice of copyright, i.e., "Copyright © 2001 Python Software Foundation; All Rights Reserved" are retained in Python alone or in any derivative version prepared by Licensee. 3. In the event Licensee prepares a derivative work that is based on or incorporates Python or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python. 4. PSF is making Python available to Licensee on an "AS IS" basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between PSF and Licensee. This License Agreement does not grant permission to use PSF trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By copying, installing or otherwise using Python, Licensee agrees to be bound by the terms and conditions of this License Agreement. BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 ¶ BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the Individual or Organization ("Licensee") accessing and otherwise using this software in source or binary form and its associated documentation ("the Software"). 2. Subject to the terms and conditions of this BeOpen Python License Agreement, BeOpen hereby grants Licensee a non-exclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use the Software alone or in any derivative version, provided, however, that the BeOpen Python License is retained in the Software, alone or in any derivative version prepared by Licensee. 3. BeOpen is making the Software available to Licensee on an "AS IS" basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 5. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 6. This License Agreement shall be governed by and interpreted in all respects by the law of the State of California, excluding conflict of law provisions. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between BeOpen and Licensee. This License Agreement does not grant permission to use BeOpen trademarks or trade names in a trademark sense to endorse or promote products or services of Licensee, or any third party. As an exception, the "BeOpen Python" logos available at http://www.pythonlabs.com/logos.html may be used according to the permissions granted on that web page. 7. By copying, installing or otherwise using the software, Licensee agrees to be bound by the terms and conditions of this License Agreement. CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 ¶ 1. This LICENSE AGREEMENT is between the Corporation for National Research Initiatives, having an office at 1895 Preston White Drive, Reston, VA 20191 ("CNRI"), and the Individual or Organization ("Licensee") accessing and otherwise using Python 1.6.1 software in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, CNRI hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python 1.6.1 alone or in any derivative version, provided, however, that CNRI's License Agreement and CNRI's notice of copyright, i.e., "Copyright © 1995-2001 Corporation for National Research Initiatives; All Rights Reserved" are retained in Python 1.6.1 alone or in any derivative version prepared by Licensee. Alternately, in lieu of CNRI's License Agreement, Licensee may substitute the following text (omitting the quotes): "Python 1.6.1 is made available subject to the terms and conditions in CNRI's License Agreement. This Agreement together with Python 1.6.1 may be located on the internet using the following unique, persistent identifier (known as a handle): 1895.22/1013. This Agreement may also be obtained from a proxy server on the internet using the following URL: http://hdl.handle.net/1895.22/1013". 3. In the event Licensee prepares a derivative work that is based on or incorporates Python 1.6.1 or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python 1.6.1. 4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. This License Agreement shall be governed by the federal intellectual property law of the United States, including without limitation the federal copyright law, and, to the extent such U.S. federal law does not apply, by the law of the Commonwealth of Virginia, excluding Virginia's conflict of law provisions. Notwithstanding the foregoing, with regard to derivative works based on Python 1.6.1 that incorporate non-separable material that was previously distributed under the GNU General Public License (GPL), the law of the Commonwealth of Virginia shall govern this License Agreement only as to issues arising under or with respect to Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between CNRI and Licensee. This License Agreement does not grant permission to use CNRI trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By clicking on the "ACCEPT" button where indicated, or by copying, installing or otherwise using Python 1.6.1, Licensee agrees to be bound by the terms and conditions of this License Agreement. CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ¶ Copyright © 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION ¶ Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Licenses and Acknowledgements for Incorporated Software ¶ This section is an incomplete, but growing list of licenses and acknowledgements for third-party software incorporated in the Python distribution. Mersenne Twister ¶ The _random C extension underlying the random module includes code based on a download from http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/MT2002/emt19937ar.html . The following are the verbatim comments from the original code: A C-program for MT19937, with initialization improved 2002/1/26. Coded by Takuji Nishimura and Makoto Matsumoto. Before using, initialize the state by using init_genrand(seed) or init_by_array(init_key, key_length). Copyright (C) 1997 - 2002, Makoto Matsumoto and Takuji Nishimura, All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The names of its contributors may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Any feedback is very welcome. http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html email: m-mat @ math.sci.hiroshima-u.ac.jp (remove space) Sockets ¶ The socket module uses the functions, getaddrinfo() , and getnameinfo() , which are coded in separate source files from the WIDE Project, https://www.wide.ad.jp/ . Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Asynchronous socket services ¶ The test.support.asynchat and test.support.asyncore modules contain the following notice: Copyright 1996 by Sam Rushing All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Sam Rushing not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Cookie management ¶ The http.cookies module contains the following notice: Copyright 2000 by Timothy O'Malley <timo@alum.mit.edu> All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Timothy O'Malley not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Timothy O'Malley DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL Timothy O'Malley BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Execution tracing ¶ The trace module contains the following notice: portions copyright 2001, Autonomous Zones Industries, Inc., all rights... err... reserved and offered to the public under the terms of the Python 2.2 license. Author: Zooko O'Whielacronx http://zooko.com/ mailto:zooko@zooko.com Copyright 2000, Mojam Media, Inc., all rights reserved. Author: Skip Montanaro Copyright 1999, Bioreason, Inc., all rights reserved. Author: Andrew Dalke Copyright 1995-1997, Automatrix, Inc., all rights reserved. Author: Skip Montanaro Copyright 1991-1995, Stichting Mathematisch Centrum, all rights reserved. Permission to use, copy, modify, and distribute this Python software and its associated documentation for any purpose without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of neither Automatrix, Bioreason or Mojam Media be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. UUencode and UUdecode functions ¶ The uu codec contains the following notice: Copyright 1994 by Lance Ellinghouse Cathedral City, California Republic, United States of America. All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Lance Ellinghouse not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Modified by Jack Jansen, CWI, July 1995: - Use binascii module to do the actual line-by-line conversion between ascii and binary. This results in a 1000-fold speedup. The C version is still 5 times faster, though. - Arguments more compliant with Python standard XML Remote Procedure Calls ¶ The xmlrpc.client module contains the following notice: The XML-RPC client interface is Copyright (c) 1999-2002 by Secret Labs AB Copyright (c) 1999-2002 by Fredrik Lundh By obtaining, using, and/or copying this software and/or its associated documentation, you agree that you have read, understood, and will comply with the following terms and conditions: Permission to use, copy, modify, and distribute this software and its associated documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Secret Labs AB or the author not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT- ABILITY AND FITNESS. IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. test_epoll ¶ The test.test_epoll module contains the following notice: Copyright (c) 2001-2006 Twisted Matrix Laboratories. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Select kqueue ¶ The select module contains the following notice for the kqueue interface: Copyright (c) 2000 Doug White, 2006 James Knight, 2007 Christian Heimes All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SipHash24 ¶ The file Python/pyhash.c contains Marek Majkowski’ implementation of Dan Bernstein’s SipHash24 algorithm. It contains the following note: <MIT License> Copyright (c) 2013 Marek Majkowski <marek@popcount.org> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. </MIT License> Original location: https://github.com/majek/csiphash/ Solution inspired by code from: Samuel Neves (supercop/crypto_auth/siphash24/little) djb (supercop/crypto_auth/siphash24/little2) Jean-Philippe Aumasson (https://131002.net/siphash/siphash24.c) strtod and dtoa ¶ The file Python/dtoa.c , which supplies C functions dtoa and strtod for conversion of C doubles to and from strings, is derived from the file of the same name by David M. Gay, currently available from https://web.archive.org/web/20220517033456/http://www.netlib.org/fp/dtoa.c . The original file, as retrieved on March 16, 2009, contains the following copyright and licensing notice: /**************************************************************** * * The author of this software is David M. Gay. * * Copyright (c) 1991, 2000, 2001 by Lucent Technologies. * * Permission to use, copy, modify, and distribute this software for any * purpose without fee is hereby granted, provided that this entire notice * is included in all copies of any software which is or includes a copy * or modification of this software and in all copies of the supporting * documentation for such software. * * THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED * WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY * REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY * OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. * ***************************************************************/ OpenSSL ¶ The modules hashlib , posix and ssl use the OpenSSL library for added performance if made available by the operating system. Additionally, the Windows and macOS installers for Python may include a copy of the OpenSSL libraries, so we include a copy of the OpenSSL license here. For the OpenSSL 3.0 release, and later releases derived from that, the Apache License v2 applies: Apache License Version 2.0, January 2004 https://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS expat ¶ The pyexpat extension is built using an included copy of the expat sources unless the build is configured --with-system-expat : Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. libffi ¶ The _ctypes C extension underlying the ctypes module is built using an included copy of the libffi sources unless the build is configured --with-system-libffi : Copyright (c) 1996-2008 Red Hat, Inc and others. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. zlib ¶ The zlib extension is built using an included copy of the zlib sources if the zlib version found on the system is too old to be used for the build: Copyright (C) 1995-2011 Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly Mark Adler jloup@gzip.org madler@alumni.caltech.edu cfuhash ¶ The implementation of the hash table used by the tracemalloc is based on the cfuhash project: Copyright (c) 2005 Don Owens All rights reserved. This code is released under the BSD license: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. libmpdec ¶ The _decimal C extension underlying the decimal module is built using an included copy of the libmpdec library unless the build is configured --with-system-libmpdec : Copyright (c) 2008-2020 Stefan Krah. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. W3C C14N test suite ¶ The C14N 2.0 test suite in the test package ( Lib/test/xmltestdata/c14n-20/ ) was retrieved from the W3C website at https://www.w3.org/TR/xml-c14n2-testcases/ and is distributed under the 3-clause BSD license: Copyright (c) 2013 W3C(R) (MIT, ERCIM, Keio, Beihang), All Rights Reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of works must retain the original copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the original copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the W3C nor the names of its contributors may be used to endorse or promote products derived from this work without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. mimalloc ¶ MIT License: Copyright (c) 2018-2021 Microsoft Corporation, Daan Leijen Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. asyncio ¶ Parts of the asyncio module are incorporated from uvloop 0.16 , which is distributed under the MIT license: Copyright (c) 2015-2021 MagicStack Inc. http://magic.io Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Global Unbounded Sequences (GUS) ¶ The file Python/qsbr.c is adapted from FreeBSD’s “Global Unbounded Sequences” safe memory reclamation scheme in subr_smr.c . The file is distributed under the 2-Clause BSD License: Copyright (c) 2019,2020 Jeffrey Roberson <jeff@FreeBSD.org> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following con | 2026-01-13T08:49:06 |
https://gg.forem.com/t/indie | Indie - Gamers Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Gamers Forem Close # indie Follow Hide independent spirit, lo-fi vibes Create Post Older #indie posts 1 2 3 4 5 6 7 8 9 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu My first game - Online Sudoku Corbin Corbin Corbin Follow Jan 2 My first game - Online Sudoku # gamedev # sudoku # puzzlegames # indie 4 reactions Comments Add Comment 1 min read My First game - Comms Under Fire Shaquille Niekerk Shaquille Niekerk Shaquille Niekerk Follow Dec 11 '25 My First game - Comms Under Fire # gamedev # indie # cloudgaming # singleplayer 8 reactions Comments 3 comments 1 min read 🚀 Launching Market Tycoon: A Casual Supermarket Management Game! seagames seagames seagames Follow Dec 6 '25 🚀 Launching Market Tycoon: A Casual Supermarket Management Game! # indie # gamedev # pcgaming # playstation 48 reactions Comments 1 comment 3 min read 🚇 Metro — The Only Series That Made Me Afraid of Breathing Faisal Mujahid Faisal Mujahid Faisal Mujahid Follow Dec 3 '25 🚇 Metro — The Only Series That Made Me Afraid of Breathing # indie # pcgaming # gamedev # playstation 1 reaction Comments 2 comments 1 min read One Year of Building My Untitled Horror Inspired OS Game STG STG STG Follow Nov 19 '25 One Year of Building My Untitled Horror Inspired OS Game # indie # gamedev # pcgaming # modding 4 reactions Comments 10 comments 2 min read Theater Alpha - The Rewind Update Terrillo Walls Terrillo Walls Terrillo Walls Follow Nov 9 '25 Theater Alpha - The Rewind Update # gamedev # gamedesign # strategy # indie 9 reactions Comments 3 comments 2 min read IGN: Absolum Review Gaming News Gaming News Gaming News Follow Oct 9 '25 IGN: Absolum Review # pcgaming # nintendoswitch # indie # playstation Comments Add Comment 1 min read IGN: Megabonk - Quick Review Gaming News Gaming News Gaming News Follow Oct 7 '25 IGN: Megabonk - Quick Review # pcgaming # indie # steam Comments Add Comment 1 min read Wolverine PS5 Game: Insomniac’s Marvel Hit Sanjay Naker Sanjay Naker Sanjay Naker Follow Oct 7 '25 Wolverine PS5 Game: Insomniac’s Marvel Hit # gamedev # pcgaming # indie # playstation Comments Add Comment 2 min read How Narrative Design Helps Indie Games Compete with AAA Titles Mitch Mitch Mitch Follow Nov 7 '25 How Narrative Design Helps Indie Games Compete with AAA Titles # gamedev # indie # indiegames 7 reactions Comments Add Comment 3 min read IGN: Bye Sweet Carole - Official Launch Trailer Gaming News Gaming News Gaming News Follow Oct 10 '25 IGN: Bye Sweet Carole - Official Launch Trailer # indie # pcgaming # playstation # xbox Comments Add Comment 1 min read Slicing Through Code: I Built Fruit Ninja Faisal Mujahid Faisal Mujahid Faisal Mujahid Follow Nov 2 '25 Slicing Through Code: I Built Fruit Ninja # gamedev # indie # unity3d # mobilegaming 4 reactions Comments Add Comment 1 min read GameSpot: Super Meat Boy 3D. It's good... BUT | First Look Gaming News Gaming News Gaming News Follow Oct 18 '25 GameSpot: Super Meat Boy 3D. It's good... BUT | First Look # pcgaming # indie # retrogaming Comments Add Comment 1 min read IGN: Super Meat Boy 3D Makes Great Use of its Extra Dimension Gaming News Gaming News Gaming News Follow Oct 17 '25 IGN: Super Meat Boy 3D Makes Great Use of its Extra Dimension # pcgaming # indie # retrogaming Comments Add Comment 1 min read IGN: Crabs Must Die! - Official Demo Launch Trailer Gaming News Gaming News Gaming News Follow Oct 17 '25 IGN: Crabs Must Die! - Official Demo Launch Trailer # gamedev # pcgaming # indie # steam Comments 1 comment 1 min read 70,000 users affected in Discord customer service breach UPDATE: Social platform clarifies it has secured the affected systems Kanha Gochhayat Kanha Gochhayat Kanha Gochhayat Follow Oct 10 '25 70,000 users affected in Discord customer service breach UPDATE: Social platform clarifies it has secured the affected systems # gamedev # pcgaming # indie # playstation Comments Add Comment 2 min read GameSpot: Absolum Review: A Sleeper Hit Gaming News Gaming News Gaming News Follow Oct 10 '25 GameSpot: Absolum Review: A Sleeper Hit # pcgaming # indie # retrogaming Comments 1 comment 1 min read Hollow Knight: Silksong derruba as lojas digitais e até combate a pirataria com preço justo IamThiago-IT IamThiago-IT IamThiago-IT Follow Sep 6 '25 Hollow Knight: Silksong derruba as lojas digitais e até combate a pirataria com preço justo # gamedev # pcgaming # indie # playstation 1 reaction Comments Add Comment 3 min read IGN: Hades 2 - How to Unlock (and Survive) The Surface Gaming News Gaming News Gaming News Follow Oct 3 '25 IGN: Hades 2 - How to Unlock (and Survive) The Surface # pcgaming # indie Comments Add Comment 1 min read IGN: Carnival Hunt - Official Steam Open Playtest Trailer Gaming News Gaming News Gaming News Follow Sep 30 '25 IGN: Carnival Hunt - Official Steam Open Playtest Trailer # pcgaming # steam # indie # gamedev Comments Add Comment 1 min read IGN: Maid of Sker VR - Official Announcement Trailer | Horror Game Awards Showcase 2025 Gaming News Gaming News Gaming News Follow Sep 30 '25 IGN: Maid of Sker VR - Official Announcement Trailer | Horror Game Awards Showcase 2025 # pcgaming # playstation # indie Comments Add Comment 1 min read IGN: Kaiju Cleanup - Official Announcement Trailer Gaming News Gaming News Gaming News Follow Sep 29 '25 IGN: Kaiju Cleanup - Official Announcement Trailer # pcgaming # gamedev # indie # steam Comments Add Comment 1 min read IGN: Titan Quest 2 - Official Northern Beaches Gameplay Deep Dive Trailer Gaming News Gaming News Gaming News Follow Sep 30 '25 IGN: Titan Quest 2 - Official Northern Beaches Gameplay Deep Dive Trailer # pcgaming # steam # indie Comments Add Comment 1 min read IGN: Morbid Metal - Official Playtest Announcement Trailer | TGS 2025 Gaming News Gaming News Gaming News Follow Sep 29 '25 IGN: Morbid Metal - Official Playtest Announcement Trailer | TGS 2025 # pcgaming # indie # steam # gamedev Comments Add Comment 1 min read GameSpot: 2XKO - Teemo Gameplay Reveal Trailer Gaming News Gaming News Gaming News Follow Sep 29 '25 GameSpot: 2XKO - Teemo Gameplay Reveal Trailer # pcgaming # gamedev # indie Comments Add Comment 1 min read loading... trending guides/resources 🚇 Metro — The Only Series That Made Me Afraid of Breathing Slicing Through Code: I Built Fruit Ninja One Year of Building My Untitled Horror Inspired OS Game How Narrative Design Helps Indie Games Compete with AAA Titles 🚀 Launching Market Tycoon: A Casual Supermarket Management Game! My First game - Comms Under Fire Theater Alpha - The Rewind Update 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Gamers Forem — An inclusive community for gaming enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Gamers Forem © 2025 - 2026. We're a place where gamers unite, level up, and share epic adventures. Log in Create account | 2026-01-13T08:49:06 |
https://docs.python.org/3/license.html#uuencode-and-uudecode-functions | History and License — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents History and License History of the software Terms and conditions for accessing or otherwise using Python PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION Licenses and Acknowledgements for Incorporated Software Mersenne Twister Sockets Asynchronous socket services Cookie management Execution tracing UUencode and UUdecode functions XML Remote Procedure Calls test_epoll Select kqueue SipHash24 strtod and dtoa OpenSSL expat libffi zlib cfuhash libmpdec W3C C14N test suite mimalloc asyncio Global Unbounded Sequences (GUS) Zstandard bindings Previous topic Copyright This page Report a bug Show source Navigation index modules | previous | Python » 3.14.2 Documentation » History and License | Theme Auto Light Dark | History and License ¶ History of the software ¶ Python was created in the early 1990s by Guido van Rossum at Stichting Mathematisch Centrum (CWI, see https://www.cwi.nl ) in the Netherlands as a successor of a language called ABC. Guido remains Python’s principal author, although it includes many contributions from others. In 1995, Guido continued his work on Python at the Corporation for National Research Initiatives (CNRI, see https://www.cnri.reston.va.us ) in Reston, Virginia where he released several versions of the software. In May 2000, Guido and the Python core development team moved to BeOpen.com to form the BeOpen PythonLabs team. In October of the same year, the PythonLabs team moved to Digital Creations, which became Zope Corporation. In 2001, the Python Software Foundation (PSF, see https://www.python.org/psf/ ) was formed, a non-profit organization created specifically to own Python-related Intellectual Property. Zope Corporation was a sponsoring member of the PSF. All Python releases are Open Source (see https://opensource.org for the Open Source Definition). Historically, most, but not all, Python releases have also been GPL-compatible; the table below summarizes the various releases. Release Derived from Year Owner GPL-compatible? (1) 0.9.0 thru 1.2 n/a 1991-1995 CWI yes 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes 1.6 1.5.2 2000 CNRI no 2.0 1.6 2000 BeOpen.com no 1.6.1 1.6 2001 CNRI yes (2) 2.1 2.0+1.6.1 2001 PSF no 2.0.1 2.0+1.6.1 2001 PSF yes 2.1.1 2.1+2.0.1 2001 PSF yes 2.1.2 2.1.1 2002 PSF yes 2.1.3 2.1.2 2002 PSF yes 2.2 and above 2.1.1 2001-now PSF yes Note GPL-compatible doesn’t mean that we’re distributing Python under the GPL. All Python licenses, unlike the GPL, let you distribute a modified version without making your changes open source. The GPL-compatible licenses make it possible to combine Python with other software that is released under the GPL; the others don’t. According to Richard Stallman, 1.6.1 is not GPL-compatible, because its license has a choice of law clause. According to CNRI, however, Stallman’s lawyer has told CNRI’s lawyer that 1.6.1 is “not incompatible” with the GPL. Thanks to the many outside volunteers who have worked under Guido’s direction to make these releases possible. Terms and conditions for accessing or otherwise using Python ¶ Python software and documentation are licensed under the Python Software Foundation License Version 2. Starting with Python 3.8.6, examples, recipes, and other code in the documentation are dual licensed under the PSF License Version 2 and the Zero-Clause BSD license . Some software incorporated into Python is under different licenses. The licenses are listed with code falling under that license. See Licenses and Acknowledgements for Incorporated Software for an incomplete list of these licenses. PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 ¶ 1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using this software ("Python") in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative version, provided, however, that PSF's License Agreement and PSF's notice of copyright, i.e., "Copyright © 2001 Python Software Foundation; All Rights Reserved" are retained in Python alone or in any derivative version prepared by Licensee. 3. In the event Licensee prepares a derivative work that is based on or incorporates Python or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python. 4. PSF is making Python available to Licensee on an "AS IS" basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between PSF and Licensee. This License Agreement does not grant permission to use PSF trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By copying, installing or otherwise using Python, Licensee agrees to be bound by the terms and conditions of this License Agreement. BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 ¶ BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the Individual or Organization ("Licensee") accessing and otherwise using this software in source or binary form and its associated documentation ("the Software"). 2. Subject to the terms and conditions of this BeOpen Python License Agreement, BeOpen hereby grants Licensee a non-exclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use the Software alone or in any derivative version, provided, however, that the BeOpen Python License is retained in the Software, alone or in any derivative version prepared by Licensee. 3. BeOpen is making the Software available to Licensee on an "AS IS" basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 5. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 6. This License Agreement shall be governed by and interpreted in all respects by the law of the State of California, excluding conflict of law provisions. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between BeOpen and Licensee. This License Agreement does not grant permission to use BeOpen trademarks or trade names in a trademark sense to endorse or promote products or services of Licensee, or any third party. As an exception, the "BeOpen Python" logos available at http://www.pythonlabs.com/logos.html may be used according to the permissions granted on that web page. 7. By copying, installing or otherwise using the software, Licensee agrees to be bound by the terms and conditions of this License Agreement. CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 ¶ 1. This LICENSE AGREEMENT is between the Corporation for National Research Initiatives, having an office at 1895 Preston White Drive, Reston, VA 20191 ("CNRI"), and the Individual or Organization ("Licensee") accessing and otherwise using Python 1.6.1 software in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, CNRI hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python 1.6.1 alone or in any derivative version, provided, however, that CNRI's License Agreement and CNRI's notice of copyright, i.e., "Copyright © 1995-2001 Corporation for National Research Initiatives; All Rights Reserved" are retained in Python 1.6.1 alone or in any derivative version prepared by Licensee. Alternately, in lieu of CNRI's License Agreement, Licensee may substitute the following text (omitting the quotes): "Python 1.6.1 is made available subject to the terms and conditions in CNRI's License Agreement. This Agreement together with Python 1.6.1 may be located on the internet using the following unique, persistent identifier (known as a handle): 1895.22/1013. This Agreement may also be obtained from a proxy server on the internet using the following URL: http://hdl.handle.net/1895.22/1013". 3. In the event Licensee prepares a derivative work that is based on or incorporates Python 1.6.1 or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python 1.6.1. 4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. This License Agreement shall be governed by the federal intellectual property law of the United States, including without limitation the federal copyright law, and, to the extent such U.S. federal law does not apply, by the law of the Commonwealth of Virginia, excluding Virginia's conflict of law provisions. Notwithstanding the foregoing, with regard to derivative works based on Python 1.6.1 that incorporate non-separable material that was previously distributed under the GNU General Public License (GPL), the law of the Commonwealth of Virginia shall govern this License Agreement only as to issues arising under or with respect to Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between CNRI and Licensee. This License Agreement does not grant permission to use CNRI trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By clicking on the "ACCEPT" button where indicated, or by copying, installing or otherwise using Python 1.6.1, Licensee agrees to be bound by the terms and conditions of this License Agreement. CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ¶ Copyright © 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION ¶ Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Licenses and Acknowledgements for Incorporated Software ¶ This section is an incomplete, but growing list of licenses and acknowledgements for third-party software incorporated in the Python distribution. Mersenne Twister ¶ The _random C extension underlying the random module includes code based on a download from http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/MT2002/emt19937ar.html . The following are the verbatim comments from the original code: A C-program for MT19937, with initialization improved 2002/1/26. Coded by Takuji Nishimura and Makoto Matsumoto. Before using, initialize the state by using init_genrand(seed) or init_by_array(init_key, key_length). Copyright (C) 1997 - 2002, Makoto Matsumoto and Takuji Nishimura, All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The names of its contributors may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Any feedback is very welcome. http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html email: m-mat @ math.sci.hiroshima-u.ac.jp (remove space) Sockets ¶ The socket module uses the functions, getaddrinfo() , and getnameinfo() , which are coded in separate source files from the WIDE Project, https://www.wide.ad.jp/ . Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Asynchronous socket services ¶ The test.support.asynchat and test.support.asyncore modules contain the following notice: Copyright 1996 by Sam Rushing All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Sam Rushing not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Cookie management ¶ The http.cookies module contains the following notice: Copyright 2000 by Timothy O'Malley <timo@alum.mit.edu> All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Timothy O'Malley not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Timothy O'Malley DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL Timothy O'Malley BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Execution tracing ¶ The trace module contains the following notice: portions copyright 2001, Autonomous Zones Industries, Inc., all rights... err... reserved and offered to the public under the terms of the Python 2.2 license. Author: Zooko O'Whielacronx http://zooko.com/ mailto:zooko@zooko.com Copyright 2000, Mojam Media, Inc., all rights reserved. Author: Skip Montanaro Copyright 1999, Bioreason, Inc., all rights reserved. Author: Andrew Dalke Copyright 1995-1997, Automatrix, Inc., all rights reserved. Author: Skip Montanaro Copyright 1991-1995, Stichting Mathematisch Centrum, all rights reserved. Permission to use, copy, modify, and distribute this Python software and its associated documentation for any purpose without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of neither Automatrix, Bioreason or Mojam Media be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. UUencode and UUdecode functions ¶ The uu codec contains the following notice: Copyright 1994 by Lance Ellinghouse Cathedral City, California Republic, United States of America. All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Lance Ellinghouse not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Modified by Jack Jansen, CWI, July 1995: - Use binascii module to do the actual line-by-line conversion between ascii and binary. This results in a 1000-fold speedup. The C version is still 5 times faster, though. - Arguments more compliant with Python standard XML Remote Procedure Calls ¶ The xmlrpc.client module contains the following notice: The XML-RPC client interface is Copyright (c) 1999-2002 by Secret Labs AB Copyright (c) 1999-2002 by Fredrik Lundh By obtaining, using, and/or copying this software and/or its associated documentation, you agree that you have read, understood, and will comply with the following terms and conditions: Permission to use, copy, modify, and distribute this software and its associated documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Secret Labs AB or the author not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT- ABILITY AND FITNESS. IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. test_epoll ¶ The test.test_epoll module contains the following notice: Copyright (c) 2001-2006 Twisted Matrix Laboratories. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Select kqueue ¶ The select module contains the following notice for the kqueue interface: Copyright (c) 2000 Doug White, 2006 James Knight, 2007 Christian Heimes All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SipHash24 ¶ The file Python/pyhash.c contains Marek Majkowski’ implementation of Dan Bernstein’s SipHash24 algorithm. It contains the following note: <MIT License> Copyright (c) 2013 Marek Majkowski <marek@popcount.org> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. </MIT License> Original location: https://github.com/majek/csiphash/ Solution inspired by code from: Samuel Neves (supercop/crypto_auth/siphash24/little) djb (supercop/crypto_auth/siphash24/little2) Jean-Philippe Aumasson (https://131002.net/siphash/siphash24.c) strtod and dtoa ¶ The file Python/dtoa.c , which supplies C functions dtoa and strtod for conversion of C doubles to and from strings, is derived from the file of the same name by David M. Gay, currently available from https://web.archive.org/web/20220517033456/http://www.netlib.org/fp/dtoa.c . The original file, as retrieved on March 16, 2009, contains the following copyright and licensing notice: /**************************************************************** * * The author of this software is David M. Gay. * * Copyright (c) 1991, 2000, 2001 by Lucent Technologies. * * Permission to use, copy, modify, and distribute this software for any * purpose without fee is hereby granted, provided that this entire notice * is included in all copies of any software which is or includes a copy * or modification of this software and in all copies of the supporting * documentation for such software. * * THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED * WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY * REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY * OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. * ***************************************************************/ OpenSSL ¶ The modules hashlib , posix and ssl use the OpenSSL library for added performance if made available by the operating system. Additionally, the Windows and macOS installers for Python may include a copy of the OpenSSL libraries, so we include a copy of the OpenSSL license here. For the OpenSSL 3.0 release, and later releases derived from that, the Apache License v2 applies: Apache License Version 2.0, January 2004 https://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS expat ¶ The pyexpat extension is built using an included copy of the expat sources unless the build is configured --with-system-expat : Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. libffi ¶ The _ctypes C extension underlying the ctypes module is built using an included copy of the libffi sources unless the build is configured --with-system-libffi : Copyright (c) 1996-2008 Red Hat, Inc and others. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. zlib ¶ The zlib extension is built using an included copy of the zlib sources if the zlib version found on the system is too old to be used for the build: Copyright (C) 1995-2011 Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly Mark Adler jloup@gzip.org madler@alumni.caltech.edu cfuhash ¶ The implementation of the hash table used by the tracemalloc is based on the cfuhash project: Copyright (c) 2005 Don Owens All rights reserved. This code is released under the BSD license: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. libmpdec ¶ The _decimal C extension underlying the decimal module is built using an included copy of the libmpdec library unless the build is configured --with-system-libmpdec : Copyright (c) 2008-2020 Stefan Krah. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. W3C C14N test suite ¶ The C14N 2.0 test suite in the test package ( Lib/test/xmltestdata/c14n-20/ ) was retrieved from the W3C website at https://www.w3.org/TR/xml-c14n2-testcases/ and is distributed under the 3-clause BSD license: Copyright (c) 2013 W3C(R) (MIT, ERCIM, Keio, Beihang), All Rights Reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of works must retain the original copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the original copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the W3C nor the names of its contributors may be used to endorse or promote products derived from this work without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. mimalloc ¶ MIT License: Copyright (c) 2018-2021 Microsoft Corporation, Daan Leijen Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. asyncio ¶ Parts of the asyncio module are incorporated from uvloop 0.16 , which is distributed under the MIT license: Copyright (c) 2015-2021 MagicStack Inc. http://magic.io Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Global Unbounded Sequences (GUS) ¶ The file Python/qsbr.c is adapted from FreeBSD’s “Global Unbounded Sequences” safe memory reclamation scheme in subr_smr.c . The file is distributed under the 2-Clause BSD License: Copyright (c) 2019,2020 Jeffrey Roberson <jeff@FreeBSD.org> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following con | 2026-01-13T08:49:06 |
https://future.forem.com/privacy#d-other-purposes | Privacy Policy - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:06 |
https://www.python.org/downloads/release/pymanager-252/ | Python Release Python install manager 25.2 | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Notice: Your browser is ancient . Please upgrade to a different browser to experience a better web. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python install manager 25.2 Release date: Dec. 5, 2025 The Python install manager for Windows is our tool for installing and managing runtimes. The traditional executable installer will stop being released with Python 3.16 As well as the files below, the Python install manager can be installed using the Microsoft Store app . For most users, this is the recommended approach. To install using WinGet, the command is winget install 9NQ7512CXL7T . Full documentation for the Python install manager is available in our documentation . In particular, there are troubleshooting guides, as well as instructions around administrative installs, including intended use of the legacy MSI installer. Use of the Store app or the MSIX package is recommended. The install manager can install versions of Python as far back as 3.5, but only supports Windows 10 operating systems (or Windows Server 2022) and later. Use py list --online to see all available packages, including the embeddable distro, experimental free-threaded builds, and packages including the standard library test suite and debug symbols. We recommend uninstalling the Python launcher from previous installs when installing the Python install manager, as both use the py command. After installing the install manager, the first launch should run a configuration checker, which can also be manually launched with py install --configure or pymanager install --configure . Removing the install manager will not remove any installs, but the py uninstall --purge command will perform a full cleanup. The Python install manager will automatically update within a day of an update being released. Once installed, you should not need to download the install manager again. Please provide all feedback as issues on our GitHub repository at github.com/python/pymanager . Files Windows Download Installer (MSIX) Version Operating System Description MD5 Checksum SHA256 Checksum File Size Installer (MSIX) Windows Bundles Python 3.14.2 E10D069121AF8F0BB8F66C63EE4E2766 n/a 43.9 MB MSI package Windows See documentation before use A67D5338A56904698AC205C3D84BDC9A n/a 9.4 MB ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://dev.to/dorahacks/dorahacks-start-up-ideas-2026-pt1-digital-finance-in-the-circlearc-ecosystem-98m | DoraHacks Start-up Ideas 2026: Pt.1 Digital Finance in the Circle/Arc ecosystem - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse DoraHacks Posted on Jan 13 DoraHacks Start-up Ideas 2026: Pt.1 Digital Finance in the Circle/Arc ecosystem # cryptocurrency # startup # web3 By Steve Ngok, Chief Strategy Officer, DoraHacks The Introduction For nearly a decade, the established financial order has viewed crypto with skepticism and disdain. To observers in ivory towers, the industry appeared as little more than a casino—a chaotic theater of speculation divorced from the real economy. For a long time, this criticism had merit. But surveying the landscape of 2026, the early confusion has given way to structural clarity. The industry hasn't merely grown; it has bifurcated. We are witnessing a decisive schism. On one side lies continued speculation: prediction markets, exchanges, volatility optimization. This remains a vibrant, if noisy, arena. But distinct from this, a more sober reality has emerged. Stablecoins have become the TCP/IP of money. They are eating cross-border payments, devouring FX inefficiencies, and enabling entirely new economic primitives for AI agents. In this landscape, early DeFi's "move fast and break things" mantra has been replaced by demands for determinism, compliance, and institutional scale. This is why the Circle and Arc ecosystem has emerged as the dominant stack. They didn't just build a blockchain; they built an Economic Operating System . They did the hard, unglamorous work of regulatory integration and liquidity plumbing so you don't have to. If you're a founder in 2026, you don't need to reinvent the wheel. The rails are laid by DoraHacks and its partners. The regulatory moat is dug. The liquidity is deep. The question is no longer whether we can put real-world assets on-chain, but what happens when money becomes as programmable as bits. Here is where the alpha lies. Time to build for the future. Track I: The Global Capital Expressway From Simple Remittances to Programmable Settlement 1. The Core Thesis The traditional cross-border payment system is trapped in a structural trilemma: you can have speed, you can have low cost, or you can have regulatory transparency, but you rarely get all three. The current correspondent banking model is a relic of the analog age, ill-equipped for the velocity of the internet economy. The Circle and Arc ecosystem has finally solved this coordination problem: CPN (Circle Payments Network) solves the "Last Mile," connecting the digital ledger to the global banking system. CCTP & Gateway solve liquidity fragmentation, unifying assets across fragmented blockchains. Arc provides the "Matching and Clearing Engine": delivering the sub-second certainty and low latency that Wall Street demands. The Mission: To use Arc as the central clearing layer for global capital, building the next generation of commercial payment applications that render the SWIFT network obsolete. 2. The High-Value Opportunities We are looking beyond basic payroll or merchant checkout. The real opportunity lies in re-architecting B2B flows and platform economics. A. Programmable Trade Finance The Thesis: "Funds arrive the second the cargo does." The Problem: International trade runs on friction. Exporters wait 30–90 days for payment or rely on expensive, paper-heavy Letters of Credit. Trust is slow and costly. The Solution: Escrow: The importer locks USDC in a smart contract on Arc. Trigger: An Oracle feeds real-time logistics data (API) to the chain. "Cargo Signed" = "Payment Triggered." Settlement: The contract autonomously releases the USDC. Exit: CPN converts the USDC to local currency (e.g., Vietnamese Dong) and wires it to the exporter instantly. Why Arc? Only Arc’s sub-second finality and near-zero fees make it economically viable to trigger payments based on high-frequency logistics updates. The Builder Profile: Experts in supply chain ERP and logistics data. B. The Internal Treasury Engine The Thesis: "Stop burning millions on internal wires." The Problem: A multinational like Toyota or Siemens has subsidiaries in 50 countries. When Brazil owes Germany, and Germany owes the US, they send wires back and forth, bleeding money on FX fees and float. The Solution: On-Chain Pooling: Subsidiaries convert local cash to USDC via CPN and pool it in a central Arc Treasury. Netting: A "Netting Algorithm" runs on Arc, calculating exactly who owes what to whom on a ledger. Settlement: You only move the difference . Off-Ramp: Subsidiaries pull liquidity back to local fiat only when needed. Why Arc? Privacy tooling protects internal financial data, while high throughput handles the complex math of real-time netting. The Builder Profile: Fintech architects and Enterprise SaaS founders. C. The "Web3 Stripe Connect" The Thesis: "A universal payout router for the gig economy." The Problem: Platforms like Uber, Airbnb, or Upwork struggle to pay a global workforce. Sending $50 to a freelancer in the Philippines is often too expensive to justify. The Solution: Aggregate: The platform loads a single pool of USDC onto Arc. Distribute: One API call triggers thousands of payouts. Route: The smart contract acts as a router. Crypto-native user? Send to wallet. Traditional user? Route through CPN to their local bank. Why Arc? Batch processing capabilities allow for "micropayments" that are mathematically impossible on legacy rails. The Builder Profile: Payment gateway engineers and platform aggregators. D. The Programmable Corporate Card The Thesis: "Give your AI agent a credit card, but control the spending with code." The Problem: Companies need to buy software globally, but corporate cards are dumb. They lack granular control, and you can't easily give one to an AI agent or a temporary contractor. The Solution: The Pool: A corporate USDC treasury on Arc. The Card: Instantly issue virtual Visa/Mastercard credentials via CPN. The Rules: Embed logic in the smart contract: "This card only works for AWS," or "Max spend $100/day." The Settlement: Transactions are settled instantly on-chain via StableFX. Why Arc? It moves financial control from the bank's policy department to the company's code repository. The Builder Profile: Expense management and B2B fintech teams. 3. The Technical Blueprint For the developer, the architecture is now standardized. Here is how you build it: Step 1: On-Ramp. Use the CPN API to generate Virtual IBANs. Fiat flows in; USDC is automatically minted to an Arc address. Step 2: Liquidity. Use the Gateway SDK to sweep USDC from fragmented chains (Ethereum, Solana) into your central Arc application. Step 3: Business Logic. Deploy your Solidity contracts on Arc. Payroll: distributeSalary(recipients, amounts) Trade: releaseFunds(proofOfShipping) Step 4: Off-Ramp. Call the CPN Payout API to burn USDC and trigger a local bank wire, or use Programmable Wallets to settle directly on-chain. 4. The Conclusion "Build a bank that runs on code." Understand your competition: You are competing against the friction of the 1970s banking system. By combining the speed of Arc with the reach of CPN, you have the power to reduce global settlement costs by 80% and accelerate speed from "T+2 Days" to "T+0 Seconds." This is an entry ticket to a multi-trillion dollar market. Track II: The On-Chain FX Revolution From Manual Conversion to Algorithmic Liquidity Networks 1. The Core Thesis The traditional Foreign Exchange (FX) market, the largest financial market in the world, is currently held back by an antiquated triad of inefficiencies: Settlement Latency (the T+2 day standard), Gatekeeping (only giants get the best rates), and Opacity (layers of hidden fees). The combination of Circle and Arc dismantles this structure: StableFX provides an institutional-grade price feed (RFQ mechanism), meaning "Inquiry equals Execution." Partner Stablecoins (e.g., MXNB, JPYC, BRLA) provide the necessary local currency anchors. Arc provides the execution environment where these currencies can be swapped in mere milliseconds. The Mission: To utilize code to autonomously manage currency risk and eliminate the friction of exchange from cross-border commerce. 2. The High-Value Opportunities We are looking beyond simple hedging or remittance apps. The real opportunity lies in deep financial engineering applied to global trade. A. The Autonomous Multi-Currency Treasury The Thesis: "Democratizing Apple’s treasury capabilities for the SME." The Problem: A mid-sized cross-border e-commerce firm earns in Euros (EUR), pays server costs in Dollars (USD), and pays salaries in Yen (JPY). Traditional banking charges exorbitant spreads for these conversions, and finance teams often miss optimal windows due to manual processing. The Solution: Automated Strategy: The enterprise sets rules on Arc: "If EURC balance > 50,000 and EUR/USD rate > 1.08, automatically swap 50% to USDC." Instant Execution: Smart contracts monitor StableFX quotes via Oracle and execute immediately when conditions are met. Payroll: At month's end, USDC is automatically converted to JPYC at the best market rate and distributed to employee wallets. Why Arc? Only Arc supports this high-frequency monitoring and low-cost execution. Traditional banks cannot offer this level of programmability. The Builder Profile: Enterprise financial SaaS teams and ERP integrators. B. The "1inch" for FX The Thesis: "Best execution, globally and instantly." The Problem: When converting USDC to EURC, prices vary between Uniswap, StableFX, and Curve. The user rarely knows where the best liquidity lies. The Solution: Aggregation: Build a dApp on Arc that connects StableFX (RFQ mode) with on-chain AMMs. Routing: When a user wants to swap $1M, the algorithm splits the order: 60% via StableFX (for depth) and 40% via AMM. Atomic Settlement: The user clicks once. The complexity is abstracted. Why Arc? Its high performance allows for the querying of multiple liquidity sources and trade execution within a single block. The Builder Profile: DeFi developers and Market Makers. C. The Tokenized Carry Trade Protocol The Thesis: "bringing Wall Street’s oldest strategy to DeFi rails." The Problem: The Carry Trade, borrowing in a low-interest currency to invest in a high-interest one, has historically been the exclusive preserve of hedge funds and banks. The Solution: The Mechanism: A user deposits USDC. The Operation: The protocol borrows a low-rate currency (e.g., JPYC) in the background, swaps it via StableFX, and invests in a high-yield asset (e.g., Tokenized T-Bills). Risk Management: Utilizing Arc’s automation, the system executes millisecond-level liquidation if exchange rates hit a volatility threshold. Why Arc? This strategy requires extreme speed. Arc’s Deterministic Finality is the critical safeguard against liquidation failure. The Builder Profile: Quantitative trading teams and advanced DeFi architects. D. The "Local-First" Checkout The Thesis: "Pay in Pesos, Settle in Dollars. Zero Friction." The Problem: A US-based Shopify merchant wants USDC, but their Mexican customer wants to pay in Pesos (MXN). Current credit card rails charge 3-5% in FX fees for this privilege. The Solution: Frontend: The buyer sees the price in MXNB (Mexican Peso Stablecoin). Payment: The buyer pays MXNB. Backend: The transaction hits Arc, instantly swaps MXNB to USDC via StableFX. Settlement: The merchant receives USDC. No banks involved. Total fees < 1%. Why Arc? Instant confirmation makes the checkout experience silky smooth, no "waiting for block confirmations." The Builder Profile: Payment gateway developers and e-commerce infrastructure teams. 3. The Technical Blueprint For the developer, the integration path is clear: Step 1: Pricing. Integrate the StableFX API (Oracle) . This is a stream of executable quotes. Step 2: Assets. Ensure your smart contracts are compatible with ERC-20 standards for USDC, EURC, and Partner Stablecoins (JPYC, MXNB). Step 3: Execution. Build a swapCurrency(tokenIn, tokenOut, amount, minRate) function. Inside, call the StableFX settlement contract, passing the signed RFQ quote to finalize the atomic swap. Step 4: Interoperability (Optional). Use the xReserve pattern. If your strategy requires assets from the Bitcoin network, wrap them into the Arc ecosystem via xReserve to access FX liquidity. 4. The Conclusion "Forex is the biggest market in the world, and it is still running on 1980s technology." In this track, you are re-plumbing the vascular system of global trade. By leveraging StableFX and Arc, you have the opportunity to build the next generation of foreign exchange applications: 24/7 operation, T+0 settlement, and zero banking fees. This is the Crown Jewel of Fintech. Track III: The Silicon Economy From Human-Computer Interaction to Machine-to-Machine Commerce 1. The Core Thesis The current generation of Artificial Intelligence is defined by a structural paradox: infinite intelligence, yet zero financial agency. An AI Agent can plan a complex itinerary for a trip to Tokyo, but it is powerless to book the flight. It can write the code for a server, but it cannot rent the hardware. It is a brain in a jar, brilliant, but severed from the physical economy. The Circle and Arc ecosystem provides the missing limb: Circle Programmable Wallets grant each Agent a unique, policy-controlled on-chain identity. The x402 Protocol serves as the universal "negotiation language" for value (restoring the "Payment Required" status to the web). Gas Station resolves the UX friction, abstracting away the complexity of ETH and Gas so that payment feels like a simple API call. Arc provides the high-concurrency, deterministic environment required for machine-speed transactions. The Mission: To construct the infrastructure and applications that allow AI to autonomously earn, spend, and manage assets. To grant economic sovereignty to the machine. 2. The High-Value Opportunities We are looking beyond simple "crypto-browsers." We are looking for the fundamental rails of a machine-native GDP. A. The API Negotiator The Thesis: "The death of the monthly subscription; the birth of real-time bidding." The Problem: Developers are currently forced to manually subscribe to dozens of APIs (OpenAI, Twilio, SerpApi), managing a chaotic ring of keys and credit card limits. The Solution: Dynamic Gateway: Service providers publish APIs on Arc with dynamic, load-based pricing. The Agent: Before calling data, the user’s AI Agent queries via x402: "Price check?" The Settlement: The provider responds: "0.002 USDC." The Agent verifies its budget and executes the payment instantly. Pay-As-You-Go: No subscriptions. No breakage. Millisecond settlement. Why Arc? High-frequency micropayments are economically impossible on legacy rails. On Arc, they are the standard. The Builder Profile: API aggregators and developer tool architects. B. The "Pay-per-Context" Gateway The Thesis: "Solving the 'New York Times vs. OpenAI' legal deadlock." The Problem: Large Language Models (LLMs) need fresh data, but publishers are blocking scrapers because they aren't getting paid. The legal system is gridlocked. The Solution: Compliance: Publishers deploy x402 headers on their content. Micro-Access: When an AI scraper visits, it doesn't hit a paywall; it autonomously pays 0.01 USDC to the publisher's Arc wallet for the legal right to ingest that specific article. Revenue Flow: Capital flows instantly to creators and platforms, creating a sustainable "AI-Media" ecology. Why Arc? The negligible transaction fees make the $0.01 economy viable. The Builder Profile: Media-tech firms and Web3 browser plugin developers. C. The "Budgeted Butler" Protocol The Thesis: "Trust through code, not faith." The Problem: You want your AI to buy your coffee and book your flights, but you will never give a hallucinating chatbot your credit card. The Solution: Scoped Permissions: Leverage the "Policy Engine" of Circle Programmable Wallets. The Rules: Issue the AI a sub-wallet with strict on-chain logic: "Max spend 50 USDC/day," "Transfer only to whitelisted addresses (Starbucks, Uber)," "Transactions > $100 require human biometric approval." Autonomy: Inside these guardrails, the AI operates with total freedom. Why Arc? On-chain policy execution is transparent and immutable, offering a flexibility that traditional bank risk models cannot match. The Builder Profile: Smart home hubs and Personal Assistant App developers. D. Flash Bounties for RLHF The Thesis: "The Reverse Turing Test." The Problem: AI still gets stuck. It fails to read a blurred CAPTCHA or misunderstands the nuance of sarcasm. The Solution: The Request: The AI Agent encapsulates the difficult task into a "Micro-Bounty" and broadcasts it to Arc with a 0.5 USDC reward. The Human: A "micro-worker" anywhere in the world taps the notification, solves the CAPTCHA, or labels the data. The Payment: The AI verifies the input and releases funds instantly. Why Arc? This creates a global, frictionless labor market settled in USDC. The Builder Profile: Data labeling platforms and crowdsourcing networks. 3. The Technical Blueprint For the engineer, the assembly instructions for a Silicon Economic Entity are as follows: Step 1: Identity. Use the Circle Programmable Wallets API to instantiate a Smart Contract Account (SCA) for the AI. Critical: Configure Spending Policies (e.g., maxAmountPerDay = 10 USDC). Step 2: Protocol. Integrate the x402 (HTTP 402) standard. When the AI makes a request, the server returns 402 Payment Required along with a destination address and amount. The AI parses this and signs the transaction. Step 3: Gas. Configure Gas Station and Paymaster . The AI holds only USDC. The Paymaster abstracts the gas fees in the background, ensuring the AI's logic loop is never broken by a lack of native tokens. Step 4: Logic. Deploy verification contracts on Arc. Ensure that successful payment triggers an Oracle or Event Listener to release the API key or service access off-chain. 4. The Conclusion "Give your AI a wallet, not just a prompt." Right now, your AI is like a genius locked in a library: it knows everything, but it can affect nothing in the physical world. By combining the speed of Arc with the identity layer of Circle Wallets, you are handing that genius a key. You are architecting the GDP of the Machine Economy. Track IV: Economic Leapfrog & Inclusion From "Waiting for Aid" to "Accessing the Global Grid" 1. The Core Thesis Traditional financial inclusion has failed not because of malice, but because of math. The unit economics of the legacy banking system are broken: the Customer Acquisition Cost (CAC) and service overhead for a user in a developing market far exceed the profit generated by their deposits. Banks simply cannot afford to open an account for $50. The Circle and Arc ecosystem fundamentally alters this equation: Arc's Negligible Gas Fees make a $1 transfer economically rational, not just charitable. Circle User-Controlled Wallets resolve the "Key Management" barrier, replacing terrifying seed phrases with familiar social logins and passkeys. USDC solves the "Volatility" problem, protecting the vulnerable from local currency inflation. The Mission: To build the "Leapfrog Stack", minimalist, anti-inflationary, and disintermediated financial tools that serve the bottom 50% of the global population. 2. The High-Value Opportunities We are talking about sustainable, scalable business models for the next billion users. A. Reputation-Based Micro-Lending The Thesis: "Digitizing the social capital of the village to access global liquidity." The Problem: A fruit vendor in Kenya needs $100 for inventory. She has no credit score, so she is forced into predatory loans. Meanwhile, DeFi protocols sit on billions of dollars of idle capital that cannot be deployed without over-collateralization. The Solution: ROSCA 2.0: Move the traditional "rotating savings and credit association" onto Arc. The SBT: If a member repays on time, this behavior is minted as a Soulbound Token (SBT), a digital credit score. The Bridge: High-reputation ROSCA groups are bundled together to borrow from global DeFi pools at competitive rates (e.g., 10%), bypassing local loan sharks (100%+). Why Arc? Only Arc can handle the high volume of micro-repayment data while providing the transparent audit trail required by global lenders. The Builder Profile: Emerging market Fintech founders and DeFi protocol architects. B. Pay-As-You-Go Asset Networks The Thesis: "Streaming money for streaming utility." The Problem: A low-income family cannot afford the upfront cost of a solar panel or a motorbike, despite having a steady cash flow to pay for it over time. The Solution: IoT + Blockchain: Connect the physical asset (solar panel) to an internet controller. Micro-Unlocking: The user pays 0.50 USDC via their Arc wallet. Smart Contract Logic: Payment confirmed -> Signal sent -> Device unlocks for 24 hours. Ownership: If payment stops, the device locks. Once the total principal is paid, an NFT represents full ownership transfer. Why Arc? The friction of traditional payments makes daily micropayments impossible. Arc makes them trivial. The Builder Profile: IoT hardware hackers and ReFi (Regenerative Finance) entrepreneurs. C. The Programmable Aid Protocol The Thesis: "Ensuring donor funds buy medicine, not alcohol." The Problem: Humanitarian aid is plagued by two cancers: intermediary corruption (skimming off the top) and misuse of funds at the bottom. The Solution: Restricted Assets: Issue a "Wrapped USDC" on Arc specifically for aid. Allow-Listing: Code the token so it can only be transferred to whitelisted wallets (verified pharmacies, schools, grocery stores). Auto-Redemption: Vendors who receive the token can swap it 1:1 for liquid USDC instantly. Privacy: Use Zero-Knowledge proofs so the public sees the flow of funds to valid categories, without exposing the identity of the refugee. Why Arc? Programmable Money is the ultimate solution to the Principal-Agent problem in charity. The Builder Profile: GovTech developers and NGO technical partners. D. Direct-to-Biller Remittances The Thesis: "Don't send cash; settle the bill." The Problem: A migrant worker sends money home for school fees. The cash is received, but due to urgent needs or lack of discipline, it is spent on other things. The sender wants control over the allocation of capital. The Solution: Aggregation: The platform integrates with utility and education providers in the destination country. Direct Payment: The sender in the US pays USDC in the app. Settlement: Arc settles the transaction in the background, converting via CPN to local fiat and paying the electric company directly. Certainty: The sender receives an instant digital receipt: "Bill Paid." Why Arc? It acts as a global settlement layer that bypasses the slow, opaque correspondent banking chain. The Builder Profile: Cross-border payment startups and Digital Nomad service providers. 3. The Technical Blueprint In this track, User Experience (UX) is survival. Your users have low-end devices and spotty internet. Step 1: The Invisible Wallet. Use Circle User-Controlled Wallets with PIN or Biometric recovery. If you ask a user to write down 12 words, you have already lost. Step 2: Gas Sponsorship. You must configure a Gas Station . The user should know they received "10 Dollars," not that they need "Arc Token" for gas. Abstract the blockchain away completely. Step 3: The Lite Stack. Build Progressive Web Apps (PWAs) or Telegram Mini Apps. The binary must be small; the interface must be fast. Step 4: Offline Tolerance. Design for latency. Allow users to sign transactions offline and broadcast them when the network reconnects. 4. The Conclusion "Technology has no conscience, but builders do." On Wall Street, being 1 millisecond faster might mean an extra million dollars in profit. But in the developing world, saving $1 in fees and moving money instantly means a family eats dinner tonight. This track is about using code to eliminate the "Poverty Premium." By leveraging the power of Arc and Circle, you are building a ladder to economic freedom. The Conclusion The Time to Build is Now History doesn't repeat but it rhymes. In the late 90s, we laid fiber optic cables that allowed the internet to scale. In the 2000s, Stripe and PayPal built the logic layer that enabled e-commerce to explode. Today, we're at a similar inflection point for the financial internet. The opportunities outlined above - Borderless Payment Rails, Programmable FX, The Machine Economy, and Financial Inclusion - are not theoretical science projects. They are immediate, addressable markets worth trillions of dollars. The legacy banking system's friction - 3-day settlement times, predatory remittance fees, walled gardens - is an anomaly that technology is now correcting. Circle and Arc have provided the "AWS" for this financial revolution : scalable, compliant, and ready for deployment. Infrastructure risk has been removed. What remains is execution risk. We are looking for founders who aren't interested in launching the next meme coin, but who are obsessed with unbundling the bank, rewiring global trade, and giving AI agents their own economic sovereignty. The Economic OS is open. The API is live. It's time to build. About DoraHacks DoraHacks is the leading global hackathon community and open source developer incentive platform. DoraHacks provides toolkits for anyone to organize hackathons and fund early-stage ecosystem startups. DoraHacks creates a global hacker movement in Web3, AI, Quantum Computing and Space Tech. So far, more than 30,000 startup teams from the DoraHacks community have received over $300M in funding, and a large number of open source communities, companies and tech ecosystems are actively using DoraHacks together with its BUIDL AI capabilities for organizing hackathons and funding open source initiatives. Website ｜ Twitter ｜ Discord ｜ Telegram ｜ Binance Live ｜ Youtube Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse DoraHacks Follow Contribute to crypto/web3, AI, quantum computing, space and other frontier technologies through hackathons with DoraHacks. https://dorahacks.io/ Joined Nov 26, 2025 More from DoraHacks DoraHacks Must-attend Hackathons 2025 December # hackathon # web3 # blockchain 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/t/beginners/page/6#for-questions | Beginners Page 6 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Beginners Follow Hide "A journey of a thousand miles begins with a single step." -Chinese Proverb Create Post submission guidelines UPDATED AUGUST 2, 2019 This tag is dedicated to beginners to programming, development, networking, or to a particular language. Everything should be geared towards that! For Questions... Consider using this tag along with #help, if... You are new to a language, or to programming in general, You want an explanation with NO prerequisite knowledge required. You want insight from more experienced developers. Please do not use this tag if you are merely new to a tool, library, or framework. See also, #explainlikeimfive For Articles... Posts should be specifically geared towards true beginners (experience level 0-2 out of 10). Posts should require NO prerequisite knowledge, except perhaps general (language-agnostic) essentials of programming. Posts should NOT merely be for beginners to a tool, library, or framework. If your article does not meet these qualifications, please select a different tag. Promotional Rules Posts should NOT primarily promote an external work. This is what Listings is for. Otherwise accepable posts MAY include a brief (1-2 sentence) plug for another resource at the bottom. Resource lists ARE acceptable if they follow these rules: Include at least 3 distinct authors/creators. Clearly indicate which resources are FREE, which require PII, and which cost money. Do not use personal affiliate links to monetize. Indicate at the top that the article contains promotional links. about #beginners If you're writing for this tag, we recommend you read this article . If you're asking a question, read this article . Older #beginners posts 3 4 5 6 7 8 9 10 11 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Headless Mode: Unleash AI in Your CI/CD Pipeline Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 11 Headless Mode: Unleash AI in Your CI/CD Pipeline # tutorial # claudecode # productivity # beginners 1 reaction Comments Add Comment 4 min read New Python Courseware for Early-Career CS Students Jesse Casman Jesse Casman Jesse Casman Follow Jan 8 New Python Courseware for Early-Career CS Students # python # ai # career # beginners Comments Add Comment 3 min read Day 10 of 100 Palak Hirave Palak Hirave Palak Hirave Follow Jan 10 Day 10 of 100 # programming # python # devjournal # beginners Comments Add Comment 1 min read From Math Teacher to Data Science & Web Development: My Coding Journey#introduction #learning #webdev #python #datascience Ahmed Anter Elsayed Ahmed Anter Elsayed Ahmed Anter Elsayed Follow Jan 11 From Math Teacher to Data Science & Web Development: My Coding Journey#introduction #learning #webdev #python #datascience # beginners # webdev # datascience # career Comments 3 comments 2 min read In-place Modification Jayaprasanna Roddam Jayaprasanna Roddam Jayaprasanna Roddam Follow Jan 9 In-place Modification # programming # beginners # tutorial # datastructures Comments Add Comment 2 min read Java Basics: Variables and Data Types Explained for Beginners Kesavarthini Kesavarthini Kesavarthini Follow Jan 10 Java Basics: Variables and Data Types Explained for Beginners # java # beginners # learning # programming Comments Add Comment 2 min read Two Pointers (Opposite Ends) Jayaprasanna Roddam Jayaprasanna Roddam Jayaprasanna Roddam Follow Jan 9 Two Pointers (Opposite Ends) # programming # beginners # tutorial # career Comments Add Comment 2 min read # Welcome to React World: Grasp the Fundamentals and Mental Model! (React Day 1) Vasu Ghanta Vasu Ghanta Vasu Ghanta Follow Jan 9 # Welcome to React World: Grasp the Fundamentals and Mental Model! (React Day 1) # beginners # javascript # react # tutorial Comments Add Comment 5 min read The Java Developer's Roadmap for 2026: From First Program to Production-Ready Professional dbc2201 dbc2201 dbc2201 Follow Jan 9 The Java Developer's Roadmap for 2026: From First Program to Production-Ready Professional # beginners # career # java # tutorial Comments Add Comment 23 min read Prefix Sum Jayaprasanna Roddam Jayaprasanna Roddam Jayaprasanna Roddam Follow Jan 9 Prefix Sum # programming # beginners # tutorial # python Comments Add Comment 2 min read Build a Screen Capture & Scopes Tool with Python, Tkinter, and MSS Mate Technologies Mate Technologies Mate Technologies Follow Jan 9 Build a Screen Capture & Scopes Tool with Python, Tkinter, and MSS # python # tkinter # beginners # opensource Comments Add Comment 4 min read Sliding Window (Variable Size) Jayaprasanna Roddam Jayaprasanna Roddam Jayaprasanna Roddam Follow Jan 9 Sliding Window (Variable Size) # programming # beginners # tutorial # python Comments Add Comment 3 min read I Built a Gesture Controlled Fluid Simulation (And Accidentally Fought GitHub) TROJAN TROJAN TROJAN Follow Jan 10 I Built a Gesture Controlled Fluid Simulation (And Accidentally Fought GitHub) # discuss # programming # ai # beginners 8 reactions Comments 3 comments 2 min read Hash Map Frequency Counting Jayaprasanna Roddam Jayaprasanna Roddam Jayaprasanna Roddam Follow Jan 9 Hash Map Frequency Counting # programming # beginners # tutorial # datastructures Comments Add Comment 2 min read I build a small website to challenge people's CSS skill! AnsonRE AnsonRE AnsonRE Follow Jan 9 I build a small website to challenge people's CSS skill! # challenge # beginners # css # showdev Comments Add Comment 1 min read How Overusing Redis Almost Killed Our Project at Scale Saif Ullah Usmani Saif Ullah Usmani Saif Ullah Usmani Follow Jan 9 How Overusing Redis Almost Killed Our Project at Scale # webdev # devops # softwareengineering # beginners Comments Add Comment 2 min read JAVA INTERNALS: JDK, JRE, JVM, and JIT! Anees Abdul Anees Abdul Anees Abdul Follow Jan 9 JAVA INTERNALS: JDK, JRE, JVM, and JIT! # beginners # java # tutorial Comments Add Comment 2 min read The TypeScript Features I Wish I'd Learned Sooner Tarun Moorjani Tarun Moorjani Tarun Moorjani Follow Jan 8 The TypeScript Features I Wish I'd Learned Sooner # discuss # typescript # beginners # webdev Comments Add Comment 9 min read Las 5 Estructuras de Datos que Dominarán tu Próxima Entrevista Técnica Grego Grego Grego Follow Jan 8 Las 5 Estructuras de Datos que Dominarán tu Próxima Entrevista Técnica # datastructures # interview # beginners # spanish Comments Add Comment 5 min read Fast & Slow Pointers (Cycle Detection) Jayaprasanna Roddam Jayaprasanna Roddam Jayaprasanna Roddam Follow Jan 9 Fast & Slow Pointers (Cycle Detection) # programming # beginners # tutorial # python Comments Add Comment 2 min read I Built a Simple MIPS CPU Simulator in Python 🧠 Alberto Alberto Alberto Follow Jan 8 I Built a Simple MIPS CPU Simulator in Python 🧠 # python # beginners # codecademy # architecture Comments Add Comment 1 min read Creating Materials in Unreal Engine 5 and Understanding ORM Textures (Day 14) Dinesh Dinesh Dinesh Follow Jan 9 Creating Materials in Unreal Engine 5 and Understanding ORM Textures (Day 14) # gamedev # unrealengine # beginners # learning Comments Add Comment 2 min read Java Basics: Understanding Class and Object for Beginners Kesavarthini Kesavarthini Kesavarthini Follow Jan 9 Java Basics: Understanding Class and Object for Beginners # java # beginners # learning # programming Comments Add Comment 1 min read Day 6 – Build a Fixed Transport Route & Fare Reference System in Python Kingsley Ifeanyichukwu Onyema Kingsley Ifeanyichukwu Onyema Kingsley Ifeanyichukwu Onyema Follow Jan 9 Day 6 – Build a Fixed Transport Route & Fare Reference System in Python # python # beginners # devops # nigeria Comments Add Comment 2 min read You Know Python Basics—Now Let's Build Something Real Samuel Ochaba Samuel Ochaba Samuel Ochaba Follow Jan 8 You Know Python Basics—Now Let's Build Something Real # python # beginners # gamedev # programming Comments Add Comment 3 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/kolkov | Andrey Kolkov - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Andrey Kolkov Full Stack Developer specializing in Pure Go (no CGO) & Modern Angular 1040+ ⭐ across 30+ projects | Available for consulting Joined Joined on Nov 21, 2019 github website 2 Week Community Wellness Streak Keep the community conversation going! Post at least 2 comments for 2 straight weeks and unlock the 4 Week Badge. Got it Close 1 Week Community Wellness Streak For actively engaging with the community by posting at least 2 comments in a single week. Got it Close Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Six Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least six years. Got it Close Five Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least five years. Got it Close Four Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least four years. Got it Close Three Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least three years. Got it Close Two Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least two years. Got it Close One Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least one year. Got it Close More info about @kolkov Post 17 posts published Comment 18 comments written Tag 9 tags followed Pin Pinned Go 1.26 Meets 2026 with a Professional Graphics Ecosystem Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Dec 29 '25 Go 1.26 Meets 2026 with a Professional Graphics Ecosystem # go # graphics # gpu # newyear 1 reaction Comments 6 comments 5 min read Smart Coding vs Vibe Coding: Engineering Discipline in the Age of AI Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Jan 12 Smart Coding vs Vibe Coding: Engineering Discipline in the Age of AI # programming # ai # productivity # architecture 1 reaction Comments Add Comment 15 min read Want to connect with Andrey Kolkov? Create an account to connect with Andrey Kolkov. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in GRPM v0.5.0: 75% Gentoo Coverage — Rapid Development Complete Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Jan 10 GRPM v0.5.0: 75% Gentoo Coverage — Rapid Development Complete # go # linux # opensource # packagemanager Comments Add Comment 4 min read Why I Rewrote Portage in Go: Introducing GRPM v0.1.0 Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Jan 8 Why I Rewrote Portage in Go: Introducing GRPM v0.1.0 # go # linux # opensource # programming 5 reactions Comments Add Comment 5 min read GxPDF v0.1.0: 100% Table Extraction Accuracy in Pure Go Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Jan 7 GxPDF v0.1.0: 100% Table Extraction Accuracy in Pure Go # go # pdf # opensource # database Comments Add Comment 4 min read FURSY: The First Type-Safe HTTP Router for Go - 10M req/s with Zero Runtime Errors Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Jan 5 FURSY: The First Type-Safe HTTP Router for Go - 10M req/s with Zero Runtime Errors # go # webdev # api # opensource Comments Add Comment 8 min read GPU Compute Shaders in Pure Go: gogpu/gg v0.15.3 Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Dec 26 '25 GPU Compute Shaders in Pure Go: gogpu/gg v0.15.3 # go # gpu # graphics # webgpu 1 reaction Comments Add Comment 7 min read Pure Go 2D Graphics Library with GPU Acceleration: Introducing gogpu/gg Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Dec 18 '25 Pure Go 2D Graphics Library with GPU Acceleration: Introducing gogpu/gg # go # graphics # gpu # opensource Comments Add Comment 3 min read GoGPU: From Idea to 100K Lines in Two Weeks — Building Go's GPU Ecosystem Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Dec 17 '25 GoGPU: From Idea to 100K Lines in Two Weeks — Building Go's GPU Ecosystem # go # graphics # gpu # webgpu Comments Add Comment 5 min read Relica: A Zero-Dependency Query Builder for Go That Won't Break Your Code Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Dec 15 '25 Relica: A Zero-Dependency Query Builder for Go That Won't Break Your Code # go # database # sql # opensource Comments Add Comment 9 min read naga v0.8.0: Pure Go Shader Compiler Reaches Stability Milestone Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Dec 12 '25 naga v0.8.0: Pure Go Shader Compiler Reaches Stability Milestone # go # gpu # graphics # webgpu Comments Add Comment 4 min read From 0 to 11 Bugs Fixed: How GoAWK Battle-Tested My 3000x Faster Regex Engine Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Dec 8 '25 From 0 to 11 Bugs Fixed: How GoAWK Battle-Tested My 3000x Faster Regex Engine # go # opensource # regex # performance Comments Add Comment 4 min read GoGPU: A Pure Go Graphics Library for GPU Programming Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Dec 5 '25 GoGPU: A Pure Go Graphics Library for GPU Programming # go # graphics # gpu # opensource 1 reaction Comments 4 comments 6 min read Born ML v0.6.0: From 90 Seconds to 5 - How We Made Go ML Training Actually Fast Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Dec 4 '25 Born ML v0.6.0: From 90 Seconds to 5 - How We Made Go ML Training Actually Fast # go # machinelearning # gpu # opensource Comments Add Comment 5 min read I Skipped My Birthday to Give Go Its First Real ML Framework Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Dec 2 '25 I Skipped My Birthday to Give Go Its First Real ML Framework # go # machinelearning # opensource # deeplearning Comments Add Comment 4 min read Go's Regexp is Slow. So I Built My Own - up to 3000x Faster Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Nov 29 '25 Go's Regexp is Slow. So I Built My Own - up to 3000x Faster # go # performance # regex # opensource 4 reactions Comments 2 comments 8 min read Pure-Go Race Detector - Race Detection Without CGO Andrey Kolkov Andrey Kolkov Andrey Kolkov Follow Nov 28 '25 Pure-Go Race Detector - Race Detection Without CGO # go # concurrency # testing Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/kevburnsjr/websockets-vs-long-polling-3a0o#websockets | WebSockets vs Long Polling - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Kevin Burns Posted on Jul 22, 2021 • Edited on Aug 28, 2025 WebSockets vs Long Polling This article contrasts the operational complexity of WebSockets and Long Polling using real world examples to promote Long Polling as a simpler alternative to Websockets in systems where a half-duplex message channel will suffice. WebSockets A WebSocket is a long lived persistent TCP connection (often utilizing TLS) between a client and a server which provides a real-time full-duplex communication channel. These are often seen in chat applications and real-time dashboards. Long Polling Long Polling is a near-real-time data access pattern that predates WebSockets. A client initiates a TCP connection (usually an HTTP request) with a maximum duration (ie. 20 seconds). If the server has data to return, it returns the data immediately, usually in batch up to a specified limit. If not, the server pauses the request thread until data becomes available at which point it returns the data to the client. Analysis WebSockets are Full-Duplex meaning both the client and the server can send and receive messages across the channel. Long Polling is Half-Duplex meaning that a new request-response cycle is required each time the client wants to communicate something to the server. Long Polling usually produces slightly higher average latency and significantly higher latency variability compared to WebSockets. WebSockets do support compression, but usually per-message. Long Polling typically operates in batch which can significantly improve message compression efficiency. Scaling Up We’ll now contrast the systemic behavior of server-side scalability for applications using primarily WebSockets vs Long Polling. WebSockets Suppose we have 4 app servers in a scaling group with 10,000 connected clients. Now suppose we scale up the group by adding a new app server and wait for 60 seconds. We find that all of the existing clients are still connected to the original 4 app servers. The Load Balancer may be intelligent enough to route new connections to the new app server in order to balance the number of concurrent connections so that this effect will diminish over time. However, the amount of time required for this system to return to equilibrium is unknown and theoretically infinite. These effects could be mitigated by the application using a system to intelligently preempt web socket connections in response to changes in the scaling group's capacity but this would require the application to have special real-time knowledge about the state of its external environment which crosses a boundary that is typically best left uncrossed without ample justification. Long Polling Suppose we have the same 4 app servers in a scaling group with 10,000 connected clients using Long Polling. Now suppose we scale up the group by adding a new app server and wait for 60 seconds. We observe that the number of open connections has automatically rebalanced with no intervention. We can even state declaratively that if the long poll duration is set to 60 seconds or less, then any autoscaling group will automatically regain equilibrium within 60 seconds of any membership change. This trait can be reflected in the application’s Service Level Objectives. These numbers are important because they are used by operators to correctly tune the app’s autoscaling mechanisms. Analysis Service Level Objectives are an important aspect of system management since they ultimately serve as the contractual interface between dev and ops. If an application’s ability to return to equilibrium after scaling is unbounded, a change in application behavior is likely warranted. Scaling Down The following example illustrates difficulties encountered by a real world device management software company operating thousands of 24/7 concurrent WebSocket connections from thousands of data collection agents placed inside corporate networks. The System A Data Collection Agent, written in Go, is distributed as an executable binary that runs as a service on a customer's machine scanning local networks for SNMP devices and reporting SNMP data periodically to the application in the cloud. One key feature of the product was the ability for a customer to interact with any of their devices in real time from anywhere in the world using a single page web application hosted in the cloud. Because each agent resides on a customer network behind a firewall, the agents would need to initiate and maintain a WebSocket connection to the application in the cloud as a secure full-duplex tunnel. The web service sends commands to agents and agents send data to the web service all through a single persistent TCP connection. The Problem There was one big unexpected technical challenge faced by the team when deploying this system that made deployments risky. Whenever a new version of the app server was deployed to production, the system would be shocked by high impulse reconnect storms originating from the data collection agents. If a server has 2500 active connections and you take it out of service, those 2500 connections will be closed simultaneously and all the agents will reopen new connections simultaneously. This can overwhelm some systems, especially if the socket initialization code touches the database for anything important (ie. authorization). If an agent can’t establish a connection before the read deadline, it will retry the connection again which will drown the app servers even further, causing an unrecoverable negative feedback loop. This proclivity toward failure caused management to change their policies regarding deployments to reduce the number of deployments as much as possible to avoid disruption. The Solution The problem was partially solved by implementing strict exponential retry policies on their clients. This solution was effective enough at reducing the severity of retry storms on app deployment to be considered a good temporary solution. However, deployments were still infrequent by design and the high impulse load spikes weren’t gone, they just no longer produced undesirable secondary effects. Analysis This temporary solution is only possible in situations where the server has complete control over all of its clients. In many scenarios this may not be the case. If the agents were modeled to receive commands from the server by Long Poll and push data to the server through a normal API, the load would be evenly spread. If using a Long Poll architecture, the deployment system would replace a node by notifying the load balancer that the node is going out of service to ensure the node doesn’t receive any new connections, then wait 60 seconds for existing connections to drain in accordance with the service’s shutdown grace period SLO, then take the node offline with confidence. The resulting load increase on other nodes in the group would be gradual and roughly linear. When it comes to distributed systems and their scalability, people often focus on creating efficient systems. Efficiency is important but usually not as important as stability. High impulse events like reconnect storms can produce complex systemic effects. Left unattended, they often amplify the severity of similar effects in different parts of the system in ways that are both unexpected and difficult to predict. If you fail to solve enough of these types of problems, you may soon find yourself a situation where so many components are failing so simultaneously that it’s exceptionally difficult to discern the underlying cause(s) empirically from logs and dashboards. An application’s architecture must be designed primarily in accordance with principle and remain open to modification in response to statistical performance analysis. Conclusion WebSockets are appropriate for many applications which require consistent low latency full duplex high frequency communication such as chat applications. However, any WebSocket architecture that can be reduced to a half-duplex problem can probably be remodeled to use Long Polling to improve the application’s runtime performance variability, reducing operational complexity and promoting total systemic stability. Top comments (3) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Rockie Yang Rockie Yang Rockie Yang Follow Start from user experience and working backward out technologies Work Knock Data Joined Oct 14, 2022 • Jan 12 '23 Dropdown menu Copy link Hide Thanks for great in depth explanation. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Juro Oravec Juro Oravec Juro Oravec Follow Where software, biology and business meets. Location London, UK Work Software Engineer at BenevolentAI Joined Jul 13, 2020 • Jan 10 '24 Dropdown menu Copy link Hide Very insightful write-up! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Paul Pryor Paul Pryor Paul Pryor Follow Full Stack Web Application Developer Joined Mar 4, 2024 • Mar 5 '24 Dropdown menu Copy link Hide Server Sent Events is another alternative similar to Web Sockets but is half duplex. Like comment: Like comment: 2 likes Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Kevin Burns Follow Professional Gopher Location Menlo Park, CA Joined Jul 23, 2017 More from Kevin Burns The Large Language Centipede # ai # ouroboros Skipfilter # go # bitmap # skiplist Data Constraints: From Imperative to Declarative # go # mongodb # architecture # database 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/t/beginners/page/6#main-content | Beginners Page 6 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Beginners Follow Hide "A journey of a thousand miles begins with a single step." -Chinese Proverb Create Post submission guidelines UPDATED AUGUST 2, 2019 This tag is dedicated to beginners to programming, development, networking, or to a particular language. Everything should be geared towards that! For Questions... Consider using this tag along with #help, if... You are new to a language, or to programming in general, You want an explanation with NO prerequisite knowledge required. You want insight from more experienced developers. Please do not use this tag if you are merely new to a tool, library, or framework. See also, #explainlikeimfive For Articles... Posts should be specifically geared towards true beginners (experience level 0-2 out of 10). Posts should require NO prerequisite knowledge, except perhaps general (language-agnostic) essentials of programming. Posts should NOT merely be for beginners to a tool, library, or framework. If your article does not meet these qualifications, please select a different tag. Promotional Rules Posts should NOT primarily promote an external work. This is what Listings is for. Otherwise accepable posts MAY include a brief (1-2 sentence) plug for another resource at the bottom. Resource lists ARE acceptable if they follow these rules: Include at least 3 distinct authors/creators. Clearly indicate which resources are FREE, which require PII, and which cost money. Do not use personal affiliate links to monetize. Indicate at the top that the article contains promotional links. about #beginners If you're writing for this tag, we recommend you read this article . If you're asking a question, read this article . Older #beginners posts 3 4 5 6 7 8 9 10 11 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Headless Mode: Unleash AI in Your CI/CD Pipeline Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 11 Headless Mode: Unleash AI in Your CI/CD Pipeline # tutorial # claudecode # productivity # beginners 1 reaction Comments Add Comment 4 min read New Python Courseware for Early-Career CS Students Jesse Casman Jesse Casman Jesse Casman Follow Jan 8 New Python Courseware for Early-Career CS Students # python # ai # career # beginners Comments Add Comment 3 min read Day 10 of 100 Palak Hirave Palak Hirave Palak Hirave Follow Jan 10 Day 10 of 100 # programming # python # devjournal # beginners Comments Add Comment 1 min read From Math Teacher to Data Science & Web Development: My Coding Journey#introduction #learning #webdev #python #datascience Ahmed Anter Elsayed Ahmed Anter Elsayed Ahmed Anter Elsayed Follow Jan 11 From Math Teacher to Data Science & Web Development: My Coding Journey#introduction #learning #webdev #python #datascience # beginners # webdev # datascience # career Comments 3 comments 2 min read In-place Modification Jayaprasanna Roddam Jayaprasanna Roddam Jayaprasanna Roddam Follow Jan 9 In-place Modification # programming # beginners # tutorial # datastructures Comments Add Comment 2 min read Java Basics: Variables and Data Types Explained for Beginners Kesavarthini Kesavarthini Kesavarthini Follow Jan 10 Java Basics: Variables and Data Types Explained for Beginners # java # beginners # learning # programming Comments Add Comment 2 min read Two Pointers (Opposite Ends) Jayaprasanna Roddam Jayaprasanna Roddam Jayaprasanna Roddam Follow Jan 9 Two Pointers (Opposite Ends) # programming # beginners # tutorial # career Comments Add Comment 2 min read # Welcome to React World: Grasp the Fundamentals and Mental Model! (React Day 1) Vasu Ghanta Vasu Ghanta Vasu Ghanta Follow Jan 9 # Welcome to React World: Grasp the Fundamentals and Mental Model! (React Day 1) # beginners # javascript # react # tutorial Comments Add Comment 5 min read The Java Developer's Roadmap for 2026: From First Program to Production-Ready Professional dbc2201 dbc2201 dbc2201 Follow Jan 9 The Java Developer's Roadmap for 2026: From First Program to Production-Ready Professional # beginners # career # java # tutorial Comments Add Comment 23 min read Prefix Sum Jayaprasanna Roddam Jayaprasanna Roddam Jayaprasanna Roddam Follow Jan 9 Prefix Sum # programming # beginners # tutorial # python Comments Add Comment 2 min read Build a Screen Capture & Scopes Tool with Python, Tkinter, and MSS Mate Technologies Mate Technologies Mate Technologies Follow Jan 9 Build a Screen Capture & Scopes Tool with Python, Tkinter, and MSS # python # tkinter # beginners # opensource Comments Add Comment 4 min read Sliding Window (Variable Size) Jayaprasanna Roddam Jayaprasanna Roddam Jayaprasanna Roddam Follow Jan 9 Sliding Window (Variable Size) # programming # beginners # tutorial # python Comments Add Comment 3 min read I Built a Gesture Controlled Fluid Simulation (And Accidentally Fought GitHub) TROJAN TROJAN TROJAN Follow Jan 10 I Built a Gesture Controlled Fluid Simulation (And Accidentally Fought GitHub) # discuss # programming # ai # beginners 8 reactions Comments 3 comments 2 min read Hash Map Frequency Counting Jayaprasanna Roddam Jayaprasanna Roddam Jayaprasanna Roddam Follow Jan 9 Hash Map Frequency Counting # programming # beginners # tutorial # datastructures Comments Add Comment 2 min read I build a small website to challenge people's CSS skill! AnsonRE AnsonRE AnsonRE Follow Jan 9 I build a small website to challenge people's CSS skill! # challenge # beginners # css # showdev Comments Add Comment 1 min read How Overusing Redis Almost Killed Our Project at Scale Saif Ullah Usmani Saif Ullah Usmani Saif Ullah Usmani Follow Jan 9 How Overusing Redis Almost Killed Our Project at Scale # webdev # devops # softwareengineering # beginners Comments Add Comment 2 min read JAVA INTERNALS: JDK, JRE, JVM, and JIT! Anees Abdul Anees Abdul Anees Abdul Follow Jan 9 JAVA INTERNALS: JDK, JRE, JVM, and JIT! # beginners # java # tutorial Comments Add Comment 2 min read The TypeScript Features I Wish I'd Learned Sooner Tarun Moorjani Tarun Moorjani Tarun Moorjani Follow Jan 8 The TypeScript Features I Wish I'd Learned Sooner # discuss # typescript # beginners # webdev Comments Add Comment 9 min read Las 5 Estructuras de Datos que Dominarán tu Próxima Entrevista Técnica Grego Grego Grego Follow Jan 8 Las 5 Estructuras de Datos que Dominarán tu Próxima Entrevista Técnica # datastructures # interview # beginners # spanish Comments Add Comment 5 min read Fast & Slow Pointers (Cycle Detection) Jayaprasanna Roddam Jayaprasanna Roddam Jayaprasanna Roddam Follow Jan 9 Fast & Slow Pointers (Cycle Detection) # programming # beginners # tutorial # python Comments Add Comment 2 min read I Built a Simple MIPS CPU Simulator in Python 🧠 Alberto Alberto Alberto Follow Jan 8 I Built a Simple MIPS CPU Simulator in Python 🧠 # python # beginners # codecademy # architecture Comments Add Comment 1 min read Creating Materials in Unreal Engine 5 and Understanding ORM Textures (Day 14) Dinesh Dinesh Dinesh Follow Jan 9 Creating Materials in Unreal Engine 5 and Understanding ORM Textures (Day 14) # gamedev # unrealengine # beginners # learning Comments Add Comment 2 min read Java Basics: Understanding Class and Object for Beginners Kesavarthini Kesavarthini Kesavarthini Follow Jan 9 Java Basics: Understanding Class and Object for Beginners # java # beginners # learning # programming Comments Add Comment 1 min read Day 6 – Build a Fixed Transport Route & Fare Reference System in Python Kingsley Ifeanyichukwu Onyema Kingsley Ifeanyichukwu Onyema Kingsley Ifeanyichukwu Onyema Follow Jan 9 Day 6 – Build a Fixed Transport Route & Fare Reference System in Python # python # beginners # devops # nigeria Comments Add Comment 2 min read You Know Python Basics—Now Let's Build Something Real Samuel Ochaba Samuel Ochaba Samuel Ochaba Follow Jan 8 You Know Python Basics—Now Let's Build Something Real # python # beginners # gamedev # programming Comments Add Comment 3 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/tatyanabayramova/accessibility-testing-on-windows-on-mac-48e4#step-3-installing-screen-readers | Accessibility Testing on Windows on Mac - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Tatyana Bayramova, CPACC Posted on May 13, 2025 • Originally published at tatanotes.com Accessibility Testing on Windows on Mac # a11y # testing # web # discuss Today's note is about something that I, as a new Mac user, had to deal with while setting up my work environment. TL;DR: To run NVDA and JAWS on a Mac, you need to install Windows 11 for ARM in a virtual machine like UTM , and map a spare key to the Insert key with SharpKeys . Why do accessibility testing on Windows if you have a Mac? According to the WebAIM Screen Reader User Survey #10 , Windows-only screen readers NVDA and JAWS are used by the majority of users. Just like browsers, screen readers have differences in how they present information, so it's always a good idea to test your website or app using different browser/screen reader combinations. In addition, some of the styling, like box shadows, background images, and so on, is removed when Windows High Contrast Mode (WHCM) is enabled. Sadly, there is no alternative to the WHCM on the Mac. Installation Step 1 – Installing a virtual machine There are multiple virtual machines available on Mac, such as Parallels, VirtualBox, and UTM. I'm using UTM, but this guide doesn't depend on its specifics, so you can choose whatever works for you. You can download UTM for free from the official website . You can also purchase it from the Mac App Store to support the team behind the software. Step 2 – Installing Windows When you have got UTM up and running, create a new virtual machine. You will need a Windows installation disk image, which you can download from the Microsoft website . Click on "Create a New Virtual Machine", select "Virtualize", and follow the wizard. You will need to specify the path to the installation ISO here. Step 3 – Installing screen readers Both NVDA and JAWS work on ARM-based devices now, so you can install them in a virtual machine, just as you would on a real device. If you would like to install any other programs, make sure that they also support ARM processors. Step 4 – Mapping missing keys Due to the fact that Mac and Windows use different keyboards, you are not able to use the Insert key in your UTM virtual machine. (You will need it for the various shortcuts for NVDA and JAWS.) You have to use a third-party program to remap keys on Mac or Windows level. I'm using SharpKeys – an open-source program for Windows. Download, install, and run SharpKeys inside the virtual machine . Click on the "Add" button. In the new window, find "Special: Insert" on the right. In the left list, select a key that you would like to act as the Insert key. For instance, if you select F1 on the left, every time you press F1 key inside your virtual machine, it will register as Insert. Make sure to map a key that is not used in any shortcuts. Once finished, press "OK", and then "Write to registry" to save changes – it will not work otherwise. At this point, you're good to go and start your accessibility testing. Hooray! Step 5 (bonus) – Accessing localhost If you are developing a project and running it locally, you might want to do quality assurance before deploying changes. For this, you need to be able to access your project at http://localhost:port from within the virtual machine. One way to do that with UTM is to set the network mode for the virtual machine to "Shared Network". Then, look up the Default Gateway IP address in Windows, which you can do by running ipconfig command in the Command Prompt: Now make sure that your project is accepting requests to this IP address. For example, to run a SvelteKit project in development mode and accept connections on all available IP addresses, you need to slightly modify the default command: npm run dev -- --host Enter fullscreen mode Exit fullscreen mode You can find a similar command for your tool. Extensive accessibility testing is important Mac is a great platform for web development. However, the reality is that majority of desktop users are Windows users. Thanks to tools like UTM, we are able to run Windows and Windows-specific software directly on a Mac. By testing on a wide range of tools and platforms, we make the Web accessible for all. What is your setup? Share it in the comments! Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Tatyana Bayramova, CPACC Follow Senior Software Engineer | CPACC | IAAP Member | Accessibility Joined Dec 3, 2024 More from Tatyana Bayramova, CPACC AI in Assistive Technologies for People with Visual Impairments # discuss # a11y # ai # news Glaucoma Awareness Month # a11y # discuss # news Our Rights, Our Future, Right Now - Celebrating Human Rights Day # a11y # discuss # news # learning 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://future.forem.com/privacy#b-information-collected-automatically | Privacy Policy - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:06 |
https://future.forem.com/privacy#7-retention-of-personal-information | Privacy Policy - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/askrishnapravin/for-loop-vs-map-for-making-multiple-api-calls-3lhd#map | for loop vs .map() for making multiple API calls - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Krishna Pravin Posted on May 14, 2020 • Edited on May 29, 2020 for loop vs .map() for making multiple API calls # javascript # api # async Promise / async-await is used for making API calls. const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/1` ) const todo = await response . json () console . log ( todo ) Enter fullscreen mode Exit fullscreen mode Assuming I have a list of ids of todo items and I want the title of all them then I shall use the below snippet inside an async function const todoIdList = [ 1 , 2 , 3 , 4 ] for ( const id of todoIdList ) { const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) const todo = await response . json () console . log ( todo . title ) } Enter fullscreen mode Exit fullscreen mode This same can be written with any of these for , for...in , for...of loops. Assuming each API request arbitrarily takes 100ms exactly, the total time taken for getting the details of four todo items will have to be greater than 400ms if we use any of the above-mentioned loops. This execution time can be drastically reduced by using .map() . const todoIdList = [ 1 , 2 , 3 , 4 ] await Promise . all ( todoIdList . map ( async ( id ) => { const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) const todo = await response . json () console . log ( todo . title ) }) ) Enter fullscreen mode Exit fullscreen mode Adding timers const todoIdList = [ 1 , 2 , 3 , 4 ] console . time ( ' for {} ' ); for ( const id of todoIdList ) { const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) const todo = await response . json () console . log ( todo . title ) } console . timeEnd ( ' for {} ' ); console . time ( ' .map() ' ); await Promise . all ( todoIdList . map ( async ( id ) => { const response = await fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) const todo = await response . json () console . log ( todo . title ) }) ) console . timeEnd ( ' .map() ' ); Enter fullscreen mode Exit fullscreen mode The Reason for loop for loop goes to the next iteration only after the whole block's execution is completed. In the above scenario only after both the promises(await) gets resolved , for loop moves to the next iteration and makes the API call for the next todo item. .map() .map() moves on to the next item as soon as a promise is returned . It does not wait until the promise is resolved. In the above scenario, .map() does not wait until the response for todo items comes from the server. It makes all the API calls one by one and for each API call it makes, a respective promise is returned. Promise.all waits until all of these promises are resolved. async/await is syntactic sugar for Promises It will be more clear if the same code is written without async/await const todoIdList = [ 1 , 2 , 3 , 4 ] console . time ( ' .map() ' ) Promise . all ( todoIdList . map ( id => { return new Promise (( resolve ) => { fetch ( `https://jsonplaceholder.typicode.com/todos/ ${ id } ` ) . then ( response => { return new Promise (() => { response . json () . then ( todo => { console . log ( todo . title ) resolve () }) }) }) }) }) ) . then (() => { console . timeEnd ( ' .map() ' ); }) Enter fullscreen mode Exit fullscreen mode It is not possible to mimic the respective code for for loop by replacing async/await with Promises because, the control which triggers the next iteration will have to written within the .then() block. This piece of code will have to be created within the JS engine. All the snippets are working code, you can try it directly in the browser console. Note: snippets need to be enclosed within an async function except for the last one use Axios or any other suitable library if fetch is not available. Let me know if there is an even better and easy/short way of making API calls. Also, do not forget to mention any mistakes I've made or tips, suggestions to improve this content. Top comments (6) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Quinn Quinn Quinn Follow Joined Jun 28, 2021 • Jun 28 '21 Dropdown menu Copy link Hide Not really a fair comparison. Map is creating a new array of promises then asynchronously executing them. To do this with a for loop you would do something like this: const todoIdList = [1, 2, 3, 4] const promiseList = [] for (const id of todoIdList) { const response = fetch( https://jsonplaceholder.typicode.com/todos/${id} ) promiseList.push(response.json()) } const responses = Promise.all(promiseList) Like comment: Like comment: 5 likes Like Comment button Reply Collapse Expand Krishna Pravin Krishna Pravin Krishna Pravin Follow Location Bangalore, India Education B. Tech IT Work Software Engineer - Full Stack at Gyanmatrix Technologies Joined Jun 10, 2019 • Jul 26 '21 Dropdown menu Copy link Hide This approach looks good. Pushing the promises into an array within for loop will achieve concurrency. But when we have a need for more than one await inside the block, it will not work. In the above code, response.json() won't work because response is a promise, it won't have json() method. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Yogendra Yogendra Yogendra Follow Location Bengaluru, India Work Web Developer at LayerIV Joined Sep 25, 2020 • Jan 31 '21 Dropdown menu Copy link Hide This is quite great. But, could you tell me what is the optimum way to resolve multiple promises and get their statuses, as Promise.all() fails as soon as any of the Promise rejects? I heard of Promise.allSettled() but is only available in recent versions of ES. Thanks!! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Krishna Pravin Krishna Pravin Krishna Pravin Follow Location Bangalore, India Education B. Tech IT Work Software Engineer - Full Stack at Gyanmatrix Technologies Joined Jun 10, 2019 • Feb 9 '21 Dropdown menu Copy link Hide Shim: npmjs.com/package/promise.allsettled Polyfill: logic24by7.com/promise-allsettled-... Like comment: Like comment: Like Comment button Reply Collapse Expand Rajesh Moka Rajesh Moka Rajesh Moka Follow I am a front end developer. I like building stuff with react. Location India Work Front End Developer at Tata Consultancy Services Joined May 27, 2020 • Jan 20 '21 Dropdown menu Copy link Hide This is a great article. I had trouble understanding the last example without async await but with promises. I knew promise.all takes promises array as an argument, but why did we write promise in each fetch call? Can u explain a little Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Krishna Pravin Krishna Pravin Krishna Pravin Follow Location Bangalore, India Education B. Tech IT Work Software Engineer - Full Stack at Gyanmatrix Technologies Joined Jun 10, 2019 • Jan 29 '21 Dropdown menu Copy link Hide The last example(using promise) is the same as the previous one(using await). We have a promise inside fetch because parsing response as json response.json() returns a promise. For each API call, Promise.all() will first wait for the API call's response to arrive, and then it will wait for the json parsing to complete. When Promise.all takes an array of promises, it will wait for all the inner promises as well to get resolved. Like comment: Like comment: 1 like Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Krishna Pravin Follow Location Bangalore, India Education B. Tech IT Work Software Engineer - Full Stack at Gyanmatrix Technologies Joined Jun 10, 2019 Trending on DEV Community Hot Top 7 Featured DEV Posts of the Week # top7 # discuss Stop Overengineering: How to Write Clean Code That Actually Ships 🚀 # discuss # javascript # programming # webdev If a problem can be solved without AI, does AI actually make it better? # ai # architecture # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/ed-wantuil/cloud-sem-falencia-o-minimo-que-voce-precisa-saber-de-finops-8ao#7-dilema-geogr%C3%A1fico-reduzindo-a-fatura-pela-metade | Cloud Sem Falência: O mínimo que você precisa saber de FinOps - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Ed Wantuil Posted on Jan 12 Cloud Sem Falência: O mínimo que você precisa saber de FinOps # devops # cloud # braziliandevs Imagine a cena: você trabalha em uma empresa consolidada. Vocês têm aquele rack de servidores físicos robusto, piscando luzinhas em uma sala gelada, com piso elevado e controle biométrico (o famoso On-Premise ). Tudo funciona. O banco de dados aguenta o tranco, a latência é zero na rede local. Mas a diretoria decide que é hora de "modernizar". "Vamos migrar para a Nuvem!" , dizem eles, com os olhos brilhando. A promessa no PowerPoint é sedutora: flexibilidade infinita , segurança gerenciada e o mantra mágico: "pagar só pelo que usar" . A migração acontece via Lift-and-Shift (pegar o que existe e jogar na nuvem sem refatorar). A equipe de Infra e Dev comemoram. O Deploy é um sucesso. Três meses depois, chega a fatura da AWS. O diretor financeiro (CFO) não apenas cai da cadeira; ele convoca uma reunião de emergência. O custo, que antes era uma linha fixa e previsível no balanço anual, triplicou e agora flutua violentamente. O que deu errado? Simples: A engenharia tratou a Nuvem como um Data Center físico, apenas alugado. Hoje, vamos falar sobre os riscos dessa mudança e como aplicar FinOps não como burocracia, mas como requisito de arquitetura. (Nota: Usaremos a AWS nos exemplos por ser a stack padrão de mercado, mas a lógica se aplica integralmente ao Azure, GCP e OCI). 🦄 A Ilusão da Mágica: CAPEX vs. OPEX na Engenharia Para entender a conta da AWS, você precisa entender como o dinheiro sai do cofre da empresa. A mudança da nuvem não é apenas sobre onde o servidor roda, é sobre quem assume o risco do desperdício. 1. CAPEX (Capital Expenditure): A Lógica do "PC Gamer" CAPEX é Despesa de Capital. É comprar a "caixa". Imagine que você vai montar um PC Gamer High-End. Você gasta R$ 20.000,00 na loja. Doeu no bolso na hora, certo? Mas depois que o PC está na sua mesa: Custo Marginal Zero: Se você jogar Paciência ou renderizar um vídeo em 8K a noite toda, não faz diferença financeira para o seu bolso (tirando a conta de luz, que é irrisória perto do hardware). O dinheiro já foi gasto ( Sunk Cost ). O Comportamento do Engenheiro (On-Premise): Como o processo de compra é lento (meses de cotação e aprovação), você tem medo de faltar recurso. Mentalidade: "Vou pedir um servidor com 64 Cores, mesmo precisando de 16. Se sobrar, melhor. O hardware é nosso mesmo." Código: Eficiência não é prioridade financeira. Um código mal otimizado que consome 90% da CPU não gera uma fatura extra no fim do mês. 2. OPEX (Operational Expenditure): A Lógica do Uber OPEX é Despesa Operacional. É o custo de funcionamento do dia a dia. Na nuvem, você não comprou o carro; você está rodando de Uber 24 horas por dia. Custo Marginal Real: Cada minuto parado no sinal custa dinheiro. Cada desvio de rota custa dinheiro. O Comportamento do Engenheiro (Cloud): Aqui, a ineficiência é taxada instantaneamente. Mentalidade: Aquele servidor de 64 cores e 512GB de ram parado esperando tráfego é como deixar o Uber te esperando na porta do escritório enquanto você trabalha. O taxímetro está rodando. Código: Um loop infinito ou uma query sem índice no banco de dados não deixa apenas o sistema lento; ele queima dinheiro vivo . Comparativo para Desenvolvedores (Salve isso) Feature CAPEX (On-Premise / Hardware Próprio) OPEX (Cloud / AWS / Azure) Commit Financeiro Você paga tudo antes de usar (Upfront). Você paga depois de usar (Pay-as-you-go). Latência de Aprovação Alta. Precisa de reuniões, assinaturas e compras. Zero. Um terraform apply gasta dinheiro instantaneamente. Risco de Capacidade Subutilização. Comprar um servidor monstro e usar 10%. Conta Surpresa. Esquecer algo ligado ou escalar infinitamente. Otimização de Código Melhora performance, mas não reduz a fatura do hardware. Reduz diretamente a fatura. Código limpo = Dinheiro no caixa. Por que isso afeta a sua Arquitetura? Se você desenha uma arquitetura pensando em CAPEX (Mundo Físico) e a implementa em OPEX (Nuvem), você cria um desastre financeiro. No CAPEX , a estratégia de defesa é: "Superdimensionar para garantir estabilidade". (Compre o maior servidor possível). No OPEX , a estratégia de defesa é: "Elasticidade". (Comece com o menor servidor possível e configure para crescer sozinho apenas se necessário). 💸 Os 8 Cavaleiros do Apocalipse Financeiro na AWS Na nuvem, os maiores vilões raramente são tecnologias complexas de IA ou Big Data. Quase sempre são decisões arquiteturais preguiçosas e falta de governança . 1. Instâncias "Just in Case": O Custo do Seguro Psicológico O sobredimensionamento é um vício comum: o desenvolvedor sobe uma instância m5.2xlarge (8 vCPUs, 32GB RAM) não porque a aplicação exige, mas porque ele "não quer ter dor de cabeça". É o provisionamento baseado no medo, criando uma margem de segurança gigantesca e cara para evitar qualquer risco hipotético de lentidão. A realidade nua e crua aparece no CloudWatch: na maior parte do tempo, essa supermáquina opera com apenas 12% de CPU e usa uma fração da memória. Pagar por uma 2xlarge para rodar essa carga é como fretar um ônibus de 50 lugares para levar apenas 4 pessoas ao trabalho todos os dias. Você está pagando pelo "espaço vazio" e pelo motor potente do ônibus, enquanto um carro popular ( t3.medium ) faria o mesmo trajeto com o mesmo conforto e muito mais economia. 2. Ambientes Zumbis: A Torneira Aberta Fora do Expediente "Ambientes Zumbis" são servidores de Desenvolvimento e Homologação que operam como cópias fiéis da Produção, mas sem a audiência dela. Eles permanecem ligados e faturando às 3 da manhã de um domingo, consumindo recursos de nuvem para processar absolutamente nada. Manter esses servidores ligados 24/7 é o equivalente digital de deixar o ar-condicionado de um escritório ligado no máximo durante todo o fim de semana , com o prédio completamente vazio. O impacto financeiro atua como um multiplicador de desperdício. Se você mantém três ambientes (Dev, Staging e Produção) com arquiteturas similares ligados ininterruptamente, seu custo base é 300% do necessário . A matemática é cruel: uma semana tem 168 horas, mas seus desenvolvedores trabalham apenas 40. Você está pagando por 128 horas de ociosidade pura por máquina, todas as semanas. A primeira cura para esse desperdício é o agendamento automático. Utilizando soluções como o AWS Instance Scheduler (ou Lambdas simples), configuramos os ambientes para "acordar" às 08:00 e "dormir" às 20:00, de segunda a sexta-feira. Apenas essa automação básica, sem alterar uma linha de código da aplicação, reduz a fatura desses ambientes não-produtivos em cerca de 70% . 3. O Esquecimento Crônico: O Custo do Limbo Um dos "pegadinhas" mais comuns da nuvem acontece no momento de desligar as luzes: quando você termina uma instância EC2, o senso comum diz que a cobrança para. O erro está em assumir que a máquina e o disco são uma peça única. Por padrão, ao "matar" o servidor, o volume de armazenamento (EBS) acoplado a ele muitas vezes sobrevive, entrando num estado de limbo financeiro. O resultado é o acúmulo de EBS Órfãos : centenas de discos no estado "Available" (não atrelados a ninguém), cheios de dados inúteis ou completamente vazios, pelos quais você paga o preço cheio do gigabyte provisionado. É comparável a vender seu carro, mas esquecer de cancelar o aluguel da vaga de garagem: o veículo não existe mais, mas a cobrança pelo espaço que ele ocupava continua chegando todo mês na fatura. A situação piora com os Elastic IPs (EIPs) , que possuem uma lógica de cobrança invertida e punitiva. Devido à escassez mundial de endereços IPv4, a AWS não cobra pelo IP enquanto você o utiliza, mas começa a cobrar assim que ele fica ocioso . É como uma "multa por não uso": se você reserva um endereço IP e não o atrela a uma instância em execução, você paga por estar "segurando" um recurso escasso sem necessidade. 4. O Cemitério de Dados no S3 Buckets S3 tendem a virar "cemitérios digitais" onde logs, backups e assets se acumulam indefinidamente. O erro crucial não é guardar os dados, mas a falta de estratégia: manter 100% desse volume na classe S3 Standard , pagando a tarifa mais alta da AWS por arquivos que ninguém acessa há meses. Para entender o prejuízo, imagine o S3 Standard como uma loja no corredor principal de um shopping: o aluguel é caríssimo porque o acesso é imediato e fácil ( baixa latência ). Manter logs de 2022 nessa classe é como alugar essa vitrine premium apenas para estocar caixas de papelão velhas. Dados "frios", que raramente são consultados, não precisam estar à mão em milissegundos; eles podem ficar num armazém mais distante e barato. A solução é o S3 Lifecycle , que automatiza a logística desse "estoque". Primeiro, ele atua na Transição : move automaticamente os dados que envelhecem da "vitrine" (Standard) para o "armazém" ( S3 Glacier ). No Glacier, você paga uma fração do preço, aceitando que o resgate do arquivo leve alguns minutos ou horas (maior latência), o que é aceitável para arquivos de auditoria ou backups antigos. Por fim, o Lifecycle resolve o acúmulo de lixo através da Expiração . Além de mover dados, você configura regras para deletar objetos definitivamente após um período, como remover logs temporários após 7 dias. Isso garante a higiene do ambiente, impedindo que você pague aluguel (seja no shopping ou no armazém) por dados inúteis que não deveriam mais existir. 5. Snapshots: O Colecionador de Backups Fantasmas Backups são a apólice de seguro da sua infraestrutura, mas a facilidade de criar snapshots na AWS gera um comportamento perigoso de acumulação. O erro clássico é configurar uma automação de snapshot diário e definir a retenção para "nunca" ou prazos absurdos como 5 anos. Embora os snapshots sejam incrementais (salvando apenas o que mudou), em bancos de dados transacionais com muita escrita, o volume de dados alterados cresce rápido, e a fatura acompanha. Para visualizar o desperdício, imagine que você compra o jornal do dia para ler as notícias. É útil ter os jornais da última semana na mesa para referência rápida. Mas guardar uma pilha de jornais diários de três anos atrás na sua sala ocupa espaço valioso e custa dinheiro, sendo que a chance de você precisar saber a "cotação do dólar numa terça-feira específica de 2021" é praticamente nula. Você está pagando armazenamento premium por "jornais velhos" que não têm valor de negócio. 6. Licenciamento Comercial (O Custo Invisível) Muitas empresas focam tanto em otimizar CPU e RAM que esquecem o elefante na sala: o custo de software. Ao rodar instâncias com Windows Server ou SQL Server Enterprise na AWS no modelo "License Included", você não paga apenas pela infraestrutura; você paga uma sobretaxa pesada pelo direito de uso do software proprietário. Esse custo é embutido na tarifa por hora e, em máquinas grandes, a licença pode custar mais caro que o próprio hardware. Para ilustrar a desproporção, usar o SQL Server Enterprise para uma aplicação que não utiliza funcionalidades avançadas (como Always On complexo ou compressão de dados específica) é como fretar um jato executivo apenas para ir comprar pão na padaria . O objetivo (armazenar e recuperar dados) é cumprido, mas você está pagando por um veículo de luxo quando uma bicicleta ou um Uber resolveria o problema com a mesma eficiência e uma fração do custo. A primeira camada de solução é a Otimização de Edição . É comum desenvolvedores solicitarem a versão Enterprise por "garantia" ou hábito, sem necessidade técnica real. Uma auditoria simples muitas vezes revela que a versão Standard atende a todos os requisitos da aplicação. Fazer esse downgrade reduz a fatura de licenciamento imediatamente, sem exigir mudanças drásticas na arquitetura ou no código. 7. Dilema Geográfico: Reduzindo a Fatura pela Metade Hospedar aplicações na região sa-east-1 (São Paulo) carrega um ágio pesado: o "Custo Brasil" digital faz com que a infraestrutura local custe, cerca de 50% a mais do que na us-east-1 (N. Virgínia). Migrar workloads para os EUA é, frequentemente, a manobra de FinOps com maior retorno imediato (ROI): você corta a fatura desses recursos praticamente pela metade apenas alterando o CEP do servidor, acessando o mesmo hardware por uma fração do preço. O principal bloqueador costuma ser o medo da LGPD , mas a crença de que a lei exige residência física dos dados no Brasil é um mito . O Artigo 33 permite a transferência internacional para países com proteção adequada (como os EUA), desde que coberto por contratos padrão. A legislação foca na segurança e privacidade do dado, não na sua latitude e longitude geográfica. Quanto à técnica, a latência para a Virgínia (~120ms) é imperceptível para a maioria das aplicações web, sistemas internos e dashboards. A estratégia inteligente é adotar uma região como US East como padrão para maximizar a economia, reservando São Paulo apenas para exceções que realmente exigem resposta em tempo real (como High Frequency Trading), evitando pagar preço de "primeira classe" para cargas de trabalho que rodariam perfeitamente na econômica. 8. Serverless: A Faca de Dois Gumes "Serverless" é computação sem gestão de infraestrutura (como AWS Lambda ou DynamoDB). Diferente de alugar um servidor fixo mensal, aqui você paga apenas pelos milissegundos que seu código executa ou pelo dado que você lê. É como a conta de luz: você só paga se o interruptor estiver ligado. A Estratégia: Para uso esporádico, é imbatível. Mas e para uso constante? Também pode ser uma excelente escolha! Embora a fatura de infraestrutura possa vir mais alta do que em servidores tradicionais, você elimina o trabalho pesado de manutenção. Muitas vezes, é financeiramente mais inteligente pagar um pouco mais para a AWS do que custear horas de engenharia ou contratar uma equipe dedicada apenas para gerenciar servidores, aplicar patches de segurança e configurar escalas. O segredo é olhar para o Custo Total (TCO), e não apenas para a linha de processamento na fatura. 🕵️♂️ FinOps: Engenharia Financeira na Prática FinOps não é apenas sobre "pedir desconto" ou cortar gastos; é a mudança cultural que descentraliza a responsabilidade do custo, empoderando engenheiros a tomar decisões baseadas em dados, não em palpites. Para que essa cultura saia do papel, ela precisa se apoiar em um tripé de governança robusto: a visibilidade granular garantida pelo tageamento correto (saber quem gasta), a segurança operacional monitorada pelo AWS Budgets (saber quando gasta) e a eficiência financeira obtida através dos Modelos de Compra inteligentes (saber como pagar). Sem integrar essas três frentes, a nuvem deixa de ser um acelerador de inovação para se tornar um passivo financeiro descontrolado. 1. TAGs: Sem Etiquetas, Sem Dados 🏷️ No AWS Cost Explorer, uma infraestrutura sem tags opera como uma "caixa preta" financeira: você encara uma fatura de $50.000, mas é incapaz de discernir se o rombo veio de um modelo crítico de Data Science ou de um cluster Kubernetes esquecido por um estagiário. Utiliza tags como custo:centro , app:nome , env e dono no momento dos recursos transformara números genéricos em rastreáveis, permitindo que cada centavo gasto tenha um responsável atrelado, eliminando definitivamente a cultura de que "o custo da nuvem não é problema meu". 2. AWS Budgets e Detecção de Anomalias 🚨 Não espere o fim do mês. Configure o AWS Budgets para alertar quando o custo projetado (forecasted) ultrapassar o limite. Dica: Ative o Cost Anomaly Detection . Ele usa Machine Learning para identificar picos anormais. Exemplo: Um deploy errado fez a cahamada para um Lambda entrar em loop infinito. O Anomaly Detection te avisa em horas, não no fim do mês. 3. Modelos de Compra: O Fim do On-Demand 💸 Operar 100% em On-Demand é pagar voluntariamente um "imposto sobre a falta de planejamento". A maturidade em FinOps exige abandonar o preço de varejo e adotar um mix estratégico: cubra sua carga de trabalho base (aquela que roda 24/7) com Savings Plans , que oferecem descontos de até 72% em troca de fidelidade, e mova cargas tolerantes a interrupções, como processamento de dados e pipelines de CI/CD, para Spot Instances , aproveitando a capacidade ociosa da AWS por até 10% do valor original . Ignorar essa estratégia e manter tudo no On-Demand é uma decisão consciente de desperdiçar orçamento que poderia ser reinvestido em inovação. 🧠 Dev Assina o Código e o Cheque No mundo On-Premise, um código ruim apenas deixava o sistema lento. Na Nuvem, código ineficiente gera uma fatura imediata . A barreira entre Engenharia e Financeiro desapareceu: cada linha de código é uma decisão de compra executada em tempo real. O desenvolvedor não consome apenas CPU, ele consome o orçamento da empresa. Para entender o impacto, veja o preço das más práticas: O Custo da Leitura: Uma query sem " WHERE " ou um Full Table Scan no DynamoDB não é apenas um problema de performance; você está pagando unidades de leitura para ler milhares de linhas inúteis. É como comprar a biblioteca inteira para ler uma única página. O Custo da Ineficiência: Um código com vazamento de memória engana o Auto Scaling . O sistema provisiona 10 servidores para fazer o trabalho de 2, desperdiçando dinheiro para compensar código ruim. O Custo do Ruído: Logs em modo VERBOSE esquecidos em produção são vilões. O CloudWatch cobra caro pela ingestão. Enviar gigabytes de "log de lixo" é literalmente pagar frete aéreo para transportar entulho. A Cultura de Engenharia Consciente de Custos: Estimativa no Refinamento: O custo deve ser debatido antes do código existir. Durante o Refinamento, ao definir a arquitetura, faça a pergunta: "Quais recursos vamos usar e quanto isso vai custar com a volumetria esperada?" . Se a solução técnica custa $1.000 para economizar $50 de esforço manual, ela deve ser vetada ali mesmo. Feedback Loop: O desenvolvedor precisa ver quanto o serviço dele custa. Painéis do Grafana ou Datadog devem mostrar não só a latência da API, mas o custo diário dela. Só existe responsabilidade quando existe consciência do preço. Cerimônia de Custo (FinOps Review): Estabeleça uma reunião recorrente dedicada a olhar o "Extrato da Conta" . O time analisa os custos atuais, investiga picos não planejados da semana anterior e discute ativamente: "Existe alguma oportunidade de desligar recursos ou otimizar este serviço agora?" . É a higiene financeira mantendo o projeto saudável. 🌐 O Mundo Híbrido e Multicloud: Complexidade é Custo Nem tudo precisa ir para a AWS, e nem tudo deve sair do seu Data Center local. A maturidade em nuvem não significa "desligar tudo o que é físico", mas sim saber onde cada peça do jogo custa menos. Empresas podem operam em modelos híbridos estratégicos: O Lugar do Legado (On-Premise): Aquele banco de dados gigante ou mainframe que já está quitado, não cresce mais e roda de forma previsível? Deixe onde está. Migrar esses monstros para a nuvem apenas copiando e colando ("Lift-and-Shift") costuma ser um desastre financeiro. Na nuvem, você paga caro por performance de disco (IOPS) e memória que, no seu servidor físico, já são "gratuitos". O Lugar da Inovação (Nuvem): Seu site, aplicativos móveis e APIs que precisam aguentar milhões de acessos num dia e zero no outro? Leve para a nuvem. Lá você paga pela elasticidade e pelo alcance global que o servidor físico não consegue entregar. Cuidado com a Armadilha Multicloud Muitos gestores caem na tentação de usar AWS, Azure e Google Cloud ao mesmo tempo sob o pretexto de "evitar ficar preso a um fornecedor" (Vendor Lock-in). Na prática, para a maioria das empresas, isso triplica o custo operacional . Você precisará de equipes especialistas em três plataformas diferentes, perderá descontos por volume (diluindo seu gasto) e pagará taxas altíssimas de transferência de dados (Egress) para fazer as nuvens conversarem entre si. Complexidade técnica é, invariavelmente, custo financeiro. Como gerenciar essa infraestrutura sem perder o controle? O uso de ferramentas como Terraform ou OpenTofu . Com elas, criar um servidor não é mais clicar em botões numa tela, mas sim escrever um arquivo de texto (código). Isso habilita a Revisão de Código Financeira : Um desenvolvedor propõe uma mudança no código da infraestrutura. Antes de aprovar, o time revisa num "Pull Request". A pergunta muda de "O código está certo?" para "Por que você alterou a máquina de micro para extra-large ?" . O Code Review de infraestrutura torna-se a primeira e mais barata linha de defesa do FinOps, barrando gastos desnecessários antes mesmo que eles sejam criados. Conclusão: A Nuvem não é um Destino, é um Modelo Econômico Migrar para a nuvem não é apenas trocar de servidor; é adotar um novo paradigma operacional e financeiro. Tratar a AWS como um "datacenter glorificado" é o caminho mais rápido para transformar a inovação em prejuízo: ao fazer isso, você acaba pagando a diária de um hotel cinco estrelas apenas para estocar caixas de papelão que poderiam estar num depósito simples. A virada de chave acontece na cultura. Comece pelo básico bem feito: aplique Tags rigorosamente, automatize a limpeza de recursos e traga o custo para o centro das decisões de arquitetura. Lembre-se que, neste novo mundo, a excelência técnica é inseparável da eficiência financeira: o melhor código não é apenas o que funciona, é o que entrega valor máximo consumindo o mínimo de orçamento. Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Ed Wantuil Follow Meu objetivo é compartilhar conhecimento, criar soluções e ajudar outras pessoas a evoluírem na carreira de tecnologia. Location Brasil Joined Dec 15, 2023 More from Ed Wantuil Java 25: tudo que mudou desde o Java 21 em um guia prático # java # braziliandevs # java25 # jvm 10 Passos Para Conduzir um Pós-Mortem Que Realmente Evita Novos Incidentes # devops # incidentes # crises # dev Top 5 Vacilos que Desenvolvedores Cometem em uma Crise (e como evitar) # devops # postmortem # deploydesexta 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fsrikarsunchu%2Fi-got-tired-of-waiting-for-gradle-so-i-built-a-runtime-that-runs-kotlin-like-python-10nl&title=I%20got%20tired%20of%20waiting%20for%20Gradle%2C%20so%20I%20built%20a%20runtime%20that%20runs%20Kotlin%20like%20Python.&summary=I%20hit%20.%2Fgradlew%20run%20and%20alt-tab%20to%20Discord.%20By%20the%20time%20I%20tab%20back%2C%20it%27s%20still%20resolving...&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:06 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Farunavamodak%2Freact-router-v5-vs-v6-dp0&title=React%20Router%20V5%20vs%20V6&summary=React%20Router%20version%206%20was%20released%20recently%2C%20and%20it%20is%20important%20for%20us%20to%20understand%20the%20changes%20as...&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:06 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Falexsergey%2Fcss-modules-vs-css-in-js-who-wins-3n25&title=CSS%20Modules%20vs%20CSS-in-JS.%20Who%20wins%3F&summary=Introduction%20%20%20In%20modern%20React%20application%20development%2C%20there%20are%20many%20approaches%20to%20organiz...&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:06 |
https://dev.to/t/designpatterns | Designpatterns - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close # designpatterns Follow Hide Create Post Older #designpatterns posts 1 2 3 4 5 6 7 8 9 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu The Coderpunk Crown: Why Moti Barski Dethroned Terry Davis owly owly owly Follow Jan 12 The Coderpunk Crown: Why Moti Barski Dethroned Terry Davis # designpatterns # templeos # coding Comments Add Comment 4 min read Observer Pattern Explained Simply With JavaScript Examples Arun Teja Arun Teja Arun Teja Follow Jan 11 Observer Pattern Explained Simply With JavaScript Examples # designpatterns # javascript # beginners # programming Comments Add Comment 3 min read Constructor Hell: Replacing Dependency Injection with Chain of Responsibility in Ruby andriy-baran andriy-baran andriy-baran Follow Jan 9 Constructor Hell: Replacing Dependency Injection with Chain of Responsibility in Ruby # rails # ruby # designpatterns # javascript Comments Add Comment 7 min read Here's what I'm doing to learn Design Patterns Vincent Cavanna Vincent Cavanna Vincent Cavanna Follow Jan 6 Here's what I'm doing to learn Design Patterns # gangof4 # designpatterns # programming # beginners 1 reaction Comments Add Comment 1 min read Adaptability Over Cleverness: What Makes Code Actually Good Steven Stuart Steven Stuart Steven Stuart Follow Jan 5 Adaptability Over Cleverness: What Makes Code Actually Good # architecture # bestpractices # designpatterns Comments Add Comment 2 min read Design Patterns in a Real-World Tkinter Application: From Lateral Coupling to Clean Architecture giuseppe costanzi giuseppe costanzi giuseppe costanzi Follow Jan 4 Design Patterns in a Real-World Tkinter Application: From Lateral Coupling to Clean Architecture # python # designpatterns # tkinter # architecture Comments Add Comment 6 min read Mastering the Factory Pattern in Laravel: Challenges, Solutions & Real-World Magic ✨ Laravel Mastery Laravel Mastery Laravel Mastery Follow Jan 4 Mastering the Factory Pattern in Laravel: Challenges, Solutions & Real-World Magic ✨ # webdev # programming # laravel # designpatterns Comments Add Comment 7 min read Builder Pattern in Java: Clear Examples and Real Application Eduardo Eduardo Eduardo Follow Dec 30 '25 Builder Pattern in Java: Clear Examples and Real Application # java # programming # designpatterns Comments Add Comment 5 min read Singleton Pattern Explained Simply With JavaScript Examples Arun Teja Arun Teja Arun Teja Follow Jan 11 Singleton Pattern Explained Simply With JavaScript Examples # beginners # javascript # designpatterns # programming Comments Add Comment 3 min read Publisher–Subscriber Pattern in JavaScript (Simple Implementation) Bobby Sadhwani Bobby Sadhwani Bobby Sadhwani Follow Dec 25 '25 Publisher–Subscriber Pattern in JavaScript (Simple Implementation) # javascript # designpatterns # eventdriven # pubsub Comments Add Comment 2 min read Strategy Pattern in Laravel: Clean Payment Processing Laravel Mastery Laravel Mastery Laravel Mastery Follow Jan 6 Strategy Pattern in Laravel: Clean Payment Processing # webdev # laravel # designpatterns # cleancode 1 reaction Comments Add Comment 2 min read Trocando de APM sem dor de cabeça Rodrigo Barreto Rodrigo Barreto Rodrigo Barreto Follow Dec 21 '25 Trocando de APM sem dor de cabeça # rails # ruby # designpatterns # apm 1 reaction Comments 1 comment 7 min read Switching APM providers without the headache Rodrigo Barreto Rodrigo Barreto Rodrigo Barreto Follow Dec 21 '25 Switching APM providers without the headache # rails # ruby # apm # designpatterns Comments Add Comment 7 min read Drupal Service Decorators : L'art de modifier l'existant sans tout casser DamienGR DamienGR DamienGR Follow Dec 19 '25 Drupal Service Decorators : L'art de modifier l'existant sans tout casser # french # drupal # designpatterns Comments Add Comment 8 min read Repository Pattern in Laravel: Clean Up Your Messy Code Laravel Mastery Laravel Mastery Laravel Mastery Follow Dec 28 '25 Repository Pattern in Laravel: Clean Up Your Messy Code # laravel # php # designpatterns # webdev Comments Add Comment 3 min read The Pattern Purist's Delusion: When Dogma Destroys Software Slavko Mihajlovic Slavko Mihajlovic Slavko Mihajlovic Follow Dec 16 '25 The Pattern Purist's Delusion: When Dogma Destroys Software # programming # designpatterns # softwareengineering Comments Add Comment 5 min read Building Reusable UI in React: Compound Components, Render Props, and API Design Ward Khaddour Ward Khaddour Ward Khaddour Follow Dec 26 '25 Building Reusable UI in React: Compound Components, Render Props, and API Design # react # designpatterns # typescript # compoundcomponents 1 reaction Comments Add Comment 9 min read Supporting 3 Databases with One Codebase: The Adapter Pattern Rohith Gilla Rohith Gilla Rohith Gilla Follow Dec 16 '25 Supporting 3 Databases with One Codebase: The Adapter Pattern # database # typescript # designpatterns # beginners 6 reactions Comments Add Comment 7 min read Simply Order (Part 9) — CQRS Pattern: Separating Reads from Writes for Better Performance Mohamed Hassan Mohamed Hassan Mohamed Hassan Follow Dec 8 '25 Simply Order (Part 9) — CQRS Pattern: Separating Reads from Writes for Better Performance # systemdesign # microservices # designpatterns # cqrs Comments Add Comment 6 min read 5 Patrones de Orquestación Multi-Agente que Funcionan en Producción (LangGraph) Abdessamad Ammi Abdessamad Ammi Abdessamad Ammi Follow Dec 9 '25 5 Patrones de Orquestación Multi-Agente que Funcionan en Producción (LangGraph) # agents # designpatterns # architecture # ai Comments Add Comment 5 min read A solid explanation to SOLID Principle Aman Kr Pandey Aman Kr Pandey Aman Kr Pandey Follow Dec 31 '25 A solid explanation to SOLID Principle # solidprinciples # designpatterns # lld # design 1 reaction Comments Add Comment 5 min read Agentic patterns and architectural approaches in AI websilvercraft websilvercraft websilvercraft Follow Dec 7 '25 Agentic patterns and architectural approaches in AI # designpatterns # ai # systemdesign # mcp 1 reaction Comments Add Comment 3 min read Adapter Pattern Explained with Real Examples Adrián Bailador Adrián Bailador Adrián Bailador Follow Dec 7 '25 Adapter Pattern Explained with Real Examples # csharp # dotnet # designpatterns # architecture Comments 2 comments 6 min read A Supplementary Analysis of Reversible Computation Theory for Programmers canonical canonical canonical Follow Dec 7 '25 A Supplementary Analysis of Reversible Computation Theory for Programmers # nop # programming # architecture # designpatterns Comments Add Comment 22 min read Understanding Proxy Patterns: The Why and How of Static and Dynamic Proxies in Java Rajat Arora Rajat Arora Rajat Arora Follow Dec 29 '25 Understanding Proxy Patterns: The Why and How of Static and Dynamic Proxies in Java # java # programming # designpatterns 1 reaction Comments Add Comment 6 min read loading... trending guides/resources 6 Must-Read Microservices and Design Patterns Books for Senior Developers Repository Pattern in Golang: A Practical Guide From Repetitive Code to Clean Architecture: How the Decorator Pattern Simplified Activity Logging... ⚡ CQRS & Use Cases (PHP): Why Your Service Layer is a Mess (And How to Fix It) Agentic patterns and architectural approaches in AI Circuit Breaking: A Love Story Between Laravel and RabbitMQ Repository Pattern vs Direct EF Core: The Great Debate Full resiliency guide for Spring Boot microservices — using all Resilience4j annotations Domain-Driven Design (DDD) Design Patterns #12: Let the Visitor In — A Deep Dive into the Visitor Pattern. Tutorial: Building a .NET 9 Console App with Hangfire and Channels Bringing Rust & Go-Inspired Functional Error Handling to TypeScript What is Declarative Programming Padrões de projeto no front-end? - Parte 1 Blog Post: Demystifying ZIO's Dependency Injection: A Practical Guide Supporting 3 Databases with One Codebase: The Adapter Pattern The Delete Button Dilemma: When to Soft Delete vs Hard Delete Hexagonal Architecture: Simple Introduction + Real-World Example 🧩 DAY 3 — Repository & Seed Data Setup (with Unit of Work) Day 3: Multi-Agent Systems - The Supervisor Pattern 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fsiy%2Fthe-underlying-process-of-request-processing-1od4&title=The%20Underlying%20Process%20of%20Request%20Processing&summary=Request%20processing%20is%20data%20transformation.%20When%20you%20think%20in%20data%20flow%2C%20sync%2Fasync%20and%20parallel%2Fsequential%20become%20transparent%20execution%20details.&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:06 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fkevburnsjr%2Fwebsockets-vs-long-polling-3a0o&title=WebSockets%20vs%20Long%20Polling&summary=A%20Comparison%20of%20Scalability%20Characteristics&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Stay updated on your professional world. Email or phone Password Show Forgot password? Keep me logged in Sign in or By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in with Apple Sign in with a passkey We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:06 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fed-wantuil%2Fcloud-sem-falencia-o-minimo-que-voce-precisa-saber-de-finops-8ao&title=Cloud%20Sem%20Fal%C3%AAncia%3A%20O%20m%C3%ADnimo%20que%20voc%C3%AA%20precisa%20saber%20de%20FinOps&summary=Imagine%20a%20cena%3A%20voc%C3%AA%20trabalha%20em%20uma%20empresa%20consolidada.%20Voc%C3%AAs%20t%C3%AAm%20aquele%20rack%20de%20servidores%20f%C3%ADsicos...&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:06 |
https://dev.to/t/ai/page/77 | Artificial Intelligence Page 77 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Artificial Intelligence Follow Hide Artificial intelligence leverages computers and machines to mimic the problem-solving and decision-making capabilities found in humans and in nature. Create Post submission guidelines Posts about artificial intelligence. Older #ai posts 74 75 76 77 78 79 80 81 82 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu How the Creator of Claude Code Actually Uses It Ashok Naik Ashok Naik Ashok Naik Follow Jan 6 How the Creator of Claude Code Actually Uses It # ai # productivity # claudecode # devtools 1 reaction Comments Add Comment 3 min read A Senior Engineer’s Guide to Securing and Scaling Model Context Protocol (MCP) OnlineProxy OnlineProxy OnlineProxy Follow Dec 22 '25 A Senior Engineer’s Guide to Securing and Scaling Model Context Protocol (MCP) # programming # ai # beginners # tutorial Comments Add Comment 7 min read Stop Paying for OpenAI: Build Your Own Local RAG Pipeline in Python- a PDF Chatbot Niyati Gupta Niyati Gupta Niyati Gupta Follow Dec 28 '25 Stop Paying for OpenAI: Build Your Own Local RAG Pipeline in Python- a PDF Chatbot # ai # python 1 reaction Comments Add Comment 11 min read New to this Community Salman Ahmad Salman Ahmad Salman Ahmad Follow Dec 24 '25 New to this Community # webdev # programming # ai # javascript Comments Add Comment 1 min read Speedrun your AI coding workflow.⚡️ rx76d rx76d rx76d Follow Dec 23 '25 Speedrun your AI coding workflow.⚡️ # ai # productivity # opensource # npm Comments Add Comment 1 min read Boosting Developer Productivity with AI: What the Data Really Says Fay Fay Fay Follow Dec 27 '25 Boosting Developer Productivity with AI: What the Data Really Says # ai # productivity # developers # programming Comments Add Comment 3 min read The Hidden Costs of Inefficient AI Agents (And How to Fix Them) shashank agarwal shashank agarwal shashank agarwal Follow Dec 24 '25 The Hidden Costs of Inefficient AI Agents (And How to Fix Them) # webdev # ai # programming # devops Comments 1 comment 2 min read How I Built a Stroke Capture System for an AI Drawing Game Adam Adam Adam Follow Dec 22 '25 How I Built a Stroke Capture System for an AI Drawing Game # showdev # gamedev # webdev # ai Comments Add Comment 2 min read Rule of Two Piece Mathew Pregasen Mathew Pregasen Mathew Pregasen Follow Dec 24 '25 Rule of Two Piece # ai # security # llm # authorization Comments 1 comment 7 min read Architecting Enterprise grade Multi‑Agent AI with AWS Strands & Amazon Bedrock AgentCore Seenivasa Ramadurai Seenivasa Ramadurai Seenivasa Ramadurai Follow Dec 27 '25 Architecting Enterprise grade Multi‑Agent AI with AWS Strands & Amazon Bedrock AgentCore # architecture # ai # agents # aws 2 reactions Comments Add Comment 7 min read Qwen-Image-2512 vs. Z-Image Turbo: 5-Prompt Benchmark - Which Model is Better? Garyvov Garyvov Garyvov Follow Jan 5 Qwen-Image-2512 vs. Z-Image Turbo: 5-Prompt Benchmark - Which Model is Better? # ai # performance # promptengineering Comments Add Comment 5 min read THE SKETCH Lisa Girlinghouse Lisa Girlinghouse Lisa Girlinghouse Follow Jan 6 THE SKETCH # ai # devchallenge # machinelearning # portfolio Comments Add Comment 2 min read How Amazon Protects User Privacy in Advertising Mehwish Malik Mehwish Malik Mehwish Malik Follow Dec 23 '25 How Amazon Protects User Privacy in Advertising # aws # awschallenge # ai # webdev 10 reactions Comments Add Comment 3 min read AI should not be in Code Editors Badr chanaa Badr chanaa Badr chanaa Follow Jan 10 AI should not be in Code Editors # discuss # programming # ai # productivity 11 reactions Comments 15 comments 2 min read Auto-loading .nvmrc in JetBrains Junie terminal David Haley David Haley David Haley Follow Dec 23 '25 Auto-loading .nvmrc in JetBrains Junie terminal # ai # jetbrains # programming # shell Comments Add Comment 2 min read Z-Image Turbo Quantized: Complete Guide to Running Professional AI Image Generation on Low VRAM GPUs Garyvov Garyvov Garyvov Follow Jan 5 Z-Image Turbo Quantized: Complete Guide to Running Professional AI Image Generation on Low VRAM GPUs # ai # performance # tutorial Comments Add Comment 10 min read Using the Reinforcement Learning GitHub Package Dipti M Dipti M Dipti M Follow Dec 23 '25 Using the Reinforcement Learning GitHub Package # webdev # programming # ai # beginners Comments Add Comment 4 min read Forward and Backward Propagation In Neural Networks likhitha manikonda likhitha manikonda likhitha manikonda Follow Dec 23 '25 Forward and Backward Propagation In Neural Networks # ai # machinelearning # tensorflow # beginners Comments Add Comment 3 min read Building a YouTube Automation System with Claude AI: From News to Shorts in Minutes Trollz1004 Trollz1004 Trollz1004 Follow Dec 23 '25 Building a YouTube Automation System with Claude AI: From News to Shorts in Minutes # ai # automation # youtube # node Comments Add Comment 2 min read Day 35 of improving my Data Science skills Sylvester Promise Sylvester Promise Sylvester Promise Follow Dec 27 '25 Day 35 of improving my Data Science skills # ai # productivity # tutorial # opensource Comments Add Comment 2 min read Are custom decentralised app the future? Sachit Sachit Sachit Follow Dec 23 '25 Are custom decentralised app the future? # webdev # javascript # ai # fitness Comments Add Comment 4 min read 4 Days, 18,599 Lines: What Happens When You Go All-In on Pure C Dmitry Labintcev Dmitry Labintcev Dmitry Labintcev Follow Jan 5 4 Days, 18,599 Lines: What Happens When You Go All-In on Pure C # c # security # ai # opensource Comments Add Comment 5 min read Why Most Small Businesses Overpay for Cloud Servers (And How to Avoid It) Vamsi Vamsi Vamsi Follow Dec 23 '25 Why Most Small Businesses Overpay for Cloud Servers (And How to Avoid It) # webdev # ai # heroku # programming Comments Add Comment 4 min read 10 Website Features Clients Always Ask For (But Rarely Use) Dev. Resources Dev. Resources Dev. Resources Follow Dec 27 '25 10 Website Features Clients Always Ask For (But Rarely Use) # webdev # programming # ai # beginners 7 reactions Comments Add Comment 9 min read Context Rot: Why AI Forgets Your Perfect Prompts Kourtney Meiss Kourtney Meiss Kourtney Meiss Follow Dec 22 '25 Context Rot: Why AI Forgets Your Perfect Prompts # ai # productivity # learning # tooling Comments Add Comment 2 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/t/web3/page/208 | Web3 Page 208 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Web3 Follow Hide Web3 refers to the next generation of the internet that leverages blockchain technology to enable decentralized and trustless systems for financial transactions, data storage, and other applications. Create Post Older #web3 posts 205 206 207 208 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://docs.python.org/3/license.html#strtod-and-dtoa | History and License — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents History and License History of the software Terms and conditions for accessing or otherwise using Python PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION Licenses and Acknowledgements for Incorporated Software Mersenne Twister Sockets Asynchronous socket services Cookie management Execution tracing UUencode and UUdecode functions XML Remote Procedure Calls test_epoll Select kqueue SipHash24 strtod and dtoa OpenSSL expat libffi zlib cfuhash libmpdec W3C C14N test suite mimalloc asyncio Global Unbounded Sequences (GUS) Zstandard bindings Previous topic Copyright This page Report a bug Show source Navigation index modules | previous | Python » 3.14.2 Documentation » History and License | Theme Auto Light Dark | History and License ¶ History of the software ¶ Python was created in the early 1990s by Guido van Rossum at Stichting Mathematisch Centrum (CWI, see https://www.cwi.nl ) in the Netherlands as a successor of a language called ABC. Guido remains Python’s principal author, although it includes many contributions from others. In 1995, Guido continued his work on Python at the Corporation for National Research Initiatives (CNRI, see https://www.cnri.reston.va.us ) in Reston, Virginia where he released several versions of the software. In May 2000, Guido and the Python core development team moved to BeOpen.com to form the BeOpen PythonLabs team. In October of the same year, the PythonLabs team moved to Digital Creations, which became Zope Corporation. In 2001, the Python Software Foundation (PSF, see https://www.python.org/psf/ ) was formed, a non-profit organization created specifically to own Python-related Intellectual Property. Zope Corporation was a sponsoring member of the PSF. All Python releases are Open Source (see https://opensource.org for the Open Source Definition). Historically, most, but not all, Python releases have also been GPL-compatible; the table below summarizes the various releases. Release Derived from Year Owner GPL-compatible? (1) 0.9.0 thru 1.2 n/a 1991-1995 CWI yes 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes 1.6 1.5.2 2000 CNRI no 2.0 1.6 2000 BeOpen.com no 1.6.1 1.6 2001 CNRI yes (2) 2.1 2.0+1.6.1 2001 PSF no 2.0.1 2.0+1.6.1 2001 PSF yes 2.1.1 2.1+2.0.1 2001 PSF yes 2.1.2 2.1.1 2002 PSF yes 2.1.3 2.1.2 2002 PSF yes 2.2 and above 2.1.1 2001-now PSF yes Note GPL-compatible doesn’t mean that we’re distributing Python under the GPL. All Python licenses, unlike the GPL, let you distribute a modified version without making your changes open source. The GPL-compatible licenses make it possible to combine Python with other software that is released under the GPL; the others don’t. According to Richard Stallman, 1.6.1 is not GPL-compatible, because its license has a choice of law clause. According to CNRI, however, Stallman’s lawyer has told CNRI’s lawyer that 1.6.1 is “not incompatible” with the GPL. Thanks to the many outside volunteers who have worked under Guido’s direction to make these releases possible. Terms and conditions for accessing or otherwise using Python ¶ Python software and documentation are licensed under the Python Software Foundation License Version 2. Starting with Python 3.8.6, examples, recipes, and other code in the documentation are dual licensed under the PSF License Version 2 and the Zero-Clause BSD license . Some software incorporated into Python is under different licenses. The licenses are listed with code falling under that license. See Licenses and Acknowledgements for Incorporated Software for an incomplete list of these licenses. PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 ¶ 1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using this software ("Python") in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative version, provided, however, that PSF's License Agreement and PSF's notice of copyright, i.e., "Copyright © 2001 Python Software Foundation; All Rights Reserved" are retained in Python alone or in any derivative version prepared by Licensee. 3. In the event Licensee prepares a derivative work that is based on or incorporates Python or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python. 4. PSF is making Python available to Licensee on an "AS IS" basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between PSF and Licensee. This License Agreement does not grant permission to use PSF trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By copying, installing or otherwise using Python, Licensee agrees to be bound by the terms and conditions of this License Agreement. BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 ¶ BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the Individual or Organization ("Licensee") accessing and otherwise using this software in source or binary form and its associated documentation ("the Software"). 2. Subject to the terms and conditions of this BeOpen Python License Agreement, BeOpen hereby grants Licensee a non-exclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use the Software alone or in any derivative version, provided, however, that the BeOpen Python License is retained in the Software, alone or in any derivative version prepared by Licensee. 3. BeOpen is making the Software available to Licensee on an "AS IS" basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 5. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 6. This License Agreement shall be governed by and interpreted in all respects by the law of the State of California, excluding conflict of law provisions. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between BeOpen and Licensee. This License Agreement does not grant permission to use BeOpen trademarks or trade names in a trademark sense to endorse or promote products or services of Licensee, or any third party. As an exception, the "BeOpen Python" logos available at http://www.pythonlabs.com/logos.html may be used according to the permissions granted on that web page. 7. By copying, installing or otherwise using the software, Licensee agrees to be bound by the terms and conditions of this License Agreement. CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 ¶ 1. This LICENSE AGREEMENT is between the Corporation for National Research Initiatives, having an office at 1895 Preston White Drive, Reston, VA 20191 ("CNRI"), and the Individual or Organization ("Licensee") accessing and otherwise using Python 1.6.1 software in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, CNRI hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python 1.6.1 alone or in any derivative version, provided, however, that CNRI's License Agreement and CNRI's notice of copyright, i.e., "Copyright © 1995-2001 Corporation for National Research Initiatives; All Rights Reserved" are retained in Python 1.6.1 alone or in any derivative version prepared by Licensee. Alternately, in lieu of CNRI's License Agreement, Licensee may substitute the following text (omitting the quotes): "Python 1.6.1 is made available subject to the terms and conditions in CNRI's License Agreement. This Agreement together with Python 1.6.1 may be located on the internet using the following unique, persistent identifier (known as a handle): 1895.22/1013. This Agreement may also be obtained from a proxy server on the internet using the following URL: http://hdl.handle.net/1895.22/1013". 3. In the event Licensee prepares a derivative work that is based on or incorporates Python 1.6.1 or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python 1.6.1. 4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. This License Agreement shall be governed by the federal intellectual property law of the United States, including without limitation the federal copyright law, and, to the extent such U.S. federal law does not apply, by the law of the Commonwealth of Virginia, excluding Virginia's conflict of law provisions. Notwithstanding the foregoing, with regard to derivative works based on Python 1.6.1 that incorporate non-separable material that was previously distributed under the GNU General Public License (GPL), the law of the Commonwealth of Virginia shall govern this License Agreement only as to issues arising under or with respect to Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between CNRI and Licensee. This License Agreement does not grant permission to use CNRI trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By clicking on the "ACCEPT" button where indicated, or by copying, installing or otherwise using Python 1.6.1, Licensee agrees to be bound by the terms and conditions of this License Agreement. CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 ¶ Copyright © 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON DOCUMENTATION ¶ Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Licenses and Acknowledgements for Incorporated Software ¶ This section is an incomplete, but growing list of licenses and acknowledgements for third-party software incorporated in the Python distribution. Mersenne Twister ¶ The _random C extension underlying the random module includes code based on a download from http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/MT2002/emt19937ar.html . The following are the verbatim comments from the original code: A C-program for MT19937, with initialization improved 2002/1/26. Coded by Takuji Nishimura and Makoto Matsumoto. Before using, initialize the state by using init_genrand(seed) or init_by_array(init_key, key_length). Copyright (C) 1997 - 2002, Makoto Matsumoto and Takuji Nishimura, All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The names of its contributors may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Any feedback is very welcome. http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html email: m-mat @ math.sci.hiroshima-u.ac.jp (remove space) Sockets ¶ The socket module uses the functions, getaddrinfo() , and getnameinfo() , which are coded in separate source files from the WIDE Project, https://www.wide.ad.jp/ . Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Asynchronous socket services ¶ The test.support.asynchat and test.support.asyncore modules contain the following notice: Copyright 1996 by Sam Rushing All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Sam Rushing not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Cookie management ¶ The http.cookies module contains the following notice: Copyright 2000 by Timothy O'Malley <timo@alum.mit.edu> All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Timothy O'Malley not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Timothy O'Malley DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL Timothy O'Malley BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Execution tracing ¶ The trace module contains the following notice: portions copyright 2001, Autonomous Zones Industries, Inc., all rights... err... reserved and offered to the public under the terms of the Python 2.2 license. Author: Zooko O'Whielacronx http://zooko.com/ mailto:zooko@zooko.com Copyright 2000, Mojam Media, Inc., all rights reserved. Author: Skip Montanaro Copyright 1999, Bioreason, Inc., all rights reserved. Author: Andrew Dalke Copyright 1995-1997, Automatrix, Inc., all rights reserved. Author: Skip Montanaro Copyright 1991-1995, Stichting Mathematisch Centrum, all rights reserved. Permission to use, copy, modify, and distribute this Python software and its associated documentation for any purpose without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of neither Automatrix, Bioreason or Mojam Media be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. UUencode and UUdecode functions ¶ The uu codec contains the following notice: Copyright 1994 by Lance Ellinghouse Cathedral City, California Republic, United States of America. All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Lance Ellinghouse not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Modified by Jack Jansen, CWI, July 1995: - Use binascii module to do the actual line-by-line conversion between ascii and binary. This results in a 1000-fold speedup. The C version is still 5 times faster, though. - Arguments more compliant with Python standard XML Remote Procedure Calls ¶ The xmlrpc.client module contains the following notice: The XML-RPC client interface is Copyright (c) 1999-2002 by Secret Labs AB Copyright (c) 1999-2002 by Fredrik Lundh By obtaining, using, and/or copying this software and/or its associated documentation, you agree that you have read, understood, and will comply with the following terms and conditions: Permission to use, copy, modify, and distribute this software and its associated documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Secret Labs AB or the author not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT- ABILITY AND FITNESS. IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. test_epoll ¶ The test.test_epoll module contains the following notice: Copyright (c) 2001-2006 Twisted Matrix Laboratories. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Select kqueue ¶ The select module contains the following notice for the kqueue interface: Copyright (c) 2000 Doug White, 2006 James Knight, 2007 Christian Heimes All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SipHash24 ¶ The file Python/pyhash.c contains Marek Majkowski’ implementation of Dan Bernstein’s SipHash24 algorithm. It contains the following note: <MIT License> Copyright (c) 2013 Marek Majkowski <marek@popcount.org> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. </MIT License> Original location: https://github.com/majek/csiphash/ Solution inspired by code from: Samuel Neves (supercop/crypto_auth/siphash24/little) djb (supercop/crypto_auth/siphash24/little2) Jean-Philippe Aumasson (https://131002.net/siphash/siphash24.c) strtod and dtoa ¶ The file Python/dtoa.c , which supplies C functions dtoa and strtod for conversion of C doubles to and from strings, is derived from the file of the same name by David M. Gay, currently available from https://web.archive.org/web/20220517033456/http://www.netlib.org/fp/dtoa.c . The original file, as retrieved on March 16, 2009, contains the following copyright and licensing notice: /**************************************************************** * * The author of this software is David M. Gay. * * Copyright (c) 1991, 2000, 2001 by Lucent Technologies. * * Permission to use, copy, modify, and distribute this software for any * purpose without fee is hereby granted, provided that this entire notice * is included in all copies of any software which is or includes a copy * or modification of this software and in all copies of the supporting * documentation for such software. * * THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED * WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY * REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY * OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. * ***************************************************************/ OpenSSL ¶ The modules hashlib , posix and ssl use the OpenSSL library for added performance if made available by the operating system. Additionally, the Windows and macOS installers for Python may include a copy of the OpenSSL libraries, so we include a copy of the OpenSSL license here. For the OpenSSL 3.0 release, and later releases derived from that, the Apache License v2 applies: Apache License Version 2.0, January 2004 https://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS expat ¶ The pyexpat extension is built using an included copy of the expat sources unless the build is configured --with-system-expat : Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd and Clark Cooper Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. libffi ¶ The _ctypes C extension underlying the ctypes module is built using an included copy of the libffi sources unless the build is configured --with-system-libffi : Copyright (c) 1996-2008 Red Hat, Inc and others. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. zlib ¶ The zlib extension is built using an included copy of the zlib sources if the zlib version found on the system is too old to be used for the build: Copyright (C) 1995-2011 Jean-loup Gailly and Mark Adler This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly Mark Adler jloup@gzip.org madler@alumni.caltech.edu cfuhash ¶ The implementation of the hash table used by the tracemalloc is based on the cfuhash project: Copyright (c) 2005 Don Owens All rights reserved. This code is released under the BSD license: Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. libmpdec ¶ The _decimal C extension underlying the decimal module is built using an included copy of the libmpdec library unless the build is configured --with-system-libmpdec : Copyright (c) 2008-2020 Stefan Krah. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. W3C C14N test suite ¶ The C14N 2.0 test suite in the test package ( Lib/test/xmltestdata/c14n-20/ ) was retrieved from the W3C website at https://www.w3.org/TR/xml-c14n2-testcases/ and is distributed under the 3-clause BSD license: Copyright (c) 2013 W3C(R) (MIT, ERCIM, Keio, Beihang), All Rights Reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of works must retain the original copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the original copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the W3C nor the names of its contributors may be used to endorse or promote products derived from this work without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. mimalloc ¶ MIT License: Copyright (c) 2018-2021 Microsoft Corporation, Daan Leijen Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. asyncio ¶ Parts of the asyncio module are incorporated from uvloop 0.16 , which is distributed under the MIT license: Copyright (c) 2015-2021 MagicStack Inc. http://magic.io Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Global Unbounded Sequences (GUS) ¶ The file Python/qsbr.c is adapted from FreeBSD’s “Global Unbounded Sequences” safe memory reclamation scheme in subr_smr.c . The file is distributed under the 2-Clause BSD License: Copyright (c) 2019,2020 Jeffrey Roberson <jeff@FreeBSD.org> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following con | 2026-01-13T08:49:06 |
https://dev.to/srikarsunchu/i-got-tired-of-waiting-for-gradle-so-i-built-a-runtime-that-runs-kotlin-like-python-10nl#why-this-matters | I got tired of waiting for Gradle, so I built a runtime that runs Kotlin like Python. - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Srikar Sunchu Posted on Jan 13 I got tired of waiting for Gradle, so I built a runtime that runs Kotlin like Python. # kotlin # performance # productivity # tooling I hit ./gradlew run and alt-tab to Discord. By the time I tab back, it's still resolving dependencies. This is a script. It's 40 lines. So I helped build something that doesn't make me wait. Elide . What is Elide? Elide is a runtime. Like Node. Like Python. You install it, you run code. curl -sSL elide.sh | bash Enter fullscreen mode Exit fullscreen mode But here's the thing: it doesn't just run one language. elide run app.kt # Kotlin, no Gradle elide run server.ts # TypeScript, no build step elide run script.py # Python, faster than CPython Enter fullscreen mode Exit fullscreen mode One binary. One toolchain. Multiple languages. Why this matters Most teams aren't single-language. You've got TypeScript on the frontend, Python for ML scripts, maybe Kotlin or Java somewhere in the backend. That's three runtimes, three package managers, three sets of problems. Elide is one runtime that speaks all of them. Install dependencies from npm and Maven in the same project. Run tests across languages with one command. No context switching. How it works Elide is built on GraalVM. The same compiler optimizes across languages-JavaScript, Python, Kotlin. No serialization when crossing language boundaries. All in one engine. What you can do today elide run — run code in any supported language elide test — run tests with built-in coverage elide install — fetch from npm or Maven elide serve — spin up a fast polyglot server Drop-in Gradle plugin for existing Java/Kotlin projects Try it Elide is in beta. curl -sSL elide.sh | bash Enter fullscreen mode Exit fullscreen mode We're on Discord if you want to talk, report bugs, or tell us what we're missing. Here's our Github - if you've read this far, leave us a star :) Top comments (1) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Baasil Ali Baasil Ali Baasil Ali Follow Joined Jan 13, 2026 • Jan 13 Dropdown menu Copy link Hide This is so sick! Like comment: Like comment: 2 likes Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Srikar Sunchu Follow Design engineer at Elide, where we're making Kotlin run like Python. I write about dev tools, terminal UIs, and why your build is too slow. Location San Francisco Work Design Engineer @ Elide Joined Jan 12, 2026 Trending on DEV Community Hot From CDN to Pixel: A React App's Journey # react # programming # webdev # performance What was your win this week??? # weeklyretro # discuss How to Crack Any Software Developer Interview in 2026 (Updated for AI & Modern Hiring) # softwareengineering # programming # career # interview 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Faws-builders%2Fhow-i-troubleshoot-an-ec2-instance-in-the-real-world-using-instance-diagnostics-3dk8&title=%F0%9F%A9%BA%20How%20I%20Troubleshoot%20an%20EC2%20Instance%20in%20the%20Real%20World%20%28Using%20Instance%20Diagnostics%29&summary=When%20an%20EC2%20instance%20starts%20misbehaving%2C%20my%20first%20reaction%20is%20not%20to%20SSH%20into%20it%20or%20reboot%20it....&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:06 |
https://dev.to/t/async | Async - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close # async Follow Hide Create Post Older #async posts 1 2 3 4 5 6 7 8 9 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Why Your @Async Method Ignores @Transactional (And Leaks Internal Errors) Anand Rathnas Anand Rathnas Anand Rathnas Follow Jan 4 Why Your @Async Method Ignores @Transactional (And Leaks Internal Errors) # java # springboot # async # transactions Comments Add Comment 4 min read Part 2 - Performance & Concurrency Essentials in C#: Memory, Async, and High-Performance Primitives Seigo Kitamura Seigo Kitamura Seigo Kitamura Follow Jan 7 Part 2 - Performance & Concurrency Essentials in C#: Memory, Async, and High-Performance Primitives # csharp # performance # async # concurrency Comments Add Comment 3 min read Mastering RabbitMQ in Microservices: A JavaScript Guide to Async Magic Harsh Mishra Harsh Mishra Harsh Mishra Follow Dec 31 '25 Mastering RabbitMQ in Microservices: A JavaScript Guide to Async Magic # rabbitmq # async # microservices # tutorial Comments Add Comment 10 min read Kotlin 코루틴: 비동기 프로그래밍 dss99911 dss99911 dss99911 Follow Dec 31 '25 Kotlin 코루틴: 비동기 프로그래밍 # programming # kotlin # coroutine # async Comments Add Comment 1 min read JavaScript Async, AJAX, and JSONP - Handling Asynchronous Operations dss99911 dss99911 dss99911 Follow Dec 30 '25 JavaScript Async, AJAX, and JSONP - Handling Asynchronous Operations # frontend # javascript # async # ajax Comments Add Comment 3 min read Designing type-safe sync/async mode support in TypeScript Hong Minhee Hong Minhee Hong Minhee Follow Jan 2 Designing type-safe sync/async mode support in TypeScript # typescript # cli # programming # async 2 reactions Comments Add Comment 8 min read Global Error Handling in SwiftUI Sebastien Lato Sebastien Lato Sebastien Lato Follow Dec 9 '25 Global Error Handling in SwiftUI # swiftui # architecture # errors # async Comments Add Comment 3 min read SwiftUI Async & Concurrency Patterns Sebastien Lato Sebastien Lato Sebastien Lato Follow Dec 4 '25 SwiftUI Async & Concurrency Patterns # swiftui # concurrency # async # architecture Comments Add Comment 3 min read Building an Effect Runtime in TypeScript: My little detour into Fibers and Structured Concurrency Augusto Vivaldelli Augusto Vivaldelli Augusto Vivaldelli Follow Dec 7 '25 Building an Effect Runtime in TypeScript: My little detour into Fibers and Structured Concurrency # javascript # async # programming # experiments Comments Add Comment 5 min read How Do I Return the Response from an Asynchronous Call? Prashant Sharma Prashant Sharma Prashant Sharma Follow Nov 28 '25 How Do I Return the Response from an Asynchronous Call? # javascript # async # promises # webdev Comments Add Comment 1 min read How I Ended Up Building a Stable Async Processor for n8n (and Turned It Into a PRO Tempate) Emre Akman Emre Akman Emre Akman Follow Nov 15 '25 How I Ended Up Building a Stable Async Processor for n8n (and Turned It Into a PRO Tempate) # n8n # automation # async # developers Comments 1 comment 2 min read From 'Why the F@&k Do I Need This?' to 'Oh, That's Why' - My GAT Journey Illia Illia Illia Follow Nov 7 '25 From 'Why the F@&k Do I Need This?' to 'Oh, That's Why' - My GAT Journey # rust # async # gat # beginners Comments Add Comment 12 min read Understanding Python Async Patterns: Basics Ravi Ravi Ravi Follow Nov 8 '25 Understanding Python Async Patterns: Basics # python # async # patterns Comments Add Comment 4 min read Ability to Create Async Commands in WebForms Core 2 Elanat Framework Elanat Framework Elanat Framework Follow Nov 11 '25 Ability to Create Async Commands in WebForms Core 2 # performance # architecture # async # webformscore Comments Add Comment 2 min read Key Differences Between setImmediate() and process.nextTick() in Node.js Jeferson Eiji Jeferson Eiji Jeferson Eiji Follow Dec 10 '25 Key Differences Between setImmediate() and process.nextTick() in Node.js # node # javascript # async # eventloop 1 reaction Comments Add Comment 1 min read A Deep Dive into Multi-Transport Protocol Abstraction in Python Tosin Akinosho Tosin Akinosho Tosin Akinosho Follow Nov 4 '25 A Deep Dive into Multi-Transport Protocol Abstraction in Python # python # designpatterns # async Comments Add Comment 6 min read RAP Framework for Asynchronous Work sta sta sta Follow Dec 6 '25 RAP Framework for Asynchronous Work # asynccommunication # asyncwork # async # communication Comments Add Comment 5 min read Cancelable async tasks and typed server errors with SolidJS and LazyPromise Ivan Novikov Ivan Novikov Ivan Novikov Follow Dec 4 '25 Cancelable async tasks and typed server errors with SolidJS and LazyPromise # solidjs # typescript # async # javascript Comments Add Comment 4 min read Full Async sta sta sta Follow Nov 24 '25 Full Async # workstyle # async # communication # tealorganization Comments Add Comment 9 min read Full-Four: Full Remote, Full Flex, Full Async, Full Mask sta sta sta Follow Nov 24 '25 Full-Four: Full Remote, Full Flex, Full Async, Full Mask # remote # flex # async # workstyle Comments Add Comment 2 min read Entendendo Sícrono vs Assíncrono: Threads, Await e Performance Iana Sampaio Iana Sampaio Iana Sampaio Follow Nov 20 '25 Entendendo Sícrono vs Assíncrono: Threads, Await e Performance # programming # síncrono # assíncrono # async 4 reactions Comments 1 comment 6 min read C# Async/Await in .NET 10: The Complete Technical Guide for 2025 IronSoftware IronSoftware IronSoftware Follow Nov 20 '25 C# Async/Await in .NET 10: The Complete Technical Guide for 2025 # webdev # csharp # programming # async Comments 1 comment 8 min read Architectural vs Transport Asynchrony: What Most Engineers Get Wrong About Async Systems Sergey Yungman Sergey Yungman Sergey Yungman Follow Oct 10 '25 Architectural vs Transport Asynchrony: What Most Engineers Get Wrong About Async Systems # architecture # microservices # async # distributedsystems Comments Add Comment 5 min read What Are Webhooks, and How Do You Implement Them? uma victor uma victor uma victor Follow for Flutterwave Engineering Nov 7 '25 What Are Webhooks, and How Do You Implement Them? # webhooks # fintech # async # eventdriven 26 reactions Comments 1 comment 10 min read Sistema de Archivos (fs) en Node.js Pedro Alvarado Pedro Alvarado Pedro Alvarado Follow Oct 3 '25 Sistema de Archivos (fs) en Node.js # filesystem # async Comments Add Comment 20 min read loading... trending guides/resources C# Async/Await in .NET 10: The Complete Technical Guide for 2025 What Are Webhooks, and How Do You Implement Them? Global Error Handling in SwiftUI How Do I Return the Response from an Asynchronous Call? Full-Four: Full Remote, Full Flex, Full Async, Full Mask Understanding Python Async Patterns: Basics Ability to Create Async Commands in WebForms Core 2 Kotlin 코루틴: 비동기 프로그래밍 Cancelable async tasks and typed server errors with SolidJS and LazyPromise RAP Framework for Asynchronous Work Key Differences Between setImmediate() and process.nextTick() in Node.js Designing type-safe sync/async mode support in TypeScript Part 2 - Performance & Concurrency Essentials in C#: Memory, Async, and High-Performance Primitives SwiftUI Async & Concurrency Patterns Mastering RabbitMQ in Microservices: A JavaScript Guide to Async Magic Building an Effect Runtime in TypeScript: My little detour into Fibers and Structured Concurrency JavaScript Async, AJAX, and JSONP - Handling Asynchronous Operations A Deep Dive into Multi-Transport Protocol Abstraction in Python Why Your @Async Method Ignores @Transactional (And Leaks Internal Errors) How I Ended Up Building a Stable Async Processor for n8n (and Turned It Into a PRO Tempate) 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fflo152121063061%2Fi-tried-to-capture-system-audio-in-the-browser-heres-what-i-learned-1f99&title=I%20tried%20to%20capture%20system%20audio%20in%20the%20browser.%20Here%27s%20what%20I%20learned.&summary=I%27m%20building%20LiveSuggest%2C%20a%20real-time%20AI%20assistant%20that%20listens%20to%20your%20meetings%20and%20gives%20you...&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:06 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fmissamarakay%2Ffollowing-cooking-recipes-makes-you-a-clearer-writer-460a&title=Following%20Cooking%20Recipes%20Makes%20You%20a%20Clearer%20Writer&summary=Some%20tips%20to%20help%20you%20write%20clearer%20technical%20content%20by%20looking%20at%20cooking%20recipes.&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:06 |
https://dev.to/t/ai/page/79 | Artificial Intelligence Page 79 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Artificial Intelligence Follow Hide Artificial intelligence leverages computers and machines to mimic the problem-solving and decision-making capabilities found in humans and in nature. Create Post submission guidelines Posts about artificial intelligence. Older #ai posts 76 77 78 79 80 81 82 83 84 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu ✨ Starting 2026 with a builder’s mindset ✨ Prashant Lakhera Prashant Lakhera Prashant Lakhera Follow Dec 23 '25 ✨ Starting 2026 with a builder’s mindset ✨ # ai # llm # gpt3 # programming Comments Add Comment 1 min read Add authentication to your Nuxt 3 and Vue 3 applications (Logto) Alex Kernel Alex Kernel Alex Kernel Follow Dec 22 '25 Add authentication to your Nuxt 3 and Vue 3 applications (Logto) # webdev # programming # ai # beginners Comments Add Comment 5 min read Seamless Real-Time Multilingual Communication with Language Detection: My Journey CallStack Tech CallStack Tech CallStack Tech Follow Dec 22 '25 Seamless Real-Time Multilingual Communication with Language Detection: My Journey # ai # tutorial # webdev # programming Comments Add Comment 11 min read Launching CertPing, Managed SSL Certificates Seaionl Seaionl Seaionl Follow Dec 23 '25 Launching CertPing, Managed SSL Certificates # webdev # ai # cybersecurity # devops Comments Add Comment 1 min read From Messy HTML to AI-Ready News Apps with Firecrawl + Lovable Etop - Essien Emmanuella Ubokabasi Etop - Essien Emmanuella Ubokabasi Etop - Essien Emmanuella Ubokabasi Follow Jan 6 From Messy HTML to AI-Ready News Apps with Firecrawl + Lovable # firecrawl # webscraping # nocode # ai Comments 1 comment 3 min read Agentic CMS: Redefining Content Management for the Future Nick Peterson Nick Peterson Nick Peterson Follow Dec 22 '25 Agentic CMS: Redefining Content Management for the Future # ai # djangocms # frontend # agenticpostgreschallenge Comments Add Comment 7 min read Early adoption is the key to AI coding success Darko from Kilo Darko from Kilo Darko from Kilo Follow Dec 22 '25 Early adoption is the key to AI coding success # discuss # ai # coding Comments Add Comment 5 min read Activation Functions: How Simple Curves Power Neural Networks Rijul Rajesh Rijul Rajesh Rijul Rajesh Follow Dec 23 '25 Activation Functions: How Simple Curves Power Neural Networks # ai # machinelearning # rnn # neuralnetwork 10 reactions Comments Add Comment 3 min read Why I’m building a Windows-first emotional AI assistant (lessons so far) Anna Jambhulkar Anna Jambhulkar Anna Jambhulkar Follow Dec 22 '25 Why I’m building a Windows-first emotional AI assistant (lessons so far) # ai # saas # productivity # automation Comments Add Comment 2 min read Adding Cryptographic Audit Trails to FIX Without Touching Your Trading Engine VeritasChain Standards Organization (VSO) VeritasChain Standards Organization (VSO) VeritasChain Standards Organization (VSO) Follow Dec 22 '25 Adding Cryptographic Audit Trails to FIX Without Touching Your Trading Engine # fix # cryptocurrency # fintech # ai Comments Add Comment 4 min read Building a RAG based agent using DronaHQ Gayatri Sachdeva Gayatri Sachdeva Gayatri Sachdeva Follow Dec 22 '25 Building a RAG based agent using DronaHQ # rag # agents # ai # nocode Comments Add Comment 8 min read Understanding How ChatGPT Produces Human-Like Responses Shamim Ali Shamim Ali Shamim Ali Follow Jan 6 Understanding How ChatGPT Produces Human-Like Responses # webdev # ai # chatgpt # openai Comments Add Comment 2 min read Minion Framework Already Implements PTC: Agent Architecture Beyond Traditional Tool Calling femto Zheng femto Zheng femto Zheng Follow Dec 22 '25 Minion Framework Already Implements PTC: Agent Architecture Beyond Traditional Tool Calling # agents # llm # architecture # ai Comments Add Comment 9 min read Tech Pulse: December 23, 2025 - AI, Cybersecurity & Development News Roundup krlz krlz krlz Follow Dec 23 '25 Tech Pulse: December 23, 2025 - AI, Cybersecurity & Development News Roundup # news # security # ai # webdev Comments 1 comment 3 min read Documentation Sucks (I may have made it suck less) Luke Mueller Luke Mueller Luke Mueller Follow Dec 23 '25 Documentation Sucks (I may have made it suck less) # documentation # cli # opensource # ai Comments Add Comment 2 min read Day 29 of improving my Data Science skills Sylvester Promise Sylvester Promise Sylvester Promise Follow Dec 22 '25 Day 29 of improving my Data Science skills # ai # productivity # tutorial # opensource Comments Add Comment 1 min read When Your Users Are Bots, Not People GuardingPearSoftware GuardingPearSoftware GuardingPearSoftware Follow Dec 22 '25 When Your Users Are Bots, Not People # discuss # webdev # security # ai Comments Add Comment 3 min read Mobile Supply Chain Security: SBOM and Dependency Risk for App Teams M Sikandar M Sikandar M Sikandar Follow Dec 22 '25 Mobile Supply Chain Security: SBOM and Dependency Risk for App Teams # edtec # ai # learning # development Comments Add Comment 5 min read Why Voicebot Latency Is the Hardest Problem in Real-Time Voice AI Jack Morris Jack Morris Jack Morris Follow Dec 22 '25 Why Voicebot Latency Is the Hardest Problem in Real-Time Voice AI # ai # voicebot # webdev # devops Comments Add Comment 2 min read Ship Secure Code Faster: How Context-Driven Development and AI Agents Supercharge Your CI/CD Pipeline Barecheck Team Barecheck Team Barecheck Team Follow Dec 23 '25 Ship Secure Code Faster: How Context-Driven Development and AI Agents Supercharge Your CI/CD Pipeline # cicd # ai # devops # codequality Comments Add Comment 5 min read Interactive Visualization Using R: Origins, Applications, and Case Studies Perceptive Analytics Perceptive Analytics Perceptive Analytics Follow Dec 22 '25 Interactive Visualization Using R: Origins, Applications, and Case Studies # webdev # programming # ai # javascript 1 reaction Comments Add Comment 5 min read Algolia Search in Nuxt 3: Production-Ready Integration Guide Alex Kernel Alex Kernel Alex Kernel Follow Dec 22 '25 Algolia Search in Nuxt 3: Production-Ready Integration Guide # webdev # programming # javascript # ai Comments Add Comment 2 min read What Deep Learning Theory Teaches Us About AI Memory Gregory Dickson Gregory Dickson Gregory Dickson Follow Dec 26 '25 What Deep Learning Theory Teaches Us About AI Memory # ai # memory # agents Comments Add Comment 10 min read When AI-Generated Video Makes Sense in a Content Workflow Herman_Sun Herman_Sun Herman_Sun Follow Dec 23 '25 When AI-Generated Video Makes Sense in a Content Workflow # ai # contentworkflow # creatortools # videotechnology Comments Add Comment 2 min read AI Trading Daily Report: December 23, 2025 | $+161.84 Igor Ganapolsky Igor Ganapolsky Igor Ganapolsky Follow Dec 23 '25 AI Trading Daily Report: December 23, 2025 | $+161.84 # trading # ai # machinelearning # python Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/dalaez | Daniel - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Follow User actions Daniel Telecom Eng, MBA & Big Data in Defense & Security industry. Leading Planning and Processes with Data Models to optimize operations by bridging engineering, strategy, and AI. Location Spain Joined Joined on Dec 6, 2025 Personal website https://www.datalaria.com/ github website twitter website Education Telecom Engineer, Business Analytics and Data Master and MBA Work Technical Manager More info about @dalaez Organizations Datalaria Post 36 posts published Comment 0 comments written Tag 16 tags followed Weather Service Project (Part 2): Building the Interactive Frontend with GitHub Pages or Netlify and JavaScript Daniel Daniel Daniel Follow for Datalaria Jan 13 Weather Service Project (Part 2): Building the Interactive Frontend with GitHub Pages or Netlify and JavaScript # frontend # javascript # tutorial # webdev Comments Add Comment 6 min read Proyecto Weather Service (Parte 2): Construyendo el Frontend Interactivo con GitHub Pages o Netlify y JavaScript Daniel Daniel Daniel Follow for Datalaria Jan 13 Proyecto Weather Service (Parte 2): Construyendo el Frontend Interactivo con GitHub Pages o Netlify y JavaScript # frontend # javascript # spanish # tutorial Comments Add Comment 7 min read Weather Service Project (Part 1): Building the Data Collector with Python and GitHub Actions or Netlify Daniel Daniel Daniel Follow for Datalaria Jan 12 Weather Service Project (Part 1): Building the Data Collector with Python and GitHub Actions or Netlify # api # automation # python # tutorial 3 reactions Comments Add Comment 9 min read Proyecto Weather Service (Parte 1): Construyendo el Recolector de Datos con Python y GitHub Actions o Netlify Daniel Daniel Daniel Follow for Datalaria Jan 12 Proyecto Weather Service (Parte 1): Construyendo el Recolector de Datos con Python y GitHub Actions o Netlify # dataengineering # python # spanish # tutorial 1 reaction Comments Add Comment 10 min read Carto: De una Factura a la ONU a Conquistar la Nube Geoespacial Daniel Daniel Daniel Follow for Datalaria Jan 11 Carto: De una Factura a la ONU a Conquistar la Nube Geoespacial # startup # cloud # datascience # spanish Comments 1 comment 5 min read Carto: From a UN Invoice to Conquering the Geospatial Cloud Daniel Daniel Daniel Follow for Datalaria Jan 11 Carto: From a UN Invoice to Conquering the Geospatial Cloud # cloud # datascience # startup Comments Add Comment 4 min read AI-Powered Programming: Creating My Own Magical Flashcards Study App Daniel Daniel Daniel Follow for Datalaria Jan 10 AI-Powered Programming: Creating My Own Magical Flashcards Study App # showdev # ai # programming 5 reactions Comments 2 comments 5 min read Programando con IA: Creando mi Propia App mágica de Flashcards para Estudiar Daniel Daniel Daniel Follow for Datalaria Jan 10 Programando con IA: Creando mi Propia App mágica de Flashcards para Estudiar # showdev # ai # programming # spanish Comments Add Comment 5 min read Freepik: La Historia del Gigante Malagueño que Domó a la IA para Conquistar el Mundo Creativo Daniel Daniel Daniel Follow for Datalaria Jan 9 Freepik: La Historia del Gigante Malagueño que Domó a la IA para Conquistar el Mundo Creativo Comments Add Comment 6 min read Freepik: The Story of the Giant from Málaga that Tamed AI to Conquer the Creative World Daniel Daniel Daniel Follow for Datalaria Jan 9 Freepik: The Story of the Giant from Málaga that Tamed AI to Conquer the Creative World Comments Add Comment 5 min read Building My Digital 'Swiss Army Knife': A Custom Unit Converter with AI Daniel Daniel Daniel Follow for Datalaria Jan 8 Building My Digital 'Swiss Army Knife': A Custom Unit Converter with AI # showdev # ai # productivity # tooling 2 reactions Comments Add Comment 6 min read Creando mi 'Navaja Suiza' Digital: Un Conversor de Unidades a Medida con la IA Daniel Daniel Daniel Follow for Datalaria Jan 8 Creando mi 'Navaja Suiza' Digital: Un Conversor de Unidades a Medida con la IA # showdev # ai # spanish # tooling Comments Add Comment 7 min read Investigando con IA: Cómo Creé un Informe detallado sobre el impacto de la IA en la Educación con Deep Research de Gemini Daniel Daniel Daniel Follow for Datalaria Jan 7 Investigando con IA: Cómo Creé un Informe detallado sobre el impacto de la IA en la Educación con Deep Research de Gemini # gemini # ia # unesco # research 3 reactions Comments Add Comment 9 min read Researching with AI: How I Created a Detailed Report on the Global Impact of AI in Education with Gemini's Deep Research Daniel Daniel Daniel Follow for Datalaria Jan 7 Researching with AI: How I Created a Detailed Report on the Global Impact of AI in Education with Gemini's Deep Research # ai # gemini # deepresearch # unesco Comments Add Comment 7 min read From Systems Engineering to Formula 1: Using AI (Nanobana) to Illustrate a Complex Roadmap Daniel Daniel Daniel Follow for Datalaria Jan 6 From Systems Engineering to Formula 1: Using AI (Nanobana) to Illustrate a Complex Roadmap # ai # management # productivity # softwareengineering Comments Add Comment 6 min read De la Ingeniería de Sistemas a la Fórmula 1: La IA (Nanobana) para ilustrar un Roadmap Complejo Daniel Daniel Daniel Follow for Datalaria Jan 6 De la Ingeniería de Sistemas a la Fórmula 1: La IA (Nanobana) para ilustrar un Roadmap Complejo # ai # productivity # systemdesign Comments Add Comment 7 min read Netflix: Cómo los Datos Forjan un Imperio en Plena Guerra del Streaming Daniel Daniel Daniel Follow for Datalaria Jan 5 Netflix: Cómo los Datos Forjan un Imperio en Plena Guerra del Streaming # data # datascience # product Comments Add Comment 6 min read Netflix: How Data Forges an Empire in the Midst of the Streaming Wars Daniel Daniel Daniel Follow for Datalaria Jan 5 Netflix: How Data Forges an Empire in the Midst of the Streaming Wars Comments Add Comment 5 min read Copiloting with AI: Learning with Founderz and ChatGPT Daniel Daniel Daniel Follow for Datalaria Jan 4 Copiloting with AI: Learning with Founderz and ChatGPT # ai # chatgpt # learning # promptengineering Comments Add Comment 5 min read Copilotando con IA: Aprendiendo con Founderz y ChatGPT Daniel Daniel Daniel Follow for Datalaria Jan 4 Copilotando con IA: Aprendiendo con Founderz y ChatGPT Comments Add Comment 6 min read Florence Nightingale - The Mother of Nursing Daniel Daniel Daniel Follow for Datalaria Jan 3 Florence Nightingale - The Mother of Nursing # analytics # datascience # leadership Comments Add Comment 3 min read Florence Nightingale - La madre de la Enfermería Daniel Daniel Daniel Follow for Datalaria Jan 3 Florence Nightingale - La madre de la Enfermería # datascience # learning # science # spanish Comments Add Comment 3 min read Learning with AI - NotebookLM: From a Book to a Multimedia Learning Platform Daniel Daniel Daniel Follow for Datalaria Jan 2 Learning with AI - NotebookLM: From a Book to a Multimedia Learning Platform # productivity # tooling # ai # learning Comments Add Comment 5 min read Aprendiendo con IA - NotebookLM: De un libro a una plataforma de aprendizaje multimedia Daniel Daniel Daniel Follow for Datalaria Jan 2 Aprendiendo con IA - NotebookLM: De un libro a una plataforma de aprendizaje multimedia # productivity # ai # learning # spanish Comments Add Comment 6 min read The Thinking Game: How DeepMind Turned Video Games into History's Greatest Scientific Tool Daniel Daniel Daniel Follow for Datalaria Jan 1 The Thinking Game: How DeepMind Turned Video Games into History's Greatest Scientific Tool Comments Add Comment 6 min read The Thinking Game: De cómo DeepMind convirtió los videojuegos en la mayor herramienta científica de la historia Daniel Daniel Daniel Follow for Datalaria Jan 1 The Thinking Game: De cómo DeepMind convirtió los videojuegos en la mayor herramienta científica de la historia Comments Add Comment 7 min read The authentic John Snow, a precursor of Geolocation Daniel Daniel Daniel Follow for Datalaria Dec 31 '25 The authentic John Snow, a precursor of Geolocation # data # datascience # science Comments Add Comment 3 min read El auténtico John Snow, precursor de la Geolocalización Daniel Daniel Daniel Follow for Datalaria Dec 31 '25 El auténtico John Snow, precursor de la Geolocalización # learning # datascience # spanish # science Comments Add Comment 3 min read Building Datalaria: Technologies and Tools Daniel Daniel Daniel Follow for Datalaria Dec 30 '25 Building Datalaria: Technologies and Tools # showdev # github # tooling # webdev Comments Add Comment 5 min read Construyendo Datalaria: Tecnologías y herramientas Daniel Daniel Daniel Follow for Datalaria Dec 30 '25 Construyendo Datalaria: Tecnologías y herramientas # showdev # tooling # webdev # spanish Comments Add Comment 5 min read Data Visualization - Basics Daniel Daniel Daniel Follow for Datalaria Dec 30 '25 Data Visualization - Basics # beginners # datascience # tutorial Comments Add Comment 6 min read Visualizaciones básicas Daniel Daniel Daniel Follow for Datalaria Dec 30 '25 Visualizaciones básicas # tutorial # datascience # beginners # spanish Comments Add Comment 7 min read Descriptive Analysis Daniel Daniel Daniel Follow for Datalaria Dec 30 '25 Descriptive Analysis # analytics # beginners # datascience Comments Add Comment 9 min read Estadística Descriptiva Daniel Daniel Daniel Follow for Datalaria Dec 30 '25 Estadística Descriptiva # beginners # datascience # learning Comments Add Comment 11 min read Kilometer 0: Why Datalaria is Born Daniel Daniel Daniel Follow for Datalaria Dec 28 '25 Kilometer 0: Why Datalaria is Born Comments Add Comment 1 min read Kilómetro 0: Por qué nace Datalaria Daniel Daniel Daniel Follow for Datalaria Dec 28 '25 Kilómetro 0: Por qué nace Datalaria Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/srikarsunchu/i-got-tired-of-waiting-for-gradle-so-i-built-a-runtime-that-runs-kotlin-like-python-10nl#comment-33h9o | I got tired of waiting for Gradle, so I built a runtime that runs Kotlin like Python. - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Srikar Sunchu Posted on Jan 13 I got tired of waiting for Gradle, so I built a runtime that runs Kotlin like Python. # kotlin # performance # productivity # tooling I hit ./gradlew run and alt-tab to Discord. By the time I tab back, it's still resolving dependencies. This is a script. It's 40 lines. So I helped build something that doesn't make me wait. Elide . What is Elide? Elide is a runtime. Like Node. Like Python. You install it, you run code. curl -sSL elide.sh | bash Enter fullscreen mode Exit fullscreen mode But here's the thing: it doesn't just run one language. elide run app.kt # Kotlin, no Gradle elide run server.ts # TypeScript, no build step elide run script.py # Python, faster than CPython Enter fullscreen mode Exit fullscreen mode One binary. One toolchain. Multiple languages. Why this matters Most teams aren't single-language. You've got TypeScript on the frontend, Python for ML scripts, maybe Kotlin or Java somewhere in the backend. That's three runtimes, three package managers, three sets of problems. Elide is one runtime that speaks all of them. Install dependencies from npm and Maven in the same project. Run tests across languages with one command. No context switching. How it works Elide is built on GraalVM. The same compiler optimizes across languages-JavaScript, Python, Kotlin. No serialization when crossing language boundaries. All in one engine. What you can do today elide run — run code in any supported language elide test — run tests with built-in coverage elide install — fetch from npm or Maven elide serve — spin up a fast polyglot server Drop-in Gradle plugin for existing Java/Kotlin projects Try it Elide is in beta. curl -sSL elide.sh | bash Enter fullscreen mode Exit fullscreen mode We're on Discord if you want to talk, report bugs, or tell us what we're missing. Here's our Github - if you've read this far, leave us a star :) Top comments (1) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Baasil Ali Baasil Ali Baasil Ali Follow Joined Jan 13, 2026 • Jan 13 Dropdown menu Copy link Hide This is so sick! Like comment: Like comment: 2 likes Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Srikar Sunchu Follow Design engineer at Elide, where we're making Kotlin run like Python. I write about dev tools, terminal UIs, and why your build is too slow. Location San Francisco Work Design Engineer @ Elide Joined Jan 12, 2026 Trending on DEV Community Hot From CDN to Pixel: A React App's Journey # react # programming # webdev # performance What was your win this week??? # weeklyretro # discuss How to Crack Any Software Developer Interview in 2026 (Updated for AI & Modern Hiring) # softwareengineering # programming # career # interview 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://www.python.org/psf/fellows-roster | PSF Fellows Roster | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse PSF Fellows Roster Nominate a Fellow The criteria for PSF Fellows and how to nominate someone to be a Fellow can be found on our PSF Fellow main page. Fellows of the Python Software Foundation Fellows The year the fellow was elected is in parentheses. Aaron Yankey (2019) Abhijeet Mote (2025) Abigail Afi Gbadago (2025) Abigail Mesrenyame Dogbe (2019) Abhishek Mishra (2023) Adam Johnson (2024) Adrian Holovaty (2009) Aidis Stukas (2025) Aisha Bello (2017) Al Sweigart (2020) Alex Gaynor (2011) Alex Martelli (2002) Alex Willmer (2010) Alexander Hendorf (2018) Alexandre Savio (2020) Allison Randal (2010) Alyssa Coghlan (2007) Amaury Forgeot d'Arc (2008) Amber Brown (2018) Ana Dulce Padovan (2021) Anand Chitipothu (2012) Anand Pillai (2010) Andrew Godwin (2018) Andrew Kuchling (2003) Anna Martelli Ravenscroft (2006) Anne Gentle (2012) Anthony Baxter (2002) Anthony Scopatz (2013) Anthony Shaw (2018) Anthony Sottile (2021) Antoine Pitrou (2010) Anton Caceres (2019) Antonio Cuni (2012) Anwesha Das (2022) Arc Riley (2010) Archana Vaidheeswaran (2022) Armin Ronacher (2012) Armin Stroß-Radschinski (2012) Artur Czepiel (2024) Asheesh Laroia (2011) Audrey Roy (2011) Bae KwonHan (2022) Baptiste Mispelon (2025) Batuhan Taskaya (2021) Barbara Shaurette (2013) Barney Gale (2023) Barry Warsaw (2001) Becky Smith (2025) Belinda Weaver (2017) Ben Bangert (2009) Benjamin Peterson (2009) Benoit Chesneau (2012) Berker Peksag (2020) Bernát Gábor (2021) Brandon Rhodes (2010) Brett Cannon (2003) Brian Costlow (2017) Brian Curtin (2011) Brian K. Jones (2011) Brian Zimmer (2005) Briana Augenreich (2021) Bruno Oliveira ( 2019) Bruno Rocha (2012) Titus Brown (2008) Cameron Laird (2002) Carl F. Karsten (2010) Carl Friedrich Bolz (2010) Carl Meyer (2012) Carol Willing (2017) Carlton Gibson (2022) Carrie Anne Philbin (2017) Catherine Devlin (2007) Chandan Kumar (2022) Charlie Marsh (2025) Cheuk Ting Ho (2021) Chris Jerdonek (2019) Chris Neugebauer (2013) Chris Withers (2012) Christian Barra (2018) Christian Heimes (2008) Christian Scholz (2010) Christian Theune (2012) Christian Tismer (2001) Christoph Gohlke (2019) Christopher Armstrong (2009) Christopher Bailey (2025) Christopher MacGowan (2012) Chukwudi Nwachukwu (2017) Claudiu Popa (2018) Cory Benfield (2017) Cristián Danilo Maureira-Fredes (2021) Damien George (2017) Dana Bauer (2012) Daniel Greenfeld (2011) Daniel Pope (2017) Daniele Procida (2017) Danny Adair (2022) Darya Chyzhyk (2020) Dave Malcolm (2012) David Goodger (2003) David Lord (2020) David Markey (2018) Dawn Wages (2025) Dean Troyer (2012) Débora Azevedo (2020) Denny Perez (2022) Diana Clarke (2013) Dino Viehland (2009) Don Sheu (2017) Donald Beaudry (2002) Donald Stufft (2017) Doug Hellmann (2009) Doug Napoleone (2007) Duncan McGreggor (2009) Dustin Ingram (2023) Dusty Phillips (2017) Eduardo Mendes (2018) Elaine Wong (2021) Elana Hashman (2018) Emily Morehouse-Valcarcel (2021) Emmanuelle Gouillart (2013) Eric Holscher (2013) Eric Jones (2002) Eric S. Raymond (2001) Eric Traut (2023) Eric V. Smith (2010) Érico Andrei (2013) Esteban Maya Cadavid (2023) Ee Durbin (2018) Ewa Jodlowska (2012) Eyitemi Egbejule (2018) Fabio Pliger (2011) Facundo Batista (2005) Felipe de Morais (2025) Fernando Masanori Ashikaga (2017) Fernando Perez (2010) Filip Kłębczyk (2017) Finn Bock (2001) Fiorella De Luca (2021) Florian Bruhin (2019) Francisco Palm (2021) Frank Wierzbicki (2009) Frank Wiles (2025) Fred L. Drake, Jr. (2001) Gael Varoquaux (2013) Gautier Hayoun (2019) Gavin M. Roy (2011) Georg Brandl (2006) George Paci (2006) Georgi Ker (2021) Giles Thomas (2012) Gina Häußge (2023) Giovanni Bajo (2011) Glyph Lefkowitz (2009) Graham Dumpleton (2009) Greg Ewing (2002) Greg Stein (2001) Greg Ward (2001 - converted to emeritus in 2008, re-activated in 2013) Greg Wilson (2010) Gregory Smith (2011) Grishma Jena (2023) Guido van Rossum (2001) Gustavo Niemeyer (2004) Hamdalah Adetunji (2025) Hanno Schlichting (2012) Harald Armin Massa (2010) Henrique Bastos (2012) Hugo van Kemenade (2022) Humphrey Butau (2019) Hye-Shik Chang (2004) Hynek Schlawack (2013) Ian Bicking (2010) Ines Montani (2020) Iqbal Abdullah (2022) Ivan Levkivskyi (2021) Ivaylo Bachvarov (2017) Ivy Fung Oi Wei (2025) Jack Jansen (2001) Jackie Kazil (2017) Jacob Hallén (2010) Jacob Kaplan-Moss (2009) Jakub Baláš (2021) James Bennett (2009) James Blair (2012) James Tauber (2008) Jan Ulrich Hasecke (2012) Jannis Leidel (2012) Jason Pellerin (2013) Jason Tishler (2003) Jay Miller (2024) Jean-Paul Calderone (2009) Jeff Elkner (2004) Jeff Reback (2018) Jeff Rush (2007) Jeff Triplett (2018) Jelle Zijlstra (2023) Jeremy Dunck (2013) Jeremy Hylton (2001) Jesse Noller (2009) Jessica McKellar (2011) Jim Baker (2009) Jimena Escobar Bermúdez (2024) Jim Fulton (2001) Jim Hugunin (2006) João Sebastião de Oliveira Bueno (2021) Joe Banks (2021) John Roa (2020) John Hawley (2022) Jonathan Hartley (2011) Jonathan LaCour (2011) Jon Banafato (2025) Joris Van den Bossche (2018) Josef Heinen (2022) Joshua McKenty (2012) Juan Luis Cano (2017) Jukka Lehtosalo (2021) Julia Duimovich (2025) Julien Palard (2020) Jürgen Gmach (2022) Just van Rossum (2002) Ka-Ping Yee (2001) Kamon Ayeva (2013) Karolina Ladino (2020) Katia Lira (2020) Katie Cunningham (2013) Katie McLaughlin (2018) Ken Manheimer (2001) Kenneth Love (2020) Kenneth Reitz (2012) Kevin Altis (2003) Kevin O'Brien (2020) Kirby Urner (2009) Kristian Glass (2020) Kojo Idrissa (2024) Kurt B. Kaiser (2004) Kushal Das (2013) Laís Carvalho (2025) Lance Ellinghaus (2010) Larry Hastings (2012) Laura Cassell (2017) Laurens Van Houtven (2010) Leah Silen (2021) Leah Wasser (2025) Leandro Enrique Colombo Viña (2025) Lennart Regebro (2011) Leon Sandøy (2021) Leonard Richardson (2024) Lorena Mesa (2017) Luciano Ramalho (2012) Łukasz Langa (2017) Lynn Root (2013) Maaya Ishida (2025) Mabel Delgado (2017) Mahmoud Hashemi (2019) Mai Giménez (2017) Manabu Terada (2019) Mannie Young (2019) Manuel Kaufmann (2017) Marc-André Lemburg (2001) Marcelo Elizeche Landó (2021) Marco Rougeth (2020) Mark Smith (2025) Mariano Reingart (2012) Mariatta Wijaya (2020) Mario Corchero (2017) Mário Sérgio Oliveira de Queiroz (2017) Mark Dickinson (2008) Mark Hammond (2001) Mark Lutz (2002) Mark McLoughlin (2012) Mark Ramm (2009) Marlene Mhangami (2023) Martijn Faassen (2009) Martijn Pieters (2023) Martin Aspeli (2012) Martin von Löwis (2001) Mason Egger (2025) Massimo DiPierro (2011) Mathieu Leduc-Hamel (2013) Matt Lebrun (2019) Matteo Benci (2022) Matthew Dixon Cowles (2003) Matthew Lagoe (2022) Matthias Klose (2009) Melissa Weber Mendonça (2020) Micaela Reyes (2019) Michael Bayer (2010) Michael Hudson (2002) Michael Iyanda (2021) Michael Kennedy (2018) Michael Sparks (2010) Michael J. Sullivan (2021) Michael Young (2019) Michelle Rowley (2012) Mike Driscoll (2011) Mike Fletcher (2009) Mike McLay (2002) Mike Müller (2010) Mike Olson (2002) Mike Orr (2011) Mike Pirnat (2025) Miguel Grinberg (2025) Miroslav Šedivý (2021) Monty Taylor (2012) Moshe Zadka (2001) Naomi Ceder (2011) Nathaniel Smith (2018) Neal Norwitz (2002) Ned Batchelder (2011) Ned Deily (2013) Neil Schemenauer (2001) Ng Swee Meng (2020) Ngazetungue Muheue (2019) Nick Barcet (2012) Nicolas Chauvat (2010) Nicolás Demarchi (2021) Nicolas Laurance (2022) Nicole Harris (2021) Nikita Sobolev (2023) Nilo Ney Coutinho Menezes (2020) Noah Alorwu (2019) Noah Kantrowitz (2012) Noufal Ibrahim (2012) Ola Sendecka (2017) Ola Sitarska (2017) Olivier Grisel (2013) Osvaldo Santana (2013) Pablo Galindo Salgado (2019) Pablo Rivera (2021) Park Hyun-woo (2020) Patrick Arminio (2019) Paul Everitt (2006) Paul Kehrer (2019) Paul McGuire (2022) Paul McMillan (2012) Paolo Melchiorre (2024) Paulo Nuin (2011) Peter Inglesby (2017) Peter Kropf (2012) Peter Schneider-Kamp (2001) Peter Wang (2022) Philip James (2021) Philip Jenvey (2011) Philip Jones (2023) Prabhu Ramachandran (2010) Pradyun Gedam (2019) Quentin Wright (2010) David Murray (2010) Ralph Green (2010) Ram Rachum (2020) Rami Chowdhury (2019) Raquel Dou (2023) Reimar Bauer (2013) Reshama Shaikh (2022) Richard Jones (2003) Richard Kellner (2017) Richard Taylor (2011) Rick Copeland (2011) Rizky Ariestiyansyah (2018) Robert Collins (2013) Robert Kern (2010) Robin Dunn (2002) Ronald Oussoren (2011) Roy Hyunjin Han (2020) Ruben Orduz (2017) Russell Keith-Magee (2017) Sage Sharp (2025) Sammy Fung (2022) Samuel Colvin (2023) Samuele Pedroni (2001) Saptak Sengupta (2023) Sarah Kaiser (2021) Sean Reifschneider (2007) Sebastiaan Zeeff (2021) Sebastian Vetter (2020) Selena Deckelman (2017) Serhiy Storchaka (2020) Seth Michael Larson (2022) Simon Cross (2013) Simon Willison (2009) Sjoerd Mullender (2001) Soon Seng Goh (2023) Soong Chee Gi (2022) Stefan Behnel (2018) Stefan van der Walt (2013) Stephan Deibel (2003) Stephane Wirtel (2013) Stephen Hawkes (2012) Stephen Thorne (2010) Steven d’Aprano (2010) Tania Allard (2019) Ted Pollari (2009) Tereza Iofciu (2025) Terri Oda (2013) Terry Peppers (2010) Terry Reedy (2010) Tetsuya Morimoto (2011) Thea Flowers (2020) Thierry Carrez (2012) Thomas A Caswell (2022) Thomas Waldmann (2009) Thomas Wouters (2001) Tim Ansell (2012) Tim Couper (2010) Tim Golden (2010) Tim Peters (2001) Tom Augspurger (2018) Tom Christie (2020) Tom Viner (2019) Travis Oliphant (2006) Trent Mick (2001) Tres Seaver (2012) Trevor Toenjes (2004) Trey Hunner (2024) Uche Ogbuji (2002) Valentin Dombrovsky (2019) Van Lindberg (2008) Vasudev Ram (2010) Velda Kiara (2025) Vicky Twomey-Lee (2012) Victor Stinner (2010) Vinay Sajip (2003) Vish Ishaya (2012) Walter Dörwald (2003) Wes McKinney (2018) Wesley Chun (2010) Wilfredo Sanchez Vega (2012) Will McGugan (2025) William Vincent (2025) Winnie Ke (2024) Yamila Moreno (2017) Yannick Gingras (2011) Yifei Wang (2023) Younggun Kim (2020) Yung-Yu Chen (2022) Yury Selivanov (2018) Zac Hatfield-Dodds (2021) Zachary Ware (2018) Zeth Green (2010) Emeritus Fellows These are our emeritus members (year of election / year of emeritus conversion) : David Abrahams (2002/2008) Paul Boddie (2010/2015) Paul F. Dubois (2002/2008) Paul Dubois was an original contributor to Numerical Python, and its coordinator for five years. Paul also hosted the Fourth International Python Conference in 1996. Lars Marius Garshol (2001/2005) Charles G. Waldman (2001/2005) Skip Montanaro (2001/2008) Sam Rushing (2002/2008) Danny Yoo (2004/2008) Thomas Heller (2001/2009) Neil Hodgson (2002/2009) Armin Rigo (2004/2010) David Ascher (2001/2011) Steven Bethard (2007/2011) Maciej Fijalkowski (2011/2012) Paul Prescod (2001/2013) André Roberge (2010/2013) Tarek Ziadé (2010/2013) Gloria W. Jacobs (2010/2013) Holger Krekel (2010/2018) Nicholas H. Tollervey (2012/2019) Steve Holden (2003/2020) David M. Beazley (2002/2020) Raymond Hettinger (2003/2020) Jack Diederich (2010/2020) Laura Creighton (2007/2021) David Mertz (2008/2024) Chris McDonough (2010/2024) Marc Garcia (2018/2024) Andrew Dalke (2004/2025) Deceased Fellows, In Memoriam The year the fellow was elected is in parentheses. Aahz (2002, emeritus since 2013) Fredrik Lundh (2001) James Lopeman (2022) John Pinner (member from 2008-2015) Malcolm Tredinnick (2009) Michael Foord (2009) The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fibn_abubakre%2Fappend-vs-appendchild-a4m&title=append%20VS%20appendChild&summary=This%20is%20the%20first%20post%20in%20the%20this%20vs%20that%20series.%20A%20series%20aimed%20at%20comparing%20two%20often%20confusing%20te...&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:06 |
https://dev.to/t/cloudflare | Cloudflare - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close # cloudflare Follow Hide Create Post Older #cloudflare posts 1 2 3 4 5 6 7 8 9 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu The Future of Cloudflare Workers AI and Vectorize for RAG applications: A Comprehensive Guide Karol Karol Karol Follow Jan 9 The Future of Cloudflare Workers AI and Vectorize for RAG applications: A Comprehensive Guide # ai # cloudflare # automation Comments Add Comment 3 min read Protecting Your Website with Cloudflare: Security, Performance, and Reliability [Part 1] Bemals Dvanitha Bemals Dvanitha Bemals Dvanitha Follow Jan 9 Protecting Your Website with Cloudflare: Security, Performance, and Reliability [Part 1] # devops # security # cloudflare # webdev Comments Add Comment 5 min read Zero Egress Costs: How I Built P2P File Sharing with Cloudflare kiyo-e kiyo-e kiyo-e Follow Jan 9 Zero Egress Costs: How I Built P2P File Sharing with Cloudflare # webrtc # cloudflare # hono # typescript Comments Add Comment 4 min read Test z emoji i URL Karol Karol Karol Follow Jan 7 Test z emoji i URL # ai # cloudflare # automation Comments Add Comment 3 min read Test z emoji i URL Karol Karol Karol Follow Jan 7 Test z emoji i URL # ai # cloudflare # automation Comments Add Comment 3 min read Quick Zen install + profile switcher enable (Linux/macOS) Karol Karol Karol Follow Jan 7 Quick Zen install + profile switcher enable (Linux/macOS) # ai # cloudflare # automation Comments Add Comment 3 min read Quick Zen install + profile switcher enable (Linux/macOS) Karol Karol Karol Follow Jan 7 Quick Zen install + profile switcher enable (Linux/macOS) # ai # cloudflare # automation Comments Add Comment 3 min read How to Deploy a SvelteKit App to Cloudflare Containers qaynam qaynam qaynam Follow Jan 4 How to Deploy a SvelteKit App to Cloudflare Containers # sveltekit # cloudflare # cloudflarecontainers # docker 1 reaction Comments Add Comment 7 min read Test z emoji i URL Karol Karol Karol Follow Jan 7 Test z emoji i URL # ai # cloudflare # automation Comments Add Comment 3 min read Why Autonomous AI Agents are the Future of DevOps in 2026 Karol Karol Karol Follow Jan 7 Why Autonomous AI Agents are the Future of DevOps in 2026 # ai # cloudflare # automation Comments Add Comment 3 min read Why Pollinations AI Crushes DALL-E as the Ultimate Free Alternative Karol Karol Karol Follow Jan 7 Why Pollinations AI Crushes DALL-E as the Ultimate Free Alternative # ai # cloudflare # automation Comments Add Comment 3 min read **Optymalizacja zasięgów na Twitterze: Automatyczne formatowanie pod 280 znaków z Pythonem i API v2** Karol Karol Karol Follow Jan 7 **Optymalizacja zasięgów na Twitterze: Automatyczne formatowanie pod 280 znaków z Pythonem i API v2** # ai # cloudflare # automation Comments Add Comment 3 min read Building RAG on the Edge: Cloudflare Workers, Vectorize, and FAISS — What Actually Works Karol Karol Karol Follow Jan 7 Building RAG on the Edge: Cloudflare Workers, Vectorize, and FAISS — What Actually Works # ai # cloudflare # automation Comments Add Comment 4 min read Ditch Cloudflare's $5k/Mo Bills: Self-Host Workers at 1/100th Cost in 2 Hours 🚀 Aparna Pradhan Aparna Pradhan Aparna Pradhan Follow Jan 5 Ditch Cloudflare's $5k/Mo Bills: Self-Host Workers at 1/100th Cost in 2 Hours 🚀 # cloudflare # openworker # hetzner # selfhost Comments Add Comment 3 min read Caching API Responses at the Edge with Cloudflare Cache Rules Anand Rathnas Anand Rathnas Anand Rathnas Follow Jan 5 Caching API Responses at the Edge with Cloudflare Cache Rules # cloudflare # performance # caching # api Comments Add Comment 3 min read How to Use Cloudflare Firewall Rules to Secure Your Website Meghna Meghwani Meghna Meghwani Meghna Meghwani Follow for ServerAvatar Jan 1 How to Use Cloudflare Firewall Rules to Secure Your Website # cloudflare # websecurity # cybersecurity # devops Comments Add Comment 4 min read Cloudflare + MongoDB: How to fix 'Error: Dynamic require of "punycode/" is not supported' Alex Bevilacqua Alex Bevilacqua Alex Bevilacqua Follow Dec 31 '25 Cloudflare + MongoDB: How to fix 'Error: Dynamic require of "punycode/" is not supported' # mongodb # cloudflare # webdev # javascript Comments Add Comment 4 min read Optimized Image Hosting: Why I Integrated Cloudflare R2 with my AWS Backend Yasith wijesuriya Yasith wijesuriya Yasith wijesuriya Follow Dec 28 '25 Optimized Image Hosting: Why I Integrated Cloudflare R2 with my AWS Backend # aws # cloudflare # serverless # architecture Comments Add Comment 2 min read Building Cryptographically Enforced Time-Locked Vaults on Cloudflare's Edge Teycir Ben Soltane Teycir Ben Soltane Teycir Ben Soltane Follow Dec 27 '25 Building Cryptographically Enforced Time-Locked Vaults on Cloudflare's Edge # cryptography # nextjs # cloudflare # opensource Comments Add Comment 7 min read I saw 'Just Use Tailwind' trending, so I made one for Cloudflare My Name is Tito My Name is Tito My Name is Tito Follow Dec 28 '25 I saw 'Just Use Tailwind' trending, so I made one for Cloudflare # showdev # cloudflare # watercooler # webdev Comments Add Comment 1 min read Solving the "410 Gone" & Cloudflare Loop Issue on Shared Hosting (Case Study) Jamal Pinang Jamal Pinang Jamal Pinang Follow Dec 25 '25 Solving the "410 Gone" & Cloudflare Loop Issue on Shared Hosting (Case Study) # webdev # php # cloudflare # devops Comments Add Comment 2 min read Building a Simple MCP Server That Just Returns the Current Time kiyo-e kiyo-e kiyo-e Follow Dec 19 '25 Building a Simple MCP Server That Just Returns the Current Time # mcp # cloudflare # chatgpt # claude 1 reaction Comments Add Comment 3 min read Wrangler “write EOF” on Windows: The Actual Fix mrtoxas mrtoxas mrtoxas Follow Dec 17 '25 Wrangler “write EOF” on Windows: The Actual Fix # cloudflare # wrangler # windows # eof Comments Add Comment 2 min read # From Monolith to the Edge: Migrating Tenders SA's Blog to Cloudflare Workers mobius-crypt mobius-crypt mobius-crypt Follow Dec 16 '25 # From Monolith to the Edge: Migrating Tenders SA's Blog to Cloudflare Workers # cloudflare # seo # blog # tenders 1 reaction Comments Add Comment 3 min read Why We Migrated from Next.js to Vite and Hono jj811208 jj811208 jj811208 Follow Dec 31 '25 Why We Migrated from Next.js to Vite and Hono # webdev # nextjs # javascript # cloudflare 2 reactions Comments 1 comment 8 min read loading... trending guides/resources 20% of internet down: Why X, ChatGPT, and Cloudflare were Down Cloudflare Went Down - Here's What Really Happened Today Why Edge Computing Forced Me to Write Better Code (And Why That's the Future) When the Internet Held Its Breath: The Day Cloudflare Took Down 20% of the Web I Built a Production RAG System for $5/month (Most Alternatives Cost $100-200+) Architecting "Agentic" systems at the edge: an analysis of the Cloudflare platform Exposing Home Container with Traefik and Cloudflare Tunnel Building an Automated Bilingual Blog System with Obsidian: Going Global in Two Languages Automate Your Astro Blog with GitHub Actions I Almost Used LangGraph for Social Media Automation (Here's Why I Built an MCP Server Instead) Using OG Image Outside of Node Why We Migrated from Next.js to Vite and Hono I Built an AI Chatbot Wrong (And What I Learned About Cloudflare's AI Search) Cloud Outages: The Unpopular Truth No One Wants to Hear Hosting a Minecraft Server on Cloudflare Containers # From Monolith to the Edge: Migrating Tenders SA's Blog to Cloudflare Workers How to Deploy a SvelteKit App to Cloudflare Containers Cloudflare Custom Domain Email Tutorial: 3 Steps to Build a Professional Brand Email (with DNS Se... How to Ingest 1 Billion Events Per Day Without Kafka: A Serverless Masterclass Beyond the Context Window: Building a Stateful 'Memory' MCP Server on Cloudflare Workers 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Ftatyanabayramova%2Faccessibility-testing-on-windows-on-mac-48e4&title=Accessibility%20Testing%20on%20Windows%20on%20Mac&summary=Today%27s%20note%20is%20about%20something%20that%20I%2C%20as%20a%20new%20Mac%20user%2C%20had%20to%20deal%20with%20while%20setting%20up%20my%20work...&source=DEV%20Community | LinkedIn Login, Sign in | LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional)) | 2026-01-13T08:49:06 |
https://docs.python.org/3/tutorial/controlflow.html#break-and-continue-statements | 4. More Control Flow Tools — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | Theme Auto Light Dark | 4. More Control Flow Tools ¶ As well as the while statement just introduced, Python uses a few more that we will encounter in this chapter. 4.1. if Statements ¶ Perhaps the most well-known statement type is the if statement. For example: >>> x = int ( input ( "Please enter an integer: " )) Please enter an integer: 42 >>> if x < 0 : ... x = 0 ... print ( 'Negative changed to zero' ) ... elif x == 0 : ... print ( 'Zero' ) ... elif x == 1 : ... print ( 'Single' ) ... else : ... print ( 'More' ) ... More There can be zero or more elif parts, and the else part is optional. The keyword ‘ elif ’ is short for ‘else if’, and is useful to avoid excessive indentation. An if … elif … elif … sequence is a substitute for the switch or case statements found in other languages. If you’re comparing the same value to several constants, or checking for specific types or attributes, you may also find the match statement useful. For more details see match Statements . 4.2. for Statements ¶ The for statement in Python differs a bit from what you may be used to in C or Pascal. Rather than always iterating over an arithmetic progression of numbers (like in Pascal), or giving the user the ability to define both the iteration step and halting condition (as C), Python’s for statement iterates over the items of any sequence (a list or a string), in the order that they appear in the sequence. For example (no pun intended): >>> # Measure some strings: >>> words = [ 'cat' , 'window' , 'defenestrate' ] >>> for w in words : ... print ( w , len ( w )) ... cat 3 window 6 defenestrate 12 Code that modifies a collection while iterating over that same collection can be tricky to get right. Instead, it is usually more straight-forward to loop over a copy of the collection or to create a new collection: # Create a sample collection users = { 'Hans' : 'active' , 'Éléonore' : 'inactive' , '景太郎' : 'active' } # Strategy: Iterate over a copy for user , status in users . copy () . items (): if status == 'inactive' : del users [ user ] # Strategy: Create a new collection active_users = {} for user , status in users . items (): if status == 'active' : active_users [ user ] = status 4.3. The range() Function ¶ If you do need to iterate over a sequence of numbers, the built-in function range() comes in handy. It generates arithmetic progressions: >>> for i in range ( 5 ): ... print ( i ) ... 0 1 2 3 4 The given end point is never part of the generated sequence; range(10) generates 10 values, the legal indices for items of a sequence of length 10. It is possible to let the range start at another number, or to specify a different increment (even negative; sometimes this is called the ‘step’): >>> list ( range ( 5 , 10 )) [5, 6, 7, 8, 9] >>> list ( range ( 0 , 10 , 3 )) [0, 3, 6, 9] >>> list ( range ( - 10 , - 100 , - 30 )) [-10, -40, -70] To iterate over the indices of a sequence, you can combine range() and len() as follows: >>> a = [ 'Mary' , 'had' , 'a' , 'little' , 'lamb' ] >>> for i in range ( len ( a )): ... print ( i , a [ i ]) ... 0 Mary 1 had 2 a 3 little 4 lamb In most such cases, however, it is convenient to use the enumerate() function, see Looping Techniques . A strange thing happens if you just print a range: >>> range ( 10 ) range(0, 10) In many ways the object returned by range() behaves as if it is a list, but in fact it isn’t. It is an object which returns the successive items of the desired sequence when you iterate over it, but it doesn’t really make the list, thus saving space. We say such an object is iterable , that is, suitable as a target for functions and constructs that expect something from which they can obtain successive items until the supply is exhausted. We have seen that the for statement is such a construct, while an example of a function that takes an iterable is sum() : >>> sum ( range ( 4 )) # 0 + 1 + 2 + 3 6 Later we will see more functions that return iterables and take iterables as arguments. In chapter Data Structures , we will discuss in more detail about list() . 4.4. break and continue Statements ¶ The break statement breaks out of the innermost enclosing for or while loop: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( f " { n } equals { x } * { n // x } " ) ... break ... 4 equals 2 * 2 6 equals 2 * 3 8 equals 2 * 4 9 equals 3 * 3 The continue statement continues with the next iteration of the loop: >>> for num in range ( 2 , 10 ): ... if num % 2 == 0 : ... print ( f "Found an even number { num } " ) ... continue ... print ( f "Found an odd number { num } " ) ... Found an even number 2 Found an odd number 3 Found an even number 4 Found an odd number 5 Found an even number 6 Found an odd number 7 Found an even number 8 Found an odd number 9 4.5. else Clauses on Loops ¶ In a for or while loop the break statement may be paired with an else clause. If the loop finishes without executing the break , the else clause executes. In a for loop, the else clause is executed after the loop finishes its final iteration, that is, if no break occurred. In a while loop, it’s executed after the loop’s condition becomes false. In either kind of loop, the else clause is not executed if the loop was terminated by a break . Of course, other ways of ending the loop early, such as a return or a raised exception, will also skip execution of the else clause. This is exemplified in the following for loop, which searches for prime numbers: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( n , 'equals' , x , '*' , n // x ) ... break ... else : ... # loop fell through without finding a factor ... print ( n , 'is a prime number' ) ... 2 is a prime number 3 is a prime number 4 equals 2 * 2 5 is a prime number 6 equals 2 * 3 7 is a prime number 8 equals 2 * 4 9 equals 3 * 3 (Yes, this is the correct code. Look closely: the else clause belongs to the for loop, not the if statement.) One way to think of the else clause is to imagine it paired with the if inside the loop. As the loop executes, it will run a sequence like if/if/if/else. The if is inside the loop, encountered a number of times. If the condition is ever true, a break will happen. If the condition is never true, the else clause outside the loop will execute. When used with a loop, the else clause has more in common with the else clause of a try statement than it does with that of if statements: a try statement’s else clause runs when no exception occurs, and a loop’s else clause runs when no break occurs. For more on the try statement and exceptions, see Handling Exceptions . 4.6. pass Statements ¶ The pass statement does nothing. It can be used when a statement is required syntactically but the program requires no action. For example: >>> while True : ... pass # Busy-wait for keyboard interrupt (Ctrl+C) ... This is commonly used for creating minimal classes: >>> class MyEmptyClass : ... pass ... Another place pass can be used is as a place-holder for a function or conditional body when you are working on new code, allowing you to keep thinking at a more abstract level. The pass is silently ignored: >>> def initlog ( * args ): ... pass # Remember to implement this! ... For this last case, many people use the ellipsis literal ... instead of pass . This use has no special meaning to Python, and is not part of the language definition (you could use any constant expression here), but ... is used conventionally as a placeholder body as well. See The Ellipsis Object . 4.7. match Statements ¶ A match statement takes an expression and compares its value to successive patterns given as one or more case blocks. This is superficially similar to a switch statement in C, Java or JavaScript (and many other languages), but it’s more similar to pattern matching in languages like Rust or Haskell. Only the first pattern that matches gets executed and it can also extract components (sequence elements or object attributes) from the value into variables. If no case matches, none of the branches is executed. The simplest form compares a subject value against one or more literals: def http_error ( status ): match status : case 400 : return "Bad request" case 404 : return "Not found" case 418 : return "I'm a teapot" case _ : return "Something's wrong with the internet" Note the last block: the “variable name” _ acts as a wildcard and never fails to match. You can combine several literals in a single pattern using | (“or”): case 401 | 403 | 404 : return "Not allowed" Patterns can look like unpacking assignments, and can be used to bind variables: # point is an (x, y) tuple match point : case ( 0 , 0 ): print ( "Origin" ) case ( 0 , y ): print ( f "Y= { y } " ) case ( x , 0 ): print ( f "X= { x } " ) case ( x , y ): print ( f "X= { x } , Y= { y } " ) case _ : raise ValueError ( "Not a point" ) Study that one carefully! The first pattern has two literals, and can be thought of as an extension of the literal pattern shown above. But the next two patterns combine a literal and a variable, and the variable binds a value from the subject ( point ). The fourth pattern captures two values, which makes it conceptually similar to the unpacking assignment (x, y) = point . If you are using classes to structure your data you can use the class name followed by an argument list resembling a constructor, but with the ability to capture attributes into variables: class Point : def __init__ ( self , x , y ): self . x = x self . y = y def where_is ( point ): match point : case Point ( x = 0 , y = 0 ): print ( "Origin" ) case Point ( x = 0 , y = y ): print ( f "Y= { y } " ) case Point ( x = x , y = 0 ): print ( f "X= { x } " ) case Point (): print ( "Somewhere else" ) case _ : print ( "Not a point" ) You can use positional parameters with some builtin classes that provide an ordering for their attributes (e.g. dataclasses). You can also define a specific position for attributes in patterns by setting the __match_args__ special attribute in your classes. If it’s set to (“x”, “y”), the following patterns are all equivalent (and all bind the y attribute to the var variable): Point ( 1 , var ) Point ( 1 , y = var ) Point ( x = 1 , y = var ) Point ( y = var , x = 1 ) A recommended way to read patterns is to look at them as an extended form of what you would put on the left of an assignment, to understand which variables would be set to what. Only the standalone names (like var above) are assigned to by a match statement. Dotted names (like foo.bar ), attribute names (the x= and y= above) or class names (recognized by the “(…)” next to them like Point above) are never assigned to. Patterns can be arbitrarily nested. For example, if we have a short list of Points, with __match_args__ added, we could match it like this: class Point : __match_args__ = ( 'x' , 'y' ) def __init__ ( self , x , y ): self . x = x self . y = y match points : case []: print ( "No points" ) case [ Point ( 0 , 0 )]: print ( "The origin" ) case [ Point ( x , y )]: print ( f "Single point { x } , { y } " ) case [ Point ( 0 , y1 ), Point ( 0 , y2 )]: print ( f "Two on the Y axis at { y1 } , { y2 } " ) case _ : print ( "Something else" ) We can add an if clause to a pattern, known as a “guard”. If the guard is false, match goes on to try the next case block. Note that value capture happens before the guard is evaluated: match point : case Point ( x , y ) if x == y : print ( f "Y=X at { x } " ) case Point ( x , y ): print ( f "Not on the diagonal" ) Several other key features of this statement: Like unpacking assignments, tuple and list patterns have exactly the same meaning and actually match arbitrary sequences. An important exception is that they don’t match iterators or strings. Sequence patterns support extended unpacking: [x, y, *rest] and (x, y, *rest) work similar to unpacking assignments. The name after * may also be _ , so (x, y, *_) matches a sequence of at least two items without binding the remaining items. Mapping patterns: {"bandwidth": b, "latency": l} captures the "bandwidth" and "latency" values from a dictionary. Unlike sequence patterns, extra keys are ignored. An unpacking like **rest is also supported. (But **_ would be redundant, so it is not allowed.) Subpatterns may be captured using the as keyword: case ( Point ( x1 , y1 ), Point ( x2 , y2 ) as p2 ): ... will capture the second element of the input as p2 (as long as the input is a sequence of two points) Most literals are compared by equality, however the singletons True , False and None are compared by identity. Patterns may use named constants. These must be dotted names to prevent them from being interpreted as capture variable: from enum import Enum class Color ( Enum ): RED = 'red' GREEN = 'green' BLUE = 'blue' color = Color ( input ( "Enter your choice of 'red', 'blue' or 'green': " )) match color : case Color . RED : print ( "I see red!" ) case Color . GREEN : print ( "Grass is green" ) case Color . BLUE : print ( "I'm feeling the blues :(" ) For a more detailed explanation and additional examples, you can look into PEP 636 which is written in a tutorial format. 4.8. Defining Functions ¶ We can create a function that writes the Fibonacci series to an arbitrary boundary: >>> def fib ( n ): # write Fibonacci series less than n ... """Print a Fibonacci series less than n.""" ... a , b = 0 , 1 ... while a < n : ... print ( a , end = ' ' ) ... a , b = b , a + b ... print () ... >>> # Now call the function we just defined: >>> fib ( 2000 ) 0 1 1 2 3 5 8 13 21 34 55 89 144 233 377 610 987 1597 The keyword def introduces a function definition . It must be followed by the function name and the parenthesized list of formal parameters. The statements that form the body of the function start at the next line, and must be indented. The first statement of the function body can optionally be a string literal; this string literal is the function’s documentation string, or docstring . (More about docstrings can be found in the section Documentation Strings .) There are tools which use docstrings to automatically produce online or printed documentation, or to let the user interactively browse through code; it’s good practice to include docstrings in code that you write, so make a habit of it. The execution of a function introduces a new symbol table used for the local variables of the function. More precisely, all variable assignments in a function store the value in the local symbol table; whereas variable references first look in the local symbol table, then in the local symbol tables of enclosing functions, then in the global symbol table, and finally in the table of built-in names. Thus, global variables and variables of enclosing functions cannot be directly assigned a value within a function (unless, for global variables, named in a global statement, or, for variables of enclosing functions, named in a nonlocal statement), although they may be referenced. The actual parameters (arguments) to a function call are introduced in the local symbol table of the called function when it is called; thus, arguments are passed using call by value (where the value is always an object reference , not the value of the object). [ 1 ] When a function calls another function, or calls itself recursively, a new local symbol table is created for that call. A function definition associates the function name with the function object in the current symbol table. The interpreter recognizes the object pointed to by that name as a user-defined function. Other names can also point to that same function object and can also be used to access the function: >>> fib <function fib at 10042ed0> >>> f = fib >>> f ( 100 ) 0 1 1 2 3 5 8 13 21 34 55 89 Coming from other languages, you might object that fib is not a function but a procedure since it doesn’t return a value. In fact, even functions without a return statement do return a value, albeit a rather boring one. This value is called None (it’s a built-in name). Writing the value None is normally suppressed by the interpreter if it would be the only value written. You can see it if you really want to using print() : >>> fib ( 0 ) >>> print ( fib ( 0 )) None It is simple to write a function that returns a list of the numbers of the Fibonacci series, instead of printing it: >>> def fib2 ( n ): # return Fibonacci series up to n ... """Return a list containing the Fibonacci series up to n.""" ... result = [] ... a , b = 0 , 1 ... while a < n : ... result . append ( a ) # see below ... a , b = b , a + b ... return result ... >>> f100 = fib2 ( 100 ) # call it >>> f100 # write the result [0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89] This example, as usual, demonstrates some new Python features: The return statement returns with a value from a function. return without an expression argument returns None . Falling off the end of a function also returns None . The statement result.append(a) calls a method of the list object result . A method is a function that ‘belongs’ to an object and is named obj.methodname , where obj is some object (this may be an expression), and methodname is the name of a method that is defined by the object’s type. Different types define different methods. Methods of different types may have the same name without causing ambiguity. (It is possible to define your own object types and methods, using classes , see Classes ) The method append() shown in the example is defined for list objects; it adds a new element at the end of the list. In this example it is equivalent to result = result + [a] , but more efficient. 4.9. More on Defining Functions ¶ It is also possible to define functions with a variable number of arguments. There are three forms, which can be combined. 4.9.1. Default Argument Values ¶ The most useful form is to specify a default value for one or more arguments. This creates a function that can be called with fewer arguments than it is defined to allow. For example: def ask_ok ( prompt , retries = 4 , reminder = 'Please try again!' ): while True : reply = input ( prompt ) if reply in { 'y' , 'ye' , 'yes' }: return True if reply in { 'n' , 'no' , 'nop' , 'nope' }: return False retries = retries - 1 if retries < 0 : raise ValueError ( 'invalid user response' ) print ( reminder ) This function can be called in several ways: giving only the mandatory argument: ask_ok('Do you really want to quit?') giving one of the optional arguments: ask_ok('OK to overwrite the file?', 2) or even giving all arguments: ask_ok('OK to overwrite the file?', 2, 'Come on, only yes or no!') This example also introduces the in keyword. This tests whether or not a sequence contains a certain value. The default values are evaluated at the point of function definition in the defining scope, so that i = 5 def f ( arg = i ): print ( arg ) i = 6 f () will print 5 . Important warning: The default value is evaluated only once. This makes a difference when the default is a mutable object such as a list, dictionary, or instances of most classes. For example, the following function accumulates the arguments passed to it on subsequent calls: def f ( a , L = []): L . append ( a ) return L print ( f ( 1 )) print ( f ( 2 )) print ( f ( 3 )) This will print [ 1 ] [ 1 , 2 ] [ 1 , 2 , 3 ] If you don’t want the default to be shared between subsequent calls, you can write the function like this instead: def f ( a , L = None ): if L is None : L = [] L . append ( a ) return L 4.9.2. Keyword Arguments ¶ Functions can also be called using keyword arguments of the form kwarg=value . For instance, the following function: def parrot ( voltage , state = 'a stiff' , action = 'voom' , type = 'Norwegian Blue' ): print ( "-- This parrot wouldn't" , action , end = ' ' ) print ( "if you put" , voltage , "volts through it." ) print ( "-- Lovely plumage, the" , type ) print ( "-- It's" , state , "!" ) accepts one required argument ( voltage ) and three optional arguments ( state , action , and type ). This function can be called in any of the following ways: parrot ( 1000 ) # 1 positional argument parrot ( voltage = 1000 ) # 1 keyword argument parrot ( voltage = 1000000 , action = 'VOOOOOM' ) # 2 keyword arguments parrot ( action = 'VOOOOOM' , voltage = 1000000 ) # 2 keyword arguments parrot ( 'a million' , 'bereft of life' , 'jump' ) # 3 positional arguments parrot ( 'a thousand' , state = 'pushing up the daisies' ) # 1 positional, 1 keyword but all the following calls would be invalid: parrot () # required argument missing parrot ( voltage = 5.0 , 'dead' ) # non-keyword argument after a keyword argument parrot ( 110 , voltage = 220 ) # duplicate value for the same argument parrot ( actor = 'John Cleese' ) # unknown keyword argument In a function call, keyword arguments must follow positional arguments. All the keyword arguments passed must match one of the arguments accepted by the function (e.g. actor is not a valid argument for the parrot function), and their order is not important. This also includes non-optional arguments (e.g. parrot(voltage=1000) is valid too). No argument may receive a value more than once. Here’s an example that fails due to this restriction: >>> def function ( a ): ... pass ... >>> function ( 0 , a = 0 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : function() got multiple values for argument 'a' When a final formal parameter of the form **name is present, it receives a dictionary (see Mapping Types — dict ) containing all keyword arguments except for those corresponding to a formal parameter. This may be combined with a formal parameter of the form *name (described in the next subsection) which receives a tuple containing the positional arguments beyond the formal parameter list. ( *name must occur before **name .) For example, if we define a function like this: def cheeseshop ( kind , * arguments , ** keywords ): print ( "-- Do you have any" , kind , "?" ) print ( "-- I'm sorry, we're all out of" , kind ) for arg in arguments : print ( arg ) print ( "-" * 40 ) for kw in keywords : print ( kw , ":" , keywords [ kw ]) It could be called like this: cheeseshop ( "Limburger" , "It's very runny, sir." , "It's really very, VERY runny, sir." , shopkeeper = "Michael Palin" , client = "John Cleese" , sketch = "Cheese Shop Sketch" ) and of course it would print: -- Do you have any Limburger ? -- I'm sorry, we're all out of Limburger It's very runny, sir. It's really very, VERY runny, sir. ---------------------------------------- shopkeeper : Michael Palin client : John Cleese sketch : Cheese Shop Sketch Note that the order in which the keyword arguments are printed is guaranteed to match the order in which they were provided in the function call. 4.9.3. Special parameters ¶ By default, arguments may be passed to a Python function either by position or explicitly by keyword. For readability and performance, it makes sense to restrict the way arguments can be passed so that a developer need only look at the function definition to determine if items are passed by position, by position or keyword, or by keyword. A function definition may look like: def f(pos1, pos2, /, pos_or_kwd, *, kwd1, kwd2): ----------- ---------- ---------- | | | | Positional or keyword | | - Keyword only -- Positional only where / and * are optional. If used, these symbols indicate the kind of parameter by how the arguments may be passed to the function: positional-only, positional-or-keyword, and keyword-only. Keyword parameters are also referred to as named parameters. 4.9.3.1. Positional-or-Keyword Arguments ¶ If / and * are not present in the function definition, arguments may be passed to a function by position or by keyword. 4.9.3.2. Positional-Only Parameters ¶ Looking at this in a bit more detail, it is possible to mark certain parameters as positional-only . If positional-only , the parameters’ order matters, and the parameters cannot be passed by keyword. Positional-only parameters are placed before a / (forward-slash). The / is used to logically separate the positional-only parameters from the rest of the parameters. If there is no / in the function definition, there are no positional-only parameters. Parameters following the / may be positional-or-keyword or keyword-only . 4.9.3.3. Keyword-Only Arguments ¶ To mark parameters as keyword-only , indicating the parameters must be passed by keyword argument, place an * in the arguments list just before the first keyword-only parameter. 4.9.3.4. Function Examples ¶ Consider the following example function definitions paying close attention to the markers / and * : >>> def standard_arg ( arg ): ... print ( arg ) ... >>> def pos_only_arg ( arg , / ): ... print ( arg ) ... >>> def kwd_only_arg ( * , arg ): ... print ( arg ) ... >>> def combined_example ( pos_only , / , standard , * , kwd_only ): ... print ( pos_only , standard , kwd_only ) The first function definition, standard_arg , the most familiar form, places no restrictions on the calling convention and arguments may be passed by position or keyword: >>> standard_arg ( 2 ) 2 >>> standard_arg ( arg = 2 ) 2 The second function pos_only_arg is restricted to only use positional parameters as there is a / in the function definition: >>> pos_only_arg ( 1 ) 1 >>> pos_only_arg ( arg = 1 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : pos_only_arg() got some positional-only arguments passed as keyword arguments: 'arg' The third function kwd_only_arg only allows keyword arguments as indicated by a * in the function definition: >>> kwd_only_arg ( 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : kwd_only_arg() takes 0 positional arguments but 1 was given >>> kwd_only_arg ( arg = 3 ) 3 And the last uses all three calling conventions in the same function definition: >>> combined_example ( 1 , 2 , 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() takes 2 positional arguments but 3 were given >>> combined_example ( 1 , 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( 1 , standard = 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( pos_only = 1 , standard = 2 , kwd_only = 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() got some positional-only arguments passed as keyword arguments: 'pos_only' Finally, consider this function definition which has a potential collision between the positional argument name and **kwds which has name as a key: def foo ( name , ** kwds ): return 'name' in kwds There is no possible call that will make it return True as the keyword 'name' will always bind to the first parameter. For example: >>> foo ( 1 , ** { 'name' : 2 }) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : foo() got multiple values for argument 'name' >>> But using / (positional only arguments), it is possible since it allows name as a positional argument and 'name' as a key in the keyword arguments: >>> def foo ( name , / , ** kwds ): ... return 'name' in kwds ... >>> foo ( 1 , ** { 'name' : 2 }) True In other words, the names of positional-only parameters can be used in **kwds without ambiguity. 4.9.3.5. Recap ¶ The use case will determine which parameters to use in the function definition: def f ( pos1 , pos2 , / , pos_or_kwd , * , kwd1 , kwd2 ): As guidance: Use positional-only if you want the name of the parameters to not be available to the user. This is useful when parameter names have no real meaning, if you want to enforce the order of the arguments when the function is called or if you need to take some positional parameters and arbitrary keywords. Use keyword-only when names have meaning and the function definition is more understandable by being explicit with names or you want to prevent users relying on the position of the argument being passed. For an API, use positional-only to prevent breaking API changes if the parameter’s name is modified in the future. 4.9.4. Arbitrary Argument Lists ¶ Finally, the least frequently used option is to specify that a function can be called with an arbitrary number of arguments. These arguments will be wrapped up in a tuple (see Tuples and Sequences ). Before the variable number of arguments, zero or more normal arguments may occur. def write_multiple_items ( file , separator , * args ): file . write ( separator . join ( args )) Normally, these variadic arguments will be last in the list of formal parameters, because they scoop up all remaining input arguments that are passed to the function. Any formal parameters which occur after the *args parameter are ‘keyword-only’ arguments, meaning that they can only be used as keywords rather than positional arguments. >>> def concat ( * args , sep = "/" ): ... return sep . join ( args ) ... >>> concat ( "earth" , "mars" , "venus" ) 'earth/mars/venus' >>> concat ( "earth" , "mars" , "venus" , sep = "." ) 'earth.mars.venus' 4.9.5. Unpacking Argument Lists ¶ The reverse situation occurs when the arguments are already in a list or tuple but need to be unpacked for a function call requiring separate positional arguments. For instance, the built-in range() function expects separate start and stop arguments. If they are not available separately, write the function call with the * -operator to unpack the arguments out of a list or tuple: >>> list ( range ( 3 , 6 )) # normal call with separate arguments [3, 4, 5] >>> args = [ 3 , 6 ] >>> list ( range ( * args )) # call with arguments unpacked from a list [3, 4, 5] In the same fashion, dictionaries can deliver keyword arguments with the ** -operator: >>> def parrot ( voltage , state = 'a stiff' , action = 'voom' ): ... print ( "-- This parrot wouldn't" , action , end = ' ' ) ... print ( "if you put" , voltage , "volts through it." , end = ' ' ) ... print ( "E's" , state , "!" ) ... >>> d = { "voltage" : "four million" , "state" : "bleedin' demised" , "action" : "VOOM" } >>> parrot ( ** d ) -- This parrot wouldn't VOOM if you put four million volts through it. E's bleedin' demised ! 4.9.6. Lambda Expressions ¶ Small anonymous functions can be created with the lambda keyword. This function returns the sum of its two arguments: lambda a, b: a+b . Lambda functions can be used wherever function objects are required. They are syntactically restricted to a single expression. Semantically, they are just syntactic sugar for a normal function definition. Like nested function definitions, lambda functions can reference variables from the containing scope: >>> def make_incrementor ( n ): ... return lambda x : x + n ... >>> f = make_incrementor ( 42 ) >>> f ( 0 ) 42 >>> f ( 1 ) 43 The above example uses a lambda expression to return a function. Another use is to pass a small function as an argument. For instance, list.sort() takes a sorting key function key which can be a lambda function: >>> pairs = [( 1 , 'one' ), ( 2 , 'two' ), ( 3 , 'three' ), ( 4 , 'four' )] >>> pairs . sort ( key = lambda pair : pair [ 1 ]) >>> pairs [(4, 'four'), (1, 'one'), (3, 'three'), (2, 'two')] 4.9.7. Documentation Strings ¶ Here are some conventions about the content and formatting of documentation strings. The first line should always be a short, concise summary of the object’s purpose. For brevity, it should not explicitly state the object’s name or type, since these are available by other means (except if the name happens to be a verb describing a function’s operation). This line should begin with a capital letter and end with a period. If there are more lines in the documentation string, the second line should be blank, visually separating the summary from the rest of the description. The following lines should be one or more paragraphs describing the object’s calling conventions, its side effects, etc. The Python parser strips indentation from multi-line string literals when they serve as module, class, or function docstrings. Here is an example of a multi-line docstring: >>> def my_function (): ... """Do nothing, but document it. ... ... No, really, it doesn't do anything: ... ... >>> my_function() ... >>> ... """ ... pass ... >>> print ( my_function . __doc__ ) Do nothing, but document it. No, really, it doesn't do anything: >>> my_function() >>> 4.9.8. Function Annotations ¶ Function annotations are completely optional metadata information about the types used by user-defined functions (see PEP 3107 and PEP 484 for more information). Annotations are stored in the __annotations__ attribute of the function as a dictionary and have no effect on any other part of the function. Parameter annotations are defined by a colon after the parameter name, followed by an expression evaluating to the value of the annotation. Return annotations are defined by a literal -> , followed by an expression, between the parameter list and the colon denoting the end of the def statement. The following example has a required argument, an optional argument, and the return value annotated: >>> def f ( ham : str , eggs : str = 'eggs' ) -> str : ... print ( "Annotations:" , f . __annotations__ ) ... print ( "Arguments:" , ham , eggs ) ... return ham + ' and ' + eggs ... >>> f ( 'spam' ) Annotations: {'ham': <class 'str'>, 'return': <class 'str'>, 'eggs': <class 'str'>} Arguments: spam eggs 'spam and eggs' 4.10. Intermezzo: Coding Style ¶ Now that you are about to write longer, more complex pieces of Python, it is a good time to talk about coding style . Most languages can be written (or more concise, formatted ) in different styles; some are more readable than others. Making it easy for others to read your code is always a good idea, and adopting a nice coding style helps tremendously for that. For Python, PEP 8 has emerged as the style guide that most projects adhere to; it promotes a very readable and eye-pleasing coding style. Every Python developer should read it at some point; here are the most important points extracted for you: Use 4-space indentation, and no tabs. 4 spaces are a good compromise between small indentation (allows greater nesting depth) and large indentation (easier to read). Tabs introduce confusion, and are best left out. Wrap lines so that they don’t exceed 79 characters. This helps users with small displays and makes it possible to have several code files side-by-side on larger displays. Use blank lines to separate functions and classes, and larger blocks of code inside functions. When possible, put comments on a line of their own. Use docstrings. Use spaces around operators and after commas, but not directly inside bracketing constructs: a = f(1, 2) + g(3, 4) . Name your classes and functions consistently; the convention is to use UpperCamelCase for classes and lowercase_with_underscores for functions and methods. Always use self as the name for the first method argument (see A First Look at Classes for more on classes and methods). Don’t use fancy encodings if your code is meant to be used in international environments. Python’s default, UTF-8, or even plain ASCII work best in any case. Likewise, don’t use non-ASCII characters in identifiers if there is only the slightest chance people speaking a different language will read or maintain the code. Footnotes [ 1 ] Actually, call by object reference would be a better description, since if a mutable object is passed, the caller will see any changes the callee makes to it (items inserted into a list). Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source « Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | Theme Auto Light Dark | © Copyright 2001 Python Software Foundation. This page is licensed under the Python Software Foundation License Version 2. Examples, recipes, and other code in the documentation are additionally licensed under the Zero Clause BSD License. See History and License for more information. The Python Software Foundation is a non-profit corporation. Please donate. Last updated on Jan 13, 2026 (06:19 UTC). Found a bug ? Created using Sphinx 8.2.3. | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/terms#main-content | Web Site Terms and Conditions of Use - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Web Site Terms and Conditions of Use 1. Terms By accessing this web site, you are agreeing to be bound by these web site Terms and Conditions of Use, our Privacy Policy , all applicable laws and regulations, and agree that you are responsible for compliance with any applicable local laws. If you do not agree with any of these terms, you are prohibited from using or accessing this site. The materials contained in this web site are protected by applicable copyright and trade mark law. 2. Use License Permission is granted to temporarily download one copy of the materials (information or software) on DEV Community's web site for personal, non-commercial transitory viewing only. This is the grant of a license, not a transfer of title, and under this license you may not: modify or copy the materials; use the materials for any commercial purpose, or for any public display (commercial or non-commercial); attempt to decompile or reverse engineer any software contained on DEV Community's web site; remove any copyright or other proprietary notations from the materials; or transfer the materials to another person or "mirror" the materials on any other server. This license shall automatically terminate if you violate any of these restrictions and may be terminated by DEV Community at any time. Upon terminating your viewing of these materials or upon the termination of this license, you must destroy any downloaded materials in your possession whether in electronic or printed format. 3. Disclaimer The materials on DEV Community's web site are provided "as is". DEV Community makes no warranties, expressed or implied, and hereby disclaims and negates all other warranties, including without limitation, implied warranties or conditions of merchantability, fitness for a particular purpose, or non-infringement of intellectual property or other violation of rights. Further, DEV Community does not warrant or make any representations concerning the accuracy, likely results, or reliability of the use of the materials on its Internet web site or otherwise relating to such materials or on any sites linked to this site. 4. Limitations In no event shall DEV Community or its suppliers be liable for any damages (including, without limitation, damages for loss of data or profit, or due to business interruption,) arising out of the use or inability to use the materials on DEV Community's Internet site, even if DEV Community or an authorized representative has been notified orally or in writing of the possibility of such damage. Because some jurisdictions do not allow limitations on implied warranties, or limitations of liability for consequential or incidental damages, these limitations may not apply to you. 5. Revisions and Errata The materials appearing on DEV Community's web site could include technical, typographical, or photographic errors. DEV Community does not warrant that any of the materials on its web site are accurate, complete, or current. DEV Community may make changes to the materials contained on its web site at any time without notice. DEV Community does not, however, make any commitment to update the materials. 6. Links DEV Community has not reviewed all of the sites linked to its Internet web site and is not responsible for the contents of any such linked site. The inclusion of any link does not imply endorsement by DEV Community of the site. Use of any such linked web site is at the user's own risk. 7. Copyright / Takedown Users agree and certify that they have rights to share all content that they post on DEV Community — including, but not limited to, information posted in articles, discussions, and comments. This rule applies to prose, code snippets, collections of links, etc. Regardless of citation, users may not post copy and pasted content that does not belong to them. DEV Community does not tolerate plagiarism of any kind, including mosaic or patchwork plagiarism. Users assume all risk for the content they post, including someone else's reliance on its accuracy, claims relating to intellectual property, or other legal rights. If you believe that a user has plagiarized content, misrepresented their identity, misappropriated work, or otherwise run afoul of DMCA regulations, please email support@dev.to. DEV Community may remove any content users post for any reason. 8. Site Terms of Use Modifications DEV Community may revise these terms of use for its web site at any time without notice. By using this web site you are agreeing to be bound by the then current version of these Terms and Conditions of Use. 9. DEV Community Trademarks and Logos Policy All uses of the DEV Community logo, DEV Community badges, brand slogans, iconography, and the like, may only be used with express permission from DEV Community. DEV Community reserves all rights, even if certain assets are included in DEV Community open source projects. Please contact support@dev.to with any questions or to request permission. 10. Reserved Names DEV Community has the right to maintain a list of reserved names which will not be made publicly available. These reserved names may be set aside for purposes of proactive trademark protection, avoiding user confusion, security measures, or any other reason (or no reason). Additionally, DEV Community reserves the right to change any already-claimed name at its sole discretion. In such cases, DEV Community will make reasonable effort to find a suitable alternative and assist with any transition-related concerns. 11. Content Policy The following policy applies to comments, articles, and all other works shared on the DEV Community platform: Users must make a good-faith effort to share content that is on-topic, of high-quality, and is not designed primarily for the purposes of promotion or creating backlinks. Posts must contain substantial content — they may not merely reference an external link that contains the full post. If a post contains affiliate links, that fact must be clearly disclosed. For instance, with language such as: “This post includes affiliate links; I may receive compensation if you purchase products or services from the different links provided in this article.” DEV Community reserves the right to remove any content that it deems to be in violation of this policy at its sole discretion. Additionally, DEV Community reserves the right to restrict any user’s ability to participate on the platform at its sole discretion. 12. Fees, Payment, Renewal Fees for Paid Services .Fees for Paid Services. Some of our Services may be offered for a fee (collectively, “Paid Services”). This section applies to any purchases of Paid Services. By using a Paid Service, you agree to pay the specified fees. Depending on the Paid Service, there may be different kinds of fees, for instance some that are one-time, recurring, and/or based on an advertising campaign budget that you set. For recurring fees (AKA Subscriptions), your subscription begins on your purchase date, and we’ll bill or charge you in the automatically-renewing interval (such as monthly, annually) you select, on a pre-pay basis until you cancel, which you can do at any time by contacting plusplus@dev.to . Payment. You must provide accurate and up-to-date payment information. By providing your payment information, you authorize us to store it until you request deletion. If your payment fails, we suspect fraud, or Paid Services are otherwise not paid for or paid for on time (for example, if you contact your bank or credit card company to decline or reverse the charge of fees for Paid Services), we may immediately cancel or revoke your access to Paid Services without notice to you. You authorize us to charge any updated payment information provided by your bank or payment service provider (e.g., new expiration date) or other payment methods provided if we can’t charge your primary payment method. Automatic Renewal. By enrolling in a subscription, you authorize us to automatically charge the then-applicable fees for each subsequent subscription period until the subscription is canceled. If you received a discount, used a coupon code, or subscribed during a free trial or promotion, your subscription will automatically renew for the full price of the subscription at the end of the discount period. This means that unless you cancel a subscription, it’ll automatically renew and we’ll charge your payment method(s). The date for the automatic renewal is based on the date of the original purchase and cannot be changed. You can view your renewal date(s), cancel, or manage subscriptions by contacting plusplus@dev.to . Fees and Changes. We may change our fees at any time in accordance with these Terms and requirements under applicable law. This means that we may change our fees going forward or remove or update features or functionality that were previously included in the fees. If you don’t agree with the changes, you must cancel your Paid Service. Refunds. There are no refunds and all payments are final. European Users: You have the right to withdraw from the transaction within fourteen (14) days from the date of the purchase without giving any reason as long as your purchase was not of downloadable content or of a customized nature, and (i) the service has not been fully performed, or (ii) subject to other limitations as permitted by law. If you cancel this contract, we will reimburse you all payments we have received from you, without undue delay and no later than within fourteen days from the day on which we received the notification of your cancellation of this contract. For this repayment, we will use the same means of payment that you used for the original transaction, unless expressly agreed otherwise with you; you will not be charged for this repayment. You may exercise your right to withdrawal by sending a clear, email request to plusplus@dev.to with the following information: List of services you wish to withdraw from List the date that you purchased the goods or services. If this is a recurring subscription, please list the most recent renewal date List your full legal name and the email associated with your account List the address in which you legally reside Today's Date 13. Governing Law Any claim relating to DEV Community's web site shall be governed by the laws of the State of New York without regard to its conflict of law provisions. General Terms and Conditions applicable to Use of a Web Site. 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/new/discuss | New Post - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Join the HMPL.js Forem HMPL.js Forem is a community of 3,676,891 amazing developers Continue with Apple Continue with Google Continue with Facebook Continue with Forem Continue with GitHub Continue with Twitter (X) OR Email Password Remember me Forgot password? By signing in, you are agreeing to our privacy policy , terms of use and code of conduct . New to HMPL.js Forem? Create account . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://docs.python.org/3/tutorial/controlflow.html#for-statements | 4. More Control Flow Tools — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | Theme Auto Light Dark | 4. More Control Flow Tools ¶ As well as the while statement just introduced, Python uses a few more that we will encounter in this chapter. 4.1. if Statements ¶ Perhaps the most well-known statement type is the if statement. For example: >>> x = int ( input ( "Please enter an integer: " )) Please enter an integer: 42 >>> if x < 0 : ... x = 0 ... print ( 'Negative changed to zero' ) ... elif x == 0 : ... print ( 'Zero' ) ... elif x == 1 : ... print ( 'Single' ) ... else : ... print ( 'More' ) ... More There can be zero or more elif parts, and the else part is optional. The keyword ‘ elif ’ is short for ‘else if’, and is useful to avoid excessive indentation. An if … elif … elif … sequence is a substitute for the switch or case statements found in other languages. If you’re comparing the same value to several constants, or checking for specific types or attributes, you may also find the match statement useful. For more details see match Statements . 4.2. for Statements ¶ The for statement in Python differs a bit from what you may be used to in C or Pascal. Rather than always iterating over an arithmetic progression of numbers (like in Pascal), or giving the user the ability to define both the iteration step and halting condition (as C), Python’s for statement iterates over the items of any sequence (a list or a string), in the order that they appear in the sequence. For example (no pun intended): >>> # Measure some strings: >>> words = [ 'cat' , 'window' , 'defenestrate' ] >>> for w in words : ... print ( w , len ( w )) ... cat 3 window 6 defenestrate 12 Code that modifies a collection while iterating over that same collection can be tricky to get right. Instead, it is usually more straight-forward to loop over a copy of the collection or to create a new collection: # Create a sample collection users = { 'Hans' : 'active' , 'Éléonore' : 'inactive' , '景太郎' : 'active' } # Strategy: Iterate over a copy for user , status in users . copy () . items (): if status == 'inactive' : del users [ user ] # Strategy: Create a new collection active_users = {} for user , status in users . items (): if status == 'active' : active_users [ user ] = status 4.3. The range() Function ¶ If you do need to iterate over a sequence of numbers, the built-in function range() comes in handy. It generates arithmetic progressions: >>> for i in range ( 5 ): ... print ( i ) ... 0 1 2 3 4 The given end point is never part of the generated sequence; range(10) generates 10 values, the legal indices for items of a sequence of length 10. It is possible to let the range start at another number, or to specify a different increment (even negative; sometimes this is called the ‘step’): >>> list ( range ( 5 , 10 )) [5, 6, 7, 8, 9] >>> list ( range ( 0 , 10 , 3 )) [0, 3, 6, 9] >>> list ( range ( - 10 , - 100 , - 30 )) [-10, -40, -70] To iterate over the indices of a sequence, you can combine range() and len() as follows: >>> a = [ 'Mary' , 'had' , 'a' , 'little' , 'lamb' ] >>> for i in range ( len ( a )): ... print ( i , a [ i ]) ... 0 Mary 1 had 2 a 3 little 4 lamb In most such cases, however, it is convenient to use the enumerate() function, see Looping Techniques . A strange thing happens if you just print a range: >>> range ( 10 ) range(0, 10) In many ways the object returned by range() behaves as if it is a list, but in fact it isn’t. It is an object which returns the successive items of the desired sequence when you iterate over it, but it doesn’t really make the list, thus saving space. We say such an object is iterable , that is, suitable as a target for functions and constructs that expect something from which they can obtain successive items until the supply is exhausted. We have seen that the for statement is such a construct, while an example of a function that takes an iterable is sum() : >>> sum ( range ( 4 )) # 0 + 1 + 2 + 3 6 Later we will see more functions that return iterables and take iterables as arguments. In chapter Data Structures , we will discuss in more detail about list() . 4.4. break and continue Statements ¶ The break statement breaks out of the innermost enclosing for or while loop: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( f " { n } equals { x } * { n // x } " ) ... break ... 4 equals 2 * 2 6 equals 2 * 3 8 equals 2 * 4 9 equals 3 * 3 The continue statement continues with the next iteration of the loop: >>> for num in range ( 2 , 10 ): ... if num % 2 == 0 : ... print ( f "Found an even number { num } " ) ... continue ... print ( f "Found an odd number { num } " ) ... Found an even number 2 Found an odd number 3 Found an even number 4 Found an odd number 5 Found an even number 6 Found an odd number 7 Found an even number 8 Found an odd number 9 4.5. else Clauses on Loops ¶ In a for or while loop the break statement may be paired with an else clause. If the loop finishes without executing the break , the else clause executes. In a for loop, the else clause is executed after the loop finishes its final iteration, that is, if no break occurred. In a while loop, it’s executed after the loop’s condition becomes false. In either kind of loop, the else clause is not executed if the loop was terminated by a break . Of course, other ways of ending the loop early, such as a return or a raised exception, will also skip execution of the else clause. This is exemplified in the following for loop, which searches for prime numbers: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( n , 'equals' , x , '*' , n // x ) ... break ... else : ... # loop fell through without finding a factor ... print ( n , 'is a prime number' ) ... 2 is a prime number 3 is a prime number 4 equals 2 * 2 5 is a prime number 6 equals 2 * 3 7 is a prime number 8 equals 2 * 4 9 equals 3 * 3 (Yes, this is the correct code. Look closely: the else clause belongs to the for loop, not the if statement.) One way to think of the else clause is to imagine it paired with the if inside the loop. As the loop executes, it will run a sequence like if/if/if/else. The if is inside the loop, encountered a number of times. If the condition is ever true, a break will happen. If the condition is never true, the else clause outside the loop will execute. When used with a loop, the else clause has more in common with the else clause of a try statement than it does with that of if statements: a try statement’s else clause runs when no exception occurs, and a loop’s else clause runs when no break occurs. For more on the try statement and exceptions, see Handling Exceptions . 4.6. pass Statements ¶ The pass statement does nothing. It can be used when a statement is required syntactically but the program requires no action. For example: >>> while True : ... pass # Busy-wait for keyboard interrupt (Ctrl+C) ... This is commonly used for creating minimal classes: >>> class MyEmptyClass : ... pass ... Another place pass can be used is as a place-holder for a function or conditional body when you are working on new code, allowing you to keep thinking at a more abstract level. The pass is silently ignored: >>> def initlog ( * args ): ... pass # Remember to implement this! ... For this last case, many people use the ellipsis literal ... instead of pass . This use has no special meaning to Python, and is not part of the language definition (you could use any constant expression here), but ... is used conventionally as a placeholder body as well. See The Ellipsis Object . 4.7. match Statements ¶ A match statement takes an expression and compares its value to successive patterns given as one or more case blocks. This is superficially similar to a switch statement in C, Java or JavaScript (and many other languages), but it’s more similar to pattern matching in languages like Rust or Haskell. Only the first pattern that matches gets executed and it can also extract components (sequence elements or object attributes) from the value into variables. If no case matches, none of the branches is executed. The simplest form compares a subject value against one or more literals: def http_error ( status ): match status : case 400 : return "Bad request" case 404 : return "Not found" case 418 : return "I'm a teapot" case _ : return "Something's wrong with the internet" Note the last block: the “variable name” _ acts as a wildcard and never fails to match. You can combine several literals in a single pattern using | (“or”): case 401 | 403 | 404 : return "Not allowed" Patterns can look like unpacking assignments, and can be used to bind variables: # point is an (x, y) tuple match point : case ( 0 , 0 ): print ( "Origin" ) case ( 0 , y ): print ( f "Y= { y } " ) case ( x , 0 ): print ( f "X= { x } " ) case ( x , y ): print ( f "X= { x } , Y= { y } " ) case _ : raise ValueError ( "Not a point" ) Study that one carefully! The first pattern has two literals, and can be thought of as an extension of the literal pattern shown above. But the next two patterns combine a literal and a variable, and the variable binds a value from the subject ( point ). The fourth pattern captures two values, which makes it conceptually similar to the unpacking assignment (x, y) = point . If you are using classes to structure your data you can use the class name followed by an argument list resembling a constructor, but with the ability to capture attributes into variables: class Point : def __init__ ( self , x , y ): self . x = x self . y = y def where_is ( point ): match point : case Point ( x = 0 , y = 0 ): print ( "Origin" ) case Point ( x = 0 , y = y ): print ( f "Y= { y } " ) case Point ( x = x , y = 0 ): print ( f "X= { x } " ) case Point (): print ( "Somewhere else" ) case _ : print ( "Not a point" ) You can use positional parameters with some builtin classes that provide an ordering for their attributes (e.g. dataclasses). You can also define a specific position for attributes in patterns by setting the __match_args__ special attribute in your classes. If it’s set to (“x”, “y”), the following patterns are all equivalent (and all bind the y attribute to the var variable): Point ( 1 , var ) Point ( 1 , y = var ) Point ( x = 1 , y = var ) Point ( y = var , x = 1 ) A recommended way to read patterns is to look at them as an extended form of what you would put on the left of an assignment, to understand which variables would be set to what. Only the standalone names (like var above) are assigned to by a match statement. Dotted names (like foo.bar ), attribute names (the x= and y= above) or class names (recognized by the “(…)” next to them like Point above) are never assigned to. Patterns can be arbitrarily nested. For example, if we have a short list of Points, with __match_args__ added, we could match it like this: class Point : __match_args__ = ( 'x' , 'y' ) def __init__ ( self , x , y ): self . x = x self . y = y match points : case []: print ( "No points" ) case [ Point ( 0 , 0 )]: print ( "The origin" ) case [ Point ( x , y )]: print ( f "Single point { x } , { y } " ) case [ Point ( 0 , y1 ), Point ( 0 , y2 )]: print ( f "Two on the Y axis at { y1 } , { y2 } " ) case _ : print ( "Something else" ) We can add an if clause to a pattern, known as a “guard”. If the guard is false, match goes on to try the next case block. Note that value capture happens before the guard is evaluated: match point : case Point ( x , y ) if x == y : print ( f "Y=X at { x } " ) case Point ( x , y ): print ( f "Not on the diagonal" ) Several other key features of this statement: Like unpacking assignments, tuple and list patterns have exactly the same meaning and actually match arbitrary sequences. An important exception is that they don’t match iterators or strings. Sequence patterns support extended unpacking: [x, y, *rest] and (x, y, *rest) work similar to unpacking assignments. The name after * may also be _ , so (x, y, *_) matches a sequence of at least two items without binding the remaining items. Mapping patterns: {"bandwidth": b, "latency": l} captures the "bandwidth" and "latency" values from a dictionary. Unlike sequence patterns, extra keys are ignored. An unpacking like **rest is also supported. (But **_ would be redundant, so it is not allowed.) Subpatterns may be captured using the as keyword: case ( Point ( x1 , y1 ), Point ( x2 , y2 ) as p2 ): ... will capture the second element of the input as p2 (as long as the input is a sequence of two points) Most literals are compared by equality, however the singletons True , False and None are compared by identity. Patterns may use named constants. These must be dotted names to prevent them from being interpreted as capture variable: from enum import Enum class Color ( Enum ): RED = 'red' GREEN = 'green' BLUE = 'blue' color = Color ( input ( "Enter your choice of 'red', 'blue' or 'green': " )) match color : case Color . RED : print ( "I see red!" ) case Color . GREEN : print ( "Grass is green" ) case Color . BLUE : print ( "I'm feeling the blues :(" ) For a more detailed explanation and additional examples, you can look into PEP 636 which is written in a tutorial format. 4.8. Defining Functions ¶ We can create a function that writes the Fibonacci series to an arbitrary boundary: >>> def fib ( n ): # write Fibonacci series less than n ... """Print a Fibonacci series less than n.""" ... a , b = 0 , 1 ... while a < n : ... print ( a , end = ' ' ) ... a , b = b , a + b ... print () ... >>> # Now call the function we just defined: >>> fib ( 2000 ) 0 1 1 2 3 5 8 13 21 34 55 89 144 233 377 610 987 1597 The keyword def introduces a function definition . It must be followed by the function name and the parenthesized list of formal parameters. The statements that form the body of the function start at the next line, and must be indented. The first statement of the function body can optionally be a string literal; this string literal is the function’s documentation string, or docstring . (More about docstrings can be found in the section Documentation Strings .) There are tools which use docstrings to automatically produce online or printed documentation, or to let the user interactively browse through code; it’s good practice to include docstrings in code that you write, so make a habit of it. The execution of a function introduces a new symbol table used for the local variables of the function. More precisely, all variable assignments in a function store the value in the local symbol table; whereas variable references first look in the local symbol table, then in the local symbol tables of enclosing functions, then in the global symbol table, and finally in the table of built-in names. Thus, global variables and variables of enclosing functions cannot be directly assigned a value within a function (unless, for global variables, named in a global statement, or, for variables of enclosing functions, named in a nonlocal statement), although they may be referenced. The actual parameters (arguments) to a function call are introduced in the local symbol table of the called function when it is called; thus, arguments are passed using call by value (where the value is always an object reference , not the value of the object). [ 1 ] When a function calls another function, or calls itself recursively, a new local symbol table is created for that call. A function definition associates the function name with the function object in the current symbol table. The interpreter recognizes the object pointed to by that name as a user-defined function. Other names can also point to that same function object and can also be used to access the function: >>> fib <function fib at 10042ed0> >>> f = fib >>> f ( 100 ) 0 1 1 2 3 5 8 13 21 34 55 89 Coming from other languages, you might object that fib is not a function but a procedure since it doesn’t return a value. In fact, even functions without a return statement do return a value, albeit a rather boring one. This value is called None (it’s a built-in name). Writing the value None is normally suppressed by the interpreter if it would be the only value written. You can see it if you really want to using print() : >>> fib ( 0 ) >>> print ( fib ( 0 )) None It is simple to write a function that returns a list of the numbers of the Fibonacci series, instead of printing it: >>> def fib2 ( n ): # return Fibonacci series up to n ... """Return a list containing the Fibonacci series up to n.""" ... result = [] ... a , b = 0 , 1 ... while a < n : ... result . append ( a ) # see below ... a , b = b , a + b ... return result ... >>> f100 = fib2 ( 100 ) # call it >>> f100 # write the result [0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89] This example, as usual, demonstrates some new Python features: The return statement returns with a value from a function. return without an expression argument returns None . Falling off the end of a function also returns None . The statement result.append(a) calls a method of the list object result . A method is a function that ‘belongs’ to an object and is named obj.methodname , where obj is some object (this may be an expression), and methodname is the name of a method that is defined by the object’s type. Different types define different methods. Methods of different types may have the same name without causing ambiguity. (It is possible to define your own object types and methods, using classes , see Classes ) The method append() shown in the example is defined for list objects; it adds a new element at the end of the list. In this example it is equivalent to result = result + [a] , but more efficient. 4.9. More on Defining Functions ¶ It is also possible to define functions with a variable number of arguments. There are three forms, which can be combined. 4.9.1. Default Argument Values ¶ The most useful form is to specify a default value for one or more arguments. This creates a function that can be called with fewer arguments than it is defined to allow. For example: def ask_ok ( prompt , retries = 4 , reminder = 'Please try again!' ): while True : reply = input ( prompt ) if reply in { 'y' , 'ye' , 'yes' }: return True if reply in { 'n' , 'no' , 'nop' , 'nope' }: return False retries = retries - 1 if retries < 0 : raise ValueError ( 'invalid user response' ) print ( reminder ) This function can be called in several ways: giving only the mandatory argument: ask_ok('Do you really want to quit?') giving one of the optional arguments: ask_ok('OK to overwrite the file?', 2) or even giving all arguments: ask_ok('OK to overwrite the file?', 2, 'Come on, only yes or no!') This example also introduces the in keyword. This tests whether or not a sequence contains a certain value. The default values are evaluated at the point of function definition in the defining scope, so that i = 5 def f ( arg = i ): print ( arg ) i = 6 f () will print 5 . Important warning: The default value is evaluated only once. This makes a difference when the default is a mutable object such as a list, dictionary, or instances of most classes. For example, the following function accumulates the arguments passed to it on subsequent calls: def f ( a , L = []): L . append ( a ) return L print ( f ( 1 )) print ( f ( 2 )) print ( f ( 3 )) This will print [ 1 ] [ 1 , 2 ] [ 1 , 2 , 3 ] If you don’t want the default to be shared between subsequent calls, you can write the function like this instead: def f ( a , L = None ): if L is None : L = [] L . append ( a ) return L 4.9.2. Keyword Arguments ¶ Functions can also be called using keyword arguments of the form kwarg=value . For instance, the following function: def parrot ( voltage , state = 'a stiff' , action = 'voom' , type = 'Norwegian Blue' ): print ( "-- This parrot wouldn't" , action , end = ' ' ) print ( "if you put" , voltage , "volts through it." ) print ( "-- Lovely plumage, the" , type ) print ( "-- It's" , state , "!" ) accepts one required argument ( voltage ) and three optional arguments ( state , action , and type ). This function can be called in any of the following ways: parrot ( 1000 ) # 1 positional argument parrot ( voltage = 1000 ) # 1 keyword argument parrot ( voltage = 1000000 , action = 'VOOOOOM' ) # 2 keyword arguments parrot ( action = 'VOOOOOM' , voltage = 1000000 ) # 2 keyword arguments parrot ( 'a million' , 'bereft of life' , 'jump' ) # 3 positional arguments parrot ( 'a thousand' , state = 'pushing up the daisies' ) # 1 positional, 1 keyword but all the following calls would be invalid: parrot () # required argument missing parrot ( voltage = 5.0 , 'dead' ) # non-keyword argument after a keyword argument parrot ( 110 , voltage = 220 ) # duplicate value for the same argument parrot ( actor = 'John Cleese' ) # unknown keyword argument In a function call, keyword arguments must follow positional arguments. All the keyword arguments passed must match one of the arguments accepted by the function (e.g. actor is not a valid argument for the parrot function), and their order is not important. This also includes non-optional arguments (e.g. parrot(voltage=1000) is valid too). No argument may receive a value more than once. Here’s an example that fails due to this restriction: >>> def function ( a ): ... pass ... >>> function ( 0 , a = 0 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : function() got multiple values for argument 'a' When a final formal parameter of the form **name is present, it receives a dictionary (see Mapping Types — dict ) containing all keyword arguments except for those corresponding to a formal parameter. This may be combined with a formal parameter of the form *name (described in the next subsection) which receives a tuple containing the positional arguments beyond the formal parameter list. ( *name must occur before **name .) For example, if we define a function like this: def cheeseshop ( kind , * arguments , ** keywords ): print ( "-- Do you have any" , kind , "?" ) print ( "-- I'm sorry, we're all out of" , kind ) for arg in arguments : print ( arg ) print ( "-" * 40 ) for kw in keywords : print ( kw , ":" , keywords [ kw ]) It could be called like this: cheeseshop ( "Limburger" , "It's very runny, sir." , "It's really very, VERY runny, sir." , shopkeeper = "Michael Palin" , client = "John Cleese" , sketch = "Cheese Shop Sketch" ) and of course it would print: -- Do you have any Limburger ? -- I'm sorry, we're all out of Limburger It's very runny, sir. It's really very, VERY runny, sir. ---------------------------------------- shopkeeper : Michael Palin client : John Cleese sketch : Cheese Shop Sketch Note that the order in which the keyword arguments are printed is guaranteed to match the order in which they were provided in the function call. 4.9.3. Special parameters ¶ By default, arguments may be passed to a Python function either by position or explicitly by keyword. For readability and performance, it makes sense to restrict the way arguments can be passed so that a developer need only look at the function definition to determine if items are passed by position, by position or keyword, or by keyword. A function definition may look like: def f(pos1, pos2, /, pos_or_kwd, *, kwd1, kwd2): ----------- ---------- ---------- | | | | Positional or keyword | | - Keyword only -- Positional only where / and * are optional. If used, these symbols indicate the kind of parameter by how the arguments may be passed to the function: positional-only, positional-or-keyword, and keyword-only. Keyword parameters are also referred to as named parameters. 4.9.3.1. Positional-or-Keyword Arguments ¶ If / and * are not present in the function definition, arguments may be passed to a function by position or by keyword. 4.9.3.2. Positional-Only Parameters ¶ Looking at this in a bit more detail, it is possible to mark certain parameters as positional-only . If positional-only , the parameters’ order matters, and the parameters cannot be passed by keyword. Positional-only parameters are placed before a / (forward-slash). The / is used to logically separate the positional-only parameters from the rest of the parameters. If there is no / in the function definition, there are no positional-only parameters. Parameters following the / may be positional-or-keyword or keyword-only . 4.9.3.3. Keyword-Only Arguments ¶ To mark parameters as keyword-only , indicating the parameters must be passed by keyword argument, place an * in the arguments list just before the first keyword-only parameter. 4.9.3.4. Function Examples ¶ Consider the following example function definitions paying close attention to the markers / and * : >>> def standard_arg ( arg ): ... print ( arg ) ... >>> def pos_only_arg ( arg , / ): ... print ( arg ) ... >>> def kwd_only_arg ( * , arg ): ... print ( arg ) ... >>> def combined_example ( pos_only , / , standard , * , kwd_only ): ... print ( pos_only , standard , kwd_only ) The first function definition, standard_arg , the most familiar form, places no restrictions on the calling convention and arguments may be passed by position or keyword: >>> standard_arg ( 2 ) 2 >>> standard_arg ( arg = 2 ) 2 The second function pos_only_arg is restricted to only use positional parameters as there is a / in the function definition: >>> pos_only_arg ( 1 ) 1 >>> pos_only_arg ( arg = 1 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : pos_only_arg() got some positional-only arguments passed as keyword arguments: 'arg' The third function kwd_only_arg only allows keyword arguments as indicated by a * in the function definition: >>> kwd_only_arg ( 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : kwd_only_arg() takes 0 positional arguments but 1 was given >>> kwd_only_arg ( arg = 3 ) 3 And the last uses all three calling conventions in the same function definition: >>> combined_example ( 1 , 2 , 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() takes 2 positional arguments but 3 were given >>> combined_example ( 1 , 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( 1 , standard = 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( pos_only = 1 , standard = 2 , kwd_only = 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() got some positional-only arguments passed as keyword arguments: 'pos_only' Finally, consider this function definition which has a potential collision between the positional argument name and **kwds which has name as a key: def foo ( name , ** kwds ): return 'name' in kwds There is no possible call that will make it return True as the keyword 'name' will always bind to the first parameter. For example: >>> foo ( 1 , ** { 'name' : 2 }) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : foo() got multiple values for argument 'name' >>> But using / (positional only arguments), it is possible since it allows name as a positional argument and 'name' as a key in the keyword arguments: >>> def foo ( name , / , ** kwds ): ... return 'name' in kwds ... >>> foo ( 1 , ** { 'name' : 2 }) True In other words, the names of positional-only parameters can be used in **kwds without ambiguity. 4.9.3.5. Recap ¶ The use case will determine which parameters to use in the function definition: def f ( pos1 , pos2 , / , pos_or_kwd , * , kwd1 , kwd2 ): As guidance: Use positional-only if you want the name of the parameters to not be available to the user. This is useful when parameter names have no real meaning, if you want to enforce the order of the arguments when the function is called or if you need to take some positional parameters and arbitrary keywords. Use keyword-only when names have meaning and the function definition is more understandable by being explicit with names or you want to prevent users relying on the position of the argument being passed. For an API, use positional-only to prevent breaking API changes if the parameter’s name is modified in the future. 4.9.4. Arbitrary Argument Lists ¶ Finally, the least frequently used option is to specify that a function can be called with an arbitrary number of arguments. These arguments will be wrapped up in a tuple (see Tuples and Sequences ). Before the variable number of arguments, zero or more normal arguments may occur. def write_multiple_items ( file , separator , * args ): file . write ( separator . join ( args )) Normally, these variadic arguments will be last in the list of formal parameters, because they scoop up all remaining input arguments that are passed to the function. Any formal parameters which occur after the *args parameter are ‘keyword-only’ arguments, meaning that they can only be used as keywords rather than positional arguments. >>> def concat ( * args , sep = "/" ): ... return sep . join ( args ) ... >>> concat ( "earth" , "mars" , "venus" ) 'earth/mars/venus' >>> concat ( "earth" , "mars" , "venus" , sep = "." ) 'earth.mars.venus' 4.9.5. Unpacking Argument Lists ¶ The reverse situation occurs when the arguments are already in a list or tuple but need to be unpacked for a function call requiring separate positional arguments. For instance, the built-in range() function expects separate start and stop arguments. If they are not available separately, write the function call with the * -operator to unpack the arguments out of a list or tuple: >>> list ( range ( 3 , 6 )) # normal call with separate arguments [3, 4, 5] >>> args = [ 3 , 6 ] >>> list ( range ( * args )) # call with arguments unpacked from a list [3, 4, 5] In the same fashion, dictionaries can deliver keyword arguments with the ** -operator: >>> def parrot ( voltage , state = 'a stiff' , action = 'voom' ): ... print ( "-- This parrot wouldn't" , action , end = ' ' ) ... print ( "if you put" , voltage , "volts through it." , end = ' ' ) ... print ( "E's" , state , "!" ) ... >>> d = { "voltage" : "four million" , "state" : "bleedin' demised" , "action" : "VOOM" } >>> parrot ( ** d ) -- This parrot wouldn't VOOM if you put four million volts through it. E's bleedin' demised ! 4.9.6. Lambda Expressions ¶ Small anonymous functions can be created with the lambda keyword. This function returns the sum of its two arguments: lambda a, b: a+b . Lambda functions can be used wherever function objects are required. They are syntactically restricted to a single expression. Semantically, they are just syntactic sugar for a normal function definition. Like nested function definitions, lambda functions can reference variables from the containing scope: >>> def make_incrementor ( n ): ... return lambda x : x + n ... >>> f = make_incrementor ( 42 ) >>> f ( 0 ) 42 >>> f ( 1 ) 43 The above example uses a lambda expression to return a function. Another use is to pass a small function as an argument. For instance, list.sort() takes a sorting key function key which can be a lambda function: >>> pairs = [( 1 , 'one' ), ( 2 , 'two' ), ( 3 , 'three' ), ( 4 , 'four' )] >>> pairs . sort ( key = lambda pair : pair [ 1 ]) >>> pairs [(4, 'four'), (1, 'one'), (3, 'three'), (2, 'two')] 4.9.7. Documentation Strings ¶ Here are some conventions about the content and formatting of documentation strings. The first line should always be a short, concise summary of the object’s purpose. For brevity, it should not explicitly state the object’s name or type, since these are available by other means (except if the name happens to be a verb describing a function’s operation). This line should begin with a capital letter and end with a period. If there are more lines in the documentation string, the second line should be blank, visually separating the summary from the rest of the description. The following lines should be one or more paragraphs describing the object’s calling conventions, its side effects, etc. The Python parser strips indentation from multi-line string literals when they serve as module, class, or function docstrings. Here is an example of a multi-line docstring: >>> def my_function (): ... """Do nothing, but document it. ... ... No, really, it doesn't do anything: ... ... >>> my_function() ... >>> ... """ ... pass ... >>> print ( my_function . __doc__ ) Do nothing, but document it. No, really, it doesn't do anything: >>> my_function() >>> 4.9.8. Function Annotations ¶ Function annotations are completely optional metadata information about the types used by user-defined functions (see PEP 3107 and PEP 484 for more information). Annotations are stored in the __annotations__ attribute of the function as a dictionary and have no effect on any other part of the function. Parameter annotations are defined by a colon after the parameter name, followed by an expression evaluating to the value of the annotation. Return annotations are defined by a literal -> , followed by an expression, between the parameter list and the colon denoting the end of the def statement. The following example has a required argument, an optional argument, and the return value annotated: >>> def f ( ham : str , eggs : str = 'eggs' ) -> str : ... print ( "Annotations:" , f . __annotations__ ) ... print ( "Arguments:" , ham , eggs ) ... return ham + ' and ' + eggs ... >>> f ( 'spam' ) Annotations: {'ham': <class 'str'>, 'return': <class 'str'>, 'eggs': <class 'str'>} Arguments: spam eggs 'spam and eggs' 4.10. Intermezzo: Coding Style ¶ Now that you are about to write longer, more complex pieces of Python, it is a good time to talk about coding style . Most languages can be written (or more concise, formatted ) in different styles; some are more readable than others. Making it easy for others to read your code is always a good idea, and adopting a nice coding style helps tremendously for that. For Python, PEP 8 has emerged as the style guide that most projects adhere to; it promotes a very readable and eye-pleasing coding style. Every Python developer should read it at some point; here are the most important points extracted for you: Use 4-space indentation, and no tabs. 4 spaces are a good compromise between small indentation (allows greater nesting depth) and large indentation (easier to read). Tabs introduce confusion, and are best left out. Wrap lines so that they don’t exceed 79 characters. This helps users with small displays and makes it possible to have several code files side-by-side on larger displays. Use blank lines to separate functions and classes, and larger blocks of code inside functions. When possible, put comments on a line of their own. Use docstrings. Use spaces around operators and after commas, but not directly inside bracketing constructs: a = f(1, 2) + g(3, 4) . Name your classes and functions consistently; the convention is to use UpperCamelCase for classes and lowercase_with_underscores for functions and methods. Always use self as the name for the first method argument (see A First Look at Classes for more on classes and methods). Don’t use fancy encodings if your code is meant to be used in international environments. Python’s default, UTF-8, or even plain ASCII work best in any case. Likewise, don’t use non-ASCII characters in identifiers if there is only the slightest chance people speaking a different language will read or maintain the code. Footnotes [ 1 ] Actually, call by object reference would be a better description, since if a mutable object is passed, the caller will see any changes the callee makes to it (items inserted into a list). Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source « Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | Theme Auto Light Dark | © Copyright 2001 Python Software Foundation. This page is licensed under the Python Software Foundation License Version 2. Examples, recipes, and other code in the documentation are additionally licensed under the Zero Clause BSD License. See History and License for more information. The Python Software Foundation is a non-profit corporation. Please donate. Last updated on Jan 13, 2026 (06:19 UTC). Found a bug ? Created using Sphinx 8.2.3. | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/about#what-to-discuss-here | About HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close About HMPL.js Forem Welcome to the HMPL.js Forem! Hello and welcome, developers! This is the official community hub for HMPL.js, the server-oriented, customizable templating language for JavaScript. If you're excited about building dynamic, modern, and incredibly small web applications by keeping logic on the server and fetching HTML, you've found your home. What This Community Is About Our mission is to create a central place for developers to learn, discuss, and master HMPL.js. We believe in building powerful user interfaces with minimal client-side JavaScript, leveraging the server to do the heavy lifting. HMPL.js is designed to be: Flexible: Get the benefits of SSR on any platform, whether it's a simple static site or a complex single-page application. Easy to Use: Describe a couple of properties in an object and get ready-to-use HTML directly from your server. Reliable: With 100% code coverage and built-in protection against XSS vulnerabilities (using DOMPurify), you can build with confidence. Lightweight: All this functionality is packed into just ~24 kilobytes, making your apps significantly smaller than those built with other popular tools. This forum is the place to explore these concepts, share your successes, and get help when you need it. What to Discuss Here We encourage a wide range of discussions. Whether you're a beginner or an expert, your voice is welcome. Here are a few ideas to get you started: Questions & Support: Need help with installation, hmpl.compile() , or the hmpl-dom module? Ask away! Use the #help tag. Show & Tell: Share the awesome things you've built with HMPL.js. Post a link to your project or a code snippet. Use the #showdev tag. Tutorials & Guides: Found a great way to solve a common problem? Write a post to share your knowledge with the community. Use the #tutorial tag. In-Depth Discussions: Let's talk about best practices, performance, or how HMPL.js compares to libraries like HTMX and Alpine.js. Use the #discuss tag. Ideas & Feedback: Have a suggestion for a new feature or an improvement? We'd love to hear it! How to Get Involved Jumping in is easy! Introduce yourself in the comments of a welcome thread. Ask a question or help answer someone else's. Share your project or a cool code snippet you've written. Experiment with the online HMPL Playground and share your creations. Our Community Guidelines To ensure this remains a friendly and productive space for everyone, we ask that you follow a few simple principles: Be Kind and Respectful: Treat everyone with courtesy. Healthy debate is encouraged, but personal attacks are not. Be Collaborative: This is a space for learning together. Share what you know, and be open to learning from others. Stay Constructive: Offer feedback that is helpful, supportive, and aimed at moving the conversation forward. Stay On Topic: Keep discussions focused on HMPL.js and related web development technologies. We're thrilled to have you here. Let's build something amazing together 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://www.facebook.com/sharer.php?u=https%3A%2F%2Fdev.to%2Frsionnach%2Fshift-left-reliability-4poo | Facebook에 로그인 Notice 계속하려면 로그인해주세요. Facebook에 로그인 계속하려면 로그인해주세요. 로그인 계정을 잊으셨나요? 또는 새 계정 만들기 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch 가입하기 로그인 Messenger Facebook Lite 동영상 Meta Pay Meta 스토어 Meta Quest Ray-Ban Meta Meta AI Meta AI 콘텐츠 더 보기 Instagram Threads 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026 | 2026-01-13T08:49:06 |
https://dev.to/stackforgetx/getting-started-with-fortune-sheet-in-react-building-your-first-spreadsheet-76g | Getting Started with Fortune Sheet in React: Building Your First Spreadsheet - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Michael Turner Posted on Jan 12 Getting Started with Fortune Sheet in React: Building Your First Spreadsheet # react # webdev # programming # tutorial Fortune Sheet is a powerful, open-source spreadsheet component for React that provides Excel-like functionality directly in your web application. It offers features like cell editing, formulas, formatting, and data manipulation, making it perfect for building data-intensive applications. This guide walks through setting up and creating your first interactive spreadsheet using Fortune Sheet with React, from installation to a working implementation. This is part 1 of a series on using Fortune Sheet with React. Prerequisites Before you begin, make sure you have: Node.js version 16.0 or higher installed npm , yarn , or pnpm package manager A React project (version 16.8 or higher) or create-react-app setup Basic knowledge of React hooks (useState, useEffect) Installation Install Fortune Sheet and its dependencies using your preferred package manager: npm install fortune-sheet Enter fullscreen mode Exit fullscreen mode Or with yarn: yarn add fortune-sheet Enter fullscreen mode Exit fullscreen mode Or with pnpm: pnpm add fortune-sheet Enter fullscreen mode Exit fullscreen mode After installation, your package.json should include the dependency: { "dependencies" : { "fortune-sheet" : "^1.0.0" , "react" : "^18.0.0" , "react-dom" : "^18.0.0" } } Enter fullscreen mode Exit fullscreen mode Project Setup Fortune Sheet requires CSS styles to be imported. Create or update your main entry file (typically src/index.js or src/main.jsx ) to include the necessary styles: // src/index.js import React from ' react ' ; import ReactDOM from ' react-dom/client ' ; import ' fortune-sheet/dist/fortune-sheet.css ' ; import App from ' ./App ' ; const root = ReactDOM . createRoot ( document . getElementById ( ' root ' )); root . render ( < React . StrictMode > < App /> < /React.StrictMode > ); Enter fullscreen mode Exit fullscreen mode If you're using a CSS-in-JS solution or want to import styles differently, you can also import the CSS in your component file. First Example / Basic Usage Let's create a simple spreadsheet component to get started. Create a new file src/Spreadsheet.jsx : // src/Spreadsheet.jsx import React , { useRef , useEffect } from ' react ' ; import FortuneSheet from ' fortune-sheet ' ; function Spreadsheet () { const containerRef = useRef ( null ); useEffect (() => { if ( containerRef . current ) { // Initialize Fortune Sheet const sheet = new FortuneSheet ( containerRef . current , { data : [ [ { v : ' Name ' , ct : { fa : ' General ' , t : ' g ' } }, { v : ' Age ' , ct : { fa : ' General ' , t : ' g ' } }, { v : ' City ' , ct : { fa : ' General ' , t : ' g ' } } ], [ { v : ' John ' , ct : { fa : ' General ' , t : ' g ' } }, { v : 25 , ct : { fa : ' General ' , t : ' n ' } }, { v : ' New York ' , ct : { fa : ' General ' , t : ' g ' } } ], [ { v : ' Jane ' , ct : { fa : ' General ' , t : ' g ' } }, { v : 30 , ct : { fa : ' General ' , t : ' n ' } }, { v : ' London ' , ct : { fa : ' General ' , t : ' g ' } } ] ], defaultRowHeight : 25 , defaultColWidth : 100 }); // Cleanup on unmount return () => { if ( sheet && sheet . destroy ) { sheet . destroy (); } }; } }, []); return ( < div ref = { containerRef } style = { { width : ' 100% ' , height : ' 500px ' } } /> ); } export default Spreadsheet ; Enter fullscreen mode Exit fullscreen mode Now, update your App.jsx to use the spreadsheet: // src/App.jsx import React from ' react ' ; import Spreadsheet from ' ./Spreadsheet ' ; import ' ./App.css ' ; function App () { return ( < div className = "App" > < h1 > Fortune Sheet Example </ h1 > < Spreadsheet /> </ div > ); } export default App ; Enter fullscreen mode Exit fullscreen mode This creates a basic spreadsheet with three columns (Name, Age, City) and two rows of data. The spreadsheet is fully interactive - you can click on cells to edit them, navigate with arrow keys, and resize columns. Understanding the Basics Fortune Sheet uses a data structure where each cell is represented as an object with: v : The cell value (can be a string, number, or formula) ct : Cell type information with format ( fa ) and type ( t ) t: 'g' for general/text t: 'n' for numbers The component initializes with a container DOM element and a configuration object. The configuration includes: data : A 2D array of cell objects representing the spreadsheet data defaultRowHeight : Height of rows in pixels defaultColWidth : Width of columns in pixels Here's a simpler example with just text data: // src/SimpleSpreadsheet.jsx import React , { useRef , useEffect } from ' react ' ; import FortuneSheet from ' fortune-sheet ' ; function SimpleSpreadsheet () { const containerRef = useRef ( null ); useEffect (() => { if ( containerRef . current ) { const sheet = new FortuneSheet ( containerRef . current , { data : [ [{ v : ' A1 ' }, { v : ' B1 ' }, { v : ' C1 ' }], [{ v : ' A2 ' }, { v : ' B2 ' }, { v : ' C2 ' }], [{ v : ' A3 ' }, { v : ' B3 ' }, { v : ' C3 ' }] ] }); return () => { if ( sheet && sheet . destroy ) { sheet . destroy (); } }; } }, []); return ( < div ref = { containerRef } style = { { width : ' 100% ' , height : ' 400px ' , border : ' 1px solid #ddd ' } } /> ); } export default SimpleSpreadsheet ; Enter fullscreen mode Exit fullscreen mode Practical Example / Building Something Real Let's build a more practical example - a budget tracker spreadsheet. This will demonstrate how to work with formulas and handle user interactions: // src/BudgetTracker.jsx import React , { useRef , useEffect , useState } from ' react ' ; import FortuneSheet from ' fortune-sheet ' ; import ' fortune-sheet/dist/fortune-sheet.css ' ; function BudgetTracker () { const containerRef = useRef ( null ); const [ sheetInstance , setSheetInstance ] = useState ( null ); useEffect (() => { if ( containerRef . current ) { const sheet = new FortuneSheet ( containerRef . current , { data : [ [ { v : ' Category ' , ct : { fa : ' General ' , t : ' g ' } }, { v : ' Budgeted ' , ct : { fa : ' General ' , t : ' g ' } }, { v : ' Spent ' , ct : { fa : ' General ' , t : ' g ' } }, { v : ' Remaining ' , ct : { fa : ' General ' , t : ' g ' } } ], [ { v : ' Food ' , ct : { fa : ' General ' , t : ' g ' } }, { v : 500 , ct : { fa : ' General ' , t : ' n ' } }, { v : 320 , ct : { fa : ' General ' , t : ' n ' } }, { v : ' =B2-C2 ' , ct : { fa : ' General ' , t : ' g ' } } ], [ { v : ' Transportation ' , ct : { fa : ' General ' , t : ' g ' } }, { v : 200 , ct : { fa : ' General ' , t : ' n ' } }, { v : 150 , ct : { fa : ' General ' , t : ' n ' } }, { v : ' =B3-C3 ' , ct : { fa : ' General ' , t : ' g ' } } ], [ { v : ' Entertainment ' , ct : { fa : ' General ' , t : ' g ' } }, { v : 300 , ct : { fa : ' General ' , t : ' n ' } }, { v : 280 , ct : { fa : ' General ' , t : ' n ' } }, { v : ' =B4-C4 ' , ct : { fa : ' General ' , t : ' g ' } } ], [ { v : ' Total ' , ct : { fa : ' General ' , t : ' g ' } }, { v : ' =SUM(B2:B4) ' , ct : { fa : ' General ' , t : ' g ' } }, { v : ' =SUM(C2:C4) ' , ct : { fa : ' General ' , t : ' g ' } }, { v : ' =SUM(D2:D4) ' , ct : { fa : ' General ' , t : ' g ' } } ] ], defaultRowHeight : 30 , defaultColWidth : 120 , allowEdit : true }); setSheetInstance ( sheet ); return () => { if ( sheet && sheet . destroy ) { sheet . destroy (); } }; } }, []); return ( < div style = { { padding : ' 20px ' } } > < h2 > Monthly Budget Tracker </ h2 > < div ref = { containerRef } style = { { width : ' 100% ' , height : ' 400px ' , border : ' 1px solid #ccc ' , borderRadius : ' 4px ' } } /> </ div > ); } export default BudgetTracker ; Enter fullscreen mode Exit fullscreen mode This example creates a functional budget tracker with: Headers for categories and columns Budgeted and spent amounts Formulas to calculate remaining amounts A total row with SUM formulas Full editing capabilities Common Issues / Troubleshooting Spreadsheet not rendering : Make sure you've imported the CSS file ( fortune-sheet/dist/fortune-sheet.css ). Without the styles, the spreadsheet may not display correctly. Container has no height : The container div must have an explicit height. Use inline styles or CSS to set a height (e.g., height: '500px' ). Memory leaks : Always clean up the sheet instance in the useEffect cleanup function by calling sheet.destroy() to prevent memory leaks. Data format errors : Ensure your data array follows the correct structure with cell objects containing v (value) and ct (cell type) properties. Next Steps Now that you have a basic understanding of Fortune Sheet: Learn about advanced features like cell formatting, conditional formatting, and data validation Explore how to save and load spreadsheet data Discover how to customize the appearance and add custom functions Check out the official repository: https://github.com/ruilisi/fortune-sheet Look for part 2 of this series for more advanced topics Summary You've successfully set up Fortune Sheet in your React application and created your first interactive spreadsheet. You can now create spreadsheets with editable cells, formulas, and custom data structures. The library provides a solid foundation for building data-intensive applications with Excel-like functionality. Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Michael Turner Follow Software developer focused on Web3 infrastructure. Cross-chain systems, APIs, smart contracts. Real-world examples on GitHub. Joined Dec 21, 2025 Trending on DEV Community Hot The First Week at a Startup Taught Me More Than I Expected # startup # beginners # career # learning AI should not be in Code Editors # programming # ai # productivity # discuss Prompt Engineering Won’t Fix Your Architecture # discuss # career # ai # programming 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/t/go | Go - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Go Follow Hide A statically typed, compiled programming language designed at Google Create Post submission guidelines Write! Just keep it clean and civil! about #go Go is an open source programming language that makes it easy to build simple, reliable, and efficient software. Go is expressive, concise, clean, and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language. https://go.dev/doc/ Older #go posts 1 2 3 4 5 6 7 8 9 … 75 … 398 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Zig vs Go: init and run Paolo Carraro Paolo Carraro Paolo Carraro Follow Jan 12 Zig vs Go: init and run # zig # go # programming # comparison Comments Add Comment 2 min read Super Fast Markdown Linting for Go Developers: Meet gomarklint Kazu Kazu Kazu Follow Jan 13 Super Fast Markdown Linting for Go Developers: Meet gomarklint # showdev # go # performance # markdown Comments Add Comment 4 min read [Golang] Garbage Collection in General Satyajit Roy Satyajit Roy Satyajit Roy Follow Jan 13 [Golang] Garbage Collection in General # go # programming Comments Add Comment 5 min read Building PathCraft: An Open-Source Routing Engine in Go Daniel Reis Daniel Reis Daniel Reis Follow Jan 11 Building PathCraft: An Open-Source Routing Engine in Go # go # algorithms # programming # sideprojects Comments 1 comment 5 min read I got tired of memorizing swaggo comment order, so I made this WonJeong Kim WonJeong Kim WonJeong Kim Follow Jan 9 I got tired of memorizing swaggo comment order, so I made this # showdev # go # vscode # swagger Comments Add Comment 3 min read Reclaiming Idle GPUs in Kubernetes: Why We Built a Custom Scheduler Plugin Lalit Somavarapha Lalit Somavarapha Lalit Somavarapha Follow Jan 9 Reclaiming Idle GPUs in Kubernetes: Why We Built a Custom Scheduler Plugin # kubernetes # devops # gpu # go Comments Add Comment 5 min read Build Network Proxies and Reverse Proxies in Go: A Hands-On Guide Jones Charles Jones Charles Jones Charles Follow Jan 12 Build Network Proxies and Reverse Proxies in Go: A Hands-On Guide # go # networking # programming # webdev Comments Add Comment 6 min read [Learning Notes] [Golang] How to Develop OAuth2 PKCE with Golang - Using LINE Login as an Example Evan Lin Evan Lin Evan Lin Follow Jan 11 [Learning Notes] [Golang] How to Develop OAuth2 PKCE with Golang - Using LINE Login as an Example # security # webdev # go # tutorial Comments Add Comment 8 min read [Golang] Issues When Enabling Go Modules in Old Open Source Projects Evan Lin Evan Lin Evan Lin Follow Jan 11 [Golang] Issues When Enabling Go Modules in Old Open Source Projects # learning # tooling # go # opensource Comments Add Comment 5 min read [Learning Notes] [Golang] Migrating Disqus Comments to Github Issues by Writing disqus-importor-go Evan Lin Evan Lin Evan Lin Follow Jan 11 [Learning Notes] [Golang] Migrating Disqus Comments to Github Issues by Writing disqus-importor-go # tooling # github # go # opensource Comments Add Comment 4 min read [Golang] Fixing "undefined: sql.NullTime" Errors with go-pg on Heroku Evan Lin Evan Lin Evan Lin Follow Jan 11 [Golang] Fixing "undefined: sql.NullTime" Errors with go-pg on Heroku # learning # postgres # backend # go Comments Add Comment 2 min read [Golang] Deploy Docker Containers on GitHub with Heroku (One-Click) Evan Lin Evan Lin Evan Lin Follow Jan 11 [Golang] Deploy Docker Containers on GitHub with Heroku (One-Click) # docker # go # devops # tutorial Comments Add Comment 4 min read What Backend Developers Should Know About Passkeys (WWDC22) Evan Lin Evan Lin Evan Lin Follow Jan 11 What Backend Developers Should Know About Passkeys (WWDC22) # learning # security # backend # go Comments Add Comment 4 min read [Learning Notes][Golang] Using GitHub Issues as a Database Evan Lin Evan Lin Evan Lin Follow Jan 11 [Learning Notes][Golang] Using GitHub Issues as a Database # database # github # api # go Comments Add Comment 3 min read Go-GORM: CRUD basico + Postgres Docker (Parte 1). Carlos Andres Lopez Carlos Andres Lopez Carlos Andres Lopez Follow Jan 12 Go-GORM: CRUD basico + Postgres Docker (Parte 1). # go # goorm # programacion # docker Comments Add Comment 5 min read [Golang][Gemini Pro] Build a LINE Bot with Memory Using Chat Sessions Evan Lin Evan Lin Evan Lin Follow Jan 11 [Golang][Gemini Pro] Build a LINE Bot with Memory Using Chat Sessions # gemini # llm # go # tutorial Comments Add Comment 6 min read LINE OA Travel Assistant Chatbot (4): Gemini Pro Server Changes... Evan Lin Evan Lin Evan Lin Follow Jan 11 LINE OA Travel Assistant Chatbot (4): Gemini Pro Server Changes... # gemini # go # api # ai Comments Add Comment 4 min read [Golang] Quickly Set Up a Free Local ChatGPT with Ollama and Build a LangChainGo Application Evan Lin Evan Lin Evan Lin Follow Jan 11 [Golang] Quickly Set Up a Free Local ChatGPT with Ollama and Build a LangChainGo Application # llm # tutorial # go # chatgpt Comments Add Comment 4 min read [Learning Notes] [Golang] Efficiently Preparing FLEX Messages When Developing a LINE Chatbot with Golang Evan Lin Evan Lin Evan Lin Follow Jan 11 [Learning Notes] [Golang] Efficiently Preparing FLEX Messages When Developing a LINE Chatbot with Golang # api # go # tutorial Comments Add Comment 3 min read LINE OA Travel Assistant Chatbot: Golang, Cloud Functions, Gemini Pro, Firebase Evan Lin Evan Lin Evan Lin Follow Jan 11 LINE OA Travel Assistant Chatbot: Golang, Cloud Functions, Gemini Pro, Firebase # gemini # serverless # go # tutorial Comments Add Comment 3 min read [Golang] How to Update Golang LINE Bot SDK v8 OpenAPI (Swagger) Evan Lin Evan Lin Evan Lin Follow Jan 11 [Golang] How to Update Golang LINE Bot SDK v8 OpenAPI (Swagger) # api # go # tutorial Comments Add Comment 4 min read [Golang][GCP] Cleaning Up Artifact Registry Space Caused by Cloud Run Evan Lin Evan Lin Evan Lin Follow Jan 11 [Golang][GCP] Cleaning Up Artifact Registry Space Caused by Cloud Run # serverless # cloud # go # devops Comments Add Comment 1 min read [Golang][Gemini Pro] Building a Business Card Chatbot with Gemini-Pro-Vision Evan Lin Evan Lin Evan Lin Follow Jan 11 [Golang][Gemini Pro] Building a Business Card Chatbot with Gemini-Pro-Vision # gemini # go # tutorial # ai Comments Add Comment 7 min read [Gemini][Golang] Building a LINE File Backup Bot in Golang to Google Drive Evan Lin Evan Lin Evan Lin Follow Jan 11 [Gemini][Golang] Building a LINE File Backup Bot in Golang to Google Drive # gemini # automation # go # tutorial Comments Add Comment 7 min read [Python/Golang] Solving Imgur Image Download Redirection Issues Evan Lin Evan Lin Evan Lin Follow Jan 11 [Python/Golang] Solving Imgur Image Download Redirection Issues # networking # python # go # api Comments Add Comment 3 min read loading... trending guides/resources Deadlocks in Go: The Silent Production Killer Stop Burning Snowflake Credits - Build a Local Emulator with Go and DuckDB JSON vs MessagePack vs Protobuf in Go — My Real Benchmarks and What They Mean in Production Understanding Goroutines, Concurrency, and Parallelism in Go Building a Producer–Consumer Pipeline in Go Using Goroutines and Channels Repository Pattern in Golang: A Practical Guide LiteLLM Broke at 300 RPS in Production. Here's How We Fixed It Go 1.26 Meets 2026 with a Professional Graphics Ecosystem Wails as Electron Alternative GoGPU: A Pure Go Graphics Library for GPU Programming Bifrost: The Fastest Open Source LLM Gateway 1M+ Req/s Heavy-Read API in Go. Production Lessons Learned Mastering HTTP Clients in Go: Your Guide to the `net/http` Package Why I Migrated My Backend from Go to Elixir/Phoenix Building DNS Resolution and Domain Services with Go: A Practical Guide Go vs. Rust for TUI Development: A Deep Dive into Bubbletea and Ratatui Reactive Tree Management in Nuxt 4: How I Modeled Complex Hierarchies with Pinia Go: Stick to the Standard Library, Fill the Gaps with Chi, Zap, and Migrate Building RESTful APIs in Go: A Practical Guide for Dev.to Devs Raffi: a modern Stremio‑compatible streaming client I built at 16 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://core.forem.com/#main-content | Forem Core Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Forem Core Close Welcome to Forem Core — part of the Forem network! Community building community Create account Log in Home About Contact Other Code of Conduct Privacy Policy Terms of Use Twitter Facebook Github Instagram Twitch Mastodon Popular Tags #javascript #productivity #security #api #performance #docker #mobile #seo #postgres #rails #cicd #help #product #analytics #devto #documentation #redis #authentication #oauth #deployment #search #announcement #scalability #stripe #caching #roadmap #selfhost #webhooks #installation #uiux Forem Core Discussing the core forem open source software project — features, bugs, performance, self-hosting. Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem Core © 2016 - 2026. Posts Relevant Latest Top October 2025 Forem Core Update: Hacktoberfest Momentum, PR Cleanups, and Self-Hosting Tweaks Om Shree Om Shree Om Shree Follow Oct 12 '25 October 2025 Forem Core Update: Hacktoberfest Momentum, PR Cleanups, and Self-Hosting Tweaks # productivity # security # performance # javascript 20 reactions Comments 1 comment 4 min read How to Use Cron Jobs in Linux: Step-by-Step Guide Admin Admin Admin Follow Jan 7 How to Use Cron Jobs in Linux: Step-by-Step Guide # backgroundjobs # productivity # selfhost Comments Add Comment 7 min read Extending the Nano Banana image generation to also be responsible for fun unique profile images for users who register through a path without providing their own profile pic. Ben Halpern Ben Halpern Ben Halpern Follow Nov 14 '25 Extending the Nano Banana image generation to also be responsible for fun unique profile images for users who register through a path without providing their own profile pic. 7 reactions Comments Add Comment 1 min read Available across the whole Forem network and self-hosted instances if configured Ben Halpern Ben Halpern Ben Halpern Follow Nov 13 '25 Available across the whole Forem network and self-hosted instances if configured Cover Image Generation Now an Option in the DEV Editor Ben Halpern for The DEV Team ・ Nov 13 #community #forem #ai #design 7 reactions Comments Add Comment 1 min read Forem Project Weekly: Scheduled Automations, Image Generation & UX Upgrades Forem Project News Forem Project News Forem Project News Follow Nov 10 '25 Forem Project Weekly: Scheduled Automations, Image Generation & UX Upgrades # opensource # performance # productivity # uiux 9 reactions Comments 1 comment 2 min read Stream of small fixes — this week's repo recap is going to be full! Ben Halpern Ben Halpern Ben Halpern Follow Nov 6 '25 Stream of small fixes — this week's repo recap is going to be full! 4 reactions Comments Add Comment 1 min read Next version of mobile app is going to be a nice upgrade Ben Halpern Ben Halpern Ben Halpern Follow Nov 3 '25 Next version of mobile app is going to be a nice upgrade 3 reactions Comments Add Comment 1 min read Forem Weekly Repo Recap: New Community Hub, Email Fixes & Markdown Improvements Forem Project News Forem Project News Forem Project News Follow Oct 31 '25 Forem Weekly Repo Recap: New Community Hub, Email Fixes & Markdown Improvements # news # product # deployment # opensource 14 reactions Comments 1 comment 1 min read Lots of momentum this week! Ben Halpern Ben Halpern Ben Halpern Follow Oct 31 '25 Lots of momentum this week! Forem Weekly Repo Recap: New Community Hub, Email Fixes & Markdown Improvements Forem Project News ・ Oct 31 #product #deployment #opensource #news 5 reactions Comments 1 comment 1 min read Added a /community endpoint as sort of an info hub for every subforem. It's kind of just a proof of concept at the moment but can be refined. Ideally it's customizable so we can link off to places like /challenges etc. but keeping it dynamic vs static. Ben Halpern Ben Halpern Ben Halpern Follow Oct 30 '25 Added a /community endpoint as sort of an info hub for every subforem. It's kind of just a proof of concept at the moment but can be refined. Ideally it's customizable so we can link off to places like /challenges etc. but keeping it dynamic vs static. 7 reactions Comments Add Comment 1 min read Hopefully releasing a new Forem app with lots of little fixes in the next couple days Ben Halpern Ben Halpern Ben Halpern Follow Oct 29 '25 Hopefully releasing a new Forem app with lots of little fixes in the next couple days 3 reactions Comments Add Comment 1 min read We need to adjust quickie posts to properly not count full URLs for characters. I know Twitter traditionally capped these at 17 chars regardless of length — we'll want to do something similar along those lines. Ben Halpern Ben Halpern Ben Halpern Follow Oct 23 '25 We need to adjust quickie posts to properly not count full URLs for characters. I know Twitter traditionally capped these at 17 chars regardless of length — we'll want to do something similar along those lines. 3 reactions Comments Add Comment 1 min read Hoping to make improvements to quickie posts like this so they show up when appropriate in feeds (currently they sink pretty quickly) without overwhelming or taking away from the experience. Ben Halpern Ben Halpern Ben Halpern Follow Oct 23 '25 Hoping to make improvements to quickie posts like this so they show up when appropriate in feeds (currently they sink pretty quickly) without overwhelming or taking away from the experience. 3 reactions Comments Add Comment 1 min read So much of what we do is building in public, but we need to use this space more to talk about it. Ben Halpern Ben Halpern Ben Halpern Follow Oct 23 '25 So much of what we do is building in public, but we need to use this space more to talk about it. 3 reactions Comments Add Comment 1 min read This was one of several recent performance improvements. Under the hood, we did some interesting memory-first caching as well. Ben Halpern Ben Halpern Ben Halpern Follow Oct 3 '25 This was one of several recent performance improvements. Under the hood, we did some interesting memory-first caching as well. Preloading the DEV (and Forem) home feed and sidebar for substantial performance benefits Ben Halpern for The DEV Team ・ Oct 3 #webdev #frontend #performance #webperf 8 reactions Comments 2 comments 1 min read I think we're definitely going to want to support inline markdown syntax like backticks for code snippets etc. But we *don't* want to *fully* support markdown as we have full posts for rich content. But doing all this in a non-confusing way is key. Ben Halpern Ben Halpern Ben Halpern Follow Oct 3 '25 I think we're definitely going to want to support inline markdown syntax like backticks for code snippets etc. But we *don't* want to *fully* support markdown as we have full posts for rich content. But doing all this in a non-confusing way is key. 4 reactions Comments Add Comment 1 min read New spam detection targeting mass registration live and working well so far. github.com/forem/forem... Ben Halpern Ben Halpern Ben Halpern Follow Sep 24 '25 New spam detection targeting mass registration live and working well so far. github.com/forem/forem... feat: Add domain-based spam blocking with background worker by benhalpern · Pull Request #22350 · forem/forem · GitHub Summary This PR implements automatic domain-based spam blocking to prevent mass registration attacks from single email domains. Changes Spam::DomainDetector: Detects spam patterns by email domain... github.com 3 reactions Comments Add Comment 1 min read The Official Forem App review Junaid Junaid Junaid Follow Aug 11 '25 The Official Forem App review Comments 1 comment 1 min read loading... #discuss Discussion threads targeting the whole community #watercooler Light, and off-topic conversation. 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem Core — Discussing the core forem open source software project — features, bugs, performance, self-hosting. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem Core © 2016 - 2026. Community building community Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/t/discuss#main-content | Discussion Threads - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Discussion Threads Follow Hide Discussion threads targeting the whole community Create Post submission guidelines These posts should include a question, prompt, or topic that initiates a discussion in the comments section. Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/new/webdev | New Post - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Join the HMPL.js Forem HMPL.js Forem is a community of 3,676,891 amazing developers Continue with Apple Continue with Google Continue with Facebook Continue with Forem Continue with GitHub Continue with Twitter (X) OR Email Password Remember me Forgot password? By signing in, you are agreeing to our privacy policy , terms of use and code of conduct . New to HMPL.js Forem? Create account . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/t/career#main-content | Career - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Career Follow Hide This tag is for anything relating to careers! Job offers, workplace conflict, interviews, resumes, promotions, etc. Create Post submission guidelines All articles and discussions should relate to careers in some way. Pretty much everything on dev.to is about our careers in some way. Ideally, though, keep the tag related to getting, leaving, or maintaining a career or job. about #career A career is the field in which you work, while a job is a position held in that field. Related tags include #resume and #portfolio as resources to enhance your #career Older #career posts 1 2 3 4 5 6 7 8 9 … 75 … 833 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/about#how-to-get-involved | About HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close About HMPL.js Forem Welcome to the HMPL.js Forem! Hello and welcome, developers! This is the official community hub for HMPL.js, the server-oriented, customizable templating language for JavaScript. If you're excited about building dynamic, modern, and incredibly small web applications by keeping logic on the server and fetching HTML, you've found your home. What This Community Is About Our mission is to create a central place for developers to learn, discuss, and master HMPL.js. We believe in building powerful user interfaces with minimal client-side JavaScript, leveraging the server to do the heavy lifting. HMPL.js is designed to be: Flexible: Get the benefits of SSR on any platform, whether it's a simple static site or a complex single-page application. Easy to Use: Describe a couple of properties in an object and get ready-to-use HTML directly from your server. Reliable: With 100% code coverage and built-in protection against XSS vulnerabilities (using DOMPurify), you can build with confidence. Lightweight: All this functionality is packed into just ~24 kilobytes, making your apps significantly smaller than those built with other popular tools. This forum is the place to explore these concepts, share your successes, and get help when you need it. What to Discuss Here We encourage a wide range of discussions. Whether you're a beginner or an expert, your voice is welcome. Here are a few ideas to get you started: Questions & Support: Need help with installation, hmpl.compile() , or the hmpl-dom module? Ask away! Use the #help tag. Show & Tell: Share the awesome things you've built with HMPL.js. Post a link to your project or a code snippet. Use the #showdev tag. Tutorials & Guides: Found a great way to solve a common problem? Write a post to share your knowledge with the community. Use the #tutorial tag. In-Depth Discussions: Let's talk about best practices, performance, or how HMPL.js compares to libraries like HTMX and Alpine.js. Use the #discuss tag. Ideas & Feedback: Have a suggestion for a new feature or an improvement? We'd love to hear it! How to Get Involved Jumping in is easy! Introduce yourself in the comments of a welcome thread. Ask a question or help answer someone else's. Share your project or a cool code snippet you've written. Experiment with the online HMPL Playground and share your creations. Our Community Guidelines To ensure this remains a friendly and productive space for everyone, we ask that you follow a few simple principles: Be Kind and Respectful: Treat everyone with courtesy. Healthy debate is encouraged, but personal attacks are not. Be Collaborative: This is a space for learning together. Share what you know, and be open to learning from others. Stay Constructive: Offer feedback that is helpful, supportive, and aimed at moving the conversation forward. Stay On Topic: Keep discussions focused on HMPL.js and related web development technologies. We're thrilled to have you here. Let's build something amazing together 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/t/showdev#main-content | Show DEV - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Show DEV Follow Hide Show off what you've built! Create Post submission guidelines For showing off projects and launching products. Please make posts community-driven and not overly corporate or salesy. Typically it is for showing off your thing or your company's thing. You can however, show off someone else's thing, but just make it clear it's theirs and not yours. Don't just use this tag to share posts or tutorials your proud of — this is really for projects. Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu We're launching on ProductHunt Anthony Max Anthony Max Anthony Max Follow Dec 28 '25 We're launching on ProductHunt # news # javascript # showdev Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/about#welcome-to-the-hmpljs-forem | About HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close About HMPL.js Forem Welcome to the HMPL.js Forem! Hello and welcome, developers! This is the official community hub for HMPL.js, the server-oriented, customizable templating language for JavaScript. If you're excited about building dynamic, modern, and incredibly small web applications by keeping logic on the server and fetching HTML, you've found your home. What This Community Is About Our mission is to create a central place for developers to learn, discuss, and master HMPL.js. We believe in building powerful user interfaces with minimal client-side JavaScript, leveraging the server to do the heavy lifting. HMPL.js is designed to be: Flexible: Get the benefits of SSR on any platform, whether it's a simple static site or a complex single-page application. Easy to Use: Describe a couple of properties in an object and get ready-to-use HTML directly from your server. Reliable: With 100% code coverage and built-in protection against XSS vulnerabilities (using DOMPurify), you can build with confidence. Lightweight: All this functionality is packed into just ~24 kilobytes, making your apps significantly smaller than those built with other popular tools. This forum is the place to explore these concepts, share your successes, and get help when you need it. What to Discuss Here We encourage a wide range of discussions. Whether you're a beginner or an expert, your voice is welcome. Here are a few ideas to get you started: Questions & Support: Need help with installation, hmpl.compile() , or the hmpl-dom module? Ask away! Use the #help tag. Show & Tell: Share the awesome things you've built with HMPL.js. Post a link to your project or a code snippet. Use the #showdev tag. Tutorials & Guides: Found a great way to solve a common problem? Write a post to share your knowledge with the community. Use the #tutorial tag. In-Depth Discussions: Let's talk about best practices, performance, or how HMPL.js compares to libraries like HTMX and Alpine.js. Use the #discuss tag. Ideas & Feedback: Have a suggestion for a new feature or an improvement? We'd love to hear it! How to Get Involved Jumping in is easy! Introduce yourself in the comments of a welcome thread. Ask a question or help answer someone else's. Share your project or a cool code snippet you've written. Experiment with the online HMPL Playground and share your creations. Our Community Guidelines To ensure this remains a friendly and productive space for everyone, we ask that you follow a few simple principles: Be Kind and Respectful: Treat everyone with courtesy. Healthy debate is encouraged, but personal attacks are not. Be Collaborative: This is a space for learning together. Share what you know, and be open to learning from others. Stay Constructive: Offer feedback that is helpful, supportive, and aimed at moving the conversation forward. Stay On Topic: Keep discussions focused on HMPL.js and related web development technologies. We're thrilled to have you here. Let's build something amazing together 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://docs.suprsend.com/docs/integrate-go-sdk | Integrate Go SDK - SuprSend, Notification infrastructure for Product teams Skip to main content SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Community Trust Center Platform Status Postman Collection Developer Resources Overview Updates and Versioning Versioning and Support Policy SDK Changelog Authentication API Keys and Secrets Service Token Best Practices for Key & Token Management MCP Overview BETA Quickstart Tool List Building with LLMs Security Security SDKs and APIs SDKs SDK Overview SuprSend Backend SDK Python SDK Node.js SDK Java SDK Go SDK Integrate Go SDK Manage Users Send and Track Events Trigger Workflow from API Tenants Lists Broadcast SuprSend Client SDK Management API REST API Postman Collection Features Validate Trigger Payload Type Safety Testing Testing the Template Test Mode Monitoring and Logging Logs Data Out Contact Us Get Started SuprSend, Notification infrastructure for Product teams home page Search... ⌘ K Ask AI Contact Us Get Started Get Started Search... Navigation Go SDK Integrate Go SDK Documentation API Reference Management API CLI Reference Developer Resources Changelog Documentation API Reference Management API CLI Reference Developer Resources Changelog Go SDK Integrate Go SDK OpenAI Open in ChatGPT Install & Initialize SuprSend Go SDK using your workspace credentials for sending notifications. OpenAI Open in ChatGPT Installation Install suprsend-go sdk bash Copy Ask AI go get github.com/suprsend/suprsend-go Initialization For initializing SDK, you need workspace_key and workspace_secret. You will get both the tokens from your Suprsend dashboard (Developers -> API Keys). Request Copy Ask AI package main import ( " log " suprsend " github.com/suprsend/suprsend-go " ) // Initialize SDK func main () { opts := [] suprsend . ClientOption { // suprsend.WithDebug(true), } suprClient , err := suprsend . NewClient ( "__workspace_key__" , "__workspace_secret__" , opts ... ) if err != nil { log . Println ( err ) } } Was this page helpful? Yes No Suggest edits Raise issue Previous Manage Users Manage user profiles and communication channels programmatically with the Go SDK. Next ⌘ I x github linkedin youtube Powered by On this page Installation Initialization | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/new/react | New Post - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Join the HMPL.js Forem HMPL.js Forem is a community of 3,676,891 amazing developers Continue with Apple Continue with Google Continue with Facebook Continue with Forem Continue with GitHub Continue with Twitter (X) OR Email Password Remember me Forgot password? By signing in, you are agreeing to our privacy policy , terms of use and code of conduct . New to HMPL.js Forem? Create account . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/t/web3/page/4 | Web3 Page 4 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Web3 Follow Hide Web3 refers to the next generation of the internet that leverages blockchain technology to enable decentralized and trustless systems for financial transactions, data storage, and other applications. Create Post Older #web3 posts 1 2 3 4 5 6 7 8 9 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Frontend Development: Where Trends Meet Real-World Freelancing erdem-sicak erdem-sicak erdem-sicak Follow Dec 23 '25 Frontend Development: Where Trends Meet Real-World Freelancing # web3 # css # frontend # design Comments Add Comment 3 min read Blockchain Beyond Crypto: Real-World Applications That Matter Ahmed Radwan Ahmed Radwan Ahmed Radwan Follow for Nerd Level Tech Dec 23 '25 Blockchain Beyond Crypto: Real-World Applications That Matter # blockchain # web3 # smartcontract 1 reaction Comments Add Comment 7 min read Ethereum-Solidity Quiz Q3: What is the ABI? MihaiHng MihaiHng MihaiHng Follow Dec 24 '25 Ethereum-Solidity Quiz Q3: What is the ABI? # web3 # beginners # ethereum # api Comments Add Comment 1 min read Sending EIP-4844 Blob Transactions with ethers.js and kzg-wasm Kurt Kurt Kurt Follow Dec 22 '25 Sending EIP-4844 Blob Transactions with ethers.js and kzg-wasm # eip4844 # protodarksharding # ethereum # web3 Comments Add Comment 2 min read How to Easily Call Smart Contracts Using Ethers.js and Next.js (BSC Testnet) Daniel Brooks Daniel Brooks Daniel Brooks Follow Dec 22 '25 How to Easily Call Smart Contracts Using Ethers.js and Next.js (BSC Testnet) # web3 # etherjs # nextjs # webdev Comments Add Comment 3 min read Next.js Web3 Boilerplate: Build a Production-Ready dApp Faster Daniel Brooks Daniel Brooks Daniel Brooks Follow Dec 22 '25 Next.js Web3 Boilerplate: Build a Production-Ready dApp Faster # nextjs # etherjs # web3 # boilerplate Comments Add Comment 3 min read How to Run and Test Your Midnight DApps Giovanni Giovanni Giovanni Follow Dec 23 '25 How to Run and Test Your Midnight DApps # testing # tutorial # web3 Comments Add Comment 2 min read From Zero to RWA: My 14-Day Journey Building on Mantle Azhar Aditya Pratama Azhar Aditya Pratama Azhar Aditya Pratama Follow Dec 21 '25 From Zero to RWA: My 14-Day Journey Building on Mantle # challenge # web3 # devjournal # learning Comments Add Comment 3 min read The MEV Dark Pool Problem: Why Private Mempools Need Decentralized Verification sid sid sid Follow Dec 25 '25 The MEV Dark Pool Problem: Why Private Mempools Need Decentralized Verification # web3 # blockchain # security # architecture Comments 2 comments 4 min read HTTP payments without logins, subscriptions, or checkout pages (x402 idea) Aditya Singh Aditya Singh Aditya Singh Follow Dec 25 '25 HTTP payments without logins, subscriptions, or checkout pages (x402 idea) # discuss # web3 # architecture # webdev Comments 2 comments 1 min read Adding a Missing Example for Privacy Controls Kalu Jennifer Kalu Jennifer Kalu Jennifer Follow Dec 21 '25 Adding a Missing Example for Privacy Controls # privacy # web3 # documentation # opensource Comments Add Comment 1 min read Beyond the PDF: Law as an Architectural Layer in the Modern Tech Stack Sercan Koç Sercan Koç Sercan Koç Follow Dec 20 '25 Beyond the PDF: Law as an Architectural Layer in the Modern Tech Stack # architecture # web3 # programming # law Comments Add Comment 3 min read Simplifying Technical Jargon in the Docs Marycynthia Ihemebiwo Marycynthia Ihemebiwo Marycynthia Ihemebiwo Follow Dec 20 '25 Simplifying Technical Jargon in the Docs # web3 # writing # documentation # beginners Comments Add Comment 1 min read # `@xchainjs/xchain-litecoin` Fabricio Viskor Fabricio Viskor Fabricio Viskor Follow Dec 19 '25 # `@xchainjs/xchain-litecoin` # web3 # blockchain # webdev # programming Comments Add Comment 3 min read # `@xchainjs/xchain-ethereum` Fabricio Viskor Fabricio Viskor Fabricio Viskor Follow Dec 19 '25 # `@xchainjs/xchain-ethereum` # ethereum # blockchain # web3 # etherjs Comments Add Comment 2 min read # XChainJS Check Transaction Example Fabricio Viskor Fabricio Viskor Fabricio Viskor Follow Dec 19 '25 # XChainJS Check Transaction Example # web3 # blockchain # webdev # solidity Comments Add Comment 2 min read AI Dominates Tech Landscape with Major Advancements and Strategic Shifts Across Leading Companies Stelixx Insights Stelixx Insights Stelixx Insights Follow Dec 20 '25 AI Dominates Tech Landscape with Major Advancements and Strategic Shifts Across Leading Companies # ai # web3 # blockchain # productivity Comments Add Comment 1 min read # XChainJS Liquidity Example (THORChain) Fabricio Viskor Fabricio Viskor Fabricio Viskor Follow Dec 19 '25 # XChainJS Liquidity Example (THORChain) # webdev # web3 # blockchain # solidity Comments Add Comment 2 min read Reflection of Co-Learning Mantle week 2 Bagas Hariyanto Bagas Hariyanto Bagas Hariyanto Follow Dec 21 '25 Reflection of Co-Learning Mantle week 2 # web3 # devjournal # blockchain # beginners Comments Add Comment 2 min read Building a Decentralized Event Ticketing System Web3 with Symfony 7.4 Matt Mochalkin Matt Mochalkin Matt Mochalkin Follow Dec 19 '25 Building a Decentralized Event Ticketing System Web3 with Symfony 7.4 # web3 # symfony # php # blockchain Comments Add Comment 5 min read Clarifying Zero Knowledge Proof Concepts Marycynthia Ihemebiwo Marycynthia Ihemebiwo Marycynthia Ihemebiwo Follow Dec 19 '25 Clarifying Zero Knowledge Proof Concepts # documentation # learning # web3 Comments Add Comment 1 min read The "Prompt-to-Playable" Shift: Why Gemini 3 Marks the End of Passive Media Juddiy Juddiy Juddiy Follow Dec 24 '25 The "Prompt-to-Playable" Shift: Why Gemini 3 Marks the End of Passive Media # webdev # ai # gamedev # web3 4 reactions Comments Add Comment 4 min read Understanding the Constant Product Formula in AMMs (Without Getting Tricked by k) Maria Kalala Maria Kalala Maria Kalala Follow Dec 23 '25 Understanding the Constant Product Formula in AMMs (Without Getting Tricked by k) # blockchain # web3 # smartcontract # defi Comments Add Comment 3 min read A Guide to Web3 Infrastructure & Concepts Malawige Inusha Thathsara Gunasekara Malawige Inusha Thathsara Gunasekara Malawige Inusha Thathsara Gunasekara Follow Jan 1 A Guide to Web3 Infrastructure & Concepts # web3 # architecture # blockchain # cloud Comments Add Comment 3 min read Architecting Web3: Integrating Blockchain Events with Google Cloud (GKE) Malawige Inusha Thathsara Gunasekara Malawige Inusha Thathsara Gunasekara Malawige Inusha Thathsara Gunasekara Follow Jan 1 Architecting Web3: Integrating Blockchain Events with Google Cloud (GKE) # architecture # blockchain # web3 # bitcoin Comments Add Comment 2 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/privacy#b-administrative-purposes | Privacy Policy - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/about#what-this-community-is-about | About HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close About HMPL.js Forem Welcome to the HMPL.js Forem! Hello and welcome, developers! This is the official community hub for HMPL.js, the server-oriented, customizable templating language for JavaScript. If you're excited about building dynamic, modern, and incredibly small web applications by keeping logic on the server and fetching HTML, you've found your home. What This Community Is About Our mission is to create a central place for developers to learn, discuss, and master HMPL.js. We believe in building powerful user interfaces with minimal client-side JavaScript, leveraging the server to do the heavy lifting. HMPL.js is designed to be: Flexible: Get the benefits of SSR on any platform, whether it's a simple static site or a complex single-page application. Easy to Use: Describe a couple of properties in an object and get ready-to-use HTML directly from your server. Reliable: With 100% code coverage and built-in protection against XSS vulnerabilities (using DOMPurify), you can build with confidence. Lightweight: All this functionality is packed into just ~24 kilobytes, making your apps significantly smaller than those built with other popular tools. This forum is the place to explore these concepts, share your successes, and get help when you need it. What to Discuss Here We encourage a wide range of discussions. Whether you're a beginner or an expert, your voice is welcome. Here are a few ideas to get you started: Questions & Support: Need help with installation, hmpl.compile() , or the hmpl-dom module? Ask away! Use the #help tag. Show & Tell: Share the awesome things you've built with HMPL.js. Post a link to your project or a code snippet. Use the #showdev tag. Tutorials & Guides: Found a great way to solve a common problem? Write a post to share your knowledge with the community. Use the #tutorial tag. In-Depth Discussions: Let's talk about best practices, performance, or how HMPL.js compares to libraries like HTMX and Alpine.js. Use the #discuss tag. Ideas & Feedback: Have a suggestion for a new feature or an improvement? We'd love to hear it! How to Get Involved Jumping in is easy! Introduce yourself in the comments of a welcome thread. Ask a question or help answer someone else's. Share your project or a cool code snippet you've written. Experiment with the online HMPL Playground and share your creations. Our Community Guidelines To ensure this remains a friendly and productive space for everyone, we ask that you follow a few simple principles: Be Kind and Respectful: Treat everyone with courtesy. Healthy debate is encouraged, but personal attacks are not. Be Collaborative: This is a space for learning together. Share what you know, and be open to learning from others. Stay Constructive: Offer feedback that is helpful, supportive, and aimed at moving the conversation forward. Stay On Topic: Keep discussions focused on HMPL.js and related web development technologies. We're thrilled to have you here. Let's build something amazing together 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/privacy#c-information-collected-from-other-sources | Privacy Policy - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/msnmongare/admin-only-dashboard-rule-of-thumb-3hhl | Admin-Only Dashboard Rule of Thumb - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Sospeter Mong'are Posted on Jan 12 Admin-Only Dashboard Rule of Thumb # programming # beginners # database # datascience Most admin dashboards fail for one simple reason: They try to be informative instead of operational . An admin dashboard is not a report. It is not a marketing page. It is not a vanity wall of numbers. An admin dashboard is a control room . After building and reviewing multiple systems-APIs, SaaS platforms, internal tools-one rule consistently separates useful admin dashboards from useless ones. The Rule of Thumb If a metric doesn’t help you: Detect issues Control abuse Plan scaling Protect revenue 👉 It doesn’t belong on the admin dashboard. This rule works across industries, tech stacks, and company sizes because it aligns with the actual job of an admin. Why Admin Dashboards Exist Admins are responsible for: System stability User safety Operational efficiency Business continuity They are not there to admire growth charts. They are there to prevent damage and respond fast . Every metric on an admin dashboard should answer at least one question: “What action might I need to take because of this?” If the answer is “none,” the metric is noise. 1. Detect Issues Admins must see problems before users do . Metrics in this category answer: Is something broken? Is performance degrading? Are errors increasing? Examples: Error rate Failed requests System downtime Unhealthy services Spike anomalies If an issue exists and your dashboard doesn’t surface it, the dashboard has failed. 2. Control Abuse Any system with users will eventually be abused-intentionally or unintentionally. Admins need visibility into: Misuse Overconsumption Security risks Policy violations Examples: Suspicious activity Rate-limit violations Error-heavy users or API keys Unusual usage patterns Abuse metrics protect both infrastructure and fairness . 3. Plan Scaling Success can break systems just as fast as bugs. Admins must know: When capacity limits are approaching Where usage is concentrated What growth looks like under load Examples: Peak usage times Requests per second Active users over time Resource saturation signals Scaling should be predictive , not reactive. 4. Protect Revenue If usage is not tracked properly, money leaks quietly. Admins must ensure: Usage matches billing Paid resources aren’t abused High-value customers are visible Examples: Billable actions High-usage customers Unpaid consumption Revenue-impacting failures If revenue is affected and the dashboard doesn’t show it, the business is flying blind. What Doesn’t Belong on an Admin Dashboard These metrics are common-but dangerous in admin views: Vanity numbers with no action Marketing KPIs User-facing analytics Pretty charts without thresholds “Interesting” but non-operational data Admins don’t need interesting . They need actionable . A Note on Logs and Audit Data Some data exists to explain why something happened: Audit logs Change history Access trails These are important-but they should live below the dashboard , not as headline cards. Dashboards surface problems. Logs explain them. Why This Rule Works Everywhere This rule applies to: APIs SaaS platforms Fintech systems E-commerce backends Internal tools Infrastructure dashboards The metrics change. The principle does not. How This Rule Adapts Across Domains While the metrics themselves differ from system to system, the rule of thumb remains consistent. What changes is what you measure , not why you measure it . E-commerce Platforms Detect issues → Failed checkouts, payment errors Control abuse → Fraud attempts, refund abuse Plan scaling → Traffic spikes, inventory turnover Protect revenue → Abandoned carts, payment success rates Fintech & Payments Systems Detect issues → Transaction failures, settlement delays Control abuse → Suspicious accounts, unusual transfer patterns Plan scaling → Transactions per second, peak load times Protect revenue → Reconciliation mismatches, failed settlements APIs & Developer Platforms Detect issues → Error rates, unhealthy endpoints Control abuse → Rate-limit violations, key misuse Plan scaling → Request volume, peak usage hours Protect revenue → Billable calls, unpaid consumption SaaS Products Detect issues → Service outages, degraded performance Control abuse → License misuse, account sharing Plan scaling → Active users, feature usage growth Protect revenue → Subscription churn risks, overuse beyond plan limits Across all these domains, the admin dashboard remains a decision-making surface , not an analytics playground. The moment a metric stops supporting detection, control, scaling, or revenue protection, it no longer belongs in the admin view. Final Thought A great admin dashboard is calm, focused, and boring in the best way. If every card exists to: Detect issues Control abuse Plan scaling Protect revenue Then your dashboard is doing its job. Anything else belongs somewhere else. Top comments (2) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Vincent Tommi Vincent Tommi Vincent Tommi Follow Backend-Developer Email vincenttommi@gmail.com Location Nairobi-Kenya Education Moringa-School Pronouns Thinking Beyond Code Work Backend-Nerd Joined Apr 2, 2023 • Jan 12 Dropdown menu Copy link Hide great insights senior Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Sospeter Mong'are Sospeter Mong'are Sospeter Mong'are Follow Software Engineer passionate about developing for the web Location Kenya Education BSC. Software Engineering Pronouns Mr Work Software Engineer (Backend) | API Development & Integration | Technical writer | Mentor Joined Nov 22, 2018 • Jan 12 Dropdown menu Copy link Hide Thank you sir Like comment: Like comment: 1 like Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Sospeter Mong'are Follow Software Engineer passionate about developing for the web Location Kenya Education BSC. Software Engineering Pronouns Mr Work Software Engineer (Backend) | API Development & Integration | Technical writer | Mentor Joined Nov 22, 2018 More from Sospeter Mong'are Building a Simple Node.js + Express Backend Using PostgreSQL and an ORM (Beginner Guide) # webdev # programming # ai # productivity 2025 Was the Year of Fast AI, 2026 Will Be the Year of AI Quality # webdev # programming # python # beginners From Zero to Interview-Ready: A Beginner’s DSA Roadmap (2026 Edition) # programming # webdev # beginners # productivity 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Forem — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Forem © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/alexsergey/css-modules-vs-css-in-js-who-wins-3n25#cssinjs | CSS Modules vs CSS-in-JS. Who wins? - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Sergey Posted on Mar 11, 2021 CSS Modules vs CSS-in-JS. Who wins? # webdev # css # javascript # react Introduction In modern React application development, there are many approaches to organizing application styles. One of the popular ways of such an organization is the CSS-in-JS approach (in the article we will use styled-components as the most popular solution) and CSS Modules. In this article, we will try to answer the question: which is better CSS-in-JS or CSS Modules ? So let's get back to basics. When a web page was primarily set for storing textual documentation and didn't include user interactions, properties were introduced to style the content. Over time, the web became more and more popular, sites got bigger, and it became necessary to reuse styles. For these purposes, CSS was invented. Cascading Style Sheets. Cascading plays a very important role in this name. We write styles that lay like a waterfall over the hollows of our document, filling it with colors and highlighting important elements. Time passed, the web became more and more complex, and we are facing the fact that the styles cascade turned into a problem for us. Distributed teams, working on their parts of the system, combining them into reusable modules, assemble an application from pieces, like Dr. Frankenstein, stitching styles into one large canvas, can get the sudden result... Due to the cascade, the styles of module 1 can affect the display of module 3, and module 4 can make changes to the global styles and change the entire display of the application in general. Developers have started to think of solving this problem. Style naming conventions were created to avoid overlaps, such as Yandex's BEM or Atomic CSS. The idea is clear, we operate with names in order to get predictability, but at the same time to prevent repetitions. These approaches were crashed of the rocks of the human factor. Anyway, we have no guarantee that the developer from team A won't use the name from team C. The naming problem can only be solved by assigning a random name to the CSS class. Thus, we get a completely independent CSS set of styles that will be applied to a specific HTML block and we understand for sure that the rest of the system won't be affected in any way. And then 2 approaches came onto the stage to organize our CSS: CSS Modules and CSS-in-JS . Under the hood, having a different technical implementation, and in fact solving the problem of atomicity, reusability, and avoiding side effects when writing CSS. Technically, CSS Modules transforms style names using a hash-based on the filename, path, style name. Styled-components handles styles in JS runtime, adding them as they go to the head HTML section (<head>). Approaches overview Let's see which approach is more optimal for writing a modern web application! Let's imagine we have a basic React application: import React , { Component } from ' react ' ; import ' ./App.css ' ; class App extends Component { render () { return ( < div className = "title" > React application title </ div > ); } } Enter fullscreen mode Exit fullscreen mode CSS styles of this application: .title { padding : 20px ; background-color : #222 ; text-align : center ; color : white ; font-size : 1.5em ; } Enter fullscreen mode Exit fullscreen mode The dependencies are React 16.14 , react-dom 16.14 Let's try to build this application using webpack using all production optimizations. we've got uglified JS - 129kb separated and minified CSS - 133 bytes The same code in CSS Modules will look like this: import React , { Component } from ' react ' ; import styles from ' ./App.module.css ' ; class App extends Component { render () { return ( < div className = { styles . title } > React application title </ div > ); } } Enter fullscreen mode Exit fullscreen mode uglified JS - 129kb separated and minified CSS - 151 bytes The CSS Modules version will take up a couple of bytes more due to the impossibility of compressing the long generated CSS names. Finally, let's rewrite the same code under styled-components: import React , { Component } from ' react ' ; import styles from ' styled-components ' ; const Title = styles . h1 ` padding: 20px; background-color: #222; text-align: center; color: white; font-size: 1.5em; ` ; class App extends Component { render () { return ( < Title > React application title </ Title > ); } } Enter fullscreen mode Exit fullscreen mode uglified JS - 163kb CSS file is missing The more than 30kb difference between CSS Modules and CSS-in-JS (styled-components) is due to styled-components adding extra code to add styles to the <head> part of the HTML document. In this synthetic test, the CSS Modules approach wins, since the build system doesn't add something extra to implement it, except for the changed class name. Styled-components due to technical implementation, adds dependency as well as code for runtime handling and styling of <head>. Now let's take a quick look at the pros and cons of CSS-in-JS / CSS Modules. Pros and cons CSS-in-JS cons The browser won't start interpreting the styles until styled-components has parsed them and added them to the DOM, which slows down rendering. The absence of CSS files means that you cannot cache separate CSS. One of the key downsides is that most libraries don't support this approach and we still can't get rid of CSS. All native JS and jQuery plugins are written without using this approach. Not all React solutions use it. Styles integration problems. When a markup developer prepares a layout for a JS developer, we may forget to transfer something; there will also be difficulty in synchronizing a new version of layout and JS code. We can't use CSS utilities: SCSS, Less, Postcss, stylelint, etc. pros Styles can use JS logic. This reminds me of Expression in IE6, when we could wrap some logic in our styles (Hello, CSS Expressions :) ). const Title = styles . h1 ` padding: 20px; background-color: #222; text-align: center; color: white; font-size: 1.5em; ${ props => props . secondary && css ` background-color: #fff; color: #000; padding: 10px; font-size: 1em; ` } ` ; Enter fullscreen mode Exit fullscreen mode When developing small modules, it simplifies the connection to the project, since you only need to connect the one independent JS file. It is semantically nicer to use <Title> in a React component than <h1 className={style.title}>. CSS Modules cons To describe global styles, you must use a syntax that does not belong to the CSS specification. :global ( .myclass ) { text-decoration : underline ; } Enter fullscreen mode Exit fullscreen mode Integrating into a project, you need to include styles. Working with typescript, you need to automatically or manually generate interfaces. For these purposes, I use webpack loader: @teamsupercell/typings-for-css-modules-loader pros We work with regular CSS, it makes it possible to use SCSS, Less, Postcss, stylelint, and more. Also, you don't waste time on adapting the CSS to JS. No integration of styles into the code, clean code as result. Almost 100% standardized except for global styles. Conclusion So the fundamental problem with the CSS-in-JS approach is that it's not CSS! This kind of code is harder to maintain if you have a defined person in your team working on markup. Such code will be slower, due to the fact that the CSS rendered into the file is processed in parallel, and the CSS-in-JS cannot be rendered into a separate CSS file. And the last fundamental flaw is the inability to use ready-made approaches and utilities, such as SCSS, Less and Stylelint, and so on. On the other hand, the CSS-in-JS approach can be a good solution for the Frontend team who deals with both markup and JS, and develops all components from scratch. Also, CSS-in-JS will be useful for modules that integrate into other applications. In my personal opinion, the issue of CSS cascading is overrated. If we are developing a small application or site, with one team, then we are unlikely to encounter a name collision or the difficulty of reusing components. If you faced with this problem, I recommend considering CSS Modules, as, in my opinion, this is a more optimal solution for the above factors. In any case, whatever you choose, write meaningful code and don't get fooled by the hype. Hype will pass, and we all have to live with it. Have great and interesting projects, dear readers! Top comments (30) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand dastasoft dastasoft dastasoft Follow Senior Software Engineer Work Senior Software Engineer Joined Feb 17, 2020 • Mar 12 '21 Dropdown menu Copy link Hide One pro of CSS, the hot reload is instant when you just change CSS, with CSS in JS the project is recompiled. For CSS-in-JS I find easier to reuse that code in a React Native project. My personal conclusion is that we are constantly trying to avoid CSS but at the end of the day, CSS will stay here forever. Great article btw! Like comment: Like comment: 25 likes Like Comment button Reply Collapse Expand GreggHume GreggHume GreggHume Follow A developer who works with and on some of the worlds leading brands. My company is called Cold Brew Studios, see you out there :) Joined Mar 10, 2021 • Mar 9 '22 • Edited on Mar 9 • Edited Dropdown menu Copy link Hide I ran into issues with css modules that styled components seemed to solve. But i ran into issues with styled components that I wouldn't have had with plain scss. So some things to think about: Styled components is a lot more overhead because all the styled components need to be complied into stylesheets and mounted to the head by javascript which is a blocking language. On SSR styled components get compiled into a ServerStyleSheet that then hydrate the react dom tree in the browser via the context api. So even then the mounting of styles only happens in the browser but the parsing of styles happens on the server - that is still a performance penalty and will slow down the page load. In some cases I had no issues with styled components but as my site grew and in complex cases I couldn't help but feel like it was slower, or didn't load as smoothly... and in a world where every second matters, this was a problem for me. Here is an article doing benchmarks on CSS vs CSS in JS: pustelto.com/blog/css-vs-css-in-js... I use nextjs, it is a pity they do not support component level css and we are forced to use css modules or styled components... where as with Nuxt component level scss is part of the package and you have the option on how you want the sites css to bundled - all in one file, split into their own files and some other nifty options. I hope nextjs sharped up on this. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Nwanguma Victor Nwanguma Victor Nwanguma Victor Follow 🕊 Location Lagos, Nigeria Work Software Developer Joined Feb 18, 2021 • Jun 22 '22 • Edited on Jun 22 • Edited Dropdown menu Copy link Hide A big tip that might help. Why not use SCSS and unique classNames: For example create a unique container className (name of the component) and nest all the other classNames under that unique container className. .home-page-guest { .nav {} .main {} .footer {} } Enter fullscreen mode Exit fullscreen mode < div className = " home-page-guest " > < div className = " nav " /> < div className = " main " /> < div className = " footer " /> < /div > Enter fullscreen mode Exit fullscreen mode Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Cindy Vos Cindy Vos Cindy Vos Follow Tuff shed and light and strong enough Joined Sep 11, 2025 • Sep 15 '25 Dropdown menu Copy link Hide I bet you did Greg Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Hank Queston Hank Queston Hank Queston Follow Work CTO at Bonfire Joined May 25, 2021 • May 25 '21 Dropdown menu Copy link Hide I agreed, CSS Modules make a lot more sense to me over Styled Components, always have! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Comment deleted Collapse Expand Alien Padilla Rodriguez Alien Padilla Rodriguez Alien Padilla Rodriguez Follow Joined Jan 24, 2022 • Apr 23 '22 Dropdown menu Copy link Hide @Petar Kokev If something I learned from this years of working with React and other projects is that the correct library for project isn't the correct library for another. So the mos important think that we need to do is select the tools, libraries and technologies that fit better to the current project. In this case you can't use Styled-components on sites that require a good SEO, becouse the mos important think here is the SEO and you cant sacrify it. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand thedev1232 thedev1232 thedev1232 Follow tech enthusiast - code to the nuts Location sanjose Work Senior dev Manager at self Joined Oct 26, 2020 • Mar 31 '22 Dropdown menu Copy link Hide How about having to deal with libraries like Material UI with next js? I have an issue to decide whether to use just makeStyles function or should we use styled components? My main concern is code longevity and maintenance without any issues Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Will Farley Will Farley Will Farley Follow Joined Jan 24, 2022 • Jan 24 '22 Dropdown menu Copy link Hide My big issues with styled components is they are deeply coupled with your code. I've opted to use emotion's css utility exclusively and instructed my team to avoid using any of the styled component features. We've loved it but this was a few years ago. For newer projects I'm going with the css modules design. Also why does anyone care about sass anymore? With css variables and the css nesting module in the specification, you get the best parts of sass with vanilla css. The other features are just overkill for a css-module that should represent a single react component and thus nothing :global . Complicated sass directives and stuff are just overkill. Turn it into a react component and don't make any crazy css systems. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Nwanguma Victor Nwanguma Victor Nwanguma Victor Follow 🕊 Location Lagos, Nigeria Work Software Developer Joined Feb 18, 2021 • Mar 23 '22 Dropdown menu Copy link Hide Same I was trying to revamp my personal site, I discovered that I would have to rewrite alot of things, and then I later gave up. I would advice css modules are the way to go, and it greatly helps with SEO. And in teams using SC, naming becomes an issue because some people don't know how to name components and you have to scroll around, just to check if a component is a h1 tag 🤮 CACHEing I can't stress this enough, for enterprise in-house apps it doesn't really matter, but for everyday consumer-essentric apps CACHEing should not be overlooked Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Cindy Vos Cindy Vos Cindy Vos Follow Tuff shed and light and strong enough Joined Sep 11, 2025 • Sep 15 '25 Dropdown menu Copy link Hide Matty Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Will Farley Will Farley Will Farley Follow Joined Jan 24, 2022 • Jan 24 '22 Dropdown menu Copy link Hide You can still have a top-level css file that isn't a css module for global stuff Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Petar Kolev Petar Kolev Petar Kolev Follow Senior Software Engineer with React && TypeScript Location Bulgaria Work Senior Software Engineer @ alkem.io Joined Nov 27, 2019 • Sep 10 '21 Dropdown menu Copy link Hide It is not true that with styled-components one can't use scss syntax, etc. styled-components supports it. Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Eduard Eduard Eduard Follow Taxation is robbery Joined Oct 25, 2019 • Mar 28 '21 Dropdown menu Copy link Hide How about css-in-js frameworks like material-ua, chakra-ui and others? In my opinion, they dramatically speed up development. Like comment: Like comment: 5 likes Like Comment button Reply Collapse Expand Alien Padilla Rodriguez Alien Padilla Rodriguez Alien Padilla Rodriguez Follow Joined Jan 24, 2022 • Apr 23 '22 Dropdown menu Copy link Hide In my personal opinion I see Styled Components more for a Single Page Aplications where the SEO isn't important and is unecessary to cache css files. In the case of static web site or a site that must have a good SEO the Module-Css is better. @greggcbs My recomendation is to use code splitting if you have problem with the performans when you use Styled-Components in your project, in order to avoid brign all code in the first load of the site. Good article @sergey Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Cindy Vos Cindy Vos Cindy Vos Follow Tuff shed and light and strong enough Joined Sep 11, 2025 • Sep 15 '25 Dropdown menu Copy link Hide Hi Jess Rodriguez celly Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Gass Gass Gass Follow hi there 👋 Email g.szada@gmail.com Location Budapest, Hungary Education engineering Work software developer @ itemis Joined Dec 25, 2021 • Apr 25 '22 • Edited on Apr 25 • Edited Dropdown menu Copy link Hide Good post. I've been using CSS modules for a short time now and I like it. Allows everything to be nicely compartmentalized. I also like that it gives more freedom to name classes in smaller chunks of CSS code. Instead of using it like so: {styles.my_class} I preffer {s.my_class} makes the code looks nicer and more concise. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Mario Iliev Mario Iliev Mario Iliev Follow Joined Jun 14, 2023 • Jun 14 '23 Dropdown menu Copy link Hide I'm sorry but it seems that you don't have much experience with Styled Components. "And the last fundamental flaw is the inability to use ready-made approaches and utilities, such as SCSS, Less and Stylelint, and so on." Not a single thing here is true. SCSS is the original syntax of the package, you can use Stylelint as well. There are a lot more "pros" which are not listed here. By working with JS you are opened to another world. I'll list some more "pros" from the top of my head: consume and validate your theme colors as pure JS object consume state/props and create dynamic CSS out of it you have plugins which can be a live savers in cases like RTL (right to left orientation). Whoever had to support an app/website with RTL will be magically saved by this plugin. You can create custom plugins to fix various problems, or make your own linting in your team project. you don't think about CSS class names and collision. I prefer to be focused on thinking about variable names in my JS only and not spending effort in the CSS as well when you break your visual habits you will realise that's it's easier to have your CSS in your JS file just the way you got used to have your HTML in your JS file (React) In these days CSS has become a monster. You have inheritance, mixins, variables, IF statements, loops etc. Sure they can be useful somewhere but I'm pretty sure that most of you just need to center that div. So in my personal opinion we should strive to keep CSS as simpler as possible (as with everything actually) and I think that Styled Components are kind of pushing you to do exactly that. Don't re-use CSS, re-use components! The only global things you should have are probably just the color theme and animations. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Annie-Huang Annie-Huang Annie-Huang Follow Joined Mar 14, 2021 • Feb 16 '25 Dropdown menu Copy link Hide Couldn't agree more on the last two bullet points~~ Like comment: Like comment: Like Comment button Reply Collapse Expand DrBeehre DrBeehre DrBeehre Follow Location New Zealand Work Software Engineer at Self-Employed Joined Nov 10, 2020 • Mar 14 '21 Dropdown menu Copy link Hide This is awesome! I'm quite new to Web dev in particular and when starting a new project, I've often wondered which approach is better as I could see pros and cons to both, but I never found the time to dig in. Thanks for pulling all this together into a concise blog post! Like comment: Like comment: 1 like Like Comment button Reply View full discussion (30 comments) Some comments may only be visible to logged-in visitors. Sign in to view all comments. Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Sergey Follow Joined Nov 18, 2020 More from Sergey Mastering the Dependency Inversion Principle: Best Practices for Clean Code with DI # webdev # javascript # typescript # programming Rockpack 2.0 Official Release # react # javascript # webdev # showdev Project Structure. Repository and folders. Review of approaches. # javascript # react # webdev # codenewbie 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://www.python.org/success-stories/category/government/#python-network | Government | Our Success Stories | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> Success Stories >>> Government Government Python Powered CrossCompute Report Automation for eReliability Tracker Leads to Cost and Time Savings for the American Public Power Association Saving the world with Open Data and Python Frequentis TAPtools® - Python in Air Traffic Control Success stories home Arts Business Data Science Education Engineering Government Scientific Software Development Submit Yours! ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://www.python.org/success-stories/category/government/#site-map | Government | Our Success Stories | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> Success Stories >>> Government Government Python Powered CrossCompute Report Automation for eReliability Tracker Leads to Cost and Time Savings for the American Public Power Association Saving the world with Open Data and Python Frequentis TAPtools® - Python in Air Traffic Control Success stories home Arts Business Data Science Education Engineering Government Scientific Software Development Submit Yours! ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/privacy#b-information-collected-automatically | Privacy Policy - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://www.python.org/success-stories/category/government/#content | Government | Our Success Stories | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> Success Stories >>> Government Government Python Powered CrossCompute Report Automation for eReliability Tracker Leads to Cost and Time Savings for the American Public Power Association Saving the world with Open Data and Python Frequentis TAPtools® - Python in Air Traffic Control Success stories home Arts Business Data Science Education Engineering Government Scientific Software Development Submit Yours! ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://www.python.org/community/irc/#site-map | Internet Relay Chat | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> IRC Internet Relay Chat There are several Python-related channels on the libera IRC network. All channels are available by connecting to Internet Relay Chat server Libera.Chat . The #python channel is for all discussion about the Python language, ecosystem, and community. You can get immediate help with programming questions. You will need to first register your nickname with Libera, using the nickname setup instructions ( https://libera.chat/guides/registration ). Spanish speakers can use the #pyar channel, from the Python Argentina user group. French speakers can join the #python-fr channel. Finnish speakers can join the #python.fi channel on a different network, IRCnet . (Note: prior to May 2021, these channels existed on Freenode. Some of them were forcibly removed by Freenode operators, after a change in management and network policy. The channels on Freenode are no longer under the PSF umbrella.) Other Channels #python-dev is for CPython developers, where they can coordinate their work or discuss problems. Bots post updates to the channel based on activity in the CPython source tree and bug tracker. #python-infra is for Python infrastructure discussion. #pydotorg is for discussion of this website, python.org. #distutils and #pypa are for Python packaging discussion. Other Sites IRC clients for many platforms can be found in the Internet Relay Chat (IRC) Help Archive . The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/hmpljs | HMPL.js - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Follow Organization actions HMPL.js 🐜 Server-oriented customizable templating for JavaScript hmpl is a small template language for displaying UI from server to client. It is based on customizable requests sent to the server via fetch and processed into ready-made HTML. Location Anthill Joined Joined on Nov 11, 2024 Twitter logo GitHub logo External link icon Support email hmpllang@gmail.com Meet the team Our story We'll do it cool, like an ant. We will build solidly, like an anthill. Our stack Branch, leaf Post 47 posts published Member 1 member Major module update! Anthony Max Anthony Max Anthony Max Follow Nov 17 '25 Major module update! # webdev # javascript # programming # opensource 23 reactions Comments 2 comments 2 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/t/javascript#main-content | JavaScript - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close JavaScript Follow Hide Once relegated to the browser as one of the 3 core technologies of the web, JavaScript can now be found almost anywhere you find code. JavaScript developers move fast and push software development forward; they can be as opinionated as the frameworks they use, so let's keep it clean here and make it a place to learn from each other! Create Post submission guidelines Client-side, server-side, it doesn't matter. This tag should be used for anything JavaScript focused. If the topic is about a JavaScript framework or library , just remember to include the framework's tag as well. about #javascript How should the tag be written? All lower-case letters for the tag: javascript . Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu We're launching on ProductHunt Anthony Max Anthony Max Anthony Max Follow Dec 28 '25 We're launching on ProductHunt # news # javascript # showdev Comments Add Comment 1 min read Major module update! Anthony Max Anthony Max Anthony Max Follow for HMPL.js Nov 17 '25 Major module update! # webdev # javascript # programming # opensource 23 reactions Comments 2 comments 2 min read loading... trending guides/resources Great news today: we've finally launched a section featuring community projects built with hmpl-j... Major module update! 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/missamarakay/following-cooking-recipes-makes-you-a-clearer-writer-460a#audience | Following Cooking Recipes Makes You a Clearer Writer - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Amara Graham Posted on Jul 17, 2019 Following Cooking Recipes Makes You a Clearer Writer # devrel # documentation I'm really into cooking, baking, pickling, really anything that will end in me eating something delicious. But I didn't find it enjoyable or "get good" at cooking overnight. My parents cooked most of our meals and if you planned on eating said meal, you were required to provide some amount of assistance, regardless of your blood relation to the family. After graduating out of dorm life I realized I needed to feed myself or starve, so I started getting bolder with my kitchen experiments and I'm pleased to say I'm still alive. "Ok Amara, but where is the tech components of this blog?" Hold on, I'm setting up the metaphor. "Ok fine." In the Kitchen If you stand in a kitchen and watch my dad cook - he reads a recipe, studies it, then goes through and pulls out all the things he needs to make it happen. For banana bread he usually has to pull the frozen bananas out early to thaw them enough to peel them, he portions out the spices so he can toss them in while mixing, he sprays the loaf pan before the mixture is together. If you watched me in my first apartment attempting banana bread for the first time, you would have seen someone who barely read the recipe (I've made this before, with supervision, and watched my dad make it for years, how hard can it be?) and did exactly every step of the instruction in series. Pull frozen bananas out of the freezer, immediately realize you can't peel a banana when its extra frozen, wait just long enough you can pry the peel off, smash the mostly still frozen bananas, slowly add each spice one at a time, measuring as you go, mix everything together, spray the pan, realize the oven isn't on, wait to pre-heat, blah blah blah, why did this take double the prep time? My dad has always taken the methodical approach to everything, he's a chemist and he loves math. I'm impatient and can't spend even 30 seconds idle when I know I need to complete a task, so I pretty much have the attention span of a Border Collie (have you seen those dogs stare at a ball, full body shaking with excitement?). At My Desk I'm sure you'll be shocked to hear when I sit down to learn some kind of new tech, I barely skim the tutorial or docs, immediately start the "doing", and often end up frustrated and annoyed with the experience. In some cases I tell myself things like "oh I've used an API like this before, I can just make it work" and 3 days later I'm banging my head on the keyboard. "Amara, just slow down and actually read the tutorial." Easier said than done. Not just for me personally, but for any dev, and that includes your dev coworkers, customers, community, etc. Time is precious, workplaces are more agile than ever, and people pay money for other people to stand in line for them. In My Brain Now recipes, just like tutorials, can be poorly written, but even the good ones can suffer from poor execution as I rambled on above. There are 5 things I learned from getting better at following cooking recipes that I think apply to written technical content. Ambiguous Terms Jargon Chunking Brevity Audience Let's take a look at each one. Ambiguous Terms Have you ever read a recipe, seen the word "mix" and go... with a spoon? A stand mixer? How long? Or how about "hand mix"? Did you know that a 'Hand Mixer' is an appliance and not the things at the end of your arms? Because a few years ago when we first started dating, my now husband did not. In tech, we love using the same term for a number of different things. Or we have a number of different words for the same thing. Really friendly to beginners right? Something like "Run this" might make sense to you, the engineer who built it, because its probably never crossed your mind that you run it globally and not in a particular directory (or vice versa) but that can be one of the most irritating things for a dev struggling with the worry of doing something wrong and/or irreversible. Be explicit in your use of terms and maybe consider a glossary of terms relevant to your project/product/industry/company. What does this mean in this context, right here, right now? Don't leave your reading punching out to search for answers. Jargon Every talk I've given on AI to beginners has included a disclaimer about not only ambiguous terminology but jargon. 'Fine-tuning' is not super intuitive, neither is 'hyperparameter'. 'Fold in' or 'soft peaks' in cooking is right up there too. Mastering the jargon can disrupt retention of fundamental topics. Explaining these terms early in docs and tutorials is crucial. You should not assume knowledge of jargon, so this is another +1 for a glossary. Chunking I am a huge fan of multi-part tutorials and how-to series, so long as they are done right. At the end of each part in a series, you should have a small complete something. Developers may not have time to sit down and do a 3-6 hour tutorial, but they should be able to get 20 minutes to an hour of uninterrupted time. You don't want to tackle a slow cooker recipe at 5pm expecting to eat it for dinner, but you may want to brown some meat so it is ready to toss in the next morning. If I have 20 minutes today to set myself up for success later today or tomorrow, I need to know I can get it done in the allocated time. And I need to feel like I can pick it up again without rereading the entire thing. Brevity Unlike this blog which is probably way too long for most of you, the more concise your written technical content the easier its going to be to follow. It's part of what makes the Tasty videos so appealing to watch - someone makes a sped up, top-down recipe that feels fast and easy even if its neither. This doesn't mean you can't write an introduction or a conclusion that goes more in depth about the content, but when you get to the meat of the docs or tutorial it should be a lean, mean, executing machine. Food bloggers are great at this, they may give you step-by-step pictures and commentary, but they almost always include the recipe separately. So feel free to tell me how you are going to save the world with this tutorial, but keep it out of the exact steps I'm following so I don't get overwhelmed. Audience This is maybe the most important, although I could argue that they all are. Knowing your developer audience is extremely important in technical writing. This helps you make decisions about what languages and references to use, what their workstation may look like, and maybe even things like their attention span. If your audience is students, whether they will admit it or not, they tend to have WAY more time to sit down and really study a tutorial. Or maybe they are participating in a hackathon and it just needs to work as fast as possible. But maybe your audience is enterprise developers, like mine often is. This means it has to be production-ready, maintainable, and even trainable across teams. Your maintenance team may be entirely separate from your product engineering team, so the content they follow may need to be different. Knowing or identifying your audience can be challenging, but this is a great opportunity for your devrel team to really shine. Celebrate Those Incremental Improvements Like I mentioned earlier, I didn't wake up one day and realize if I actually read the recipe, prepped ahead of time, and researched how to do certain kitchen techniques (again, ahead of time), I could maximize my time in the kitchen and feel less overwhelmed. In fact, I'm probably 50:50 in my ability to prep and run in parallel or haphazardly skim in series today. But snaps for me because this week I measured everything out before I started cooking! I'm sure you could make an argument that my dad is a 'senior' in the kitchen and I'm not (but I'm also not junior either), but he'd prefer you only use 'senior' when used in conjunction with "senior discount" at this point in his life. Let's say 'seasoned'. Whether you are a junior or senior dev, you still need the content you are consuming to prepare you for success. But with more and more folks using services like Blue Apron, Hello Fresh, Home Chef, arguably boxed Bootcamp experiences for the kitchen, we have a new generation of folks training themselves how to follow recipes and we can translate that experience into the tech world, allowing for more confident, empowered folks in the kitchen and at the keyboard. So instead of shouting "read the docs" or "follow the tutorial" make sure your content is as consumable and delicious as a home cooked meal. Top comments (5) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Author. Speaker. Time Lord. (Views are my own) Email codemouse92@outlook.com Location Time Vortex Pronouns he/him Work Author of "Dead Simple Python" (No Starch Press) Joined Jan 31, 2017 • Aug 5 '19 Dropdown menu Copy link Hide Excellent write up! I'm actually going to include this on the #beginners tag wiki for authors to read. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand JeffD JeffD JeffD Follow Code-quality 🩺 Teamwork 🐝 & everything that can simplify the developper's life 🗂️. Location France Joined Oct 16, 2017 • Sep 16 '19 Dropdown menu Copy link Hide This post is a must-read ! It's perfect 🏆 ("Hold on, I'm setting up the metaphor." 🤣) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Alvarez García Alvarez García Alvarez García Follow After more than 10 years backending, now trying to make this CSS properties work. Location Buenos Aires, Argentina Work FullStack Joined Apr 24, 2019 • Jul 25 '19 Dropdown menu Copy link Hide DevRel in construction here, thanks for this really simple and enjoyable post. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Amara Graham Amara Graham Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 • Jul 25 '19 Dropdown menu Copy link Hide Thank you! :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Shashamura1 Shashamura1 Shashamura1 Follow Hi everyone my name is daniel.gentle loving caring I’am a type of person that always optimistic in every thing that I doing im very couriours and ambitious to lean I’m very new in this site Email ashogbondaniel292@gmail.com Location USA Education Technical college Work CEO at mylocallatest ...https://mylocallatest512644105.wordpress.com Joined Sep 12, 2022 • Oct 8 '22 Dropdown menu Copy link Hide Nice post I can use it to learn as project in dev.com ..to share the interest story of cooking Like comment: Like comment: 1 like Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 More from Amara Graham Moving Config Docs From YAML to Markdown # documentation # yaml # markdown Moving DevEx from DevRel to Engineering # devrel # devex # engineering # reorg Bing Webmaster Tools De-indexed My Docs Site and Increased My Cognitive Load # webdev # seo # documentation 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/new/javascript | New Post - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Join the HMPL.js Forem HMPL.js Forem is a community of 3,676,891 amazing developers Continue with Apple Continue with Google Continue with Facebook Continue with Forem Continue with GitHub Continue with Twitter (X) OR Email Password Remember me Forgot password? By signing in, you are agreeing to our privacy policy , terms of use and code of conduct . New to HMPL.js Forem? Create account . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/t/help | Help! - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Help! Follow Hide A place to ask questions and provide answers. We're here to work things out together. Create Post submission guidelines This tag is to be used when you need to ask for help , not to share an article you think is helpful . Please review our community guidelines When asking for help, please follow these rules: Title: Write a clear, concise, title Body: What is your question/issue (provide as much detail as possible)? What technologies are you using? What were you expecting to happen? What is actually happening? What have you already tried/thought about? What errors are you getting? Please try to avoid very broad "How do I make x" questions, unless you have used Google and there are no tutorials on the subject. about #help This is a place to ask for help for specific problems. Before posting, please consider the following: If you're asking for peoples opinions on a specific technology/metholody - #discuss is more appropriate. Are you looking for how to build x? Have you Googled to see if there is already a comprehensive tutorial available? Older #help posts 1 2 3 4 5 6 7 8 9 … 75 … 158 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu [TIL][Android] Common Android Studio Project Opening Issues Evan Lin Evan Lin Evan Lin Follow Jan 11 [TIL][Android] Common Android Studio Project Opening Issues # help # beginners # android # kotlin Comments Add Comment 2 min read Adding a Missing Warning Note Favoured Anuanatata Favoured Anuanatata Favoured Anuanatata Follow Jan 10 Adding a Missing Warning Note # help # beginners # opensource Comments Add Comment 1 min read How I Fixed the dyld: Symbol not found Error After Updating PHP 8.4 in Laravel Herd (macOS Monterey) Timothy Adeleke Timothy Adeleke Timothy Adeleke Follow Jan 10 How I Fixed the dyld: Symbol not found Error After Updating PHP 8.4 in Laravel Herd (macOS Monterey) # help # fix # php # laravel 5 reactions Comments Add Comment 3 min read OpenLens Cannot Connect to AWS EKS Cluster: executable aws not found Camille Chang Camille Chang Camille Chang Follow Jan 7 OpenLens Cannot Connect to AWS EKS Cluster: executable aws not found # help # aws # kubernetes # tooling Comments Add Comment 1 min read How to Successfully Remove a Password from a PST File Without Data Loss? Brant anson Brant anson Brant anson Follow Jan 6 How to Successfully Remove a Password from a PST File Without Data Loss? # help # microsoft # security Comments 2 comments 1 min read JDBC Connection issue to Sybase Server Ravi Manthena Ravi Manthena Ravi Manthena Follow Jan 6 JDBC Connection issue to Sybase Server # help # database # java Comments Add Comment 1 min read 🌈 Looking for Guidance: I’m Building an HRT Journey Tracker Suite, but I’m Stuck codebunny20 codebunny20 codebunny20 Follow Jan 10 🌈 Looking for Guidance: I’m Building an HRT Journey Tracker Suite, but I’m Stuck # discuss # architecture # help # privacy Comments 2 comments 2 min read Hi , Started Docker Chandra Shekar Chandra Shekar Chandra Shekar Follow Jan 5 Hi , Started Docker # help # learning # docker Comments Add Comment 1 min read Question: Can a UAE Freezone company legally operate in other freezones or the mainland in 2026? Mandeep Singh Mandeep Singh Mandeep Singh Follow Jan 4 Question: Can a UAE Freezone company legally operate in other freezones or the mainland in 2026? # help # news # startup Comments Add Comment 2 min read I landed myself in a weird technical spot before graduation need perspective anant anant anant Follow Jan 2 I landed myself in a weird technical spot before graduation need perspective # help # programming # ai # machinelearning Comments Add Comment 1 min read React Flow: adding Controls to example hides nodes and edges Tim Coddington Tim Coddington Tim Coddington Follow Jan 1 React Flow: adding Controls to example hides nodes and edges # help # beginners # css # react Comments Add Comment 2 min read How to Win Clients Online with Trust and Clarity - a Practical Guide Per Starke Per Starke Per Starke Follow Jan 1 How to Win Clients Online with Trust and Clarity - a Practical Guide # help # freelance # opensource # website 1 reaction Comments Add Comment 8 min read What I Learned Trying to Write Better GitHub Issues for Open-Source Contributors georgetoloraia georgetoloraia georgetoloraia Follow Dec 30 '25 What I Learned Trying to Write Better GitHub Issues for Open-Source Contributors # help # opensource # github # programming Comments Add Comment 2 min read Proxmox'ta io-error Enes Baytekin Enes Baytekin Enes Baytekin Follow for Açıklab Dec 29 '25 Proxmox'ta io-error # help # linux # tutorial # devops 1 reaction Comments Add Comment 2 min read My Indie App Got Quarantined on itch.io — and I’m Opening It Up to the Dev Community Saami abbas Khan Saami abbas Khan Saami abbas Khan Follow Jan 7 My Indie App Got Quarantined on itch.io — and I’m Opening It Up to the Dev Community # help # opensource # coding # javascript 3 reactions Comments Add Comment 2 min read How to fix the problem of the right side being completely black when creating a function to convert a web page to PDF Kazutora Hattori Kazutora Hattori Kazutora Hattori Follow Dec 25 '25 How to fix the problem of the right side being completely black when creating a function to convert a web page to PDF # help # webdev # programming # javascript 5 reactions Comments Add Comment 2 min read AI Look-Alike Search for OF Creators — Need Advice on Better Face Models Галина Садовская Галина Садовская Галина Садовская Follow Dec 25 '25 AI Look-Alike Search for OF Creators — Need Advice on Better Face Models # help # ai # deeplearning Comments Add Comment 3 min read Top-level await on iOS Safari/Chrome fails Andrew Elans Andrew Elans Andrew Elans Follow Dec 22 '25 Top-level await on iOS Safari/Chrome fails # help # frontend # ios # javascript Comments Add Comment 2 min read What’s One Bazel Feature You Wish Docker Had? Sai Kiran Sai Kiran Sai Kiran Follow Dec 21 '25 What’s One Bazel Feature You Wish Docker Had? # discuss # bazelbuild # help # docker Comments Add Comment 1 min read Cause and solution for "Module 'markdown-it' not found" in TypeScript (@types/markdown-it) Kazutora Hattori Kazutora Hattori Kazutora Hattori Follow Dec 21 '25 Cause and solution for "Module 'markdown-it' not found" in TypeScript (@types/markdown-it) # help # typescript # webdev # programming 1 reaction Comments Add Comment 1 min read Resolving Old AUR App Dependency Hell after Arch Update (ICU 76 78) hopsayer hopsayer hopsayer Follow Dec 25 '25 Resolving Old AUR App Dependency Hell after Arch Update (ICU 76 78) # help # archlinux # linux Comments Add Comment 5 min read Fix Resolution in frontend Farhan Khan Farhan Khan Farhan Khan Follow Dec 18 '25 Fix Resolution in frontend # help # frontend # react # css Comments Add Comment 1 min read Need Helps '=' HexZo Network HexZo Network HexZo Network Follow Dec 16 '25 Need Helps '=' # help # python # beginners # deeplearning Comments Add Comment 2 min read Vite + Antd App works on Windows but Single Page crashes on Linux Production (Minified React Error #130) Prashant Vaghela Prashant Vaghela Prashant Vaghela Follow Dec 13 '25 Vite + Antd App works on Windows but Single Page crashes on Linux Production (Minified React Error #130) # help # devops # linux # react Comments Add Comment 2 min read Form content disappears after page refresh ShangYunYao ShangYunYao ShangYunYao Follow Dec 14 '25 Form content disappears after page refresh # help # ux # frontend # javascript Comments Add Comment 1 min read loading... trending guides/resources Resolving Old AUR App Dependency Hell after Arch Update (ICU 76 78) My Indie App Got Quarantined on itch.io — and I’m Opening It Up to the Dev Community AttributeError: 'int' object has no attribute 'title' in python3 Windows Service equivalent in Linux? Do anyone know about any tool which can help me cross post between few tech platforms like dev.to... How to Fix Sanity Studio Module Error on Windows Question: Can a UAE Freezone company legally operate in other freezones or the mainland in 2026? OpenLens Cannot Connect to AWS EKS Cluster: executable aws not found How can I determine the position of a text string on the screen? Anybody else getting 500 errors on GitHub at all? Don't see anything on their status page. Summary of the error "Cannot find module 'function qt(e={})...'" that occurs when using Tailwind ... Top-level await on iOS Safari/Chrome fails WordPress Common Errors (And How to Fix Them Like a Pro) ⚠️ How to Win Clients Online with Trust and Clarity - a Practical Guide AI Look-Alike Search for OF Creators — Need Advice on Better Face Models Cause and solution for "Module 'markdown-it' not found" in TypeScript (@types/markdown-it) Why a 4-Day Workweek Just Makes Sense This kind of content is what WordPress documentation lacks. Hi , Started Docker Need Helps '=' 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://www.python.org/community/irc/#top | Internet Relay Chat | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> IRC Internet Relay Chat There are several Python-related channels on the libera IRC network. All channels are available by connecting to Internet Relay Chat server Libera.Chat . The #python channel is for all discussion about the Python language, ecosystem, and community. You can get immediate help with programming questions. You will need to first register your nickname with Libera, using the nickname setup instructions ( https://libera.chat/guides/registration ). Spanish speakers can use the #pyar channel, from the Python Argentina user group. French speakers can join the #python-fr channel. Finnish speakers can join the #python.fi channel on a different network, IRCnet . (Note: prior to May 2021, these channels existed on Freenode. Some of them were forcibly removed by Freenode operators, after a change in management and network policy. The channels on Freenode are no longer under the PSF umbrella.) Other Channels #python-dev is for CPython developers, where they can coordinate their work or discuss problems. Bots post updates to the channel based on activity in the CPython source tree and bug tracker. #python-infra is for Python infrastructure discussion. #pydotorg is for discussion of this website, python.org. #distutils and #pypa are for Python packaging discussion. Other Sites IRC clients for many platforms can be found in the Internet Relay Chat (IRC) Help Archive . The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/new/showdev | New Post - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Join the HMPL.js Forem HMPL.js Forem is a community of 3,676,891 amazing developers Continue with Apple Continue with Google Continue with Facebook Continue with Forem Continue with GitHub Continue with Twitter (X) OR Email Password Remember me Forgot password? By signing in, you are agreeing to our privacy policy , terms of use and code of conduct . New to HMPL.js Forem? Create account . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/dorahacks/dorahacks-start-up-ideas-2026-pt1-digital-finance-in-the-circlearc-ecosystem-98m#comments | DoraHacks Start-up Ideas 2026: Pt.1 Digital Finance in the Circle/Arc ecosystem - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse DoraHacks Posted on Jan 13 DoraHacks Start-up Ideas 2026: Pt.1 Digital Finance in the Circle/Arc ecosystem # cryptocurrency # startup # web3 By Steve Ngok, Chief Strategy Officer, DoraHacks The Introduction For nearly a decade, the established financial order has viewed crypto with skepticism and disdain. To observers in ivory towers, the industry appeared as little more than a casino—a chaotic theater of speculation divorced from the real economy. For a long time, this criticism had merit. But surveying the landscape of 2026, the early confusion has given way to structural clarity. The industry hasn't merely grown; it has bifurcated. We are witnessing a decisive schism. On one side lies continued speculation: prediction markets, exchanges, volatility optimization. This remains a vibrant, if noisy, arena. But distinct from this, a more sober reality has emerged. Stablecoins have become the TCP/IP of money. They are eating cross-border payments, devouring FX inefficiencies, and enabling entirely new economic primitives for AI agents. In this landscape, early DeFi's "move fast and break things" mantra has been replaced by demands for determinism, compliance, and institutional scale. This is why the Circle and Arc ecosystem has emerged as the dominant stack. They didn't just build a blockchain; they built an Economic Operating System . They did the hard, unglamorous work of regulatory integration and liquidity plumbing so you don't have to. If you're a founder in 2026, you don't need to reinvent the wheel. The rails are laid by DoraHacks and its partners. The regulatory moat is dug. The liquidity is deep. The question is no longer whether we can put real-world assets on-chain, but what happens when money becomes as programmable as bits. Here is where the alpha lies. Time to build for the future. Track I: The Global Capital Expressway From Simple Remittances to Programmable Settlement 1. The Core Thesis The traditional cross-border payment system is trapped in a structural trilemma: you can have speed, you can have low cost, or you can have regulatory transparency, but you rarely get all three. The current correspondent banking model is a relic of the analog age, ill-equipped for the velocity of the internet economy. The Circle and Arc ecosystem has finally solved this coordination problem: CPN (Circle Payments Network) solves the "Last Mile," connecting the digital ledger to the global banking system. CCTP & Gateway solve liquidity fragmentation, unifying assets across fragmented blockchains. Arc provides the "Matching and Clearing Engine": delivering the sub-second certainty and low latency that Wall Street demands. The Mission: To use Arc as the central clearing layer for global capital, building the next generation of commercial payment applications that render the SWIFT network obsolete. 2. The High-Value Opportunities We are looking beyond basic payroll or merchant checkout. The real opportunity lies in re-architecting B2B flows and platform economics. A. Programmable Trade Finance The Thesis: "Funds arrive the second the cargo does." The Problem: International trade runs on friction. Exporters wait 30–90 days for payment or rely on expensive, paper-heavy Letters of Credit. Trust is slow and costly. The Solution: Escrow: The importer locks USDC in a smart contract on Arc. Trigger: An Oracle feeds real-time logistics data (API) to the chain. "Cargo Signed" = "Payment Triggered." Settlement: The contract autonomously releases the USDC. Exit: CPN converts the USDC to local currency (e.g., Vietnamese Dong) and wires it to the exporter instantly. Why Arc? Only Arc’s sub-second finality and near-zero fees make it economically viable to trigger payments based on high-frequency logistics updates. The Builder Profile: Experts in supply chain ERP and logistics data. B. The Internal Treasury Engine The Thesis: "Stop burning millions on internal wires." The Problem: A multinational like Toyota or Siemens has subsidiaries in 50 countries. When Brazil owes Germany, and Germany owes the US, they send wires back and forth, bleeding money on FX fees and float. The Solution: On-Chain Pooling: Subsidiaries convert local cash to USDC via CPN and pool it in a central Arc Treasury. Netting: A "Netting Algorithm" runs on Arc, calculating exactly who owes what to whom on a ledger. Settlement: You only move the difference . Off-Ramp: Subsidiaries pull liquidity back to local fiat only when needed. Why Arc? Privacy tooling protects internal financial data, while high throughput handles the complex math of real-time netting. The Builder Profile: Fintech architects and Enterprise SaaS founders. C. The "Web3 Stripe Connect" The Thesis: "A universal payout router for the gig economy." The Problem: Platforms like Uber, Airbnb, or Upwork struggle to pay a global workforce. Sending $50 to a freelancer in the Philippines is often too expensive to justify. The Solution: Aggregate: The platform loads a single pool of USDC onto Arc. Distribute: One API call triggers thousands of payouts. Route: The smart contract acts as a router. Crypto-native user? Send to wallet. Traditional user? Route through CPN to their local bank. Why Arc? Batch processing capabilities allow for "micropayments" that are mathematically impossible on legacy rails. The Builder Profile: Payment gateway engineers and platform aggregators. D. The Programmable Corporate Card The Thesis: "Give your AI agent a credit card, but control the spending with code." The Problem: Companies need to buy software globally, but corporate cards are dumb. They lack granular control, and you can't easily give one to an AI agent or a temporary contractor. The Solution: The Pool: A corporate USDC treasury on Arc. The Card: Instantly issue virtual Visa/Mastercard credentials via CPN. The Rules: Embed logic in the smart contract: "This card only works for AWS," or "Max spend $100/day." The Settlement: Transactions are settled instantly on-chain via StableFX. Why Arc? It moves financial control from the bank's policy department to the company's code repository. The Builder Profile: Expense management and B2B fintech teams. 3. The Technical Blueprint For the developer, the architecture is now standardized. Here is how you build it: Step 1: On-Ramp. Use the CPN API to generate Virtual IBANs. Fiat flows in; USDC is automatically minted to an Arc address. Step 2: Liquidity. Use the Gateway SDK to sweep USDC from fragmented chains (Ethereum, Solana) into your central Arc application. Step 3: Business Logic. Deploy your Solidity contracts on Arc. Payroll: distributeSalary(recipients, amounts) Trade: releaseFunds(proofOfShipping) Step 4: Off-Ramp. Call the CPN Payout API to burn USDC and trigger a local bank wire, or use Programmable Wallets to settle directly on-chain. 4. The Conclusion "Build a bank that runs on code." Understand your competition: You are competing against the friction of the 1970s banking system. By combining the speed of Arc with the reach of CPN, you have the power to reduce global settlement costs by 80% and accelerate speed from "T+2 Days" to "T+0 Seconds." This is an entry ticket to a multi-trillion dollar market. Track II: The On-Chain FX Revolution From Manual Conversion to Algorithmic Liquidity Networks 1. The Core Thesis The traditional Foreign Exchange (FX) market, the largest financial market in the world, is currently held back by an antiquated triad of inefficiencies: Settlement Latency (the T+2 day standard), Gatekeeping (only giants get the best rates), and Opacity (layers of hidden fees). The combination of Circle and Arc dismantles this structure: StableFX provides an institutional-grade price feed (RFQ mechanism), meaning "Inquiry equals Execution." Partner Stablecoins (e.g., MXNB, JPYC, BRLA) provide the necessary local currency anchors. Arc provides the execution environment where these currencies can be swapped in mere milliseconds. The Mission: To utilize code to autonomously manage currency risk and eliminate the friction of exchange from cross-border commerce. 2. The High-Value Opportunities We are looking beyond simple hedging or remittance apps. The real opportunity lies in deep financial engineering applied to global trade. A. The Autonomous Multi-Currency Treasury The Thesis: "Democratizing Apple’s treasury capabilities for the SME." The Problem: A mid-sized cross-border e-commerce firm earns in Euros (EUR), pays server costs in Dollars (USD), and pays salaries in Yen (JPY). Traditional banking charges exorbitant spreads for these conversions, and finance teams often miss optimal windows due to manual processing. The Solution: Automated Strategy: The enterprise sets rules on Arc: "If EURC balance > 50,000 and EUR/USD rate > 1.08, automatically swap 50% to USDC." Instant Execution: Smart contracts monitor StableFX quotes via Oracle and execute immediately when conditions are met. Payroll: At month's end, USDC is automatically converted to JPYC at the best market rate and distributed to employee wallets. Why Arc? Only Arc supports this high-frequency monitoring and low-cost execution. Traditional banks cannot offer this level of programmability. The Builder Profile: Enterprise financial SaaS teams and ERP integrators. B. The "1inch" for FX The Thesis: "Best execution, globally and instantly." The Problem: When converting USDC to EURC, prices vary between Uniswap, StableFX, and Curve. The user rarely knows where the best liquidity lies. The Solution: Aggregation: Build a dApp on Arc that connects StableFX (RFQ mode) with on-chain AMMs. Routing: When a user wants to swap $1M, the algorithm splits the order: 60% via StableFX (for depth) and 40% via AMM. Atomic Settlement: The user clicks once. The complexity is abstracted. Why Arc? Its high performance allows for the querying of multiple liquidity sources and trade execution within a single block. The Builder Profile: DeFi developers and Market Makers. C. The Tokenized Carry Trade Protocol The Thesis: "bringing Wall Street’s oldest strategy to DeFi rails." The Problem: The Carry Trade, borrowing in a low-interest currency to invest in a high-interest one, has historically been the exclusive preserve of hedge funds and banks. The Solution: The Mechanism: A user deposits USDC. The Operation: The protocol borrows a low-rate currency (e.g., JPYC) in the background, swaps it via StableFX, and invests in a high-yield asset (e.g., Tokenized T-Bills). Risk Management: Utilizing Arc’s automation, the system executes millisecond-level liquidation if exchange rates hit a volatility threshold. Why Arc? This strategy requires extreme speed. Arc’s Deterministic Finality is the critical safeguard against liquidation failure. The Builder Profile: Quantitative trading teams and advanced DeFi architects. D. The "Local-First" Checkout The Thesis: "Pay in Pesos, Settle in Dollars. Zero Friction." The Problem: A US-based Shopify merchant wants USDC, but their Mexican customer wants to pay in Pesos (MXN). Current credit card rails charge 3-5% in FX fees for this privilege. The Solution: Frontend: The buyer sees the price in MXNB (Mexican Peso Stablecoin). Payment: The buyer pays MXNB. Backend: The transaction hits Arc, instantly swaps MXNB to USDC via StableFX. Settlement: The merchant receives USDC. No banks involved. Total fees < 1%. Why Arc? Instant confirmation makes the checkout experience silky smooth, no "waiting for block confirmations." The Builder Profile: Payment gateway developers and e-commerce infrastructure teams. 3. The Technical Blueprint For the developer, the integration path is clear: Step 1: Pricing. Integrate the StableFX API (Oracle) . This is a stream of executable quotes. Step 2: Assets. Ensure your smart contracts are compatible with ERC-20 standards for USDC, EURC, and Partner Stablecoins (JPYC, MXNB). Step 3: Execution. Build a swapCurrency(tokenIn, tokenOut, amount, minRate) function. Inside, call the StableFX settlement contract, passing the signed RFQ quote to finalize the atomic swap. Step 4: Interoperability (Optional). Use the xReserve pattern. If your strategy requires assets from the Bitcoin network, wrap them into the Arc ecosystem via xReserve to access FX liquidity. 4. The Conclusion "Forex is the biggest market in the world, and it is still running on 1980s technology." In this track, you are re-plumbing the vascular system of global trade. By leveraging StableFX and Arc, you have the opportunity to build the next generation of foreign exchange applications: 24/7 operation, T+0 settlement, and zero banking fees. This is the Crown Jewel of Fintech. Track III: The Silicon Economy From Human-Computer Interaction to Machine-to-Machine Commerce 1. The Core Thesis The current generation of Artificial Intelligence is defined by a structural paradox: infinite intelligence, yet zero financial agency. An AI Agent can plan a complex itinerary for a trip to Tokyo, but it is powerless to book the flight. It can write the code for a server, but it cannot rent the hardware. It is a brain in a jar, brilliant, but severed from the physical economy. The Circle and Arc ecosystem provides the missing limb: Circle Programmable Wallets grant each Agent a unique, policy-controlled on-chain identity. The x402 Protocol serves as the universal "negotiation language" for value (restoring the "Payment Required" status to the web). Gas Station resolves the UX friction, abstracting away the complexity of ETH and Gas so that payment feels like a simple API call. Arc provides the high-concurrency, deterministic environment required for machine-speed transactions. The Mission: To construct the infrastructure and applications that allow AI to autonomously earn, spend, and manage assets. To grant economic sovereignty to the machine. 2. The High-Value Opportunities We are looking beyond simple "crypto-browsers." We are looking for the fundamental rails of a machine-native GDP. A. The API Negotiator The Thesis: "The death of the monthly subscription; the birth of real-time bidding." The Problem: Developers are currently forced to manually subscribe to dozens of APIs (OpenAI, Twilio, SerpApi), managing a chaotic ring of keys and credit card limits. The Solution: Dynamic Gateway: Service providers publish APIs on Arc with dynamic, load-based pricing. The Agent: Before calling data, the user’s AI Agent queries via x402: "Price check?" The Settlement: The provider responds: "0.002 USDC." The Agent verifies its budget and executes the payment instantly. Pay-As-You-Go: No subscriptions. No breakage. Millisecond settlement. Why Arc? High-frequency micropayments are economically impossible on legacy rails. On Arc, they are the standard. The Builder Profile: API aggregators and developer tool architects. B. The "Pay-per-Context" Gateway The Thesis: "Solving the 'New York Times vs. OpenAI' legal deadlock." The Problem: Large Language Models (LLMs) need fresh data, but publishers are blocking scrapers because they aren't getting paid. The legal system is gridlocked. The Solution: Compliance: Publishers deploy x402 headers on their content. Micro-Access: When an AI scraper visits, it doesn't hit a paywall; it autonomously pays 0.01 USDC to the publisher's Arc wallet for the legal right to ingest that specific article. Revenue Flow: Capital flows instantly to creators and platforms, creating a sustainable "AI-Media" ecology. Why Arc? The negligible transaction fees make the $0.01 economy viable. The Builder Profile: Media-tech firms and Web3 browser plugin developers. C. The "Budgeted Butler" Protocol The Thesis: "Trust through code, not faith." The Problem: You want your AI to buy your coffee and book your flights, but you will never give a hallucinating chatbot your credit card. The Solution: Scoped Permissions: Leverage the "Policy Engine" of Circle Programmable Wallets. The Rules: Issue the AI a sub-wallet with strict on-chain logic: "Max spend 50 USDC/day," "Transfer only to whitelisted addresses (Starbucks, Uber)," "Transactions > $100 require human biometric approval." Autonomy: Inside these guardrails, the AI operates with total freedom. Why Arc? On-chain policy execution is transparent and immutable, offering a flexibility that traditional bank risk models cannot match. The Builder Profile: Smart home hubs and Personal Assistant App developers. D. Flash Bounties for RLHF The Thesis: "The Reverse Turing Test." The Problem: AI still gets stuck. It fails to read a blurred CAPTCHA or misunderstands the nuance of sarcasm. The Solution: The Request: The AI Agent encapsulates the difficult task into a "Micro-Bounty" and broadcasts it to Arc with a 0.5 USDC reward. The Human: A "micro-worker" anywhere in the world taps the notification, solves the CAPTCHA, or labels the data. The Payment: The AI verifies the input and releases funds instantly. Why Arc? This creates a global, frictionless labor market settled in USDC. The Builder Profile: Data labeling platforms and crowdsourcing networks. 3. The Technical Blueprint For the engineer, the assembly instructions for a Silicon Economic Entity are as follows: Step 1: Identity. Use the Circle Programmable Wallets API to instantiate a Smart Contract Account (SCA) for the AI. Critical: Configure Spending Policies (e.g., maxAmountPerDay = 10 USDC). Step 2: Protocol. Integrate the x402 (HTTP 402) standard. When the AI makes a request, the server returns 402 Payment Required along with a destination address and amount. The AI parses this and signs the transaction. Step 3: Gas. Configure Gas Station and Paymaster . The AI holds only USDC. The Paymaster abstracts the gas fees in the background, ensuring the AI's logic loop is never broken by a lack of native tokens. Step 4: Logic. Deploy verification contracts on Arc. Ensure that successful payment triggers an Oracle or Event Listener to release the API key or service access off-chain. 4. The Conclusion "Give your AI a wallet, not just a prompt." Right now, your AI is like a genius locked in a library: it knows everything, but it can affect nothing in the physical world. By combining the speed of Arc with the identity layer of Circle Wallets, you are handing that genius a key. You are architecting the GDP of the Machine Economy. Track IV: Economic Leapfrog & Inclusion From "Waiting for Aid" to "Accessing the Global Grid" 1. The Core Thesis Traditional financial inclusion has failed not because of malice, but because of math. The unit economics of the legacy banking system are broken: the Customer Acquisition Cost (CAC) and service overhead for a user in a developing market far exceed the profit generated by their deposits. Banks simply cannot afford to open an account for $50. The Circle and Arc ecosystem fundamentally alters this equation: Arc's Negligible Gas Fees make a $1 transfer economically rational, not just charitable. Circle User-Controlled Wallets resolve the "Key Management" barrier, replacing terrifying seed phrases with familiar social logins and passkeys. USDC solves the "Volatility" problem, protecting the vulnerable from local currency inflation. The Mission: To build the "Leapfrog Stack", minimalist, anti-inflationary, and disintermediated financial tools that serve the bottom 50% of the global population. 2. The High-Value Opportunities We are talking about sustainable, scalable business models for the next billion users. A. Reputation-Based Micro-Lending The Thesis: "Digitizing the social capital of the village to access global liquidity." The Problem: A fruit vendor in Kenya needs $100 for inventory. She has no credit score, so she is forced into predatory loans. Meanwhile, DeFi protocols sit on billions of dollars of idle capital that cannot be deployed without over-collateralization. The Solution: ROSCA 2.0: Move the traditional "rotating savings and credit association" onto Arc. The SBT: If a member repays on time, this behavior is minted as a Soulbound Token (SBT), a digital credit score. The Bridge: High-reputation ROSCA groups are bundled together to borrow from global DeFi pools at competitive rates (e.g., 10%), bypassing local loan sharks (100%+). Why Arc? Only Arc can handle the high volume of micro-repayment data while providing the transparent audit trail required by global lenders. The Builder Profile: Emerging market Fintech founders and DeFi protocol architects. B. Pay-As-You-Go Asset Networks The Thesis: "Streaming money for streaming utility." The Problem: A low-income family cannot afford the upfront cost of a solar panel or a motorbike, despite having a steady cash flow to pay for it over time. The Solution: IoT + Blockchain: Connect the physical asset (solar panel) to an internet controller. Micro-Unlocking: The user pays 0.50 USDC via their Arc wallet. Smart Contract Logic: Payment confirmed -> Signal sent -> Device unlocks for 24 hours. Ownership: If payment stops, the device locks. Once the total principal is paid, an NFT represents full ownership transfer. Why Arc? The friction of traditional payments makes daily micropayments impossible. Arc makes them trivial. The Builder Profile: IoT hardware hackers and ReFi (Regenerative Finance) entrepreneurs. C. The Programmable Aid Protocol The Thesis: "Ensuring donor funds buy medicine, not alcohol." The Problem: Humanitarian aid is plagued by two cancers: intermediary corruption (skimming off the top) and misuse of funds at the bottom. The Solution: Restricted Assets: Issue a "Wrapped USDC" on Arc specifically for aid. Allow-Listing: Code the token so it can only be transferred to whitelisted wallets (verified pharmacies, schools, grocery stores). Auto-Redemption: Vendors who receive the token can swap it 1:1 for liquid USDC instantly. Privacy: Use Zero-Knowledge proofs so the public sees the flow of funds to valid categories, without exposing the identity of the refugee. Why Arc? Programmable Money is the ultimate solution to the Principal-Agent problem in charity. The Builder Profile: GovTech developers and NGO technical partners. D. Direct-to-Biller Remittances The Thesis: "Don't send cash; settle the bill." The Problem: A migrant worker sends money home for school fees. The cash is received, but due to urgent needs or lack of discipline, it is spent on other things. The sender wants control over the allocation of capital. The Solution: Aggregation: The platform integrates with utility and education providers in the destination country. Direct Payment: The sender in the US pays USDC in the app. Settlement: Arc settles the transaction in the background, converting via CPN to local fiat and paying the electric company directly. Certainty: The sender receives an instant digital receipt: "Bill Paid." Why Arc? It acts as a global settlement layer that bypasses the slow, opaque correspondent banking chain. The Builder Profile: Cross-border payment startups and Digital Nomad service providers. 3. The Technical Blueprint In this track, User Experience (UX) is survival. Your users have low-end devices and spotty internet. Step 1: The Invisible Wallet. Use Circle User-Controlled Wallets with PIN or Biometric recovery. If you ask a user to write down 12 words, you have already lost. Step 2: Gas Sponsorship. You must configure a Gas Station . The user should know they received "10 Dollars," not that they need "Arc Token" for gas. Abstract the blockchain away completely. Step 3: The Lite Stack. Build Progressive Web Apps (PWAs) or Telegram Mini Apps. The binary must be small; the interface must be fast. Step 4: Offline Tolerance. Design for latency. Allow users to sign transactions offline and broadcast them when the network reconnects. 4. The Conclusion "Technology has no conscience, but builders do." On Wall Street, being 1 millisecond faster might mean an extra million dollars in profit. But in the developing world, saving $1 in fees and moving money instantly means a family eats dinner tonight. This track is about using code to eliminate the "Poverty Premium." By leveraging the power of Arc and Circle, you are building a ladder to economic freedom. The Conclusion The Time to Build is Now History doesn't repeat but it rhymes. In the late 90s, we laid fiber optic cables that allowed the internet to scale. In the 2000s, Stripe and PayPal built the logic layer that enabled e-commerce to explode. Today, we're at a similar inflection point for the financial internet. The opportunities outlined above - Borderless Payment Rails, Programmable FX, The Machine Economy, and Financial Inclusion - are not theoretical science projects. They are immediate, addressable markets worth trillions of dollars. The legacy banking system's friction - 3-day settlement times, predatory remittance fees, walled gardens - is an anomaly that technology is now correcting. Circle and Arc have provided the "AWS" for this financial revolution : scalable, compliant, and ready for deployment. Infrastructure risk has been removed. What remains is execution risk. We are looking for founders who aren't interested in launching the next meme coin, but who are obsessed with unbundling the bank, rewiring global trade, and giving AI agents their own economic sovereignty. The Economic OS is open. The API is live. It's time to build. About DoraHacks DoraHacks is the leading global hackathon community and open source developer incentive platform. DoraHacks provides toolkits for anyone to organize hackathons and fund early-stage ecosystem startups. DoraHacks creates a global hacker movement in Web3, AI, Quantum Computing and Space Tech. So far, more than 30,000 startup teams from the DoraHacks community have received over $300M in funding, and a large number of open source communities, companies and tech ecosystems are actively using DoraHacks together with its BUIDL AI capabilities for organizing hackathons and funding open source initiatives. Website ｜ Twitter ｜ Discord ｜ Telegram ｜ Binance Live ｜ Youtube Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse DoraHacks Follow Contribute to crypto/web3, AI, quantum computing, space and other frontier technologies through hackathons with DoraHacks. https://dorahacks.io/ Joined Nov 26, 2025 More from DoraHacks DoraHacks Must-attend Hackathons 2025 December # hackathon # web3 # blockchain 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://docs.python.org/3/tutorial/controlflow.html#positional-or-keyword-arguments | 4. More Control Flow Tools — Python 3.14.2 documentation Theme Auto Light Dark Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | Theme Auto Light Dark | 4. More Control Flow Tools ¶ As well as the while statement just introduced, Python uses a few more that we will encounter in this chapter. 4.1. if Statements ¶ Perhaps the most well-known statement type is the if statement. For example: >>> x = int ( input ( "Please enter an integer: " )) Please enter an integer: 42 >>> if x < 0 : ... x = 0 ... print ( 'Negative changed to zero' ) ... elif x == 0 : ... print ( 'Zero' ) ... elif x == 1 : ... print ( 'Single' ) ... else : ... print ( 'More' ) ... More There can be zero or more elif parts, and the else part is optional. The keyword ‘ elif ’ is short for ‘else if’, and is useful to avoid excessive indentation. An if … elif … elif … sequence is a substitute for the switch or case statements found in other languages. If you’re comparing the same value to several constants, or checking for specific types or attributes, you may also find the match statement useful. For more details see match Statements . 4.2. for Statements ¶ The for statement in Python differs a bit from what you may be used to in C or Pascal. Rather than always iterating over an arithmetic progression of numbers (like in Pascal), or giving the user the ability to define both the iteration step and halting condition (as C), Python’s for statement iterates over the items of any sequence (a list or a string), in the order that they appear in the sequence. For example (no pun intended): >>> # Measure some strings: >>> words = [ 'cat' , 'window' , 'defenestrate' ] >>> for w in words : ... print ( w , len ( w )) ... cat 3 window 6 defenestrate 12 Code that modifies a collection while iterating over that same collection can be tricky to get right. Instead, it is usually more straight-forward to loop over a copy of the collection or to create a new collection: # Create a sample collection users = { 'Hans' : 'active' , 'Éléonore' : 'inactive' , '景太郎' : 'active' } # Strategy: Iterate over a copy for user , status in users . copy () . items (): if status == 'inactive' : del users [ user ] # Strategy: Create a new collection active_users = {} for user , status in users . items (): if status == 'active' : active_users [ user ] = status 4.3. The range() Function ¶ If you do need to iterate over a sequence of numbers, the built-in function range() comes in handy. It generates arithmetic progressions: >>> for i in range ( 5 ): ... print ( i ) ... 0 1 2 3 4 The given end point is never part of the generated sequence; range(10) generates 10 values, the legal indices for items of a sequence of length 10. It is possible to let the range start at another number, or to specify a different increment (even negative; sometimes this is called the ‘step’): >>> list ( range ( 5 , 10 )) [5, 6, 7, 8, 9] >>> list ( range ( 0 , 10 , 3 )) [0, 3, 6, 9] >>> list ( range ( - 10 , - 100 , - 30 )) [-10, -40, -70] To iterate over the indices of a sequence, you can combine range() and len() as follows: >>> a = [ 'Mary' , 'had' , 'a' , 'little' , 'lamb' ] >>> for i in range ( len ( a )): ... print ( i , a [ i ]) ... 0 Mary 1 had 2 a 3 little 4 lamb In most such cases, however, it is convenient to use the enumerate() function, see Looping Techniques . A strange thing happens if you just print a range: >>> range ( 10 ) range(0, 10) In many ways the object returned by range() behaves as if it is a list, but in fact it isn’t. It is an object which returns the successive items of the desired sequence when you iterate over it, but it doesn’t really make the list, thus saving space. We say such an object is iterable , that is, suitable as a target for functions and constructs that expect something from which they can obtain successive items until the supply is exhausted. We have seen that the for statement is such a construct, while an example of a function that takes an iterable is sum() : >>> sum ( range ( 4 )) # 0 + 1 + 2 + 3 6 Later we will see more functions that return iterables and take iterables as arguments. In chapter Data Structures , we will discuss in more detail about list() . 4.4. break and continue Statements ¶ The break statement breaks out of the innermost enclosing for or while loop: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( f " { n } equals { x } * { n // x } " ) ... break ... 4 equals 2 * 2 6 equals 2 * 3 8 equals 2 * 4 9 equals 3 * 3 The continue statement continues with the next iteration of the loop: >>> for num in range ( 2 , 10 ): ... if num % 2 == 0 : ... print ( f "Found an even number { num } " ) ... continue ... print ( f "Found an odd number { num } " ) ... Found an even number 2 Found an odd number 3 Found an even number 4 Found an odd number 5 Found an even number 6 Found an odd number 7 Found an even number 8 Found an odd number 9 4.5. else Clauses on Loops ¶ In a for or while loop the break statement may be paired with an else clause. If the loop finishes without executing the break , the else clause executes. In a for loop, the else clause is executed after the loop finishes its final iteration, that is, if no break occurred. In a while loop, it’s executed after the loop’s condition becomes false. In either kind of loop, the else clause is not executed if the loop was terminated by a break . Of course, other ways of ending the loop early, such as a return or a raised exception, will also skip execution of the else clause. This is exemplified in the following for loop, which searches for prime numbers: >>> for n in range ( 2 , 10 ): ... for x in range ( 2 , n ): ... if n % x == 0 : ... print ( n , 'equals' , x , '*' , n // x ) ... break ... else : ... # loop fell through without finding a factor ... print ( n , 'is a prime number' ) ... 2 is a prime number 3 is a prime number 4 equals 2 * 2 5 is a prime number 6 equals 2 * 3 7 is a prime number 8 equals 2 * 4 9 equals 3 * 3 (Yes, this is the correct code. Look closely: the else clause belongs to the for loop, not the if statement.) One way to think of the else clause is to imagine it paired with the if inside the loop. As the loop executes, it will run a sequence like if/if/if/else. The if is inside the loop, encountered a number of times. If the condition is ever true, a break will happen. If the condition is never true, the else clause outside the loop will execute. When used with a loop, the else clause has more in common with the else clause of a try statement than it does with that of if statements: a try statement’s else clause runs when no exception occurs, and a loop’s else clause runs when no break occurs. For more on the try statement and exceptions, see Handling Exceptions . 4.6. pass Statements ¶ The pass statement does nothing. It can be used when a statement is required syntactically but the program requires no action. For example: >>> while True : ... pass # Busy-wait for keyboard interrupt (Ctrl+C) ... This is commonly used for creating minimal classes: >>> class MyEmptyClass : ... pass ... Another place pass can be used is as a place-holder for a function or conditional body when you are working on new code, allowing you to keep thinking at a more abstract level. The pass is silently ignored: >>> def initlog ( * args ): ... pass # Remember to implement this! ... For this last case, many people use the ellipsis literal ... instead of pass . This use has no special meaning to Python, and is not part of the language definition (you could use any constant expression here), but ... is used conventionally as a placeholder body as well. See The Ellipsis Object . 4.7. match Statements ¶ A match statement takes an expression and compares its value to successive patterns given as one or more case blocks. This is superficially similar to a switch statement in C, Java or JavaScript (and many other languages), but it’s more similar to pattern matching in languages like Rust or Haskell. Only the first pattern that matches gets executed and it can also extract components (sequence elements or object attributes) from the value into variables. If no case matches, none of the branches is executed. The simplest form compares a subject value against one or more literals: def http_error ( status ): match status : case 400 : return "Bad request" case 404 : return "Not found" case 418 : return "I'm a teapot" case _ : return "Something's wrong with the internet" Note the last block: the “variable name” _ acts as a wildcard and never fails to match. You can combine several literals in a single pattern using | (“or”): case 401 | 403 | 404 : return "Not allowed" Patterns can look like unpacking assignments, and can be used to bind variables: # point is an (x, y) tuple match point : case ( 0 , 0 ): print ( "Origin" ) case ( 0 , y ): print ( f "Y= { y } " ) case ( x , 0 ): print ( f "X= { x } " ) case ( x , y ): print ( f "X= { x } , Y= { y } " ) case _ : raise ValueError ( "Not a point" ) Study that one carefully! The first pattern has two literals, and can be thought of as an extension of the literal pattern shown above. But the next two patterns combine a literal and a variable, and the variable binds a value from the subject ( point ). The fourth pattern captures two values, which makes it conceptually similar to the unpacking assignment (x, y) = point . If you are using classes to structure your data you can use the class name followed by an argument list resembling a constructor, but with the ability to capture attributes into variables: class Point : def __init__ ( self , x , y ): self . x = x self . y = y def where_is ( point ): match point : case Point ( x = 0 , y = 0 ): print ( "Origin" ) case Point ( x = 0 , y = y ): print ( f "Y= { y } " ) case Point ( x = x , y = 0 ): print ( f "X= { x } " ) case Point (): print ( "Somewhere else" ) case _ : print ( "Not a point" ) You can use positional parameters with some builtin classes that provide an ordering for their attributes (e.g. dataclasses). You can also define a specific position for attributes in patterns by setting the __match_args__ special attribute in your classes. If it’s set to (“x”, “y”), the following patterns are all equivalent (and all bind the y attribute to the var variable): Point ( 1 , var ) Point ( 1 , y = var ) Point ( x = 1 , y = var ) Point ( y = var , x = 1 ) A recommended way to read patterns is to look at them as an extended form of what you would put on the left of an assignment, to understand which variables would be set to what. Only the standalone names (like var above) are assigned to by a match statement. Dotted names (like foo.bar ), attribute names (the x= and y= above) or class names (recognized by the “(…)” next to them like Point above) are never assigned to. Patterns can be arbitrarily nested. For example, if we have a short list of Points, with __match_args__ added, we could match it like this: class Point : __match_args__ = ( 'x' , 'y' ) def __init__ ( self , x , y ): self . x = x self . y = y match points : case []: print ( "No points" ) case [ Point ( 0 , 0 )]: print ( "The origin" ) case [ Point ( x , y )]: print ( f "Single point { x } , { y } " ) case [ Point ( 0 , y1 ), Point ( 0 , y2 )]: print ( f "Two on the Y axis at { y1 } , { y2 } " ) case _ : print ( "Something else" ) We can add an if clause to a pattern, known as a “guard”. If the guard is false, match goes on to try the next case block. Note that value capture happens before the guard is evaluated: match point : case Point ( x , y ) if x == y : print ( f "Y=X at { x } " ) case Point ( x , y ): print ( f "Not on the diagonal" ) Several other key features of this statement: Like unpacking assignments, tuple and list patterns have exactly the same meaning and actually match arbitrary sequences. An important exception is that they don’t match iterators or strings. Sequence patterns support extended unpacking: [x, y, *rest] and (x, y, *rest) work similar to unpacking assignments. The name after * may also be _ , so (x, y, *_) matches a sequence of at least two items without binding the remaining items. Mapping patterns: {"bandwidth": b, "latency": l} captures the "bandwidth" and "latency" values from a dictionary. Unlike sequence patterns, extra keys are ignored. An unpacking like **rest is also supported. (But **_ would be redundant, so it is not allowed.) Subpatterns may be captured using the as keyword: case ( Point ( x1 , y1 ), Point ( x2 , y2 ) as p2 ): ... will capture the second element of the input as p2 (as long as the input is a sequence of two points) Most literals are compared by equality, however the singletons True , False and None are compared by identity. Patterns may use named constants. These must be dotted names to prevent them from being interpreted as capture variable: from enum import Enum class Color ( Enum ): RED = 'red' GREEN = 'green' BLUE = 'blue' color = Color ( input ( "Enter your choice of 'red', 'blue' or 'green': " )) match color : case Color . RED : print ( "I see red!" ) case Color . GREEN : print ( "Grass is green" ) case Color . BLUE : print ( "I'm feeling the blues :(" ) For a more detailed explanation and additional examples, you can look into PEP 636 which is written in a tutorial format. 4.8. Defining Functions ¶ We can create a function that writes the Fibonacci series to an arbitrary boundary: >>> def fib ( n ): # write Fibonacci series less than n ... """Print a Fibonacci series less than n.""" ... a , b = 0 , 1 ... while a < n : ... print ( a , end = ' ' ) ... a , b = b , a + b ... print () ... >>> # Now call the function we just defined: >>> fib ( 2000 ) 0 1 1 2 3 5 8 13 21 34 55 89 144 233 377 610 987 1597 The keyword def introduces a function definition . It must be followed by the function name and the parenthesized list of formal parameters. The statements that form the body of the function start at the next line, and must be indented. The first statement of the function body can optionally be a string literal; this string literal is the function’s documentation string, or docstring . (More about docstrings can be found in the section Documentation Strings .) There are tools which use docstrings to automatically produce online or printed documentation, or to let the user interactively browse through code; it’s good practice to include docstrings in code that you write, so make a habit of it. The execution of a function introduces a new symbol table used for the local variables of the function. More precisely, all variable assignments in a function store the value in the local symbol table; whereas variable references first look in the local symbol table, then in the local symbol tables of enclosing functions, then in the global symbol table, and finally in the table of built-in names. Thus, global variables and variables of enclosing functions cannot be directly assigned a value within a function (unless, for global variables, named in a global statement, or, for variables of enclosing functions, named in a nonlocal statement), although they may be referenced. The actual parameters (arguments) to a function call are introduced in the local symbol table of the called function when it is called; thus, arguments are passed using call by value (where the value is always an object reference , not the value of the object). [ 1 ] When a function calls another function, or calls itself recursively, a new local symbol table is created for that call. A function definition associates the function name with the function object in the current symbol table. The interpreter recognizes the object pointed to by that name as a user-defined function. Other names can also point to that same function object and can also be used to access the function: >>> fib <function fib at 10042ed0> >>> f = fib >>> f ( 100 ) 0 1 1 2 3 5 8 13 21 34 55 89 Coming from other languages, you might object that fib is not a function but a procedure since it doesn’t return a value. In fact, even functions without a return statement do return a value, albeit a rather boring one. This value is called None (it’s a built-in name). Writing the value None is normally suppressed by the interpreter if it would be the only value written. You can see it if you really want to using print() : >>> fib ( 0 ) >>> print ( fib ( 0 )) None It is simple to write a function that returns a list of the numbers of the Fibonacci series, instead of printing it: >>> def fib2 ( n ): # return Fibonacci series up to n ... """Return a list containing the Fibonacci series up to n.""" ... result = [] ... a , b = 0 , 1 ... while a < n : ... result . append ( a ) # see below ... a , b = b , a + b ... return result ... >>> f100 = fib2 ( 100 ) # call it >>> f100 # write the result [0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89] This example, as usual, demonstrates some new Python features: The return statement returns with a value from a function. return without an expression argument returns None . Falling off the end of a function also returns None . The statement result.append(a) calls a method of the list object result . A method is a function that ‘belongs’ to an object and is named obj.methodname , where obj is some object (this may be an expression), and methodname is the name of a method that is defined by the object’s type. Different types define different methods. Methods of different types may have the same name without causing ambiguity. (It is possible to define your own object types and methods, using classes , see Classes ) The method append() shown in the example is defined for list objects; it adds a new element at the end of the list. In this example it is equivalent to result = result + [a] , but more efficient. 4.9. More on Defining Functions ¶ It is also possible to define functions with a variable number of arguments. There are three forms, which can be combined. 4.9.1. Default Argument Values ¶ The most useful form is to specify a default value for one or more arguments. This creates a function that can be called with fewer arguments than it is defined to allow. For example: def ask_ok ( prompt , retries = 4 , reminder = 'Please try again!' ): while True : reply = input ( prompt ) if reply in { 'y' , 'ye' , 'yes' }: return True if reply in { 'n' , 'no' , 'nop' , 'nope' }: return False retries = retries - 1 if retries < 0 : raise ValueError ( 'invalid user response' ) print ( reminder ) This function can be called in several ways: giving only the mandatory argument: ask_ok('Do you really want to quit?') giving one of the optional arguments: ask_ok('OK to overwrite the file?', 2) or even giving all arguments: ask_ok('OK to overwrite the file?', 2, 'Come on, only yes or no!') This example also introduces the in keyword. This tests whether or not a sequence contains a certain value. The default values are evaluated at the point of function definition in the defining scope, so that i = 5 def f ( arg = i ): print ( arg ) i = 6 f () will print 5 . Important warning: The default value is evaluated only once. This makes a difference when the default is a mutable object such as a list, dictionary, or instances of most classes. For example, the following function accumulates the arguments passed to it on subsequent calls: def f ( a , L = []): L . append ( a ) return L print ( f ( 1 )) print ( f ( 2 )) print ( f ( 3 )) This will print [ 1 ] [ 1 , 2 ] [ 1 , 2 , 3 ] If you don’t want the default to be shared between subsequent calls, you can write the function like this instead: def f ( a , L = None ): if L is None : L = [] L . append ( a ) return L 4.9.2. Keyword Arguments ¶ Functions can also be called using keyword arguments of the form kwarg=value . For instance, the following function: def parrot ( voltage , state = 'a stiff' , action = 'voom' , type = 'Norwegian Blue' ): print ( "-- This parrot wouldn't" , action , end = ' ' ) print ( "if you put" , voltage , "volts through it." ) print ( "-- Lovely plumage, the" , type ) print ( "-- It's" , state , "!" ) accepts one required argument ( voltage ) and three optional arguments ( state , action , and type ). This function can be called in any of the following ways: parrot ( 1000 ) # 1 positional argument parrot ( voltage = 1000 ) # 1 keyword argument parrot ( voltage = 1000000 , action = 'VOOOOOM' ) # 2 keyword arguments parrot ( action = 'VOOOOOM' , voltage = 1000000 ) # 2 keyword arguments parrot ( 'a million' , 'bereft of life' , 'jump' ) # 3 positional arguments parrot ( 'a thousand' , state = 'pushing up the daisies' ) # 1 positional, 1 keyword but all the following calls would be invalid: parrot () # required argument missing parrot ( voltage = 5.0 , 'dead' ) # non-keyword argument after a keyword argument parrot ( 110 , voltage = 220 ) # duplicate value for the same argument parrot ( actor = 'John Cleese' ) # unknown keyword argument In a function call, keyword arguments must follow positional arguments. All the keyword arguments passed must match one of the arguments accepted by the function (e.g. actor is not a valid argument for the parrot function), and their order is not important. This also includes non-optional arguments (e.g. parrot(voltage=1000) is valid too). No argument may receive a value more than once. Here’s an example that fails due to this restriction: >>> def function ( a ): ... pass ... >>> function ( 0 , a = 0 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : function() got multiple values for argument 'a' When a final formal parameter of the form **name is present, it receives a dictionary (see Mapping Types — dict ) containing all keyword arguments except for those corresponding to a formal parameter. This may be combined with a formal parameter of the form *name (described in the next subsection) which receives a tuple containing the positional arguments beyond the formal parameter list. ( *name must occur before **name .) For example, if we define a function like this: def cheeseshop ( kind , * arguments , ** keywords ): print ( "-- Do you have any" , kind , "?" ) print ( "-- I'm sorry, we're all out of" , kind ) for arg in arguments : print ( arg ) print ( "-" * 40 ) for kw in keywords : print ( kw , ":" , keywords [ kw ]) It could be called like this: cheeseshop ( "Limburger" , "It's very runny, sir." , "It's really very, VERY runny, sir." , shopkeeper = "Michael Palin" , client = "John Cleese" , sketch = "Cheese Shop Sketch" ) and of course it would print: -- Do you have any Limburger ? -- I'm sorry, we're all out of Limburger It's very runny, sir. It's really very, VERY runny, sir. ---------------------------------------- shopkeeper : Michael Palin client : John Cleese sketch : Cheese Shop Sketch Note that the order in which the keyword arguments are printed is guaranteed to match the order in which they were provided in the function call. 4.9.3. Special parameters ¶ By default, arguments may be passed to a Python function either by position or explicitly by keyword. For readability and performance, it makes sense to restrict the way arguments can be passed so that a developer need only look at the function definition to determine if items are passed by position, by position or keyword, or by keyword. A function definition may look like: def f(pos1, pos2, /, pos_or_kwd, *, kwd1, kwd2): ----------- ---------- ---------- | | | | Positional or keyword | | - Keyword only -- Positional only where / and * are optional. If used, these symbols indicate the kind of parameter by how the arguments may be passed to the function: positional-only, positional-or-keyword, and keyword-only. Keyword parameters are also referred to as named parameters. 4.9.3.1. Positional-or-Keyword Arguments ¶ If / and * are not present in the function definition, arguments may be passed to a function by position or by keyword. 4.9.3.2. Positional-Only Parameters ¶ Looking at this in a bit more detail, it is possible to mark certain parameters as positional-only . If positional-only , the parameters’ order matters, and the parameters cannot be passed by keyword. Positional-only parameters are placed before a / (forward-slash). The / is used to logically separate the positional-only parameters from the rest of the parameters. If there is no / in the function definition, there are no positional-only parameters. Parameters following the / may be positional-or-keyword or keyword-only . 4.9.3.3. Keyword-Only Arguments ¶ To mark parameters as keyword-only , indicating the parameters must be passed by keyword argument, place an * in the arguments list just before the first keyword-only parameter. 4.9.3.4. Function Examples ¶ Consider the following example function definitions paying close attention to the markers / and * : >>> def standard_arg ( arg ): ... print ( arg ) ... >>> def pos_only_arg ( arg , / ): ... print ( arg ) ... >>> def kwd_only_arg ( * , arg ): ... print ( arg ) ... >>> def combined_example ( pos_only , / , standard , * , kwd_only ): ... print ( pos_only , standard , kwd_only ) The first function definition, standard_arg , the most familiar form, places no restrictions on the calling convention and arguments may be passed by position or keyword: >>> standard_arg ( 2 ) 2 >>> standard_arg ( arg = 2 ) 2 The second function pos_only_arg is restricted to only use positional parameters as there is a / in the function definition: >>> pos_only_arg ( 1 ) 1 >>> pos_only_arg ( arg = 1 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : pos_only_arg() got some positional-only arguments passed as keyword arguments: 'arg' The third function kwd_only_arg only allows keyword arguments as indicated by a * in the function definition: >>> kwd_only_arg ( 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : kwd_only_arg() takes 0 positional arguments but 1 was given >>> kwd_only_arg ( arg = 3 ) 3 And the last uses all three calling conventions in the same function definition: >>> combined_example ( 1 , 2 , 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() takes 2 positional arguments but 3 were given >>> combined_example ( 1 , 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( 1 , standard = 2 , kwd_only = 3 ) 1 2 3 >>> combined_example ( pos_only = 1 , standard = 2 , kwd_only = 3 ) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : combined_example() got some positional-only arguments passed as keyword arguments: 'pos_only' Finally, consider this function definition which has a potential collision between the positional argument name and **kwds which has name as a key: def foo ( name , ** kwds ): return 'name' in kwds There is no possible call that will make it return True as the keyword 'name' will always bind to the first parameter. For example: >>> foo ( 1 , ** { 'name' : 2 }) Traceback (most recent call last): File "<stdin>" , line 1 , in <module> TypeError : foo() got multiple values for argument 'name' >>> But using / (positional only arguments), it is possible since it allows name as a positional argument and 'name' as a key in the keyword arguments: >>> def foo ( name , / , ** kwds ): ... return 'name' in kwds ... >>> foo ( 1 , ** { 'name' : 2 }) True In other words, the names of positional-only parameters can be used in **kwds without ambiguity. 4.9.3.5. Recap ¶ The use case will determine which parameters to use in the function definition: def f ( pos1 , pos2 , / , pos_or_kwd , * , kwd1 , kwd2 ): As guidance: Use positional-only if you want the name of the parameters to not be available to the user. This is useful when parameter names have no real meaning, if you want to enforce the order of the arguments when the function is called or if you need to take some positional parameters and arbitrary keywords. Use keyword-only when names have meaning and the function definition is more understandable by being explicit with names or you want to prevent users relying on the position of the argument being passed. For an API, use positional-only to prevent breaking API changes if the parameter’s name is modified in the future. 4.9.4. Arbitrary Argument Lists ¶ Finally, the least frequently used option is to specify that a function can be called with an arbitrary number of arguments. These arguments will be wrapped up in a tuple (see Tuples and Sequences ). Before the variable number of arguments, zero or more normal arguments may occur. def write_multiple_items ( file , separator , * args ): file . write ( separator . join ( args )) Normally, these variadic arguments will be last in the list of formal parameters, because they scoop up all remaining input arguments that are passed to the function. Any formal parameters which occur after the *args parameter are ‘keyword-only’ arguments, meaning that they can only be used as keywords rather than positional arguments. >>> def concat ( * args , sep = "/" ): ... return sep . join ( args ) ... >>> concat ( "earth" , "mars" , "venus" ) 'earth/mars/venus' >>> concat ( "earth" , "mars" , "venus" , sep = "." ) 'earth.mars.venus' 4.9.5. Unpacking Argument Lists ¶ The reverse situation occurs when the arguments are already in a list or tuple but need to be unpacked for a function call requiring separate positional arguments. For instance, the built-in range() function expects separate start and stop arguments. If they are not available separately, write the function call with the * -operator to unpack the arguments out of a list or tuple: >>> list ( range ( 3 , 6 )) # normal call with separate arguments [3, 4, 5] >>> args = [ 3 , 6 ] >>> list ( range ( * args )) # call with arguments unpacked from a list [3, 4, 5] In the same fashion, dictionaries can deliver keyword arguments with the ** -operator: >>> def parrot ( voltage , state = 'a stiff' , action = 'voom' ): ... print ( "-- This parrot wouldn't" , action , end = ' ' ) ... print ( "if you put" , voltage , "volts through it." , end = ' ' ) ... print ( "E's" , state , "!" ) ... >>> d = { "voltage" : "four million" , "state" : "bleedin' demised" , "action" : "VOOM" } >>> parrot ( ** d ) -- This parrot wouldn't VOOM if you put four million volts through it. E's bleedin' demised ! 4.9.6. Lambda Expressions ¶ Small anonymous functions can be created with the lambda keyword. This function returns the sum of its two arguments: lambda a, b: a+b . Lambda functions can be used wherever function objects are required. They are syntactically restricted to a single expression. Semantically, they are just syntactic sugar for a normal function definition. Like nested function definitions, lambda functions can reference variables from the containing scope: >>> def make_incrementor ( n ): ... return lambda x : x + n ... >>> f = make_incrementor ( 42 ) >>> f ( 0 ) 42 >>> f ( 1 ) 43 The above example uses a lambda expression to return a function. Another use is to pass a small function as an argument. For instance, list.sort() takes a sorting key function key which can be a lambda function: >>> pairs = [( 1 , 'one' ), ( 2 , 'two' ), ( 3 , 'three' ), ( 4 , 'four' )] >>> pairs . sort ( key = lambda pair : pair [ 1 ]) >>> pairs [(4, 'four'), (1, 'one'), (3, 'three'), (2, 'two')] 4.9.7. Documentation Strings ¶ Here are some conventions about the content and formatting of documentation strings. The first line should always be a short, concise summary of the object’s purpose. For brevity, it should not explicitly state the object’s name or type, since these are available by other means (except if the name happens to be a verb describing a function’s operation). This line should begin with a capital letter and end with a period. If there are more lines in the documentation string, the second line should be blank, visually separating the summary from the rest of the description. The following lines should be one or more paragraphs describing the object’s calling conventions, its side effects, etc. The Python parser strips indentation from multi-line string literals when they serve as module, class, or function docstrings. Here is an example of a multi-line docstring: >>> def my_function (): ... """Do nothing, but document it. ... ... No, really, it doesn't do anything: ... ... >>> my_function() ... >>> ... """ ... pass ... >>> print ( my_function . __doc__ ) Do nothing, but document it. No, really, it doesn't do anything: >>> my_function() >>> 4.9.8. Function Annotations ¶ Function annotations are completely optional metadata information about the types used by user-defined functions (see PEP 3107 and PEP 484 for more information). Annotations are stored in the __annotations__ attribute of the function as a dictionary and have no effect on any other part of the function. Parameter annotations are defined by a colon after the parameter name, followed by an expression evaluating to the value of the annotation. Return annotations are defined by a literal -> , followed by an expression, between the parameter list and the colon denoting the end of the def statement. The following example has a required argument, an optional argument, and the return value annotated: >>> def f ( ham : str , eggs : str = 'eggs' ) -> str : ... print ( "Annotations:" , f . __annotations__ ) ... print ( "Arguments:" , ham , eggs ) ... return ham + ' and ' + eggs ... >>> f ( 'spam' ) Annotations: {'ham': <class 'str'>, 'return': <class 'str'>, 'eggs': <class 'str'>} Arguments: spam eggs 'spam and eggs' 4.10. Intermezzo: Coding Style ¶ Now that you are about to write longer, more complex pieces of Python, it is a good time to talk about coding style . Most languages can be written (or more concise, formatted ) in different styles; some are more readable than others. Making it easy for others to read your code is always a good idea, and adopting a nice coding style helps tremendously for that. For Python, PEP 8 has emerged as the style guide that most projects adhere to; it promotes a very readable and eye-pleasing coding style. Every Python developer should read it at some point; here are the most important points extracted for you: Use 4-space indentation, and no tabs. 4 spaces are a good compromise between small indentation (allows greater nesting depth) and large indentation (easier to read). Tabs introduce confusion, and are best left out. Wrap lines so that they don’t exceed 79 characters. This helps users with small displays and makes it possible to have several code files side-by-side on larger displays. Use blank lines to separate functions and classes, and larger blocks of code inside functions. When possible, put comments on a line of their own. Use docstrings. Use spaces around operators and after commas, but not directly inside bracketing constructs: a = f(1, 2) + g(3, 4) . Name your classes and functions consistently; the convention is to use UpperCamelCase for classes and lowercase_with_underscores for functions and methods. Always use self as the name for the first method argument (see A First Look at Classes for more on classes and methods). Don’t use fancy encodings if your code is meant to be used in international environments. Python’s default, UTF-8, or even plain ASCII work best in any case. Likewise, don’t use non-ASCII characters in identifiers if there is only the slightest chance people speaking a different language will read or maintain the code. Footnotes [ 1 ] Actually, call by object reference would be a better description, since if a mutable object is passed, the caller will see any changes the callee makes to it (items inserted into a list). Table of Contents 4. More Control Flow Tools 4.1. if Statements 4.2. for Statements 4.3. The range() Function 4.4. break and continue Statements 4.5. else Clauses on Loops 4.6. pass Statements 4.7. match Statements 4.8. Defining Functions 4.9. More on Defining Functions 4.9.1. Default Argument Values 4.9.2. Keyword Arguments 4.9.3. Special parameters 4.9.3.1. Positional-or-Keyword Arguments 4.9.3.2. Positional-Only Parameters 4.9.3.3. Keyword-Only Arguments 4.9.3.4. Function Examples 4.9.3.5. Recap 4.9.4. Arbitrary Argument Lists 4.9.5. Unpacking Argument Lists 4.9.6. Lambda Expressions 4.9.7. Documentation Strings 4.9.8. Function Annotations 4.10. Intermezzo: Coding Style Previous topic 3. An Informal Introduction to Python Next topic 5. Data Structures This page Report a bug Show source « Navigation index modules | next | previous | Python » 3.14.2 Documentation » The Python Tutorial » 4. More Control Flow Tools | Theme Auto Light Dark | © Copyright 2001 Python Software Foundation. This page is licensed under the Python Software Foundation License Version 2. Examples, recipes, and other code in the documentation are additionally licensed under the Zero Clause BSD License. See History and License for more information. The Python Software Foundation is a non-profit corporation. Please donate. Last updated on Jan 13, 2026 (06:19 UTC). Found a bug ? Created using Sphinx 8.2.3. | 2026-01-13T08:49:06 |
https://dev.to/t/programming/page/3#main-content | Programming Page 3 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Programming Follow Hide The magic behind computers. 💻 🪄 Create Post Older #programming posts 1 2 3 4 5 6 7 8 9 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Getting Started with Fortune Sheet in React: Building Your First Spreadsheet Michael Turner Michael Turner Michael Turner Follow Jan 12 Getting Started with Fortune Sheet in React: Building Your First Spreadsheet # react # webdev # programming # tutorial Comments Add Comment 5 min read Admin-Only Dashboard Rule of Thumb Sospeter Mong'are Sospeter Mong'are Sospeter Mong'are Follow Jan 12 Admin-Only Dashboard Rule of Thumb # programming # beginners # datascience # database 1 reaction Comments 2 comments 3 min read Why Your Python Code Takes Hours Instead of Seconds (A 3-Line Fix) Samuel Ochaba Samuel Ochaba Samuel Ochaba Follow Jan 12 Why Your Python Code Takes Hours Instead of Seconds (A 3-Line Fix) # python # performance # beginners # programming Comments Add Comment 2 min read Understanding custom auth flow and its implementation.. Sourav Mahato Sourav Mahato Sourav Mahato Follow Jan 12 Understanding custom auth flow and its implementation.. # webdev # programming # zod # authentication Comments Add Comment 1 min read Notifications Are Not Just Messages. They Are Memory Triggers. Surhid Amatya Surhid Amatya Surhid Amatya Follow Jan 12 Notifications Are Not Just Messages. They Are Memory Triggers. # webdev # programming # productivity Comments Add Comment 3 min read From Rusty to Release: How an Infinite Loop Taught Me to Respect React DevTools Beleke Ian Beleke Ian Beleke Ian Follow Jan 12 From Rusty to Release: How an Infinite Loop Taught Me to Respect React DevTools # react # webdev # beginners # programming 1 reaction Comments Add Comment 2 min read Scrapy Log Files: Save, Rotate, and Organize Your Crawler Logs Muhammad Ikramullah Khan Muhammad Ikramullah Khan Muhammad Ikramullah Khan Follow Jan 12 Scrapy Log Files: Save, Rotate, and Organize Your Crawler Logs # webdev # programming # beginners # python Comments Add Comment 9 min read My first real project : Lemon chat Joseph Pascal Yao Joseph Pascal Yao Joseph Pascal Yao Follow Jan 12 My first real project : Lemon chat # programming # beginners # csharp # opensource Comments Add Comment 1 min read I Thought I Understood Python Functions — Until One Line Returned None Emmimal Alexander Emmimal Alexander Emmimal Alexander Follow Jan 12 I Thought I Understood Python Functions — Until One Line Returned None # python # programming # learning # beginners Comments Add Comment 3 min read From Copilot to Autonomous AI: The Evolution of AI-Assisted Programming Eva Clari Eva Clari Eva Clari Follow Jan 12 From Copilot to Autonomous AI: The Evolution of AI-Assisted Programming # programming # ai # coding # development Comments Add Comment 4 min read Best Python Web Scraping Libraries 2026 Rodrigo Bull Rodrigo Bull Rodrigo Bull Follow Jan 12 Best Python Web Scraping Libraries 2026 # webdev # python # webscraping # programming Comments Add Comment 7 min read Advanced Data Table Implementation with ka-table in React Michael Turner Michael Turner Michael Turner Follow Jan 12 Advanced Data Table Implementation with ka-table in React # react # webdev # programming # javascript Comments Add Comment 6 min read Why Version Control Exists: The Pen Drive Problem Anoop Rajoriya Anoop Rajoriya Anoop Rajoriya Follow Jan 12 Why Version Control Exists: The Pen Drive Problem # git # beginners # webdev # programming Comments Add Comment 3 min read Load Balancing Explained (Simple Guide for Beginners) Mourya Vamsi Modugula Mourya Vamsi Modugula Mourya Vamsi Modugula Follow Jan 12 Load Balancing Explained (Simple Guide for Beginners) # webdev # programming # systemdesign # beginners Comments Add Comment 3 min read What am I doing wrong? Soufiane Amt Soufiane Amt Soufiane Amt Follow Jan 12 What am I doing wrong? # career # webdev # careerdevelopment # programming Comments Add Comment 2 min read Build a Hashtag Research Tool That Finds Hidden Gems Olamide Olaniyan Olamide Olaniyan Olamide Olaniyan Follow Jan 12 Build a Hashtag Research Tool That Finds Hidden Gems # webdev # programming # ai # tutorial Comments Add Comment 9 min read Java Variables Kesavarthini Kesavarthini Kesavarthini Follow Jan 12 Java Variables # java # beginners # learning # programming Comments Add Comment 1 min read DevOps Isn’t a Toolchain, It’s a Feedback Loop Shamim Ali Shamim Ali Shamim Ali Follow Jan 12 DevOps Isn’t a Toolchain, It’s a Feedback Loop # devops # programming # backend # distributedsystems Comments Add Comment 1 min read Here Are the 7 Best Resources to Master Docker Stack Overflowed Stack Overflowed Stack Overflowed Follow Jan 12 Here Are the 7 Best Resources to Master Docker # webdev # programming # docker # containers Comments Add Comment 4 min read Beyond Nested Queries: A Practical Guide to SQL Subquery Flattening SQLFlash SQLFlash SQLFlash Follow Jan 12 Beyond Nested Queries: A Practical Guide to SQL Subquery Flattening # sql # mysql # ai # programming Comments Add Comment 5 min read My Dashboard: как я превратил старые Android-устройства в кроссплатформенные дашборды с помощью AI и типобезопасного fullstack ILshat Khamitov ILshat Khamitov ILshat Khamitov Follow Jan 11 My Dashboard: как я превратил старые Android-устройства в кроссплатформенные дашборды с помощью AI и типобезопасного fullstack # webdev # javascript # programming # ai Comments Add Comment 1 min read Introducing Installerpedia - Install Anything With Zero Hassle Rijul Rajesh Rijul Rajesh Rijul Rajesh Follow Jan 11 Introducing Installerpedia - Install Anything With Zero Hassle # installation # developers # tools # programming 20 reactions Comments Add Comment 9 min read Self-Documenting Code vs. Comments: Lessons from Maintaining Large-Scale Codebases ThankGod Chibugwum Obobo ThankGod Chibugwum Obobo ThankGod Chibugwum Obobo Follow Jan 11 Self-Documenting Code vs. Comments: Lessons from Maintaining Large-Scale Codebases # webdev # softwaredevelopment # programming Comments Add Comment 3 min read Integrating HubSpot with Salesforce using Webhooks for Real-Time Data Synchronization CallStack Tech CallStack Tech CallStack Tech Follow Jan 12 Integrating HubSpot with Salesforce using Webhooks for Real-Time Data Synchronization # api # webdev # tutorial # programming 1 reaction Comments Add Comment 13 min read Getting Started with MUI X Data Grid in React: Building Your First Data Table Michael Turner Michael Turner Michael Turner Follow Jan 12 Getting Started with MUI X Data Grid in React: Building Your First Data Table # webdev # programming # javascript # beginners Comments Add Comment 6 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/alexsergey/css-modules-vs-css-in-js-who-wins-3n25#conclusion | CSS Modules vs CSS-in-JS. Who wins? - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Sergey Posted on Mar 11, 2021 CSS Modules vs CSS-in-JS. Who wins? # webdev # css # javascript # react Introduction In modern React application development, there are many approaches to organizing application styles. One of the popular ways of such an organization is the CSS-in-JS approach (in the article we will use styled-components as the most popular solution) and CSS Modules. In this article, we will try to answer the question: which is better CSS-in-JS or CSS Modules ? So let's get back to basics. When a web page was primarily set for storing textual documentation and didn't include user interactions, properties were introduced to style the content. Over time, the web became more and more popular, sites got bigger, and it became necessary to reuse styles. For these purposes, CSS was invented. Cascading Style Sheets. Cascading plays a very important role in this name. We write styles that lay like a waterfall over the hollows of our document, filling it with colors and highlighting important elements. Time passed, the web became more and more complex, and we are facing the fact that the styles cascade turned into a problem for us. Distributed teams, working on their parts of the system, combining them into reusable modules, assemble an application from pieces, like Dr. Frankenstein, stitching styles into one large canvas, can get the sudden result... Due to the cascade, the styles of module 1 can affect the display of module 3, and module 4 can make changes to the global styles and change the entire display of the application in general. Developers have started to think of solving this problem. Style naming conventions were created to avoid overlaps, such as Yandex's BEM or Atomic CSS. The idea is clear, we operate with names in order to get predictability, but at the same time to prevent repetitions. These approaches were crashed of the rocks of the human factor. Anyway, we have no guarantee that the developer from team A won't use the name from team C. The naming problem can only be solved by assigning a random name to the CSS class. Thus, we get a completely independent CSS set of styles that will be applied to a specific HTML block and we understand for sure that the rest of the system won't be affected in any way. And then 2 approaches came onto the stage to organize our CSS: CSS Modules and CSS-in-JS . Under the hood, having a different technical implementation, and in fact solving the problem of atomicity, reusability, and avoiding side effects when writing CSS. Technically, CSS Modules transforms style names using a hash-based on the filename, path, style name. Styled-components handles styles in JS runtime, adding them as they go to the head HTML section (<head>). Approaches overview Let's see which approach is more optimal for writing a modern web application! Let's imagine we have a basic React application: import React , { Component } from ' react ' ; import ' ./App.css ' ; class App extends Component { render () { return ( < div className = "title" > React application title </ div > ); } } Enter fullscreen mode Exit fullscreen mode CSS styles of this application: .title { padding : 20px ; background-color : #222 ; text-align : center ; color : white ; font-size : 1.5em ; } Enter fullscreen mode Exit fullscreen mode The dependencies are React 16.14 , react-dom 16.14 Let's try to build this application using webpack using all production optimizations. we've got uglified JS - 129kb separated and minified CSS - 133 bytes The same code in CSS Modules will look like this: import React , { Component } from ' react ' ; import styles from ' ./App.module.css ' ; class App extends Component { render () { return ( < div className = { styles . title } > React application title </ div > ); } } Enter fullscreen mode Exit fullscreen mode uglified JS - 129kb separated and minified CSS - 151 bytes The CSS Modules version will take up a couple of bytes more due to the impossibility of compressing the long generated CSS names. Finally, let's rewrite the same code under styled-components: import React , { Component } from ' react ' ; import styles from ' styled-components ' ; const Title = styles . h1 ` padding: 20px; background-color: #222; text-align: center; color: white; font-size: 1.5em; ` ; class App extends Component { render () { return ( < Title > React application title </ Title > ); } } Enter fullscreen mode Exit fullscreen mode uglified JS - 163kb CSS file is missing The more than 30kb difference between CSS Modules and CSS-in-JS (styled-components) is due to styled-components adding extra code to add styles to the <head> part of the HTML document. In this synthetic test, the CSS Modules approach wins, since the build system doesn't add something extra to implement it, except for the changed class name. Styled-components due to technical implementation, adds dependency as well as code for runtime handling and styling of <head>. Now let's take a quick look at the pros and cons of CSS-in-JS / CSS Modules. Pros and cons CSS-in-JS cons The browser won't start interpreting the styles until styled-components has parsed them and added them to the DOM, which slows down rendering. The absence of CSS files means that you cannot cache separate CSS. One of the key downsides is that most libraries don't support this approach and we still can't get rid of CSS. All native JS and jQuery plugins are written without using this approach. Not all React solutions use it. Styles integration problems. When a markup developer prepares a layout for a JS developer, we may forget to transfer something; there will also be difficulty in synchronizing a new version of layout and JS code. We can't use CSS utilities: SCSS, Less, Postcss, stylelint, etc. pros Styles can use JS logic. This reminds me of Expression in IE6, when we could wrap some logic in our styles (Hello, CSS Expressions :) ). const Title = styles . h1 ` padding: 20px; background-color: #222; text-align: center; color: white; font-size: 1.5em; ${ props => props . secondary && css ` background-color: #fff; color: #000; padding: 10px; font-size: 1em; ` } ` ; Enter fullscreen mode Exit fullscreen mode When developing small modules, it simplifies the connection to the project, since you only need to connect the one independent JS file. It is semantically nicer to use <Title> in a React component than <h1 className={style.title}>. CSS Modules cons To describe global styles, you must use a syntax that does not belong to the CSS specification. :global ( .myclass ) { text-decoration : underline ; } Enter fullscreen mode Exit fullscreen mode Integrating into a project, you need to include styles. Working with typescript, you need to automatically or manually generate interfaces. For these purposes, I use webpack loader: @teamsupercell/typings-for-css-modules-loader pros We work with regular CSS, it makes it possible to use SCSS, Less, Postcss, stylelint, and more. Also, you don't waste time on adapting the CSS to JS. No integration of styles into the code, clean code as result. Almost 100% standardized except for global styles. Conclusion So the fundamental problem with the CSS-in-JS approach is that it's not CSS! This kind of code is harder to maintain if you have a defined person in your team working on markup. Such code will be slower, due to the fact that the CSS rendered into the file is processed in parallel, and the CSS-in-JS cannot be rendered into a separate CSS file. And the last fundamental flaw is the inability to use ready-made approaches and utilities, such as SCSS, Less and Stylelint, and so on. On the other hand, the CSS-in-JS approach can be a good solution for the Frontend team who deals with both markup and JS, and develops all components from scratch. Also, CSS-in-JS will be useful for modules that integrate into other applications. In my personal opinion, the issue of CSS cascading is overrated. If we are developing a small application or site, with one team, then we are unlikely to encounter a name collision or the difficulty of reusing components. If you faced with this problem, I recommend considering CSS Modules, as, in my opinion, this is a more optimal solution for the above factors. In any case, whatever you choose, write meaningful code and don't get fooled by the hype. Hype will pass, and we all have to live with it. Have great and interesting projects, dear readers! Top comments (30) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand dastasoft dastasoft dastasoft Follow Senior Software Engineer Work Senior Software Engineer Joined Feb 17, 2020 • Mar 12 '21 Dropdown menu Copy link Hide One pro of CSS, the hot reload is instant when you just change CSS, with CSS in JS the project is recompiled. For CSS-in-JS I find easier to reuse that code in a React Native project. My personal conclusion is that we are constantly trying to avoid CSS but at the end of the day, CSS will stay here forever. Great article btw! Like comment: Like comment: 25 likes Like Comment button Reply Collapse Expand GreggHume GreggHume GreggHume Follow A developer who works with and on some of the worlds leading brands. My company is called Cold Brew Studios, see you out there :) Joined Mar 10, 2021 • Mar 9 '22 • Edited on Mar 9 • Edited Dropdown menu Copy link Hide I ran into issues with css modules that styled components seemed to solve. But i ran into issues with styled components that I wouldn't have had with plain scss. So some things to think about: Styled components is a lot more overhead because all the styled components need to be complied into stylesheets and mounted to the head by javascript which is a blocking language. On SSR styled components get compiled into a ServerStyleSheet that then hydrate the react dom tree in the browser via the context api. So even then the mounting of styles only happens in the browser but the parsing of styles happens on the server - that is still a performance penalty and will slow down the page load. In some cases I had no issues with styled components but as my site grew and in complex cases I couldn't help but feel like it was slower, or didn't load as smoothly... and in a world where every second matters, this was a problem for me. Here is an article doing benchmarks on CSS vs CSS in JS: pustelto.com/blog/css-vs-css-in-js... I use nextjs, it is a pity they do not support component level css and we are forced to use css modules or styled components... where as with Nuxt component level scss is part of the package and you have the option on how you want the sites css to bundled - all in one file, split into their own files and some other nifty options. I hope nextjs sharped up on this. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Nwanguma Victor Nwanguma Victor Nwanguma Victor Follow 🕊 Location Lagos, Nigeria Work Software Developer Joined Feb 18, 2021 • Jun 22 '22 • Edited on Jun 22 • Edited Dropdown menu Copy link Hide A big tip that might help. Why not use SCSS and unique classNames: For example create a unique container className (name of the component) and nest all the other classNames under that unique container className. .home-page-guest { .nav {} .main {} .footer {} } Enter fullscreen mode Exit fullscreen mode < div className = " home-page-guest " > < div className = " nav " /> < div className = " main " /> < div className = " footer " /> < /div > Enter fullscreen mode Exit fullscreen mode Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Cindy Vos Cindy Vos Cindy Vos Follow Tuff shed and light and strong enough Joined Sep 11, 2025 • Sep 15 '25 Dropdown menu Copy link Hide I bet you did Greg Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Hank Queston Hank Queston Hank Queston Follow Work CTO at Bonfire Joined May 25, 2021 • May 25 '21 Dropdown menu Copy link Hide I agreed, CSS Modules make a lot more sense to me over Styled Components, always have! Like comment: Like comment: 7 likes Like Comment button Reply Collapse Expand Comment deleted Collapse Expand Alien Padilla Rodriguez Alien Padilla Rodriguez Alien Padilla Rodriguez Follow Joined Jan 24, 2022 • Apr 23 '22 Dropdown menu Copy link Hide @Petar Kokev If something I learned from this years of working with React and other projects is that the correct library for project isn't the correct library for another. So the mos important think that we need to do is select the tools, libraries and technologies that fit better to the current project. In this case you can't use Styled-components on sites that require a good SEO, becouse the mos important think here is the SEO and you cant sacrify it. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand thedev1232 thedev1232 thedev1232 Follow tech enthusiast - code to the nuts Location sanjose Work Senior dev Manager at self Joined Oct 26, 2020 • Mar 31 '22 Dropdown menu Copy link Hide How about having to deal with libraries like Material UI with next js? I have an issue to decide whether to use just makeStyles function or should we use styled components? My main concern is code longevity and maintenance without any issues Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Will Farley Will Farley Will Farley Follow Joined Jan 24, 2022 • Jan 24 '22 Dropdown menu Copy link Hide My big issues with styled components is they are deeply coupled with your code. I've opted to use emotion's css utility exclusively and instructed my team to avoid using any of the styled component features. We've loved it but this was a few years ago. For newer projects I'm going with the css modules design. Also why does anyone care about sass anymore? With css variables and the css nesting module in the specification, you get the best parts of sass with vanilla css. The other features are just overkill for a css-module that should represent a single react component and thus nothing :global . Complicated sass directives and stuff are just overkill. Turn it into a react component and don't make any crazy css systems. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Nwanguma Victor Nwanguma Victor Nwanguma Victor Follow 🕊 Location Lagos, Nigeria Work Software Developer Joined Feb 18, 2021 • Mar 23 '22 Dropdown menu Copy link Hide Same I was trying to revamp my personal site, I discovered that I would have to rewrite alot of things, and then I later gave up. I would advice css modules are the way to go, and it greatly helps with SEO. And in teams using SC, naming becomes an issue because some people don't know how to name components and you have to scroll around, just to check if a component is a h1 tag 🤮 CACHEing I can't stress this enough, for enterprise in-house apps it doesn't really matter, but for everyday consumer-essentric apps CACHEing should not be overlooked Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Cindy Vos Cindy Vos Cindy Vos Follow Tuff shed and light and strong enough Joined Sep 11, 2025 • Sep 15 '25 Dropdown menu Copy link Hide Matty Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Will Farley Will Farley Will Farley Follow Joined Jan 24, 2022 • Jan 24 '22 Dropdown menu Copy link Hide You can still have a top-level css file that isn't a css module for global stuff Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Petar Kolev Petar Kolev Petar Kolev Follow Senior Software Engineer with React && TypeScript Location Bulgaria Work Senior Software Engineer @ alkem.io Joined Nov 27, 2019 • Sep 10 '21 Dropdown menu Copy link Hide It is not true that with styled-components one can't use scss syntax, etc. styled-components supports it. Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Eduard Eduard Eduard Follow Taxation is robbery Joined Oct 25, 2019 • Mar 28 '21 Dropdown menu Copy link Hide How about css-in-js frameworks like material-ua, chakra-ui and others? In my opinion, they dramatically speed up development. Like comment: Like comment: 5 likes Like Comment button Reply Collapse Expand Alien Padilla Rodriguez Alien Padilla Rodriguez Alien Padilla Rodriguez Follow Joined Jan 24, 2022 • Apr 23 '22 Dropdown menu Copy link Hide In my personal opinion I see Styled Components more for a Single Page Aplications where the SEO isn't important and is unecessary to cache css files. In the case of static web site or a site that must have a good SEO the Module-Css is better. @greggcbs My recomendation is to use code splitting if you have problem with the performans when you use Styled-Components in your project, in order to avoid brign all code in the first load of the site. Good article @sergey Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Cindy Vos Cindy Vos Cindy Vos Follow Tuff shed and light and strong enough Joined Sep 11, 2025 • Sep 15 '25 Dropdown menu Copy link Hide Hi Jess Rodriguez celly Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Gass Gass Gass Follow hi there 👋 Email g.szada@gmail.com Location Budapest, Hungary Education engineering Work software developer @ itemis Joined Dec 25, 2021 • Apr 25 '22 • Edited on Apr 25 • Edited Dropdown menu Copy link Hide Good post. I've been using CSS modules for a short time now and I like it. Allows everything to be nicely compartmentalized. I also like that it gives more freedom to name classes in smaller chunks of CSS code. Instead of using it like so: {styles.my_class} I preffer {s.my_class} makes the code looks nicer and more concise. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Mario Iliev Mario Iliev Mario Iliev Follow Joined Jun 14, 2023 • Jun 14 '23 Dropdown menu Copy link Hide I'm sorry but it seems that you don't have much experience with Styled Components. "And the last fundamental flaw is the inability to use ready-made approaches and utilities, such as SCSS, Less and Stylelint, and so on." Not a single thing here is true. SCSS is the original syntax of the package, you can use Stylelint as well. There are a lot more "pros" which are not listed here. By working with JS you are opened to another world. I'll list some more "pros" from the top of my head: consume and validate your theme colors as pure JS object consume state/props and create dynamic CSS out of it you have plugins which can be a live savers in cases like RTL (right to left orientation). Whoever had to support an app/website with RTL will be magically saved by this plugin. You can create custom plugins to fix various problems, or make your own linting in your team project. you don't think about CSS class names and collision. I prefer to be focused on thinking about variable names in my JS only and not spending effort in the CSS as well when you break your visual habits you will realise that's it's easier to have your CSS in your JS file just the way you got used to have your HTML in your JS file (React) In these days CSS has become a monster. You have inheritance, mixins, variables, IF statements, loops etc. Sure they can be useful somewhere but I'm pretty sure that most of you just need to center that div. So in my personal opinion we should strive to keep CSS as simpler as possible (as with everything actually) and I think that Styled Components are kind of pushing you to do exactly that. Don't re-use CSS, re-use components! The only global things you should have are probably just the color theme and animations. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Annie-Huang Annie-Huang Annie-Huang Follow Joined Mar 14, 2021 • Feb 16 '25 Dropdown menu Copy link Hide Couldn't agree more on the last two bullet points~~ Like comment: Like comment: Like Comment button Reply Collapse Expand DrBeehre DrBeehre DrBeehre Follow Location New Zealand Work Software Engineer at Self-Employed Joined Nov 10, 2020 • Mar 14 '21 Dropdown menu Copy link Hide This is awesome! I'm quite new to Web dev in particular and when starting a new project, I've often wondered which approach is better as I could see pros and cons to both, but I never found the time to dig in. Thanks for pulling all this together into a concise blog post! Like comment: Like comment: 1 like Like Comment button Reply View full discussion (30 comments) Some comments may only be visible to logged-in visitors. Sign in to view all comments. Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Sergey Follow Joined Nov 18, 2020 More from Sergey Mastering the Dependency Inversion Principle: Best Practices for Clean Code with DI # webdev # javascript # typescript # programming Rockpack 2.0 Official Release # react # javascript # webdev # showdev Project Structure. Repository and folders. Review of approaches. # javascript # react # webdev # codenewbie 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/privacy#a-provide-our-services | Privacy Policy - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Privacy Policy Last Updated: September 01, 2023 This Privacy Policy is designed to help you understand how DEV Community Inc. (" DEV ," " we ," or " us ") collects, use, and discloses your personal information. What's With the Defined Terms? You'll notice that some words appear in quotes in this Privacy Policy. They're called "defined terms," and we use them so that we don't have to repeat the same language again and again. They mean the same thing in every instance, to help us make sure that this Privacy Policy is consistent. We've included the defined terms throughout because we want it to be easy for you to read them in context. 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? 2. PERSONAL INFORMATION WE COLLECT 3. HOW WE USE YOUR INFORMATION 4. HOW WE DISCLOSE YOUR INFORMATION 5. YOUR PRIVACY CHOICES AND RIGHTS 6. INTERNATIONAL DATA TRANSFERS 7. RETENTION OF PERSONAL INFORMATION 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS 10. CHILDREN'S INFORMATION 11. OTHER PROVISIONS 12. CONTACT US 1. WHAT DOES THIS PRIVACY POLICY APPLY TO? This Privacy Policy applies to personal information processed by us, including on our websites, mobile applications, and other online or offline offerings — basically anything we do. To make this Privacy Policy easier to read, our websites, mobile applications, and other offerings are all collectively called the " Services. " Beyond this Privacy Policy, your use of the Services is subject to our DEV Community Terms and our Forem Terms. The Services include both our own community forum at https://www.dev.to (the " DEV Community ") and the open source tool we provide called " Forem ," available at https://www.forem.com which allows our customers to create and operate their own online forums. We collect personal information from two categories of people: (1) our customers, who use Forem and our hosting services to run and host their own forums (we'll call them " Forem Operators "), and (2) the people who interact with DEV-hosted forums, including forums provided by Forem Operators utilizing Forem and separately our own DEV Community (we'll call them " Users "). An Important Note for Users Since we provide hosting services for Forem Operators, technically we also process your information on their behalf. That processing is governed by the contracts that we have in place with each Forem Operator, not this Privacy Policy. In other words, when you share your data on a DEV-hosted forum operated by a Forem Operator, we at DEV are basically just the "pipes" — we process the data on behalf of the Forem Operator, but don't do anything with it ourselves beyond what we're required to do under our contract (and by law). So, if you post your information on a DEV-powered forum provided by a Forem Operator, that Forem Operator's privacy policy applies, and any questions or requests relating to your data on that service should be directed to that Forem Operator, not us. Likewise, if you use our mobile application, you may also interact with forums that use DEV's open-source tools but do all their hosting and data collection themselves. For those forums, we at DEV have no access to your data, so be sure to read the privacy policy of any third-party hosted forum before posting. 2. PERSONAL INFORMATION WE COLLECT The categories of personal information we collect depend on whether you're a User or Forem Operator, how you interact with us, our Services, and the requirements of applicable law. Breaking it down, we collect three types of information: (1) information that you provide to us directly, (2) information we obtain automatically when you use our Services, and (3) information we get about you from other sources (such as third-party services and organizations). More details are below. A. Information You Provide to Us Directly We may collect the following personal information that you provide to us. Account Creation (for Forem Operators): We'll require your name and email address to get started, as well as some details about the Forem you want to run, such as: whether you're running the Forem on your own behalf or as part of an organization, and details about the community you want to support (how big is it, what topics does it cover, where do members currently communicate, how/if the community earns money, whether the community is open, invite-only or paid, any existing social media accounts, etc.) You'll need to tell us a bit about your personal coding background, and you'll have the option to provide your DEV username as well, if you are a member of the DEV.to community. Account Creation (for Users) : We collect name and email address from users that create an account on DEV Community. For other forums created by Forem Operators using Forem, the Forem Operator determines what information is required for User account creation for their respective forums. Interactive Features (for Users) . Like any other social network, both we and other Users of our Services may collect personal information that you submit or make available through our interactive features (e.g., messaging and chat features, commenting functionalities, forums, blogs, posts, and other social media pages). While we do have private messages that are only between you and the person you're messaging (as well as us and the Forem Operator, as applicable), any information you provide using the public sharing features of the Services, such as the information you post to your public profile or the topics you follow is public, including to recruiters and prospective employers, and is not subject to any of the privacy protections we mention in this Privacy Policy except where legally required. Please exercise caution before revealing any information that may identify you in the real world to others. Purchases . If you buy stuff on our shop site https://shop.dev.to/ (as either a User or Forem Operator), or otherwise if you pay us in connection with your use of the Forem service, we may collect personal information and details associated with your purchases, including payment information. Any payments made via our Services are processed by third-party payment processors, such as Stripe, Shopify, and PayPal. We do not directly collect or store any payment card information entered through our Services, but may receive information associated with your payment card information (e.g., your billing details). Your Communications with Us (Users and Forem Operators) . We may collect personal information, such as email address, phone number, or mailing address when you request information about our Services, register for our newsletter or loyalty program, request customer or technical support, apply for a job, or otherwise communicate with us. Surveys . We may contact you to participate in surveys. If you decide to participate, you may be asked to provide certain information, which may include personal information (for example, your home address). Sweepstakes or Contests . We may collect personal information you provide for any sweepstakes or contests that we offer. In some jurisdictions, we are required to publicly share information of sweepstakes and contest winners. Conferences, Trade Shows, and Other Events . We may collect personal information from individuals when we attend conferences, trade shows, and other events. Business Development and Strategic Partnerships . We may collect personal information from individuals and third parties to assess and pursue potential business opportunities. Job Applications . We may post job openings and opportunities on our Services. If you reply to one of these postings by submitting your application, CV and/or cover letter to us, we will collect and use your information to assess your qualifications. B. Information Collected Automatically We may collect personal information automatically when you use our Services: Automatic Data Collection . We may collect certain information automatically when you use our Services, such as your Internet protocol (IP) address, user settings, MAC address, cookie identifiers, mobile carrier, mobile advertising and other unique identifiers, browser or device information, location information (including approximate location derived from IP address), and Internet service provider. We may also automatically collect information regarding your use of our Services, such as pages that you visit before, during and after using our Services, information about the links you click, the types of content you interact with, the frequency and duration of your activities, and other information about how you use our Services. In addition, we may collect information that other people provide about you when they use our Services, including information about you when they tag you in their posts. Cookies, Pixel Tags/Web Beacons, and Other Technologies . We, as well as third parties that provide content, advertising, or other functionality on our Services, may use cookies, pixel tags, local storage, and other technologies (" Technologies ") to automatically collect information through your use of our Services. Cookies . Cookies are small text files placed in device browsers that store preferences and facilitate and enhance your experience. Pixel Tags/Web Beacons . A pixel tag (also known as a web beacon) is a piece of code embedded in our Services that collects information about engagement on our Services. The use of a pixel tag allows us to record, for example, that a user has visited a particular web page or clicked on a particular advertisement. We may also include web beacons in e-mails to understand whether messages have been opened, acted on, or forwarded. Our uses of these Technologies fall into the following general categories: Operationally Necessary . This includes Technologies that allow you access to our Services, applications, and tools that are required to identify irregular website behavior, prevent fraudulent activity and improve security or that allow you to make use of our functionality. Performance-Related . We may use Technologies to assess the performance of our Services, including as part of our analytic practices to help us understand how individuals use our Services ( see Analytics below ). Functionality-Related . We may use Technologies that allow us to offer you enhanced functionality when accessing or using our Services. This may include identifying you when you sign into our Services or keeping track of your specified preferences, interests, or past items viewed. Analytics . We may use Technologies and other third-party tools to process analytics information on our Services. Some of our analytics partners include Google Analytics. For more information,please visit Google Analytics' Privacy Policy . To learn more about how to opt-out of Google Analytics' use of your information, please click here . Social Media Platforms . Our Services may contain social media buttons such as Twitter, Facebook, GitHub, Instagram, and Twitch (that might include widgets such as the "share this" button or other interactive mini programs). These features may collect your IP address, which page you are visiting on our Services, and may set a cookie to enable the feature to function properly. Your interactions with these platforms are governed by the privacy policy of the company providing it. See the "Your Privacy Choices and Rights" section below to understand your choices regarding these Technologies. C. Information Collected from Other Sources We may obtain information about you from other sources, including through third-party services and organizations. For example, if you access our Services through a third-party application, such as an app store, a third-party login service (e.g., through Twitter, Apple, or GitHub), or a social networking site, we may collect whatever information about you from that third-party application that you have made available via your privacy settings. 3. HOW WE USE YOUR INFORMATION We use your information for a variety of business purposes, including to provide our Services, for administrative purposes, and to market our products and Services, as described below. A. Provide Our Services We use your information to fulfill our contract with you and provide you with our Services, such as: Managing your information and accounts; Providing access to certain areas, functionalities, and features of our Services; Answering requests for customer or technical support; Communicating with you about your account, activities on our Services, and policy changes; Processing your financial information and other payment methods for products or Services purchased; Processing applications if you apply for a job we post on our Services; and Allowing you to register for events. B. Administrative Purposes We use your information for various administrative purposes, such as: Pursuing our legitimate interests such as direct marketing, research and development (including marketing research), network and information security, and fraud prevention; Detecting security incidents, protecting against malicious, deceptive, fraudulent or illegal activity, and prosecuting those responsible for that activity; Measuring interest and engagement in our Services, including for usage-based billing purposes; Short-term, transient use, such as contextual customization of ads; Improving, optimizing, upgrading, or enhancing our Services; Developing new products and Services; Ensuring internal quality control and safety; Authenticating and verifying individual identities, including requests to exercise your rights under this policy; Debugging to identify and repair errors with our Services; Auditing relating to interactions, transactions and other compliance activities; Enforcing our agreements and policies; and Complying with our legal obligations. C. Marketing and Advertising our Products and Services We may use your personal information to tailor and provide you with content and advertisements for our Services, such as via email. If you have any questions about our marketing practices, you may contact us at any time as set forth in the "Contact Us" section below. D. Other Purposes We also use your information for other purposes as requested by you or as permitted by applicable law. Consent . We may use personal information for other purposes that are clearly disclosed to you at the time you provide personal information or with your consent. Automated Decision Making. We may engage in automated decision making, including profiling, such as to suggest topics or other Users for you to follow. DEV's processing of your personal information will not result in a decision based solely on automated processing that significantly affects you unless such a decision is necessary as part of a contract we have with you, we have your consent, or we are permitted by law to engage in such automated decision making. If you have questions about our automated decision making, you may contact us as set forth in the "Contact Us" section below. De-identified and Aggregated Information . We may use personal information and other information about you to create de-identified and/or aggregated information, such as de-identified demographic information, information about the device from which you access our Services, or other analyses we create. For example, we may collect system-wide information to ensure availability of the platform, or measure aggregate data trends to analyze and optimize our Services. Share Content with Friends or Colleagues. Our Services may offer various tools and functionalities. For example, we may allow you to provide information about your friends through our referral services. Our referral services may allow you to forward or share certain content with a friend or colleague, such as an email inviting your friend to use our Services. Please only share with us contact information of people with whom you have a relationship (e.g., relative, friend neighbor, or co-worker). 4. HOW WE DISCLOSE YOUR INFORMATION We disclose your information to third parties for a variety of business purposes, including to provide our Services, to protect us or others, or in the event of a major business transaction such as a merger, sale, or asset transfer, as described below. A. Disclosures to Provide our Services The categories of third parties with whom we may share your information are described below. Service Providers . We may share your personal information with our third-party service providers who use that information to help us provide our Services. This includes service providers that provide us with IT support, hosting, payment processing, customer service, and related services. For example, our Shop site is run by Shopify, who handle your shipping details on our behalf. Business Partners . We may share your personal information with business partners to provide you with a product or service you have requested. We may also share your personal information to business partners with whom we jointly offer products or services. Other Users . As described above in the "Personal Information We Collect" section of this Privacy Policy, our Service allows Users to share their profiles, and any posts, chats, etc. with other Users and with the general public, including to those who do not use our Services. APIs/SDKs . We may use third-party Application Program Interfaces ("APIs") and Software Development Kits ("SDKs") as part of the functionality of our Services. For more information about our use of APIs and SDKs, please contact us as set forth in the "Contact Us" section below. B . Disclosures to Protect Us or Others We may access, preserve, and disclose any information we store associated with you to external parties if we, in good faith, believe doing so is required or appropriate to: comply with law enforcement or national security requests and legal process, such as a court order or subpoena; protect your, our, or others' rights, property, or safety; enforce our policies or contracts; collect amounts owed to us; or assist with an investigation or prosecution of suspected or actual illegal activity. C. Disclosure in the Event of Merger, Sale, or Other Asset Transfers If we are involved in a merger, acquisition, financing due diligence, reorganization, bankruptcy, receivership, purchase or sale of assets, or transition of service to another provider, your information may be sold or transferred as part of such a transaction, as permitted by law and/or contract. 5. YOUR PRIVACY CHOICES AND RIGHTS Your Privacy Choices . The privacy choices you may have about your personal information are determined by applicable law and are described below. Email Communications . If you receive an unwanted email from us, you can use the unsubscribe link found at the bottom of the email to opt out of receiving future emails. Note that you will continue to receive transaction-related emails regarding products or Services you have requested. We may also send you certain non-promotional communications regarding us and our Services, and you will not be able to opt out of those communications (e.g., communications regarding our Services or updates to our Terms or this Privacy Policy). Mobile Devices . We may send you push notifications through our mobile application. You may opt out from receiving these push notifications by changing the settings on your mobile device. "Do Not Track." Do Not Track (" DNT ") is a privacy preference that users can set in certain web browsers. Please note that we do not respond to or honor DNT signals or similar mechanisms transmitted by web browsers. Cookies and Interest-Based Advertising . You may stop or restrict the placement of Technologies on your device or remove them by adjusting your preferences as your browser or device permits. However, if you adjust your preferences, our Services may not work properly. Please note that cookie-based opt-outs are not effective on mobile applications. Please note you must separately opt out in each browser and on each device. Your Privacy Rights . In accordance with applicable law, you may have the right to: Access Personal Information about you, including: (i) confirming whether we are processing your personal information; (ii) obtaining access to or a copy of your personal information; Request Correction of your personal information where it is inaccurate, incomplete or outdated. In some cases, we may provide self-service tools that enable you to update your personal information; Request Deletion, Anonymization or Blocking of your personal information when processing is based on your consent or when processing is unnecessary, excessive or noncompliant; Request Restriction of or Object to our processing of your personal information when processing is noncompliant; Withdraw Your Consent to our processing of your personal information. If you refrain from providing personal information or withdraw your consent to processing, some features of our Service may not be available; Request Data Portability and Receive an Electronic Copy of Personal Information that You Have Provided to Us; Be Informed about third parties with which your personal information has been shared; and Request the Review of Decisions Taken Exclusively Based on Automated Processing if such decisions could affect your data subject rights. If you would like to exercise any of these rights, please contact us as set forth in "Contact Us" below. We will process such requests in accordance with applicable laws. 6. INTERNATIONAL DATA TRANSFERS All information processed by us may be transferred, processed, and stored anywhere in the world, including, but not limited to, the United States or other countries, which may have data protection laws that are different from the laws where you live. We always strive to safeguard your information consistent with the requirements of applicable laws. 7. RETENTION OF PERSONAL INFORMATION We store the personal information we collect as described in this Privacy Policy for as long as you use our Services or as necessary: to fulfill the purpose or purposes for which it was collected, to provide our Services, to resolve disputes, to establish legal defenses, to conduct audits, to pursue legitimate business purposes, to enforce our agreements, and to comply with applicable laws. 8. SUPPLEMENTAL DISCLOSURES FOR CALIFORNIA RESIDENTS Refer-a-Friend and Similar Incentive Programs . As described above in the How We Use Your Personal Information section ("Share Content with Friends or Colleagues" subsection), we may offer referral programs or other incentivized data collection programs. For example, we may offer incentives to you such as discounts or promotional items or credit in connection with these programs, wherein you provide your personal information in exchange for a reward, or provide personal information regarding your friends or colleagues (such as their email address) and receive rewards when they sign up to use our Services. (The referred party may also receive rewards for signing up via your referral.) These programs are entirely voluntary and allow us to grow our business and provide additional benefits to you. The value of your data to us depends on how you ultimately use our Services, whereas the value of the referred party's data to us depends on whether the referred party ultimately becomes a User or Forem Operator and uses our Services. Said value will be reflected in the incentive offered in connection with each program. Accessibility . This Privacy Policy uses industry-standard technologies and was developed in line with the World Wide Web Consortium's Web Content Accessibility Guidelines, version 2.1* . * If you wish to print this policy, please do so from your web browser or by saving the page as a PDF. California Shine the Light . The California "Shine the Light" law permits users who are California residents to request and obtain from us once a year, free of charge, a list of the third parties to whom we have disclosed their personal information (if any) for their direct marketing purposes in the prior calendar year, as well as the type of personal information disclosed to those parties. Right for Minors to Remove Posted Content . Where required by law, California residents under the age of 18 may request to have their posted content or information removed from the publicly-viewable portions of the Services by contacting us directly as set forth in the "Contact Us" section below or by logging into their account and removing the content or information using our self-service tools. 9. SUPPLEMENTAL NOTICE FOR NEVADA RESIDENTS If you are a resident of Nevada, you have the right to opt-out of the sale of certain Personal Information to third parties who intend to license or sell that Personal Information. You can exercise this right by contacting us as set forth in the "Contact Us\" section below with the subject line "Nevada Do Not Sell Request" and providing us with your name and the email address associated with your account. Please note that we do not currently sell your Personal Information as sales are defined in Nevada Revised Statutes Chapter 603A. If you have any questions, please contact us as set forth below. 10. CHILDREN'S INFORMATION The Services are not directed to children under 13 (or other age as required by local law), and we do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has uploaded personal information to our site without your consent, you may contact us as described in the "Contact Us" section below. If we become aware that a child has provided us with personal information in violation of applicable law, we will delete any personal information we have collected, unless we have a legal obligation to keep it, and terminate the child's account if applicable. 11. OTHER PROVISIONS Third-Party Websites or Applications . The Services may contain links to other websites or applications, and other websites or applications may reference or link to our Services. These third-party services are not controlled by us. We encourage our users to read the privacy policies of each website and application with which they interact. We do not endorse, screen or approve, and are not responsible for, the privacy practices or content of such other websites or applications. Providing personal information to third-party websites or applications is at your own risk. Changes to Our Privacy Policy . We may revise this Privacy Policy from time to time in our sole discretion. If there are any material changes to this Privacy Policy, we will notify you as required by applicable law. You understand and agree that you will be deemed to have accepted the updated Privacy Policy if you continue to use our Services after the new Privacy Policy takes effect. 12. CONTACT US If you have any questions about our privacy practices or this Privacy Policy, or to exercise your rights as detailed in this Privacy Policy, please contact us at: support@dev.to . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/about#our-community-guidelines | About HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close About HMPL.js Forem Welcome to the HMPL.js Forem! Hello and welcome, developers! This is the official community hub for HMPL.js, the server-oriented, customizable templating language for JavaScript. If you're excited about building dynamic, modern, and incredibly small web applications by keeping logic on the server and fetching HTML, you've found your home. What This Community Is About Our mission is to create a central place for developers to learn, discuss, and master HMPL.js. We believe in building powerful user interfaces with minimal client-side JavaScript, leveraging the server to do the heavy lifting. HMPL.js is designed to be: Flexible: Get the benefits of SSR on any platform, whether it's a simple static site or a complex single-page application. Easy to Use: Describe a couple of properties in an object and get ready-to-use HTML directly from your server. Reliable: With 100% code coverage and built-in protection against XSS vulnerabilities (using DOMPurify), you can build with confidence. Lightweight: All this functionality is packed into just ~24 kilobytes, making your apps significantly smaller than those built with other popular tools. This forum is the place to explore these concepts, share your successes, and get help when you need it. What to Discuss Here We encourage a wide range of discussions. Whether you're a beginner or an expert, your voice is welcome. Here are a few ideas to get you started: Questions & Support: Need help with installation, hmpl.compile() , or the hmpl-dom module? Ask away! Use the #help tag. Show & Tell: Share the awesome things you've built with HMPL.js. Post a link to your project or a code snippet. Use the #showdev tag. Tutorials & Guides: Found a great way to solve a common problem? Write a post to share your knowledge with the community. Use the #tutorial tag. In-Depth Discussions: Let's talk about best practices, performance, or how HMPL.js compares to libraries like HTMX and Alpine.js. Use the #discuss tag. Ideas & Feedback: Have a suggestion for a new feature or an improvement? We'd love to hear it! How to Get Involved Jumping in is easy! Introduce yourself in the comments of a welcome thread. Ask a question or help answer someone else's. Share your project or a cool code snippet you've written. Experiment with the online HMPL Playground and share your creations. Our Community Guidelines To ensure this remains a friendly and productive space for everyone, we ask that you follow a few simple principles: Be Kind and Respectful: Treat everyone with courtesy. Healthy debate is encouraged, but personal attacks are not. Be Collaborative: This is a space for learning together. Share what you know, and be open to learning from others. Stay Constructive: Offer feedback that is helpful, supportive, and aimed at moving the conversation forward. Stay On Topic: Keep discussions focused on HMPL.js and related web development technologies. We're thrilled to have you here. Let's build something amazing together 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://www.python.org/psf/annual-report/2024/#top | 2024 PSF Annual Impact Report | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event PSF >>> About >>> Annual Impact Report 2024 PSF Annual Impact Report The Python Software Foundation 2024 Annual Impact Report In 2024, the Python community and language continued to grow! The PSF celebrated a year of remarkable growth, with Python becoming the most popular language on GitHub and worldwide community engagement at an all-time high. We expanded our impact by welcoming our inaugural PyPI Support Specialist, Maria Ashna, the revival of the User Success and Education and Outreach Workgroups, and continued investment in grants, infrastructure, and accessibility. We’d love for you to take a look at the 2024 Annual Impact Report that we put together to share more highlights from the year, financial reporting, and some previews of what’s to come in the next year. Download and read the report today! Thank you to Robb Design Co. for the beautiful design! The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://dev.to/ibn_abubakre/em-vs-rem-5b33 | em VS rem - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Abdulqudus Abubakre Posted on May 23, 2020 em VS rem # css # html This VS That (3 Part Series) 1 append VS appendChild 2 Spread VS Rest Operator 3 em VS rem In the world of CSS and sizing, there are several units that can be used either for your font sizing, margin, padding and so on. Two commonly used, but slightly confusing units are the rem and em . Both units are relative CSS units (they depend on something else for their sizing). Now how are these two different??? em This unit inherits the font size of its nearest parent element having a font-size. I'll be going with a visual representation here to explain how the inheritance works. In the image above, the root element has a font size of 36px. The body element which is a child of the root element has a font size of 0.8em, which is equivalent to 80% of the font-size of the root element i.e (0.8 * 36px = 28.8), and it goes on and on. If the immediate parent does not have a set font size, it looks for the parent element having a defined font size. rem This unit inherits the font size of the root element. You can think of it as the root em . In this case, rather than inheriting the font size of its immediate element, it inherits that of the html element. Here, no matter how deeply nested the element is, it always finds its way home 😀😀....in this case, the root element. Here's a codepen demo showing em and rem in action. Conclusion This a just a look into em and rem, which one you choose is entirely up to you. With em you can have different font sizes for different sections. With rem you have a central controller that you can use to determine sizes of other elements in your html. This VS That (3 Part Series) 1 append VS appendChild 2 Spread VS Rest Operator 3 em VS rem Top comments (9) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Rahul Jain Rahul Jain Rahul Jain Follow ♥️In relationship with front end dev👨💻 Email rahuldkjain@gmail.com Location Bangalore, India Education IIIT Jabalpur Work Software Engineer at CRED Joined Oct 18, 2019 • May 24 '20 Dropdown menu Copy link Hide Amazing explanation indeed! Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Abdulqudus Abubakre Abdulqudus Abubakre Abdulqudus Abubakre Follow Front end developer, JavaScript enthusiast, Community Builder Location Abuja, Nigeria Joined Jan 3, 2020 • May 24 '20 Dropdown menu Copy link Hide Thanks Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Bayu Angora Bayu Angora Bayu Angora Follow ★★★★★ Location https://angora.id Joined Jun 9, 2019 • May 24 '20 • Edited on May 24 • Edited Dropdown menu Copy link Hide So, where's rem inherited to if we don't fill anything (margin, padding, font-size, etc) on html class? Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Daniel Atwood Daniel Atwood Daniel Atwood Follow Location Chattanooga, TN Work Full Stack Web Developer Joined May 4, 2020 • May 24 '20 Dropdown menu Copy link Hide I think most browsers default the body to 16px which is what rem would be set to. Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Abdulqudus Abubakre Abdulqudus Abubakre Abdulqudus Abubakre Follow Front end developer, JavaScript enthusiast, Community Builder Location Abuja, Nigeria Joined Jan 3, 2020 • May 24 '20 Dropdown menu Copy link Hide Yes, it has a default of 16px Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand timothyokooboh timothyokooboh timothyokooboh Follow Frontend Engineer Email okoobohtimothy@gmail.com Location Lagos, Nigeria Work Lead frontend engineer at SeamlessHR Joined Feb 8, 2020 • May 24 '20 Dropdown menu Copy link Hide One of the "clearest" explanations I have seen on this topic. Like comment: Like comment: 6 likes Like Comment button Reply Collapse Expand Abdulqudus Abubakre Abdulqudus Abubakre Abdulqudus Abubakre Follow Front end developer, JavaScript enthusiast, Community Builder Location Abuja, Nigeria Joined Jan 3, 2020 • May 24 '20 Dropdown menu Copy link Hide Glad I could help Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand yusuf-saif yusuf-saif yusuf-saif Follow A web developer ready to learn anything at anytime from anyone Location Abuja Work Web developer at Knowledgebased services limited Joined Mar 3, 2020 • May 24 '20 Dropdown menu Copy link Hide What a very nice and interesting write up Hope we will be expecting more right Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Tetteh Simon Tetteh Simon Tetteh Simon Follow Location Ashanti Region/ Ghana Joined Jul 21, 2024 • Jul 21 '24 Dropdown menu Copy link Hide Thanks for the explanation 👍 Like comment: Like comment: 1 like Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Abdulqudus Abubakre Follow Front end developer, JavaScript enthusiast, Community Builder Location Abuja, Nigeria Joined Jan 3, 2020 More from Abdulqudus Abubakre Using aria-labelledby for accessible names # webdev # a11y # html Understanding Accessible Names in HTML # webdev # a11y # html Hiding Elements in CSS: The Accessible Way # a11y # html # css # webdev 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://www.python.org/psf/annual-report/2024/#python-network | 2024 PSF Annual Impact Report | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event PSF >>> About >>> Annual Impact Report 2024 PSF Annual Impact Report The Python Software Foundation 2024 Annual Impact Report In 2024, the Python community and language continued to grow! The PSF celebrated a year of remarkable growth, with Python becoming the most popular language on GitHub and worldwide community engagement at an all-time high. We expanded our impact by welcoming our inaugural PyPI Support Specialist, Maria Ashna, the revival of the User Success and Education and Outreach Workgroups, and continued investment in grants, infrastructure, and accessibility. We’d love for you to take a look at the 2024 Annual Impact Report that we put together to share more highlights from the year, financial reporting, and some previews of what’s to come in the next year. Download and read the report today! Thank you to Robb Design Co. for the beautiful design! The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://dev.to/t/web3/page/75 | Web3 Page 75 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Web3 Follow Hide Web3 refers to the next generation of the internet that leverages blockchain technology to enable decentralized and trustless systems for financial transactions, data storage, and other applications. Create Post Older #web3 posts 72 73 74 75 76 77 78 79 80 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Building On Mina: A guide to writing smart contract implementing Merkle Trees using 01js Adetayo Lasisi Adetayo Lasisi Adetayo Lasisi Follow Feb 1 '25 Building On Mina: A guide to writing smart contract implementing Merkle Trees using 01js # web3 # blockchain # zkapps # mina Comments Add Comment 10 min read The Future of Digital Identity: How Web3 Domains Are Redefining Ownership Jay Saadana Jay Saadana Jay Saadana Follow Mar 2 '25 The Future of Digital Identity: How Web3 Domains Are Redefining Ownership # web3 # blockchain # programming # productivity 36 reactions Comments Add Comment 3 min read 🚀 Your Daily Crypto Job Digest For 28 January!! 🚀 Web3 Hires Web3 Hires Web3 Hires Follow Jan 28 '25 🚀 Your Daily Crypto Job Digest For 28 January!! 🚀 # hiring # whoishiring # web3 5 reactions Comments 1 comment 2 min read Optimizing Storage Layout with Solidity Struct Clustering Tahzib Mahmud Rifat Tahzib Mahmud Rifat Tahzib Mahmud Rifat Follow Mar 2 '25 Optimizing Storage Layout with Solidity Struct Clustering # solidity # web3 # blockchain # ethereum Comments Add Comment 2 min read How to build your Solana sniper bot (1)💰🚀 Viet Thanh Sai Viet Thanh Sai Viet Thanh Sai Follow Feb 28 '25 How to build your Solana sniper bot (1)💰🚀 # blockchain # web3 # typescript # solana 147 reactions Comments 3 comments 6 min read Build a Trustless React App to Swap EVM Assets for Bitcoin via THORChain Radzion Chachura Radzion Chachura Radzion Chachura Follow Jan 28 '25 Build a Trustless React App to Swap EVM Assets for Bitcoin via THORChain # react # web3 # bitcoin # thorchain 1 reaction Comments Add Comment 14 min read Learn Rust if You Don’t Wanna Be Rusty FOBABS FOBABS FOBABS Follow Jan 25 '25 Learn Rust if You Don’t Wanna Be Rusty # programming # rust # web3 # blockchain Comments Add Comment 3 min read Web3 and Cybersecurity: How AI Protects Decentralized Systems Alex Roor Alex Roor Alex Roor Follow Mar 12 '25 Web3 and Cybersecurity: How AI Protects Decentralized Systems # web3 # blockchain # productivity # ai Comments 1 comment 1 min read How to DeRug a Solana NFT Collection - Updating NFT Authority carson carson carson Follow Feb 17 '25 How to DeRug a Solana NFT Collection - Updating NFT Authority # web3 # solana # javascript # programming 2 reactions Comments Add Comment 4 min read Decentralized Wallet Networks: The Backbone of Seamless Web3 Precious Precious Precious Follow Jan 25 '25 Decentralized Wallet Networks: The Backbone of Seamless Web3 # wallet # web3 # blockchain # decentralizenetwork 1 reaction Comments Add Comment 4 min read Introduction to Okto and it's Decentralized Transaction Networks Abhinav Kale Abhinav Kale Abhinav Kale Follow Jan 24 '25 Introduction to Okto and it's Decentralized Transaction Networks # blockchain # web3 # crypto 1 reaction Comments Add Comment 6 min read End-to-End Privacy for Web3 dApps with Oasis Sapphire Manav Manav Manav Follow Feb 27 '25 End-to-End Privacy for Web3 dApps with Oasis Sapphire # web3 # privacy # blockchain # programming Comments 1 comment 2 min read ROFL: Unlocking Secure Off-Chain Computation with Oasis Network Manav Manav Manav Follow Feb 27 '25 ROFL: Unlocking Secure Off-Chain Computation with Oasis Network # blockchain # web3 # privacy # security Comments Add Comment 2 min read Trustless Agents and Secure Execution: Why Oasis's TEE is a Game Changer Manav Manav Manav Follow Feb 27 '25 Trustless Agents and Secure Execution: Why Oasis's TEE is a Game Changer # ai # web3 # blockchain # security Comments Add Comment 2 min read A Guide to Web Evolution: From Web1 to Web3 Ella🦋🌸 Ella🦋🌸 Ella🦋🌸 Follow Feb 27 '25 A Guide to Web Evolution: From Web1 to Web3 # webdev # javascript # tutorial # web3 3 reactions Comments Add Comment 4 min read The Evolution Of Wireless Networking : A Deep Dive Into IEEE 802 Standards Sujit Parte Sujit Parte Sujit Parte Follow Feb 27 '25 The Evolution Of Wireless Networking : A Deep Dive Into IEEE 802 Standards # wireless # networking # security # web3 Comments Add Comment 4 min read What is Web3? Differences Between Web2 and Web3 OstryKot OstryKot OstryKot Follow Feb 27 '25 What is Web3? Differences Between Web2 and Web3 # web3 # blockchain # programming # webdev Comments Add Comment 2 min read Building dApps: Hardhat vs. Foundry vs. Truffle – Which Framework is Best? Raji moshood Raji moshood Raji moshood Follow Feb 11 '25 Building dApps: Hardhat vs. Foundry vs. Truffle – Which Framework is Best? # hardhat # truffle # foundry # web3 Comments 1 comment 3 min read Republic Day of India Jay Ramoliya Jay Ramoliya Jay Ramoliya Follow Jan 24 '25 Republic Day of India # html # javascript # css # web3 Comments Add Comment 2 min read 🚀 Your Daily Crypto Job Digest For 23 January!! 🚀 Web3 Hires Web3 Hires Web3 Hires Follow Jan 24 '25 🚀 Your Daily Crypto Job Digest For 23 January!! 🚀 # hiring # whoishiring # web3 4 reactions Comments Add Comment 2 min read Smart Privacy & TEEs Unlocking Next-gen Web3: The Oasis Way DC DC DC Follow Feb 27 '25 Smart Privacy & TEEs Unlocking Next-gen Web3: The Oasis Way # privacy # tee # web3 # smartcontract 1 reaction Comments Add Comment 5 min read Earn Up to 1M XIAN: Xian Blockchain’s Bounty Program is Live! crosschainer crosschainer crosschainer Follow Feb 26 '25 Earn Up to 1M XIAN: Xian Blockchain’s Bounty Program is Live! # blockchain # python # programming # web3 5 reactions Comments Add Comment 1 min read Getting Started with CrossFi Development: Keplr & MetaMask Wallet Integration Azeez Abidoye Azeez Abidoye Azeez Abidoye Follow Feb 26 '25 Getting Started with CrossFi Development: Keplr & MetaMask Wallet Integration # blockchain # crossfi # ethereum # web3 17 reactions Comments 1 comment 6 min read Start a new journey in Laravel Rishi Patel Rishi Patel Rishi Patel Follow Feb 6 '25 Start a new journey in Laravel # laravel # webdev # web3 # php 1 reaction Comments 1 comment 1 min read 🛡️ Smarter Crypto Trading: How Sub-Accounts & Isolated Margin Minimize Risk Theodor Coin Theodor Coin Theodor Coin Follow Feb 26 '25 🛡️ Smarter Crypto Trading: How Sub-Accounts & Isolated Margin Minimize Risk # web3 # blockchain # webdev Comments Add Comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://www.python.org/psf/annual-report/2024/#content | 2024 PSF Annual Impact Report | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event PSF >>> About >>> Annual Impact Report 2024 PSF Annual Impact Report The Python Software Foundation 2024 Annual Impact Report In 2024, the Python community and language continued to grow! The PSF celebrated a year of remarkable growth, with Python becoming the most popular language on GitHub and worldwide community engagement at an all-time high. We expanded our impact by welcoming our inaugural PyPI Support Specialist, Maria Ashna, the revival of the User Success and Education and Outreach Workgroups, and continued investment in grants, infrastructure, and accessibility. We’d love for you to take a look at the 2024 Annual Impact Report that we put together to share more highlights from the year, financial reporting, and some previews of what’s to come in the next year. Download and read the report today! Thank you to Robb Design Co. for the beautiful design! The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://www.python.org/community/irc/#content | Internet Relay Chat | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> IRC Internet Relay Chat There are several Python-related channels on the libera IRC network. All channels are available by connecting to Internet Relay Chat server Libera.Chat . The #python channel is for all discussion about the Python language, ecosystem, and community. You can get immediate help with programming questions. You will need to first register your nickname with Libera, using the nickname setup instructions ( https://libera.chat/guides/registration ). Spanish speakers can use the #pyar channel, from the Python Argentina user group. French speakers can join the #python-fr channel. Finnish speakers can join the #python.fi channel on a different network, IRCnet . (Note: prior to May 2021, these channels existed on Freenode. Some of them were forcibly removed by Freenode operators, after a change in management and network policy. The channels on Freenode are no longer under the PSF umbrella.) Other Channels #python-dev is for CPython developers, where they can coordinate their work or discuss problems. Bots post updates to the channel based on activity in the CPython source tree and bug tracker. #python-infra is for Python infrastructure discussion. #pydotorg is for discussion of this website, python.org. #distutils and #pypa are for Python packaging discussion. Other Sites IRC clients for many platforms can be found in the Internet Relay Chat (IRC) Help Archive . The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://www.python.org/success-stories/category/engineering/#python-network | Engineering | Our Success Stories | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python >>> Success Stories >>> Engineering Engineering Python for Collaborative Robots Abridging clinical conversations using Python Getting to Know Python Success stories home Arts Business Data Science Education Engineering Government Scientific Software Development Submit Yours! ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://discuss.python.org/c/packaging | Latest Packaging topics - Discussions on Python.org Discussions on Python.org Packaging Standards Standards discussions, ala PEPs as well as some proposals/grand ideas for changes to how things are done. Announcements Announcements about projects. This is releases for “major” projects (mainly pip releases and PyPI feature deployments), as well as one-off announcements for new projects/tools. User Feedback User feedback about the packaging tooling such as information from a UX review, user surveys, and feedback about specific user workflows. Coordination Coordination discussions. This is mechanical stuff that involves co-ordinating multi-project effort, or stuff like the governance story about how we do those things. Topic Replies Views Activity About the Packaging category Packaging 5 7001 March 11, 2019 PEP 819: JSON Package Metadata Standards 30 771 January 13, 2026 Adopting TOML 1.1? Packaging 39 736 January 13, 2026 Announcement: packaging 26.0rc1 released! Announcements 1 198 January 10, 2026 Spec change/bugfix: dependency specifiers simplification (PEP 508) Standards 15 624 January 10, 2026 Block download of components when violating policy Packaging 12 645 January 10, 2026 PSA: proposed change to the `.pypirc` "spec" Packaging 0 111 January 7, 2026 Path towards manylinux / PyPI support for loongarch64 Packaging 2 211 January 7, 2026 PEP 771: Default Extras for Python Software Packages (Round 2) Standards 106 2760 January 6, 2026 PEP 725: Specifying external dependencies in pyproject.toml (round 2) Standards 91 2362 January 3, 2026 Pre-PEP Discussion: RFC 9457 Error Responses for Package registries Standards 8 334 January 2, 2026 PEP 804: An external dependency registry and name mapping mechanism Standards 44 1705 December 31, 2025 Accessibility issues in the PyPI donation banner User Feedback 11 825 December 24, 2025 Are setuptools abandoned? User Feedback setuptools 12 1152 December 22, 2025 PEP 808: Partially dynamic project metadata Packaging 33 1307 December 21, 2025 Can't log in to pypi and PYPI_TOKEN no longer works User Feedback 3 204 December 18, 2025 Encoding "origin" in wheel and dist-info metadata (for downstream security backports) Packaging 17 562 December 17, 2025 On resolving distributions vs. releases Packaging 14 415 December 16, 2025 Adding extension module examples to the packaging user guide Packaging 36 797 December 15, 2025 PEP 772: Packaging Council governance process (Round 3) Coordination 101 2958 December 14, 2025 New project (CLI) install-locked-env. What about security? Packaging 8 257 December 12, 2025 Installing dependencies without the package Packaging 7 250 December 11, 2025 PEP 815: Deprecate `RECORD.jws` and `RECORD.p7s` Packaging 6 286 December 11, 2025 Hatch v1.16.0 - workspaces, dependency groups and SBOMs Announcements 3 410 December 8, 2025 Reconciling `packaging` module & The Dependency Specifier Spec's non-version to version comparison rules Standards 17 780 December 8, 2025 PEP 694 -- PyPI upload API 2.0 (Round 2) Standards 34 1094 December 7, 2025 PEP 739: Static description file for build details of Python installations Standards 120 4310 December 7, 2025 A tool to see what dependencies support free-threading Announcements free-threading 0 130 December 5, 2025 How to hash a directory in lockfiles Packaging 37 1032 December 4, 2025 Mistakes in Dependency specifiers Grammar Standards 2 180 December 4, 2025 next page → Home Categories Guidelines Terms of Service Privacy Policy Powered by Discourse , best viewed with JavaScript enabled | 2026-01-13T08:49:06 |
https://www.python.org/psf/annual-report/2024/#site-map | 2024 PSF Annual Impact Report | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event PSF >>> About >>> Annual Impact Report 2024 PSF Annual Impact Report The Python Software Foundation 2024 Annual Impact Report In 2024, the Python community and language continued to grow! The PSF celebrated a year of remarkable growth, with Python becoming the most popular language on GitHub and worldwide community engagement at an all-time high. We expanded our impact by welcoming our inaugural PyPI Support Specialist, Maria Ashna, the revival of the User Success and Education and Outreach Workgroups, and continued investment in grants, infrastructure, and accessibility. We’d love for you to take a look at the 2024 Annual Impact Report that we put together to share more highlights from the year, financial reporting, and some previews of what’s to come in the next year. Download and read the report today! Thank you to Robb Design Co. for the beautiful design! The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://future.forem.com/t/education/page/3 | Education Page 3 - Future Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Future Close # education Follow Hide Discussions on academic programs, online courses, and learning paths in security. Create Post Older #education posts 1 2 3 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Narcissists report high emotional intelligence but perform worse on objective tests, suggests a new study. Science News Science News Science News Follow Aug 7 '25 Narcissists report high emotional intelligence but perform worse on objective tests, suggests a new study. # science # healthtech # productivity # education Comments Add Comment 1 min read Y Combinator Wants to Fund the First ‘10 Person, $100 Billion' Company AI News AI News AI News Follow Aug 5 '25 Y Combinator Wants to Fund the First ‘10 Person, $100 Billion' Company # ai # education # employment # productivity Comments Add Comment 1 min read How to Write Your First Program for a Quantum Computer Quantum News Quantum News Quantum News Follow Aug 5 '25 How to Write Your First Program for a Quantum Computer # quantum # science # education # ai Comments Add Comment 1 min read New Nanodevice can enable Holographic XR Headsets: “we can do everything – holography, beam steering, 3D displays – anything” AR/VR News AR/VR News AR/VR News Follow Aug 5 '25 New Nanodevice can enable Holographic XR Headsets: “we can do everything – holography, beam steering, 3D displays – anything” # education # science # healthtech # energy Comments Add Comment 1 min read Jeff Su: How to Join Google (honest advice from ex-Googler) AI News AI News AI News Follow Aug 1 '25 Jeff Su: How to Join Google (honest advice from ex-Googler) # education # productivity Comments Add Comment 1 min read Jeff Su: ex-Googler: My honest advice for someone who wants to join Google AI News AI News AI News Follow Jul 30 '25 Jeff Su: ex-Googler: My honest advice for someone who wants to join Google # education # productivity Comments Add Comment 1 min read Kurzgesagt - In a Nutshell: Dear Alcohol... Future YouTube Future YouTube Future YouTube Follow Aug 13 '25 Kurzgesagt - In a Nutshell: Dear Alcohol... # education # science 1 reaction Comments Add Comment 1 min read China's SpinQ Targets 500-Qubit Milestone as Quantum Computing Nears Real-World Utility Quantum News Quantum News Quantum News Follow Jul 22 '25 China's SpinQ Targets 500-Qubit Milestone as Quantum Computing Nears Real-World Utility # quantum # science # education # nanotech Comments Add Comment 1 min read Exhausted man defeats AI model in world coding championship AI News AI News AI News Follow Jul 21 '25 Exhausted man defeats AI model in world coding championship # ai # science # education # employment Comments Add Comment 1 min read Don't Get Comfortable: Why Today's Mixed Reality is a Bridge, Not a Destination AR/VR News AR/VR News AR/VR News Follow Jul 14 '25 Don't Get Comfortable: Why Today's Mixed Reality is a Bridge, Not a Destination # productivity # education # security # privacy Comments Add Comment 1 min read Jeff Su: The AI Agent Tutorial That Should've Been Your First (no code) AI News AI News AI News Follow Aug 13 '25 Jeff Su: The AI Agent Tutorial That Should've Been Your First (no code) # ai # productivity # education Comments 1 comment 1 min read Jeff Su: The CORRECT way to use ChatGPT (in 2025) AI News AI News AI News Follow Jul 10 '25 Jeff Su: The CORRECT way to use ChatGPT (in 2025) # ai # productivity # education # science Comments Add Comment 1 min read Jeff Su: The CORRECT way to use ChatGPT (in 2025) AI News AI News AI News Follow Jul 10 '25 Jeff Su: The CORRECT way to use ChatGPT (in 2025) # ai # productivity # education # science Comments Add Comment 1 min read People with short-video addiction show altered brain responses during decision-making Science News Science News Science News Follow Jul 10 '25 People with short-video addiction show altered brain responses during decision-making # science # healthtech # biotech # education Comments Add Comment 1 min read Jeff Su: If you can use ChatGPT, you can build this AI Agent AI News AI News AI News Follow Aug 12 '25 Jeff Su: If you can use ChatGPT, you can build this AI Agent # ai # productivity # education 1 reaction Comments Add Comment 1 min read Jeff Su: The CORRECT way to use ChatGPT (in 2025) AI News AI News AI News Follow Jul 9 '25 Jeff Su: The CORRECT way to use ChatGPT (in 2025) # ai # productivity # education # science Comments Add Comment 1 min read Jeff Su: The CORRECT way to use ChatGPT (in 2025) AI News AI News AI News Follow Jul 8 '25 Jeff Su: The CORRECT way to use ChatGPT (in 2025) # ai # productivity # education # science Comments Add Comment 1 min read Leaked Meta Hypernova firmware reveals Photos App zoom and pan instructions AR/VR News AR/VR News AR/VR News Follow Jul 8 '25 Leaked Meta Hypernova firmware reveals Photos App zoom and pan instructions # privacy # security # productivity # education Comments Add Comment 1 min read Laid-off workers should use AI to manage their emotions, says Xbox exec AI News AI News AI News Follow Jul 7 '25 Laid-off workers should use AI to manage their emotions, says Xbox exec # ai # employment # productivity # education 1 reaction Comments Add Comment 1 min read Longer antidepressant use linked to more severe, long-lasting withdrawal symptoms, study finds Science News Science News Science News Follow Jul 2 '25 Longer antidepressant use linked to more severe, long-lasting withdrawal symptoms, study finds # science # healthtech # biotech # education Comments Add Comment 1 min read Earth is trapping much more heat than climate models forecast – and the rate has doubled in 20 years Science News Science News Science News Follow Jul 2 '25 Earth is trapping much more heat than climate models forecast – and the rate has doubled in 20 years # science # energy # solar # education Comments Add Comment 1 min read ChatGPT is bringing back 4o as an option because people missed it AI News AI News AI News Follow Aug 12 '25 ChatGPT is bringing back 4o as an option because people missed it # ai # productivity # education # science 4 reactions Comments 1 comment 1 min read Jeff Su: The CORRECT way to use ChatGPT (in 2025) AI News AI News AI News Follow Jul 7 '25 Jeff Su: The CORRECT way to use ChatGPT (in 2025) # ai # productivity # education # science 5 reactions Comments Add Comment 1 min read Veritasium: The Perfect Battery Material Is DANGEROUS Future YouTube Future YouTube Future YouTube Follow Aug 15 '25 Veritasium: The Perfect Battery Material Is DANGEROUS # science # education Comments 1 comment 1 min read OpenAI Scrambles to Update GPT-5 After Users Revolt AI News AI News AI News Follow Aug 12 '25 OpenAI Scrambles to Update GPT-5 After Users Revolt # ai # science # productivity # education Comments 1 comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Future — News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Future © 2025 - 2026. Stay on the cutting edge, and shape tomorrow Log in Create account | 2026-01-13T08:49:06 |
https://peps.python.org/pep-0247/ | PEP 247 – API for Cryptographic Hash Functions | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 247 Toggle light / dark / auto colour theme PEP 247 – API for Cryptographic Hash Functions Author : A.M. Kuchling <amk at amk.ca> Status : Final Type : Informational Created : 23-Mar-2001 Post-History : 20-Sep-2001 Table of Contents Abstract Specification Rationale Changes Acknowledgements Copyright Abstract There are several different modules available that implement cryptographic hashing algorithms such as MD5 or SHA. This document specifies a standard API for such algorithms, to make it easier to switch between different implementations. Specification All hashing modules should present the same interface. Additional methods or variables can be added, but those described in this document should always be present. Hash function modules define one function: new([string])             (unkeyed hashes) new([key] , [string])     (keyed hashes) Create a new hashing object and return it. The first form is for hashes that are unkeyed, such as MD5 or SHA. For keyed hashes such as HMAC, key is a required parameter containing a string giving the key to use. In both cases, the optional string parameter, if supplied, will be immediately hashed into the object’s starting state, as if obj.update(string) was called. After creating a hashing object, arbitrary strings can be fed into the object using its update() method, and the hash value can be obtained at any time by calling the object’s digest() method. Arbitrary additional keyword arguments can be added to this function, but if they’re not supplied, sensible default values should be used. For example, rounds and digest_size keywords could be added for a hash function which supports a variable number of rounds and several different output sizes, and they should default to values believed to be secure. Hash function modules define one variable: digest_size An integer value; the size of the digest produced by the hashing objects created by this module, measured in bytes. You could also obtain this value by creating a sample object and accessing its digest_size attribute, but it can be convenient to have this value available from the module. Hashes with a variable output size will set this variable to None . Hashing objects require a single attribute: digest_size This attribute is identical to the module-level digest_size variable, measuring the size of the digest produced by the hashing object, measured in bytes. If the hash has a variable output size, this output size must be chosen when the hashing object is created, and this attribute must contain the selected size. Therefore, None is not a legal value for this attribute. Hashing objects require the following methods: copy() Return a separate copy of this hashing object. An update to this copy won’t affect the original object. digest() Return the hash value of this hashing object as a string containing 8-bit data. The object is not altered in any way by this function; you can continue updating the object after calling this function. hexdigest() Return the hash value of this hashing object as a string containing hexadecimal digits. Lowercase letters should be used for the digits a through f . Like the .digest() method, this method mustn’t alter the object. update(string) Hash string into the current state of the hashing object. update() can be called any number of times during a hashing object’s lifetime. Hashing modules can define additional module-level functions or object methods and still be compliant with this specification. Here’s an example, using a module named MD5 : >>> from Crypto.Hash import MD5 >>> m = MD5 . new () >>> m . digest_size 16 >>> m . update ( 'abc' ) >>> m . digest () '\x90\x01P\x98<\xd2O\xb0\xd6\x96?}(\xe1\x7fr' >>> m . hexdigest () '900150983cd24fb0d6963f7d28e17f72' >>> MD5 . new ( 'abc' ) . digest () '\x90\x01P\x98<\xd2O\xb0\xd6\x96?}(\xe1\x7fr' Rationale The digest size is measured in bytes, not bits, even though hash algorithm sizes are usually quoted in bits; MD5 is a 128-bit algorithm and not a 16-byte one, for example. This is because, in the sample code I looked at, the length in bytes is often needed (to seek ahead or behind in a file; to compute the length of an output string) while the length in bits is rarely used. Therefore, the burden will fall on the few people actually needing the size in bits, who will have to multiply digest_size by 8. It’s been suggested that the update() method would be better named append() . However, that method is really causing the current state of the hashing object to be updated, and update() is already used by the md5 and sha modules included with Python, so it seems simplest to leave the name update() alone. The order of the constructor’s arguments for keyed hashes was a sticky issue. It wasn’t clear whether the key should come first or second. It’s a required parameter, and the usual convention is to place required parameters first, but that also means that the string parameter moves from the first position to the second. It would be possible to get confused and pass a single argument to a keyed hash, thinking that you’re passing an initial string to an unkeyed hash, but it doesn’t seem worth making the interface for keyed hashes more obscure to avoid this potential error. Changes 2001-09-17: Renamed clear() to reset() ; added digest_size attribute to objects; added .hexdigest() method. 2001-09-20: Removed reset() method completely. 2001-09-28: Set digest_size to None for variable-size hashes. Acknowledgements Thanks to Aahz, Andrew Archibald, Rich Salz, Itamar Shtull-Trauring, and the readers of the python-crypto list for their comments on this PEP. Copyright This document has been placed in the public domain. Source: https://github.com/python/peps/blob/main/peps/pep-0247.rst Last modified: 2025-02-01 08:59:27 GMT Contents Abstract Specification Rationale Changes Acknowledgements Copyright Page Source (GitHub) | 2026-01-13T08:49:06 |
https://dev.to/missamarakay/following-cooking-recipes-makes-you-a-clearer-writer-460a#jargon | Following Cooking Recipes Makes You a Clearer Writer - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Amara Graham Posted on Jul 17, 2019 Following Cooking Recipes Makes You a Clearer Writer # devrel # documentation I'm really into cooking, baking, pickling, really anything that will end in me eating something delicious. But I didn't find it enjoyable or "get good" at cooking overnight. My parents cooked most of our meals and if you planned on eating said meal, you were required to provide some amount of assistance, regardless of your blood relation to the family. After graduating out of dorm life I realized I needed to feed myself or starve, so I started getting bolder with my kitchen experiments and I'm pleased to say I'm still alive. "Ok Amara, but where is the tech components of this blog?" Hold on, I'm setting up the metaphor. "Ok fine." In the Kitchen If you stand in a kitchen and watch my dad cook - he reads a recipe, studies it, then goes through and pulls out all the things he needs to make it happen. For banana bread he usually has to pull the frozen bananas out early to thaw them enough to peel them, he portions out the spices so he can toss them in while mixing, he sprays the loaf pan before the mixture is together. If you watched me in my first apartment attempting banana bread for the first time, you would have seen someone who barely read the recipe (I've made this before, with supervision, and watched my dad make it for years, how hard can it be?) and did exactly every step of the instruction in series. Pull frozen bananas out of the freezer, immediately realize you can't peel a banana when its extra frozen, wait just long enough you can pry the peel off, smash the mostly still frozen bananas, slowly add each spice one at a time, measuring as you go, mix everything together, spray the pan, realize the oven isn't on, wait to pre-heat, blah blah blah, why did this take double the prep time? My dad has always taken the methodical approach to everything, he's a chemist and he loves math. I'm impatient and can't spend even 30 seconds idle when I know I need to complete a task, so I pretty much have the attention span of a Border Collie (have you seen those dogs stare at a ball, full body shaking with excitement?). At My Desk I'm sure you'll be shocked to hear when I sit down to learn some kind of new tech, I barely skim the tutorial or docs, immediately start the "doing", and often end up frustrated and annoyed with the experience. In some cases I tell myself things like "oh I've used an API like this before, I can just make it work" and 3 days later I'm banging my head on the keyboard. "Amara, just slow down and actually read the tutorial." Easier said than done. Not just for me personally, but for any dev, and that includes your dev coworkers, customers, community, etc. Time is precious, workplaces are more agile than ever, and people pay money for other people to stand in line for them. In My Brain Now recipes, just like tutorials, can be poorly written, but even the good ones can suffer from poor execution as I rambled on above. There are 5 things I learned from getting better at following cooking recipes that I think apply to written technical content. Ambiguous Terms Jargon Chunking Brevity Audience Let's take a look at each one. Ambiguous Terms Have you ever read a recipe, seen the word "mix" and go... with a spoon? A stand mixer? How long? Or how about "hand mix"? Did you know that a 'Hand Mixer' is an appliance and not the things at the end of your arms? Because a few years ago when we first started dating, my now husband did not. In tech, we love using the same term for a number of different things. Or we have a number of different words for the same thing. Really friendly to beginners right? Something like "Run this" might make sense to you, the engineer who built it, because its probably never crossed your mind that you run it globally and not in a particular directory (or vice versa) but that can be one of the most irritating things for a dev struggling with the worry of doing something wrong and/or irreversible. Be explicit in your use of terms and maybe consider a glossary of terms relevant to your project/product/industry/company. What does this mean in this context, right here, right now? Don't leave your reading punching out to search for answers. Jargon Every talk I've given on AI to beginners has included a disclaimer about not only ambiguous terminology but jargon. 'Fine-tuning' is not super intuitive, neither is 'hyperparameter'. 'Fold in' or 'soft peaks' in cooking is right up there too. Mastering the jargon can disrupt retention of fundamental topics. Explaining these terms early in docs and tutorials is crucial. You should not assume knowledge of jargon, so this is another +1 for a glossary. Chunking I am a huge fan of multi-part tutorials and how-to series, so long as they are done right. At the end of each part in a series, you should have a small complete something. Developers may not have time to sit down and do a 3-6 hour tutorial, but they should be able to get 20 minutes to an hour of uninterrupted time. You don't want to tackle a slow cooker recipe at 5pm expecting to eat it for dinner, but you may want to brown some meat so it is ready to toss in the next morning. If I have 20 minutes today to set myself up for success later today or tomorrow, I need to know I can get it done in the allocated time. And I need to feel like I can pick it up again without rereading the entire thing. Brevity Unlike this blog which is probably way too long for most of you, the more concise your written technical content the easier its going to be to follow. It's part of what makes the Tasty videos so appealing to watch - someone makes a sped up, top-down recipe that feels fast and easy even if its neither. This doesn't mean you can't write an introduction or a conclusion that goes more in depth about the content, but when you get to the meat of the docs or tutorial it should be a lean, mean, executing machine. Food bloggers are great at this, they may give you step-by-step pictures and commentary, but they almost always include the recipe separately. So feel free to tell me how you are going to save the world with this tutorial, but keep it out of the exact steps I'm following so I don't get overwhelmed. Audience This is maybe the most important, although I could argue that they all are. Knowing your developer audience is extremely important in technical writing. This helps you make decisions about what languages and references to use, what their workstation may look like, and maybe even things like their attention span. If your audience is students, whether they will admit it or not, they tend to have WAY more time to sit down and really study a tutorial. Or maybe they are participating in a hackathon and it just needs to work as fast as possible. But maybe your audience is enterprise developers, like mine often is. This means it has to be production-ready, maintainable, and even trainable across teams. Your maintenance team may be entirely separate from your product engineering team, so the content they follow may need to be different. Knowing or identifying your audience can be challenging, but this is a great opportunity for your devrel team to really shine. Celebrate Those Incremental Improvements Like I mentioned earlier, I didn't wake up one day and realize if I actually read the recipe, prepped ahead of time, and researched how to do certain kitchen techniques (again, ahead of time), I could maximize my time in the kitchen and feel less overwhelmed. In fact, I'm probably 50:50 in my ability to prep and run in parallel or haphazardly skim in series today. But snaps for me because this week I measured everything out before I started cooking! I'm sure you could make an argument that my dad is a 'senior' in the kitchen and I'm not (but I'm also not junior either), but he'd prefer you only use 'senior' when used in conjunction with "senior discount" at this point in his life. Let's say 'seasoned'. Whether you are a junior or senior dev, you still need the content you are consuming to prepare you for success. But with more and more folks using services like Blue Apron, Hello Fresh, Home Chef, arguably boxed Bootcamp experiences for the kitchen, we have a new generation of folks training themselves how to follow recipes and we can translate that experience into the tech world, allowing for more confident, empowered folks in the kitchen and at the keyboard. So instead of shouting "read the docs" or "follow the tutorial" make sure your content is as consumable and delicious as a home cooked meal. Top comments (5) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Jason C. McDonald Jason C. McDonald Jason C. McDonald Follow Author. Speaker. Time Lord. (Views are my own) Email codemouse92@outlook.com Location Time Vortex Pronouns he/him Work Author of "Dead Simple Python" (No Starch Press) Joined Jan 31, 2017 • Aug 5 '19 Dropdown menu Copy link Hide Excellent write up! I'm actually going to include this on the #beginners tag wiki for authors to read. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand JeffD JeffD JeffD Follow Code-quality 🩺 Teamwork 🐝 & everything that can simplify the developper's life 🗂️. Location France Joined Oct 16, 2017 • Sep 16 '19 Dropdown menu Copy link Hide This post is a must-read ! It's perfect 🏆 ("Hold on, I'm setting up the metaphor." 🤣) Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Alvarez García Alvarez García Alvarez García Follow After more than 10 years backending, now trying to make this CSS properties work. Location Buenos Aires, Argentina Work FullStack Joined Apr 24, 2019 • Jul 25 '19 Dropdown menu Copy link Hide DevRel in construction here, thanks for this really simple and enjoyable post. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Amara Graham Amara Graham Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 • Jul 25 '19 Dropdown menu Copy link Hide Thank you! :) Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Shashamura1 Shashamura1 Shashamura1 Follow Hi everyone my name is daniel.gentle loving caring I’am a type of person that always optimistic in every thing that I doing im very couriours and ambitious to lean I’m very new in this site Email ashogbondaniel292@gmail.com Location USA Education Technical college Work CEO at mylocallatest ...https://mylocallatest512644105.wordpress.com Joined Sep 12, 2022 • Oct 8 '22 Dropdown menu Copy link Hide Nice post I can use it to learn as project in dev.com ..to share the interest story of cooking Like comment: Like comment: 1 like Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Amara Graham Follow Enabling developers Location Austin, TX Education BS Computer Science from Trinity University Work Developer Advocate at Kestra Joined Jan 4, 2017 More from Amara Graham Moving Config Docs From YAML to Markdown # documentation # yaml # markdown Moving DevEx from DevRel to Engineering # devrel # devex # engineering # reorg Bing Webmaster Tools De-indexed My Docs Site and Increased My Cognitive Load # webdev # seo # documentation 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:49:06 |
https://www.python.org/community/logos/#python-network | The Python Logo | Python Software Foundation Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Mission Statement Board of Directors & Officers PSF Staff Annual Impact Report Fiscal Sponsorees Public Records Legal & Policies PSF FAQ Developers in Residence Sponsorship PSF Sponsors Apply to Sponsor Sponsorship Prospectus 2025-26 Membership Sign up as a Member of the PSF! Membership FAQ PSF Elections Nominate a Fellow & Fellows Roster Donate End of year fundraiser 2025: Python is for Everyone Donate to the PSF Become a Supporting Member of the PSF PSF Matching Donations Volunteer Volunteer for the PSF PSF Work Groups Volunteer for PyCon US Grants Grants program Grants Program FAQ PyCon US News & Community Subscribe to the Newsletter PSF Blog Python Community Code of Conduct Community Awards Discourse PSF >>> Logo The Python Logo The Python Logo Projects and companies that use Python are encouraged to incorporate the Python logo on their websites, brochures, packaging, and elsewhere to indicate suitability for use with Python or implementation in Python. Use of the "two snakes" logo element alone (the logo device), without the accompanying wordmark is permitted on the same terms as the combined logo. Combined logo: Logo device only: Currently, the following larger sized and vector variants of the logo are available: PNG format -- the original master which should open as a vector image in Adobe Fireworks PNG format (flattened) Photoshop format SVG format (generic SVG export from Inkscape) SVG format (Inkscape-specific SVG) SVG format of only "two snakes" PNG format (269 × 326) of only "two snakes" The font used in the logo is called "Flux Regular". The PSF owns a copy but we cannot distribute it, except for work on the PSF's behalf. The Python Powered Logo The official Python Powered logo is available in two forms, wide and tall: This logo available in sizes 200x80 , 140x56 , 100x40 , and 70x28 . Also as SVG format source file. This logo available in sizes 140x182 , 100x130 , 70x91 , and 50x65 . Also as SVG format source file. Guidelines for Use The Python logo is a trademark of the Python Software Foundation, which is responsible for defending against any damaging or confusing uses of the trademark. See the PSF Trademark Usage Policy . In general, we want the logo to be used as widely as possible to indicate use of Python or suitability for Python. However, please ask first when using a derived version of the logo or when in doubt. T-shirts and other Merchandise Making your own shirts and other items featuring the Python logo is OK, but please seek permission from the PSF if you are planning to sell merchandise that shows the Python logo. The PSF The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission. ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://www.python.org/success-stories/python-for-collaborative-robots/ | Python for Collaborative Robots | Our Success Stories | Python.org Notice: While JavaScript is not essential for this website, your interaction with the content will be limited. Please turn JavaScript on for the full experience. Skip to content ▼ Close Python PSF Docs PyPI Jobs Community ▲ The Python Network Donate ≡ Menu Search This Site GO A A Smaller Larger Reset Socialize LinkedIn Mastodon Chat on IRC Twitter About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Python for Collaborative Robots Written by Ilya Grozov , Rozum Robotics At Rozum Robotics our mission is to create safe and easy to use collaborative robotic arms. We are striving to make robots that could be integrated into different workspaces and industries as quickly as possible. Moreover, the goal is not only for the end-users to be able to use robots with the help of UI, but also to develop complex industrial-grade applications that could take advantage of the full potential of the robot and auxiliary devices. When there was a discussion in the company about what programming language to use for such purposes, there were plenty of strong and mature competitors (e.g. Java and C/C++), but the advantages of Python beat all other options. The process of designing, implementing, and making Python API for the Pulse robotic arm public was our first successful experience. The simplicity of development and setup which, in basic cases, include installation of the interpreter, running one pip install command, and writing several lines of code to get access to the robot functionality, led to the intensive expansion of the language into the company’s processes and codebase. For example, our QA team started creating automated testing pipelines using the open-source tooling provided by the community. This reduced the time needed to test the systems from days to hours. But, of course, the main benefit was that we created an opportunity to develop high-level applications that use our robot for everyone who owns one. After achieving promising results with the robot API, we chose the next milestone. Robotic arms are not the only product of the company ― we have our servo-motors, and we wanted to control them using Python, too. The motors API is written in C, so it was not a problem to wrap it with Python. And again, this tiny library and wide choice of open-source libraries helped us to build diverse infrastructure. For instance: various testing stands with auto-generated reports and automatic notification of the results, as well as research applications gave us a possibility to make our hardware and software even better. Needless to say, it helped to establish a “plug and play” experience for the end-users. And here comes the next story where Python plays a crucial role in our Rozum Cafe project. It started as a fun project for the evening but has grown into an industrial application. The language has become the glue that combined all the parts, including robotic arm control, payment processing, system state monitoring, etc. The future plans for Python expansion in our company include several topics. First of all, we are building custom execution runtimes for user programs. It should provide a safe (from the robotics perspective) and easy to use environment that would have access both to the rich Python functionality and packages and to the robotic arm facilities. Secondly, we continue the automation of the research and development activities in order to reduce the time and effort needed to perform necessary computations and analysis. Thirdly, our integration team is working on robotic solutions for different industries, and Python has become their best friend that helps during prototyping and industrial integration. Conclusion The stories that are set out in this article are just some of the examples of how Python influences the robotics field. The Python community deserves an honorable mention for the wonderful packages and language it is creating and improving. Here is a shortlist of the ones that we use: NumPy, Matplotlib, Pandas, PyTorch, Jupyter, Flask, FastAPI, SQLAlchemy, Gunicorn, Requests, PyTest, Cookiecutter, ROS libraries, and many many others. The people standing behind the Python ecosystem are truly amazing, and we wish them (and us) to continue their productive work to make the world better! About the Author Ilya Grozov is a Software Engineer and Robotics researcher at Rozum Robotics. Success stories home Arts Business Data Science Education Engineering Government Scientific Software Development Submit Yours! ▲ Back to Top About Applications Quotes Getting Started Help Python Brochure Downloads All releases Source code Windows macOS Android Other Platforms License Alternative Implementations Documentation Docs Audio/Visual Talks Beginner's Guide FAQ Non-English Docs PEP Index Python Books Python Essays Community Diversity Mailing Lists IRC Forums PSF Annual Impact Report Python Conferences Special Interest Groups Python Logo Python Wiki Code of Conduct Community Awards Get Involved Shared Stories Success Stories Arts Business Education Engineering Government Scientific Software Development News Python News PSF Newsletter PSF News PyCon US News News from the Community Events Python Events User Group Events Python Events Archive User Group Events Archive Submit an Event Contributing Developer's Guide Issue Tracker python-dev list Core Mentorship Report a Security Issue ▲ Back to Top Help & General Contact Diversity Initiatives Submit Website Bug Status Copyright ©2001-2026. Python Software Foundation Legal Statements Privacy Notice Powered by PSF Community Infrastructure --> | 2026-01-13T08:49:06 |
https://vitejs.dev/guide/#scaffolding-your-first-vite-project | Getting Started | Vite The Unified Toolchain for the Web Learn more Skip to content Vite Search Main Navigation Guide Config Plugins Resources Team Blog Releases The Documentary Bluesky Mastodon X Discord Chat Awesome Vite ViteConf DEV Community v7.2.7 Changelog Contributing Unreleased Docs Vite 6 Docs Vite 5 Docs Vite 4 Docs Vite 3 Docs Vite 2 Docs English 简体中文 日本語 Español Português 한국어 Deutsch فارسی English 简体中文 日本語 Español Português 한국어 Deutsch فارسی Appearance Menu Return to top Sidebar Navigation Introduction Getting Started Philosophy Why Vite Guide Features CLI Using Plugins Dependency Pre-Bundling Static Asset Handling Building for Production Deploying a Static Site Env Variables and Modes Server-Side Rendering (SSR) Backend Integration Troubleshooting Performance Rolldown Migration from v6 Breaking Changes APIs Plugin API HMR API JavaScript API Config Reference Environment API Introduction Environment Instances Plugins Frameworks Runtimes On this page Building Together ViteConf 2025 View the replays Are you an LLM? You can read better optimized documentation at /guide.md for this page in Markdown format Getting Started Overview Vite (French word for "quick", pronounced /vit/ , like "veet") is a build tool that aims to provide a faster and leaner development experience for modern web projects. It consists of two major parts: A dev server that provides rich feature enhancements over native ES modules , for example extremely fast Hot Module Replacement (HMR) . A build command that bundles your code with Rollup , pre-configured to output highly optimized static assets for production. Vite is opinionated and comes with sensible defaults out of the box. Read about what's possible in the Features Guide . Support for frameworks or integration with other tools is possible through Plugins . The Config Section explains how to adapt Vite to your project if needed. Vite is also highly extensible via its Plugin API and JavaScript API with full typing support. You can learn more about the rationale behind the project in the Why Vite section. Browser Support During development, Vite assumes that a modern browser is used. This means the browser supports most of the latest JavaScript and CSS features. For that reason, Vite sets esnext as the transform target . This prevents syntax lowering, letting Vite serve modules as close as possible to the original source code. Vite injects some runtime code to make the development server work. These code use features included in Baseline Newly Available at the time of each major release (2025-05-01 for this major). For production builds, Vite by default targets Baseline Widely Available browsers. These are browsers that were released at least 2.5 years ago. The target can be lowered via configuration. Additionally, legacy browsers can be supported via the official @vitejs/plugin-legacy . See the Building for Production section for more details. Trying Vite Online You can try Vite online on StackBlitz . It runs the Vite-based build setup directly in the browser, so it is almost identical to the local setup but doesn't require installing anything on your machine. You can navigate to vite.new/{template} to select which framework to use. The supported template presets are: JavaScript TypeScript vanilla vanilla-ts vue vue-ts react react-ts preact preact-ts lit lit-ts svelte svelte-ts solid solid-ts qwik qwik-ts Scaffolding Your First Vite Project npm Yarn pnpm Bun Deno bash $ npm create vite@latest bash $ yarn create vite bash $ pnpm create vite bash $ bun create vite bash $ deno init --npm vite Then follow the prompts! Compatibility Note Vite requires Node.js version 20.19+, 22.12+. However, some templates require a higher Node.js version to work, please upgrade if your package manager warns about it. Using create vite with command line options You can also directly specify the project name and the template you want to use via additional command line options. For example, to scaffold a Vite + Vue project, run: npm Yarn pnpm Bun Deno bash # npm 7+, extra double-dash is needed: $ npm create vite@latest my-vue-app -- --template vue bash $ yarn create vite my-vue-app --template vue bash $ pnpm create vite my-vue-app --template vue bash $ bun create vite my-vue-app --template vue bash $ deno init --npm vite my-vue-app --template vue See create-vite for more details on each supported template: vanilla , vanilla-ts , vue , vue-ts , react , react-ts , react-swc , react-swc-ts , preact , preact-ts , lit , lit-ts , svelte , svelte-ts , solid , solid-ts , qwik , qwik-ts . You can use . for the project name to scaffold in the current directory. To create a project without interactive prompts, you can use the --no-interactive flag. Community Templates create-vite is a tool to quickly start a project from a basic template for popular frameworks. Check out Awesome Vite for community maintained templates that include other tools or target different frameworks. For a template at https://github.com/user/project , you can try it out online using https://github.stackblitz.com/user/project (adding .stackblitz after github to the URL of the project). You can also use a tool like degit to scaffold your project with one of the templates. Assuming the project is on GitHub and uses main as the default branch, you can create a local copy using: bash npx degit user/project#main my-project cd my-project npm install npm run dev Manual Installation In your project, you can install the vite CLI using: npm Yarn pnpm Bun Deno bash $ npm install -D vite bash $ yarn add -D vite bash $ pnpm add -D vite bash $ bun add -D vite bash $ deno add -D npm:vite And create an index.html file like this: html < p >Hello Vite!</ p > Then run the appropriate CLI command in your terminal: npm Yarn pnpm Bun Deno bash $ npx vite bash $ yarn vite bash $ pnpm vite bash $ bunx vite bash $ deno run -A npm:vite The index.html will be served on http://localhost:5173 . index.html and Project Root One thing you may have noticed is that in a Vite project, index.html is front-and-central instead of being tucked away inside public . This is intentional: during development Vite is a server, and index.html is the entry point to your application. Vite treats index.html as source code and part of the module graph. It resolves <script type="module" src="..."> that references your JavaScript source code. Even inline <script type="module"> and CSS referenced via <link href> also enjoy Vite-specific features. In addition, URLs inside index.html are automatically rebased so there's no need for special %PUBLIC_URL% placeholders. Similar to static http servers, Vite has the concept of a "root directory" which your files are served from. You will see it referenced as <root> throughout the rest of the docs. Absolute URLs in your source code will be resolved using the project root as base, so you can write code as if you are working with a normal static file server (except way more powerful!). Vite is also capable of handling dependencies that resolve to out-of-root file system locations, which makes it usable even in a monorepo-based setup. Vite also supports multi-page apps with multiple .html entry points. Specifying Alternative Root Running vite starts the dev server using the current working directory as root. You can specify an alternative root with vite serve some/sub/dir . Note that Vite will also resolve its config file (i.e. vite.config.js ) inside the project root, so you'll need to move it if the root is changed. Command Line Interface In a project where Vite is installed, you can use the vite binary in your npm scripts, or run it directly with npx vite . Here are the default npm scripts in a scaffolded Vite project: package.json json { "scripts" : { "dev" : "vite" , // start dev server, aliases: `vite dev`, `vite serve` "build" : "vite build" , // build for production "preview" : "vite preview" // locally preview production build } } You can specify additional CLI options like --port or --open . For a full list of CLI options, run npx vite --help in your project. Learn more about the Command Line Interface Using Unreleased Commits If you can't wait for a new release to test the latest features, you can install a specific commit of Vite with https://pkg.pr.new : npm Yarn pnpm Bun bash $ npm install -D https://pkg.pr.new/vite@SHA bash $ yarn add -D https://pkg.pr.new/vite@SHA bash $ pnpm add -D https://pkg.pr.new/vite@SHA bash $ bun add -D https://pkg.pr.new/vite@SHA Replace SHA with any of Vite's commit SHAs . Note that only commits within the last month will work, as older commit releases are purged. Alternatively, you can also clone the vite repo to your local machine and then build and link it yourself ( pnpm is required): bash git clone https://github.com/vitejs/vite.git cd vite pnpm install cd packages/vite pnpm run build pnpm link --global # use your preferred package manager for this step Then go to your Vite based project and run pnpm link --global vite (or the package manager that you used to link vite globally). Now restart the development server to ride on the bleeding edge! To learn more about how and when Vite does releases, check out the Releases documentation. Dependencies using Vite To replace the Vite version used by dependencies transitively, you should use npm overrides or pnpm overrides . Community If you have questions or need help, reach out to the community at Discord and GitHub Discussions . Suggest changes to this page Pager Next page Philosophy Released under the MIT License. (317b3b27) Copyright © 2019-present VoidZero Inc. & Vite Contributors | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/#main-content | HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Welcome to HMPL.js Forem — part of the Forem network! Powerful templates, minimal JS Create account Log in Home About Contact Other Code of Conduct Privacy Policy Terms of Use Twitter Facebook Github Instagram Twitch Mastodon Popular Tags #webdev #programming #javascript #beginners #tutorial #react #opensource #discuss #career #architecture #security #news #api #showdev #frontend #backend #performance #angular #html #tools #vue #ui #help #code #fullstack #npm #bestpractices #vite #integration #migration HMPL.js Forem For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Posts Relevant Latest Top We're launching on ProductHunt Anthony Max Anthony Max Anthony Max Follow Dec 28 '25 We're launching on ProductHunt # news # javascript # showdev Comments Add Comment 1 min read Added a new example of a HATEOAS application: github.com/hmpl-langua... Anthony Max Anthony Max Anthony Max Follow Nov 27 '25 Added a new example of a HATEOAS application: github.com/hmpl-langua... GitHub - hmpl-language/examples: List of sample applications on HMPL List of sample applications on HMPL. Contribute to hmpl-language/examples development by creating an account on GitHub. github.com 5 reactions Comments Add Comment 1 min read hmpl-lang.dev - new website Anthony Max Anthony Max Anthony Max Follow Dec 21 '25 hmpl-lang.dev - new website HMPL.js | HMPL Documentation HMPL.js is a lightweight server-oriented template language for JavaScript. Fetch HTML, render it safely, and keep apps dynamic, modern, and small. Alternative to HTMX and Alpine.js. hmpl-lang.dev 6 reactions Comments Add Comment 1 min read A new example of using the template language: codesandbox.io/p/sandb... Anthony Max Anthony Max Anthony Max Follow Dec 4 '25 A new example of using the template language: codesandbox.io/p/sandb... codesandbox.io 6 reactions Comments Add Comment 1 min read Great news today: we've finally launched a section featuring community projects built with hmpl-js. github.com/hmpl-langua... Anthony Max Anthony Max Anthony Max Follow Nov 20 '25 Great news today: we've finally launched a section featuring community projects built with hmpl-js. github.com/hmpl-langua... GitHub - hmpl-language/projects: A list of community projects built with hmpl-js A list of community projects built with hmpl-js. Contribute to hmpl-language/projects development by creating an account on GitHub. github.com 8 reactions Comments 1 comment 1 min read hello~ seagames seagames seagames Follow Nov 20 '25 hello~ Comments 1 comment 1 min read Major module update! Anthony Max Anthony Max Anthony Max Follow for HMPL.js Nov 17 '25 Major module update! # webdev # javascript # programming # opensource 23 reactions Comments 2 comments 2 min read loading... #discuss Discussion threads targeting the whole community #watercooler Light, and off-topic conversation. 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/new/career | New Post - HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Join the HMPL.js Forem HMPL.js Forem is a community of 3,676,891 amazing developers Continue with Apple Continue with Google Continue with Facebook Continue with Forem Continue with GitHub Continue with Twitter (X) OR Email Password Remember me Forgot password? By signing in, you are agreeing to our privacy policy , terms of use and code of conduct . New to HMPL.js Forem? Create account . 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/contact#main-content | Contact HMPL.js Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account HMPL.js Forem Close Contacts HMPL.js Forem would love to hear from you! Email: support@dev.to 😁 Twitter: @thepracticaldev 👻 Report a vulnerability: dev.to/security 🐛 To report a bug, please create a bug report in our open source repository. To request a feature, please start a new GitHub Discussion in the Forem repo! 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV HMPL.js Forem — For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . HMPL.js Forem © 2016 - 2026. Powerful templates, minimal JS Log in Create account | 2026-01-13T08:49:06 |
https://peps.python.org/topic/packaging/ | Packaging PEPs | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » Packaging PEPs Toggle light / dark / auto colour theme Packaging PEPs Introduction This is the index of all Python Enhancement Proposals (PEPs) labelled under the ‘Packaging’ topic. This is a sub-index of PEP 0 , the PEP index. Packaging PEPs follow the PyPA specification update process . They are used to propose major additions or changes to the PyPA specifications. The canonical, up-to-date packaging specifications can be found on the Python Packaging Authority (PyPA) specifications page. Index by Category Process and Meta-PEPs PEP Title Authors PA 609 Python Packaging Authority (PyPA) Governance Dustin Ingram, Pradyun Gedam, Sumana Harihareswara Provisional PEPs (provisionally accepted; interface may still change) PEP Title Authors SP 708 Extending the Repository API to Mitigate Dependency Confusion Attacks Donald Stufft Accepted PEPs (accepted; may not be implemented yet) PEP Title Authors SA 458 Secure PyPI downloads with signed repository metadata Trishank Karthik Kuppusamy, Vladimir Diaz, Marina Moore, Lukas Puehringer, Joshua Lock, Lois Anne DeLong, Justin Cappos SA 658 Serve Distribution Metadata in the Simple Repository API Tzu-ping Chung SA 668 Marking Python base environments as “externally managed” Geoffrey Thomas, Matthias Klose, Filipe Laíns, Donald Stufft, Tzu-ping Chung, Stefano Rivera, Elana Hashman, Pradyun Gedam SA 691 JSON-based Simple API for Python Package Indexes Donald Stufft, Pradyun Gedam, Cooper Lees, Dustin Ingram SA 714 Rename dist-info-metadata in the Simple API Donald Stufft SA 739 build-details.json 1.0 — a static description file for Python build details Filipe Laíns 3.14 SA 753 Uniform project URLs in core metadata William Woodruff, Facundo Tuesca SA 770 Improving measurability of Python packages with Software Bill-of-Materials Seth Larson SA 794 Import Name Metadata Brett Cannon Open PEPs (under consideration) PEP Title Authors S 480 Surviving a Compromise of PyPI: End-to-end signing of packages Trishank Karthik Kuppusamy, Vladimir Diaz, Justin Cappos, Marina Moore S 694 Upload 2.0 API for Python Package Indexes Barry Warsaw, Donald Stufft, Ee Durbin S 710 Recording the provenance of installed packages Fridolín Pokorný S 711 PyBI: a standard format for distributing Python Binaries Nathaniel J. Smith S 725 Specifying external dependencies in pyproject.toml Pradyun Gedam, Jaime Rodríguez-Guerra, Ralf Gommers S 752 Implicit namespaces for package repositories Ofek Lev, Jarek Potiuk P 755 Implicit namespace policy for PyPI Ofek Lev I 766 Explicit Priority Choices Among Multiple Indexes Michael Sarahan S 771 Default Extras for Python Software Packages Thomas Robitaille, Jonathan Dekhtiar P 772 Packaging Council governance process Barry Warsaw, Deb Nicholson, Pradyun Gedam S 777 How to Re-invent the Wheel Emma Harper Smith S 780 ABI features as environment markers Klaus Zimmermann, Ralf Gommers 3.14 S 783 Emscripten Packaging Hood Chatham S 804 An external dependency registry and name mapping mechanism Pradyun Gedam, Ralf Gommers, Michał Górny, Jaime Rodríguez-Guerra, Michael Sarahan S 807 Index support for Trusted Publishing William Woodruff S 808 Including static values in dynamic project metadata Henry Schreiner, Cristian Le S 815 Deprecate RECORD.jws and RECORD.p7s Konstantin Schütze, William Woodruff S 819 JSON Package Metadata Emma Harper Smith Finished PEPs (done, with a stable interface) PEP Title Authors SF 301 Package Index and Metadata for Distutils Richard Jones 2.3 SF 376 Database of Installed Python Distributions Tarek Ziadé 2.7, 3.2 SF 405 Python Virtual Environments Carl Meyer 3.3 SF 425 Compatibility Tags for Built Distributions Daniel Holth 3.4 SF 427 The Wheel Binary Package Format 1.0 Daniel Holth SF 440 Version Identification and Dependency Specification Alyssa Coghlan, Donald Stufft SF 503 Simple Repository API Donald Stufft SF 508 Dependency specification for Python Software Packages Robert Collins SF 517 A build-system independent format for source trees Nathaniel J. Smith, Thomas Kluyver SF 518 Specifying Minimum Build System Requirements for Python Projects Brett Cannon, Nathaniel J. Smith, Donald Stufft SF 527 Removing Un(der)used file types/extensions on PyPI Donald Stufft SF 561 Distributing and Packaging Type Information Emma Harper Smith 3.7 SF 566 Metadata for Python Software Packages 2.1 Dustin Ingram 3.x SF 592 Adding “Yank” Support to the Simple API Donald Stufft SF 600 Future ‘manylinux’ Platform Tags for Portable Linux Built Distributions Nathaniel J. Smith, Thomas Kluyver SF 610 Recording the Direct URL Origin of installed distributions Stéphane Bidoul, Chris Jerdonek SF 621 Storing project metadata in pyproject.toml Brett Cannon, Dustin Ingram, Paul Ganssle, Pradyun Gedam, Sébastien Eustace, Thomas Kluyver, Tzu-ping Chung SF 625 Filename of a Source Distribution Tzu-ping Chung, Paul Moore SF 627 Recording installed projects Petr Viktorin SF 629 Versioning PyPI’s Simple API Donald Stufft SF 639 Improving License Clarity with Better Package Metadata Philippe Ombredanne, C.A.M. Gerlach, Karolina Surma SF 643 Metadata for Package Source Distributions Paul Moore SF 656 Platform Tag for Linux Distributions Using Musl Tzu-ping Chung SF 660 Editable installs for pyproject.toml based builds (wheel based) Daniel Holth, Stéphane Bidoul SF 685 Comparison of extra names for optional distribution dependencies Brett Cannon SF 700 Additional Fields for the Simple API for Package Indexes Paul Moore SF 715 Disabling bdist_egg distribution uploads on PyPI William Woodruff SF 721 Using tarfile.data_filter for source distribution extraction Petr Viktorin 3.12 SF 723 Inline script metadata Ofek Lev SF 735 Dependency Groups in pyproject.toml Stephen Rosen SF 740 Index support for digital attestations William Woodruff, Facundo Tuesca, Dustin Ingram SF 751 A file format to record Python dependencies for installation reproducibility Brett Cannon SF 792 Project status markers in the simple index William Woodruff, Facundo Tuesca Historical Meta-PEPs and Informational PEPs PEP Title Authors PS 438 Transitioning to release-file hosting on PyPI Holger Krekel, Carl Meyer PF 449 Removal of the PyPI Mirror Auto Discovery and Naming Scheme Donald Stufft PF 464 Removal of the PyPI Mirror Authenticity API Donald Stufft PF 470 Removing External Hosting Support on PyPI Donald Stufft PF 541 Package Index Name Retention Łukasz Langa Deferred PEPs (postponed pending further research or updates) PEP Title Authors ID 423 Naming conventions and recipes related to packaging Benoit Bryon SD 491 The Wheel Binary Package Format 1.9 Daniel Holth SD 778 Supporting Symlinks in Wheels Emma Harper Smith Rejected, Superseded, and Withdrawn PEPs PEP Title Authors SS 241 Metadata for Python Software Packages A.M. Kuchling SW 243 Module Repository Upload Mechanism Sean Reifschneider 2.1 SR 262 A Database of Installed Python Packages A.M. Kuchling SS 314 Metadata for Python Software Packages 1.1 A.M. Kuchling, Richard Jones 2.5 SS 345 Metadata for Python Software Packages 1.2 Richard Jones 2.7 SR 365 Adding the pkg_resources module Phillip J. Eby SW 381 Mirroring infrastructure for PyPI Tarek Ziadé, Martin von Löwis SS 386 Changing the version comparison module in Distutils Tarek Ziadé SR 390 Static metadata for Distutils Tarek Ziadé 2.7, 3.2 IW 396 Module Version Numbers Barry Warsaw SR 402 Simplified Package Layout and Partitioning Phillip J. Eby 3.3 IW 426 Metadata for Python Software Packages 2.0 Alyssa Coghlan, Daniel Holth, Donald Stufft SR 439 Inclusion of implicit pip bootstrap in Python installation Richard Jones 3.4 SW 459 Standard Metadata Extensions for Python Software Packages Alyssa Coghlan IR 496 Environment Markers James Polley IS 513 A Platform Tag for Portable Linux Built Distributions Robert T. McGibbon, Nathaniel J. Smith SR 516 Build system abstraction for pip/conda etc Robert Collins, Nathaniel J. Smith IS 571 The manylinux2010 Platform Tag Mark Williams, Geoffrey Thomas, Thomas Kluyver SR 582 Python local packages directory Kushal Das, Steve Dower, Donald Stufft, Alyssa Coghlan 3.12 IS 599 The manylinux2014 Platform Tag Dustin Ingram SS 631 Dependency specification in pyproject.toml based on PEP 508 Ofek Lev SR 633 Dependency specification in pyproject.toml using an exploded TOML table Laurie Opperman, Arun Babu Neelicattu SW 650 Specifying Installer Requirements for Python Projects Vikram Jayanthi, Dustin Ingram, Brett Cannon SR 662 Editable installs via virtual wheels Bernát Gábor SR 665 A file format to list Python dependencies for reproducibility of an application Brett Cannon, Pradyun Gedam, Tzu-ping Chung SW 704 Require virtual environments by default for package installers Pradyun Gedam SR 722 Dependency specification for single-file scripts Paul Moore SW 759 External Wheel Hosting Barry Warsaw, Emma Harper Smith SW 763 Limiting deletions on PyPI William Woodruff, Alexis Challande PEP Types Key I — Informational : Non-normative PEP containing background, guidelines or other information relevant to the Python ecosystem P — Process : Normative PEP describing or proposing a change to a Python community process, workflow or governance S — Standards Track : Normative PEP with a new feature for Python, implementation change for CPython or interoperability standard for the ecosystem More info in PEP 1 . PEP Status Key A — Accepted : Normative proposal accepted for implementation A — Active : Currently valid informational guidance, or an in-use process D — Deferred : Inactive draft that may be taken up again at a later time <No letter> — Draft : Proposal under active discussion and revision F — Final : Accepted and implementation complete, or no longer active P — Provisional : Provisionally accepted but additional feedback needed R — Rejected : Formally declined and will not be accepted S — Superseded : Replaced by another succeeding PEP W — Withdrawn : Removed from consideration by sponsor or authors More info in PEP 1 . Contents Index by Category Process and Meta-PEPs Provisional PEPs (provisionally accepted; interface may still change) Accepted PEPs (accepted; may not be implemented yet) Open PEPs (under consideration) Finished PEPs (done, with a stable interface) Historical Meta-PEPs and Informational PEPs Deferred PEPs (postponed pending further research or updates) Rejected, Superseded, and Withdrawn PEPs PEP Types Key PEP Status Key | 2026-01-13T08:49:06 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.