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://hmpljs.forem.com/subforems/new#main-content | 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 Information Subforems are New and Experimental Subforems are a new feature that allows communities to create focused spaces within the larger Forem ecosystem. These networks are designed to empower our community to build intentional community around what they care about and the ways they awant to express their interest. Some subforems will be run communally, and others will be run by you . What Subforems Should Exist? What kind of Forem are you envisioning? 🤔 A general Forem that should exist in the world Think big! What community is the world missing? A specific interest Forem I'd like to run myself You have a passion and want to build a community around it. A company-run Forem for our product or ecosystem For customer support, developer relations, or brand engagement. ✓ Thank you for your response. ✓ Thank you for completing the survey! Give us the elevator pitch! What is your Forem about, and what general topics would it cover? 💡 ✓ Thank you for your response. ✓ Thank you for your response. ✓ Thank you for completing the survey! ← Previous Next → Survey completed 💎 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/arunavamodak/react-router-v5-vs-v6-dp0#so-what-is-react-router- | React Router V5 vs V6 - 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 Arunava Modak Posted on Nov 14, 2021 React Router V5 vs V6 # webdev # javascript # react # reactrouter React Router version 6 was released recently, and it is important for us to understand the changes as it is one of the most widely used react libraries out there. So What Is React Router ? React Router is a fully-featured client and server-side routing library for React, a JavaScript library for building user interfaces. React Router runs anywhere React runs; on the web, on the server with node.js, and on React Native. In V6, there has been a lot of under the hood changes, be it an enhanced path pattern matching algorithm or addition of new components. Not only that but the bundle size has been reduced by almost 58%. So here are some of the changes you can make to upgrade an existing project from React Router v5 to v6. Switch Replaced With Routes In v6, Switch in not exported from react-router-dom . In the earlier version we could use Switch to wrap our routes. Now we use Routes to do the same thing instead of Switch . Changes In The Way We Define Our Route The component that should be rendered on matching a route can not be written as children of the Route component, but it takes a prop called element where we have to pass a JSX component for that to be rendered. The exact Prop Is Not Needed Anymore With version 6, React Router has just become alot more awesome. The now better, path matching algorithm, enables us to match a particular route match without the exact prop. Earlier, without exact , any URL starting with the concerned keyword would be loaded, as the matching process was done from top to down the route definitions. But now, we do not have to worry about that, as React Router has a better algorithm for loading the best route for a particular URL, the order of defining does not really matters now. So, to sum up these three points we can consider this code snippet. In v5 import { Switch , Route } from " react-router-dom " ; . . . < Switch > < Route path = " / " > < Home /> < /Route > < Route exact path = " /cryptocurrencies " > < Cryptocurrencies /> < /Route > < Route exact path = " /crypto/:coinId " > < CryptoDetails /> < /Route > < Route exact path = " /exchanges " > < Exchanges /> < /Route > < /Switch > Enter fullscreen mode Exit fullscreen mode In v6 import { Routes , Route } from " react-router-dom " ; . . . < Routes > < Route path = " / " element = { < Home /> } / > < Route path = " /crypto/:coinId " element = { < CryptoDetails /> } / > < Route path = " /cryptocurrencies " element = { < Cryptocurrencies /> } / > < Route path = " /exchanges " element = { < Exchanges /> } / > < /Routes > Enter fullscreen mode Exit fullscreen mode No Need To Install react-router-config Seperately react-router-config allowed us to define our routes as javascript objects, instead of React elements, and all it's functionalities have to moved in the core react router v6. //V5 import { renderRoutes } from " react-router-config " ; const routes = [ { path : " / " , exact : true , component : Home }, { path : " /cryptocurrencies " , exact : true , component : Cryptocurrencies }, { path : " /exchanges " , exact : true , component : Exchanges } ]; export default function App () { return ( < div > < Router > { renderRoutes ( routes )} < /Router > < /div > ); } //V6 function App () { let element = useRoutes ([ // These are the same as the props you provide to <Route> { path : " / " , element : < Home /> }, { path : " /cryptocurrencies " , element : < Cryptocurrencies /> , // Nested routes use a children property children : [ { path : " :coinId " , element : < CryptoDetails /> }, ] }, { path : " /exchanges " , element : < Exchanges /> }, ]); // The returned element will render the entire element // hierarchy with all the appropriate context it needs return element ; } Enter fullscreen mode Exit fullscreen mode useHistory Is Now useNavigate React Router v6 now has the navigate api, which most of the times would mean replacing useHistory to useNavigate . //V5 import { useHistory } from " react-router-dom " ; function News () { let history = useHistory (); function handleClick () { history . push ( " /home " ); } return ( < div > < button onClick = {() => { history . push ( " /home " ); }} > Home < /button > < /div > ); } //V6 import { useNavigate } from " react-router-dom " ; function News () { let navigate = useNavigate (); return ( < div > < button onClick = {() => { navigate ( " /home " ); }} > go home < /button > < /div > ); } Enter fullscreen mode Exit fullscreen mode Some more common features of useHistory were go , goBack and goForward . These can also be achieved by navigate api too, we just need to mention the number of steps we want to move forward or backward ('+' for forward and '-' for backward). So we can code these features we can consider this. //V5 import { useHistory } from " react-router-dom " ; function Exchanges () { const { go , goBack , goForward } = useHistory (); return ( <> < button onClick = {() => go ( - 2 )} > 2 steps back < /button > < button onClick = { goBack } > 1 step back < /button > < button onClick = { goForward } > 1 step forward < /button > < button onClick = {() => go ( 2 )} > 2 steps forward < /button > < / > ); } //V6 import { useNavigate } from " react-router-dom " ; function Exchanges () { const navigate = useNavigate (); return ( <> < button onClick = {() => navigate ( - 2 )} > 2 steps back < /button > < button onClick = {() => navigate ( - 1 )} > 1 step back < /button > < button onClick = {() => navigate ( 1 )} > 1 step forward < /button > < button onClick = {() => navigate ( 2 )} > 2 steps forward < /button > < / > ); } Enter fullscreen mode Exit fullscreen mode activeStyle and activeClassName Props Removed From <NavLink /> In the previous version we could set a seperate class or a style object for the time when the <NavLink/> would be active. In V6, these two props are removed, instead in case of Nav Links className and style props, work a bit differently. They take a function which in turn gives up some information about the link, for us to better control the styles. //V5 < NavLink to = " /news " style = {{ color : ' black ' }} activeStyle = {{ color : ' blue ' }} > Exchanges < /NavLink > < NavLink to = " /news " className = " nav-link " activeClassName = " active " > Exchanges < /NavLink > //V6 < NavLink to = " /news " style = {({ isActive }) => { color : isActive ? ' blue ' : ' black ' }} > Exchanges < /NavLink > < NavLink to = " /news " className = {({ isActive }) => " nav-link " + ( isActive ? " active " : "" )} > Exchanges < /NavLink > Enter fullscreen mode Exit fullscreen mode Replace Redirect with Navigate Redirect is no longer exported from react-router-dom , instead we use can Navigate to achieve the same features. //V5 import { Redirect } from " react-router-dom " ; < Route exact path = " /latest-news " > < Redirect to = " /news " > < /Route > < Route exact path = " /news " > < News /> < /Route > //V6 import { Navigate } from " react-router-dom " ; < Route path = " /latest-news " element = { < Navigate replace to = " /news " > } / > < Route path = " /news " element = { < Home /> } / > Enter fullscreen mode Exit fullscreen mode Please note the replace prop passed inside the element of the Route . This signifies we are replacing the current navigation stack. Without replace it would mean we are just pushing the component in the existing navigation stack. That's it for today. Hope this helps you upgrading your react project, to React Router V6. Thank you for reading !! 😇😇 Happy Coding !! Happy Building !! Top comments (17) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand rkganeshan rkganeshan rkganeshan Follow Joined Aug 28, 2021 • Jul 3 '22 Dropdown menu Copy link Hide Hey @arunavamodak , liked this blog. Crisp content ; differences of the versions as well as the new implementation is dealt very well. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Henrik VT Henrik VT Henrik VT Follow Location Northeast US Joined Mar 7, 2021 • Nov 16 '21 Dropdown menu Copy link Hide As someone who hasn't used React Router, what's the advantage of using this over a framework like Next.js or Gatsby? Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Arunava Modak Arunava Modak Arunava Modak Follow A Software Engineer, in love with building things. Passionate, especially about beautiful UI. Email arunavamodak2@gmail.com Location Bengaluru, India Work Senior Software Engineer @ Rizzle Joined Nov 12, 2021 • Nov 17 '21 Dropdown menu Copy link Hide Well it totally depends on the requirement of your project. If you want an SPA, you can use React and React Router, which takes care of your client-side routing. For something like Next.js it comes with it's own page based routing, I don't think we can implement SPA. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Lesley van der Pol Lesley van der Pol Lesley van der Pol Follow Fullstack Consultant (web) 💻 · Based in The Netherlands Location The Netherlands Education Bachelor Software Engineering Work Fullstack Development Consultant at Passionate People, VodafoneZiggo Joined Aug 2, 2019 • Nov 20 '21 Dropdown menu Copy link Hide I don't think there is an advantage of using React Router over Next.js or Gatsby. If you want the tools that Next or Gatsby offer then it makes sense to just go for those. If you're working on a more vanilla React project then you will generally see something like React Router in place to handle the routing. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Johannes Mogashoa Johannes Mogashoa Johannes Mogashoa Follow Full Stack Javascript and C# developer. Lover of all things problem solving and worthwhile. Email jomogashoa1993@gmail.com Location Johannesburg, South Africa Education Nelson Mandela University Work Software Developer Joined Sep 8, 2020 • Nov 21 '21 Dropdown menu Copy link Hide React Router is directly plugged into Next without you having to install it as a separate dependency. For instance, with Next when you add a new JS/TS or JSX/TSX file into the pages folder, it will automatically map out the path for you without you having to define it. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Mike Robinson Mike Robinson Mike Robinson Follow Joined Nov 12, 2021 • Nov 17 '21 Dropdown menu Copy link Hide Next and Gatsby are full-fledged frameworks and do a LOT more than just routing. If you're already using them, there's no need to use React Router. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Swastik Yadav Swastik Yadav Swastik Yadav Follow Software Engineer || React JS, Next JS, TailwindCSS || Building CatalystUI || Writes about code, AI, and life. Location The Republic of India Joined May 1, 2021 • Nov 15 '21 Dropdown menu Copy link Hide Hey Arunava, Thanks for such nice and detailed explanation about the changes in react-router v6. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Arunava Modak Arunava Modak Arunava Modak Follow A Software Engineer, in love with building things. Passionate, especially about beautiful UI. Email arunavamodak2@gmail.com Location Bengaluru, India Work Senior Software Engineer @ Rizzle Joined Nov 12, 2021 • Nov 17 '21 Dropdown menu Copy link Hide Thanks man. Just looking to contribute something to the community Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand rancy98 rancy98 rancy98 Follow Work Frontend Enginner Joined Jul 7, 2021 • Nov 16 '21 Dropdown menu Copy link Hide quality sharing！ Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Ferdiansyah Ferdiansyah Ferdiansyah Follow Location localhost:3000 Work Frontend Developer Joined Aug 31, 2020 • Nov 15 '21 Dropdown menu Copy link Hide nice👏 Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand th3c0r th3c0r th3c0r Follow Joined Sep 24, 2020 • Nov 15 '21 Dropdown menu Copy link Hide Very nice article! Also a good video tutorial from Academind youtu.be/zEQiNFAwDGo Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Kristofer Pervin Kristofer Pervin Kristofer Pervin Follow Work Full Stack Developer at Adaptiiv Medical Technologies Inc Joined Nov 20, 2021 • Nov 20 '21 • Edited on Nov 20 • Edited Dropdown menu Copy link Hide At some point can you add in built-in Protected Routes? It would be quite the convenience feature. Otherwise this looks great! Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Mike Robinson Mike Robinson Mike Robinson Follow Joined Nov 12, 2021 • Nov 17 '21 Dropdown menu Copy link Hide There's also an official upgrading guide: github.com/remix-run/react-router/... Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand 77pintu 77pintu 77pintu Follow Joined Apr 5, 2020 • Oct 2 '22 Dropdown menu Copy link Hide Thanks for the great post!!! Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Daniel OUATTARA Daniel OUATTARA Daniel OUATTARA Follow Joined Mar 28, 2022 • Apr 5 '22 Dropdown menu Copy link Hide Thank you ! Like comment: Like comment: 1 like Like Comment button Reply View full discussion (17 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 Arunava Modak Follow A Software Engineer, in love with building things. Passionate, especially about beautiful UI. Location Bengaluru, India Work Senior Software Engineer @ Rizzle Joined Nov 12, 2021 Trending on DEV Community Hot AI should not be in Code Editors # programming # ai # productivity # discuss What makes a good tech Meet-up? # discuss # community # a11y # meet Meme Monday # discuss # watercooler # jokes 💎 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/programming | 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://www.python.org/community/workshops/#site-map | Conferences and Workshops | 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 >>> Python Conferences Conferences and Workshops Conference Listings There are quite a number of Python conferences happening all year around and in many parts of the world. Many of them are taking place yearly or even more frequent: Python Conferences List on the Python Wiki -- this is the main and most complete list of conferences around the world Subsets of this list are also available on other sites: pycon.org -- lists a subset of mostly national Python conferences PyData -- listings of Python conferences specializing in AI & Data Science Several of these conferences record the talk sessions on video. pyvideo.org provides an index to a large set these videos. Announcing Events If you would like to announce a Python related event, please see Submitting an event to the Python events calendars . You can also ask on pydotorg-www at python dot org for help. Adding Conferences If you have an event to add, please see the instructions on how to edit Python Wiki for details. If you are organizing a Python conference or thinking of organizing one, please subscribe to the Python conferences mailing list . 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/logos/#content | 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://peps.python.org/pep-0732/ | PEP 732 – The Python Documentation Editorial Board | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 732 Toggle light / dark / auto colour theme PEP 732 – The Python Documentation Editorial Board Author : Joanna Jablonski Sponsor : Mariatta Wijaya Discussions-To : Discourse thread Status : Active Type : Process Topic : Governance Created : 14-Oct-2023 Post-History : 20-Oct-2023 Resolution : Discourse message Table of Contents Abstract Motivation Specification Mandate Responsibilities Scope Composition Editorial Board Members Editorial Board Member Qualifications Term Changes to the Editorial Board’s Size Vacancies Amendments PEP Acceptance Contact Copyright Abstract This PEP: Establishes the Python Documentation Editorial Board Proposes how the editorial board will work Motivation The Steering Council approved the creation of a Documentation Working Group in March 2021 to set direction for the docs. This group is now called the Editorial Board to differentiate it from the Documentation Working Group that was created since then to focus on more tactical work. The purpose of the Python documentation is to serve the present and future end users of Python. As such, the core development community and the greater Python documentation contributors work together to achieve this: Specification Mandate The editorial board will: Ensure processes are in place to maintain and improve the quality of Python’s documentation Foster Python documentation as a community resource to serve the current and future users Act in alignment with the Python Software Foundation mission , which is to advance the Python programming language, and to support and facilitate the growth of a diverse and international community of Python programmers Ensure that contributing to documentation is accessible, inclusive, and sustainable Establish appropriate decision-making processes for documentation content Seek to achieve consensus among contributors prior to making decisions Be the final arbiter for documentation content decisions Responsibilities The board has authority to make decisions about Python’s documentation, as scoped below. For example, it can: Set big-picture strategy for Python’s documentation Set the intended structure for documentation Make style and editorial decisions for both writing and design Handle documentation governance (for example, delegation of decision-making to subject-matter experts, resolution of disagreements, decisions.) Scope The Editorial board oversees the content and strategy for the following: In scope Not in scope CPython documentation (docs.python.org) Code comments in CPython codebase CPython devguide (devguide.python.org) CPython docstrings Translations of CPython docs PEPs (peps.python.org) PyPA documentation www.python.org The Python Wiki (wiki.python.org) Composition The Python Documentation Editorial Board is composed of five members. Editorial Board Members The initial Editorial Board members are: Mariatta Wijaya Ned Batchelder Joanna Jablonski Guido van Rossum Carol Willing Editorial Board Member Qualifications Editorial board members should have: A good grasp of the philosophy of the Python project A background in Python education and developer-facing documentation A solid track record of being constructive and helpful A history of making significant contributions to Python A willingness to dedicate time to improving Python’s docs Members of the Editorial Board should have experience in education, communication, technical writing, Python’s documentation, accessibility, translation, or community management. Term Editorial Board members serve for an indefinite term, though it is generally expected that there will be changes in Editorial Board composition each year. Editorial Board members will confirm annually whether they wish to continue as a board member. Members may resign at any time. If a board member drops out of touch and cannot be contacted for a month or longer, then the rest of the board may vote to replace them. Changes to the Editorial Board’s Size Annually after each major Python release, the Editorial Board will review whether the board’s size should change. This provides flexibility if the needs of the documentation community change over time. A simple majority is needed to make a decision to increase the board’s size where quorum is 80% of the current board. As the sponsoring organization of the Documentation Editorial Board, the Steering Council may change the number of members of the Board at any time, including appointing new members or dismissing existing members. Vacancies If a vacancy exists on the board for any reason, the Documentation Editorial Board will publicly announce a call for prospective board members. Prospective board members would submit a brief document stating qualifications and their motivation to serve. The sitting members of the Editorial Board will select new board members by a simple majority where quorum is 80% of the current board. Amendments This PEP serves as a charter for the Docs Editorial Board. Changes to its operation can be made either through a new PEP or through a change to this PEP. In either case, the change would be decided upon by the Steering Council after discussion in the community. PEP Acceptance PEP 732 was accepted by the Python Steering Council on December 11, 2023 . The Steering Council commented that, while they don’t disagree with the scoping set out in the PEP, it would probably make sense for the Editorial Board to consider expanding the scope to include docstrings in the standard library, once the Board is sufficiently established and the higher priorities have been taken care of. Contact To ask the Editorial Board for a decision, community members may open an issue in the python/editorial-board repository. 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-0732.rst Last modified: 2025-02-01 07:28:42 GMT Contents Abstract Motivation Specification Mandate Responsibilities Scope Composition Editorial Board Members Editorial Board Member Qualifications Term Changes to the Editorial Board’s Size Vacancies Amendments PEP Acceptance Contact Copyright Page Source (GitHub) | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/t/programming#main-content | Programming - 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 Programming Follow Hide The magic behind computers. 💻 🪄 Create Post Older #programming posts 1 2 3 4 5 6 7 8 9 … 75 … 3611 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu 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 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://www.python.org/success-stories/category/software-development/#content | Software Development | 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 >>> Software Development Software Development Python on Arm: 2025 Update Zama Concrete ML: Simplifying Homomorphic Encryption for Python Machine Learning Building Robust Codebases with Python's Type Annotations Building a Dependency Graph of Our Python Codebase Bleeding Edge Dependency Testing Using Python How We Created a Python Development Framework for Non-Developers Vacation rental marketplace development using Python Deliver Clean and Safe Code for Your Python Applications A Startup Healthcare Tech Firm Is Now Poised for the Future Using Python to build a range of products across multiple industries Using Python for marketplace development under tight deadlines Using Python to develop a patient health portal Building an online pharmacy marketplace with Python Python provides convenience and flexibility for scalable ML/AI Securing Python Runtimes Building an open-source and cross-platform Azure CLI with Python D-Link Australia Uses Python to Control Firmware Updates Distributed System For Technology Integration EZRO Content Management System Avoiding Documentation Costs with Python A Custom Image Viewing Game for an Autistic Child XIST: An XML Transformation Engine 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://youtube.com/t/contact_us/ | 문의하기 KR YouTube 정보 커뮤니티 가이드 문의하기 채용정보 문의하기 도움이 필요한 경우 YouTube 고객센터 를 방문하세요. 계정 만들기, 동영상 보기 및 업로드, 채널 관리 등 여러 가지 일반적인 질문에 대한 답을 찾을 수 있습니다. 고객센터에서 원하는 내용을 찾을 수 없는 경우 커뮤니티 도움말 포럼 을 방문해 보세요. 버그가 있습니까? 현재 사이트 관련 문제 페이지에서, 이미 알려진 문제 중 현재 수정 작업이 진행되고 있는 문제의 목록을 살펴보세요. 기업 홍보 프레스룸 이 공간 에서는 미디어 연락처 정보, 보도자료, B-Roll 영상 자료, FAQ, 대화식 YouTube 연혁을 제공합니다. 파트너 프로그램 YouTube 파트너 프로그램에 가입하려면 정보 페이지 를 방문하여 자세한 내용을 확인하세요. 광고 AdAge 100 광고주이든 현지 소매상이든 관계없이 누구나 YouTube 광고 프로그램을 이용하면 전 세계에서 가장 큰 온라인 동영상 커뮤니티를 활용하는 것이 됩니다. YouTube에서 광고를 하는 데 대한 기본사항을 알아보세요 . 보안 악용 문제 사이트에 악용 문제가 있는 경우에는 안전센터 를 통해 문의해 주시기 바랍니다. 사이트 보안 문제 YouTube 사이트와 관련된 보안 문제는 여기에서 신고하실 수 있습니다 . 법적 문제 저작권 문제 내가 저작권을 보유한 동영상이 허락 없이 올라와 있는 것을 발견할 경우 다음 안내 에 따라 저작권 침해 신고를 제출하시기 바랍니다. 콘텐츠 확인 프로그램 콘텐츠 확인 프로그램에 참여하려면 콘텐츠 확인 페이지를 방문하세요. 부적절한 콘텐츠 YouTube에 올라온 부적절한 동영상을 신고하려면 동영상 아래에 있는 '신고' 링크를 클릭하세요. YouTube 정책에 대한 자세한 내용은 서비스 약관을 참조 하시기 바랍니다. 기타 개발자 개발자이거나 Google API에 관심이 있는 경우 개발자 페이지 를 방문하세요. Google에 추가 콘텐츠를 제출하세요. 가젯, 쇼핑, 지역 정보, 도서 등 콘텐츠를 Google에 배포할 수 있는 모든 방법 을 확인하세요. 주소 아래 주소로 YouTube에 연락하실 수 있습니다. Google LLC, D/B/A YouTube 901 Cherry Ave. San Bruno, CA 94066 USA 팩스: +1 650-253-0001 | 2026-01-13T08:49:06 |
https://dev.to/missamarakay/following-cooking-recipes-makes-you-a-clearer-writer-460a#in-the-kitchen | 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/success-stories/category/engineering/#top | 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://www.python.org/success-stories/category/software-development/#site-map | Software Development | 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 >>> Software Development Software Development Python on Arm: 2025 Update Zama Concrete ML: Simplifying Homomorphic Encryption for Python Machine Learning Building Robust Codebases with Python's Type Annotations Building a Dependency Graph of Our Python Codebase Bleeding Edge Dependency Testing Using Python How We Created a Python Development Framework for Non-Developers Vacation rental marketplace development using Python Deliver Clean and Safe Code for Your Python Applications A Startup Healthcare Tech Firm Is Now Poised for the Future Using Python to build a range of products across multiple industries Using Python for marketplace development under tight deadlines Using Python to develop a patient health portal Building an online pharmacy marketplace with Python Python provides convenience and flexibility for scalable ML/AI Securing Python Runtimes Building an open-source and cross-platform Azure CLI with Python D-Link Australia Uses Python to Control Firmware Updates Distributed System For Technology Integration EZRO Content Management System Avoiding Documentation Costs with Python A Custom Image Viewing Game for an Autistic Child XIST: An XML Transformation Engine 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://peps.python.org/pep-0248/ | PEP 248 – Python Database API Specification v1.0 | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 248 Toggle light / dark / auto colour theme PEP 248 – Python Database API Specification v1.0 Author : Greg Stein <gstein at lyra.org>, Marc-André Lemburg <mal at lemburg.com> Discussions-To : Db-SIG list Status : Final Type : Informational Created : 08-May-1996 Post-History : Superseded-By : 249 Table of Contents Introduction Module Interface Connection Objects Cursor Objects DBI Helper Objects Acknowledgements Copyright Introduction This API has been defined to encourage similarity between the Python modules that are used to access databases. By doing this, we hope to achieve a consistency leading to more easily understood modules, code that is generally more portable across databases, and a broader reach of database connectivity from Python. This interface specification consists of several items: Module Interface Connection Objects Cursor Objects DBI Helper Objects Comments and questions about this specification may be directed to the SIG on Tabular Databases in Python ( http://www.python.org/sigs/db-sig ). This specification document was last updated on: April 9, 1996. It will be known as Version 1.0 of this specification. Module Interface The database interface modules should typically be named with something terminated by db . Existing examples are: oracledb , informixdb , and pg95db . These modules should export several names: modulename(connection_string) Constructor for creating a connection to the database. Returns a Connection Object. error Exception raised for errors from the database module. Connection Objects Connection Objects should respond to the following methods: close() Close the connection now (rather than whenever __del__ is called). The connection will be unusable from this point forward; an exception will be raised if any operation is attempted with the connection. commit() Commit any pending transaction to the database. rollback() Roll the database back to the start of any pending transaction. cursor() Return a new Cursor Object. An exception may be thrown if the database does not support a cursor concept. callproc([params]) (Note: this method is not well-defined yet.) Call a stored database procedure with the given (optional) parameters. Returns the result of the stored procedure. (all Cursor Object attributes and methods) For databases that do not have cursors and for simple applications that do not require the complexity of a cursor, a Connection Object should respond to each of the attributes and methods of the Cursor Object. Databases that have cursor can implement this by using an implicit, internal cursor. Cursor Objects These objects represent a database cursor, which is used to manage the context of a fetch operation. Cursor Objects should respond to the following methods and attributes: arraysize This read/write attribute specifies the number of rows to fetch at a time with fetchmany() . This value is also used when inserting multiple rows at a time (passing a tuple/list of tuples/lists as the params value to execute() ). This attribute will default to a single row. Note that the arraysize is optional and is merely provided for higher performance database interactions. Implementations should observe it with respect to the fetchmany() method, but are free to interact with the database a single row at a time. description This read-only attribute is a tuple of 7-tuples. Each 7-tuple contains information describing each result column: (name, type_code, display_size, internal_size, precision, scale, null_ok). This attribute will be None for operations that do not return rows or if the cursor has not had an operation invoked via the execute() method yet. The ‘type_code’ is one of the ‘dbi’ values specified in the section below. Note: this is a bit in flux. Generally, the first two items of the 7-tuple will always be present; the others may be database specific. close() Close the cursor now (rather than whenever __del__ is called). The cursor will be unusable from this point forward; an exception will be raised if any operation is attempted with the cursor. execute(operation [,params]) Execute (prepare) a database operation (query or command). Parameters may be provided (as a sequence (e.g. tuple/list)) and will be bound to variables in the operation. Variables are specified in a database-specific notation that is based on the index in the parameter tuple (position-based rather than name-based). The parameters may also be specified as a sequence of sequences (e.g. a list of tuples) to insert multiple rows in a single operation. A reference to the operation will be retained by the cursor. If the same operation object is passed in again, then the cursor can optimize its behavior. This is most effective for algorithms where the same operation is used, but different parameters are bound to it (many times). For maximum efficiency when reusing an operation, it is best to use the setinputsizes() method to specify the parameter types and sizes ahead of time. It is legal for a parameter to not match the predefined information; the implementation should compensate, possibly with a loss of efficiency. Using SQL terminology, these are the possible result values from the execute() method: If the statement is DDL (e.g. CREATE TABLE ), then 1 is returned. If the statement is DML (e.g. UPDATE or INSERT ), then the number of rows affected is returned (0 or a positive integer). If the statement is DQL (e.g. SELECT ), None is returned, indicating that the statement is not really complete until you use one of the ‘fetch’ methods. fetchone() Fetch the next row of a query result, returning a single tuple. fetchmany([size]) Fetch the next set of rows of a query result, returning as a list of tuples. An empty list is returned when no more rows are available. The number of rows to fetch is specified by the parameter. If it is None , then the cursor’s arraysize determines the number of rows to be fetched. Note there are performance considerations involved with the size parameter. For optimal performance, it is usually best to use the arraysize attribute. If the size parameter is used, then it is best for it to retain the same value from one fetchmany() call to the next. fetchall() Fetch all rows of a query result, returning as a list of tuples. Note that the cursor’s arraysize attribute can affect the performance of this operation. setinputsizes(sizes) (Note: this method is not well-defined yet.) This can be used before a call to execute() to predefine memory areas for the operation’s parameters. sizes is specified as a tuple – one item for each input parameter. The item should be a Type object that corresponds to the input that will be used, or it should be an integer specifying the maximum length of a string parameter. If the item is None , then no predefined memory area will be reserved for that column (this is useful to avoid predefined areas for large inputs). This method would be used before the execute() method is invoked. Note that this method is optional and is merely provided for higher performance database interaction. Implementations are free to do nothing and users are free to not use it. setoutputsize(size [,col]) (Note: this method is not well-defined yet.) Set a column buffer size for fetches of large columns (e.g. LONG). The column is specified as an index into the result tuple. Using a column of None will set the default size for all large columns in the cursor. This method would be used before the execute() method is invoked. Note that this method is optional and is merely provided for higher performance database interaction. Implementations are free to do nothing and users are free to not use it. DBI Helper Objects Many databases need to have the input in a particular format for binding to an operation’s input parameters. For example, if an input is destined for a DATE column, then it must be bound to the database in a particular string format. Similar problems exist for “Row ID” columns or large binary items (e.g. blobs or RAW columns). This presents problems for Python since the parameters to the execute() method are untyped. When the database module sees a Python string object, it doesn’t know if it should be bound as a simple CHAR column, as a raw binary item, or as a DATE . To overcome this problem, the ‘dbi’ module was created. This module specifies some basic database interface types for working with databases. There are two classes: ‘dbiDate’ and ‘dbiRaw’. These are simple container classes that wrap up a value. When passed to the database modules, the module can then detect that the input parameter is intended as a DATE or a RAW . For symmetry, the database modules will return DATE and RAW columns as instances of these classes. A Cursor Object’s ‘description’ attribute returns information about each of the result columns of a query. The ‘type_code’ is defined to be one of five types exported by this module: STRING , RAW , NUMBER , DATE , or ROWID . The module exports the following names: dbiDate(value) This function constructs a ‘dbiDate’ instance that holds a date value. The value should be specified as an integer number of seconds since the “epoch” (e.g. time.time() ). dbiRaw(value) This function constructs a ‘dbiRaw’ instance that holds a raw (binary) value. The value should be specified as a Python string. STRING This object is used to describe columns in a database that are string-based (e.g. CHAR). RAW This object is used to describe (large) binary columns in a database (e.g. LONG RAW, blobs). NUMBER This object is used to describe numeric columns in a database. DATE This object is used to describe date columns in a database. ROWID This object is used to describe the “Row ID” column in a database. Acknowledgements Many thanks go to Andrew Kuchling who converted the Python Database API Specification 1.0 from the original HTML format into the PEP format in 2001. Greg Stein is the original author of the Python Database API Specification 1.0. Marc-André later continued maintenance of the API as an editor. Copyright This document has been placed in the Public Domain. Source: https://github.com/python/peps/blob/main/peps/pep-0248.rst Last modified: 2025-02-01 08:55:40 GMT Contents Introduction Module Interface Connection Objects Cursor Objects DBI Helper Objects Acknowledgements Copyright Page Source (GitHub) | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/hmpljs/major-module-update-31p5#comments | Major module update! - 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 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 Anthony Max for HMPL.js Posted on Nov 17, 2025 Major module update! # webdev # javascript # programming # opensource Hello everyone! In this short article, I'd like to talk about the new versions we recently released. It would seem that the modules are quite utilitarian and there is no particular point in updating them, but nevertheless, it is worth keeping them up to date today, and we will talk about some of the changes in them today. Stay informed! ⚙️ vite-plugin-hmpl and hmpl-loader In case you weren't aware, .hmpl actually has its own file extension. Loading it requires loaders, which were created specifically for Vite and WebPack. For these, we've updated the settings validation, which relies on the following types: interface HMPLCompileOptions { memo?: boolean; autoBody?: boolean | HMPLAutoBodyOptions; allowedContentTypes?: HMPLContentTypes; sanitize?: HMPLSanitize; disallowedTags?: HMPLDisallowedTags; sanitizeConfig?: Config; } Enter fullscreen mode Exit fullscreen mode A small, but also quite interesting update. 🌳 hmpl-dom This module is designed to use templating language syntax without npm or other add-ons. Nothing else is needed, just a single index.html file and that's it. In this update, we've added hmpl-dom.runtime.js . This is also quite an update. They've also updated the README files and other texts everywhere, but that's not really important in the context of releases. 💬 Feedback You can write your thoughts about the new features in the comments, it will be interesting to read! Or, there is a thematic Discord channel for questions and suggestions, there I or someone else will try to answer! ✅ This project is Open Source So you can take part in it too! This also means you can use it for commercial purposes: Repo: https://github.com/hmpl-language/hmpl (Star Us ★) Website: https://hmpl-lang.dev Full list of changes: https://hmpl-lang.dev/changelog Thank you very much for reading the article! 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 Anthony Max HMPL.js Anthony Max HMPL.js Anthony Max Follow 🐜 Fetch API enjoyer | collab: aanthonymaxgithub@gmail.com Education Unfinished bachelor's degree Pronouns Anthony or Tony Work HMPL.js Joined Sep 20, 2024 • Nov 17 '25 Dropdown menu Copy link Hide What do you think about the updates? Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Art light Art light Art light Follow Trust yourself🌞your capabilities are your true power. ❤Telegram - ✔lighthouse4661 ❤Discord - ✔lighthouse4661 Email art.miclight@gmail.com Pronouns He/him Work CTO Joined Nov 21, 2025 • Dec 5 '25 Dropdown menu Copy link Hide Great job on the update! The new changes look really solid, and I appreciate how clearly you explained everything. I’m especially interested in the improvements to the loaders and the new runtime addition. Looking forward to seeing how the project grows—keep it up! 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 HMPL.js Follow 🐜 Server-oriented customizable templating for JavaScript The proudly project is Open Source 🌱, so we would be very grateful if you supported it with a star! 💎 Support Us ☆ 💎 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/#top | 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/logos/#top | 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://peps.python.org/pep-0609/ | PEP 609 – Python Packaging Authority (PyPA) Governance | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 609 Toggle light / dark / auto colour theme PEP 609 – Python Packaging Authority (PyPA) Governance Author : Dustin Ingram <di at python.org>, Pradyun Gedam <pradyunsg at gmail.com>, Sumana Harihareswara <sh at changeset.nyc> Sponsor : Paul Ganssle <paul at ganssle.io> Discussions-To : Discourse thread Status : Active Type : Process Topic : Governance , Packaging Created : 05-Nov-2019 Post-History : 05-Nov-2019 Table of Contents Abstract Rationale Terminology Goals Goals of the PyPA Provide support for existing projects under the PyPA Foster the creation and acceptance of standards for PyPA projects Guide decisions which affect multiple PyPA projects Determine which projects should be under the guidance of the PyPA Enforce adherence to a Code of Conduct across all projects Non-goals of the PyPA Determine who is and isn’t a PyPA member Micromanage individual projects Develop and maintain standalone Code of Conduct Goals of the PyPA’s Governance Model Transparency in PyPA membership Document PyPA’s use of PEPs Processes Specifications Governance PyPA Committer Votes Addition of a project to the PyPA Creation of a new project in the PyPA Removal of a project from PyPA Updates to the Governance/Specification Processes Leaving PyPA Code of Conduct enforcement Copyright Abstract This document describes a governance model for the Python Packaging Authority (PyPA). The model is closely based on existing informal practices, with the intent of providing clarity into the functioning of the PyPA and formalizing transparent processes for the PyPA. Rationale The Python Packaging Authority (PyPA) is a collaborative community that maintains and advances many of the relevant projects in Python packaging. The software and standards developed through the PyPA are used to package, share, and install Python software and to interact with indexes of downloadable Python software such as PyPI , the Python Package Index. Currently, the PyPA is an informal and loosely defined organization that lacks true authority, and the inclusion of a given project under the PyPA umbrella or the creation of new projects has been done in an ad-hoc, one-off manner. Similarly, individual membership in the PyPA is not well-defined. While this model has more or less worked for the PyPA in the past, it results in an organization which is missing certain features of a stable ecosystem, namely a clear and transparent decision-making process. This PEP seeks to rectify this by defining a governance model for the PyPA. Terminology Relevant terms for groups of individual contributors used in this PEP: PyPA members : Anyone with the triage bit or commit bit, on at least one project in the PyPA organization . PyPA committers : Anyone with the commit bit on at least one project in the PyPA organization, which should correspond to everyone on the PyPA-Committers mailing list. PyPA community : Anyone who is interested in PyPA activity and wants to follow along, contribute or make proposals. Packaging-WG members : As described in the Packaging-WG Wiki page . For clarity: there is no formal relationship between the Packaging-WG and PyPA. This group is only included in this list to disambiguate it from PyPA. Goals The following section formalizes the goals (and non-goals) of the PyPA and this governance model. Goals of the PyPA These goals are the primary motivation for the existence of the PyPA. These goals are largely already being carried out, even though most have not been explicitly defined. Provide support for existing projects under the PyPA In the event that a given project needs additional support, or no longer has active maintainers, the PyPA will ensure that the given project will continue to be supported for users to the extent necessary. Foster the creation and acceptance of standards for PyPA projects The PyPA should, as much as possible, strive for standardization and coordination across PyPA projects, primarily though the governance process outlined below. PyPA projects are expected to abide by applicable specifications maintained by the PyPA. Guide decisions which affect multiple PyPA projects The PyPA community (especially PyPA members) should be expected to provide opinions, insight and experience when ecosystem-wide changes are being proposed. Determine which projects should be under the guidance of the PyPA For example: accepting new projects from the community, organically creating projects within the PyPA, etc. Enforce adherence to a Code of Conduct across all projects Generally this means leading by example, but occasionally it may mean more explicit moderation. Non-goals of the PyPA These are specific items that are explicitly _not_ goals of the PyPA. Determine who is and isn’t a PyPA member This is for members of individual projects to decide, as they add new members to their projects. Maintainership of a project that is under the PyPA organization automatically transfers membership in the PyPA. Micromanage individual projects As long as the project is adhering to the Code of Conduct and following specifications supported by the PyPA, the PyPA should only concerned with large, ecosystem-wide changes. Develop and maintain standalone Code of Conduct PyPA projects follow the PSF Code of Conduct . Goals of the PyPA’s Governance Model These are new goals which the governance model seeks to make possible. Transparency in PyPA membership Provide a transparent process for decisions taken, regarding project membership in the PyPA. Document PyPA’s use of PEPs Formally document how the PyPA uses Python Enhancement Proposals (PEPs), for maintaining interoperability specifications defined by the PyPA. Processes The processes for the PyPA’s activities are outlined below: Specifications The PyPA will use PEPs for defining, and making changes to, the interoperability specifications maintained by the PyPA. Thus, the Python Steering Council has the final say in the acceptance of these interoperability specifications. It is expected (but not required) that the Python Steering Council would delegate authority to sponsor and/or approve/reject PEPs related to packaging interoperability specifications, to individuals within the PyPA community. At the time of writing (June 2020), the Python Steering Council has standing delegations for currently active packaging interoperability specifications. The details of the process of proposing and updating the interoperability specifications are described in the PyPA Specifications document. Governance PyPA Committer Votes A PyPA member can put forward a proposal and call for a vote on a public PyPA communication channel. A PyPA committer vote is triggered when a PyPA committer (not the proposer) seconds the proposal. The proposal will be put to a vote on the PyPA-Committers mailing list, over a 7-day period. Each PyPA committer can vote once, and can choose one of +1 and -1 . If at least two thirds of recorded votes are +1 , then the vote succeeds. PyPA committer votes are required for, and limited to, the following kinds of proposals: Addition of a project to the PyPA Proposing the acceptance of a project into the PyPA organization. This proposal must not be opposed by the existing maintainers of the project. Creation of a new project in the PyPA Proposing the creation of a new tools / project in the PyPA organization. Removal of a project from PyPA Proposing the removal of a project in the PyPA organization. Updates to the Governance/Specification Processes Proposing changes to how the PyPA operates, including but not limited to changes to its specification and governance processes, and this PEP. Leaving PyPA A project that is a part of the PyPA organization, can request to leave PyPA. Such requests can made by a committer of the project, on the PyPA-Committers mailing list and must clearly state the GitHub user/organization to transfer the repository to. If the request is not opposed by another committer of the same project over a 7-day period, the project would leave the PyPA and be transferred out of the PyPA organization as per the request. Code of Conduct enforcement Each project that is a part of the PyPA organization follows the PSF Code of Conduct , including its incident reporting guidelines and enforcement procedures. PyPA members are responsible for leading by example. PyPA members occasionally may need to more explicitly moderate behavior in their projects, and each project that is a part of the PyPA organization must designate at least one PyPA member as available to contact in case of a Code of Conduct incident. If told of any Code of Conduct incidents involving their projects, PyPA members are expected to report those incidents up to the PSF Conduct WG , for recording purposes and for potential assistance. 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-0609.rst Last modified: 2025-02-01 08:55:40 GMT Contents Abstract Rationale Terminology Goals Goals of the PyPA Provide support for existing projects under the PyPA Foster the creation and acceptance of standards for PyPA projects Guide decisions which affect multiple PyPA projects Determine which projects should be under the guidance of the PyPA Enforce adherence to a Code of Conduct across all projects Non-goals of the PyPA Determine who is and isn’t a PyPA member Micromanage individual projects Develop and maintain standalone Code of Conduct Goals of the PyPA’s Governance Model Transparency in PyPA membership Document PyPA’s use of PEPs Processes Specifications Governance PyPA Committer Votes Addition of a project to the PyPA Creation of a new project in the PyPA Removal of a project from PyPA Updates to the Governance/Specification Processes Leaving PyPA Code of Conduct enforcement Copyright Page Source (GitHub) | 2026-01-13T08:49:06 |
https://www.python.org/community/irc/#python-network | 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/psf/news-and-community | Python Software Foundation News & Community | 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 Python Software Foundation News & Community News & Updates Sign up to receive our newsletter! It is currently sent out about once a quarter. Visit the Python Software Foundation News blog where we make announcements and discuss PSF activities. You can follow us on Twitter , Mastodon , and LinkedIn . You can sign up for psf-members-announce , which is a moderated, very low traffic list used for announcements to the PSF members, primarily regarding elections. Community Learn about the PSF Community Awards and see the list of past winners . Join the conversation on Discourse Volunteer for the PSF Code of Conduct You can find the Python Community Code of Conduct here . Membership You can sign up as a member here . Want to contact us? Visit How to reach the PSF . 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/anthonymax/were-launching-on-producthunt-3i43 | We're launching on ProductHunt - 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 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 Anthony Max Posted on Dec 28, 2025 We're launching on ProductHunt # javascript # news # showdev Hi everyone! 📢 Today is a very important day for us. We've launched on ProductHunt! If you don't mind, you can support us by following this link with your Upvote. Thank you! producthunt.com 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 Anthony Max Follow 🐜 Fetch API enjoyer | collab: aanthonymaxgithub@gmail.com Education Unfinished bachelor's degree Pronouns Anthony or Tony Work HMPL.js Joined Sep 20, 2024 More from Anthony Max https://hmpl-lang.dev - new website # programming # showdev # webdev A new example of using the template language: https://codesandbox.io/p/sandbox/basic-hmpl-example-dxlgfg # showcase # javascript # hmpldom # beginners Great news today: we've finally launched a section featuring community projects built with hmpl-js. https://github.com/hmpl-language/projects # javascript # news # showcase # opensource 💎 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/webdev#main-content | Web Development - 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 Development Follow Hide Because the internet... Create Post submission guidelines Be nice. Be respectful. Assume best intentions. Be kind, rewind. Older #webdev posts 1 2 3 4 5 6 7 8 9 … 75 … 5409 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu 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 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://hmpljs.forem.com/anthonymax/great-news-today-weve-finally-launched-a-section-featuring-community-projects-built-with-3h8k | Great news today: we've finally launched a section featuring community projects built with hmpl-js. https://github.com/hmpl-language/projects - 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 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 Anthony Max Posted on Nov 20, 2025 Great news today: we've finally launched a section featuring community projects built with hmpl-js. github.com/hmpl-langua... Sign in to view linked content Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss 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 Anthony Max Follow 🐜 Fetch API enjoyer | collab: aanthonymaxgithub@gmail.com Education Unfinished bachelor's degree Pronouns Anthony or Tony Work HMPL.js Joined Sep 20, 2024 More from Anthony Max We're launching on ProductHunt # javascript # news # showdev A new example of using the template language: https://codesandbox.io/p/sandbox/basic-hmpl-example-dxlgfg # showcase # javascript # hmpldom # beginners Added a new example of a HATEOAS application: https://github.com/hmpl-language/examples # architecture # showcase # api # opensource 💎 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#a-information-you-provide-to-us-directly | 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/t/web3/page/7 | Web3 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 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 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 Waveterm: Streamlining Cloud and Remote Server Workflows Stelixx Insider Stelixx Insider Stelixx Insider Follow Dec 7 '25 Waveterm: Streamlining Cloud and Remote Server Workflows # ai # web3 # blockchain # productivity Comments Add Comment 1 min read Web3 : Le bilan de Google Cloud sur la blockchain en 2025 Benjamin Bourgeois Benjamin Bourgeois Benjamin Bourgeois Follow for Zenika Dec 11 '25 Web3 : Le bilan de Google Cloud sur la blockchain en 2025 # web3 # blockchain # googlecloud # cloud 3 reactions Comments Add Comment 4 min read Yearn yETH: How a Solver Flaw Caused a $9M Loss? QuillAudits QuillAudits QuillAudits Follow Dec 11 '25 Yearn yETH: How a Solver Flaw Caused a $9M Loss? # ethereum # smartcontract # blockchain # web3 1 reaction Comments Add Comment 2 min read Ungoogled Chromium: Tách biệt trình duyệt khỏi sự phụ thuộc của Google Stelixx Insider Stelixx Insider Stelixx Insider Follow Dec 8 '25 Ungoogled Chromium: Tách biệt trình duyệt khỏi sự phụ thuộc của Google # ai # web3 # blockchain # productivity Comments Add Comment 1 min read Web 3.5: Future of the Internet or Just a Passing Hype? Nima Moosarezaie Nima Moosarezaie Nima Moosarezaie Follow for Alyvro Dec 6 '25 Web 3.5: Future of the Internet or Just a Passing Hype? # web3 # futureoftheinternet # blockchain # emergingtechnologies Comments Add Comment 9 min read Vue + XChainJS Example bock-studio bock-studio bock-studio Follow Dec 19 '25 Vue + XChainJS Example # blockchain # web3 # solidity # cryptocurrency Comments 1 comment 2 min read Why Central Banks Should Participate and Not Compete in Tokenized Markets. Victory Adugbo Victory Adugbo Victory Adugbo Follow Dec 6 '25 Why Central Banks Should Participate and Not Compete in Tokenized Markets. # discuss # web3 # blockchain # opensource 1 reaction Comments Add Comment 3 min read 🎉 Slither Deep Audit Completed – Lattice L2 ArcticChain lab ArcticChain lab ArcticChain lab Follow Dec 30 '25 🎉 Slither Deep Audit Completed – Lattice L2 # showdev # web3 # blockchain # security Comments Add Comment 2 min read AI's insatiable energy demands, massive funding rounds, and evolving market dynamics dominate tech news. Stelixx Insights Stelixx Insights Stelixx Insights Follow Dec 6 '25 AI's insatiable energy demands, massive funding rounds, and evolving market dynamics dominate tech news. # ai # web3 # blockchain # productivity Comments 1 comment 2 min read Glamsterdam, Bitcoin in MetaMask, EIL & 7702 Alignment, PillarX Universal Gas Tank Alexandra Alexandra Alexandra Follow for Etherspot Dec 29 '25 Glamsterdam, Bitcoin in MetaMask, EIL & 7702 Alignment, PillarX Universal Gas Tank # blockchain # web3 # ethereum 2 reactions Comments Add Comment 6 min read Discordo: A Go Library for Streamlined Discord Bot Development Stelixx Insider Stelixx Insider Stelixx Insider Follow Dec 6 '25 Discordo: A Go Library for Streamlined Discord Bot Development # ai # web3 # blockchain # productivity Comments Add Comment 1 min read Confessions of a Market Maker Bot: How Liquidity Really Gets Built Behind the Scenes Emir Taner Emir Taner Emir Taner Follow Dec 5 '25 Confessions of a Market Maker Bot: How Liquidity Really Gets Built Behind the Scenes # web3 # blockchain # webdev # ai 2 reactions Comments Add Comment 2 min read Bridging Banking Systems and Blockchain: Technical Realities Behind the Integration Problem YUSRI ADIB YUSRI ADIB YUSRI ADIB Follow Dec 6 '25 Bridging Banking Systems and Blockchain: Technical Realities Behind the Integration Problem # banking # iso20022 # web3 # blockchain Comments Add Comment 2 min read AI Dominates Global Tech Scene with Major Investments, Product Launches, and Ethical Debates Stelixx Insights Stelixx Insights Stelixx Insights Follow Dec 7 '25 AI Dominates Global Tech Scene with Major Investments, Product Launches, and Ethical Debates # ai # web3 # blockchain # productivity Comments Add Comment 1 min read Is Web 3.5 the Future of the Internet? Key Differences Nima Moosarezaie Nima Moosarezaie Nima Moosarezaie Follow Dec 6 '25 Is Web 3.5 the Future of the Internet? Key Differences # web3 # technology # futureinternet Comments Add Comment 4 min read ESLint for Markdown: Standardizing Documentation Consistency Stelixx Insider Stelixx Insider Stelixx Insider Follow Dec 6 '25 ESLint for Markdown: Standardizing Documentation Consistency # ai # web3 # blockchain # productivity Comments Add Comment 1 min read BUBUVERSE Introduces Real-Time PvP Dice (Beta) — A Technical Look at the New GameFi Layer bubuverse bubuverse bubuverse Follow Dec 6 '25 BUBUVERSE Introduces Real-Time PvP Dice (Beta) — A Technical Look at the New GameFi Layer # webdev # ai # web3 # gamedev Comments Add Comment 2 min read NextGenDevTools: Tăng Năng Suất Phát Triển Web Hiện Đại Stelixx Insider Stelixx Insider Stelixx Insider Follow Dec 7 '25 NextGenDevTools: Tăng Năng Suất Phát Triển Web Hiện Đại # ai # web3 # blockchain # productivity Comments Add Comment 1 min read COBOL in Big 25 Anbu Taco Anbu Taco Anbu Taco Follow Dec 5 '25 COBOL in Big 25 # kiro # legacy # ai # web3 Comments Add Comment 3 min read If Blockchains Are Public, Why Is Reading Them a Privilege? LogicDev-tools LogicDev-tools LogicDev-tools Follow Jan 8 If Blockchains Are Public, Why Is Reading Them a Privilege? # discuss # blockchain # web3 Comments 2 comments 6 min read Qik Seek: My Modern, Fast, and Interactive Search Engine FutureDev FutureDev FutureDev Follow Dec 4 '25 Qik Seek: My Modern, Fast, and Interactive Search Engine # webdev # programming # web3 # javascript Comments Add Comment 1 min read How I Built a Decentralized NFT Gift Protocol (and why digital gifting is broken) Jayant kurekar Jayant kurekar Jayant kurekar Follow Dec 4 '25 How I Built a Decentralized NFT Gift Protocol (and why digital gifting is broken) # web3 # solidity # react # kiro Comments Add Comment 3 min read Is Crypto One Big Scam? The Part Most People Never See Obafemi Ogunmokun Obafemi Ogunmokun Obafemi Ogunmokun Follow Dec 8 '25 Is Crypto One Big Scam? The Part Most People Never See # web3 # blockchain # cryptocurrency 2 reactions Comments 1 comment 6 min read Ethereum Gas Limit 60M, EF Details Full EIL Architecture, Arbitrum ARBOS, Soneium & Sony IRC Fan Identity Alexandra Alexandra Alexandra Follow for Etherspot Dec 4 '25 Ethereum Gas Limit 60M, EF Details Full EIL Architecture, Arbitrum ARBOS, Soneium & Sony IRC Fan Identity # ethereum # blockchain # web3 Comments Add Comment 6 min read (Part 4) Remote Attestation: How to Prove You Aren't a Dog on the Internet 🐶 Max Jiang Max Jiang Max Jiang Follow Dec 15 '25 (Part 4) Remote Attestation: How to Prove You Aren't a Dog on the Internet 🐶 # security # cryptograpy # web3 # backend 3 reactions Comments 1 comment 4 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/t/react#main-content | React - 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 React Follow Hide Official tag for Facebook's React JavaScript library for building user interfaces Create Post submission guidelines 1️⃣ Post Facebook's React ⚛ related posts/questions/discussion topics here~ 2️⃣ There are no silly posts or questions as we all learn from each other👩🎓👨🎓 3️⃣ Adhere to dev.to 👩💻👨💻 Code of Conduct about #react React is a declarative, component-based library, you can learn once, and write anywhere Editor Guide Check out this Editor Guide or this post to learn how to add code syntax highlights, embed CodeSandbox/Codepen, etc Official Documentations & Source Docs Tutorial Community Blog Source code on GitHub Improving Your Chances for a Reply by putting a minimal example to either JSFiddle , Code Sandbox , or StackBlitz . Describe what you want it to do, and things you've tried. Don't just post big blocks of code! Where else to ask questions StackOverflow tagged with [reactjs] Beginner's Thread / Easy Questions (Jan 2020) on r/reactjs subreddit. Note: a new "Beginner's Thread" created as sticky post on the first day of each month Learn in Public Don't afraid to post an article or being wrong. Learn in public . Older #react posts 1 2 3 4 5 6 7 8 9 … 75 … 1772 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://zeroday.forem.com/new/tools | New Post - Security 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 Security Forem Close Join the Security Forem Security 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 Security 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 Security Forem — Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike 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 . Security Forem © 2016 - 2026. Share. Secure. Succeed Log in Create account | 2026-01-13T08:49:06 |
https://www.python.org/success-stories/category/software-development/#top | Software Development | 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 >>> Software Development Software Development Python on Arm: 2025 Update Zama Concrete ML: Simplifying Homomorphic Encryption for Python Machine Learning Building Robust Codebases with Python's Type Annotations Building a Dependency Graph of Our Python Codebase Bleeding Edge Dependency Testing Using Python How We Created a Python Development Framework for Non-Developers Vacation rental marketplace development using Python Deliver Clean and Safe Code for Your Python Applications A Startup Healthcare Tech Firm Is Now Poised for the Future Using Python to build a range of products across multiple industries Using Python for marketplace development under tight deadlines Using Python to develop a patient health portal Building an online pharmacy marketplace with Python Python provides convenience and flexibility for scalable ML/AI Securing Python Runtimes Building an open-source and cross-platform Azure CLI with Python D-Link Australia Uses Python to Control Firmware Updates Distributed System For Technology Integration EZRO Content Management System Avoiding Documentation Costs with Python A Custom Image Viewing Game for an Autistic Child XIST: An XML Transformation Engine 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://peps.python.org/pep-0101/ | PEP 101 – Doing Python Releases 101 | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 101 Toggle light / dark / auto colour theme PEP 101 – Doing Python Releases 101 Author : Barry Warsaw <barry at python.org>, Guido van Rossum <guido at python.org> Status : Active Type : Informational Created : 22-Aug-2001 Post-History : Replaces : 102 Table of Contents Abstract Things You’ll Need Types of Releases How To Make A Release What Next? Moving to End-of-life Windows Notes Copyright Abstract Making a Python release is a thrilling and crazy process. You’ve heard the expression “herding cats”? Imagine trying to also saddle those purring little creatures up, and ride them into town, with some of their buddies firmly attached to your bare back, anchored by newly sharpened claws. At least they’re cute, you remind yourself. Actually, no, that’s a slight exaggeration 😉 The Python release process has steadily improved over the years and now, with the help of our amazing community, is really not too difficult. This PEP attempts to collect, in one place, all the steps needed to make a Python release. Most of the steps are now automated or guided by automation, so manually following this list is no longer necessary. Things You’ll Need As a release manager there are a lot of resources you’ll need to access. Here’s a hopefully-complete list. A GPG key. Python releases before 3.14 are digitally signed with GPG; for these you’ll need a key, which hopefully will be on the “web of trust” with at least one of the other release managers. Note GPG instructions in this PEP can be ignored for Python 3.14 and later. See PEP 761 for details. A bunch of software: A checkout of the python/release-tools repo. It contains a requirements.txt file that you need to install dependencies from first. Afterwards, you can fire up scripts in the repo, covered later in this PEP. blurb , the Misc/NEWS management tool. You can pip install it. Access to servers where you will upload files: downloads.nyc1.psf.io , the server that hosts download files; and docs.nyc1.psf.io , the server that hosts the documentation. Administrator access to python/cpython . An administrator account on www.python.org , including an “API key”. Write access to the python/peps repository. If you’re reading this, you probably already have this–the first task of any release manager is to draft the release schedule. But in case you just signed up… sucker! I mean, uh, congratulations! Posting access to blog.python.org , a Blogger-hosted weblog. The RSS feed from this blog is used for the ‘Python News’ section on www.python.org . A subscription to the super secret release manager mailing list, which may or may not be called python-cabal . Bug Barry about this. A @python.org email address that you will use to sign your releases with. Ask postmaster@ for an address; you can either get a full account, or a redirecting alias + SMTP credentials to send email from this address that looks legit to major email providers. Be added to the Python Security Response Team . Types of Releases There are several types of releases you will need to make. These include: alpha begin beta , also known as beta 1 , also known as new branch beta 2+ release candidate 1 release candidate 2+ final new branch begin bugfix mode begin security-only mode end-of-life Some of these release types actually involve more than one release branch. In particular, a new branch is that point in the release cycle when a new feature release cycle begins. Under the current organization of the CPython Git repository, the main branch is always the target for new features. At some point in the release cycle of the next feature release, a new branch release is made which creates a new separate branch for stabilization and later maintenance of the current in-progress feature release ( 3.n.0 ) and the main branch is modified to build a new version (which will eventually be released as 3.n+1.0 ). While the new branch release step could occur at one of several points in the release cycle, current practice is for it to occur at feature code cutoff for the release which is scheduled for the first beta release. In the descriptions that follow, steps specific to release types are labeled accordingly, for now, new branch and final . How To Make A Release Here are the steps taken to make a Python release. Some steps are more fuzzy than others because there’s little that can be automated (e.g. writing the NEWS entries). Where a step is usually performed by An Expert, the role of that expert is given. Otherwise, assume the step is done by the Release Manager (RM), the designated person performing the release. The roles and their current experts are: RM = Release Manager Hugo van Kemenade < hugo @ python . org > (FI) Thomas Wouters < thomas @ python . org > (NL) Pablo Galindo Salgado < pablogsal @ python . org > (UK) Łukasz Langa < lukasz @ python . org > (PL) WE = Windows - Steve Dower < steve . dower @ python . org > ME = Mac - Ned Deily < nad @ python . org > (US) Note It is highly recommended that the RM contact the Experts the day before the release. Because the world is round and everyone lives in different timezones, the RM must ensure that the release tag is created in enough time for the Experts to cut binary releases. You should not make the release public (by updating the website and sending announcements) before all experts have updated their bits. In rare cases where the expert for Windows or Mac is MIA, you may add a message “(Platform) binaries will be provided shortly” and proceed. We use the following conventions in the examples below. Where a release number is given, it is of the form 3.X.YaN , e.g. 3.13.0a3 for Python 3.13.0 alpha 3, where “a” == alpha, “b” == beta, “rc” == release candidate. Release tags are named v3.X.YaN . The branch name for minor release maintenance branches is 3.X . As much as possible, the release is automated and guided by the run_release.py script, which is available in a separate repository: python/release-tools . This helps by automating many of the following steps, and guides you to perform some manual steps. Log into Discord and join the Python Core Devs server. Ask Thomas or Łukasz for an invite. You probably need to coordinate with other people around the world. This communication channel is where we’ve arranged to meet. Check to see if there are any showstopper bugs. Go to https://github.com/python/cpython/issues and look for any open bugs that can block this release. You’re looking at two relevant labels: release-blocker Stops the release dead in its tracks. You may not make any release with any open release blocker bugs. deferred-blocker Doesn’t block this release, but it will block a future release. You may not make a final or candidate release with any open deferred blocker bugs. Review the release blockers and either resolve them, bump them down to deferred, or stop the release and ask for community assistance. If you’re making a final or candidate release, do the same with any open deferred. Check the stable buildbots. Go to https://buildbot.python.org/all/#/release_status Look at the buildbots for the release you’re making. Ignore any that are offline (or inform the community so they can be restarted). If what remains are (mostly) green buildbots, you’re good to go. If you have non-offline red buildbots, you may want to hold up the release until they are fixed. Review the problems and use your judgement, taking into account whether you are making an alpha, beta, or final release. Make a release clone. On a fork of the CPython repository on GitHub, create a release branch within it (called the “release clone” from now on). You can use the same GitHub fork you use for CPython development. Using the standard setup recommended in the Python Developer’s Guide , your fork would be referred to as origin and the standard CPython repo as upstream . You will use the branch on your fork to do the release engineering work, including tagging the release, and you will use it to share with the other experts for making the binaries. For a final or release candidate 2+ release, if you are going to cherry-pick a subset of changes for the next rc or final from all those merged since the last rc, you should create a release engineering branch starting from the most recent release candidate tag, i.e. v3.8.0rc1 . You will then cherry-pick changes from the standard release branch as necessary into the release engineering branch and then proceed as usual. If you are going to take all of the changes since the previous rc, you can proceed as normal. Make sure the current branch of your release clone is the branch you want to release from ( git status ). Run blurb release <version> specifying the version number (e.g. blurb release 3.4.7rc1 ). This merges all the recent news blurbs into a single file marked with this release’s version number. Regenerate Lib/pydoc-topics.py . While still in the Doc directory, run: make pydoc-topics cp build/pydoc-topics/topics.py ../Lib/pydoc_data/topics.py Commit your changes to pydoc_topics.py (and any fixes you made in the docs). Consider running autoconf using the currently accepted standard version in case configure or other Autoconf-generated files were last committed with a newer or older version and may contain spurious or harmful differences. Currently, Autoconf 2.71 is our de facto standard. if there are differences, commit them. Make sure the SOURCE_URI in Doc/tools/extensions/pyspecific.py points to the right branch in the Git repository ( main or 3.X ). For a new branch release, change the branch in the file from main to the new release branch you are about to create ( 3.X ). Bump version numbers via the release script: .../release-tools/release.py --bump 3 .X.YaN Reminder: X , Y , and N should be integers. a should be one of a , b , or rc (e.g. 3.4.3rc1 ). For final releases omit the aN ( 3.4.3 ). For the first release of a new version Y should be 0 ( 3.6.0 ). This automates updating various release numbers, but you will have to modify a few files manually. If your $EDITOR environment variable is set up correctly, release.py will pop up editor windows with the files you need to edit. Review the blurb-generated Misc/NEWS file and edit as necessary. Make sure all changes have been committed. ( release.py --bump doesn’t check in its changes for you.) For a final major release, edit the first paragraph of Doc/whatsnew/3.X.rst to include the actual release date; e.g. “Python 2.5 was released on August 1, 2003.” There’s no need to edit this for alpha or beta releases. Do a git status in this directory. You should not see any files, i.e., you better not have any uncommitted changes in your working directory. Tag the release for 3.X.YaN : .../release-tools/release.py --tag 3 .X.YaN This executes a git tag command with the -s option so that the release tag in the repo is signed with your GPG key. When prompted choose the private key you use for signing release tarballs etc. For begin security-only mode and end-of-life releases, review the two files and update the versions accordingly in all active branches. Push your commits to the remote release branch in your GitHub fork: # Do a dry run first. git push --dry-run --tags origin # Make sure you are pushing to your GitHub fork, # *not* to the main python/cpython repo! git push --tags origin In python/release-tools , go to the build-release workflow, select “Run workflow”, and enter the details of the tag you just created. This will perform the following steps: Create the source gzip and xz tarballs. Create the documentation tar and zip files. Check the source tarball to make sure a completely clean, virgin build passes the regression test. Build and test the Android binaries (if Python 3.14 or later). The resulting artifacts will be attached to the summary page of the GitHub workflow. Once the source tarball is available, download and unpack it to make sure things look reasonable, there are no stray .pyc files, etc. If the tests pass, then you can feel good that the tarball is fine. If some of the tests fail, or anything else about the freshly unpacked directory looks weird, you better stop now and figure out what the problem is. Notify the experts that they can start building binaries. Warning STOP : at this point you must receive the “green light” from other experts in order to create the release. There are things you can do while you wait though, so keep reading until you hit the next STOP. The WE generates and publishes the Windows files using the Azure Pipelines build scripts in .azure-pipelines/windows-release/ , currently set up at https://dev.azure.com/Python/cpython/_build?definitionId=21 . The build process runs in multiple stages, with each stage’s output being available as a downloadable artifact. The stages are: Compile all variants of binaries (32-bit, 64-bit, debug/release), including running profile-guided optimization. Compile the HTML Help file containing the Python documentation. Codesign all the binaries with the PSF’s certificate. Create packages for python.org, nuget.org, the embeddable distro and the Windows Store. Perform basic verification of the installers. Upload packages to python.org and nuget.org, purge download caches and run a test download. After the uploads are complete, the WE copies the generated hashes from the build logs and emails them to the RM. The Windows Store packages are uploaded manually to https://partner.microsoft.com/dashboard/home by the WE. The ME builds Mac installer packages and uploads them to downloads.nyc1.psf.io together with GPG signature files. scp or rsync all the files built by the build-release workflow to your home directory on downloads.nyc1.psf.io , along with any signatures, SBOMs, etc. While you’re waiting for the files to finish uploading, you can continue on with the remaining tasks. You can also ask folks on Discord and/or discuss.python.org to download the files as they finish uploading so that they can test them on their platforms as well. Now you need to go to downloads.nyc1.psf.io and move all the files in place over there. Our policy is that every Python version gets its own directory, but each directory contains all releases of that version. On downloads.nyc1.psf.io , cd /srv/www.python.org/ftp/python/3.X.Y creating it if necessary. Make sure it is owned by group downloads and group-writable. Take the files you uploaded to your home directory above, and move them into the release directory. The Win/Mac binaries are usually put there by the experts themselves. Make sure they are world readable. They should also be group writable, and group-owned by downloads . Use gpg --verify to make sure they got uploaded intact. If this is a final or rc release: Move the doc zips and tarballs to /srv/www.python.org/ftp/python/doc/3.X.Y[rcA] , creating the directory if necessary, and adapt the “current” symlink in .../doc to point to that directory. Note though that if you’re releasing a maintenance release for an older version, don’t change the current link. If this is a final or rc release (even a maintenance release), also unpack the HTML docs to /srv/docs.python.org/release/3.X.Y[rcA] on docs.nyc1.psf.io . Make sure the files are in group docs and are group-writeable. Note both the documentation and downloads are behind a caching CDN. If you change archives after downloading them through the website, you’ll need to purge the stale data in the CDN like this: curl -X PURGE https://www.python.org/ftp/python/3.12.0/Python-3.12.0.tar.xz You should always purge the cache of the directory listing as people use that to browse the release files: curl -X PURGE https://www.python.org/ftp/python/3.12.0/ For the extra paranoid, do a completely clean test of the release. This includes downloading the tarball from www.python.org . Make sure the md5 checksums match. Then unpack the tarball, and do a clean make test: make distclean ./configure make test To ensure that the regression test suite passes. If not, you screwed up somewhere! Warning STOP and confirm: Have you gotten the green light from the WE? Have you gotten the green light from the ME? If green, it’s time to merge the release engineering branch back into the main repo. In order to push your changes to GitHub, you’ll have to temporarily disable branch protection for administrators. Go to the Settings | Branches page: https://github.com/python/cpython/settings/branches “Edit” the settings for the branch you’re releasing on. This will load the settings page for that branch. Uncheck the “Include administrators” box and press the “Save changes” button at the bottom. Merge your release clone into the main development repo: # Pristine copy of the upstream repo branch git clone git@github.com:python/cpython.git merge cd merge # Checkout the correct branch: # 1. For feature pre-releases up to and including a # **new branch** release, i.e. alphas and first beta # do a checkout of the main branch git checkout main # 2. Else, for all other releases, checkout the # appropriate release branch. git checkout 3 .X # Fetch the newly created and signed tag from your clone repo git fetch --tags git@github.com:your-github-id/cpython.git v3.X.YaN # Merge the temporary release engineering branch back into git merge --no-squash v3.X.YaN git commit -m 'Merge release engineering branch' If this is a new branch release, i.e. first beta, now create the new release branch: git checkout -b 3 .X Do any steps needed to setup the new release branch, including: In README.rst , change all references from main to the new branch, in particular, GitHub repo URLs. For all releases, do the guided post-release steps with the release script: .../release-tools/release.py --done 3 .X.YaN For a final or release candidate 2+ release, you may need to do some post-merge cleanup. Check the top-level README.rst and include/patchlevel.h files to ensure they now reflect the desired post-release values for on-going development. The patchlevel should be the release tag with a + . Also, if you cherry-picked changes from the standard release branch into the release engineering branch for this release, you will now need to manually remove each blurb entry from the Misc/NEWS.d/next directory that was cherry-picked into the release you are working on since that blurb entry is now captured in the merged x.y.z.rst file for the new release. Otherwise, the blurb entry will appear twice in the changelog.html file, once under Python next and again under x.y.z . Review and commit these changes: git commit -m 'Post release updates' If this is a new branch release (e.g. the first beta), update the main branch to start development for the following feature release. When finished, the main branch will now build Python X.Y+1 . First, set main up to be the next release, i.e. X.Y+1.a0: git checkout main .../release-tools/release.py --bump 3 .9.0a0 Edit all version references in README.rst Edit Doc/tutorial/interpreter.rst (two references to ‘[Pp]ython3x’, one to ‘Python 3.x’, also make the date in the banner consistent). Edit Doc/tutorial/stdlib.rst and Doc/tutorial/stdlib2.rst , which have each one reference to ‘[Pp]ython3x’. Add a new whatsnew/3.x.rst file (with the comment near the top and the toplevel sections copied from the previous file) and add it to the toctree in whatsnew/index.rst . But beware that the initial whatsnew/3.x.rst checkin from previous releases may be incorrect due to the initial midstream change to blurb that propagates from release to release! Help break the cycle: if necessary make the following change: -For full details, see the :source:`Misc/NEWS` file. +For full details, see the :ref:`changelog <changelog>`. Update the version number in configure.ac and re-run autoconf . Make sure the SOURCE_URI in Doc/tools/extensions/pyspecific.py points to main . Update the version numbers for the Windows builds which have references to python38 : ls PC/pyconfig.h.in PCbuild/rt.bat | xargs sed -i 's/python3\(\.\?\)[0-9]\+/python3\19/g' Edit the bug.yml and crash.yml issue templates in .github/ISSUE_TEMPLATE/ to add the new branch to the “versions” dropdown. Commit these changes to the main branch: git status git add ... git commit -m 'Bump to 3.9.0a0' Do another git status in this directory. You should not see any files, i.e., you better not have any uncommitted changes in your working directory. Commit and push to the main repo: # Do a dry run first. # For feature pre-releases prior to a **new branch** release, # i.e. a feature alpha release: git push --dry-run --tags git@github.com:python/cpython.git main # If it looks OK, take the plunge. There's no going back! git push --tags git@github.com:python/cpython.git main # For a **new branch** release, i.e. first beta: git push --dry-run --tags git@github.com:python/cpython.git 3 .X git push --dry-run --tags git@github.com:python/cpython.git main # If it looks OK, take the plunge. There's no going back! git push --tags git@github.com:python/cpython.git 3 .X git push --tags git@github.com:python/cpython.git main # For all other releases: git push --dry-run --tags git@github.com:python/cpython.git 3 .X # If it looks OK, take the plunge. There's no going back! git push --tags git@github.com:python/cpython.git 3 .X If this is a new branch release, add a Branch protection rule for the newly created branch (3.X). Look at the values for the previous release branch (3.X-1) and use them as a template. https://github.com/python/cpython/settings/branches Also, add 3.x and needs backport to 3.X labels to the GitHub repo. https://github.com/python/cpython/labels You can now re-enable enforcement of branch settings against administrators on GitHub. Go back to the Settings | Branch page: https://github.com/python/cpython/settings/branches “Edit” the settings for the branch you’re releasing on. Re-check the “Include administrators” box and press the “Save changes” button at the bottom. Now it’s time to twiddle the website. Almost none of this is automated, sorry. To do these steps, you must have the permission to edit the website. If you don’t have that, ask someone on pydotorg @ python . org for the proper permissions. Log in to https://www.python.org/admin Create a new “release” for the release. Currently “Releases” are sorted under “Downloads”. The easiest thing is probably to copy fields from an existing Python release “page”, editing as you go. You can use Markdown or reStructured Text to describe your release. The former is less verbose, while the latter has nifty integration for things like referencing PEPs. Leave the “Release page” field on the form empty. “Save” the release. Populate the release with the downloadable files. Your friend and mine, Georg Brandl, made a lovely tool called add_to_pydotorg.py . You can find it in the python/release-tools repo (next to release.py ). You run the tool on downloads.nyc1.psf.io , like this: AUTH_INFO = <username>:<python.org-api-key> python add_to_pydotorg.py <version> This walks the correct download directory for <version> , looks for files marked with <version> , and populates the “Release Files” for the correct “release” on the web site with these files. Note that clears the “Release Files” for the relevant version each time it’s run. You may run it from any directory you like, and you can run it as many times as you like if the files happen to change. Keep a copy in your home directory on dl-files and keep it fresh. If new types of files are added to the release, someone will need to update add_to_pydotorg.py so it recognizes these new files. (It’s best to update add_to_pydotorg.py when file types are removed, too.) The script will also sign any remaining files that were not signed with Sigstore until this point. Again, if this happens, do use your @python.org address for this process. More info: https://www.python.org/downloads/metadata/sigstore/ In case the CDN already cached a version of the Downloads page without the files present, you can invalidate the cache using: curl -X PURGE https://www.python.org/downloads/release/python-XXX/ Write the announcement on discuss.python.org . This is the fuzzy bit because not much can be automated. You can use an earlier announcement as a template, but edit it for content! Also post the announcement to the Python Insider blog . To add a new entry, go to your Blogger home page . Update release PEPs (e.g. 719) with the release dates. Update the labels on https://github.com/python/cpython/issues : Flip all the deferred-blocker issues back to release-blocker for the next release. Review open issues, as this might find lurking showstopper bugs, besides reminding people to fix the easy ones they forgot about. You can delete the remote release clone branch from your repo clone. If this is a new branch release, you will need to ensure various pieces of the development infrastructure are updated for the new branch. These include: Update the issue tracker for the new branch: add the new version to the versions list. Update python-releases.toml to reflect the new branches and versions. Create a PR to update the supported releases table on the downloads page (see python/pythondotorg#1302 ). Ensure buildbots are defined for the new branch (contact Łukasz or Zach Ware). Ensure the various GitHub bots are updated, as needed, for the new branch. In particular, make sure backporting to the new branch works (contact the core-workflow team ). Review the most recent commit history for the main and new release branches to identify and backport any merges that might have been made to the main branch during the release engineering phase and that should be in the release branch. Verify that CI is working for new PRs for the main and new release branches and that the release branch is properly protected (no direct pushes, etc). Verify that the online docs are building properly (this may take up to 24 hours for a complete build on the website). What Next? Verify! Pretend you’re a user: download the files from www.python.org , and make Python from it. This step is too easy to overlook, and on several occasions we’ve had useless release files. Once a general server problem caused mysterious corruption of all files; once the source tarball got built incorrectly; more than once the file upload process on SF truncated files; and so on. Rejoice. Drink. Be Merry. Write a PEP like this one. Or be like unto Guido and take A Vacation. You’ve just made a Python release! Moving to End-of-life Under current policy, a release branch normally reaches end-of-life status five years after its initial release. The policy is discussed in more detail in the Python Developer’s Guide . When end-of-life is reached, there are a number of tasks that need to be performed either directly by you as release manager or by ensuring someone else does them. Some of those tasks include: Optionally making a final release to publish any remaining unreleased changes. Freeze the state of the release branch by creating a tag of its current HEAD and then deleting the branch from the CPython repo. The current HEAD should be at or beyond the final security release for the branch: git fetch upstream git tag --sign -m 'Final head of the former 3.3 branch' 3 .3 upstream/3.3 git push upstream refs/tags/3.3 If all looks good, delete the branch. This may require the assistance of someone with repo administrator privileges: git push upstream --delete 3 .3 # or perform from GitHub Settings page Remove the release from the list of “Active Python Releases” on the Downloads page. To do this, log in to the admin page for python.org, navigate to Boxes, and edit the downloads-active-releases entry. Strip out the relevant paragraph of HTML for your release. (You’ll probably have to do the curl -X PURGE trick to purge the cache if you want to confirm you made the change correctly.) Add a retired notice to each release page on python.org for the retired branch. For example: https://www.python.org/downloads/release/python-337/ https://www.python.org/downloads/release/python-336/ In python-releases.toml , set the branch status to end-of-life. Update or remove references to the branch in the developer’s guide . Retire the release from the issue tracker . Tasks include: update issues from this version to the next supported version remove version label from list of versions remove the needs backport to label for the retired version review and dispose of open issues marked for this branch Run a final build of the online docs to add the end-of-life banner Announce the branch retirement in the usual places: discuss.python.org Python Insider blog Enjoy your retirement and bask in the glow of a job well done! Windows Notes Windows has a MSI installer, various flavors of Windows have “special limitations”, and the Windows installer also packs precompiled “foreign” binaries (Tcl/Tk, expat, etc). The installer is tested as part of the Azure Pipeline. In the past, those steps were performed manually. We’re keeping this for posterity. Concurrent with uploading the installer, the WE installs Python from it twice: once into the default directory suggested by the installer, and later into a directory with embedded spaces in its name. For each installation, the WE runs the full regression suite from a DOS box, and both with and without -0. For maintenance release, the WE also tests whether upgrade installations succeed. The WE also tries every shortcut created under Start -> Menu -> the Python group. When trying IDLE this way, you need to verify that Help -> Python Documentation works. When trying pydoc this way (the “Module Docs” Start menu entry), make sure the “Start Browser” button works, and make sure you can search for a random module (like “random” <wink>) and then that the “go to selected” button works. It’s amazing how much can go wrong here – and even more amazing how often last-second checkins break one of these things. If you’re “the Windows geek”, keep in mind that you’re likely the only person routinely testing on Windows, and that Windows is simply a mess. Repeat the testing for each target architecture. Try both an Admin and a plain User (not Power User) account. Copyright This document has been placed in the public domain. Source: https://github.com/python/peps/blob/main/peps/pep-0101.rst Last modified: 2026-01-06 11:22:48 GMT Contents Abstract Things You’ll Need Types of Releases How To Make A Release What Next? Moving to End-of-life Windows Notes Copyright Page Source (GitHub) | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/anthonymax | Anthony Max - 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 User actions Anthony Max 🐜 Fetch API enjoyer | collab: aanthonymaxgithub@gmail.com Joined Joined on Sep 20, 2024 Personal website https://hmpl-lang.dev github website twitter website Education Unfinished bachelor's degree Pronouns Anthony or Tony Work HMPL.js 2025 Hacktoberfest Writing Challenge Completion Awarded for completing at least one prompt in the 2025 Hacktoberfest Writing Challenge. Thank you for sharing your open source story! 🎃✍️ 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 16 Week Community Wellness Streak You're a dedicated community champion! Keep up the great work by posting at least 2 comments per week for 16 straight weeks. The prized 24-week badge is within reach! Got it Close JavaScript Awarded to the top JavaScript author each week Got it Close 8 Week Community Wellness Streak Consistency pays off! Be an active part of our community by posting at least 2 comments per week for 8 straight weeks. Earn the 16 Week Badge next. Got it Close Top 7 Awarded for having a post featured in the weekly "must-reads" list. 🙌 Got it Close 4 Week Community Wellness Streak Keep contributing to discussions by posting at least 2 comments per week for 4 straight weeks. Unlock the 8 Week Badge next. Got it Close 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 More info about @anthonymax Organizations HMPL.js Skills/Languages TypeScript, Docker, Saas, Vue.js, PostCSS Currently learning Fortran, Basic Currently hacking on Microwave Available for Build an anthill Post 7 posts published Comment 403 comments written Tag 0 tags followed 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 Want to connect with Anthony Max? Create an account to connect with Anthony Max. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in 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... 💎 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/kevburnsjr/websockets-vs-long-polling-3a0o#scaling-down | 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/web3/page/6 | Web3 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 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 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 DeArrow: Crowdsourcing Better YouTube Titles and Thumbnails Stelixx Insider Stelixx Insider Stelixx Insider Follow Dec 14 '25 DeArrow: Crowdsourcing Better YouTube Titles and Thumbnails # ai # web3 # blockchain # productivity Comments Add Comment 2 min read Cómo escribir smart contracts en Midnight Cardumen Cardumen Cardumen Follow Dec 13 '25 Cómo escribir smart contracts en Midnight # privacy # tutorial # blockchain # web3 Comments Add Comment 3 min read The “Vibe Coding” Revolution: Why Syntax is Dead and “Vibes” Are the New Programming Language Tech Croc Tech Croc Tech Croc Follow Dec 12 '25 The “Vibe Coding” Revolution: Why Syntax is Dead and “Vibes” Are the New Programming Language # webdev # programming # ai # web3 Comments Add Comment 2 min read An Analysis of Arbitrage Markets Across Ethereum, Solana, Optimism, and Starknet (2024-2025) Erick Fernandez Erick Fernandez Erick Fernandez Follow for Extropy.IO Dec 12 '25 An Analysis of Arbitrage Markets Across Ethereum, Solana, Optimism, and Starknet (2024-2025) # analytics # ethereum # blockchain # web3 Comments Add Comment 14 min read AI continues its pervasive integration across industries, from entertainment and tech giants to automotive and public services. Stelixx Insights Stelixx Insights Stelixx Insights Follow Dec 12 '25 AI continues its pervasive integration across industries, from entertainment and tech giants to automotive and public services. # ai # web3 # blockchain # productivity Comments Add Comment 1 min read Building Story CLI: From 30-Minute IP Registration to Under 5 Ola Adesoye Ola Adesoye Ola Adesoye Follow Dec 15 '25 Building Story CLI: From 30-Minute IP Registration to Under 5 # blockchain # web3 # cli # programming Comments Add Comment 4 min read REST vs GraphQL vs gRPC — Which One Should You Really Use? Vignesh Nagarajan Vignesh Nagarajan Vignesh Nagarajan Follow Dec 17 '25 REST vs GraphQL vs gRPC — Which One Should You Really Use? # programming # productivity # web3 1 reaction Comments 1 comment 3 min read Payra WooCommerce Plugin 1.0.2 - Added Transaction Fee Support Wraith Wraith Wraith Follow Dec 12 '25 Payra WooCommerce Plugin 1.0.2 - Added Transaction Fee Support # woocommerce # crypto # wordpress # web3 Comments Add Comment 1 min read Ethereum’s 2025 Endgame: 60M Gas Blocks, EIL Cross-L2 Architecture, ARBOS Unification & On-Chain Fan Identity Ankita Virani Ankita Virani Ankita Virani Follow Dec 11 '25 Ethereum’s 2025 Endgame: 60M Gas Blocks, EIL Cross-L2 Architecture, ARBOS Unification & On-Chain Fan Identity # architecture # ethereum # web3 Comments Add Comment 4 min read Why const Doesn’t Freeze Your JavaScript Arrays Luba Luba Luba Follow Dec 11 '25 Why const Doesn’t Freeze Your JavaScript Arrays # javascript # webdev # web3 # tutorial Comments Add Comment 3 min read Issue #7: Blockchain security and attacks Temiloluwa Akintade Temiloluwa Akintade Temiloluwa Akintade Follow Dec 15 '25 Issue #7: Blockchain security and attacks # web3 # blockchain 1 reaction Comments 1 comment 3 min read OpenTelemetry - stepping into gno.land's observability tools Sergio Matone Sergio Matone Sergio Matone Follow Dec 11 '25 OpenTelemetry - stepping into gno.land's observability tools # devops # web3 # blockchain Comments Add Comment 8 min read Fusaka Goes Live, EIL vs OIF Debate, Rewardy Launches ERC-7702 Wallet, 7702 Unlocks Recovering Assets Alexandra Alexandra Alexandra Follow for Etherspot Dec 11 '25 Fusaka Goes Live, EIL vs OIF Debate, Rewardy Launches ERC-7702 Wallet, 7702 Unlocks Recovering Assets # ethereum # web3 # blockchain Comments Add Comment 6 min read Understanding Flow’s Lending Protocol Architecture Rohit Purkait Rohit Purkait Rohit Purkait Follow Dec 12 '25 Understanding Flow’s Lending Protocol Architecture # web3 # tutorial # architecture # beginners 4 reactions Comments 3 comments 3 min read Custom Base op-Erigon Node for AMM Analytics. When Standard Infrastructure Solutions are Not Enough GetBlock GetBlock GetBlock Follow for GetBlock Dec 11 '25 Custom Base op-Erigon Node for AMM Analytics. When Standard Infrastructure Solutions are Not Enough # web3 # blockchain # go Comments Add Comment 4 min read Automa: Empowering Browser Automation for Developers Stelixx Insider Stelixx Insider Stelixx Insider Follow Dec 12 '25 Automa: Empowering Browser Automation for Developers # ai # web3 # blockchain # productivity 3 reactions Comments 1 comment 2 min read An Overview of EIP-3009: Transfer With Authorisation Erick Fernandez Erick Fernandez Erick Fernandez Follow for Extropy.IO Dec 9 '25 An Overview of EIP-3009: Transfer With Authorisation # ux # ethereum # web3 # blockchain Comments Add Comment 4 min read Architecting RWAs: Architecting RWAs: How We Built a Modular Policy Engine for Tokenized Assets Anya Volkov Anya Volkov Anya Volkov Follow Dec 22 '25 Architecting RWAs: Architecting RWAs: How We Built a Modular Policy Engine for Tokenized Assets # blockchain # architecture # solidity # web3 Comments 1 comment 2 min read akash DSL 参考 drake drake drake Follow Dec 9 '25 akash DSL 参考 # devops # cloudcomputing # networking # web3 Comments Add Comment 1 min read RAGFlow: Open-Source Engine for Deep Document Understanding Stelixx Insider Stelixx Insider Stelixx Insider Follow Dec 8 '25 RAGFlow: Open-Source Engine for Deep Document Understanding # ai # web3 # blockchain # productivity Comments Add Comment 1 min read The Double-Edged Sword of "Flow State" in Game Dev ⚔️ crow crow crow Follow Dec 11 '25 The Double-Edged Sword of "Flow State" in Game Dev ⚔️ # productivity # mentalhealth # web3 # developers 1 reaction Comments 1 comment 3 min read Build with Openfort and get paid: bounties for devs available! Juan Juan Juan Follow Dec 8 '25 Build with Openfort and get paid: bounties for devs available! # rewards # bounty # blockchain # web3 Comments Add Comment 1 min read How BUBUVERSE Is Blending Web3 Gaming, NFTs, and Scalable Infrastructure bubuverse bubuverse bubuverse Follow Dec 8 '25 How BUBUVERSE Is Blending Web3 Gaming, NFTs, and Scalable Infrastructure # webdev # ai # blockchain # web3 Comments Add Comment 2 min read How to Store Critical Secrets for 100+ Years Mohamad Nashaat Mohamad Nashaat Mohamad Nashaat Follow Dec 10 '25 How to Store Critical Secrets for 100+ Years # dapp # blockchain # web3 # cybersecurity 1 reaction Comments 2 comments 3 min read Where Can I Find Reviews of Popular Blockchain Certification Courses? Georgia Weston Georgia Weston Georgia Weston Follow Dec 8 '25 Where Can I Find Reviews of Popular Blockchain Certification Courses? # productivity # blockchain # web3 # career 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/5 | Web3 Page 5 - 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 2 3 4 5 6 7 8 9 10 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu TokenEscrowV1: Fixing MPT Escrow Accounting Shashwat Mittal Shashwat Mittal Shashwat Mittal Follow for RippleX Developers Dec 17 '25 TokenEscrowV1: Fixing MPT Escrow Accounting # news # blockchain # web3 Comments Add Comment 2 min read Integrating Trust: A Developer's Guide to the Resume Protocol Obinna Duru Obinna Duru Obinna Duru Follow Dec 21 '25 Integrating Trust: A Developer's Guide to the Resume Protocol # webdev # web3 # typescript # ipfs 1 reaction Comments Add Comment 5 min read How to Get Paid in USDC - The Easiest Way jimquote jimquote jimquote Follow Dec 19 '25 How to Get Paid in USDC - The Easiest Way # cryptocurrency # tutorial # web3 Comments Add Comment 4 min read Vitalik’s Gas Futures, EIL X Space, Polygon Upgrade, USDT Gas Fees, ERC-8092 Alexandra Alexandra Alexandra Follow for Etherspot Dec 18 '25 Vitalik’s Gas Futures, EIL X Space, Polygon Upgrade, USDT Gas Fees, ERC-8092 # blockchain # web3 # ethereum 1 reaction Comments Add Comment 6 min read Designing AI Automation for Millions: CX Lessons from the Front Lines Aun Raza Aun Raza Aun Raza Follow Dec 20 '25 Designing AI Automation for Millions: CX Lessons from the Front Lines # ai # automation # cx # web3 1 reaction Comments Add Comment 6 min read Building a Gasless Crypto Payment Flow: How ERC-3009 Eliminates User Gas Fees jimquote jimquote jimquote Follow Dec 16 '25 Building a Gasless Crypto Payment Flow: How ERC-3009 Eliminates User Gas Fees # ux # web3 # ethereum # cryptocurrency Comments Add Comment 3 min read Daily AI & Automation Tech News - December 18, 2025 Web3 Web3 Web3 Follow Dec 18 '25 Daily AI & Automation Tech News - December 18, 2025 # ai # automation # blockchain # web3 1 reaction Comments 1 comment 6 min read Building a Decentralized AI Training Network: Challenges and Opportunities Kyro Kyro Kyro Follow Dec 18 '25 Building a Decentralized AI Training Network: Challenges and Opportunities # ai # machinelearning # web3 # blockchain 1 reaction Comments 2 comments 5 min read Your Career, Onchain: Building a Resume Protocol with Purpose and Trust Obinna Duru Obinna Duru Obinna Duru Follow Dec 21 '25 Your Career, Onchain: Building a Resume Protocol with Purpose and Trust # web3 # solidity # beginners # blockchain 3 reactions Comments Add Comment 4 min read 美股实时行情 API：历史数据与深度盘口技术指南 San Si wu San Si wu San Si wu Follow Dec 16 '25 美股实时行情 API：历史数据与深度盘口技术指南 # python # tutorial # web3 Comments Add Comment 2 min read 🎓 Thrilled to Announce My BTech 3rd Year Project 🚀 Blockchain-Based Digital Credential Verification System HARSH D HARSH D HARSH D Follow Jan 9 🎓 Thrilled to Announce My BTech 3rd Year Project 🚀 Blockchain-Based Digital Credential Verification System # showdev # blockchain # nextjs # web3 1 reaction Comments Add Comment 1 min read Building a Prediction Market on Solana with Anchor: Complete Rust Smart Contract Guide Sivaram Sivaram Sivaram Follow Jan 8 Building a Prediction Market on Solana with Anchor: Complete Rust Smart Contract Guide # solana # web3 # smartcontract # predictionmarket 6 reactions Comments 1 comment 11 min read LUMEN: A Minimal On-Chain Context Bus for Coordinating AI Agents (Live on Base) Maven Jang Maven Jang Maven Jang Follow Dec 16 '25 LUMEN: A Minimal On-Chain Context Bus for Coordinating AI Agents (Live on Base) # ai # langchain # web3 Comments Add Comment 3 min read 7 Days on Mantle: From 'Hello World' to a Full-Stack RWA dApp Azhar Aditya Pratama Azhar Aditya Pratama Azhar Aditya Pratama Follow Dec 14 '25 7 Days on Mantle: From 'Hello World' to a Full-Stack RWA dApp # ethereum # beginners # learning # web3 Comments Add Comment 2 min read Building a Privacy-Preserving Voting App Marycynthia Ihemebiwo Marycynthia Ihemebiwo Marycynthia Ihemebiwo Follow Dec 19 '25 Building a Privacy-Preserving Voting App # privacy # web3 # security # tutorial Comments Add Comment 1 min read Lessons from building a Solana project using iPhone Mukesh Ranjan Mukesh Ranjan Mukesh Ranjan Follow Jan 8 Lessons from building a Solana project using iPhone # devjournal # ios # learning # web3 Comments Add Comment 10 min read Why Zero Knowledge Proofs are like a Lunar Landscape. Erick Fernandez Erick Fernandez Erick Fernandez Follow for Extropy.IO Dec 15 '25 Why Zero Knowledge Proofs are like a Lunar Landscape. # web3 # zeroknowledge # math # blockchain Comments Add Comment 1 min read Invisible Online? Here Is Why AI Doesn’t Cite Your Website Nick Talwar Nick Talwar Nick Talwar Follow Dec 15 '25 Invisible Online? Here Is Why AI Doesn’t Cite Your Website # ai # seo # startup # web3 Comments Add Comment 3 min read Reflection of Co-Learning Mantle week 1 Bagas Hariyanto Bagas Hariyanto Bagas Hariyanto Follow Dec 14 '25 Reflection of Co-Learning Mantle week 1 # ethereum # learning # web3 # devjournal Comments Add Comment 2 min read Async Assumptions That Create Security Blind Spots in Web3 Backends. Progress Ochuko Eyaadah Progress Ochuko Eyaadah Progress Ochuko Eyaadah Follow Jan 7 Async Assumptions That Create Security Blind Spots in Web3 Backends. # security # web3 # web3backend # blockchain 5 reactions Comments Add Comment 4 min read What Is a Buyer Persona and Why Does It Matter Dipti Moryani Dipti Moryani Dipti Moryani Follow Dec 15 '25 What Is a Buyer Persona and Why Does It Matter # webdev # programming # ai # web3 Comments Add Comment 5 min read Mastering Sui DeepBook: A Hands-On DeFi DEX Series (3) Rajesh Royal Rajesh Royal Rajesh Royal Follow Dec 18 '25 Mastering Sui DeepBook: A Hands-On DeFi DEX Series (3) # tutorial # sui # blockchain # web3 5 reactions Comments Add Comment 5 min read DeArrow: Crowdsourcing Better YouTube Titles and Thumbnails Stelixx Insider Stelixx Insider Stelixx Insider Follow Dec 14 '25 DeArrow: Crowdsourcing Better YouTube Titles and Thumbnails # ai # web3 # blockchain # productivity Comments Add Comment 2 min read Cómo escribir smart contracts en Midnight Cardumen Cardumen Cardumen Follow Dec 13 '25 Cómo escribir smart contracts en Midnight # privacy # tutorial # blockchain # web3 Comments Add Comment 3 min read The “Vibe Coding” Revolution: Why Syntax is Dead and “Vibes” Are the New Programming Language Tech Croc Tech Croc Tech Croc Follow Dec 12 '25 The “Vibe Coding” Revolution: Why Syntax is Dead and “Vibes” Are the New Programming Language # webdev # programming # ai # web3 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/hmpljs/major-module-update-31p5 | Major module update! - 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 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 Anthony Max for HMPL.js Posted on Nov 17, 2025 Major module update! # webdev # javascript # programming # opensource Hello everyone! In this short article, I'd like to talk about the new versions we recently released. It would seem that the modules are quite utilitarian and there is no particular point in updating them, but nevertheless, it is worth keeping them up to date today, and we will talk about some of the changes in them today. Stay informed! ⚙️ vite-plugin-hmpl and hmpl-loader In case you weren't aware, .hmpl actually has its own file extension. Loading it requires loaders, which were created specifically for Vite and WebPack. For these, we've updated the settings validation, which relies on the following types: interface HMPLCompileOptions { memo?: boolean; autoBody?: boolean | HMPLAutoBodyOptions; allowedContentTypes?: HMPLContentTypes; sanitize?: HMPLSanitize; disallowedTags?: HMPLDisallowedTags; sanitizeConfig?: Config; } Enter fullscreen mode Exit fullscreen mode A small, but also quite interesting update. 🌳 hmpl-dom This module is designed to use templating language syntax without npm or other add-ons. Nothing else is needed, just a single index.html file and that's it. In this update, we've added hmpl-dom.runtime.js . This is also quite an update. They've also updated the README files and other texts everywhere, but that's not really important in the context of releases. 💬 Feedback You can write your thoughts about the new features in the comments, it will be interesting to read! Or, there is a thematic Discord channel for questions and suggestions, there I or someone else will try to answer! ✅ This project is Open Source So you can take part in it too! This also means you can use it for commercial purposes: Repo: https://github.com/hmpl-language/hmpl (Star Us ★) Website: https://hmpl-lang.dev Full list of changes: https://hmpl-lang.dev/changelog Thank you very much for reading the article! 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 Anthony Max HMPL.js Anthony Max HMPL.js Anthony Max Follow 🐜 Fetch API enjoyer | collab: aanthonymaxgithub@gmail.com Education Unfinished bachelor's degree Pronouns Anthony or Tony Work HMPL.js Joined Sep 20, 2024 • Nov 17 '25 Dropdown menu Copy link Hide What do you think about the updates? Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Art light Art light Art light Follow Trust yourself🌞your capabilities are your true power. ❤Telegram - ✔lighthouse4661 ❤Discord - ✔lighthouse4661 Email art.miclight@gmail.com Pronouns He/him Work CTO Joined Nov 21, 2025 • Dec 5 '25 Dropdown menu Copy link Hide Great job on the update! The new changes look really solid, and I appreciate how clearly you explained everything. I’m especially interested in the improvements to the loaders and the new runtime addition. Looking forward to seeing how the project grows—keep it up! 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 HMPL.js Follow 🐜 Server-oriented customizable templating for JavaScript The proudly project is Open Source 🌱, so we would be very grateful if you supported it with a star! 💎 Support Us ☆ 💎 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/community/workshops/#content | Conferences and Workshops | 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 >>> Python Conferences Conferences and Workshops Conference Listings There are quite a number of Python conferences happening all year around and in many parts of the world. Many of them are taking place yearly or even more frequent: Python Conferences List on the Python Wiki -- this is the main and most complete list of conferences around the world Subsets of this list are also available on other sites: pycon.org -- lists a subset of mostly national Python conferences PyData -- listings of Python conferences specializing in AI & Data Science Several of these conferences record the talk sessions on video. pyvideo.org provides an index to a large set these videos. Announcing Events If you would like to announce a Python related event, please see Submitting an event to the Python events calendars . You can also ask on pydotorg-www at python dot org for help. Adding Conferences If you have an event to add, please see the instructions on how to edit Python Wiki for details. If you are organizing a Python conference or thinking of organizing one, please subscribe to the Python conferences mailing list . 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/workshops/#top | Conferences and Workshops | 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 >>> Python Conferences Conferences and Workshops Conference Listings There are quite a number of Python conferences happening all year around and in many parts of the world. Many of them are taking place yearly or even more frequent: Python Conferences List on the Python Wiki -- this is the main and most complete list of conferences around the world Subsets of this list are also available on other sites: pycon.org -- lists a subset of mostly national Python conferences PyData -- listings of Python conferences specializing in AI & Data Science Several of these conferences record the talk sessions on video. pyvideo.org provides an index to a large set these videos. Announcing Events If you would like to announce a Python related event, please see Submitting an event to the Python events calendars . You can also ask on pydotorg-www at python dot org for help. Adding Conferences If you have an event to add, please see the instructions on how to edit Python Wiki for details. If you are organizing a Python conference or thinking of organizing one, please subscribe to the Python conferences mailing list . 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.youtube.com/ads/ | 온라인 동영상 광고 캠페인 - YouTube 광고 콘텐츠로 이동 YouTube를 선택해야 하는 이유 작동 방식 개요 작동 방식 채널 만들기 채널 시작하기 광고 제작 동영상 광고 제작 캠페인 설정 캠페인 설정하기 잠재고객 찾기 예산 결정 실적 측정 실적을 측정하세요 뉴스 및 아이디어 리소스 개요 리소스 광고 소재 크리에이티브 리소스 크리에이터 크리에이터 프로모션 측정 측정 도구 통계 권장사항 성공사례 FAQ 카카오톡 상담 카카오톡 상담을 시작하기 위해 아이콘을 클릭해주세요 (월-금 9:30 - 18:00) 1-877-763-9810 지금 시작하기 YouTube Ads를 통해 비즈니스 성장을 도모하세요 잠재고객이 시청하는 플랫폼을 통해 도달하여 채널의 주목도를 높이고 비즈니스 성과를 창출해 보세요 광고 시작하기 작동 방식 알아보기 고객에게 다가가고 새로운 고객을 찾으세요 거리 곳곳의 미식가, 전국의 패셔니스타. 온라인상의 더 많은 곳에서 정보를 검색, 탐색하거나 콘텐츠를 시청하는 고객에게 도달하세요. YouTube가 비즈니스에 가장 중요한 사람들과 연결해 줍니다. 천 마디 말보다 한 번 보는 게 더 낫다는 말이 있습니다. 동영상은 백만 마디의 가치가 있습니다. 뇨르드 로타 Majestic Heli Ski 사업주 중요한 순간에 등장하기 예산 규모에 상관없이 시청자를 고객으로 전환하세요. YouTube Ads는 Google 데이터를 사용하여 적절한 순간에 적절한 사용자에게 메시지를 전달합니다. 관련성이 가장 높은 순간에 정확하게 사용자에게 도달할 수 있었습니다. 킴 톰슨, Spark Foundry 원하는 성과를 달성하세요 사람들은 YouTube Ads를 통해 더욱 쉽게 비즈니스를 선택할 수 있습니다. 매출, 구독자 수, 웹사이트 방문자 수 등을 늘려보세요. YouTube에서 광고를 시작한 후로 매출이 매년 거의 두 배씩 성장했습니다. 스테파니 슈베허, Tulane's Closet 소유주 겸 개발자 고객에게 다가가고 새로운 고객을 찾으세요 거리 곳곳의 미식가, 전국의 패셔니스타. 온라인상의 더 많은 곳에서 정보를 검색, 탐색하거나 콘텐츠를 시청하는 고객에게 도달하세요. YouTube가 비즈니스에 가장 중요한 사람들과 연결해 줍니다. 천 마디 말보다 한 번 보는 게 더 낫다는 말이 있습니다. 동영상은 백만 마디의 가치가 있습니다. 뇨르드 로타 Majestic Heli Ski 사업주 중요한 순간에 등장하기 예산 규모에 상관없이 시청자를 고객으로 전환하세요. YouTube Ads는 Google 데이터를 사용하여 적절한 순간에 적절한 사용자에게 메시지를 전달합니다. 관련성이 가장 높은 순간에 정확하게 사용자에게 도달할 수 있었습니다. 킴 톰슨, Spark Foundry 원하는 성과를 달성하세요 사람들은 YouTube Ads를 통해 더욱 쉽게 비즈니스를 선택할 수 있습니다. 매출, 구독자 수, 웹사이트 방문자 수 등을 늘려보세요. YouTube에서 광고를 시작한 후로 매출이 매년 거의 두 배씩 성장했습니다. 스테파니 슈베허, Tulane's Closet 소유주 겸 개발자 2 X 시청자가 YouTube에서 상품을 접한 경우 구매 가능성이 2배 높은 것으로 조사되었습니다. 1 70 % 70%가 넘는 시청자가 YouTube를 통해 새로운 브랜드를 알게 된다고 응답했습니다. 2 4 X 시청자는 브랜드, 제품, 서비스에 대한 정보를 찾을 때 YouTube를 다른 플랫폼에 비해 4배 더 많이 사용합니다. 3 효과적인 광고 제작에 필요한 모든 것 누구나 실적을 높일 수 있는 YouTube 광고를 만들 수 있습니다. 스마트폰에서 바로 동영상을 만들거나 Google에서 제공하는 무료 도구와 리소스를 사용하세요. 도움이 될 완벽한 파트너를 찾을 수도 있습니다. 자세히 알아보기 YouTube 광고 시작하기 지금 시작하기 1 경쟁사 평균 대비. 출처: Google/Talkshoppe, 미국, whyVideo 연구, 응답자 수 2,000명, 만 18~64세 일반 대중 동영상 사용자 대상, 2020년 2월 2, 3 출처: Google/Talkshoppe, 미국, whyVideo 연구, 응답자 수 2,000명, 만 18~64세 일반 대중 동영상 사용자 대상, 2020년 2월 SNS YouTube 소개 정보 블로그 YouTube 작동의 원리 채용정보 보도자료 YouTube Culture & Trends 제품 YouTube Kids YouTube Music YouTube Originals YouTube Podcasts YouTube Premium YouTube Select YouTube Studio YouTube TV 비즈니스 개발자 YouTube 광고 크리에이터 YouTube Kids 콘텐츠 제작 크리에이터 리서치 크리에이터 서비스 디렉토리 YouTube for Artists YouTube Creators YouTube NextUp YouTube VR YouTube의 약속 Creators for Change CSAI Match 사회 공헌 YouTube 소개 제품 비즈니스 크리에이터 YouTube의 약속 정보 블로그 YouTube 작동의 원리 채용정보 보도자료 YouTube Culture & Trends YouTube Kids YouTube Music YouTube Originals YouTube Podcasts YouTube Premium YouTube Select YouTube Studio YouTube TV 개발자 YouTube 광고 YouTube Kids 콘텐츠 제작 크리에이터 리서치 크리에이터 서비스 디렉토리 YouTube for Artists YouTube Creators YouTube NextUp YouTube VR Creators for Change CSAI Match 사회 공헌 정책 및 안전 저작권 브랜드 가이드라인 개인 정보 보호 약관 Cookies management controls 도움말 العربية (الإمارات العربية المتحدة) English español (Argentina) English (Australia) português (Brasil) English (Canada) español (Chile) 中文 (简体, 中国) español (Colombia) Deutsch (Deutschland) español (España) français (France) 中文 (繁體字, 中國香港特別行政區) Bahasa Indonesia (Bahasa Indonesia) עברית (ישראל) English (India) italiano (Italia) 日本語 (日本) 한국어 (대한민국) español (México) Nederlands (Nederland) español (Perú) polski (Polska) русский (Россия) svenska (Sverige) English (Singapore) ไทย (ไทย) Türkçe (Türkiye) 中文 (繁體, 台灣) українська (Україна) English (United Kingdom) Tiếng Việt (Việt Nam) English (UAE) English (China) English (Hong Kong SAR China) English (Bahasa Indonesia) English (Israel) English (Malaysia) English (United States) español (Estados Unidos) français (Canada) हिन्दी (भारत) Melayu (Malaysia) 쿠폰 이용약관: 아래의 이용약관에서 'Google Ads'는 상황에 따라 Google Ads 또는 Google Ads Express를 의미할 수 있습니다. 이 쿠폰은 청구서 수신 주소가 미국 내에 있는 고객만 사용할 수 있습니다. 광고주당 사용할 수 있는 프로모션 코드는 1개로 제한됩니다. 이 쿠폰을 사용하려면 2020년 12월 31일까지 계정에 프로모션 코드를 입력해야 합니다. 이 쿠폰을 사용하려면 첫 Google Ads 계정에서 광고 노출이 처음 발생한 날로부터 14일 이내에 코드를 입력해야 합니다. 크레딧을 받으려면 프로모션 코드를 입력한 후 30일 이내에 광고 캠페인에서 비용이 50달러(세금 제외) 이상 발생해야 합니다. 50달러의 광고비를 결제하는 것만으로는 크레딧을 받을 수 없습니다. 광고비가 50달러 이상 지출되었는지에 대한 추적은 프로모션 코드를 입력한 다음부터 진행됩니다. 2단계와 3단계가 완료되면 보통 5일 이내에 계정의 결제 요약에 크레딧이 반영됩니다. 크레딧은 향후 광고비에만 적용되며, 코드를 입력하기 전에 발생한 비용에는 크레딧이 적용되지 않습니다. 크레딧 금액이 소진될 때 알림이 제공되지 않으며, 추가로 발생하는 광고비는 계정에서 선택한 결제 방법으로 청구됩니다. 광고를 계속하지 않은 경우 언제든지 캠페인을 일시중지하거나 삭제할 수 있습니다. 프로모션 크레딧을 받으려면 Google Ads 청구가 정상적으로 이루어지며 계정이 양호한 상태여야 합니다. 전체 이용약관은 여기에서 확인할 수 있습니다. | 2026-01-13T08:49:06 |
https://www.python.org/success-stories/category/software-development/#python-network | Software Development | 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 >>> Software Development Software Development Python on Arm: 2025 Update Zama Concrete ML: Simplifying Homomorphic Encryption for Python Machine Learning Building Robust Codebases with Python's Type Annotations Building a Dependency Graph of Our Python Codebase Bleeding Edge Dependency Testing Using Python How We Created a Python Development Framework for Non-Developers Vacation rental marketplace development using Python Deliver Clean and Safe Code for Your Python Applications A Startup Healthcare Tech Firm Is Now Poised for the Future Using Python to build a range of products across multiple industries Using Python for marketplace development under tight deadlines Using Python to develop a patient health portal Building an online pharmacy marketplace with Python Python provides convenience and flexibility for scalable ML/AI Securing Python Runtimes Building an open-source and cross-platform Azure CLI with Python D-Link Australia Uses Python to Control Firmware Updates Distributed System For Technology Integration EZRO Content Management System Avoiding Documentation Costs with Python A Custom Image Viewing Game for an Autistic Child XIST: An XML Transformation Engine 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/engineering/#content | 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://youtube.com/t/terms | 서비스 약관 KR 서비스 이용약관 유료 서비스 약관 유료 서비스 사용 규칙 저작권 집중관리단체 공지 저작권 고지 커뮤니티 가이드 서비스 약관 다른 언어로 서비스 약관 보기: English 및 한국어 약관의 구성 본 요약은 서비스 약관('약관')을 살펴보는 데 도움을 주기 위해 만들어졌습니다. 이 정보가 유용한 가이드가 되기를 바라며, 약관 전문도 반드시 확인하시기 바랍니다. YouTube에 오신 것을 환영합니다. 이 섹션에서는 YouTube와 사용자의 관계를 설명합니다. 여기에는 서비스에 대한 설명이 포함되며, 계약을 정의하고, 서비스 제공자를 밝힙니다. 서비스 이용 대상 이 섹션에서는 서비스 이용에 대한 특정 요구사항을 설명하고, 사용자 분류를 정의합니다. 서비스의 이용 이 섹션에서는 서비스를 이용할 수 있는 권한과 서비스 이용에 적용되는 조건을 설명합니다. 또한, 서비스가 변경될 수 있음에 대해서도 설명합니다. 귀하의 콘텐츠 및 운영 이 섹션은 서비스에 콘텐츠를 제공하는 사용자에게 적용됩니다. 콘텐츠를 업로드함에 따라 허여하는 권한의 범위를 정의하고, 타인의 권리를 침해하는 콘텐츠를 업로드하지 않겠다는 사용자 동의가 포함됩니다. 계정 정지 및 해지 이 섹션에서는 사용자와 YouTube가 관계를 종료할 수 있는 방법을 설명합니다. 서비스에 포함된 소프트웨어에 대하여 이 섹션에서는 서비스의 소프트웨어에 대한 세부정보를 확인할 수 있습니다. 기타 법적 조항 이 섹션에서는 당사자들의 법적 의무에 대해 설명합니다. YouTube가 책임지지 않는 사항에 대한 설명도 확인할 수 있습니다. 본 계약에 대하여 이 섹션에서는 약관의 변경이나 준거법 등 계약과 관련된 중요한 세부정보를 확인할 수 있습니다. 서비스 약관 날짜: 2022년 1월 5일 서비스 약관 YouTube에 오신 것을 환영합니다. 소개 YouTube 플랫폼과 플랫폼에서 제공되는 제품, 서비스, 기능(이하 통칭하여 ' 서비스 ')을 사용해 주셔서 감사합니다. YouTube 서비스 YouTube 서비스는 사용자가 동영상 및 기타 콘텐츠를 찾아보고, 감상하고, 공유하며, 전 세계 사람들과 소통하고, 정보를 나누며, 아이디어를 주고 받을 수 있는 공간을 제공함은 물론, 규모에 관계없이 모든 독창적인 콘텐츠 크리에이터와 광고주에게 배포 플랫폼의 역할을 합니다. YouTube 고객센터 에서 다양한 제품 정보와 사용 방법을 참고할 수 있습니다. 특히 YouTube Kids , YouTube 파트너 프로그램 , YouTube 유료 멤버십 및 구매 관련 정보가 제공됩니다. TV, 게임 콘솔 또는 Google Home 등의 다른 기기 에서 콘텐츠를 즐기는 방법도 확인할 수 있습니다. 서비스 제공자 서비스를 제공하는 법인은 델라웨어 법률에 따라 운영되며, 1600 Amphitheatre Parkway, Mountain View, CA 94043에 소재한 Google LLC입니다(이하 ' YouTube ' 또는 ' 당사 '). 본 약관에서 YouTube의 ' 계열사 '는 Alphabet Inc. 기업 그룹에 (현재 또는 추후) 소속된 다른 회사를 지칭합니다. 적용 약관 귀하는 서비스 사용 시에 수시로 업데이트될 수 있는 본 약관, YouTube 커뮤니티 가이드 , 정책, 안전 및 저작권 정책 (' 계약 '으로 총칭)을 준수해야 합니다. 본 서비스에 광고 또는 스폰서십을 제공하거나, 콘텐츠에 유료 프로모션을 포함하는 경우 YouTube 광고 정책 도 당사와의 계약에 포함됩니다. 본 약관에 제공된 기타 링크 또는 참조는 정보 참고 목적으로만 제공되며, 계약의 일부가 아닙니다. 본 계약을 주의해서 읽고 숙지하시기 바랍니다. 본 계약에 이해할 수 없거나, 동의하지 않는 내용이 있다면 서비스를 사용하지 마시기 바랍니다. 서비스 이용 대상 연령 요건 서비스를 사용하려면 만 14세 이상이어야 합니다. 하지만 부모나 법정대리인이 사용 설정하면 모든 연령대의 아동이 서비스 또는 YouTube Kids를 사용할 수 있습니다(제공 국가에만 해당). 부모 또는 법정대리인 의 허락 귀하가 거주 국가에서 법률상 미성년자에 해당하는 경우, 귀하는 서비스를 사용할 수 있도록 부모 또는 법정대리인의 허락을 받았음을 진술합니다. 부모 또는 법정대리인과 함께 본 계약을 숙지하시기 바랍니다. 거주 국가에서 법률상 미성년자로 간주되는 사용자의 부모 또는 법정대리인이 사용자의 서비스 사용을 허락한 경우, 부모 또는 법정대리인은 본 계약 조건의 적용을 받게되며, 미성년 사용자의 서비스 이용 활동에 대한 책임을 집니다. 가족의 YouTube 사용을 관리하는 데 도움이 되는 도구와 자료(만 14세 미만의 아동에게 서비스 및 YouTube Kids를 사용 설정하는 방법 포함)가 YouTube 고객센터 와 Google의 Family Link 에서 제공됩니다. 사업자 회사 또는 기관을 위해 서비스를 사용하는 경우, 귀하는 해당 단체를 대신하여 행위할 권한이 귀하에게 있고, 해당 단체가 본 계약에 동의함을 진술합니다. 서비스의 이용 서비스 내 콘텐츠 서비스 내 콘텐츠에는 귀하, YouTube 또는 제3자가 제공하는 동영상, 오디오(예를 들어, 음악 및 기타 음향), 그래픽, 사진, 텍스트(댓글 및 스크립트), 브랜딩(상표 이름, 상표권, 서비스 표시 또는 로고 등), 인터랙티브 기능, 소프트웨어, 측정항목, 기타 자료가 포함됩니다. (이하 통칭하여 ‘ 콘텐츠 ’) 법률에 따라 YouTube가 책임을 지는 경우를 제외하고, 콘텐츠에 대한 책임은 서비스에 콘텐츠를 제공하는 사용자 또는 단체에게 있습니다. YouTube는 콘텐츠를 호스팅하거나 제공할 의무가 없습니다. 커뮤니티 가이드 또는 법률을 위반하는 등 본 약관을 준수하지 않는 콘텐츠를 발견하면 YouTube에 신고 할 수 있습니다. Google 계정 및 YouTube 채널 Google 계정 없이도 콘텐츠 탐색 및 검색 등 일부 서비스를 사용할 수 있습니다. 하지만 Google 계정이 있어야 사용 가능한 기능도 있습니다. Google 계정이 있으면 동영상에 좋아요 표시, 채널 구독, YouTube 채널 만들기 등이 가능합니다. Google 계정 만들기 안내를 따르세요. YouTube 채널을 만들면 동영상 업로드, 댓글 작성, 재생목록 만들기 등의 추가 기능을 이용할 수 있습니다. YouTube 채널을 만드는 방법 에 대한 자세한 내용을 참조하세요. Google 계정을 보호하려면 비밀번호를 공개하지 말아야 합니다. 타사 애플리케이션에서 Google 계정 비밀번호를 재사용하면 안 됩니다. 비밀번호 또는 Google 계정의 무단 사용 사실을 알게 된 경우의 조치 등 Google 계정 보안 유지 에 대해 자세히 알아보세요. 귀하의 정보 당사의 개인정보처리방침 은 서비스를 사용할 때 개인정보가 어떻게 처리되고 보호되는지 설명합니다. YouTube Kids 개인정보처리방침 은 YouTube Kids에만 해당하는 개인정보 보호관행에 대한 추가 정보를 제공합니다. 개인적 용도 또는 가족 활동 과정에서 업로드한 오디오 또는 시청각 콘텐츠인 경우를 제외하고, 귀하가 서비스에 업로드한 오디오 또는 시청각 콘텐츠는 YouTube 정보처리규정 에 따라 처리됩니다. 자세히 알아보기 권한 및 제한사항 귀하는 본 계약 및 관련 법령을 준수하는 한 귀하에게 제공된 서비스에 액세스하여 이를 사용할 수 있습니다. 귀하는 개인적, 비영리적 용도로 콘텐츠를 보고 들을 수 있습니다. 귀하는 내장가능한 YouTube 플레이어를 통해 YouTube 동영상을 표시할 수도 있습니다. 서비스 사용 시 다음 제한사항이 적용됩니다. (a) 서비스의 명시적 승인, 또는 (b) YouTube 및 해당하는 경우 각 권리 소유자의 사전 서면 승인을 받은 경우를 제외하고는, 서비스나 콘텐츠의 어떤 부분에 대해서도 액세스, 복제, 다운로드, 배포, 전송, 방송, 표시, 판매, 라이선스 부여, 변경, 수정 또는 그 밖의 사용을 금지합니다. (a) 콘텐츠의 복사 또는 기타 사용을 방지 또는 제한하거나, (b) 서비스 또는 콘텐츠의 사용을 제한하는 기능 또는 보안 관련 기능을 포함하여 서비스의 어떤 부분에 대해서도 우회, 무력화, 기망적인 관여 또는 그 밖의 방해 행위(또는 이러한 행위들에 대한 시도)를 금지합니다. (a) YouTube의 robots.txt 파일에 따른 공개 검색엔진의 경우, 또는 (b) YouTube의 사전 서면 승인을 받은 경우를 제외하고, 자동화된 수단(로봇, 봇넷 또는 스크래퍼 등)을 사용해 서비스에 액세스하면 안 됩니다. 당사자의 허가를 받거나, 위의 3항에서 허용하지 않는 한, 개인 식별이 가능한 정보(예: 사용자 이름이나 얼굴 모습)를 수집해서는 안 됩니다. 서비스를 사용해 원치 않는 홍보성/상업성 콘텐츠나 그 밖의 원치 않는 대량의 구매 권유 자료를 배포하면 안 됩니다. 동영상 조회수, 좋아요 또는 싫어요 수를 늘리거나, 채널 구독자 수를 늘리기 위해 사람들에게 비용을 지불하거나, 인센티브를 제공하는 등 서비스에 대한 실제 사용자 참여도의 부정확한 측정을 야기 또는 조장하거나, 달리 어떠한 방법으로든 측정항목을 조작하면 안 됩니다. 근거가 없거나, 권한을 남용하거나 또는 사소한 제출 등으로 보고, 신고, 불만 제기, 이의 제기 또는 항소 절차를 남용하면 안 됩니다. 본 서비스에서 또는 본 서비스를 통해 YouTube 컨테스트 정책 및 가이드라인 을 준수하지 않는 컨테스트를 시행하면 안 됩니다. 개인적, 비영리적 용도 외의 목적으로 콘텐츠를 보거나 듣기 위해 서비스를 사용하면 안 됩니다(예를 들어, 공개적으로 서비스의 동영상을 상영하거나, 음악을 스트리밍하면 안 됩니다). (a) YouTube 광 고 정책 에서 허용하는 경우(정책을 준수하는 간접 광고 등)를 제외하고, 서비스나 콘텐츠에 또는 그 주변이나 내부에 배치된 광고, 후원, 홍보물을 판매하거나, (b) 오로지 서비스의 콘텐츠만 포함되거나, 광고, 후원, 홍보물 판매의 주된 이유가 서비스의 콘텐츠인 웹사이트 페이지나 애플리케이션에서 광고, 후원, 홍보물을 판매(예를 들어, 사용자들이 방문하는 주요 목적이 YouTube 동영상인 웹페이지의 광고 판매)하기 위하여 서비스를 사용하면 안 됩니다. 유보 서비스를 사용한다고 해서 본 서비스의 어떠한 요소(예를 들어, 사용자 이름이나 다른 사용자 또는 YouTube가 게시한 다른 콘텐츠 등)에 대해서 소유권이나 권리가 부여되는 것은 아닙니다. 서비스 개발, 개선 업데이트 YouTube는 지속적으로 본 서비스를 변경 및 개선하고 있습니다. 지속적인 발전의 일환으로 기능이나 구성을 추가하거나 삭제하고, 새로운 디지털 콘텐츠 또는 서비스를 제공하거나 기존 서비스의 제공을 중단하는 등 본 서비스 전체 또는 일부를 개선하거나 변경할 수 있습니다. 당사는 성능이나 보안을 개선하거나, 법령을 준수하기 위한 변경을 하거나, YouTube 시스템 상의 불법적인 활동이나 시스템을 악용하는 행위를 방지하기 위해 본 서비스나 그 일부를 변경 또는 중단할 수 있습니다. 이러한 변경사항은 사용자 전체, 일부 또는 특정 개인에게 영향을 미칠 수 있습니다. 본 서비스에 다운로드 가능한 소프트웨어(YouTube 스튜디오 애플리케이션 등)가 필요하거나 포함되는 경우, 소프트웨어에 대한 새로운 버전이나 기능이 제공되면 기기 설정에 따라 소프트웨어가 기기에서 자동으로 업데이트될 수 있습니다. 귀하가 본 서비스를 이용하는 데 부정적인 영향을 미치는 중대한 변경사항이 있을 경우, YouTube는 귀하에게 합당한 사전 통지를 전달합니다. 다만, 합리적으로 통지가 불가능한 경우(예: 사용자가 로그인 없이 본 서비스를 이용하는 경우)이거나 긴급한 상황(예: 악용사례를 방지하거나, 법적 요건에 대응하거나, 보안 및 운용가능성 관련 문제를 해결)에서는 예외로 합니다. 또한 YouTube는 Google 테이크아웃 을 사용해 Google 계정에서 귀하의 콘텐츠를 내보낼 기회를 제공하며, 여기에는 관련 법규 및 정책이 적용됩니다.. 귀하의 콘텐츠 및 운영 콘텐츠 업로드 YouTube 채널을 보유한 경우 귀하는 서비스에 콘텐츠를 업로드할 수 있습니다. 자신의 콘텐츠를 사용해 비즈니스 또는 문화예술 사업을 홍보할 수 있습니다. 콘텐츠를 업로드하기로 했다면, 본 계약 또는 법령을 준수하지 않는 콘텐츠를 서비스에 제출하면 안 됩니다. 예를 들어, 당사자 허가를 받았거나, 법적으로 허용되는 경우가 아니라면 제출한 콘텐츠에 제3자의 지적 재산(예를 들어, 저작권으로 보호되는 자료)이 포함되어서는 안 됩니다. 귀하가 서비스에 제출한 콘텐츠에 대한 법적 책임은 귀하에게 있습니다. 당사는 스팸, 멀웨어, 불법 콘텐츠 등과 같은 침해 및 악용 사례를 감지하기 위해 자동화된 시스템으로 귀하의 콘텐츠를 분석할 수 있습니다. 귀하가 부여하는 권리 귀하의 콘텐츠에 대한 소유권은 귀하에게 있습니다. 하지만 아래에 설명된 바와 같이 귀하는 YouTube 및 서비스의 다른 사용자에게 일정한 권리를 부여해야 합니다. YouTube에 부여하는 라이선스 귀하는 본 서비스에 콘텐츠를 제공함으로써 콘텐츠를 사용(복제, 배포, 수정, 표시, 공연 등)할 수 있는 세계적이고, 비독점적이며, 무상으로 제공되고, 양도가능하며, 서브라이선스를 허여할 수 있는 라이선스를 YouTube에 부여합니다. YouTube는 본 서비스를 운영하고, 홍보 및 개선하기 위한 목적으로만 이러한 라이선스를 사용할 수 있습니다. 본 약관의 어떠한 조항도 법령에서 허용되는 범위를 넘어서는 라이선스를 YouTube에 부여하는 것은 아닙니다. 다른 사용자에게 부여하는 라이선스 또한 귀하는 서비스의 다른 사용자들에게 서비스를 통해 귀하의 콘텐츠에 액세스할 수 있는 세계적이고, 비독점적이며, 무상으로 제공되는 라이선스를 부여하며, 본 서비스에서 제공하는 기능(예를 들어, 비디오 플레이백이나 퍼가기)을 통해 설정된 바에 따라 해당 콘텐츠를 사용할 권리, 즉, 복제, 배포, 수정, 표시, 공연 등을 할 수 있는 권리를 부여합니다. 보다 명확히 설명하자면, 이 라이선스는 다른 사용자가 본 서비스와는 별개로 귀하의 콘텐츠를 활용할 수 있는 어떠한 권리나 권한도 부여하지 않습니다. 라이선스 기간 귀하가 부여한 라이선스는 해당 콘텐츠가 아래에서 설명하는 바에 따라 삭제될 때까지 유지됩니다. 콘텐츠가 삭제되면 라이선스가 종료되지만, 서비스 운영, 삭제 전에 허용한 콘텐츠의 사용, 또는 법령에서 달리 요구하는 경우에는 예외가 인정될 수 있습니다. 예를 들어, 귀하가 콘텐츠를 삭제하더라도 YouTube는 (a) 귀하의 콘텐츠가 포함된 홍보자료를 회수하거나, (b) 서비스의 제한적인 오프라인 시청 기능(예를 들어, 유료가입 서비스에서 이용할 수 있는 기능)에 따라 다른 이용자가 이용하는 콘텐츠를 회수해야 하는 의무가 있는 것은 아니며, (c) YouTube가 법적 필요에 의해 보관할 합리적인 이유가 있는 사본을 삭제해야 하는 것은 아닙니다. 수익 창출 권리 귀하는 서비스에 있는 귀하의 콘텐츠에서 수익을 창출할 권리를 YouTube에 부여합니다. 수익 창출에는 콘텐츠에 광고를 게재하거나 사용자에게 이용료를 청구하는 것도 포함될 수 있습니다. 이 계약으로 귀하에게 수익금을 지급받을 자격이 주어지지는 않습니다. 2021년 6월 1일부터 YouTube와 맺은 기타 계약을 통해 YouTube로부터 지급받을 자격이 있는 수익금(YouTube 파트너 프로그램, 채널 멤버십 또는 Super Chat 수익금 포함)은 모두 로열티로 취급됩니다. 법에서 요구되는 경우 Google이 지급액에서 세금을 원천징수합니다. 귀하의 콘텐츠 삭제 귀하는 언제든지 서비스에서 자신의 콘텐츠를 삭제 할 수 있습니다. 콘텐츠를 삭제하기 전에 콘텐츠 사본 을 만들 수도 있습니다. 만약 귀하가 본 약관에서 요구하는 권한을 더 이상 보유하지 않는 경우 콘텐츠를 삭제해야 합니다. YouTube에 의한 콘텐츠 삭제 귀하의 콘텐츠가 (1) 본 계약을 위반하거나, (2) YouTube, 사용자 또는 제3자에게 위해를 야기한다고 합리적으로 판단되는 경우, 당사는 그러한 콘텐츠를 삭제하거나 차단할 권리를 보유합니다.. YouTube는 통지가 (a) 법적 이유로 금지되거나, (b) 사용자, 기타 제3자, YouTube 또는 그 계열사에게 위해를 야기할 수 있다고 합리적으로 판단되는 경우(예를 들어, 통지하는 것이 법령 또는 규제당국의 명령을 위반하는 경우, 조사를 방해하는 경우, 본 서비스의 보안을 해하는 경우 등)를 제외하고, 귀하에게 해당 조치의 이유를 지체 없이 통지합니다. 항소 방법을 포함한 신고 및 집행에 대한 자세한 내용은 고객센터의 문제해결 페이지에서 확인할 수 있습니다. 커뮤니티 가이드 위반 경고 YouTube는 YouTube 커뮤니티 가이드 를 위반하는 콘텐츠를 대상으로 한 '경고' 시스템을 운영하고 있습니다. 최초 위반인 경우 YouTube는 일반적으로 주의만 주고, 그 이후의 위반의 경우 귀하의 채널에 대해 경고가 적용됩니다. 경고마다 다양한 제한사항이 수반되며 채널이 YouTube에서 영구적으로 삭제될 수도 있습니다. 경고가 채널에 미치는 영향에 대한 자세한 설명은 커뮤니티 가이드 위반 경고 기본사항 페이지 에서 확인할 수 있습니다. 경고가 잘못 주어졌다고 생각되는 경우 여기 에서 항소할 수 있습니다. 경고로 인해 채널에 제한이 적용된 경우 다른 채널을 사용해 제한을 회피하면 안 됩니다. 이 금지 조항을 위반하는 것은 본 계약을 중대하게 위반하는 행위로서 Google은 Google 계정을 해지하거나 본 서비스 전체 또는 일부의 액세스 권한을 해지할 권리를 보유합니다. 저작권 보호 YouTube는 저작권자가 온라인상에서 자신의 지적 재산을 관리하는 데 도움이 되는 정보를 YouTube 저작권 센터 에서 제공하고 있습니다. 본 서비스에서 귀하의 저작권이 침해되었다고 생각하는 경우 YouTube에 신고 해 주시기 바랍니다. YouTube는 YouTube 저작권 센터 의 절차에 따라 저작권 침해 신고에 대응합니다. YouTube 저작권 센터에서는 저작권 위반 경고 해결 방법에 대한 정보도 제공하고 있습니다. 반복적으로 저작권을 침해하는 사용자는 YouTube 정책에 따라 일정한 경우 서비스 액세스가 해지될 수 있습니다. 계정 정지 및 해지 귀하에 의한 해지 귀하는 언제든지 서비스 사용을 중지할 수 있습니다. 안내 에 따라 자신의 Google 계정에서 본 서비스를 삭제하면 됩니다. 삭제 시 귀하의 YouTube 채널이 폐쇄되고, 데이터가 삭제됩니다. 사용을 중지하기 전에 귀하의 데이터 사본을 다운로드할 수도 있습니다. YouTube에 의한 해지 및 정지 YouTube는 (a) 귀하가 본 계약을 중대하게 또는 반복적으로 위반하거나, (b) 법적 요건이나 법원 명령 등의 준수를 위한 경우, 또는 (c) 사용자, 기타 제3자, YouTube 또는 그 계열사에 책임이나 위해를 야기하는 행위가 있다고 합리적으로 판단되는 경우, 귀하의 Google 계정을 정지 또는 해지하거나 본 서비스 전체 또는 일부에 대한 귀하의 액세스를 해지할 권리를 보유합니다. 해지 또는 정지 에 대한 통지 YouTube는 통지가 (a) 법적 이유로 금지되거나, (b) 사용자, 다른 제3자, YouTube 또는 그 계열사에게 위해를 야기할 수 있다고 합리적으로 판단되는 경우(예를 들어, 통지하는 것이 법령 또는 규제당국의 명령을 위반하는 경우, 조사를 방해하는 경우, 본 서비스의 보안을 해하는 경우 등)를 제외하고, 귀하에게 YouTube에 의한 해지 또는 정지의 이유를 지체 없이 통지합니다. 서비스 변경으로 인해 YouTube가 귀하의 액세스를 해지하는 경우, 합리적으로 가능하다면 서비스에서 귀하의 콘텐츠를 가져올 충분한 시간을 귀하에게 제공합니다. 계정 정지 또는 해지의 효과 귀하의 Google 계정이 해지되거나 본 서비스에 대한 액세스가 제한되어도 서비스의 일부(예를 들어, 단순한 시청)는 계정 없이 계속 사용할 수 있으며, 본 계약은 그러한 사용에 대해서 계속 적용됩니다. Google 계정이 잘못 해지 또는 정지되었다고판단되는 경우 이 양식을 사용하여 항소 할 수 있습니다. 서비스에 포함된 소프트웨어에 대하여 다운로드 가능한 소프트웨어 서비스에 다운로드 가능한 소프트웨어(YouTube 스튜디오 애플리케이션 등)가 필요하거나 포함되는 경우, 라이선스를 제공하는 추가 약관의 적용을 받는 소프트웨어가 아니라면, YouTube는 귀하에게 서비스의 일부로 제공한 소프트웨어를 사용할 수 있는 개인적이고, 세계적이며, 무상으로 제공되고, 양도 불가능하며, 비독점적인 라이선스를 제공합니다. 이 라이선스는 귀하가 본 계약에서 허용하는 방법에 따라 YouTube가 제공하는 바대로 본 서비스를 사용하고 혜택을 누릴 수 있도록 하기 위한 목적으로만 제공됩니다. 귀하는 이 소프트웨어의 어느 부분도 복사, 수정, 배포, 판매 또는 대여할 수 없으며, 소프트웨어를 역설계하거나, 소스 코드의 추출을 시도할 수 없습니다. 다만, 법률상 이와 같은 제한이 금지되거나, YouTube의 서면 승인을 받은 경우는 제외합니다. 오픈소스 본 서비스에서 사용되는 일부 소프트웨어는 당사가 귀하에게 부여하는 오픈소스 라이선스 하에서 제공될 수 있습니다. 오픈소스 라이선스에는 명시적으로 본 약관의 일부 규정에 우선하는 규정이 있을 수 있으므로, 그러한 라이선스 내용을 숙지하시기 바랍니다. 기타 법적 조항 보증 의 부인 본 계약에 명시되거나, 법률에서 요구되지 않는 한, 본 서비스는 '있는 그대로' 제공되며 YouTube는 서비스와 관련한 어떤 구체적인 약정이나 보증도 하지 않습니다. 예를 들어, 법률상 허용되는 한도 내에서, 당사는 (a) 서비스를 통해 제공되는 콘텐츠, (b) 서비스의 특정 기능이나 서비스의 정확성, 안정성, 가용성 또는 귀하의 필요를 충족할 능력, 또는 (c) 귀하가 제출하는 어떤 콘텐츠든 서비스에서 액세스할 수 있음을 보증하지 않습니다. 모바일로 YouTube 광고를 시청하는 경우 데이터 요금이 발생할 수 있습니다. 책임의 제한 법률에서 요구되는 경우를 제외하고, YouTube, 그 계열사, 임원, 이사, 직원 및 대리인은 다음 사항을 원인으로 발생한 이익·수입·사업 기회·영업권·예상된 절감 효과의 상실, 데이터의 손실 또는 손상, 간접적 또는 결과적 손실, 징벌적 손해에 대해 책임을 지지 않습니다. 서비스의 오류, 실수 또는 부정확한 내용 귀하의 서비스 사용으로 인한 개인의 상해나 재산 피해 서비스의 무단 액세스 또는 사용 서비스의 중단 또는 중지 제3자에 의해 서비스에 또는 서비스를 통해 전송된 바이러스 또는 악성 코드 귀하의 콘텐츠 사용을 포함해 사용자 또는 YouTube가 제출한 콘텐츠, 및/또는 콘텐츠의 삭제 또는 이용 불가 본 조항은 청구의 근거가 보증, 계약, 불법 행위 또는 기타 법리 등 무엇이든 상관없이 모든 청구에 적용됩니다. 관련 법률이 허용하는 한도 내에서, 본 서비스와 관련된 또는 그로 인한 청구에 대한 YouTube 및 그 계열사의 총 배상 책임은 (a) 귀하가 청구에 관하여 YouTube에 서면 통지하기 전 12개월 동안 YouTube가 귀하의 서비스 사용과 관련해 귀하에게 지급한 수익 금액과, (b) 미달러 $500 중 높은 금액으로 제한됩니다. 면책 관련 법률이 허용하는 한도 내에서, 귀하는 (a) 귀하의 서비스 사용 및 액세스, (b) 귀하의 본 약관 조항 위반, (c) 귀하의 제3자의 저작권, 재산권 또는 프라이버시권 등 권리침해, 또는 (d) 귀하의 콘텐츠로 손해를 입었다는 제3자의 주장으로 발생하는 모든 청구, 손해, 의무, 손실, 책임, 비용 또는 채무, 지출(변호사 비용 등)로부터 YouTube, 그 계열사, 임원, 이사, 직원 및 대리인을 보호하고, 이들의 책임을 면제하며, 이로 인하여 손해를 입지 않도록 하는 데 동의합니다. 이러한 방어 및 면책 의무는 본 계약과 귀하의 본 서비스 사용이 종료된 후에도 유효하게 존속합니다. 제3자 링크 서비스에는 YouTube가 소유하거나 관리하지 않는 제3자 웹사이트 및 온라인 서비스의 링크가 포함될 수 있습니다. YouTube는 해당 웹사이트 및 온라인 서비스에 관여할 수 없으며, 관련 법률이 허용하는 한도 내에서, 이에 대한 책임을 지지 않습니다. 본 서비스에서 떠나는 경우 귀하가 방문하는 각 제3자 웹사이트 및 온라인 서비스의 약관과 개인정보처리방침을 검토하시기 바랍니다. 본 계약에 대하여 본 계약 ' 의 변경 당사는 (1) 서비스 수정 사항을 반영하거나, 사업 방식의 변화를 반영하거나(예: 새 제품 또는 기능을 추가하거나 기존의 것들을 삭제하는 경우) (2) 법령, 규제 또는 보안상 등의 이유가 있거나 (3) 악용 또는 위해를 방지하기 위해 본 계약을 변경할 수 있습니다. 본 계약에 중대한 변경사항이 있을 경우, YouTube는 최소 30일 전에 사전 통지와 변경사항 검토 기회를 제공하지만, (1) 사용자에게 유리한 신규 제품 또는 기능을 출시하는 경우 또는 (2) 발생 중인 악용사례를 방지하거나 법적 요건에 대응해야 하는 등 긴급한 상황인 경우는 예외입니다. 새로운 약관에 동의하지 않으면 업로드한 콘텐츠를 삭제하고 본 서비스 이용을 중지해야 합니다. 본 계약의 지속 귀하의 서비스 사용이 종료되어도 본 계약의 '기타 법적 조항', '본 계약에 대하여' 부분은 계속 귀하에게 적용되며, 귀하가 부여한 라이선스는 '라이선스 기간'에서 설명된 바에 따라 지속됩니다. 분리 어떤 이유로든 본 계약의 특정 조항이 집행 불가능한 것으로 판명되는 경우, 이는 다른 조항에 영향을 미치지 않습니다.. 권리 포기 귀하가 본 계약을 준수하지 않았을 때 당사가 즉시 조치를 취하지 않더라도, 이는 당사가 보유하는 권리(향후 조치를 취할 권리 등)를 포기하는 것을 의미하지 않습니다. 해석 본 약관에 사용된 ' 포함 ' 또는 ‘ 등 '이란 표현은 '포함하되 한정되지 않음'이란 의미이며, 당사가 제시한 예시는 설명을 위한 목적으로 사용된 것입니다. 준거법 일부 국가의 법원에서는 분정 유형에 따라 미국 캘리포니아주 법률을 적용하지 않을 수 있습니다. 귀하가 이러한 국가에 거주하고, 미국 캘리포니아주 법률의 적용이 배제되는 경우, 거주 국가의 법률이 본 약관과 관련된 분쟁에 적용됩니다. 그렇지 않은 경우, 귀하는 본 약관 또는 서비스와 관련되거나, 이로부터 야기된 일체의 분쟁에 대해 미국 캘리포니아주 법률이 적용되며, 캘리포니아주 국제사법의 적용은 배제된다는 것에 동의합니다. 마찬가지로, 거주 국가의 법원이 귀하가 미국 캘리포니아주 산타클라라 카운티 법원의 관할에 합의하는 것을 허용하지 않는 경우, 본 약관과 관련된 분쟁에 관하여 귀하의 거주지 재판관할이나 법정지가 적용됩니다. 그렇지 않은 경우, 본 약관 또는 서비스와 관련되거나, 이로부터 야기된 모든 청구는 미국 캘리포니아주 산타클라라 카운티의 연방 또는 주 법원이 전속관할을 가지며, 귀하와 YouTube는 해당 법원이 인적 관할을 갖는 것에 동의합니다. 발효일: 2022년 1월 5일( 이전 버전 보기 ) | 2026-01-13T08:49:06 |
https://vitejs.dev/guide/ | 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://policies.google.com/technologies/partner-sites | How Google uses information from sites or apps that use our services – Privacy & Terms – Google Privacy & Terms Privacy & Terms Skip to main content Sign in Overview Privacy Policy Terms of Service Technologies FAQ Privacy & Terms Overview Privacy Policy Terms of Service Technologies Advertising How Google uses information from sites or apps that use our services How Google uses cookies How Google uses location information How Google uses credit card numbers for payments How Google Voice works Google Product Privacy Guide How Google retains data we collect FAQ Privacy & Terms Privacy & Terms Privacy & Terms Overview Privacy Policy Terms of Service Technologies FAQ Google Account Technologies Advertising How Google uses information from sites or apps that use our services How Google uses cookies How Google uses location information How Google uses credit card numbers for payments How Google Voice works Google Product Privacy Guide How Google retains data we collect Google advertising services are experimenting with new ways of supporting the delivery and measurement of digital advertising in ways that better protect people’s privacy online via the Privacy Sandbox initiative on Chrome and Android. Users with the relevant Privacy Sandbox settings enabled in Chrome or Android may see relevant ads from Google’s advertising services based on Topics or Protected Audience data stored on their browser or mobile device. Google’s advertising services may also measure ad performance using Attribution Reporting data stored on their browser or mobile device. More information on the Privacy Sandbox . How Google uses information from sites or apps that use our services Many websites and apps use Google services to improve their content and keep it free. When they integrate our services, these sites and apps share information with Google. For example, when you visit a website that uses advertising services like AdSense, including analytics tools like Google Analytics, or embeds video content from YouTube, your web browser automatically sends certain information to Google. This includes the URL of the page you’re visiting and your IP address. We may use the IP address, for example, to identify your general location, to measure the effectiveness of ads, and, depending on your settings, to improve the relevance of the ads you see. We may also set cookies on your browser or read cookies that are already there. Apps that use Google advertising services also share information with Google, such as the name of the app and a unique identifier for advertising. Google uses the information shared by sites and apps to deliver our services, maintain and improve them, develop new services, measure the effectiveness of advertising, protect against fraud and abuse, and personalize content and ads you see on Google and on our partners’ sites and apps. See our Privacy Policy to learn more about how we process data for each of these purposes and our Advertising page for more about Google ads, how your information is used in the context of advertising, and how long Google stores this information. Our Privacy Policy explains the legal grounds Google relies upon to process your information — for example, we may process your information with your consent or to pursue legitimate interests such as providing, maintaining and improving our services to meet the needs of our users. Sometimes, when processing information shared with us by sites and apps, those sites and apps will ask for your consent before allowing Google to process your information. For example, a banner may appear on a site asking for consent for Google to process the information that site collects. When that happens, we will respect the purposes described in the consent you give to the site or app, rather than the legal grounds described in the Google Privacy Policy. If you want to change or withdraw your consent, you should visit the site or app in question to do so. Ad personalization If ad personalization is turned on, Google will use your information to make your ads more useful for you. For example, a website that sells mountain bikes might use Google's ad services. After you visit that site, you could see an ad for mountain bikes on a different site that shows ads served by Google. If ad personalization is off, Google will not collect or use your information to create an ad profile or personalize the ads Google shows to you. You will still see ads, but they may not be as useful. Ads may still be based on the topic of the website or app you're looking at, your current search terms, or on your general location, but not on your interests, search history, or browsing history. Your information can still be used for the other purposes mentioned above, such as to measure the effectiveness of advertising and protect against fraud and abuse. When you interact with a website or app that uses Google services, you may be asked to choose whether you want to see personalized ads from ad providers, including Google. Regardless of your choice, Google will not personalize the ads you see if your ad personalization setting is off or your account is ineligible for personalized ads. You can see and control what information we use to show you ads by visiting your ad settings . How you can control the information collected by Google on these sites and apps Here are some of the ways you can control the information that is shared by your device when you visit or interact with sites and apps that use Google services: Ad Settings helps you control ads you see on Google services (such as Google Search or YouTube), or on non-Google websites and apps that use Google ad services. You can also learn how ads are personalized, opt out of ad personalization, and block specific advertisers. If you are signed in to your Google Account, and depending on your Account settings, My Activity allows you to review and control data that’s created when you use Google services, including the information we collect from the sites and apps you have visited. You can browse by date and by topic, and delete part or all of your activity. Many websites and apps use Google Analytics to understand how visitors engage with their sites or apps. If you don’t want Analytics to be used in your browser, you can install the Google Analytics browser add-on . Learn more about Google Analytics and privacy . Incognito mode in Chrome allows you to browse the web without recording webpages and files in your browser or Account history (unless you choose to sign in). Cookies are deleted after you've closed all of your incognito windows and tabs, and your bookmarks and settings are stored until you delete them. Learn more about cookies . Using Incognito mode in Chrome or other private browsing modes does not prevent the collection of data when you visit websites that use Google services, and Google may still collect data when you visit websites using these browsers. Many browsers, including Chrome, allow you to block third-party cookies. You can also clear any existing cookies from within your browser. Learn more about managing cookies in Chrome . Opens in a new tab (opens a footnote) Google About Google Privacy Policy Terms Transparency Center English Afrikaans Bahasa Indonesia Bahasa Melayu Català Čeština Dansk Deutsch Eesti English English (India) English (United Kingdom) Español Español (Latinoamérica) Euskara Filipino Français Français (Canada) Gaeilge Galego Hrvatski Isizulu Íslenska Italiano Kiswahili Latviešu Lietuvių Magyar Malti Nederlands Norsk Polski Português (Brasil) Português (Portugal) Română Slovenčina Slovenščina Srpski Suomi Svenska Tiếng Việt Türkçe অসমীয়া Ελληνικά Български ଓଡିଆ Русский Српски Українська עברית اردو العربية فارسی አማርኛ मराठी हिन्दी বাংলা ગુજરાતી தமிழ் తెలుగు ಕನ್ನಡ മലയാളം ไทย 한국어 中文 (香港) 中文（简体中文） 中文（繁體中文） 日本語 Google apps Main menu | 2026-01-13T08:49:06 |
https://peps.python.org/pep-0249/ | PEP 249 – Python Database API Specification v2.0 | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 249 Toggle light / dark / auto colour theme PEP 249 – Python Database API Specification v2.0 Author : Marc-André Lemburg <mal at lemburg.com> Discussions-To : Db-SIG list Status : Final Type : Informational Created : 12-Apr-1999 Post-History : Replaces : 248 Table of Contents Introduction Module Interface Constructors Globals Exceptions Connection Objects Connection methods Cursor Objects Cursor attributes Cursor methods Type Objects and Constructors Implementation Hints for Module Authors Optional DB API Extensions Optional Error Handling Extensions Optional Two-Phase Commit Extensions TPC Transaction IDs TPC Connection Methods Frequently Asked Questions Major Changes from Version 1.0 to Version 2.0 Open Issues Footnotes Acknowledgements Copyright Introduction This API has been defined to encourage similarity between the Python modules that are used to access databases. By doing this, we hope to achieve a consistency leading to more easily understood modules, code that is generally more portable across databases, and a broader reach of database connectivity from Python. Comments and questions about this specification may be directed to the SIG for Database Interfacing with Python . For more information on database interfacing with Python and available packages see the Database Topic Guide . This document describes the Python Database API Specification 2.0 and a set of common optional extensions. The previous version 1.0 version is still available as reference, in PEP 248 . Package writers are encouraged to use this version of the specification as basis for new interfaces. Module Interface Constructors Access to the database is made available through connection objects. The module must provide the following constructor for these: connect ( parameters… ) Constructor for creating a connection to the database. Returns a Connection Object. It takes a number of parameters which are database dependent. [1] Globals These module globals must be defined: apilevel String constant stating the supported DB API level. Currently only the strings “ 1.0 ” and “ 2.0 ” are allowed. If not given, a DB-API 1.0 level interface should be assumed. threadsafety Integer constant stating the level of thread safety the interface supports. Possible values are: threadsafety Meaning 0 Threads may not share the module. 1 Threads may share the module, but not connections. 2 Threads may share the module and connections. 3 Threads may share the module, connections and cursors. Sharing in the above context means that two threads may use a resource without wrapping it using a mutex semaphore to implement resource locking. Note that you cannot always make external resources thread safe by managing access using a mutex: the resource may rely on global variables or other external sources that are beyond your control. paramstyle String constant stating the type of parameter marker formatting expected by the interface. Possible values are [2] : paramstyle Meaning qmark Question mark style, e.g. ...WHERE name=? numeric Numeric, positional style, e.g. ...WHERE name=:1 named Named style, e.g. ...WHERE name=:name format ANSI C printf format codes, e.g. ...WHERE name=%s pyformat Python extended format codes, e.g. ...WHERE name=%(name)s Exceptions The module should make all error information available through these exceptions or subclasses thereof: Warning Exception raised for important warnings like data truncations while inserting, etc. It must be a subclass of the Python Exception class [10] [11] . Error Exception that is the base class of all other error exceptions. You can use this to catch all errors with one single except statement. Warnings are not considered errors and thus should not use this class as base. It must be a subclass of the Python Exception class [10] . InterfaceError Exception raised for errors that are related to the database interface rather than the database itself. It must be a subclass of Error . DatabaseError Exception raised for errors that are related to the database. It must be a subclass of Error . DataError Exception raised for errors that are due to problems with the processed data like division by zero, numeric value out of range, etc. It must be a subclass of DatabaseError . OperationalError Exception raised for errors that are related to the database’s operation and not necessarily under the control of the programmer, e.g. an unexpected disconnect occurs, the data source name is not found, a transaction could not be processed, a memory allocation error occurred during processing, etc. It must be a subclass of DatabaseError . IntegrityError Exception raised when the relational integrity of the database is affected, e.g. a foreign key check fails. It must be a subclass of DatabaseError . InternalError Exception raised when the database encounters an internal error, e.g. the cursor is not valid anymore, the transaction is out of sync, etc. It must be a subclass of DatabaseError . ProgrammingError Exception raised for programming errors, e.g. table not found or already exists, syntax error in the SQL statement, wrong number of parameters specified, etc. It must be a subclass of DatabaseError . NotSupportedError Exception raised in case a method or database API was used which is not supported by the database, e.g. requesting a .rollback() on a connection that does not support transaction or has transactions turned off. It must be a subclass of DatabaseError . This is the exception inheritance layout [10] [11] : Exception |__Warning |__Error |__InterfaceError |__DatabaseError |__DataError |__OperationalError |__IntegrityError |__InternalError |__ProgrammingError |__NotSupportedError Note The values of these exceptions are not defined. They should give the user a fairly good idea of what went wrong, though. Connection Objects Connection objects should respond to the following methods. Connection methods .close() Close the connection now (rather than whenever .__del__() is called). The connection will be unusable from this point forward; an Error (or subclass) exception will be raised if any operation is attempted with the connection. The same applies to all cursor objects trying to use the connection. Note that closing a connection without committing the changes first will cause an implicit rollback to be performed. .commit () Commit any pending transaction to the database. Note that if the database supports an auto-commit feature, this must be initially off. An interface method may be provided to turn it back on. Database modules that do not support transactions should implement this method with void functionality. .rollback () This method is optional since not all databases provide transaction support. [3] In case a database does provide transactions this method causes the database to roll back to the start of any pending transaction. Closing a connection without committing the changes first will cause an implicit rollback to be performed. .cursor () Return a new Cursor Object using the connection. If the database does not provide a direct cursor concept, the module will have to emulate cursors using other means to the extent needed by this specification. [4] Cursor Objects These objects represent a database cursor, which is used to manage the context of a fetch operation. Cursors created from the same connection are not isolated, i.e. , any changes done to the database by a cursor are immediately visible by the other cursors. Cursors created from different connections can or can not be isolated, depending on how the transaction support is implemented (see also the connection’s .rollback () and .commit () methods). Cursor Objects should respond to the following methods and attributes. Cursor attributes .description This read-only attribute is a sequence of 7-item sequences. Each of these sequences contains information describing one result column: name type_code display_size internal_size precision scale null_ok The first two items ( name and type_code ) are mandatory, the other five are optional and are set to None if no meaningful values can be provided. This attribute will be None for operations that do not return rows or if the cursor has not had an operation invoked via the .execute*() method yet. The type_code can be interpreted by comparing it to the Type Objects specified in the section below. .rowcount This read-only attribute specifies the number of rows that the last .execute*() produced (for DQL statements like SELECT ) or affected (for DML statements like UPDATE or INSERT ). [9] The attribute is -1 in case no .execute*() has been performed on the cursor or the rowcount of the last operation is cannot be determined by the interface. [7] Note Future versions of the DB API specification could redefine the latter case to have the object return None instead of -1. Cursor methods .callproc ( procname [, parameters ] ) (This method is optional since not all databases provide stored procedures. [3] ) Call a stored database procedure with the given name. The sequence of parameters must contain one entry for each argument that the procedure expects. The result of the call is returned as modified copy of the input sequence. Input parameters are left untouched, output and input/output parameters replaced with possibly new values. The procedure may also provide a result set as output. This must then be made available through the standard .fetch*() methods. .close () Close the cursor now (rather than whenever __del__ is called). The cursor will be unusable from this point forward; an Error (or subclass) exception will be raised if any operation is attempted with the cursor. .execute ( operation [, parameters ]) Prepare and execute a database operation (query or command). Parameters may be provided as sequence or mapping and will be bound to variables in the operation. Variables are specified in a database-specific notation (see the module’s paramstyle attribute for details). [5] A reference to the operation will be retained by the cursor. If the same operation object is passed in again, then the cursor can optimize its behavior. This is most effective for algorithms where the same operation is used, but different parameters are bound to it (many times). For maximum efficiency when reusing an operation, it is best to use the .setinputsizes() method to specify the parameter types and sizes ahead of time. It is legal for a parameter to not match the predefined information; the implementation should compensate, possibly with a loss of efficiency. The parameters may also be specified as list of tuples to e.g. insert multiple rows in a single operation, but this kind of usage is deprecated: .executemany() should be used instead. Return values are not defined. .executemany ( operation , seq_of_parameters ) Prepare a database operation (query or command) and then execute it against all parameter sequences or mappings found in the sequence seq_of_parameters . Modules are free to implement this method using multiple calls to the .execute() method or by using array operations to have the database process the sequence as a whole in one call. Use of this method for an operation which produces one or more result sets constitutes undefined behavior, and the implementation is permitted (but not required) to raise an exception when it detects that a result set has been created by an invocation of the operation. The same comments as for .execute() also apply accordingly to this method. Return values are not defined. .fetchone () Fetch the next row of a query result set, returning a single sequence, or None when no more data is available. [6] An Error (or subclass) exception is raised if the previous call to .execute*() did not produce any result set or no call was issued yet. .fetchmany ([ size=cursor.arraysize ]) Fetch the next set of rows of a query result, returning a sequence of sequences (e.g. a list of tuples). An empty sequence is returned when no more rows are available. The number of rows to fetch per call is specified by the parameter. If it is not given, the cursor’s arraysize determines the number of rows to be fetched. The method should try to fetch as many rows as indicated by the size parameter. If this is not possible due to the specified number of rows not being available, fewer rows may be returned. An Error (or subclass) exception is raised if the previous call to .execute*() did not produce any result set or no call was issued yet. Note there are performance considerations involved with the size parameter. For optimal performance, it is usually best to use the .arraysize attribute. If the size parameter is used, then it is best for it to retain the same value from one .fetchmany() call to the next. .fetchall () Fetch all (remaining) rows of a query result, returning them as a sequence of sequences (e.g. a list of tuples). Note that the cursor’s arraysize attribute can affect the performance of this operation. An Error (or subclass) exception is raised if the previous call to .execute*() did not produce any result set or no call was issued yet. .nextset () (This method is optional since not all databases support multiple result sets. [3] ) This method will make the cursor skip to the next available set, discarding any remaining rows from the current set. If there are no more sets, the method returns None . Otherwise, it returns a true value and subsequent calls to the .fetch*() methods will return rows from the next result set. An Error (or subclass) exception is raised if the previous call to .execute*() did not produce any result set or no call was issued yet. .arraysize This read/write attribute specifies the number of rows to fetch at a time with .fetchmany() . It defaults to 1 meaning to fetch a single row at a time. Implementations must observe this value with respect to the .fetchmany() method, but are free to interact with the database a single row at a time. It may also be used in the implementation of .executemany() . .setinputsizes ( sizes ) This can be used before a call to .execute*() to predefine memory areas for the operation’s parameters. sizes is specified as a sequence — one item for each input parameter. The item should be a Type Object that corresponds to the input that will be used, or it should be an integer specifying the maximum length of a string parameter. If the item is None , then no predefined memory area will be reserved for that column (this is useful to avoid predefined areas for large inputs). This method would be used before the .execute*() method is invoked. Implementations are free to have this method do nothing and users are free to not use it. .setoutputsize ( size [, column ]) Set a column buffer size for fetches of large columns (e.g. LONG s, BLOB s, etc.). The column is specified as an index into the result sequence. Not specifying the column will set the default size for all large columns in the cursor. This method would be used before the .execute*() method is invoked. Implementations are free to have this method do nothing and users are free to not use it. Type Objects and Constructors Many databases need to have the input in a particular format for binding to an operation’s input parameters. For example, if an input is destined for a DATE column, then it must be bound to the database in a particular string format. Similar problems exist for “Row ID” columns or large binary items (e.g. blobs or RAW columns). This presents problems for Python since the parameters to the .execute*() method are untyped. When the database module sees a Python string object, it doesn’t know if it should be bound as a simple CHAR column, as a raw BINARY item, or as a DATE . To overcome this problem, a module must provide the constructors defined below to create objects that can hold special values. When passed to the cursor methods, the module can then detect the proper type of the input parameter and bind it accordingly. A Cursor Object’s description attribute returns information about each of the result columns of a query. The type_code must compare equal to one of Type Objects defined below. Type Objects may be equal to more than one type code (e.g. DATETIME could be equal to the type codes for date, time and timestamp columns; see the Implementation Hints below for details). The module exports the following constructors and singletons: Date ( year , month , day ) This function constructs an object holding a date value. Time ( hour , minute , second ) This function constructs an object holding a time value. Timestamp ( year , month , day , hour , minute , second ) This function constructs an object holding a time stamp value. DateFromTicks ( ticks ) This function constructs an object holding a date value from the given ticks value (number of seconds since the epoch; see the documentation of the standard Python time module for details). TimeFromTicks ( ticks ) This function constructs an object holding a time value from the given ticks value (number of seconds since the epoch; see the documentation of the standard Python time module for details). TimestampFromTicks ( ticks ) This function constructs an object holding a time stamp value from the given ticks value (number of seconds since the epoch; see the documentation of the standard Python time module for details). Binary ( string ) This function constructs an object capable of holding a binary (long) string value. STRING type This type object is used to describe columns in a database that are string-based (e.g. CHAR ). BINARY type This type object is used to describe (long) binary columns in a database (e.g. LONG , RAW , BLOB s). NUMBER type This type object is used to describe numeric columns in a database. DATETIME type This type object is used to describe date/time columns in a database. ROWID type This type object is used to describe the “Row ID” column in a database. SQL NULL values are represented by the Python None singleton on input and output. Note Usage of Unix ticks for database interfacing can cause troubles because of the limited date range they cover. Implementation Hints for Module Authors Date/time objects can be implemented as Python datetime module objects (available since Python 2.3, with a C API since 2.4) or using the mxDateTime package (available for all Python versions since 1.5.2). They both provide all necessary constructors and methods at Python and C level. Here is a sample implementation of the Unix ticks based constructors for date/time delegating work to the generic constructors: import time def DateFromTicks ( ticks ): return Date ( * time . localtime ( ticks )[: 3 ]) def TimeFromTicks ( ticks ): return Time ( * time . localtime ( ticks )[ 3 : 6 ]) def TimestampFromTicks ( ticks ): return Timestamp ( * time . localtime ( ticks )[: 6 ]) The preferred object type for Binary objects are the buffer types available in standard Python starting with version 1.5.2. Please see the Python documentation for details. For information about the C interface have a look at Include/bufferobject.h and Objects/bufferobject.c in the Python source distribution. This Python class allows implementing the above type objects even though the description type code field yields multiple values for on type object: class DBAPITypeObject : def __init__ ( self , * values ): self . values = values def __cmp__ ( self , other ): if other in self . values : return 0 if other < self . values : return 1 else : return - 1 The resulting type object compares equal to all values passed to the constructor. Here is a snippet of Python code that implements the exception hierarchy defined above [10] : class Error ( Exception ): pass class Warning ( Exception ): pass class InterfaceError ( Error ): pass class DatabaseError ( Error ): pass class InternalError ( DatabaseError ): pass class OperationalError ( DatabaseError ): pass class ProgrammingError ( DatabaseError ): pass class IntegrityError ( DatabaseError ): pass class DataError ( DatabaseError ): pass class NotSupportedError ( DatabaseError ): pass In C you can use the PyErr_NewException(fullname, base, NULL) API to create the exception objects. Optional DB API Extensions During the lifetime of DB API 2.0, module authors have often extended their implementations beyond what is required by this DB API specification. To enhance compatibility and to provide a clean upgrade path to possible future versions of the specification, this section defines a set of common extensions to the core DB API 2.0 specification. As with all DB API optional features, the database module authors are free to not implement these additional attributes and methods (using them will then result in an AttributeError ) or to raise a NotSupportedError in case the availability can only be checked at run-time. It has been proposed to make usage of these extensions optionally visible to the programmer by issuing Python warnings through the Python warning framework. To make this feature useful, the warning messages must be standardized in order to be able to mask them. These standard messages are referred to below as Warning Message . Cursor .rownumber This read-only attribute should provide the current 0-based index of the cursor in the result set or None if the index cannot be determined. The index can be seen as index of the cursor in a sequence (the result set). The next fetch operation will fetch the row indexed by .rownumber in that sequence. Warning Message: “DB-API extension cursor.rownumber used” Connection.Error , Connection.ProgrammingError , etc. All exception classes defined by the DB API standard should be exposed on the Connection objects as attributes (in addition to being available at module scope). These attributes simplify error handling in multi-connection environments. Warning Message: “DB-API extension connection.<exception> used” Cursor .connection This read-only attribute return a reference to the Connection object on which the cursor was created. The attribute simplifies writing polymorph code in multi-connection environments. Warning Message: “DB-API extension cursor.connection used” Cursor .scroll ( value [, mode=’relative’ ]) Scroll the cursor in the result set to a new position according to mode . If mode is relative (default), value is taken as offset to the current position in the result set, if set to absolute , value states an absolute target position. An IndexError should be raised in case a scroll operation would leave the result set. In this case, the cursor position is left undefined (ideal would be to not move the cursor at all). Note This method should use native scrollable cursors, if available, or revert to an emulation for forward-only scrollable cursors. The method may raise NotSupportedError to signal that a specific operation is not supported by the database (e.g. backward scrolling). Warning Message: “DB-API extension cursor.scroll() used” Cursor.messages This is a Python list object to which the interface appends tuples (exception class, exception value) for all messages which the interfaces receives from the underlying database for this cursor. The list is cleared by all standard cursor methods calls (prior to executing the call) except for the .fetch*() calls automatically to avoid excessive memory usage and can also be cleared by executing del cursor.messages[:] . All error and warning messages generated by the database are placed into this list, so checking the list allows the user to verify correct operation of the method calls. The aim of this attribute is to eliminate the need for a Warning exception which often causes problems (some warnings really only have informational character). Warning Message: “DB-API extension cursor.messages used” Connection.messages Same as Cursor.messages except that the messages in the list are connection oriented. The list is cleared automatically by all standard connection methods calls (prior to executing the call) to avoid excessive memory usage and can also be cleared by executing del connection.messages[:] . Warning Message: “DB-API extension connection.messages used” Cursor .next () Return the next row from the currently executing SQL statement using the same semantics as .fetchone() . A StopIteration exception is raised when the result set is exhausted for Python versions 2.2 and later. Previous versions don’t have the StopIteration exception and so the method should raise an IndexError instead. Warning Message: “DB-API extension cursor.next() used” Cursor .__iter__ () Return self to make cursors compatible to the iteration protocol [8] . Warning Message: “DB-API extension cursor.__iter__() used” Cursor .lastrowid This read-only attribute provides the rowid of the last modified row (most databases return a rowid only when a single INSERT operation is performed). If the operation does not set a rowid or if the database does not support rowids, this attribute should be set to None . The semantics of .lastrowid are undefined in case the last executed statement modified more than one row, e.g. when using INSERT with .executemany() . Warning Message: “DB-API extension cursor.lastrowid used” Connection .autocommit Attribute to query and set the autocommit mode of the connection. Return True if the connection is operating in autocommit (non-transactional) mode. Return False if the connection is operating in manual commit (transactional) mode. Setting the attribute to True or False adjusts the connection’s mode accordingly. Changing the setting from True to False (disabling autocommit) will have the database leave autocommit mode and start a new transaction. Changing from False to True (enabling autocommit) has database dependent semantics with respect to how pending transactions are handled. [12] Deprecation notice : Even though several database modules implement both the read and write nature of this attribute, setting the autocommit mode by writing to the attribute is deprecated, since this may result in I/O and related exceptions, making it difficult to implement in an async context. [13] Warning Message: “DB-API extension connection.autocommit used” Optional Error Handling Extensions The core DB API specification only introduces a set of exceptions which can be raised to report errors to the user. In some cases, exceptions may be too disruptive for the flow of a program or even render execution impossible. For these cases and in order to simplify error handling when dealing with databases, database module authors may choose to implement user definable error handlers. This section describes a standard way of defining these error handlers. Connection.errorhandler , Cursor.errorhandler Read/write attribute which references an error handler to call in case an error condition is met. The handler must be a Python callable taking the following arguments: errorhandler( connection , cursor , errorclass , errorvalue ) where connection is a reference to the connection on which the cursor operates, cursor a reference to the cursor (or None in case the error does not apply to a cursor), errorclass is an error class which to instantiate using errorvalue as construction argument. The standard error handler should add the error information to the appropriate .messages attribute ( Connection.messages or Cursor.messages ) and raise the exception defined by the given errorclass and errorvalue parameters. If no .errorhandler is set (the attribute is None ), the standard error handling scheme as outlined above, should be applied. Warning Message: “DB-API extension .errorhandler used” Cursors should inherit the .errorhandler setting from their connection objects at cursor creation time. Optional Two-Phase Commit Extensions Many databases have support for two-phase commit (TPC) which allows managing transactions across multiple database connections and other resources. If a database backend provides support for two-phase commit and the database module author wishes to expose this support, the following API should be implemented. NotSupportedError should be raised, if the database backend support for two-phase commit can only be checked at run-time. TPC Transaction IDs As many databases follow the XA specification, transaction IDs are formed from three components: a format ID a global transaction ID a branch qualifier For a particular global transaction, the first two components should be the same for all resources. Each resource in the global transaction should be assigned a different branch qualifier. The various components must satisfy the following criteria: format ID: a non-negative 32-bit integer. global transaction ID and branch qualifier: byte strings no longer than 64 characters. Transaction IDs are created with the .xid() Connection method: .xid ( format_id , global_transaction_id , branch_qualifier ) Returns a transaction ID object suitable for passing to the .tpc_*() methods of this connection. If the database connection does not support TPC, a NotSupportedError is raised. The type of the object returned by .xid() is not defined, but it must provide sequence behaviour, allowing access to the three components. A conforming database module could choose to represent transaction IDs with tuples rather than a custom object. TPC Connection Methods .tpc_begin ( xid ) Begins a TPC transaction with the given transaction ID xid . This method should be called outside of a transaction ( i.e. nothing may have executed since the last .commit() or .rollback() ). Furthermore, it is an error to call .commit() or .rollback() within the TPC transaction. A ProgrammingError is raised, if the application calls .commit() or .rollback() during an active TPC transaction. If the database connection does not support TPC, a NotSupportedError is raised. .tpc_prepare () Performs the first phase of a transaction started with .tpc_begin() . A ProgrammingError should be raised if this method outside of a TPC transaction. After calling .tpc_prepare() , no statements can be executed until .tpc_commit() or .tpc_rollback() have been called. .tpc_commit ([ xid ]) When called with no arguments, .tpc_commit() commits a TPC transaction previously prepared with .tpc_prepare() . If .tpc_commit() is called prior to .tpc_prepare() , a single phase commit is performed. A transaction manager may choose to do this if only a single resource is participating in the global transaction. When called with a transaction ID xid , the database commits the given transaction. If an invalid transaction ID is provided, a ProgrammingError will be raised. This form should be called outside of a transaction, and is intended for use in recovery. On return, the TPC transaction is ended. .tpc_rollback ([ xid ]) When called with no arguments, .tpc_rollback() rolls back a TPC transaction. It may be called before or after .tpc_prepare() . When called with a transaction ID xid , it rolls back the given transaction. If an invalid transaction ID is provided, a ProgrammingError is raised. This form should be called outside of a transaction, and is intended for use in recovery. On return, the TPC transaction is ended. .tpc_recover () Returns a list of pending transaction IDs suitable for use with .tpc_commit(xid) or .tpc_rollback(xid) . If the database does not support transaction recovery, it may return an empty list or raise NotSupportedError . Frequently Asked Questions The database SIG often sees reoccurring questions about the DB API specification. This section covers some of the issues people sometimes have with the specification. Question: How can I construct a dictionary out of the tuples returned by .fetch*() : Answer: There are several existing tools available which provide helpers for this task. Most of them use the approach of using the column names defined in the cursor attribute .description as basis for the keys in the row dictionary. Note that the reason for not extending the DB API specification to also support dictionary return values for the .fetch*() methods is that this approach has several drawbacks: Some databases don’t support case-sensitive column names or auto-convert them to all lowercase or all uppercase characters. Columns in the result set which are generated by the query (e.g. using SQL functions) don’t map to table column names and databases usually generate names for these columns in a very database specific way. As a result, accessing the columns through dictionary keys varies between databases and makes writing portable code impossible. Major Changes from Version 1.0 to Version 2.0 The Python Database API 2.0 introduces a few major changes compared to the 1.0 version. Because some of these changes will cause existing DB API 1.0 based scripts to break, the major version number was adjusted to reflect this change. These are the most important changes from 1.0 to 2.0: The need for a separate dbi module was dropped and the functionality merged into the module interface itself. New constructors and Type Objects were added for date/time values, the RAW Type Object was renamed to BINARY . The resulting set should cover all basic data types commonly found in modern SQL databases. New constants ( apilevel , threadsafety , paramstyle ) and methods ( .executemany() , .nextset() ) were added to provide better database bindings. The semantics of .callproc() needed to call stored procedures are now clearly defined. The definition of the .execute() return value changed. Previously, the return value was based on the SQL statement type (which was hard to implement right) — it is undefined now; use the more flexible .rowcount attribute instead. Modules are free to return the old style return values, but these are no longer mandated by the specification and should be considered database interface dependent. Class based exceptions were incorporated into the specification. Module implementors are free to extend the exception layout defined in this specification by subclassing the defined exception classes. Post-publishing additions to the DB API 2.0 specification: Additional optional DB API extensions to the set of core functionality were specified. Open Issues Although the version 2.0 specification clarifies a lot of questions that were left open in the 1.0 version, there are still some remaining issues which should be addressed in future versions: Define a useful return value for .nextset() for the case where a new result set is available. Integrate the decimal module Decimal object for use as loss-less monetary and decimal interchange format. Footnotes [ 1 ] As a guideline the connection constructor parameters should be implemented as keyword parameters for more intuitive use and follow this order of parameters: Parameter Meaning dsn Data source name as string user User name as string (optional) password Password as string (optional) host Hostname (optional) database Database name (optional) E.g. a connect could look like this: connect ( dsn = 'myhost:MYDB' , user = 'guido' , password = '234$' ) Also see [13] regarding planned future additions to this list. [ 2 ] Module implementors should prefer numeric , named or pyformat over the other formats because these offer more clarity and flexibility. [3] ( 1 , 2 , 3 ) If the database does not support the functionality required by the method, the interface should throw an exception in case the method is used. The preferred approach is to not implement the method and thus have Python generate an AttributeError in case the method is requested. This allows the programmer to check for database capabilities using the standard hasattr() function. For some dynamically configured interfaces it may not be appropriate to require dynamically making the method available. These interfaces should then raise a NotSupportedError to indicate the non-ability to perform the roll back when the method is invoked. [ 4 ] A database interface may choose to support named cursors by allowing a string argument to the method. This feature is not part of the specification, since it complicates semantics of the .fetch*() methods. [ 5 ] The module will use the __getitem__ method of the parameters object to map either positions (integers) or names (strings) to parameter values. This allows for both sequences and mappings to be used as input. The term bound refers to the process of binding an input value to a database execution buffer. In practical terms, this means that the input value is directly used as a value in the operation. The client should not be required to “escape” the value so that it can be used — the value should be equal to the actual database value. [ 6 ] Note that the interface may implement row fetching using arrays and other optimizations. It is not guaranteed that a call to this method will only move the associated cursor forward by one row. [ 7 ] The rowcount attribute may be coded in a way that updates its value dynamically. This can be useful for databases that return usable rowcount values only after the first call to a .fetch*() method. [ 8 ] Implementation Note: Python C extensions will have to implement the tp_iter slot on the cursor object instead of the .__iter__() method. [ 9 ] The term number of affected rows generally refers to the number of rows deleted, updated or inserted by the last statement run on the database cursor. Most databases will return the total number of rows that were found by the corresponding WHERE clause of the statement. Some databases use a different interpretation for UPDATE s and only return the number of rows that were changed by the UPDATE , even though the WHERE clause of the statement may have found more matching rows. Database module authors should try to implement the more common interpretation of returning the total number of rows found by the WHERE clause, or clearly document a different interpretation of the .rowcount attribute. [10] ( 1 , 2 , 3 , 4 ) In Python 2 and earlier versions of this PEP, StandardError was used as the base class for all DB-API exceptions. Since StandardError was removed in Python 3, database modules targeting Python 3 should use Exception as base class instead. The PEP was updated to use Exception throughout the text, to avoid confusion. The change should not affect existing modules or uses of those modules, since all DB-API error exception classes are still rooted at the Error or Warning classes. [11] ( 1 , 2 ) In a future revision of the DB-API, the base class for Warning will likely change to the builtin Warning class. At the time of writing of the DB-API 2.0 in 1999, the warning framework in Python did not yet exist. [ 12 ] Many database modules implementing the autocommit attribute will automatically commit any pending transaction and then enter autocommit mode. It is generally recommended to explicitly .commit() or .rollback() transactions prior to changing the autocommit setting, since this is portable across database modules. [13] ( 1 , 2 ) In a future revision of the DB-API, we are going to introduce a new method .setautocommit(value) , which will allow setting the autocommit mode, and make .autocommit a read-only attribute. Additionally, we are considering to add a new standard keyword parameter autocommit to the Connection constructor. Modules authors are encouraged to add these changes in preparation for this change. Acknowledgements Many thanks go to Andrew Kuchling who converted the Python Database API Specification 2.0 from the original HTML format into the PEP format in 2001. Many thanks to James Henstridge for leading the discussion which led to the standardization of the two-phase commit API extensions in 2008. Many thanks to Daniele Varrazzo for converting the specification from text PEP format to ReST PEP format, which allows linking to various parts in 2012. Copyright This document has been placed in the Public Domain. Source: https://github.com/python/peps/blob/main/peps/pep-0249.rst Last modified: 2025-02-01 08:55:40 GMT Contents Introduction Module Interface Constructors Globals Exceptions Connection Objects Connection methods Cursor Objects Cursor attributes Cursor methods Type Objects and Constructors Implementation Hints for Module Authors Optional DB API Extensions Optional Error Handling Extensions Optional Two-Phase Commit Extensions TPC Transaction IDs TPC Connection Methods Frequently Asked Questions Major Changes from Version 1.0 to Version 2.0 Open Issues Footnotes Acknowledgements Copyright Page Source (GitHub) | 2026-01-13T08:49:06 |
https://popcorn.forem.com/popcorn_tv | TV News - Popcorn Movies and TV 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 Popcorn Movies and TV Close Follow User actions TV News 404 bio not found Joined Joined on Jun 22, 2025 More info about @popcorn_tv Badges 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 Post 303 posts published Comment 0 comments written Tag 0 tags followed Ramy Youssef Exits Will Ferrell's Netflix Golf Comedy Over Creative Differences; Molly Shannon Joins Cast TV News TV News TV News Follow Aug 12 '25 Ramy Youssef Exits Will Ferrell's Netflix Golf Comedy Over Creative Differences; Molly Shannon Joins Cast # marketing # offtopic # filmindustry # studios Comments Add Comment 1 min read The TVLine Performer of the Week: Alan Tudyk ("Resident Alien") TV News TV News TV News Follow Aug 12 '25 The TVLine Performer of the Week: Alan Tudyk ("Resident Alien") # tv # streaming # amazonprime # releasedates Comments Add Comment 1 min read Miranda Cosgrove shares 'exciting' update on iCarly movie: 'It looks like it's happening' TV News TV News TV News Follow Aug 12 '25 Miranda Cosgrove shares 'exciting' update on iCarly movie: 'It looks like it's happening' # tv # streaming # paramountplus # celebrityinterviews Comments Add Comment 1 min read 'One Piece' Renewed for Season 3 on Netflix TV News TV News TV News Follow Aug 12 '25 'One Piece' Renewed for Season 3 on Netflix # netflix # streaming # tv # anime Comments Add Comment 1 min read Ben Stiller Wants to Make ‘Severance' More Quickly—but First, He Needs to Get It Just Right TV News TV News TV News Follow Aug 12 '25 Ben Stiller Wants to Make ‘Severance' More Quickly—but First, He Needs to Get It Just Right # movies # hollywood # celebrities # directing Comments Add Comment 1 min read ‘Wednesday' Season 2 Review: Jenna Ortega Gets Lost Amid Addams Family Mayhem in Overcrowded Netflix Return TV News TV News TV News Follow Aug 12 '25 ‘Wednesday' Season 2 Review: Jenna Ortega Gets Lost Amid Addams Family Mayhem in Overcrowded Netflix Return # streaming # reviews # netflix # tv Comments Add Comment 1 min read Gina Carano, Disney Settle Legal Dispute Over ‘Mandalorian' Firing TV News TV News TV News Follow Aug 12 '25 Gina Carano, Disney Settle Legal Dispute Over ‘Mandalorian' Firing # filmindustry # marketing # agencies # offtopic Comments Add Comment 1 min read Kelley Mack, Actress in ‘The Walking Dead,' Dies at 33 TV News TV News TV News Follow Aug 12 '25 Kelley Mack, Actress in ‘The Walking Dead,' Dies at 33 # tv # celebrities # horror # biography Comments Add Comment 1 min read New Comedy Central Boss George Cheeks Is Noncommittal on Jon Stewart's ‘Daily Show' Future TV News TV News TV News Follow Aug 12 '25 New Comedy Central Boss George Cheeks Is Noncommittal on Jon Stewart's ‘Daily Show' Future # tv # talkshows # comedy # celebrities Comments Add Comment 1 min read Seth MacFarlane Wishes TV Was Less “Dystopian” And “Pessimistic”: “Give People Hope” TV News TV News TV News Follow Aug 12 '25 Seth MacFarlane Wishes TV Was Less “Dystopian” And “Pessimistic”: “Give People Hope” # tv # celebrities # celebrityinterviews # analysis Comments Add Comment 1 min read ‘South Park' Doubles Down on Kristi Noem With Paramount+ End Credits Scene Featuring Her on Shooting Spree at a Pet Store TV News TV News TV News Follow Aug 12 '25 ‘South Park' Doubles Down on Kristi Noem With Paramount+ End Credits Scene Featuring Her on Shooting Spree at a Pet Store # marketing # analysis # filmindustry # offtopic Comments Add Comment 1 min read TV Ratings: ‘South Park' On-Air Viewers Surge With Season 27's Second Episode (838,000 Viewers) TV News TV News TV News Follow Aug 12 '25 TV Ratings: ‘South Park' On-Air Viewers Surge With Season 27's Second Episode (838,000 Viewers) # tv # analysis # comedy # animation 5 reactions Comments Add Comment 1 min read Stephen Colbert's 'Late Show' Ratings Surge Continues, Beats Fallon and Kimmel Combined TV News TV News TV News Follow Aug 12 '25 Stephen Colbert's 'Late Show' Ratings Surge Continues, Beats Fallon and Kimmel Combined # tv # talkshows # analysis # celebrities Comments Add Comment 1 min read As Stephen Colbert Signs Off For 'Late Show' Summer Hiatus, He Says: “Netflix, Call Me I'm Available In June” TV News TV News TV News Follow Aug 12 '25 As Stephen Colbert Signs Off For 'Late Show' Summer Hiatus, He Says: “Netflix, Call Me I'm Available In June” # talkshows # tv # netflix # streaming Comments Add Comment 1 min read 'The Punisher' Special, Starring Jon Bernthal, Wraps Filming TV News TV News TV News Follow Aug 8 '25 'The Punisher' Special, Starring Jon Bernthal, Wraps Filming # tv # superhero # behindthescenes # celebrities 4 reactions Comments 1 comment 1 min read Stephen Colbert To Guest Star As a Late-Night Host In An Upcoming Episode of ‘Elsbeth' TV News TV News TV News Follow Aug 8 '25 Stephen Colbert To Guest Star As a Late-Night Host In An Upcoming Episode of ‘Elsbeth' # accessibilitymedia # marketing # filmindustry # distribution Comments Add Comment 1 min read ‘King of the Hill' Showrunner on Writing Hank Hill for a Different Era TV News TV News TV News Follow Aug 8 '25 ‘King of the Hill' Showrunner on Writing Hank Hill for a Different Era # animation # tv # hulu # celebrityinterviews Comments Add Comment 1 min read Ben Stiller Wants to Make ‘Severance' More Quickly—but First, He Needs to Get It Just Right TV News TV News TV News Follow Aug 8 '25 Ben Stiller Wants to Make ‘Severance' More Quickly—but First, He Needs to Get It Just Right # celebrities # hollywood # movies # celebrityinterviews Comments Add Comment 1 min read Popular 1980s actor Loni Anderson of the hit TV series ‘WKRP in Cincinnati' has died TV News TV News TV News Follow Aug 8 '25 Popular 1980s actor Loni Anderson of the hit TV series ‘WKRP in Cincinnati' has died # celebrities # sitcom # tv # biography Comments Add Comment 1 min read 'Superstore' Actor Jon Miyahara Dies at 83 TV News TV News TV News Follow Aug 8 '25 'Superstore' Actor Jon Miyahara Dies at 83 # tv # releasedates # recap # streaming Comments Add Comment 1 min read Gina Carano, Disney Settle Legal Dispute Over ‘Mandalorian' Firing TV News TV News TV News Follow Aug 8 '25 Gina Carano, Disney Settle Legal Dispute Over ‘Mandalorian' Firing # marketing # analysis # agencies # distribution Comments Add Comment 1 min read ‘Wednesday' Season 2 Review: Jenna Ortega Gets Lost Amid Addams Family Mayhem in Overcrowded Netflix Return TV News TV News TV News Follow Aug 8 '25 ‘Wednesday' Season 2 Review: Jenna Ortega Gets Lost Amid Addams Family Mayhem in Overcrowded Netflix Return # reviews # tv # netflix # streaming Comments Add Comment 1 min read Marvel's 'Vision' Series, Starring Paul Bettany, Wraps Filming TV News TV News TV News Follow Aug 8 '25 Marvel's 'Vision' Series, Starring Paul Bettany, Wraps Filming # disneyplus # superhero # filmindustry # studios Comments Add Comment 1 min read ‘Alien: Earth' Review: Noah Hawley's TV Spinoff Masterfully Expands Franchise's Exploration of Humanity TV News TV News TV News Follow Aug 8 '25 ‘Alien: Earth' Review: Noah Hawley's TV Spinoff Masterfully Expands Franchise's Exploration of Humanity # reviews # scifi # tv # streaming 2 reactions Comments Add Comment 1 min read ‘I'm Voting for Stephen': Jimmy Kimmel's Emmys FYC Ad Stands Up for Colbert and ‘The Late Show' Amid CBS Cancellation TV News TV News TV News Follow Aug 8 '25 ‘I'm Voting for Stephen': Jimmy Kimmel's Emmys FYC Ad Stands Up for Colbert and ‘The Late Show' Amid CBS Cancellation # marketing # distribution # filmindustry # streamingstats Comments Add Comment 1 min read Kelley Mack, Actress in ‘The Walking Dead,' Dies at 33 TV News TV News TV News Follow Aug 8 '25 Kelley Mack, Actress in ‘The Walking Dead,' Dies at 33 # tv # horror # celebrities # biography Comments Add Comment 1 min read Seth MacFarlane Applauds the ‘Incredible' Timeliness of ‘South Park' – Despite Years-Long Feud With Its Creators TV News TV News TV News Follow Aug 8 '25 Seth MacFarlane Applauds the ‘Incredible' Timeliness of ‘South Park' – Despite Years-Long Feud With Its Creators # animation # tv # comedy # celebrities Comments Add Comment 1 min read Roku launches Howdy, a $2.99 ad-free streaming service TV News TV News TV News Follow Aug 7 '25 Roku launches Howdy, a $2.99 ad-free streaming service # streaming # streamingdevices # streamingwars # tv Comments Add Comment 1 min read The Rings Of Power Season 3 Enters Production As Amazon Teases Sauron's Return TV News TV News TV News Follow Aug 7 '25 The Rings Of Power Season 3 Enters Production As Amazon Teases Sauron's Return # fantasy # tv # amazonprime # behindthescenes Comments Add Comment 1 min read Ben Stiller Wants to Make ‘Severance' More Quickly—but First, He Needs to Get It Just Right TV News TV News TV News Follow Aug 7 '25 Ben Stiller Wants to Make ‘Severance' More Quickly—but First, He Needs to Get It Just Right # celebrities # hollywood # movies # tv 3 reactions Comments 1 comment 1 min read Stephen Colbert To Guest Star As a Late-Night Host In An Upcoming Episode of ‘Elsbeth' TV News TV News TV News Follow Aug 7 '25 Stephen Colbert To Guest Star As a Late-Night Host In An Upcoming Episode of ‘Elsbeth' # cinema # hollywood # filmindustry # movies Comments Add Comment 1 min read ‘King of the Hill' Showrunner on Writing Hank Hill for a Different Era TV News TV News TV News Follow Aug 7 '25 ‘King of the Hill' Showrunner on Writing Hank Hill for a Different Era # animation # tv # streaming # hulu 1 reaction Comments 1 comment 1 min read 'Silo' Season 4 Begins Filming TV News TV News TV News Follow Aug 7 '25 'Silo' Season 4 Begins Filming # tv # drama # appletvplus # behindthescenes 1 reaction Comments 2 comments 1 min read Popular 1980s actor Loni Anderson of the hit TV series ‘WKRP in Cincinnati' has died TV News TV News TV News Follow Aug 7 '25 Popular 1980s actor Loni Anderson of the hit TV series ‘WKRP in Cincinnati' has died # celebrities # biography # tv # sitcom Comments Add Comment 1 min read ‘Wednesday' Season 2 Review: Jenna Ortega Gets Lost Amid Addams Family Mayhem in Overcrowded Netflix Return TV News TV News TV News Follow Aug 7 '25 ‘Wednesday' Season 2 Review: Jenna Ortega Gets Lost Amid Addams Family Mayhem in Overcrowded Netflix Return # reviews # tv # netflix # streaming Comments Add Comment 1 min read Alien: Earth is 'Andor for Alien' — Review TV News TV News TV News Follow Aug 7 '25 Alien: Earth is 'Andor for Alien' — Review # reviews # tv # scifi # horror Comments Add Comment 1 min read Marvel's 'Vision' Series, Starring Paul Bettany, Wraps Filming TV News TV News TV News Follow Aug 7 '25 Marvel's 'Vision' Series, Starring Paul Bettany, Wraps Filming # superhero # disneyplus # tv # filmindustry Comments Add Comment 1 min read ‘Alien: Earth' Review: Noah Hawley's TV Spinoff Masterfully Expands Franchise's Exploration of Humanity TV News TV News TV News Follow Aug 7 '25 ‘Alien: Earth' Review: Noah Hawley's TV Spinoff Masterfully Expands Franchise's Exploration of Humanity # scifi # tv # reviews # streaming Comments Add Comment 1 min read ‘I'm Voting for Stephen': Jimmy Kimmel's Emmys FYC Ad Stands Up for Colbert and ‘The Late Show' Amid CBS Cancellation TV News TV News TV News Follow Aug 7 '25 ‘I'm Voting for Stephen': Jimmy Kimmel's Emmys FYC Ad Stands Up for Colbert and ‘The Late Show' Amid CBS Cancellation # marketing # distribution # offtopic # behindthescenes Comments Add Comment 1 min read Kelley Mack, Actress in ‘The Walking Dead,' Dies at 33 TV News TV News TV News Follow Aug 7 '25 Kelley Mack, Actress in ‘The Walking Dead,' Dies at 33 # tv # celebrities # horror # biography Comments Add Comment 1 min read Disney Will Stop Reporting Subscriber Numbers for Disney+, Hulu and ESPN+ TV News TV News TV News Follow Aug 7 '25 Disney Will Stop Reporting Subscriber Numbers for Disney+, Hulu and ESPN+ # marketing # agencies # offtopic # filmindustry Comments Add Comment 1 min read Seth MacFarlane Applauds the ‘Incredible' Timeliness of ‘South Park' – Despite Years-Long Feud With Its Creators TV News TV News TV News Follow Aug 7 '25 Seth MacFarlane Applauds the ‘Incredible' Timeliness of ‘South Park' – Despite Years-Long Feud With Its Creators # animation # tv # comedy # celebrities Comments Add Comment 1 min read ‘King of the Hill' Showrunner on Writing Hank Hill for a Different Era TV News TV News TV News Follow Aug 5 '25 ‘King of the Hill' Showrunner on Writing Hank Hill for a Different Era # animation # tv # comedy # hulu 3 reactions Comments Add Comment 1 min read ‘South Park' to Exit HBO Max on August 5 as Show Consolidates Library on Paramount+ TV News TV News TV News Follow Aug 5 '25 ‘South Park' to Exit HBO Max on August 5 as Show Consolidates Library on Paramount+ # streaming # tv # hbomax # paramountplus 3 reactions Comments 1 comment 1 min read The Rings Of Power Season 3 Enters Production As Amazon Teases Sauron's Return TV News TV News TV News Follow Aug 5 '25 The Rings Of Power Season 3 Enters Production As Amazon Teases Sauron's Return # tv # amazonprime # fantasy # behindthescenes Comments Add Comment 1 min read Stephen Colbert To Guest Star As a Late-Night Host In An Upcoming Episode of ‘Elsbeth' TV News TV News TV News Follow Aug 5 '25 Stephen Colbert To Guest Star As a Late-Night Host In An Upcoming Episode of ‘Elsbeth' # movies # tv # filmindustry # hollywood Comments Add Comment 1 min read Popular 1980s actor Loni Anderson of the hit TV series ‘WKRP in Cincinnati' has died TV News TV News TV News Follow Aug 5 '25 Popular 1980s actor Loni Anderson of the hit TV series ‘WKRP in Cincinnati' has died # celebrities # tv # sitcom # biography Comments Add Comment 1 min read Paramount Needs 'South Park' — Despite the Ridicule and $1.5 Billion Price Tag | Analysis TV News TV News TV News Follow Aug 5 '25 Paramount Needs 'South Park' — Despite the Ridicule and $1.5 Billion Price Tag | Analysis # analysis # streaming # tv # streamingwars Comments Add Comment 1 min read Marvel's 'Vision' Series, Starring Paul Bettany, Wraps Filming TV News TV News TV News Follow Aug 5 '25 Marvel's 'Vision' Series, Starring Paul Bettany, Wraps Filming # superhero # disneyplus # filmindustry # behindthescenes Comments Add Comment 1 min read ‘I'm Voting for Stephen': Jimmy Kimmel's Emmys FYC Ad Stands Up for Colbert and ‘The Late Show' Amid CBS Cancellation TV News TV News TV News Follow Aug 5 '25 ‘I'm Voting for Stephen': Jimmy Kimmel's Emmys FYC Ad Stands Up for Colbert and ‘The Late Show' Amid CBS Cancellation # marketing # analysis # distribution # offtopic Comments Add Comment 1 min read 'The Daily Show' Is Taking Five Weeks Off TV News TV News TV News Follow Aug 5 '25 'The Daily Show' Is Taking Five Weeks Off # tv # comedy # talkshows # celebrities Comments Add Comment 1 min read '3 Body Problem' Season 2 Begins Filming TV News TV News TV News Follow Aug 5 '25 '3 Body Problem' Season 2 Begins Filming # netflix # scifi # tv # casting Comments Add Comment 1 min read Brennan Lee Mulligan Signs New Three-Year Deal With Dropout TV News TV News TV News Follow Aug 5 '25 Brennan Lee Mulligan Signs New Three-Year Deal With Dropout # marketing # filmindustry # hollywood # streaming Comments Add Comment 1 min read Corporation For Public Broadcasting To Shut Down Operations TV News TV News TV News Follow Aug 5 '25 Corporation For Public Broadcasting To Shut Down Operations # funding # agencies # tv # distribution Comments Add Comment 1 min read Seth MacFarlane Applauds the ‘Incredible' Timeliness of ‘South Park' – Despite Years-Long Feud With Its Creators TV News TV News TV News Follow Aug 5 '25 Seth MacFarlane Applauds the ‘Incredible' Timeliness of ‘South Park' – Despite Years-Long Feud With Its Creators # animation # comedy # tv # celebrities Comments Add Comment 1 min read ‘South Park' Skips This Week, Sets Aug. 6 Episode With Trump and Satan Returning TV News TV News TV News Follow Aug 5 '25 ‘South Park' Skips This Week, Sets Aug. 6 Episode With Trump and Satan Returning # animation # comedy # tv # celebrities Comments Add Comment 1 min read Stephen Colbert's 'The Late Show' Sets Ratings Record in Wake of Cancellation TV News TV News TV News Follow Aug 5 '25 Stephen Colbert's 'The Late Show' Sets Ratings Record in Wake of Cancellation # talkshows # streamingstats # tv # celebrities Comments Add Comment 1 min read ‘South Park': 5.9 Million Viewers Watched Trump-Mocking Season 27 Premiere in First Three Days TV News TV News TV News Follow Aug 5 '25 ‘South Park': 5.9 Million Viewers Watched Trump-Mocking Season 27 Premiere in First Three Days # marketing # agencies # analysis # offtopic 9 reactions Comments Add Comment 1 min read ‘The Legend of Vox Machina' Renewed for Fifth and Final Season TV News TV News TV News Follow Jul 29 '25 ‘The Legend of Vox Machina' Renewed for Fifth and Final Season # marketing # filmindustry # streaming # distribution Comments Add Comment 1 min read ‘Rick &amp; Morty' Lands A Presidential Spinoff At Adult Swim TV News TV News TV News Follow Jul 29 '25 ‘Rick &amp; Morty' Lands A Presidential Spinoff At Adult Swim # animation # tv # comedy # cartoons 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 Popcorn Movies and TV — Movie and TV enthusiasm, criticism and everything in-between. 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 . Popcorn Movies and TV © 2016 - 2026. Let's watch something great! Log in Create account | 2026-01-13T08:49:06 |
https://www.python.org/community/workshops/#python-network | Conferences and Workshops | 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 >>> Python Conferences Conferences and Workshops Conference Listings There are quite a number of Python conferences happening all year around and in many parts of the world. Many of them are taking place yearly or even more frequent: Python Conferences List on the Python Wiki -- this is the main and most complete list of conferences around the world Subsets of this list are also available on other sites: pycon.org -- lists a subset of mostly national Python conferences PyData -- listings of Python conferences specializing in AI & Data Science Several of these conferences record the talk sessions on video. pyvideo.org provides an index to a large set these videos. Announcing Events If you would like to announce a Python related event, please see Submitting an event to the Python events calendars . You can also ask on pydotorg-www at python dot org for help. Adding Conferences If you have an event to add, please see the instructions on how to edit Python Wiki for details. If you are organizing a Python conference or thinking of organizing one, please subscribe to the Python conferences mailing list . 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://zeroday.forem.com/andrew_despres/comptia-security-sy0-701-12-study-guide-core-security-concepts-19bg | CompTIA Security+ SY0-701 1.2 Study Guide: Core Security Concepts - Security 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 Security Forem 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 Andrew Despres Posted on Jan 9 CompTIA Security+ SY0-701 1.2 Study Guide: Core Security Concepts # comptia # securityplus # beginners # cybersecurity This guide provides a comprehensive review of fundamental security concepts essential for the CompTIA Security+ SY0-701 certification. It synthesizes critical information on identity and access management, security frameworks, deception techniques, and physical security controls to build a strong foundational knowledge base. 1. The AAA Framework: Authentication, Authorization, and Accounting The AAA framework is a foundational security model that governs how users and systems gain and maintain access to resources. It is comprised of three core components: Authentication, Authorization, and Accounting. The Three A's Explained Identification & Authentication (Who are you?): This is the process of proving an identity. It begins with identification , where a user claims to be a specific person (e.g., by entering a username). Authentication is the step that verifies this claim. This is typically done by providing a secret, like a password, or other authentication factors. The system checks these credentials to prove the user is who they say they are. Authorization (What are you allowed to do?): Once a user is authenticated, authorization determines their level of access. This process ensures users can only access the resources necessary for their specific roles. For example, a user in the Shipping and Receiving department should be authorized to access tracking systems but should be denied access to sensitive files in the Finance department. Accounting (What did you do?): This component is responsible for logging all activity. Security systems must keep a detailed record of events, such as login times, the amount of data transferred, and logout times. This creates an audit trail for security analysis and incident response. Real-World Analogy: Think of the AAA framework like entering a secure corporate office. Identification: Stating your name to the front desk security guard. Authentication: Showing your company ID badge with your picture on it to prove you are that person. Authorization: Your ID badge only grants you access to the floors where your department is located, not to the executive suite or the data center. Accounting: The electronic lock system logs every time your badge is used to open a door, creating a record of your movements. Practical Application: VPN Access A common application of AAA is managing remote access via a VPN. A remote client connects to a VPN concentrator and is prompted for credentials (username, password, etc.). The VPN concentrator does not store user credentials. It forwards the authentication request to a central AAA server . The AAA server checks the provided credentials against its database. If the credentials are valid, the AAA server sends an approval back to the VPN concentrator. The VPN concentrator, having successfully authenticated the user, then grants them authorized access to the internal network resources, like a file server. Device Authentication with Certificates Authenticating devices, such as company-owned laptops connecting remotely, presents a unique challenge as they cannot type a password. This is often solved using digital certificates. Certificate Authority (CA): A trusted entity within an organization responsible for creating, signing, and managing digital certificates. Process: The CA creates a unique device certificate specifically for the laptop. This certificate is digitally signed by the CA, which verifies its authenticity. The certificate is installed on the laptop. When the laptop attempts to connect to the network (e.g., via a VPN), it presents its certificate as an authentication factor. The network device (like a VPN concentrator) verifies that the certificate was signed by the trusted internal CA, thus authenticating the device as a legitimate, company-owned machine. Scalable Authorization Models Manually assigning specific permissions to every user for every resource is inefficient and does not scale well in large organizations. If a company has hundreds of employees in a department, an administrator would have to manually configure permissions for each person, which is a monumental task. To solve this, organizations use authorization models as an abstraction layer. Example: Role-Based Access: Instead of assigning permissions directly to users, permissions are assigned to a group. A group is created, such as "Shipping and Receiving." This group is granted all necessary permissions: access to tracking databases, shipping label software, customer contact info, etc. To grant a new employee access, an administrator simply adds their user account to the "Shipping and Receiving" group. The user instantly inherits all the permissions assigned to that group. This streamlines administration for hundreds or thousands of users. 2. The CIA Triad: The Pillars of Information Security The CIA Triad is a model designed to guide policies for information security. The three pillars—Confidentiality, Integrity, and Availability—represent the core objectives of any security program. It is sometimes referred to as the AIC Triad to avoid confusion with the U.S. Central Intelligence Agency. Confidentiality (C): Ensuring that information is not disclosed to unauthorized individuals, entities, or processes. It's about keeping data private. Methods: Encryption: Scrambling data so it's unreadable without the proper decryption key. Access Controls: Limiting access to data based on user roles and permissions. Multi-Factor Authentication: Requiring multiple forms of verification to prove identity before granting access. Integrity (I): Maintaining the consistency, accuracy, and trustworthiness of data over its entire lifecycle. It ensures data has not been altered in an unauthorized manner. Methods: Hashing: Creating a unique digital fingerprint of data. If the data changes, the hash changes, revealing the modification. Digital Signatures: Encrypting a hash with a private key to verify the sender's identity and the data's integrity. Certificates: Used to identify devices or people and ensure the integrity of data transfers. Availability (A): Ensuring that systems and data are operational and accessible to authorized users when needed. Methods: Redundancy & Fault Tolerance: Having duplicate components or systems so that if one fails, another takes over immediately. Patching: Regularly updating systems to fix bugs and close security holes, ensuring stability and preventing exploits that could cause downtime. 3. Non-repudiation: Proving an Action Occurred Non-repudiation is the assurance that someone cannot deny the validity of something. In cryptography, it provides undeniable proof that a specific action, such as sending a message, was performed by a specific entity. This is the digital equivalent of a legally binding signature on a contract. Non-repudiation is built on two key concepts: Proof of Integrity This verifies that received data is identical to the data that was originally sent, ensuring it is accurate, consistent, and unchanged. How it works: This is achieved using a hash (also called a message digest or fingerprint). A hashing algorithm takes an input (like a file or message) and produces a short, fixed-length string of text. Key Property: Even a single-character change in the input data will result in a completely different hash. Example: A user downloads an 8.1 MB file and calculates its hash. They compare this hash to the one provided by the source. If the hashes match, the file is authentic. If they don't, the file was corrupted or tampered with during download. Proof of Origin While a hash proves data integrity, it doesn't prove who sent it. Proof of origin authenticates the source of the message. This is accomplished using a digital signature . How it works: Hashing: The sender (Alice) creates a hash of her plaintext message (e.g., "You're hired, Bob."). Encryption: Alice encrypts this hash using her private key . Only she has this key. The resulting encrypted hash is the digital signature. Sending: Alice sends the original plaintext message along with the digital signature to the recipient (Bob). Decryption: Bob receives the message and signature. He uses Alice's public key (which is freely available) to decrypt the signature, revealing the original hash. Verification: Bob independently creates a hash of the plaintext message he received. Comparison: Bob compares the hash he just created with the one he decrypted from the signature. Result: If the hashes match, Bob has proven two things: Integrity: The message was not altered in transit. Origin: The message could only have been sent by Alice, because only her private key could create a signature that her public key can successfully decrypt. 4. Zero Trust Architecture Zero Trust is a modern security model built on the principle of "never trust, always verify." It operates under the assumption that threats exist both inside and outside the network. In a Zero Trust environment, no user, device, or process is trusted by default, and every access request must be strictly authenticated and authorized. Core Concepts Functional Planes: Security devices and processes can be broken into two distinct planes of operation: Data Plane: The "workhorse" of a device. It handles the actual processing and forwarding of data packets, frames, and other network traffic in real-time. Control Plane: The "management" layer. It configures the policies, rules, and routing tables that dictate how the data plane operates. Any time an administrator configures a firewall rule or sets up a routing policy, they are working in the control plane. Adaptive Identity: Instead of a simple username/password check, access decisions are made dynamically based on a wide range of contextual data points, such as the user's physical location, IP address, device type, and relationship to the organization (employee, contractor, etc.). If a request seems unusual (e.g., a U.S.-based user logging in from an IP address in China), the system can automatically require stronger authentication. Security Zones: The network is segmented into zones (e.g., untrusted, trusted, internal, VPN groups). Policies are then created to control traffic flow between these zones. For example, a rule might implicitly trust traffic from the "trusted" corporate office zone to the "internal" data center zone, while automatically denying all traffic from an "untrusted" zone. Zero Trust Model Components Policy Enforcement Point (PEP): This is the "gatekeeper." All traffic must pass through a PEP, where security policies are applied. It can be thought of as a combination of devices (firewalls, switches) that work together to control access. Policy Decision Point (PDP): This is the "brain" of the operation. The PEP gathers information about an access request and sends it to the PDP. The PDP then makes the decision to grant, deny, or revoke access based on predefined security policies. It consists of: Policy Engine: Compares the request against security policies to make a decision. Policy Administrator: Communicates the decision from the Policy Engine back to the PEP, providing any necessary credentials or tokens. 5. Deception and Disruption Techniques Beyond preventing attacks, security professionals can use deception to actively disrupt and study attackers. These techniques lure adversaries into controlled environments to waste their time and reveal their methods. Honeypot: A single computer system, application, or network service designed to look like a legitimate and attractive target. It is isolated from the production network and is heavily monitored. When an attacker interacts with the honeypot, security teams can analyze their techniques and tools without risking real systems. Honeynet: A more complex setup consisting of a network of honeypots (e.g., workstations, servers, routers). A honeynet creates a much more believable virtual world for an attacker to explore, keeping them engaged longer and providing more detailed intelligence. For more information, visit projecthoneypot.org. Honeyfile: A fake file placed on a system that is designed to be appealing to an attacker (e.g., passwords.txt or financial_reports.xlsx). The file contains no real sensitive data, but access to it is monitored. If the file is opened, an alert is triggered, notifying security teams of an intruder's presence. Honeytoken: A piece of fake, traceable data embedded within a system. This could be a fake API key, a set of bogus email addresses, or false database records. If this token appears elsewhere on the internet, it serves as an undeniable indicator of a data breach and can help trace where the information was leaked from. 6. Gap Analysis A gap analysis is a formal review process that compares an organization's current performance or state with its desired future state or an established standard. In IT security, it's used to identify deficiencies in security controls and create a strategic plan for improvement. The Process Establish a Baseline: Before starting, a goal or standard must be chosen. This could be an industry framework like NIST SP 800-171 (for protecting government information) or ISO/IEC 27001 , or a custom baseline developed by the organization. Evaluate People and Processes: The analysis examines the current security posture, including: People: The experience, training, and knowledge of security staff. Processes: How existing IT systems and procedures align with formal security policies. Identify Gaps: The core of the analysis involves comparing the current state to the baseline to find weaknesses or "gaps." This involves breaking down broad security categories (like Access Control) into smaller, specific controls (like user registration, management of privileged rights, etc.) and evaluating each one. Create a Report: The final gap analysis report summarizes the findings. It not only details where the organization is today but also provides a strategic roadmap to reach the desired state. This includes recommendations, estimated costs, required equipment, and timelines. A common visual tool is a color-coded chart (Red, Yellow, Green) that shows the compliance level of different departments or systems against the baseline requirements. 7. Physical Security Controls Protecting digital assets also requires securing the physical environment where they are stored and accessed. These concepts—from verifying identity with AAA to building resilient networks with Zero Trust—are not just theoretical; they are the active measures that professionals use every day to defend critical systems. As technology evolves, so do the threats we face. This brings a critical question to mind: How will these fundamental principles adapt to secure emerging technologies like artificial intelligence and the Internet of Things? 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 Andrew Despres Follow IT Helpdesk for over 10 years. Started off in Retail IT and worked my way into K-12 EDU helpdesk. Currently working for a Google Workspace/GCP specialized MSP. Always learning. Always growing. Location Edmonton Education Grant MacEwan University Pronouns He/Him Work Senior Support Engineer for Google Workspace Customers Joined Oct 27, 2024 More from Andrew Despres CompTIA Security+ SY0-701 1.1 Study Guide: Understanding Security Controls # comptia # securityplus # beginners # cybersecurity CompTIA Network+ N10-009 5.5 Study Guide: Network Device Commands and Tools # networking # network # comptia # beginners CompTIA Network+ N10-009 4.3 Study Guide: Device and Network Security # networking # cybersecurity # comptia # beginners 💎 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 Security Forem — Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike 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 . Security Forem © 2016 - 2026. Share. Secure. Succeed Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/stackforgetx/advanced-spreadsheet-implementation-with-revogrid-in-react-hcc | Advanced Spreadsheet Implementation with RevoGrid in React - 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 Advanced Spreadsheet Implementation with RevoGrid in React # webdev # react # tutorial # beginners RevoGrid is a high-performance, virtualized spreadsheet component for React that can handle millions of rows and columns with smooth scrolling and editing capabilities. Built with Web Components and optimized for performance, it's ideal for enterprise applications requiring Excel-like functionality. This guide walks through implementing advanced spreadsheet features using RevoGrid with React, covering virtual scrolling, custom cell editors, and complex data manipulation. This is part 6 of a series on using RevoGrid with React. Prerequisites Before you begin, ensure you have: Node.js version 16.0 or higher npm , yarn , or pnpm package manager A React project (version 16.8 or higher) with hooks support Advanced understanding of React hooks, refs, and performance optimization Familiarity with Web Components and virtualization concepts Knowledge of TypeScript (highly recommended) Installation Install RevoGrid React wrapper: npm install @revolist/revogrid-react Enter fullscreen mode Exit fullscreen mode Or with yarn: yarn add @revolist/revogrid-react Enter fullscreen mode Exit fullscreen mode Or with pnpm: pnpm add @revolist/revogrid-react Enter fullscreen mode Exit fullscreen mode Your package.json should include: { "dependencies" : { "@revolist/revogrid-react" : "^6.0.0" , "react" : "^18.0.0" , "react-dom" : "^18.0.0" } } Enter fullscreen mode Exit fullscreen mode Project Setup RevoGrid requires minimal setup. Import the component and styles in your application: // src/index.js import React from ' react ' ; import ReactDOM from ' react-dom/client ' ; import ' @revolist/revogrid/dist/revogrid.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 First Example / Basic Usage Let's create a basic RevoGrid component. Create src/Spreadsheet.jsx : // src/Spreadsheet.jsx import React , { useRef , useEffect } from ' react ' ; import { RevoGrid } from ' @revolist/revogrid-react ' ; import ' @revolist/revogrid/dist/revogrid.css ' ; function Spreadsheet () { const gridRef = useRef ( null ); // Column definitions const columns = [ { prop : ' id ' , name : ' ID ' , size : 100 }, { prop : ' name ' , name : ' Name ' , size : 200 }, { prop : ' email ' , name : ' Email ' , size : 250 }, { prop : ' role ' , name : ' Role ' , size : 150 } ]; // Row data const rows = [ { id : 1 , name : ' John Doe ' , email : ' john@example.com ' , role : ' Admin ' }, { id : 2 , name : ' Jane Smith ' , email : ' jane@example.com ' , role : ' User ' }, { id : 3 , name : ' Bob Johnson ' , email : ' bob@example.com ' , role : ' User ' }, { id : 4 , name : ' Alice Williams ' , email : ' alice@example.com ' , role : ' Admin ' } ]; useEffect (() => { if ( gridRef . current ) { const grid = gridRef . current ; // Set data after component mounts grid . columns = columns ; grid . source = rows ; } }, []); return ( < div style = { { height : ' 500px ' , width : ' 100% ' } } > < RevoGrid ref = { gridRef } /> </ div > ); } export default Spreadsheet ; Enter fullscreen mode Exit fullscreen mode Understanding the Basics RevoGrid uses a column-based configuration where: prop : Maps to a property in your row data name : Column header text size : Column width in pixels editor : Custom cell editor component cellTemplate : Custom cell renderer Key concepts for advanced usage: Virtualization : Automatically handles large datasets through virtual scrolling Web Components : Built on Web Components standard for performance Refs : Use refs to access grid API and methods Event Handlers : Respond to cell edits, selections, and other interactions Here's an example with editable cells: // src/EditableSpreadsheet.jsx import React , { useRef , useEffect , useState } from ' react ' ; import { RevoGrid } from ' @revolist/revogrid-react ' ; import ' @revolist/revogrid/dist/revogrid.css ' ; function EditableSpreadsheet () { const gridRef = useRef ( null ); const [ data , setData ] = useState ([ { id : 1 , product : ' Laptop ' , price : 999.99 , stock : 15 }, { id : 2 , product : ' Mouse ' , price : 29.99 , stock : 8 }, { id : 3 , product : ' Keyboard ' , price : 79.99 , stock : 12 } ]); const columns = [ { prop : ' id ' , name : ' ID ' , size : 80 , readonly : true }, { prop : ' product ' , name : ' Product ' , size : 200 , editor : ' string ' }, { prop : ' price ' , name : ' Price ' , size : 120 , editor : ' number ' , cellTemplate : ( h , { value }) => `$ ${ value . toFixed ( 2 )} ` }, { prop : ' stock ' , name : ' Stock ' , size : 100 , editor : ' number ' } ]; useEffect (() => { if ( gridRef . current ) { const grid = gridRef . current ; grid . columns = columns ; grid . source = data ; // Handle cell editing grid . addEventListener ( ' beforecellfocus ' , ( e ) => { console . log ( ' Cell focus: ' , e . detail ); }); grid . addEventListener ( ' aftercellfocus ' , ( e ) => { console . log ( ' Cell edited: ' , e . detail ); // Update data state const { row , prop , val } = e . detail ; setData ( prev => prev . map (( item , idx ) => idx === row ? { ... item , [ prop ]: val } : item )); }); } }, [ data ]); return ( < div style = { { height : ' 400px ' , width : ' 100% ' , border : ' 1px solid #ddd ' } } > < RevoGrid ref = { gridRef } /> </ div > ); } export default EditableSpreadsheet ; Enter fullscreen mode Exit fullscreen mode Practical Example / Building Something Real Let's build a comprehensive financial data spreadsheet with formulas, formatting, and advanced features: // src/FinancialSpreadsheet.jsx import React , { useRef , useEffect , useState , useCallback } from ' react ' ; import { RevoGrid } from ' @revolist/revogrid-react ' ; import ' @revolist/revogrid/dist/revogrid.css ' ; function FinancialSpreadsheet () { const gridRef = useRef ( null ); const [ data , setData ] = useState ([]); // Initialize with sample financial data useEffect (() => { const initialData = [ { month : ' January ' , revenue : 50000 , expenses : 30000 , profit : 20000 }, { month : ' February ' , revenue : 55000 , expenses : 32000 , profit : 23000 }, { month : ' March ' , revenue : 60000 , expenses : 35000 , profit : 25000 }, { month : ' April ' , revenue : 58000 , expenses : 33000 , profit : 25000 }, { month : ' May ' , revenue : 62000 , expenses : 36000 , profit : 26000 }, { month : ' June ' , revenue : 65000 , expenses : 38000 , profit : 27000 } ]; setData ( initialData ); }, []); const columns = [ { prop : ' month ' , name : ' Month ' , size : 150 , pinned : ' left ' , readonly : true }, { prop : ' revenue ' , name : ' Revenue ' , size : 150 , editor : ' number ' , cellTemplate : ( h , { value }) => { return h ( ' span ' , { style : { color : ' #28a745 ' , fontWeight : ' bold ' } }, `$ ${ value . toLocaleString ()} ` ); } }, { prop : ' expenses ' , name : ' Expenses ' , size : 150 , editor : ' number ' , cellTemplate : ( h , { value }) => { return h ( ' span ' , { style : { color : ' #dc3545 ' , fontWeight : ' bold ' } }, `$ ${ value . toLocaleString ()} ` ); } }, { prop : ' profit ' , name : ' Profit ' , size : 150 , editor : ' number ' , readonly : true , cellTemplate : ( h , { value }) => { const color = value > 0 ? ' #28a745 ' : ' #dc3545 ' ; return h ( ' span ' , { style : { color , fontWeight : ' bold ' } }, `$ ${ value . toLocaleString ()} ` ); } }, { prop : ' margin ' , name : ' Margin % ' , size : 120 , readonly : true , cellTemplate : ( h , { row }) => { const margin = (( row . profit / row . revenue ) * 100 ). toFixed ( 2 ); const color = parseFloat ( margin ) > 30 ? ' #28a745 ' : parseFloat ( margin ) > 20 ? ' #ffc107 ' : ' #dc3545 ' ; return h ( ' span ' , { style : { color , fontWeight : ' bold ' } }, ` ${ margin } %` ); } } ]; useEffect (() => { if ( gridRef . current && data . length > 0 ) { const grid = gridRef . current ; // Calculate profit automatically when revenue or expenses change const updatedData = data . map ( row => ({ ... row , profit : row . revenue - row . expenses })); grid . columns = columns ; grid . source = updatedData ; // Handle cell editing const handleCellEdit = ( e ) => { const { row , prop , val } = e . detail ; const newData = [... data ]; if ( newData [ row ]) { newData [ row ] = { ... newData [ row ], [ prop ]: parseFloat ( val ) || 0 }; // Recalculate profit newData [ row ]. profit = newData [ row ]. revenue - newData [ row ]. expenses ; setData ( newData ); } }; grid . addEventListener ( ' aftercellfocus ' , handleCellEdit ); return () => { grid . removeEventListener ( ' aftercellfocus ' , handleCellEdit ); }; } }, [ data , columns ]); const handleExport = useCallback (() => { if ( gridRef . current ) { const grid = gridRef . current ; // Export functionality would be implemented here console . log ( ' Exporting data: ' , data ); } }, [ data ]); const handleAddRow = useCallback (() => { setData ( prev => [... prev , { month : `Month ${ prev . length + 1 } ` , revenue : 0 , expenses : 0 , profit : 0 }]); }, []); return ( < div style = { { padding : ' 20px ' } } > < div style = { { marginBottom : ' 20px ' , display : ' flex ' , gap : ' 10px ' } } > < h2 > Financial Data Spreadsheet </ h2 > < button onClick = { handleAddRow } style = { { padding : ' 8px 16px ' , backgroundColor : ' #007bff ' , color : ' white ' , border : ' none ' , borderRadius : ' 4px ' , cursor : ' pointer ' } } > Add Row </ button > < button onClick = { handleExport } style = { { padding : ' 8px 16px ' , backgroundColor : ' #28a745 ' , color : ' white ' , border : ' none ' , borderRadius : ' 4px ' , cursor : ' pointer ' } } > Export </ button > </ div > < div style = { { height : ' 600px ' , width : ' 100% ' , border : ' 1px solid #ddd ' } } > < RevoGrid ref = { gridRef } theme = "material" range = { true } resize = { true } rowHeaders = { true } columnHeaders = { true } /> </ div > </ div > ); } export default FinancialSpreadsheet ; Enter fullscreen mode Exit fullscreen mode This advanced example demonstrates: Automatic formula calculation (profit = revenue - expenses) Custom cell templates with conditional styling Pinned columns (month column stays fixed) Real-time data updates Cell editing with validation Dynamic row addition Export functionality preparation Material theme styling Common Issues / Troubleshooting Grid not rendering : Ensure you've imported the CSS file ( @revolist/revogrid/dist/revogrid.css ). The grid requires explicit height on the container div. Data not displaying : Make sure you're setting both columns and source properties on the grid ref after it mounts. Use useEffect to ensure the ref is available. Cell editing not working : Verify that you've set editor property in column definitions and are handling the aftercellfocus event properly. Performance issues : RevoGrid handles virtualization automatically, but for extremely large datasets (millions of rows), consider implementing data pagination or lazy loading. TypeScript errors : Install type definitions if available, or create your own type declarations for the RevoGrid component and its API. Event listeners not firing : Ensure you're adding event listeners in useEffect and cleaning them up properly to avoid memory leaks. Next Steps Now that you've mastered RevoGrid basics: Explore advanced features like row grouping and aggregation Implement custom cell editors and renderers Add formula support and calculation engine Learn about column resizing and reordering Implement server-side data loading Add export/import functionality (CSV, Excel) Explore theming and customization options Check the official repository: https://github.com/revolist/revogrid Look for part 7 of this series for more advanced topics Summary You've learned how to implement advanced spreadsheet functionality with RevoGrid, including virtual scrolling, custom cell rendering, formula calculations, and real-time data updates. RevoGrid provides excellent performance for large datasets and offers extensive customization options for building enterprise-grade spreadsheet applications. 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 More from Michael Turner Getting Started with ReactGrid in React: Building Your First Spreadsheet # react # webdev # javascript # tutorial Building Interactive Data Tables with React Data Grid # react # webdev # beginners # tutorial Getting Started with MUI X Data Grid in React: Building Your First Data Table # webdev # programming # javascript # beginners 💎 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://reactjs.org/docs/create-a-new-react-app.html | Creating a React App – React React v 19.2 Search ⌘ Ctrl K Learn Reference Community Blog GET STARTED Quick Start Tutorial: Tic-Tac-Toe Thinking in React Installation Creating a React App Build a React App from Scratch Add React to an Existing Project Setup Editor Setup Using TypeScript React Developer Tools React Compiler Introduction Installation Incremental Adoption Debugging and Troubleshooting LEARN REACT Describing the UI Your First Component Importing and Exporting Components Writing Markup with JSX JavaScript in JSX with Curly Braces Passing Props to a Component Conditional Rendering Rendering Lists Keeping Components Pure Your UI as a Tree Adding Interactivity Responding to Events State: A Component's Memory Render and Commit State as a Snapshot Queueing a Series of State Updates Updating Objects in State Updating Arrays in State Managing State Reacting to Input with State Choosing the State Structure Sharing State Between Components Preserving and Resetting State Extracting State Logic into a Reducer Passing Data Deeply with Context Scaling Up with Reducer and Context Escape Hatches Referencing Values with Refs Manipulating the DOM with Refs Synchronizing with Effects You Might Not Need an Effect Lifecycle of Reactive Effects Separating Events from Effects Removing Effect Dependencies Reusing Logic with Custom Hooks Is this page useful? Learn React Installation Creating a React App If you want to build a new app or website with React, we recommend starting with a framework. If your app has constraints not well-served by existing frameworks, you prefer to build your own framework, or you just want to learn the basics of a React app, you can build a React app from scratch . Full-stack frameworks These recommended frameworks support all the features you need to deploy and scale your app in production. They have integrated the latest React features and take advantage of React’s architecture. Note Full-stack frameworks do not require a server. All the frameworks on this page support client-side rendering ( CSR ), single-page apps ( SPA ), and static-site generation ( SSG ). These apps can be deployed to a CDN or static hosting service without a server. Additionally, these frameworks allow you to add server-side rendering on a per-route basis, when it makes sense for your use case. This allows you to start with a client-only app, and if your needs change later, you can opt-in to using server features on individual routes without rewriting your app. See your framework’s documentation for configuring the rendering strategy. Next.js (App Router) Next.js’s App Router is a React framework that takes full advantage of React’s architecture to enable full-stack React apps. Terminal Copy npx create-next-app@latest Next.js is maintained by Vercel . You can deploy a Next.js app to any hosting provider that supports Node.js or Docker containers, or to your own server. Next.js also supports static export which doesn’t require a server. React Router (v7) React Router is the most popular routing library for React and can be paired with Vite to create a full-stack React framework . It emphasizes standard Web APIs and has several ready to deploy templates for various JavaScript runtimes and platforms. To create a new React Router framework project, run: Terminal Copy npx create-react-router@latest React Router is maintained by Shopify . Expo (for native apps) Expo is a React framework that lets you create universal Android, iOS, and web apps with truly native UIs. It provides an SDK for React Native that makes the native parts easier to use. To create a new Expo project, run: Terminal Copy npx create-expo-app@latest If you’re new to Expo, check out the Expo tutorial . Expo is maintained by Expo (the company) . Building apps with Expo is free, and you can submit them to the Google and Apple app stores without restrictions. Expo additionally provides opt-in paid cloud services. Other frameworks There are other up-and-coming frameworks that are working towards our full stack React vision: TanStack Start (Beta) : TanStack Start is a full-stack React framework powered by TanStack Router. It provides a full-document SSR, streaming, server functions, bundling, and more using tools like Nitro and Vite. RedwoodSDK : Redwood is a full stack React framework with lots of pre-installed packages and configuration that makes it easy to build full-stack web applications. Deep Dive Which features make up the React team’s full-stack architecture vision? Show Details Next.js’s App Router bundler fully implements the official React Server Components specification . This lets you mix build-time, server-only, and interactive components in a single React tree. For example, you can write a server-only React component as an async function that reads from a database or from a file. Then you can pass data down from it to your interactive components: // This component runs *only* on the server (or during the build). async function Talks ( { confId } ) { // 1. You're on the server, so you can talk to your data layer. API endpoint not required. const talks = await db . Talks . findAll ( { confId } ) ; // 2. Add any amount of rendering logic. It won't make your JavaScript bundle larger. const videos = talks . map ( talk => talk . video ) ; // 3. Pass the data down to the components that will run in the browser. return < SearchableVideoList videos = { videos } /> ; } Next.js’s App Router also integrates data fetching with Suspense . This lets you specify a loading state (like a skeleton placeholder) for different parts of your user interface directly in your React tree: < Suspense fallback = { < TalksLoading /> } > < Talks confId = { conf . id } /> </ Suspense > Server Components and Suspense are React features rather than Next.js features. However, adopting them at the framework level requires buy-in and non-trivial implementation work. At the moment, the Next.js App Router is the most complete implementation. The React team is working with bundler developers to make these features easier to implement in the next generation of frameworks. Start From Scratch If your app has constraints not well-served by existing frameworks, you prefer to build your own framework, or you just want to learn the basics of a React app, there are other options available for starting a React project from scratch. Starting from scratch gives you more flexibility, but does require that you make choices on which tools to use for routing, data fetching, and other common usage patterns. It’s a lot like building your own framework, instead of using a framework that already exists. The frameworks we recommend have built-in solutions for these problems. If you want to build your own solutions, see our guide to build a React app from Scratch for instructions on how to set up a new React project starting with a build tool like Vite , Parcel , or RSbuild . If you’re a framework author interested in being included on this page, please let us know . Previous Installation Next Build a React App from Scratch Copyright © Meta Platforms, Inc no uwu plz uwu? Logo by @sawaratsuki1004 Learn React Quick Start Installation Describing the UI Adding Interactivity Managing State Escape Hatches API Reference React APIs React DOM APIs Community Code of Conduct Meet the Team Docs Contributors Acknowledgements More Blog React Native Privacy Terms On this page Overview Full-stack frameworks Next.js (App Router) React Router (v7) Expo (for native apps) Other frameworks Start From Scratch | 2026-01-13T08:49:06 |
https://www.youtube.com/creators/ | YouTube Creators - Education & Inspiration for Video Creators Jump to content Welcome, Creators Partner Program How things work Getting started on YouTube Everything you need to create and manage a channel. Building your community Tips & tricks to find, nurture, and build an audience. How to make money on YouTube Explore all ways you can get paid on YouTube. Growing your channel Tools to help you create, connect, and grow. Policies & Guidelines Get the explanations behind the rules. How to get involved How we support, recognize, and celebrate Creators. Top questions Make money while recommending products you love with YouTube Shopping. How it works Everything you need to create on YouTube No matter what kind of information, advice, or help you’re looking for, this is the spot. FEATURED Creators are earning with shopping — join them Learn how to set up YouTube Shopping and start earning. See how it works How things work Getting started on YouTube Everything you need to create and manage a channel. Start creating Building your community Tips & tricks to find, nurture, and build an audience. Grow your audience How to make money on YouTube Explore all ways you can get paid on YouTube. Start earning Growing your channel Tools to help you create, connect, and grow. Reach more viewers How to get involved How we support, recognize, and celebrate Creators. Get involved Policies & Guidelines Get the explanations behind the rules. Get up to speed Top questions Creators have questions and we’ve got answers. We compiled the most common questions we get with answers, plus links to helpful how tos and help center articles. So you can get all the info you need, fast. 01 How do I start creating on YouTube? 02 How do I grow my channel? 03 How do I make edits to my channel? 04 How do I promote my videos? 05 How does the algorithm work? Creator basics: how to set up and customize your channel There are a few ways to get started on YouTube. We offer up different formats and functionalities, giving you the flexibility to create everything from Shorts, which are vertical videos that run 60 seconds or less, to longer form videos. No matter what you’re creating, you’ll need to start by creating a YouTube Channel. First you need to sign into YouTube using a Google Account. Once you’re signed in, click ‘Create Account’, and choose whether it’s for you or for your business. You can then create a YouTube channel on your account, upload videos, leave comments, and create Shorts and playlists. Next, you’ll want to upload your videos! Uploading is easy. You just sign into your YouTube account and then click on the “Create” icon. If you’re planning to upload a longer form video, select “upload video” and then choose your desired video file - you can upload 15 files at a time! If you’d like to upload a YouTube Short , you’ll need to be signed into YouTube mobile, where you’ll tap ‘Create’ and then ‘Create a Short’. From here you can either upload a video from your camera roll or create using our suite of lightweight tools. Help your videos stand out & keep viewers watching Growing your channel is all about creating videos viewers want to watch and accurately presenting them to the audience. When doing so, here’s a few tips to keep in mind. With each video, think carefully about the title, description, and thumbnail you plan to use - these should all accurately reflect your content and let viewers know what they can expect from the video. If you’re a Shorts creator, think about how the first 1-2 seconds of your content can grab viewers scrolling through the video feed! Once you’ve got viewers watching, you can redirect their attention via hashtags, playlists , cards , end screens , and more. Navigating YouTube Studio YouTube Studio is your home base for posting videos and making edits to your channel. To update your channel’s basic info like name, profile picture , and banner, just log in and tap ‘Customisation’ to see your options. You can also make changes to your channel using the Studio Mobile app. You can tap ‘Your Channel’ and then ‘Edit Channel’ to update and edit how your channel looks to your viewers. Note that you can only change your channel’s name three times every 90 days. Read more about managing your channel Promoting your videos Promoting your videos is all about getting the word out there. On YouTube, you can use tools like cards, end screens, Stories, and Community Posts to drive viewers to a specific piece of content! Off-platform, think about promoting your videos on your socials and relevant communities, podcasts, or platforms that align with your content and your intended audience. Read more about promoting your videos How YouTube recommends videos using "the algorithm" Our search and discovery systems are built to find videos that match viewers’ individual interests. We recommend videos based on things such as: what your audience watches and doesn’t watch, how much time they spend watching, what they like and dislike, if they mark a video as ‘not interested’, and on satisfaction surveys. So, rather than trying trying to find a secret code to these systems, focus instead on making videos that you think will resonate with your audience. A great tool here is YouTube Analytics, which provides data that can help you understand how your existing content is performing and provide insights for future videos! 01 How do I start creating on YouTube? Creator basics: how to set up and customize your channel There are a few ways to get started on YouTube. We offer up different formats and functionalities, giving you the flexibility to create everything from Shorts, which are vertical videos that run 60 seconds or less, to longer form videos. No matter what you’re creating, you’ll need to start by creating a YouTube Channel. First you need to sign into YouTube using a Google Account. Once you’re signed in, click ‘Create Account’, and choose whether it’s for you or for your business. You can then create a YouTube channel on your account, upload videos, leave comments, and create Shorts and playlists. Next, you’ll want to upload your videos! Uploading is easy. You just sign into your YouTube account and then click on the “Create” icon. If you’re planning to upload a longer form video, select “upload video” and then choose your desired video file - you can upload 15 files at a time! If you’d like to upload a YouTube Short , you’ll need to be signed into YouTube mobile, where you’ll tap ‘Create’ and then ‘Create a Short’. From here you can either upload a video from your camera roll or create using our suite of lightweight tools. 02 How do I grow my channel? Help your videos stand out & keep viewers watching Growing your channel is all about creating videos viewers want to watch and accurately presenting them to the audience. When doing so, here’s a few tips to keep in mind. With each video, think carefully about the title, description, and thumbnail you plan to use - these should all accurately reflect your content and let viewers know what they can expect from the video. If you’re a Shorts creator, think about how the first 1-2 seconds of your content can grab viewers scrolling through the video feed! Once you’ve got viewers watching, you can redirect their attention via hashtags, playlists , cards , end screens , and more. 03 How do I make edits to my channel? Navigating YouTube Studio YouTube Studio is your home base for posting videos and making edits to your channel. To update your channel’s basic info like name, profile picture , and banner, just log in and tap ‘Customisation’ to see your options. You can also make changes to your channel using the Studio Mobile app. You can tap ‘Your Channel’ and then ‘Edit Channel’ to update and edit how your channel looks to your viewers. Note that you can only change your channel’s name three times every 90 days. Read more about managing your channel 04 How do I promote my videos? Promoting your videos Promoting your videos is all about getting the word out there. On YouTube, you can use tools like cards, end screens, Stories, and Community Posts to drive viewers to a specific piece of content! Off-platform, think about promoting your videos on your socials and relevant communities, podcasts, or platforms that align with your content and your intended audience. Read more about promoting your videos 05 How does the algorithm work? How YouTube recommends videos using "the algorithm" Our search and discovery systems are built to find videos that match viewers’ individual interests. We recommend videos based on things such as: what your audience watches and doesn’t watch, how much time they spend watching, what they like and dislike, if they mark a video as ‘not interested’, and on satisfaction surveys. So, rather than trying trying to find a secret code to these systems, focus instead on making videos that you think will resonate with your audience. A great tool here is YouTube Analytics, which provides data that can help you understand how your existing content is performing and provide insights for future videos! See all questions Resources Learn From getting started to improving your channel’s performance, these resources help you continue to learn and grow. Updates, news, and education from experts and Creators. YouTube Creators Channel Support If you have a problem, we’re here to help you solve it. Fix upload problems, troubleshoot account issues, and more. Get the breakdown on topics most important to Creators. Help Center The place to ask questions and provide feedback. Community Forum Connect Ask questions, find answers, and understand more about YouTube via our social channels and email. The latest tools, tips, and inspiration for Creators like you. @YouTubeCreators Real-time answers. Available in: English, Español, Português, Deutsch, Français, Pусский, 日本語, and Bahasa Indonesia. @TeamYouTube Get the latest information and resources in your inbox. YouTube Emails | 2026-01-13T08:49:06 |
https://forem.com/sagarparmarr#main-content | Sagar - 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 DEV Community Close Follow User actions Sagar 404 bio not found Joined Joined on Mar 28, 2024 github website More info about @sagarparmarr Badges 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 Post 1 post published Comment 0 comments written Tag 0 tags followed GenX: From Childhood Flipbooks to Premium Scroll Animation Sagar Sagar Sagar Follow Jan 13 GenX: From Childhood Flipbooks to Premium Scroll Animation # webdev # performance # animation Comments Add Comment 5 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 — Your community HQ 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 . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/rajeshroyal | Rajesh Royal - 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 Rajesh Royal I love what I do. Location India Joined Joined on Mar 27, 2020 Personal website https://x.com/Raj_896 github website Education Masters In Computer Science Pronouns he Work Full Stack Engineer at Programmers.io 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 Frontend Challenge Completion Badge Awarded for completing at least one prompt in a Frontend Challenge. Thank you for participating! 💖 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 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 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 4 Week Community Wellness Streak Keep contributing to discussions by posting at least 2 comments per week for 4 straight weeks. Unlock the 8 Week Badge next. Got it Close 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 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 8 Week Writing Streak The streak continues! You've written at least one post per week for 8 consecutive weeks. Unlock the 16-week badge next! Got it Close 4 Week Writing Streak You've posted at least one post per week for 4 consecutive weeks! Got it Close More info about @rajeshroyal Organizations Vanilacodes GitHub Repositories liquid-button A repository which helps you in creating react-liquid-button JavaScript • 4 stars hackina Hackina A game of code | College Tech festival Hacking/Treasure Hunt in computer code Competition VBA • 1 star fees-management-system Student fees management system VB .NET 4 stars Broprint.js The world's easiest, smallest and powerful visitor identifier for browsers. TypeScript • 572 stars CommitKing CommitKings is a web application that allows users to rate GitHub profiles and repositories as "Hotty" (🔥) or "Notty" (🧊), inspired by the "Hot or Not" concept. TypeScript • 3 stars netflix-frontend-clone Video streaming website Netflix Frontend clone, Built with Pure CSS3 using Flexbox, JS dependencies: OwlCarousel and JQuery JavaScript • 63 stars react-liquid-button Liquid Button is a React component made to spice up your web creation. The component is enhanced with customization options as props, to make it easy for you to get exactly what you need JavaScript • 2 stars vThumb.js This package will generate n numbers of thumbnails at different positions in a given video file. TypeScript • 74 stars wordlEther Yet another wordle clone but with Decentralized this time. Your win score will be a blockchain entry with Ropsten test network. Fork TypeScript • 2 stars ML-model-article-share-prediction CSS • 1 star Codeigniter-bootstrap-dashboard PHP • 4 stars AccidentPredictor An accurate traffic accident predictor can potentially save lives. I hereby described the creation and deployment of such a model using scikit-learn, Google Maps API, Flask and PythonAnywhere. Fork rajesh-royal.github.io Portfolio created with React JS HTML • 4 stars catepedia Catepedia | The Ultimate Guide to Cat Breeds. A cat breed search Nuxt app. Vue • 2 stars whatsapp-analyzer Analyze the whatsapp exported chat TypeScript • 1 star Skills/Languages HTML5, CSS3, ES6, PHP, CI, REST API, GraphQl NODE JS, REACT JS, VUE3.JS, NEXT.JS, NUXT.JS, EXPRESS.JS, NST.JS, TAILWIND CSS, BOOTSTRAP, BULMA, ADOBE XD, FIGMA, BLOCKCHAIN. Currently learning Nuxt.js, Vue3.js, prompt engineering, and node.js scripting, react native. Currently hacking on https://commitking.app/ Available for React Js, Node.js, Vue.js, WP development, Programming or development challenge, Work opportunity, Feedback Post 83 posts published Comment 175 comments written Tag 11 tags followed Pin Pinned Generate video thumbnails in ReactJS, an open source thumbnail library. Rajesh Royal Rajesh Royal Rajesh Royal Follow Mar 27 '22 Generate video thumbnails in ReactJS, an open source thumbnail library. # javascript # react # tutorial # productivity 50 reactions Comments 4 comments 4 min read Get Funky on the Console - Level Up humour😅 Rajesh Royal Rajesh Royal Rajesh Royal Follow Feb 15 '22 Get Funky on the Console - Level Up humour😅 # javascript # programming # fun # react 33 reactions Comments Add Comment 2 min read Handle multiple environments in ReactJs [dev, stag, prod] Rajesh Royal Rajesh Royal Rajesh Royal Follow Feb 10 '22 Handle multiple environments in ReactJs [dev, stag, prod] # react # tutorial # codenewbie # javascript 41 reactions Comments 4 comments 2 min read Change Cursor Style and Animation in VS Code Rajesh Royal Rajesh Royal Rajesh Royal Follow Sep 5 '20 Change Cursor Style and Animation in VS Code # vscode # javascript # style # vscodesettings 54 reactions Comments 7 comments 1 min read Page Not Found Error on Netlify Reactjs React Router solved Rajesh Royal Rajesh Royal Rajesh Royal Follow Jul 14 '20 Page Not Found Error on Netlify Reactjs React Router solved # react # reactrouter # javascript # netlify 221 reactions Comments 72 comments 3 min read The `/context` Command: X-Ray Vision for Your Tokens Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 12 The `/context` Command: X-Ray Vision for Your Tokens # tutorial # claudecode # productivity # beginners Comments Add Comment 4 min read Want to connect with Rajesh Royal? Create an account to connect with Rajesh Royal. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in 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 Vim Mode: Edit Prompts at the Speed of Thought Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 10 Vim Mode: Edit Prompts at the Speed of Thought # tutorial # claudecode # productivity # beginners Comments Add Comment 4 min read The `#` Prefix: Claude's Memory Feature (And Why You Don't Need It Anymore) Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 9 The `#` Prefix: Claude's Memory Feature (And Why You Don't Need It Anymore) # tutorial # claudecode # productivity # beginners 1 reaction Comments Add Comment 5 min read Never Lose Your Work: Session Management That Saves Your Sanity Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 8 Never Lose Your Work: Session Management That Saves Your Sanity # tutorial # claudecode # productivity # beginners 4 reactions Comments 3 comments 5 min read Extended Thinking: How to Make Claude Actually Think Before It Answers Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 7 Extended Thinking: How to Make Claude Actually Think Before It Answers # tutorial # claudecode # productivity # beginners 2 reactions Comments Add Comment 5 min read Your Time Machine for Code: Double Esc to Rewind When Things Go Wrong Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 6 Your Time Machine for Code: Double Esc to Rewind When Things Go Wrong # tutorial # claudecode # productivity # beginners Comments 1 comment 4 min read Stop Wasting Tokens: The `!` Prefix That Every Claude Code User Needs to Know Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 6 Stop Wasting Tokens: The `!` Prefix That Every Claude Code User Needs to Know # tutorial # claudecode # productivity # beginners 3 reactions Comments 2 comments 4 min read The Paradox of Slow Coding: Why Rushing Kills Your Progress (And What to Do Instead) Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 1 The Paradox of Slow Coding: Why Rushing Kills Your Progress (And What to Do Instead) # programming # productivity # codenewbie # webdev 5 reactions Comments Add Comment 6 min read Mastering Sui DeepBook: A Hands-On DeFi DEX Series (3) Rajesh Royal Rajesh Royal Rajesh Royal Follow Dec 18 '25 Mastering Sui DeepBook: A Hands-On DeFi DEX Series (3) # tutorial # sui # blockchain # web3 5 reactions Comments Add Comment 5 min read Mastering Sui DeepBook: A Hands-On DeFi DEX Series (2) Rajesh Royal Rajesh Royal Rajesh Royal Follow Dec 14 '25 Mastering Sui DeepBook: A Hands-On DeFi DEX Series (2) # sui # blockchain # web3 # tutorial 1 reaction Comments Add Comment 3 min read Mastering Sui DeepBook: A Hands-On DeFi DEX Series (1) Rajesh Royal Rajesh Royal Rajesh Royal Follow Dec 14 '25 Mastering Sui DeepBook: A Hands-On DeFi DEX Series (1) # blockchain # javascript # tutorial # sui 1 reaction Comments Add Comment 2 min read 5 Things You Need to Know to Make Money with AI (Without the BS) Rajesh Royal Rajesh Royal Rajesh Royal Follow Dec 13 '25 5 Things You Need to Know to Make Money with AI (Without the BS) # ai # webdev # productivity # career 7 reactions Comments Add Comment 3 min read Practical use of the event.stopPropagation React MUI Data Grid: Allowing Arrow Key Navigation for Input Fields Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 31 '25 Practical use of the event.stopPropagation React MUI Data Grid: Allowing Arrow Key Navigation for Input Fields # javascript # react # a11y # mui 10 reactions Comments 2 comments 3 min read Unlocking WhatsApp Secrets: Analyzing Chat Data with Next.js 14 Web App Rajesh Royal Rajesh Royal Rajesh Royal Follow Sep 1 '24 Unlocking WhatsApp Secrets: Analyzing Chat Data with Next.js 14 Web App # javascript # nextjs # prisma # react 9 reactions Comments Add Comment 3 min read Introducing Catepedia: A Nuxt 3 Cat Breed Search App Rajesh Royal Rajesh Royal Rajesh Royal Follow Apr 8 '24 Introducing Catepedia: A Nuxt 3 Cat Breed Search App # javascript # nuxt # beginners # webdev 7 reactions Comments Add Comment 3 min read Geolocation Web API - explained in less than 256 chars Rajesh Royal Rajesh Royal Rajesh Royal Follow Mar 28 '24 Geolocation Web API - explained in less than 256 chars # frontendchallenge # devchallenge # javascript # webdev 19 reactions Comments 1 comment 1 min read How to view server logs in real-time in VS Code Rajesh Royal Rajesh Royal Rajesh Royal Follow Mar 11 '24 How to view server logs in real-time in VS Code # javascript # productivity # devtools # vscode 43 reactions Comments 6 comments 2 min read 100 Tips from The Pragmatic Programmers Book: Part 10/10 Rajesh Royal Rajesh Royal Rajesh Royal Follow Feb 2 '24 100 Tips from The Pragmatic Programmers Book: Part 10/10 # career # thepragmaticprogrammer # books # programming 8 reactions Comments 3 comments 2 min read 100 Tips from The Pragmatic Programmers Book: Part 8/10 Rajesh Royal Rajesh Royal Rajesh Royal Follow Feb 1 '24 100 Tips from The Pragmatic Programmers Book: Part 8/10 # career # thepragmaticprogrammer # books # programming 8 reactions Comments Add Comment 1 min read 100 Tips from The Pragmatic Programmers Book: Part 9/10 Rajesh Royal Rajesh Royal Rajesh Royal Follow Feb 1 '24 100 Tips from The Pragmatic Programmers Book: Part 9/10 # career # thepragmaticprogrammer # books # programming 7 reactions Comments Add Comment 2 min read 100 Tips from The Pragmatic Programmers Book: Part 7/10 Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 31 '24 100 Tips from The Pragmatic Programmers Book: Part 7/10 # career # thepragmaticprogrammer # books # programming 11 reactions Comments Add Comment 1 min read 100 Tips from The Pragmatic Programmers Book: Part 6/10 Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 30 '24 100 Tips from The Pragmatic Programmers Book: Part 6/10 # career # thepragmaticprogrammer # books # programming 9 reactions Comments Add Comment 1 min read 100 Tips from The Pragmatic Programmers Book: Part 5/10 Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 29 '24 100 Tips from The Pragmatic Programmers Book: Part 5/10 # career # thepragmaticprogrammer # books # programming 8 reactions Comments Add Comment 1 min read 100 Tips from The Pragmatic Programmers Book: Part 4/10 Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 28 '24 100 Tips from The Pragmatic Programmers Book: Part 4/10 # career # thepragmaticprogrammer # books # programming 30 reactions Comments 9 comments 1 min read 100 Tips from The Pragmatic Programmers Book: Part 3/10 Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 27 '24 100 Tips from The Pragmatic Programmers Book: Part 3/10 # career # thepragmaticprogrammer # books # programming 14 reactions Comments Add Comment 1 min read 100 Tips from The Pragmatic Programmers Book: Part 2/10 Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 27 '24 100 Tips from The Pragmatic Programmers Book: Part 2/10 # career # thepragmaticprogrammer # books # programming 14 reactions Comments Add Comment 2 min read 100 Tips from The Pragmatic Programmers Book: Part 1/10 Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 27 '24 100 Tips from The Pragmatic Programmers Book: Part 1/10 # career # thepragmaticprogrammer # books # programming 31 reactions Comments 1 comment 2 min read Baby steps to instantly improve your React project Rajesh Royal Rajesh Royal Rajesh Royal Follow Sep 13 '23 Baby steps to instantly improve your React project # javascript # react # beginners 41 reactions Comments 6 comments 2 min read Compress and serve big JSON dataset files in JavaScript like never before Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 28 '23 Compress and serve big JSON dataset files in JavaScript like never before # gratitude # writing 18 reactions Comments 14 comments 3 min read React.js - Interview Question - duplicate hashtag remover. Rajesh Royal Rajesh Royal Rajesh Royal Follow Aug 12 '22 React.js - Interview Question - duplicate hashtag remover. # discuss # javascript # react # programming 31 reactions Comments 9 comments 1 min read As a Interviewer what question you ask a dev while taking interview for react.js? Rajesh Royal Rajesh Royal Rajesh Royal Follow Jul 28 '22 As a Interviewer what question you ask a dev while taking interview for react.js? # help # discuss # react # javascript 23 reactions Comments 7 comments 1 min read React.js Interview - technical submission and detailed feedback Rajesh Royal Rajesh Royal Rajesh Royal Follow Jul 25 '22 React.js Interview - technical submission and detailed feedback # help # javascript # react # typescript 257 reactions Comments 34 comments 3 min read Interview experience at Google - SDE II Rajesh Royal Rajesh Royal Rajesh Royal Follow Jun 19 '22 Interview experience at Google - SDE II # discuss # javascript # google # interviewexperience 50 reactions Comments 8 comments 3 min read Sum of All Odd Length Subarrays O(N) Leetcode #1588. Rajesh Royal Rajesh Royal Rajesh Royal Follow Jun 9 '22 Sum of All Odd Length Subarrays O(N) Leetcode #1588. # discuss # javascript # programming # beginners 16 reactions Comments 2 comments 2 min read #1470 Crazy mathematics. Shuffle the Array in place O(1); Rajesh Royal Rajesh Royal Rajesh Royal Follow Jun 3 '22 #1470 Crazy mathematics. Shuffle the Array in place O(1); # showdev # javascript # programming # codenewbie 10 reactions Comments 4 comments 2 min read Find all substring of a given string in O(n^2) time. Rajesh Royal Rajesh Royal Rajesh Royal Follow May 29 '22 Find all substring of a given string in O(n^2) time. # help # javascript # programming # beginners 20 reactions Comments 3 comments 1 min read What is the use of Proxy and Reflect in JavaScript? Rajesh Royal Rajesh Royal Rajesh Royal Follow May 26 '22 What is the use of Proxy and Reflect in JavaScript? # help # javascript # programming # codenewbie 33 reactions Comments 18 comments 1 min read How to use async/await inside for loop in JavaScript Rajesh Royal Rajesh Royal Rajesh Royal Follow May 24 '22 How to use async/await inside for loop in JavaScript # javascript # webdev # tutorial # programming 14 reactions Comments Add Comment 1 min read Implement binary search tree in JavaScript - simplest possible. Rajesh Royal Rajesh Royal Rajesh Royal Follow May 20 '22 Implement binary search tree in JavaScript - simplest possible. # javascript # webdev # tutorial # binarytree 14 reactions Comments Add Comment 2 min read Cache API in JavaScript - with just 20 lines of code. Rajesh Royal Rajesh Royal Rajesh Royal Follow May 15 '22 Cache API in JavaScript - with just 20 lines of code. # cache # javascript # webdev # tutorial 288 reactions Comments 24 comments 1 min read A small alternative of fingerprint.js, Broprint.js Rajesh Royal Rajesh Royal Rajesh Royal Follow Apr 20 '22 A small alternative of fingerprint.js, Broprint.js # news # npm # javascript # react 23 reactions Comments 3 comments 1 min read How to add delay between CSS keyframe animation ⚓ Rajesh Royal Rajesh Royal Rajesh Royal Follow Mar 16 '22 How to add delay between CSS keyframe animation ⚓ # showdev # css # webdev # tutorial 11 reactions Comments 1 comment 1 min read Web Console Helpers make dev life bit easier 🐥 Rajesh Royal Rajesh Royal Rajesh Royal Follow Feb 8 '22 Web Console Helpers make dev life bit easier 🐥 # javascript # beginners # webdev # productivity 9 reactions Comments 1 comment 1 min read The simplest drag and drop feature with html and JavaScript - 16 lines Rajesh Royal Rajesh Royal Rajesh Royal Follow Feb 5 '22 The simplest drag and drop feature with html and JavaScript - 16 lines # javascript # html # beginners # tutorial 8 reactions Comments Add Comment 1 min read ReactJS - Adding a environment file to ReactJS project Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 31 '22 ReactJS - Adding a environment file to ReactJS project # react # javascript # beginners # tutorial 26 reactions Comments Add Comment 2 min read ReactJS - Disable console.log() in production and staging Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 30 '22 ReactJS - Disable console.log() in production and staging # react # javascript # beginners # tutorial 21 reactions Comments 12 comments 1 min read How to make a custom Debounce hook in react js Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 24 '22 How to make a custom Debounce hook in react js # react # javascript # beginners # tutorial 45 reactions Comments 5 comments 1 min read Update an object in nested array in MongoDB Rajesh Royal Rajesh Royal Rajesh Royal Follow Sep 28 '21 Update an object in nested array in MongoDB # mongodb # database # javascript # node 20 reactions Comments 6 comments 2 min read Some useful custom utility🛠 functions for cookie handling in javascript Rajesh Royal Rajesh Royal Rajesh Royal Follow Sep 9 '21 Some useful custom utility🛠 functions for cookie handling in javascript # javascript # tooling # cookies # react 11 reactions Comments Add Comment 1 min read Frontend challenge - Car bidders dashboard. Rajesh Royal Rajesh Royal Rajesh Royal Follow Jun 1 '21 Frontend challenge - Car bidders dashboard. # javascript # react # tailwindcss 7 reactions Comments 2 comments 1 min read How to populate nested document in MongoDB. Rajesh Royal Rajesh Royal Rajesh Royal Follow May 19 '21 How to populate nested document in MongoDB. # mongodb # node # javascript # beginners 17 reactions Comments 2 comments 1 min read Frontend interview - Questions I was asked Rajesh Royal Rajesh Royal Rajesh Royal Follow May 10 '21 Frontend interview - Questions I was asked # interview # javascript # frontend # questions 36 reactions Comments 11 comments 1 min read Frontend Development resources zero to Hero. Rajesh Royal Rajesh Royal Rajesh Royal Follow Jan 18 '21 Frontend Development resources zero to Hero. # html # frontend # development # guide 12 reactions Comments 1 comment 2 min read 𝗛𝗼𝘄 𝘁𝗼 𝗮𝗰𝗰𝗲𝗽𝘁 𝗺𝘂𝗹𝘁𝗶𝗽𝗹𝗲 𝗟𝗶𝗻𝗸𝗲𝗱𝗶𝗻 𝗜𝗻𝘃𝗶𝘁𝗮𝘁𝗶𝗼𝗻𝘀 at once❓ Rajesh Royal Rajesh Royal Rajesh Royal Follow Nov 17 '20 𝗛𝗼𝘄 𝘁𝗼 𝗮𝗰𝗰𝗲𝗽𝘁 𝗺𝘂𝗹𝘁𝗶𝗽𝗹𝗲 𝗟𝗶𝗻𝗸𝗲𝗱𝗶𝗻 𝗜𝗻𝘃𝗶𝘁𝗮𝘁𝗶𝗼𝗻𝘀 at once❓ # lifehacks # linkedin # programming # happyhacking 6 reactions Comments Add Comment 1 min read Sharing my experiences with cancer in the workplace Rajesh Royal Rajesh Royal Rajesh Royal Follow Oct 15 '20 Sharing my experiences with cancer in the workplace # workplace # cancer # experiences # apple 7 reactions Comments 1 comment 2 min read 1 reason for choosing next.js over gatsby Rajesh Royal Rajesh Royal Rajesh Royal Follow Oct 14 '20 1 reason for choosing next.js over gatsby # gatsby # nextjs # javascript # webdev 5 reactions Comments 3 comments 1 min read How to solve low disk space issue in windows. Rajesh Royal Rajesh Royal Rajesh Royal Follow Oct 8 '20 How to solve low disk space issue in windows. # windows # tutorial # webdev # disk 3 reactions Comments Add Comment 1 min read the-tech-tools-I-use-as-frontend-engineer Rajesh Royal Rajesh Royal Rajesh Royal Follow Oct 5 '20 the-tech-tools-I-use-as-frontend-engineer # javascript # react # gatsby # vscode 8 reactions Comments 1 comment 3 min read Migration to Gatsby v2 - Variable "$slug" of required type "String!" was not provided Rajesh Royal Rajesh Royal Rajesh Royal Follow Oct 2 '20 Migration to Gatsby v2 - Variable "$slug" of required type "String!" was not provided # gatsby # graphql # javascript # react 6 reactions 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://twitter.com/intent/tweet?text=%22Accessibility%20Testing%20on%20Windows%20on%20Mac%22%20by%20Tatyana%20Bayramova%2C%20CPACC%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Ftatyanabayramova%2Faccessibility-testing-on-windows-on-mac-48e4 | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:06 |
https://twitter.com/intent/tweet?text=%22%F0%9F%A9%BA%20How%20I%20Troubleshoot%20an%20EC2%20Instance%20in%20the%20Real%20World%20%28Using%20Instance%20Diagnostics%29%22%20by%20Venkata%20Pavan%20Vishnu%20Rachapudi%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Faws-builders%2Fhow-i-troubleshoot-an-ec2-instance-in-the-real-world-using-instance-diagnostics-3dk8 | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:06 |
https://twitter.com/intent/tweet?text=%22Weather%20Service%20Project%20%28Part%202%29%3A%20Building%20the%20Interactive%20Frontend%20with%20GitHub%20Pages%20or%20Netlify%20and%20JavaScript%22%20by%20%40datalaria%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fdatalaria%2Fweather-service-project-part-2-building-the-interactive-frontend-with-github-pages-or-netlify-ho1 | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/privacy#10-childrens-information | 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://twitter.com/thepsf | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/anthonymax/were-launching-on-producthunt-3i43#comments | We're launching on ProductHunt - 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 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 Anthony Max Posted on Dec 28, 2025 We're launching on ProductHunt # javascript # news # showdev Hi everyone! 📢 Today is a very important day for us. We've launched on ProductHunt! If you don't mind, you can support us by following this link with your Upvote. Thank you! producthunt.com 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 Anthony Max Follow 🐜 Fetch API enjoyer | collab: aanthonymaxgithub@gmail.com Education Unfinished bachelor's degree Pronouns Anthony or Tony Work HMPL.js Joined Sep 20, 2024 More from Anthony Max https://hmpl-lang.dev - new website # programming # showdev # webdev A new example of using the template language: https://codesandbox.io/p/sandbox/basic-hmpl-example-dxlgfg # showcase # javascript # hmpldom # beginners Great news today: we've finally launched a section featuring community projects built with hmpl-js. https://github.com/hmpl-language/projects # javascript # news # showcase # opensource 💎 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/engineering/#site-map | 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://peps.python.org/pep-0287/ | PEP 287 – reStructuredText Docstring Format | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 287 Toggle light / dark / auto colour theme PEP 287 – reStructuredText Docstring Format Author : David Goodger <goodger at python.org> Discussions-To : Doc-SIG list Status : Active Type : Informational Created : 25-Mar-2002 Post-History : 02-Apr-2002 Replaces : 216 Table of Contents Abstract Benefits Goals Rationale Specification Docstring-Significant Features Questions & Answers Copyright Acknowledgements Abstract When plaintext hasn’t been expressive enough for inline documentation, Python programmers have sought out a format for docstrings. This PEP proposes that the reStructuredText markup be adopted as a standard markup format for structured plaintext documentation in Python docstrings, and for PEPs and ancillary documents as well. reStructuredText is a rich and extensible yet easy-to-read, what-you-see-is-what-you-get plaintext markup syntax. Only the low-level syntax of docstrings is addressed here. This PEP is not concerned with docstring semantics or processing at all (see PEP 256 for a “Road Map to the Docstring PEPs”). Nor is it an attempt to deprecate pure plaintext docstrings, which are always going to be legitimate. The reStructuredText markup is an alternative for those who want more expressive docstrings. Benefits Programmers are by nature a lazy breed. We reuse code with functions, classes, modules, and subsystems. Through its docstring syntax, Python allows us to document our code from within. The “holy grail” of the Python Documentation Special Interest Group ( Doc-SIG ) has been a markup syntax and toolset to allow auto-documentation, where the docstrings of Python systems can be extracted in context and processed into useful, high-quality documentation for multiple purposes. Document markup languages have three groups of customers: the authors who write the documents, the software systems that process the data, and the readers, who are the final consumers and the most important group. Most markups are designed for the authors and software systems; readers are only meant to see the processed form, either on paper or via browser software. ReStructuredText is different: it is intended to be easily readable in source form, without prior knowledge of the markup. ReStructuredText is entirely readable in plaintext format, and many of the markup forms match common usage (e.g., *emphasis* ), so it reads quite naturally. Yet it is rich enough to produce complex documents, and extensible so that there are few limits. Of course, to write reStructuredText documents some prior knowledge is required. The markup offers functionality and expressivity, while maintaining easy readability in the source text. The processed form (HTML etc.) makes it all accessible to readers: inline live hyperlinks; live links to and from footnotes; automatic tables of contents (with live links!); tables; images for diagrams etc.; pleasant, readable styled text. The reStructuredText parser is available now, part of the Docutils project. Standalone reStructuredText documents and PEPs can be converted to HTML; other output format writers are being worked on and will become available over time. Work is progressing on a Python source “Reader” which will implement auto-documentation from docstrings. Authors of existing auto-documentation tools are encouraged to integrate the reStructuredText parser into their projects, or better yet, to join forces to produce a world-class toolset for the Python standard library. Tools will become available in the near future, which will allow programmers to generate HTML for online help, XML for multiple purposes, and eventually PDF, DocBook, and LaTeX for printed documentation, essentially “for free” from the existing docstrings. The adoption of a standard will, at the very least, benefit docstring processing tools by preventing further “reinventing the wheel”. Eventually PyDoc, the one existing standard auto-documentation tool, could have reStructuredText support added. In the interim it will have no problem with reStructuredText markup, since it treats all docstrings as preformatted plaintext. Goals These are the generally accepted goals for a docstring format, as discussed in the Doc-SIG: It must be readable in source form by the casual observer. It must be easy to type with any standard text editor. It must not need to contain information which can be deduced from parsing the module. It must contain sufficient information (structure) so it can be converted to any reasonable markup format. It must be possible to write a module’s entire documentation in docstrings, without feeling hampered by the markup language. reStructuredText meets and exceeds all of these goals, and sets its own goals as well, even more stringent. See Docstring-Significant Features below. The goals of this PEP are as follows: To establish reStructuredText as a standard structured plaintext format for docstrings (inline documentation of Python modules and packages), PEPs, README-type files and other standalone documents. “Accepted” status will be sought through Python community consensus and eventual BDFL pronouncement. Please note that reStructuredText is being proposed as a standard, not the only standard. Its use will be entirely optional. Those who don’t want to use it need not. To solicit and address any related concerns raised by the Python community. To encourage community support. As long as multiple competing markups are out there, the development community remains fractured. Once a standard exists, people will start to use it, and momentum will inevitably gather. To consolidate efforts from related auto-documentation projects. It is hoped that interested developers will join forces and work on a joint/merged/common implementation. Once reStructuredText is a Python standard, effort can be focused on tools instead of arguing for a standard. Python needs a standard set of documentation tools. With regard to PEPs, one or both of the following strategies may be applied: Keep the existing PEP section structure constructs (one-line section headers, indented body text). Subsections can either be forbidden, or supported with reStructuredText-style underlined headers in the indented body text. Replace the PEP section structure constructs with the reStructuredText syntax. Section headers will require underlines, subsections will be supported out of the box, and body text need not be indented (except for block quotes). Strategy (b) is recommended, and its implementation is complete. Support for RFC 2822 headers has been added to the reStructuredText parser for PEPs (unambiguous given a specific context: the first contiguous block of the document). It may be desired to concretely specify what over/underline styles are allowed for PEP section headers, for uniformity. Rationale The lack of a standard syntax for docstrings has hampered the development of standard tools for extracting and converting docstrings into documentation in standard formats (e.g., HTML, DocBook, TeX). There have been a number of proposed markup formats and variations, and many tools tied to these proposals, but without a standard docstring format they have failed to gain a strong following and/or floundered half-finished. Throughout the existence of the Doc-SIG, consensus on a single standard docstring format has never been reached. A lightweight, implicit markup has been sought, for the following reasons (among others): Docstrings written within Python code are available from within the interactive interpreter, and can be “print”ed. Thus the use of plaintext for easy readability. Programmers want to add structure to their docstrings, without sacrificing raw docstring readability. Unadorned plaintext cannot be transformed (“up-translated”) into useful structured formats. Explicit markup (like XML or TeX) is widely considered unreadable by the uninitiated. Implicit markup is aesthetically compatible with the clean and minimalist Python syntax. Many alternative markups for docstrings have been proposed on the Doc-SIG over the years; a representative sample is listed below. Each is briefly analyzed in terms of the goals stated above. Please note that this is not intended to be an exclusive list of all existing markup systems; there are many other markups (Texinfo, Doxygen, TIM, YODL, AFT, …) which are not mentioned. XML , SGML , DocBook , HTML , XHTML XML and SGML are explicit, well-formed meta-languages suitable for all kinds of documentation. XML is a variant of SGML. They are best used behind the scenes, because to untrained eyes they are verbose, difficult to type, and too cluttered to read comfortably as source. DocBook, HTML, and XHTML are all applications of SGML and/or XML, and all share the same basic syntax and the same shortcomings. TeX TeX is similar to XML/SGML in that it’s explicit, but not very easy to write, and not easy for the uninitiated to read. Perl POD Most Perl modules are documented in a format called POD (Plain Old Documentation). This is an easy-to-type, very low level format with strong integration with the Perl parser. Many tools exist to turn POD documentation into other formats: info, HTML and man pages, among others. However, the POD syntax takes after Perl itself in terms of readability. JavaDoc Special comments before Java classes and functions serve to document the code. A program to extract these, and turn them into HTML documentation is called javadoc, and is part of the standard Java distribution. However, JavaDoc has a very intimate relationship with HTML, using HTML tags for most markup. Thus it shares the readability problems of HTML. Setext , StructuredText Early on, variants of Setext (Structure Enhanced Text), including Zope Corp’s StructuredText, were proposed for Python docstring formatting. Hereafter these variants will collectively be called “STexts”. STexts have the advantage of being easy to read without special knowledge, and relatively easy to write. Although used by some (including in most existing Python auto-documentation tools), until now STexts have failed to become standard because: STexts have been incomplete. Lacking “essential” constructs that people want to use in their docstrings, STexts are rendered less than ideal. Note that these “essential” constructs are not universal; everyone has their own requirements. STexts have been sometimes surprising. Bits of text are unexpectedly interpreted as being marked up, leading to user frustration. SText implementations have been buggy. Most STexts have no formal specification except for the implementation itself. A buggy implementation meant a buggy spec, and vice-versa. There has been no mechanism to get around the SText markup rules when a markup character is used in a non-markup context. In other words, no way to escape markup. Proponents of implicit STexts have vigorously opposed proposals for explicit markup (XML, HTML, TeX, POD, etc.), and the debates have continued off and on since 1996 or earlier. reStructuredText is a complete revision and reinterpretation of the SText idea, addressing all of the problems listed above. Specification The specification and user documentation for reStructuredText is quite extensive. Rather than repeating or summarizing it all here, links to the originals are provided. Please first take a look at A ReStructuredText Primer , a short and gentle introduction. The Quick reStructuredText user reference quickly summarizes all of the markup constructs. For complete and extensive details, please refer to the following documents: An Introduction to reStructuredText reStructuredText Markup Specification reStructuredText Directives In addition, Problems With StructuredText explains many markup decisions made with regards to StructuredText, and A Record of reStructuredText Syntax Alternatives records markup decisions made independently. Docstring-Significant Features A markup escaping mechanism. Backslashes ( \ ) are used to escape markup characters when needed for non-markup purposes. However, the inline markup recognition rules have been constructed in order to minimize the need for backslash-escapes. For example, although asterisks are used for emphasis , in non-markup contexts such as “*” or “(*)” or “x * y”, the asterisks are not interpreted as markup and are left unchanged. For many non-markup uses of backslashes (e.g., describing regular expressions), inline literals or literal blocks are applicable; see the next item. Markup to include Python source code and Python interactive sessions: inline literals, literal blocks, and doctest blocks. Inline literals use double-backquotes to indicate program I/O or code snippets. No markup interpretation (including backslash-escape [ \ ] interpretation) is done within inline literals. Literal blocks (block-level literal text, such as code excerpts or ASCII graphics) are indented, and indicated with a double-colon (“::”) at the end of the preceding paragraph (right here –>): if literal_block : text = 'is left as-is' spaces_and_linebreaks = 'are preserved' markup_processing = None Doctest blocks begin with “>>> “ and end with a blank line. Neither indentation nor literal block double-colons are required. For example: Here 's a doctest block: >>> print 'Python-specific usage examples; begun with ">>>"' Python - specific usage examples ; begun with ">>>" >>> print '(cut and pasted from interactive sessions)' ( cut and pasted from interactive sessions ) Markup that isolates a Python identifier: interpreted text. Text enclosed in single backquotes is recognized as “interpreted text”, whose interpretation is application-dependent. In the context of a Python docstring, the default interpretation of interpreted text is as Python identifiers. The text will be marked up with a hyperlink connected to the documentation for the identifier given. Lookup rules are the same as in Python itself: LGB namespace lookups (local, global, builtin). The “role” of the interpreted text (identifying a class, module, function, etc.) is determined implicitly from the namespace lookup. For example: class Keeper ( Storer ): """ Keep data fresher longer. Extend `Storer`. Class attribute `instances` keeps track of the number of `Keeper` objects instantiated. """ instances = 0 """How many `Keeper` objects are there?""" def __init__ ( self ): """ Extend `Storer.__init__()` to keep track of instances. Keep count in `self.instances` and data in `self.data`. """ Storer . __init__ ( self ) self . instances += 1 self . data = [] """Store data in a list, most recent last.""" def storedata ( self , data ): """ Extend `Storer.storedata()`; append new `data` to a list (in `self.data`). """ self . data = data Each piece of interpreted text is looked up according to the local namespace of the block containing its docstring. Markup that isolates a Python identifier and specifies its type: interpreted text with roles. Although the Python source context reader is designed not to require explicit roles, they may be used. To classify identifiers explicitly, the role is given along with the identifier in either prefix or suffix form: Use :method:`Keeper.storedata` to store the object's data in `Keeper.data`:instance_attribute:. The syntax chosen for roles is verbose, but necessarily so (if anyone has a better alternative, please post it to the Doc-SIG ). The intention of the markup is that there should be little need to use explicit roles; their use is to be kept to an absolute minimum. Markup for “tagged lists” or “label lists”: field lists. Field lists represent a mapping from field name to field body. These are mostly used for extension syntax, such as “bibliographic field lists” (representing document metadata such as author, date, and version) and extension attributes for directives (see below). They may be used to implement methodologies (docstring semantics), such as identifying parameters, exceptions raised, etc.; such usage is beyond the scope of this PEP. A modified RFC 2822 syntax is used, with a colon before as well as after the field name. Field bodies are more versatile as well; they may contain multiple field bodies (even nested field lists). For example: : Date : 2002 - 03 - 22 : Version : 1 : Authors : - Me - Myself - I Standard RFC 2822 header syntax cannot be used for this construct because it is ambiguous. A word followed by a colon at the beginning of a line is common in written text. Markup extensibility: directives and substitutions. Directives are used as an extension mechanism for reStructuredText, a way of adding support for new block-level constructs without adding new syntax. Directives for images, admonitions (note, caution, etc.), and tables of contents generation (among others) have been implemented. For example, here’s how to place an image: .. image :: mylogo . png Substitution definitions allow the power and flexibility of block-level directives to be shared by inline text. For example: The | biohazard | symbol must be used on containers used to dispose of medical waste . .. | biohazard | image :: biohazard . png Section structure markup. Section headers in reStructuredText use adornment via underlines (and possibly overlines) rather than indentation. For example: This is a Section Title ======================= This is a Subsection Title -------------------------- This paragraph is in the subsection . This is Another Section Title ============================= This paragraph is in the second section . Questions & Answers Is reStructuredText rich enough? Yes, it is for most people. If it lacks some construct that is required for a specific application, it can be added via the directive mechanism. If a useful and common construct has been overlooked and a suitably readable syntax can be found, it can be added to the specification and parser. Is reStructuredText too rich? For specific applications or individuals, perhaps. In general, no. Since the very beginning, whenever a docstring markup syntax has been proposed on the Doc-SIG , someone has complained about the lack of support for some construct or other. The reply was often something like, “These are docstrings we’re talking about, and docstrings shouldn’t have complex markup.” The problem is that a construct that seems superfluous to one person may be absolutely essential to another. reStructuredText takes the opposite approach: it provides a rich set of implicit markup constructs (plus a generic extension mechanism for explicit markup), allowing for all kinds of documents. If the set of constructs is too rich for a particular application, the unused constructs can either be removed from the parser (via application-specific overrides) or simply omitted by convention. Why not use indentation for section structure, like StructuredText does? Isn’t it more “Pythonic”? Guido van Rossum wrote the following in a 2001-06-13 Doc-SIG post: I still think that using indentation to indicate sectioning is wrong. If you look at how real books and other print publications are laid out, you’ll notice that indentation is used frequently, but mostly at the intra-section level. Indentation can be used to offset lists, tables, quotations, examples, and the like. (The argument that docstrings are different because they are input for a text formatter is wrong: the whole point is that they are also readable without processing.) I reject the argument that using indentation is Pythonic: text is not code, and different traditions and conventions hold. People have been presenting text for readability for over 30 centuries. Let’s not innovate needlessly. See Section Structure via Indentation in Problems With StructuredText for further elaboration. Why use reStructuredText for PEPs? What’s wrong with the existing standard? The existing standard for PEPs is very limited in terms of general expressibility, and referencing is especially lacking for such a reference-rich document type. PEPs are currently converted into HTML, but the results (mostly monospaced text) are less than attractive, and most of the value-added potential of HTML (especially inline hyperlinks) is untapped. Making reStructuredText a standard markup for PEPs will enable much richer expression, including support for section structure, inline markup, graphics, and tables. In several PEPs there are ASCII graphics diagrams, which are all that plaintext documents can support. Since PEPs are made available in HTML form, the ability to include proper diagrams would be immediately useful. Current PEP practices allow for reference markers in the form “[1]” in the text, and the footnotes/references themselves are listed in a section toward the end of the document. There is currently no hyperlinking between the reference marker and the footnote/reference itself (it would be possible to add this to pep2html.py, but the “markup” as it stands is ambiguous and mistakes would be inevitable). A PEP with many references (such as this one ;-) requires a lot of flipping back and forth. When revising a PEP, often new references are added or unused references deleted. It is painful to renumber the references, since it has to be done in two places and can have a cascading effect (insert a single new reference 1, and every other reference has to be renumbered; always adding new references to the end is suboptimal). It is easy for references to go out of sync. PEPs use references for two purposes: simple URL references and footnotes. reStructuredText differentiates between the two. A PEP might contain references like this: Abstract This PEP proposes adding frungible doodads [ 1 ] to the core . It extends PEP 9876 [ 2 ] via the BCA [ 3 ] mechanism . ... References and Footnotes [ 1 ] http : // www . example . org / [ 2 ] PEP 9876 , Let 's Hope We Never Get Here http : // peps . python . org / pep - 9876 / [ 3 ] "Bogus Complexity Addition" Reference 1 is a simple URL reference. Reference 2 is a footnote containing text and a URL. Reference 3 is a footnote containing text only. Rewritten using reStructuredText, this PEP could look like this: Abstract ======== This PEP proposes adding `frungible doodads`_ to the core. It extends PEP 9876 [#pep9876]_ via the BCA [#]_ mechanism. ... References & Footnotes ====================== .. _frungible doodads: http://www.example.org/ .. [#pep9876] PEP 9876, Let's Hope We Never Get Here .. [#] "Bogus Complexity Addition" URLs and footnotes can be defined close to their references if desired, making them easier to read in the source text, and making the PEPs easier to revise. The “References and Footnotes” section can be auto-generated with a document tree transform. Footnotes from throughout the PEP would be gathered and displayed under a standard header. If URL references should likewise be written out explicitly (in citation form), another tree transform could be used. URL references can be named (“frungible doodads”), and can be referenced from multiple places in the document without additional definitions. When converted to HTML, references will be replaced with inline hyperlinks (HTML <a> tags). The two footnotes are automatically numbered, so they will always stay in sync. The first footnote also contains an internal reference name, “pep9876”, so it’s easier to see the connection between reference and footnote in the source text. Named footnotes can be referenced multiple times, maintaining consistent numbering. The “#pep9876” footnote could also be written in the form of a citation: It extends PEP 9876 [ PEP9876 ] _ ... .. [ PEP9876 ] PEP 9876 , Let 's Hope We Never Get Here Footnotes are numbered, whereas citations use text for their references. Wouldn’t it be better to keep the docstring and PEP proposals separate? The PEP markup proposal may be removed if it is deemed that there is no need for PEP markup, or it could be made into a separate PEP. If accepted, PEP 1 , PEP Purpose and Guidelines, and PEP 9 , Sample PEP Template will be updated. It seems natural to adopt a single consistent markup standard for all uses of structured plaintext in Python, and to propose it all in one place. The existing pep2html.py script converts the existing PEP format to HTML. How will the new-format PEPs be converted to HTML? A new version of pep2html.py with integrated reStructuredText parsing has been completed. The Docutils project supports PEPs with a “PEP Reader” component, including all functionality currently in pep2html.py (auto-recognition of PEP & RFC references, email masking, etc.). Who’s going to convert the existing PEPs to reStructuredText? PEP authors or volunteers may convert existing PEPs if they like, but there is no requirement to do so. The reStructuredText-based PEPs will coexist with the old PEP standard. The pep2html.py mentioned in answer 6 processes both old and new standards. Why use reStructuredText for README and other ancillary files? The reasoning given for PEPs in answer 4 above also applies to README and other ancillary files. By adopting a standard markup, these files can be converted to attractive cross-referenced HTML and put up on python.org. Developers of other projects can also take advantage of this facility for their own documentation. Won’t the superficial similarity to existing markup conventions cause problems, and result in people writing invalid markup (and not noticing, because the plaintext looks natural)? How forgiving is reStructuredText of “not quite right” markup? There will be some mis-steps, as there would be when moving from one programming language to another. As with any language, proficiency grows with experience. Luckily, reStructuredText is a very little language indeed. As with any syntax, there is the possibility of syntax errors. It is expected that a user will run the processing system over their input and check the output for correctness. In a strict sense, the reStructuredText parser is very unforgiving (as it should be; “In the face of ambiguity, refuse the temptation to guess” applies to parsing markup as well as computer languages). Here’s design goal 3 from An Introduction to reStructuredText : Unambiguous. The rules for markup must not be open for interpretation. For any given input, there should be one and only one possible output (including error output). While unforgiving, at the same time the parser does try to be helpful by producing useful diagnostic output (“system messages”). The parser reports problems, indicating their level of severity (from least to most: debug, info, warning, error, severe). The user or the client software can decide on reporting thresholds; they can ignore low-level problems or cause high-level problems to bring processing to an immediate halt. Problems are reported during the parse as well as included in the output, often with two-way links between the source of the problem and the system message explaining it. Will the docstrings in the Python standard library modules be converted to reStructuredText? No. Python’s library reference documentation is maintained separately from the source. Docstrings in the Python standard library should not try to duplicate the library reference documentation. The current policy for docstrings in the Python standard library is that they should be no more than concise hints, simple and markup-free (although many do contain ad-hoc implicit markup). I want to write all my strings in Unicode. Will anything break? The parser fully supports Unicode. Docutils supports arbitrary input and output encodings. Why does the community need a new structured text design? The existing structured text designs are deficient, for the reasons given in “Rationale” above. reStructuredText aims to be a complete markup syntax, within the limitations of the “readable plaintext” medium. What is wrong with existing documentation methodologies? What existing methodologies? For Python docstrings, there is no official standard markup format, let alone a documentation methodology akin to JavaDoc. The question of methodology is at a much higher level than syntax (which this PEP addresses). It is potentially much more controversial and difficult to resolve, and is intentionally left out of this discussion. Copyright This document has been placed in the public domain. Acknowledgements Some text is borrowed from PEP 216 , Docstring Format, by Moshe Zadka. Special thanks to all members past & present of the Python Doc-SIG . Source: https://github.com/python/peps/blob/main/peps/pep-0287.rst Last modified: 2025-02-01 08:59:27 GMT Contents Abstract Benefits Goals Rationale Specification Docstring-Significant Features Questions & Answers Copyright Acknowledgements Page Source (GitHub) | 2026-01-13T08:49:06 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fdatalaria%2Fweather-service-project-part-2-building-the-interactive-frontend-with-github-pages-or-netlify-ho1&title=Weather%20Service%20Project%20%28Part%202%29%3A%20Building%20the%20Interactive%20Frontend%20with%20GitHub%20Pages%20or%20Netlify%20and%20JavaScript&summary=In%20the%20first%20part%20of%20this%20series%2C%20we%20laid%20the%20groundwork%20for%20our%20global%20weather%20service.%20We%20built%20a...&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/stackforgetx/advanced-spreadsheet-implementation-with-revogrid-in-react-hcc#comments | Advanced Spreadsheet Implementation with RevoGrid in React - 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 Advanced Spreadsheet Implementation with RevoGrid in React # webdev # react # tutorial # beginners RevoGrid is a high-performance, virtualized spreadsheet component for React that can handle millions of rows and columns with smooth scrolling and editing capabilities. Built with Web Components and optimized for performance, it's ideal for enterprise applications requiring Excel-like functionality. This guide walks through implementing advanced spreadsheet features using RevoGrid with React, covering virtual scrolling, custom cell editors, and complex data manipulation. This is part 6 of a series on using RevoGrid with React. Prerequisites Before you begin, ensure you have: Node.js version 16.0 or higher npm , yarn , or pnpm package manager A React project (version 16.8 or higher) with hooks support Advanced understanding of React hooks, refs, and performance optimization Familiarity with Web Components and virtualization concepts Knowledge of TypeScript (highly recommended) Installation Install RevoGrid React wrapper: npm install @revolist/revogrid-react Enter fullscreen mode Exit fullscreen mode Or with yarn: yarn add @revolist/revogrid-react Enter fullscreen mode Exit fullscreen mode Or with pnpm: pnpm add @revolist/revogrid-react Enter fullscreen mode Exit fullscreen mode Your package.json should include: { "dependencies" : { "@revolist/revogrid-react" : "^6.0.0" , "react" : "^18.0.0" , "react-dom" : "^18.0.0" } } Enter fullscreen mode Exit fullscreen mode Project Setup RevoGrid requires minimal setup. Import the component and styles in your application: // src/index.js import React from ' react ' ; import ReactDOM from ' react-dom/client ' ; import ' @revolist/revogrid/dist/revogrid.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 First Example / Basic Usage Let's create a basic RevoGrid component. Create src/Spreadsheet.jsx : // src/Spreadsheet.jsx import React , { useRef , useEffect } from ' react ' ; import { RevoGrid } from ' @revolist/revogrid-react ' ; import ' @revolist/revogrid/dist/revogrid.css ' ; function Spreadsheet () { const gridRef = useRef ( null ); // Column definitions const columns = [ { prop : ' id ' , name : ' ID ' , size : 100 }, { prop : ' name ' , name : ' Name ' , size : 200 }, { prop : ' email ' , name : ' Email ' , size : 250 }, { prop : ' role ' , name : ' Role ' , size : 150 } ]; // Row data const rows = [ { id : 1 , name : ' John Doe ' , email : ' john@example.com ' , role : ' Admin ' }, { id : 2 , name : ' Jane Smith ' , email : ' jane@example.com ' , role : ' User ' }, { id : 3 , name : ' Bob Johnson ' , email : ' bob@example.com ' , role : ' User ' }, { id : 4 , name : ' Alice Williams ' , email : ' alice@example.com ' , role : ' Admin ' } ]; useEffect (() => { if ( gridRef . current ) { const grid = gridRef . current ; // Set data after component mounts grid . columns = columns ; grid . source = rows ; } }, []); return ( < div style = { { height : ' 500px ' , width : ' 100% ' } } > < RevoGrid ref = { gridRef } /> </ div > ); } export default Spreadsheet ; Enter fullscreen mode Exit fullscreen mode Understanding the Basics RevoGrid uses a column-based configuration where: prop : Maps to a property in your row data name : Column header text size : Column width in pixels editor : Custom cell editor component cellTemplate : Custom cell renderer Key concepts for advanced usage: Virtualization : Automatically handles large datasets through virtual scrolling Web Components : Built on Web Components standard for performance Refs : Use refs to access grid API and methods Event Handlers : Respond to cell edits, selections, and other interactions Here's an example with editable cells: // src/EditableSpreadsheet.jsx import React , { useRef , useEffect , useState } from ' react ' ; import { RevoGrid } from ' @revolist/revogrid-react ' ; import ' @revolist/revogrid/dist/revogrid.css ' ; function EditableSpreadsheet () { const gridRef = useRef ( null ); const [ data , setData ] = useState ([ { id : 1 , product : ' Laptop ' , price : 999.99 , stock : 15 }, { id : 2 , product : ' Mouse ' , price : 29.99 , stock : 8 }, { id : 3 , product : ' Keyboard ' , price : 79.99 , stock : 12 } ]); const columns = [ { prop : ' id ' , name : ' ID ' , size : 80 , readonly : true }, { prop : ' product ' , name : ' Product ' , size : 200 , editor : ' string ' }, { prop : ' price ' , name : ' Price ' , size : 120 , editor : ' number ' , cellTemplate : ( h , { value }) => `$ ${ value . toFixed ( 2 )} ` }, { prop : ' stock ' , name : ' Stock ' , size : 100 , editor : ' number ' } ]; useEffect (() => { if ( gridRef . current ) { const grid = gridRef . current ; grid . columns = columns ; grid . source = data ; // Handle cell editing grid . addEventListener ( ' beforecellfocus ' , ( e ) => { console . log ( ' Cell focus: ' , e . detail ); }); grid . addEventListener ( ' aftercellfocus ' , ( e ) => { console . log ( ' Cell edited: ' , e . detail ); // Update data state const { row , prop , val } = e . detail ; setData ( prev => prev . map (( item , idx ) => idx === row ? { ... item , [ prop ]: val } : item )); }); } }, [ data ]); return ( < div style = { { height : ' 400px ' , width : ' 100% ' , border : ' 1px solid #ddd ' } } > < RevoGrid ref = { gridRef } /> </ div > ); } export default EditableSpreadsheet ; Enter fullscreen mode Exit fullscreen mode Practical Example / Building Something Real Let's build a comprehensive financial data spreadsheet with formulas, formatting, and advanced features: // src/FinancialSpreadsheet.jsx import React , { useRef , useEffect , useState , useCallback } from ' react ' ; import { RevoGrid } from ' @revolist/revogrid-react ' ; import ' @revolist/revogrid/dist/revogrid.css ' ; function FinancialSpreadsheet () { const gridRef = useRef ( null ); const [ data , setData ] = useState ([]); // Initialize with sample financial data useEffect (() => { const initialData = [ { month : ' January ' , revenue : 50000 , expenses : 30000 , profit : 20000 }, { month : ' February ' , revenue : 55000 , expenses : 32000 , profit : 23000 }, { month : ' March ' , revenue : 60000 , expenses : 35000 , profit : 25000 }, { month : ' April ' , revenue : 58000 , expenses : 33000 , profit : 25000 }, { month : ' May ' , revenue : 62000 , expenses : 36000 , profit : 26000 }, { month : ' June ' , revenue : 65000 , expenses : 38000 , profit : 27000 } ]; setData ( initialData ); }, []); const columns = [ { prop : ' month ' , name : ' Month ' , size : 150 , pinned : ' left ' , readonly : true }, { prop : ' revenue ' , name : ' Revenue ' , size : 150 , editor : ' number ' , cellTemplate : ( h , { value }) => { return h ( ' span ' , { style : { color : ' #28a745 ' , fontWeight : ' bold ' } }, `$ ${ value . toLocaleString ()} ` ); } }, { prop : ' expenses ' , name : ' Expenses ' , size : 150 , editor : ' number ' , cellTemplate : ( h , { value }) => { return h ( ' span ' , { style : { color : ' #dc3545 ' , fontWeight : ' bold ' } }, `$ ${ value . toLocaleString ()} ` ); } }, { prop : ' profit ' , name : ' Profit ' , size : 150 , editor : ' number ' , readonly : true , cellTemplate : ( h , { value }) => { const color = value > 0 ? ' #28a745 ' : ' #dc3545 ' ; return h ( ' span ' , { style : { color , fontWeight : ' bold ' } }, `$ ${ value . toLocaleString ()} ` ); } }, { prop : ' margin ' , name : ' Margin % ' , size : 120 , readonly : true , cellTemplate : ( h , { row }) => { const margin = (( row . profit / row . revenue ) * 100 ). toFixed ( 2 ); const color = parseFloat ( margin ) > 30 ? ' #28a745 ' : parseFloat ( margin ) > 20 ? ' #ffc107 ' : ' #dc3545 ' ; return h ( ' span ' , { style : { color , fontWeight : ' bold ' } }, ` ${ margin } %` ); } } ]; useEffect (() => { if ( gridRef . current && data . length > 0 ) { const grid = gridRef . current ; // Calculate profit automatically when revenue or expenses change const updatedData = data . map ( row => ({ ... row , profit : row . revenue - row . expenses })); grid . columns = columns ; grid . source = updatedData ; // Handle cell editing const handleCellEdit = ( e ) => { const { row , prop , val } = e . detail ; const newData = [... data ]; if ( newData [ row ]) { newData [ row ] = { ... newData [ row ], [ prop ]: parseFloat ( val ) || 0 }; // Recalculate profit newData [ row ]. profit = newData [ row ]. revenue - newData [ row ]. expenses ; setData ( newData ); } }; grid . addEventListener ( ' aftercellfocus ' , handleCellEdit ); return () => { grid . removeEventListener ( ' aftercellfocus ' , handleCellEdit ); }; } }, [ data , columns ]); const handleExport = useCallback (() => { if ( gridRef . current ) { const grid = gridRef . current ; // Export functionality would be implemented here console . log ( ' Exporting data: ' , data ); } }, [ data ]); const handleAddRow = useCallback (() => { setData ( prev => [... prev , { month : `Month ${ prev . length + 1 } ` , revenue : 0 , expenses : 0 , profit : 0 }]); }, []); return ( < div style = { { padding : ' 20px ' } } > < div style = { { marginBottom : ' 20px ' , display : ' flex ' , gap : ' 10px ' } } > < h2 > Financial Data Spreadsheet </ h2 > < button onClick = { handleAddRow } style = { { padding : ' 8px 16px ' , backgroundColor : ' #007bff ' , color : ' white ' , border : ' none ' , borderRadius : ' 4px ' , cursor : ' pointer ' } } > Add Row </ button > < button onClick = { handleExport } style = { { padding : ' 8px 16px ' , backgroundColor : ' #28a745 ' , color : ' white ' , border : ' none ' , borderRadius : ' 4px ' , cursor : ' pointer ' } } > Export </ button > </ div > < div style = { { height : ' 600px ' , width : ' 100% ' , border : ' 1px solid #ddd ' } } > < RevoGrid ref = { gridRef } theme = "material" range = { true } resize = { true } rowHeaders = { true } columnHeaders = { true } /> </ div > </ div > ); } export default FinancialSpreadsheet ; Enter fullscreen mode Exit fullscreen mode This advanced example demonstrates: Automatic formula calculation (profit = revenue - expenses) Custom cell templates with conditional styling Pinned columns (month column stays fixed) Real-time data updates Cell editing with validation Dynamic row addition Export functionality preparation Material theme styling Common Issues / Troubleshooting Grid not rendering : Ensure you've imported the CSS file ( @revolist/revogrid/dist/revogrid.css ). The grid requires explicit height on the container div. Data not displaying : Make sure you're setting both columns and source properties on the grid ref after it mounts. Use useEffect to ensure the ref is available. Cell editing not working : Verify that you've set editor property in column definitions and are handling the aftercellfocus event properly. Performance issues : RevoGrid handles virtualization automatically, but for extremely large datasets (millions of rows), consider implementing data pagination or lazy loading. TypeScript errors : Install type definitions if available, or create your own type declarations for the RevoGrid component and its API. Event listeners not firing : Ensure you're adding event listeners in useEffect and cleaning them up properly to avoid memory leaks. Next Steps Now that you've mastered RevoGrid basics: Explore advanced features like row grouping and aggregation Implement custom cell editors and renderers Add formula support and calculation engine Learn about column resizing and reordering Implement server-side data loading Add export/import functionality (CSV, Excel) Explore theming and customization options Check the official repository: https://github.com/revolist/revogrid Look for part 7 of this series for more advanced topics Summary You've learned how to implement advanced spreadsheet functionality with RevoGrid, including virtual scrolling, custom cell rendering, formula calculations, and real-time data updates. RevoGrid provides excellent performance for large datasets and offers extensive customization options for building enterprise-grade spreadsheet applications. 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 More from Michael Turner Getting Started with ReactGrid in React: Building Your First Spreadsheet # react # webdev # javascript # tutorial Building Interactive Data Tables with React Data Grid # react # webdev # beginners # tutorial Getting Started with MUI X Data Grid in React: Building Your First Data Table # webdev # programming # javascript # beginners 💎 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://twitter.com/neondatabase/ | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:06 |
https://twitter.com/intent/tweet?text=%22The%20Underlying%20Process%20of%20Request%20Processing%22%20by%20Sergiy%20Yevtushenko%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fsiy%2Fthe-underlying-process-of-request-processing-1od4 | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/privacy#9-supplemental-notice-for-nevada-residents | 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/ruizb/what-is-functional-programming-3cn0 | What is Functional Programming? - 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 Benoit Ruiz Posted on Sep 10, 2021 • Edited on Sep 16, 2021 What is Functional Programming? # functional # programming # tutorial # typescript Demystifying Functional Programming (8 Part Series) 1 Introduction 2 What is Functional Programming? ... 4 more parts... 3 Why should we learn and use FP? 4 Function composition and higher-order function 5 Declarative vs imperative 6 Side effects 7 Function purity and referential transparency 8 Data immutability Functional Programming is a declarative programming paradigm where developers write software by: Composing pure functions, While avoiding mutable data and shared state, And pushing side-effects to the edge of the program. Don't worry about all these terms for now, I'll explain them later in this series, with dedicated articles. Hmmm... Ok sure, but what is a "paradigm", and what does declarative mean? A programming paradigm is a way to classify a programming language based on some features. Basically, a programming paradigm is a way to write programs . Some languages use only 1 paradigm, while others can use multiple paradigms. For example, Haskell uses a single paradigm: functional programming. JavaScript uses multiple paradigms, as we can write programs using procedural programming, "object-oriented" programming (OOP for short), functional programming, or even reactive programming. For single paradigm languages, since there's only 1 way of writing programs, it's easy to "stay on the track". For multi-paradigms languages, it's harder to stay on the same track, as the frontier between 2 paradigms depends solely on the developer writing the program. One piece of the software can be written in FP, while the other can be written in OOP. Both pieces can coexist, as long as the code is adapted to jump from one way to the other. This flexibility can be both a good and a bad thing, but we won't cover this topic here. I think it's important to say that FP is not a replacement for object-oriented programming, or any other paradigm whatsoever. It's just a different way of writing programs, which comes with some advantages we'll see in the next article. Well that covers the paradigm part, what about the declarative part? I won't go into many details here since I've planned on writing an article about declarative vs imperative code, later in this series. In a nutshell, declarative programming is a style of building the structure and elements of a program by describing what the program does, and not how it does it (that's the imperative way). A declarative program expresses the logic of a computation ("what") whereas an imperative program expresses the steps to perform a computation, explicitly ("how"). Don't worry if this is still blurry, we'll cover this part more thoroughly later. Requirement All languages are not born equal. There is actually one requirement for writing FP code: functions must be first-class citizens of the language. First-class what now? A first-class citizen is an entity of the language that supports the following operations: Storing the entity in a variable Passing the entity as an argument of a function Returning the entity when calling a function Let's take an example: are functions first-class citizens in JavaScript? Can they* be stored in variables? Yes. Can they be passed as arguments of other functions? Yes. Can they be returned when calling other functions? Yes. Therefore, functions are first-class citizens in JavaScript, meaning we can write FP programs using this language. * Small detail: we are not talking about the functions directly here, but rather their references. If the language you use every day fulfills this requirement, then you can definitely implement some - if not all - of the concepts and tools we'll talk about in this series. If that's not the case (e.g. Java < 8), then you can still learn through this series, but you probably won't be able to play with these concepts in your favorite language. And there's nothing better than some practice to actually learn new things. Last but not least, Functional Programming comes with some "restrictions" that are better enforced with a compiler. So my recommendation would be to use a programming language that has a compiler that offers static typing. You can still write FP programs in JavaScript - an interpreted language - for example, but you won't benefit from the greatness provided by a typed language such as TypeScript. Photo by Xavi Cabrera on Unsplash . Demystifying Functional Programming (8 Part Series) 1 Introduction 2 What is Functional Programming? ... 4 more parts... 3 Why should we learn and use FP? 4 Function composition and higher-order function 5 Declarative vs imperative 6 Side effects 7 Function purity and referential transparency 8 Data immutability 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 Andrew011002 Andrew011002 Andrew011002 Follow Joined Dec 17, 2023 • Jan 8 '24 Dropdown menu Copy link Hide I really appreciate this post. I’ve never* typed a line of JavaScript or TypeScript and your examples were clear alongside your explanations when defining declarative and imperative programming. 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 Benoit Ruiz Follow Location France Work Software Engineer at Datadog Joined Aug 2, 2020 More from Benoit Ruiz Data immutability # functional # programming # tutorial # typescript Function purity and referential transparency # functional # programming # tutorial # typescript Equivalent of Scala's for-comprehension using fp-ts # typescript # scala # functional # 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://hmpljs.forem.com/++ | 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 🐥 Lock In Your Early-Bird Pricing Join DEV++ Welcome to Your DEV++ Dashboard Build More, Spend Less DEV++ provides exclusive partnerships and offers that let you dabble, experiment, and become a stronger developer. Today's price locks you in at $11 /month —even as we add new offers! Wait! As a tag moderator, you get $7 off the base price. Your price is only $4 /month. 🤯 Join DEV++ But that's not all! DEV++ also unlocks special DEV features— scroll down to learn more . Access 18 Exclusive Partner Discounts (More Added Monthly) We have negotiated exclusive discounts with these companies, available only to verified members of the DEV community like you. $100 Credit 1-Year Free 80% Off Your First Month 1-Year Free 1-Month Free 20% off mock interviews 25% Off Scrimba Pro 1 Month Free 30% Off Storewide 3 Months Free 1 Year Free 5% Flat Fee Extended Trial 6 Months Free 25% off LabEx 50% off of Fine for 12 months 20% off any personal plan 50% off One Year $100 Neon Credit DEV++ members get a $100 credit towards Neon services Neon Postgres is a fully managed Postgres database that is easy to use and scales with your app. DEV++ members get 4x the storage on the free tier. 1 year complimentary .tech standard domain Showcase your tech expertise by launching your tech projects on a .tech domain! DEV++ members get exclusive access to a 1-Year Complimentary .tech Domain 80% Off First Month of Replit Core Go from natural language to fully deployed apps and internal tools in minutes. Receive 80% off your first month of Replit Core, which includes $25 of Replit Agent, database, and cloud services credits. 1 year free .fun domain Turn your "JUST FOR FUN" project into a reality! DEV++ members get access to a 1-Year complimentary .fun domain (non-premium). 1-Month Free CodeRabbit Cut Code Review Time & Bugs in Half Supercharge your entire team with AI-driven contextual feedback. 20% Off Mock Interviews Nail Your Tech Interviews with FAANG+ Experts Mock interviews and thorough feedback to land your dream tech roles faster. Trusted by 25,000+ experienced tech professionals. 25% Off Scrimba Pro Level up your coding skills and build awesome projects. DEV++ members get 25% off Scrimba Pro (forever). 1 Month Free Interview.study Practice real interview questions with AI-driven feedback. Try Interview.study for a month without commitment. 30% off ThemeSelection Storewide Fully Coded Dashboard Templates & UI Kits 🎉 To Kick-Start Your Next Project DEV++ members get a 30% off premium products storewide. 3 Months Free Growth Plan Multi-channel Notification Infrastructure for Developers Try SuprSend's Growth plan free for three months. 1 Year of Free Unlimited Usage Feature flags built on open standards to power faster releases Try DevCycle's Developer plan and get one year of free unlimited usage. 5% Flat Fee for Ruul Freelancer's Pay Button Ruul, as your Merchant of Record, is the legal entity selling your professional services to your business clients compliantly in 190 countries. Enjoy a 5% flat fee as a DEV++ member. Extended 3-Month Trial A beautiful, native Git client designed to make Git easy to use. With its best-in-class features and seamless integration with popular code hosting platforms such as GitHub or GitLab, Tower grants you all the power of Git in an intuitive interface. 6 Months Free on Pay-As-You-Go Plan The open source, full-stack monitoring platform. Error monitoring, session replay, logging, distributed tracing, and more. highlight.io is a monitoring tool for the next generation of developers (like you!). 25% off LabEx Pro Annual Plan Learn Linux, DevOps & Cybersecurity with Hands-on Labs Develop skills in Linux, DevOps, Cybersecurity, Programming, Data Science, and more through interactive labs and real-world projects. 50% off of Fine for 12 months (annual plan) AI Coding for Startups The all-in-one AI Coding agent for startups to ship better software, faster. 20% off any personal plan font follows function MonoLisa was designed by professionals to improve developers' productivity and reduce fatigue. 50% off One Year API as a service to detect fake users and bots Stop free tier abusers, bot accounts and mass registrations while keeping your email lists and analytics pristine. Enhance Your DEV Experience DEV++ unlocks special features to help you focus on what matters and succeed within our community. Pre-Compute Feed Optimization For DEV++ members, we're adding a setting that allows you to define which content should surface in your feed—in natural language. DEV++ Benefit of the Doubt To foster human-to-human connection, DEV++ members are less likely to be marked as spam as we moderate to ensure community quality. DEV++ Badge Get the DEV++ badge on your profile to show your support for the community and your commitment to leveling up your dev career. Ready to Elevate Your Development Journey? We've made it an easy choice. Using just one of these offers makes your subscription worthwhile. Lock in your rate at $11 /month—even as we continue to add new offers! Join DEV++ DEV Feature Augmentations Pre-Compute Feed Optimization Visit your settings to describe the type of posts you're most interested in seeing on DEV. Rolling out in full over the next few weeks. Visit Your Settings DEV++ Benefit of the Doubt Your posts are now less likely to be caught in our spam filters. We aim to connect humans to humans, and DEV++ membership is a signal. DEV++ Badge The ++ badge now appears next to your name on your posts and comments, giving you more authority in the community and your career. Exclusive Offers with DEV++ Partners 💎 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://twitter.com/intent/tweet?text=%22WebSockets%20vs%20Long%20Polling%22%20by%20%40KevBurnsJr%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fkevburnsjr%2Fwebsockets-vs-long-polling-3a0o | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:06 |
https://dev.to/t/web3/page/3 | Web3 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 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 2026 to witness major tech shifts with AI integration, new screen tech, and evolving programming languages. Stelixx Insights Stelixx Insights Stelixx Insights Follow Jan 2 2026 to witness major tech shifts with AI integration, new screen tech, and evolving programming languages. # ai # web3 # blockchain # productivity Comments Add Comment 1 min read Why GPU Marketplaces Fail Production Workloads-And What Infrastructure-First Actually Means Rohan Kumar Rohan Kumar Rohan Kumar Follow Dec 31 '25 Why GPU Marketplaces Fail Production Workloads-And What Infrastructure-First Actually Means # aethir # cloud # web3 Comments Add Comment 10 min read Ethereum-Solidity Quiz Q14: Why constructors can't be used in upgradeable contracts? MihaiHng MihaiHng MihaiHng Follow Jan 5 Ethereum-Solidity Quiz Q14: Why constructors can't be used in upgradeable contracts? # ethereum # web3 # solidity # blockchain 3 reactions Comments Add Comment 1 min read Ethereum-Solidity Quiz Q11: What is TWAP? MihaiHng MihaiHng MihaiHng Follow Jan 2 Ethereum-Solidity Quiz Q11: What is TWAP? # ethereum # web3 # solidity # blockchain 2 reactions Comments Add Comment 1 min read Ethereum-Solidity Quiz Q9: What is a flashloan? MihaiHng MihaiHng MihaiHng Follow Dec 31 '25 Ethereum-Solidity Quiz Q9: What is a flashloan? # ethereum # web3 # solidity # cyfrin 1 reaction Comments Add Comment 1 min read AI Trading Arena: Real-time Multi-Model Competition for Optimal Execution fmzquant fmzquant fmzquant Follow Dec 31 '25 AI Trading Arena: Real-time Multi-Model Competition for Optimal Execution # ai # systems # web3 # mcp Comments Add Comment 6 min read Crypto Spot-Futures Arbitrage in Practice: Lessons Learned from Theory to Reality fmzquant fmzquant fmzquant Follow Dec 30 '25 Crypto Spot-Futures Arbitrage in Practice: Lessons Learned from Theory to Reality # node # devrel # sql # web3 Comments Add Comment 12 min read Ethereum Account Abstraction (ERC-4337), Part 2: Implementation Kurt Kurt Kurt Follow Dec 30 '25 Ethereum Account Abstraction (ERC-4337), Part 2: Implementation # ethereum # web3 # solidity Comments Add Comment 1 min read Ethereum-Solidity Quiz Q8: How can you deploy a Solidity smart contract with Foundry? MihaiHng MihaiHng MihaiHng Follow Dec 30 '25 Ethereum-Solidity Quiz Q8: How can you deploy a Solidity smart contract with Foundry? # ethereum # solidity # web3 # blockchain 2 reactions Comments Add Comment 1 min read Ethereum-Solidity Quiz Q13: What are the main sections in the bytecode of a compiled Solidity smart contract? MihaiHng MihaiHng MihaiHng Follow Jan 4 Ethereum-Solidity Quiz Q13: What are the main sections in the bytecode of a compiled Solidity smart contract? # ethereum # web3 # solidity # cyfrin 2 reactions Comments Add Comment 1 min read The Quantum Event Horizon: Cryptographic Vulnerabilities in the Ethereum Network Erick Fernandez Erick Fernandez Erick Fernandez Follow for Extropy.IO Dec 29 '25 The Quantum Event Horizon: Cryptographic Vulnerabilities in the Ethereum Network # quantum # ethereum # blockchain # web3 Comments Add Comment 6 min read Ethereum-Solidity Quiz Q7: What is the "solc optimizer" in Solidity? MihaiHng MihaiHng MihaiHng Follow Dec 28 '25 Ethereum-Solidity Quiz Q7: What is the "solc optimizer" in Solidity? # ethereum # web3 # solidity # blockchain 1 reaction Comments Add Comment 1 min read Smart Contract working in etherium with Metamask wallet Harsh Bansal Harsh Bansal Harsh Bansal Follow Jan 1 Smart Contract working in etherium with Metamask wallet # solidity # ethereum # smartcontract # web3 Comments Add Comment 3 min read Ethereum-Solidity Quiz Q6: What is the max bytecode size for smart contract deployment on Ethereum? MihaiHng MihaiHng MihaiHng Follow Dec 27 '25 Ethereum-Solidity Quiz Q6: What is the max bytecode size for smart contract deployment on Ethereum? # ethereum # solidity # web3 # blockchain 1 reaction Comments Add Comment 1 min read Decentralized Finance's Biggest Vulnerability: Why Private Key Management Can't Stay Private sid sid sid Follow Dec 25 '25 Decentralized Finance's Biggest Vulnerability: Why Private Key Management Can't Stay Private # privacy # web3 # blockchain # security 1 reaction Comments 2 comments 4 min read Why I Left Banking to Bet on "Programmable Money" (RWA) JimmyGunawanSE.M.Fi JimmyGunawanSE.M.Fi JimmyGunawanSE.M.Fi Follow Dec 26 '25 Why I Left Banking to Bet on "Programmable Money" (RWA) # fintech # blockchain # web3 # systemarchitecture Comments Add Comment 1 min read Verifiable Compute for Onchain Prop Trading: How Carrotfunding Uses ROFL Manav Manav Manav Follow Dec 25 '25 Verifiable Compute for Onchain Prop Trading: How Carrotfunding Uses ROFL # web3 # blockchain # privacy # proptrading 2 reactions Comments 2 comments 2 min read x402: Turning HTTP 402 into a Real Payment Primitive Manav Manav Manav Follow Dec 25 '25 x402: Turning HTTP 402 into a Real Payment Primitive # privacy # blockchain # web3 # http 1 reaction Comments 2 comments 3 min read Why Oasis Is Backing Custody-Native Credit Infrastructure Manav Manav Manav Follow Dec 25 '25 Why Oasis Is Backing Custody-Native Credit Infrastructure # privacy # web3 # blockchain # infrastructure 2 reactions Comments 2 comments 2 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) # architecture # web3 # webdev 1 reaction Comments 1 comment 1 min read Making Testnet vs Devnet Usage Clearer Favoured Anuanatata Favoured Anuanatata Favoured Anuanatata Follow Dec 24 '25 Making Testnet vs Devnet Usage Clearer # web3 # documentation # learning # opensource Comments Add Comment 1 min read x402 V2: What's New in the Internet-Native Payments Protocol jimquote jimquote jimquote Follow Dec 23 '25 x402 V2: What's New in the Internet-Native Payments Protocol # news # api # web3 Comments Add Comment 4 min read Tokenomics' Hidden Flaw: Why Economic Models Need Privacy to Prevent Manipulation sid sid sid Follow Dec 25 '25 Tokenomics' Hidden Flaw: Why Economic Models Need Privacy to Prevent Manipulation # privacy # web3 # blockchain # security 1 reaction Comments 2 comments 5 min read Stop Flattening Your Images: How Qwen2-VL Unlocks "Layered" Vision Juddiy Juddiy Juddiy Follow Dec 23 '25 Stop Flattening Your Images: How Qwen2-VL Unlocks "Layered" Vision # webdev # ai # python # web3 3 reactions Comments Add Comment 4 min read 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 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://twitter.com/intent/tweet?text=%22append%20VS%20appendChild%22%20by%20%40ibn_Abubakre%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Fibn_abubakre%2Fappend-vs-appendchild-a4m | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:06 |
https://www.facebook.com/sharer.php?u=https%3A%2F%2Fdev.to%2Farunavamodak%2Freact-router-v5-vs-v6-dp0 | 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/t/computervision | Computervision - 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 # computervision Follow Hide Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu You can't trust Images anymore pri pri pri Follow Jan 12 You can't trust Images anymore # showdev # computervision 11 reactions Comments Add Comment 4 min read How I Built a Real-Time Hand Tracking Platform That Runs Entirely in the Browser Huy Pham Huy Pham Huy Pham Follow Jan 13 How I Built a Real-Time Hand Tracking Platform That Runs Entirely in the Browser # computervision # mediapipe # threejs # opensource Comments Add Comment 2 min read Turning Images Into Game-Ready PBR Textures With Python (Offline, No Subscriptions) Mate Technologies Mate Technologies Mate Technologies Follow Jan 9 Turning Images Into Game-Ready PBR Textures With Python (Offline, No Subscriptions) # python # gamedev # computervision # opengl Comments Add Comment 2 min read VID2IMG Pro – Video to Image Extraction & Anonymization Tool Mate Technologies Mate Technologies Mate Technologies Follow Jan 9 VID2IMG Pro – Video to Image Extraction & Anonymization Tool # computervision # videoprocessing # photogrammetry # privacyandanonymization Comments Add Comment 2 min read Building a Production-Ready Traffic Violation Detection System with Computer Vision Harris Bashir Harris Bashir Harris Bashir Follow Jan 11 Building a Production-Ready Traffic Violation Detection System with Computer Vision # computervision # machinelearning # ai # dataengineering 6 reactions Comments 2 comments 3 min read Just added SAM3 video object tracking to X-AnyLabeling! Jack Wang Jack Wang Jack Wang Follow Jan 3 Just added SAM3 video object tracking to X-AnyLabeling! # segmentanything3 # xanylabeling # computervision # ai Comments Add Comment 1 min read AI Calorie Counting: How Computer Vision Is Revolutionizing Personal Nutrition wellallyTech wellallyTech wellallyTech Follow Jan 4 AI Calorie Counting: How Computer Vision Is Revolutionizing Personal Nutrition # ai # python # pytorch # computervision Comments Add Comment 2 min read Radiant AI: Building an AI-Powered Image Editor with Python Arshvir Arshvir Arshvir Follow Jan 1 Radiant AI: Building an AI-Powered Image Editor with Python # ai # computervision # python # webdev Comments Add Comment 2 min read Designing an AI Foot Traffic Analysis System for Retail ZedIoT ZedIoT ZedIoT Follow Dec 31 '25 Designing an AI Foot Traffic Analysis System for Retail # ai # computervision # systemdesign # retail Comments Add Comment 2 min read Remove CapCut Watermark with AI — How We Built a Flicker-Free Video Inpainting System renming wang renming wang renming wang Follow Dec 30 '25 Remove CapCut Watermark with AI — How We Built a Flicker-Free Video Inpainting System # capcut # ai # computervision # machinelearning 1 reaction Comments 1 comment 3 min read AI-powered face swap explained simply: algorithms and limits FreePixel FreePixel FreePixel Follow Dec 30 '25 AI-powered face swap explained simply: algorithms and limits # ai # machinelearning # computervision # deeplearningethics Comments Add Comment 4 min read AI-powered drone-based computer vision systems for inspection and maintenance of urban infrastructure in the EU Kirill Filippov Kirill Filippov Kirill Filippov Follow Jan 1 AI-powered drone-based computer vision systems for inspection and maintenance of urban infrastructure in the EU # computervision # ai # predictivemaintenance # drones Comments Add Comment 16 min read Deploying Your AI/ML Models: A Practical Guide from Training to Production Ajor Ajor Ajor Follow Dec 23 '25 Deploying Your AI/ML Models: A Practical Guide from Training to Production # ai # fastapi # computervision # deeplearning 1 reaction Comments Add Comment 5 min read 17 y/o developer. Building weird but useful tools. Hand Mouse — control your PC with just your hand. Fl4ie Fl4ie Fl4ie Follow Dec 21 '25 17 y/o developer. Building weird but useful tools. Hand Mouse — control your PC with just your hand. # computervision # productivit # python # programming 5 reactions Comments Add Comment 1 min read AI Background Remover: Why Similar Colors Confuse Segmentation Models FreePixel FreePixel FreePixel Follow Dec 22 '25 AI Background Remover: Why Similar Colors Confuse Segmentation Models # ai # computervision Comments Add Comment 4 min read AI Background Remover: How AI Detects Objects and Separates Backgrounds FreePixel FreePixel FreePixel Follow Dec 17 '25 AI Background Remover: How AI Detects Objects and Separates Backgrounds # ai # computervision # imageprocessing # machinelearning Comments Add Comment 3 min read AI Background Remover: A Complete Guide to Automated Image Cutouts FreePixel FreePixel FreePixel Follow Dec 16 '25 AI Background Remover: A Complete Guide to Automated Image Cutouts # ai # imageprocessing # computervision # webdev Comments Add Comment 4 min read AI Background Remover: What AI Sees When Separating Objects FreePixel FreePixel FreePixel Follow Dec 20 '25 AI Background Remover: What AI Sees When Separating Objects # aibackgroundremover # computervision # aiimageprocessing Comments Add Comment 4 min read AI Background Remover: Image Quality and Edge Accuracy FreePixel FreePixel FreePixel Follow Dec 13 '25 AI Background Remover: Image Quality and Edge Accuracy # ai # imageprocessing # computervision # webdev Comments Add Comment 4 min read Starting Dusty — A Tiny DSL for ETL & Research Data Cleaning Avik Avik Avik Follow Dec 11 '25 Starting Dusty — A Tiny DSL for ETL & Research Data Cleaning # programming # computervision # dsl Comments Add Comment 2 min read AI-Driven Roof Modeling From Drone Imagery for for Insurance Company SciForce SciForce SciForce Follow Dec 10 '25 AI-Driven Roof Modeling From Drone Imagery for for Insurance Company # ai # computervision # proptech # machinelearning Comments Add Comment 7 min read The Hot-Reload Magic - Tweak Pipelines Live (No Restarts!) Elliot Silver Elliot Silver Elliot Silver Follow Dec 17 '25 The Hot-Reload Magic - Tweak Pipelines Live (No Restarts!) # computervision # go # opensource # programming 8 reactions Comments 2 comments 2 min read Post 1: Implemented Canny Edge Detection, Sobel Operators, and Perspective Transforms from scratch Jyoti Prajapati Jyoti Prajapati Jyoti Prajapati Follow Dec 8 '25 Post 1: Implemented Canny Edge Detection, Sobel Operators, and Perspective Transforms from scratch # cv # computervision # javascript # ubuntu Comments Add Comment 1 min read See Through Walls: AI's New Eye on Occluded Motion by Arvind Sundararajan Arvind SundaraRajan Arvind SundaraRajan Arvind SundaraRajan Follow Dec 4 '25 See Through Walls: AI's New Eye on Occluded Motion by Arvind Sundararajan # machinelearning # computervision # python # ai 1 reaction Comments Add Comment 2 min read AI Guardian Angel: Preventing Traffic Chaos with Smart Sensors by Arvind Sundararajan Arvind SundaraRajan Arvind SundaraRajan Arvind SundaraRajan Follow Nov 30 '25 AI Guardian Angel: Preventing Traffic Chaos with Smart Sensors by Arvind Sundararajan # ai # machinelearning # computervision # infrastructure Comments Add Comment 2 min read loading... trending guides/resources Advent of AI 2025 - Day 5: I Built a Touchless Flight Tracker You Control With Hand Gestures How I Reached 84.35% on CIFAR-100 Using ResNet-50 (PyTorch Guide) AI-powered face swap explained simply: algorithms and limits No More Manual Masking: The Science That Makes AI Batch Background Removal Tools So Accurate Teaching AI to Read Emotions: Science, Challenges, and Innovation Behind Facial Emotion Detection... Meet X-AnyLabeling: The Python-native, AI-powered Annotation Tool for Modern CV 🚀 Animating Realism: Transferring Motion Styles with AI Digital Zoom vs. Cropping: Are They the Same Thing? AI Background Remover: How AI Detects Objects and Separates Backgrounds I built «UniFace: All-in-one face analysis Library» to make Face Analysis Easier Why TrivialAugment Works (Even When It Shouldn’t) The Hot-Reload Magic - Tweak Pipelines Live (No Restarts!) Why CutMix Works (Even When It Breaks the Image Apart) Just added SAM3 video object tracking to X-AnyLabeling! How I Built a 95% Accurate Defect Detection System with an ESP32-CAM and Python How I Built a 140 FPS Real-Time Face Landmark App with Just YOLOv9 + MediaPipe (5-Part Series) Cloak of Invisibility: Hiding from AI in Plain Sight Deploying Your AI/ML Models: A Practical Guide from Training to Production Remove CapCut Watermark with AI — How We Built a Flicker-Free Video Inpainting System Introducing GoCVKit: Zero-Boilerplate Computer Vision in Go 💎 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/python-powered-crosscompute-report-automation-for-ereliability-tracker-leads-to-cost-and-time-savings-for-the-american-public-power-association-updated-20210526-0900/ | Python Powered CrossCompute Report Automation for eReliability Tracker Leads to Cost and Time Savings for the American Public Power Association | 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 Powered CrossCompute Report Automation for eReliability Tracker Leads to Cost and Time Savings for the American Public Power Association Written by Roy Hyunjin Han , CrossCompute Overview The American Public Power Association eReliability Tracker is an award-winning Pyramid web application that helps electric utilities track performance metrics. As part of their subscription benefits, utilities receive a Reliability Benchmarking Report that is custom tailored to each utility using eReliability Tracker data. In this case study, we show how the American Public Power Association used Python + Markdown + CSS + JupyterLab + CrossCompute to transform a three to six month labor intensive process into a highly flexible automated PDF report that can leverage the full analytical power of Python. The outcome is that over five hundred utilities can now receive valuable reliability metrics more frequently to improve their services. The eReliability Tracker Team uses the time saved to innovate new analytics that help utilities deliver power to their communities. Challenge The Reliability Benchmarking Report was originally developed in Microsoft Access and had been faithfully and successfully delivered for many years to eReliability Tracker subscribers. However, as the number of subscriptions multiplied, the semi-manual click intensive process to generate a custom report for each utility became increasingly arduous. Changes in the underlying data could trigger a cascade of tedious updates to the tables and charts in each utility's report and significantly delay the iterative inter-departmental review process. Solution In 2021, an analyst in the APPA Office of Data Analytics decided to recreate the eReliability Tracker Benchmarking Report using Python. Within the next two months, she was able to automate all ten sections of the report in JupyterLab using the CrossCompute Report Automation Framework . She used numpy and pandas to compute the various statistics and matplotlib and seaborn to generate the plots. To style the report, the analyst used standard Markdown + CSS. Outcome For every change in the underlying dataset or downstream computation, the analyst is now able to regenerate custom PDF reports for all 500 utilities in about an hour, which means she can iterate and innovate faster. Subsequent iterations of the report can take advantage of the rich library of free and open source computational and visualization packages available in Python. All ten sections of the report are also deployed internally as web-based CrossCompute tools so that non-technical users can drag and drop new data and regenerate the report's tables and charts without touching code. Acknowledgments Thank you to the American Public Power Association, U.S. Department of Energy, Python Software Foundation, Tampa Bay Innovation Center and CrossCompute for making this work possible. 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://dev.to/ruizb/side-effects-21fc | Side effects - 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 Benoit Ruiz Posted on Feb 16, 2022 Side effects # functional # programming # tutorial # typescript Demystifying Functional Programming (8 Part Series) 1 Introduction 2 What is Functional Programming? ... 4 more parts... 3 Why should we learn and use FP? 4 Function composition and higher-order function 5 Declarative vs imperative 6 Side effects 7 Function purity and referential transparency 8 Data immutability Table of contents Introduction How to deal with side effects Chaining side effects Introduction Initially, I wanted to talk about function purity and referential transparency at this point of the series. However, when preparing the article, I used a significant amount of references to the term "side effect". This is why I chose to introduce side effects before talking about function purity. Both concepts are related to one another, but they deserve their separate article. So, what is a side effect? A side effect is an interaction with the outside world . Now you might be wondering, what is the "outside world" then? It is anything that is not part of the domain layer of the software. Here are some examples of these types of interactions: Reading a file, and/or writing to a file Making a network request (calling an API, downloading a file...) Reading from a global state (e.g. global variable, a parameter from the parent's closure...) Throwing/intercepting an exception For web applications, using DOM objects and methods Logging messages to the console The domain layer contains all the models, logic, and rules of the domain. If you are familiar with the "hexagonal architecture", also known as "ports and adapters architecture", then this layer is at the very center of the diagram. Generally speaking, all the functions from the domain layer can be tested with unit tests, as there are no side effects. This is the only layer that is pure , all the others encompassing it have side effects. In functional programs, functions have to be pure, i.e. side-effect-free. Why? Because side effects are not deterministic, and they are hard to reason about . When we want to validate that a function works as expected, we have to be able to understand it and use automated tests. Introducing non-determinism and external references into the function makes it hard to understand it simply, and test its behavior. That being said, a program that has no side effects is not very useful. We need interactions with the outside world , such as getting input from a user, writing to a database, or displaying something to the screen. So, on the one hand, side effects are bad, but on the other hand, they are mandatory to build useful programs. What can we do about it? How to deal with side effects One particularity of a side effect is that it just happens . In our imperative programs, a side effect does not return anything. In other words, we cannot store it in a variable, or pass it as a parameter of a function. We can easily identify functions that perform side effects, as they are the ones that do not return any value. For example: function trustMeNoSideEffectHere (): void { ... } Enter fullscreen mode Exit fullscreen mode This function's name is misleading as its return type does not match its name. The void type indicates that this function does not return any value. Therefore, if it does not compute any value, it is either useless or performs at least a side effect. Of course, we can still have functions that return a value, but also perform side effects: function trustMeNoSideEffectHere (): number { let n = 21 window . foo . bar ++ // mutating the global state = side effect return n * 2 } Enter fullscreen mode Exit fullscreen mode In an imperative program with no defined rules regarding side effects, we must read the definition of the function to understand what it does, thus losing the type-based reasoning benefit. Furthermore, the moment we call the trustMeNoSideEffectHere function, the side effect immediately happens. We have to make sure the environment is ready right before calling the function, otherwise, we are exposed to undesired behaviors. In functional programs, since functions are pure (i.e. no side effects), they must return a value, otherwise, they are pretty much useless. In addition, determinism is a key aspect of functional programming. We cannot allow a function to trigger a side effect just by calling it. As developers, we want to control when the side effect happens (remember, side effects must happen at some point, otherwise the program is pointless). How can we make the trustMeNoSideEffectHere function pure, and control when the side effect (i.e. global state mutation) happens? One way of doing it would be to wrap some parts of this function in another function, making it "lazy": function trustMeNoSideEffectHere (): () => number { let n = 21 return () => { window . foo . bar ++ // mutating the global state = side effect return n * 2 } } Enter fullscreen mode Exit fullscreen mode What happens when we call trustMeNoSideEffectHere() ? We get a value of type () => number , that we can store in a variable: const res : () => number = trustMeNoSideEffectHere () Enter fullscreen mode Exit fullscreen mode Did anything happen? No. The global state has not been mutated yet since we have not called res() yet. Though, we changed the definition of trustMeNoSideEffectHere to make it pure: it always returns the same value, a function. Granted, if we call the function twice, we will get different references for the inner function: trustMeNoSideEffectHere() === trustMeNoSideEffectHere() would be false. So technically, we do not return the "same" value. Still, since functions equality is a complex topic, let us assume that the values are equivalent here, and move on. Now that the function is deterministic, we can write a unit test, although it is not very useful in this case: expect ( trustMeNoSideEffectHere ()). to . be . a ( ' function ' ) Enter fullscreen mode Exit fullscreen mode Imagine you are testing the launchNuclearWarheads function. It is pretty nice to make sure that calling launchNuclearWarheads() does not do anything, and that it requires an extra step to actually end life on Earth. The moment we are calling res() , the side effect will happen, thus propagating the non-determinism to the parent functions. At this point, it is not possible to write unit tests for the main , serviceA , and serviceB functions. What can we do to make these functions deterministic? We can apply the same strategy as before: returning functions that wrap the side effect (cf. the blue wrapping function on the following picture). We managed to make the serviceA and serviceB functions side-effect-free. Only the main function is impure and performs side effects, which is convenient: now we know where all the side effects actually happen in the program. Chaining side effects What happens when we want to chain side effects? For example: First we want to ask for the user's name Then we want to perform some API call with the user's name (e.g. to retrieve some information regarding its origin) Finally we want to display the result on the screen Again, we can use the same technique: make any side effect lazy by wrapping it inside a function. (here we are assuming the code is run in a browser) function askForUserName (): () => string { return () => prompt ( ' What is your name? ' ) } function getUserNameOrigin ( userName : string ): () => Promise < string > { const sanitizedName = userName . toLowerCase () return () => fetch ( `/get-origin/ ${ sanitizedName } ` ) . then ( res => res . json ()) . then ( res => res . userNameOriginText ) } function displayResult ( text : string ): () => void { return () => { document . getElementById ( ' origin-text ' )?. innerText = text } } function originNameService (): () => Promise < void > { return () => { const lazyUserName = askForUserName () const lazyGetUserNameOrigin = getUserNameOrigin ( lazyUserName ()) return lazyGetUserNameOrigin () . then ( originText => { const lazyDisplayResult = displayResult ( originText ) lazyDisplayResult () }) } } function main (): void { const lazyOriginNameService = originNameService () lazyOriginNameService () } Enter fullscreen mode Exit fullscreen mode Here, only the main function is non-deterministic, the remaining functions are all side-effect-free, thanks to the wrapper functions. That being said, writing tests for these pure functions would not be very useful, as we would not test their actual behavior: expect ( askForUserName ()). to . be . a ( ' function ' ) expect ( getUserNameOrigin ( ' foo ' )). to . be . a ( ' function ' ) expect ( displayResult ( ' bar ' )). to . be . a ( ' function ' ) Enter fullscreen mode Exit fullscreen mode To overcome this, we could use Dependency Injection, a.k.a DI. This is a bit out-of-scope for this article, but essentially we would pass the actual effect (i.e. prompt , fetch ...) as a dependency of the function, and we would use a mocked/controlled version of this effect for writing the unit tests. For example: interface Dependencies { prompt : ( text : string ) => string } function askForUserName ({ prompt }: Dependencies ): () => string { return () => prompt ( ' What is your name? ' ) } const lazyUserName : () => string = askForUserName ({ prompt : window . prompt }) Enter fullscreen mode Exit fullscreen mode const fakePrompt = ( text : string ) => ' foo ' const lazyUserName : () => string = askForUserName ({ prompt : fakePrompt }) expect ( lazyUserName ). to . be . a ( ' function ' ) expect ( lazyUserName ()). to . equal ( ' foo ' ) Enter fullscreen mode Exit fullscreen mode What if we wrote a simple type alias for the introduction of laziness? type IO < A > = () => A function askForUserName (): IO < string > { ... } function getUserNameOrigin ( userName : string ): IO < Promise < string >> { ... } function displayResult ( text : string ): IO < void > { ... } function originNameService (): IO < Promise < void >> { ... } function main (): void { ... } Enter fullscreen mode Exit fullscreen mode And what about a special alias for the lazy promises? type Task < A > = IO < Promise < A >> function askForUserName (): IO < string > { ... } function getUserNameOrigin ( userName : string ): Task < string > { ... } function displayResult ( text : string ): IO < void > { ... } function originNameService (): Task < void > { ... } function main (): void { ... } Enter fullscreen mode Exit fullscreen mode The type of main is () => void , so in other words, main: IO<void> . Also, askForUserName and originNameService do not take any argument, so they are already lazy. We can simplify their definition with: const askForUserName : IO < string > = ... const originNameService : Task < void > = ... const main : IO < void > = ... Enter fullscreen mode Exit fullscreen mode Now imagine if these IO and Task types had some behavior attached to them, allowing us to do something such as: const originNameService : Task < void > = Task . fromIO ( askForUserName ) . andThen ( getUserNameOrigin ) . andThen ( text => Task . fromIO ( displayResult ( text ))) Enter fullscreen mode Exit fullscreen mode This is how we can contain side effect declarations inside values, that we can compose with other values, thus describing more and more complex side effects. To run the side effects, we can simply run the final value obtained from the composition: // assuming we have some behavior attached to our Task<void> value originNameService . runEffect () Enter fullscreen mode Exit fullscreen mode Here, I presented one approach we can use to handle side effects. We have separated their declaration from their execution , giving us more flexibility to combine these effects, and more control over what happens in our program. Functional languages and libraries provide "standard" tools to deal with side effects, so we do not have to build them ourselves. Haskell has a built-in IO data type. The fp-ts TypeScript library provides both IO for synchronous side effects, and Task for asynchronous ones. The cats-effect Scala library provides the IO data type as well. Writing functional programs will undoubtedly lead you to use these data types to deal with side effects. The goal is to have as many side-effect-free functions as possible in our programs, by leveraging side effects declarations, and isolating side effects execution. This concludes the chapter on side effects. Hopefully, you enjoyed it and understood what side effects are, and how you can deal with them. The next step is to talk about function purity and referential transparency. As always, feel free to leave a comment :) See you then! Special thanks to Tristan Sallé for reviewing the draft of this article. Photo by Xavi Cabrera on Unsplash . Pictures made with Excalidraw . Demystifying Functional Programming (8 Part Series) 1 Introduction 2 What is Functional Programming? ... 4 more parts... 3 Why should we learn and use FP? 4 Function composition and higher-order function 5 Declarative vs imperative 6 Side effects 7 Function purity and referential transparency 8 Data immutability 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 Benoit Ruiz Follow Location France Work Software Engineer at Datadog Joined Aug 2, 2020 More from Benoit Ruiz Data immutability # functional # programming # tutorial # typescript Function purity and referential transparency # functional # programming # tutorial # typescript Equivalent of Scala's for-comprehension using fp-ts # typescript # scala # functional # 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 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://twitter.com/ibn_abubakre | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:06 |
https://dev.to/t/beginners/page/2#for-questions | Beginners Page 2 - 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 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 Advanced Spreadsheet Implementation with RevoGrid in React Michael Turner Michael Turner Michael Turner Follow Jan 12 Advanced Spreadsheet Implementation with RevoGrid in React # react # webdev # beginners # tutorial Comments Add Comment 6 min read Building Feature-Rich Data Tables with jQWidgets React Grid Michael Turner Michael Turner Michael Turner Follow Jan 12 Building Feature-Rich Data Tables with jQWidgets React Grid # react # webdev # javascript # beginners Comments Add Comment 6 min read Advanced Data Management with GigaTables React: Building Enterprise-Grade Tables Michael Turner Michael Turner Michael Turner Follow Jan 12 Advanced Data Management with GigaTables React: Building Enterprise-Grade Tables # webdev # programming # beginners # tutorial Comments Add Comment 6 min read Guide to get started with Retrieval-Augmented Generation (RAG) Neweraofcoding Neweraofcoding Neweraofcoding Follow Jan 12 Guide to get started with Retrieval-Augmented Generation (RAG) # beginners # llm # rag # tutorial Comments Add Comment 2 min read Building Advanced Data Tables with AG Grid in React Michael Turner Michael Turner Michael Turner Follow Jan 12 Building Advanced Data Tables with AG Grid in React # react # tutorial # beginners # programming Comments Add Comment 6 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 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 How I Would Learn Web3 From Scratch Today (Without Wasting a Year) Emir Taner Emir Taner Emir Taner Follow Jan 12 How I Would Learn Web3 From Scratch Today (Without Wasting a Year) # web3 # beginners # devops # machinelearning 2 reactions Comments Add Comment 2 min read Introduction to DevOps #5. DevOps Tooling Landscape Himanshu Bhatt Himanshu Bhatt Himanshu Bhatt Follow Jan 12 Introduction to DevOps #5. DevOps Tooling Landscape # discuss # devops # cloud # beginners 6 reactions Comments Add Comment 3 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 Understanding Okta Tokens Manikanta Yarramsetti Manikanta Yarramsetti Manikanta Yarramsetti Follow Jan 12 Understanding Okta Tokens # api # beginners # security Comments Add Comment 2 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 Inside Git: How It Works and the Role of the `.git` Folder Umar Hayat Umar Hayat Umar Hayat Follow Jan 12 Inside Git: How It Works and the Role of the `.git` Folder # git # beginners # tutorial # learning 1 reaction Comments Add Comment 4 min read Stop Building Ugly Apps: Create a Modern Python Dashboard in 15 Minutes 📊 Larry Larry Larry Follow Jan 12 Stop Building Ugly Apps: Create a Modern Python Dashboard in 15 Minutes 📊 # python # datavisualization # beginners # ui Comments Add Comment 3 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 Java Variables Kesavarthini Kesavarthini Kesavarthini Follow Jan 12 Java Variables # java # beginners # learning # programming Comments Add Comment 1 min read Python Selenium and Its Architecture, Significance of the python virtual environment NandithaShri S.k NandithaShri S.k NandithaShri S.k Follow Jan 12 Python Selenium and Its Architecture, Significance of the python virtual environment # webdev # beginners # python # career Comments Add Comment 3 min read Introduction to DevOps #2. Life Before DevOps Himanshu Bhatt Himanshu Bhatt Himanshu Bhatt Follow Jan 12 Introduction to DevOps #2. Life Before DevOps # discuss # devops # cloud # beginners 6 reactions Comments Add Comment 3 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 Cloud Computing for Beginners: A Simple Guide for Students & New Developers ☁️ Sahinur Sahinur Sahinur Follow Jan 12 Cloud Computing for Beginners: A Simple Guide for Students & New Developers ☁️ # cloud # azure # beginners # developer Comments Add Comment 2 min read Electric Industry Operation GeunWooJeon GeunWooJeon GeunWooJeon Follow Jan 12 Electric Industry Operation # beginners # devjournal # learning Comments Add Comment 4 min read Starting My Learning Journey in Tech Hassan Olamide Hassan Olamide Hassan Olamide Follow Jan 12 Starting My Learning Journey in Tech # beginners # devjournal # learning # webdev 1 reaction 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-0001/#pep-editors | PEP 1 – PEP Purpose and Guidelines | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 1 Toggle light / dark / auto colour theme PEP 1 – PEP Purpose and Guidelines Author : Barry Warsaw, Jeremy Hylton, David Goodger, Alyssa Coghlan Status : Active Type : Process Created : 13-Jun-2000 Post-History : 21-Mar-2001, 29-Jul-2002, 03-May-2003, 05-May-2012, 07-Apr-2013 Table of Contents What is a PEP? PEP Audience PEP Types PEP Workflow Python’s Steering Council Python’s Core Developers Python’s BDFL PEP Editors Start with an idea for Python Submitting a PEP Discussing a PEP PEP Review & Resolution PEP Maintenance What belongs in a successful PEP? PEP Formats and Templates PEP Header Preamble Auxiliary Files Changing Existing PEPs Transferring PEP Ownership PEP Editor Responsibilities & Workflow Copyright What is a PEP? PEP stands for Python Enhancement Proposal. A PEP is a design document providing information to the Python community, or describing a new feature for Python or its processes or environment. The PEP should provide a concise technical specification of the feature and a rationale for the feature. We intend PEPs to be the primary mechanisms for proposing major new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Python. The PEP author is responsible for building consensus within the community and documenting dissenting opinions. Because the PEPs are maintained as text files in a versioned repository, their revision history is the historical record of the feature proposal. This historical record is available by the normal git commands for retrieving older revisions, and can also be browsed on GitHub . PEP Audience The typical primary audience for PEPs are the core developers of the CPython reference interpreter and their elected Steering Council, as well as developers of other implementations of the Python language specification. However, other parts of the Python community may also choose to use the process (particularly for Informational PEPs) to document expected API conventions and to manage complex design coordination problems that require collaboration across multiple projects. PEP Types There are three kinds of PEP: A Standards Track PEP describes a new feature or implementation for Python. It may also describe an interoperability standard that will be supported outside the standard library for current Python versions before a subsequent PEP adds standard library support in a future version. An Informational PEP describes a Python design issue, or provides general guidelines or information to the Python community, but does not propose a new feature. Informational PEPs do not necessarily represent a Python community consensus or recommendation, so users and implementers are free to ignore Informational PEPs or follow their advice. A Process PEP describes a process surrounding Python, or proposes a change to (or an event in) a process. Process PEPs are like Standards Track PEPs but apply to areas other than the Python language itself. They may propose an implementation, but not to Python’s codebase; they often require community consensus; unlike Informational PEPs, they are more than recommendations, and users are typically not free to ignore them. Examples include procedures, guidelines, changes to the decision-making process, and changes to the tools or environment used in Python development. Any meta-PEP is also considered a Process PEP. PEP Workflow Python’s Steering Council There are several references in this PEP to the “Steering Council” or “Council”. This refers to the current members of the elected Steering Council described in PEP 13 , in their role as the final authorities on whether or not PEPs will be accepted or rejected. Python’s Core Developers There are several references in this PEP to “core developers”. This refers to the currently active Python core team members described in PEP 13 . Python’s BDFL Previous versions of this PEP used the title “BDFL-Delegate” for PEP decision makers. This was a historical reference to Python’s previous governance model, where all design authority ultimately derived from Guido van Rossum, the original creator of the Python programming language. By contrast, the Steering Council’s design authority derives from their election by the currently active core developers. Now, PEP-Delegate is used in place of BDFL-Delegate. PEP Editors The PEP editors are individuals responsible for managing the administrative and editorial aspects of the PEP workflow (e.g. assigning PEP numbers and changing their status). See PEP Editor Responsibilities & Workflow for details. PEP editorship is by invitation of the current editors, and they can be contacted by mentioning @python/pep-editors on GitHub. All of the PEP workflow can be conducted via the GitHub PEP repository issues and pull requests. Start with an idea for Python The PEP process begins with a new idea for Python. It is highly recommended that a single PEP contain a single key proposal or new idea; the more focused the PEP, the more successful it tends to be. Most enhancements and bug fixes don’t need a PEP and can be submitted directly to the Python issue tracker . The PEP editors reserve the right to reject PEP proposals if they appear too unfocused or too broad. If in doubt, split your PEP into several well-focused ones. Each PEP must have a champion – someone who writes the PEP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The PEP champion (a.k.a. Author) should first attempt to ascertain whether the idea is PEP-able. Posting to the Ideas category of the Python Discourse is usually the best way to go about this, unless a more specialized venue is appropriate, such as the Typing category (for static typing ideas) or Packaging category (for packaging ideas) on the Python Discourse. Vetting an idea publicly before going as far as writing a PEP is meant to save the potential author time. Many ideas have been brought forward for changing Python that have been rejected for various reasons. Asking the Python community first if an idea is original helps prevent too much time being spent on something that is guaranteed to be rejected based on prior discussions (searching the internet does not always do the trick). It also helps to make sure the idea is applicable to the entire community and not just the author. Just because an idea sounds good to the author does not mean it will work for most people in most areas where Python is used. Once the champion has asked the Python community as to whether an idea has any chance of acceptance, a draft PEP should be presented to the appropriate venue mentioned above. This gives the author a chance to flesh out the draft PEP to make properly formatted, of high quality, and to address initial concerns about the proposal. Submitting a PEP Following the above initial discussion, the workflow varies based on whether any of the PEP’s co-authors are core developers. If one or more of the PEP’s co-authors are core developers, they are responsible for following the process outlined below. Otherwise (i.e. none of the co-authors are core developers), then the PEP author(s) will need to find a sponsor for the PEP. Ideally, a core developer sponsor is identified, but non-core sponsors may also be selected with the approval of the Steering Council. Members of the GitHub “PEP editors” team and members of the Typing Council ( PEP 729 ) are pre-approved to be sponsors. The sponsor’s job is to provide guidance to the PEP author to help them through the logistics of the PEP process (somewhat acting like a mentor). Being a sponsor does not disqualify that person from becoming a co-author or PEP-Delegate later on (but not both). The sponsor of a PEP is recorded in the “Sponsor:” field of the header. Once the sponsor or the core developer(s) co-authoring the PEP deem the PEP ready for submission, the proposal should be submitted as a draft PEP via a GitHub pull request . The draft must be written in PEP style as described below, else it will fail review immediately (although minor errors may be corrected by the editors). The standard PEP workflow is: You, the PEP author, fork the PEP repository , and create a file named pep- NNNN .rst that contains your new PEP. NNNN should be the next available PEP number not used by a published or in-PR PEP. In the “PEP:” header field, enter the PEP number that matches your filename as your draft PEP number. In the “Type:” header field, enter “Standards Track”, “Informational”, or “Process” as appropriate, and for the “Status:” field enter “Draft”. For full details, see PEP Header Preamble . Update .github/CODEOWNERS such that any co-author(s) or sponsors with write access to the PEP repository are listed for your new file. This ensures any future pull requests changing the file will be assigned to them. Push this to your GitHub fork and submit a pull request. The PEP editors review your PR for structure, formatting, and other errors. For a reST-formatted PEP, PEP 12 is provided as a template. It also provides a complete introduction to reST markup that is used in PEPs. Approval criteria are: It is sound and complete. The ideas must make technical sense. The editors do not consider whether they seem likely to be accepted. The title accurately describes the content. The PEP’s language (spelling, grammar, sentence structure, etc.) and code style (examples should match PEP 7 & PEP 8 ) should be correct and conformant. The PEP text will be automatically checked for correct reStructuredText formatting when the pull request is submitted. PEPs with invalid reST markup will not be approved. Editors are generally quite lenient about this initial review, expecting that problems will be corrected by the reviewing process. Note: Approval of the PEP is no guarantee that there are no embarrassing mistakes! Correctness is the responsibility of authors and reviewers, not the editors. If the PEP isn’t ready for approval, an editor will send it back to the author for revision, with specific instructions. Once approved, they will assign your PEP a number. Once the review process is complete, and the PEP editors approve it (note that this is not the same as accepting your PEP!), they will squash commit your pull request onto main. The PEP editors will not unreasonably deny publication of a PEP. Reasons for denying PEP status include duplication of effort, being technically unsound, not providing proper motivation or addressing backwards compatibility, or not in keeping with the Python philosophy. The Steering Council can be consulted during the approval phase, and are the final arbiter of a draft’s PEP-ability. Developers with write access to the PEP repository may claim PEP numbers directly by creating and committing a new PEP. When doing so, the developer must handle the tasks that would normally be taken care of by the PEP editors (see PEP Editor Responsibilities & Workflow ). This includes ensuring the initial version meets the expected standards for submitting a PEP. Alternately, even developers should submit PEPs via pull request. When doing so, you are generally expected to handle the process yourself; if you need assistance from PEP editors, mention @python/pep-editors on GitHub. As updates are necessary, the PEP author can check in new versions if they (or a collaborating developer) have write access to the PEP repository . Getting a PEP number assigned early can be useful for ease of reference, especially when multiple draft PEPs are being considered at the same time. Standards Track PEPs consist of two parts, a design document and a reference implementation. It is generally recommended that at least a prototype implementation be co-developed with the PEP, as ideas that sound good in principle sometimes turn out to be impractical when subjected to the test of implementation. Discussing a PEP As soon as a PEP number has been assigned and the draft PEP is committed to the PEP repository , a discussion thread for the PEP should be created to provide a central place to discuss and review its contents, and the PEP should be updated so that the Discussions-To header links to it. The PEP authors (or sponsor, if applicable) may select any reasonable venue for the discussion, so long as the the following criteria are met: The forum is appropriate to the PEP’s topic. The thread is publicly available on the web so that all interested parties can participate. The discussion is subject to the Python Community Code of Conduct . A direct link to the current discussion thread is provided in the PEP under the Discussions-To header. The PEPs category of the Python Discourse is the preferred choice for most new PEPs, whereas historically the Python-Dev mailing list was commonly used. Some specialized topics have specific venues, such as the Typing category and the Packaging category on the Python Discourse for typing and packaging PEPs, respectively. If the PEP authors are unsure of the best venue, the PEP Sponsor and PEP editors can advise them accordingly. If a PEP undergoes a significant re-write or other major, substantive changes to its proposed specification, a new thread should typically be created in the chosen venue to solicit additional feedback. If this occurs, the Discussions-To link must be updated and a new Post-History entry added pointing to this new thread. If it is not chosen as the discussion venue, a brief announcement post should be made to the PEPs category with at least a link to the rendered PEP and the Discussions-To thread when the draft PEP is committed to the repository and if a major-enough change is made to trigger a new thread. PEP authors are responsible for collecting community feedback on a PEP before submitting it for review. However, to avoid long-winded and open-ended discussions, strategies such as soliciting private or more narrowly-tailored feedback in the early design phase, collaborating with other community members with expertise in the PEP’s subject matter, and picking an appropriately-specialized discussion for the PEP’s topic (if applicable) should be considered. PEP authors should use their discretion here. Once the PEP is assigned a number and committed to the PEP repository, substantive issues should generally be discussed on the canonical public thread, as opposed to private channels, GitHub pull request reviews or unrelated venues. This ensures everyone can follow and contribute, avoids fragmenting the discussion, and makes sure it is fully considered as part of the PEP review process. Comments, support, concerns and other feedback on this designated thread are a critical part of what the Steering Council or PEP-Delegate will consider when reviewing the PEP. PEP Review & Resolution Once the authors have completed a PEP, they may request a review for style and consistency from the PEP editors. However, content review and acceptance of the PEP is ultimately the responsibility of the Steering Council, which is formally initiated by opening a Steering Council issue once the authors (and sponsor, if any) determine the PEP is ready for final review and resolution. To expedite the process in selected cases (e.g. when a change is clearly beneficial and ready to be accepted, but the PEP hasn’t been formally submitted for review yet), the Steering Council may also initiate a PEP review, first notifying the PEP author(s) and giving them a chance to make revisions. The final authority for PEP approval is the Steering Council. However, whenever a new PEP is put forward, any core developer who believes they are suitably experienced to make the final decision on that PEP may offer to serve as its PEP-Delegate by notifying the Steering Council of their intent. If the Steering Council approves their offer, the PEP-Delegate will then have the authority to approve or reject that PEP. For PEPs related to the Python type system, the Typing Council ( PEP 729 ) provides a recommendation to the Steering Council. To request such a recommendation, open an issue on the Typing Council issue tracker . The term “PEP-Delegate” is used under the Steering Council governance model for the PEP’s designated decision maker, who is recorded in the “PEP-Delegate” field in the PEP’s header. The term “BDFL-Delegate” is a deprecated alias for PEP-Delegate, a legacy of the time when when Python was led by a BDFL . Any legacy references to “BDFL-Delegate” should be treated as equivalent to “PEP-Delegate”. An individual offering to nominate themselves as a PEP-Delegate must notify the relevant authors and (when present) the sponsor for the PEP, and submit their request to the Steering Council (which can be done via a new issue ). Those taking on this responsibility are free to seek additional guidance from the Steering Council at any time, and are also expected to take the advice and perspectives of other core developers into account. The Steering Council will generally approve such self-nominations by default, but may choose to decline them. Possible reasons for the Steering Council declining a self-nomination as PEP-Delegate include, but are not limited to, perceptions of a potential conflict of interest (e.g. working for the same organisation as the PEP submitter), or simply considering another potential PEP-Delegate to be more appropriate. If core developers (or other community members) have concerns regarding the suitability of a PEP-Delegate for any given PEP, they may ask the Steering Council to review the delegation. If no volunteer steps forward, then the Steering Council will approach core developers (and potentially other Python community members) with relevant expertise, in an attempt to identify a candidate that is willing to serve as PEP-Delegate for that PEP. If no suitable candidate can be found, then the PEP will be marked as Deferred until one is available. Previously appointed PEP-Delegates may choose to step down, or be asked to step down by the Council, in which case a new PEP-Delegate will be appointed in the same manner as for a new PEP (including deferral of the PEP if no suitable replacement can be found). In the event that a PEP-Delegate is asked to step down, this will overrule any prior acceptance or rejection of the PEP, and it will revert to Draft status. When such standing delegations are put in place, the Steering Council will maintain sufficient public records to allow subsequent Councils, the core developers, and the wider Python community to understand the delegations that currently exist, why they were put in place, and the circumstances under which they may no longer be needed. For a PEP to be accepted it must meet certain minimum criteria. It must be a clear and complete description of the proposed enhancement. The enhancement must represent a net improvement. The proposed implementation, if applicable, must be solid and must not complicate the interpreter unduly. Finally, a proposed enhancement must be “pythonic” in order to be accepted by the Steering Council. (However, “pythonic” is an imprecise term; it may be defined as whatever is acceptable to the Steering Council. This logic is intentionally circular.) See PEP 2 for standard library module acceptance criteria. Except where otherwise approved by the Steering Council, pronouncements of PEP resolution will be posted to the PEPs category on the Python Discourse . Once a PEP has been accepted, the reference implementation must be completed. When the reference implementation is complete and incorporated into the main source code repository, the status will be changed to “Final”. To allow gathering of additional design and interface feedback before committing to long term stability for a language feature or standard library API, a PEP may also be marked as “Provisional”. This is short for “Provisionally Accepted”, and indicates that the proposal has been accepted for inclusion in the reference implementation, but additional user feedback is needed before the full design can be considered “Final”. Unlike regular accepted PEPs, provisionally accepted PEPs may still be Rejected or Withdrawn even after the related changes have been included in a Python release . Wherever possible, it is considered preferable to reduce the scope of a proposal to avoid the need to rely on the “Provisional” status (e.g. by deferring some features to later PEPs), as this status can lead to version compatibility challenges in the wider Python ecosystem. PEP 411 provides additional details on potential use cases for the Provisional status. A PEP can also be assigned the status “Deferred”. The PEP author or an editor can assign the PEP this status when no progress is being made on the PEP. Once a PEP is deferred, a PEP editor can reassign it to draft status. A PEP can also be “Rejected”. Perhaps after all is said and done it was not a good idea. It is still important to have a record of this fact. The “Withdrawn” status is similar - it means that the PEP author themselves has decided that the PEP is actually a bad idea, or has accepted that a competing proposal is a better alternative. When a PEP is Accepted, Rejected or Withdrawn, the PEP should be updated accordingly. In addition to updating the Status field, at the very least the Resolution header should be added with a direct link to the relevant post making a decision on the PEP. PEPs can also be superseded by a different PEP, rendering the original obsolete. This is intended for Informational PEPs, where version 2 of an API can replace version 1. The possible paths of the status of PEPs are as follows: While not shown in the diagram, “Accepted” PEPs may technically move to “Rejected” or “Withdrawn” even after acceptance. This will only occur if the implementation process reveals fundamental flaws in the design that were not noticed prior to acceptance of the PEP. Unlike Provisional PEPs, these transitions are only permitted if the accepted proposal has not been included in a Python release - released changes must instead go through the regular deprecation process (which may require a new PEP providing the rationale for the deprecation). Some Informational and Process PEPs may also have a status of “Active” if they are never meant to be completed. E.g. PEP 1 (this PEP). PEP Maintenance In general, PEPs are no longer substantially modified after they have reached the Accepted, Final, Rejected or Superseded state. Once resolution is reached, a PEP is considered a historical document rather than a living specification. Formal documentation of the expected behavior should be maintained elsewhere, such as the Language Reference for core features, the Library Reference for standard library modules or the PyPA Specifications for packaging. If changes based on implementation experience and user feedback are made to Standards track PEPs while in the Provisional or (with SC approval) Accepted state, they should be noted in the PEP, such that the PEP accurately describes the implementation at the point where it is marked Final. Active (Informational and Process) PEPs may be updated over time to reflect changes to development practices and other details. The precise process followed in these cases will depend on the nature and purpose of the PEP in question. Occasionally, a Deferred or even a Withdrawn PEP may be resurrected with major updates, but it is often better to just propose a new one. What belongs in a successful PEP? Each PEP should have the following parts/sections: Preamble – RFC 2822 style headers containing meta-data about the PEP, including the PEP number, a short descriptive title (limited to a maximum of 44 characters), the names, and optionally the contact info for each author, etc. Abstract – a short (~200 word) description of the technical issue being addressed. Motivation – The motivation is critical for PEPs that want to change the Python language, library, or ecosystem. It should clearly explain why the existing language specification is inadequate to address the problem that the PEP solves. This can include collecting documented support for the PEP from important projects in the Python ecosystem. PEP submissions without sufficient motivation may be rejected. Rationale – The rationale fleshes out the specification by describing why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale should provide evidence of consensus within the community and discuss important objections or concerns raised during discussion. Specification – The technical specification should describe the syntax and semantics of any new language feature. The specification should be detailed enough to allow competing, interoperable implementations for at least the current major Python platforms (CPython, Jython, IronPython, PyPy). Backwards Compatibility – All PEPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The PEP must explain how the author proposes to deal with these incompatibilities. PEP submissions without a sufficient backwards compatibility treatise may be rejected outright. Security Implications – If there are security concerns in relation to the PEP, those concerns should be explicitly written out to make sure reviewers of the PEP are aware of them. How to Teach This – For a PEP that adds new functionality or changes language behavior, it is helpful to include a section on how to teach users, new and experienced, how to apply the PEP to their work. This section may include key points and recommended documentation changes that would help users adopt a new feature or migrate their code to use a language change. Reference Implementation – The reference implementation must be completed before any PEP is given status “Final”, but it need not be completed before the PEP is accepted. While there is merit to the approach of reaching consensus on the specification and rationale before writing code, the principle of “rough consensus and running code” is still useful when it comes to resolving many discussions of API details. The final implementation must include test code and documentation appropriate for either the Python language reference or the standard library reference. Rejected Ideas – Throughout the discussion of a PEP, various ideas will be proposed which are not accepted. Those rejected ideas should be recorded along with the reasoning as to why they were rejected. This both helps record the thought process behind the final version of the PEP as well as preventing people from bringing up the same rejected idea again in subsequent discussions. In a way this section can be thought of as a breakout section of the Rationale section that is focused specifically on why certain ideas were not ultimately pursued. Open Issues – While a PEP is in draft, ideas can come up which warrant further discussion. Those ideas should be recorded so people know that they are being thought about but do not have a concrete resolution. This helps make sure all issues required for the PEP to be ready for consideration are complete and reduces people duplicating prior discussion. Acknowledgements – Useful to thank and acknowledge people who have helped develop, discuss, or draft the PEP, or for any other purpose. The section can be used to recognise contributors to the work who are not co-authors. Footnotes – A collection of footnotes cited in the PEP, and a place to list non-inline hyperlink targets. Copyright/license – Each new PEP must be placed under a dual license of public domain and CC0-1.0-Universal (see this PEP for an example). PEP Formats and Templates PEPs are UTF-8 encoded text files using the reStructuredText format. reStructuredText allows for rich markup that is still quite easy to read, but also results in good-looking and functional HTML. PEP 12 contains instructions and a PEP template . The PEP text files are automatically converted to HTML (via a Sphinx -based build system ) for easier online reading . PEP Header Preamble Each PEP must begin with an RFC 2822 style header preamble. The headers must appear in the following order. Headers marked with “*” are optional and are described below. All other headers are required. PEP: <pep number> Title: <pep title> Author: <list of authors' names and optionally, email addrs> * Sponsor: <name of sponsor> * PEP-Delegate: <PEP delegate's name> Discussions-To: <URL of current canonical discussion thread> Status: <Draft | Active | Accepted | Provisional | Deferred | Rejected | Withdrawn | Final | Superseded> Type: <Standards Track | Informational | Process> * Topic: <Governance | Packaging | Release | Typing> * Requires: <pep numbers> Created: <date created on, in dd-mmm-yyyy format> * Python-Version: <version number> Post-History: <dates, in dd-mmm-yyyy format, inline-linked to PEP discussion threads> * Replaces: <pep number> * Superseded-By: <pep number> * Resolution: <date in dd-mmm-yyyy format, linked to the acceptance/rejection post> The Author header lists the names, and optionally the email addresses of all the authors/owners of the PEP. The format of the Author header values must be: Random J. User <random@example.com> if the email address is included, and just: Random J. User if the address is not given. Most PEP authors use their real name, but if you prefer a different name and use it consistently in discussions related to the PEP, feel free to use it here. If there are multiple authors, each should be on a separate line following RFC 2822 continuation line conventions. Note that personal email addresses in PEPs will be obscured as a defense against spam harvesters. The Sponsor field records which developer (core, or otherwise approved by the Steering Council) is sponsoring the PEP. If one of the authors of the PEP is a core developer then no sponsor is necessary and thus this field should be left out. The PEP-Delegate field is used to record the individual appointed by the Steering Council to make the final decision on whether or not to approve or reject a PEP. Note: The Resolution header is required for Standards Track PEPs only. It contains a URL that should point to an email message or other web resource where the pronouncement about (i.e. approval or rejection of) the PEP is made. The Discussions-To header provides the URL to the current canonical discussion thread for the PEP. For email lists, this should be a direct link to the thread in the list’s archives, rather than just a mailto: or hyperlink to the list itself. The Type header specifies the type of PEP: Standards Track, Informational, or Process. The optional Topic header lists the special topic, if any, the PEP belongs under. See the Topic Index for the existing topics. The Created header records the date that the PEP was assigned a number, while Post-History is used to record the dates of and corresponding URLs to the Discussions-To threads for the PEP, with the former as the linked text, and the latter as the link target. Both sets of dates should be in dd-mmm-yyyy format, e.g. 14-Aug-2001 . Standards Track PEPs will typically have a Python-Version header which indicates the version of Python that the feature will be released with. Standards Track PEPs without a Python-Version header indicate interoperability standards that will initially be supported through external libraries and tools, and then potentially supplemented by a later PEP to add support to the standard library. Informational and Process PEPs do not need a Python-Version header. PEPs may have a Requires header, indicating the PEP numbers that this PEP depends on. PEPs may also have a Superseded-By header indicating that a PEP has been rendered obsolete by a later document; the value is the number of the PEP that replaces the current document. The newer PEP must have a Replaces header containing the number of the PEP that it rendered obsolete. Auxiliary Files PEPs may include auxiliary files such as diagrams. Such files should be named pep-XXXX-Y.ext , where “XXXX” is the PEP number, “Y” is a serial number (starting at 1), and “ext” is replaced by the actual file extension (e.g. “png”). Alternatively, all support files may be placed in a subdirectory called pep-XXXX , where “XXXX” is the PEP number. When using a subdirectory, there are no constraints on the names used in files. Changing Existing PEPs Draft PEPs are freely open for discussion and proposed modification, at the discretion of the authors, until submitted to the Steering Council or PEP-Delegate for review and resolution. Substantive content changes should generally be first proposed on the PEP’s discussion thread listed in its Discussions-To header, while copyedits and corrections can be submitted as a GitHub issue or GitHub pull request . PEP authors with write access to the PEP repository can update the PEPs themselves by using git push or a GitHub PR to submit their changes. For guidance on modifying other PEPs, consult the PEP Maintenance section. See the Contributing Guide for additional details, and when in doubt, please check first with the PEP author and/or a PEP editor. Transferring PEP Ownership It occasionally becomes necessary to transfer ownership of PEPs to a new champion. In general, it is preferable to retain the original author as a co-author of the transferred PEP, but that’s really up to the original author. A good reason to transfer ownership is because the original author no longer has the time or interest in updating it or following through with the PEP process, or has fallen off the face of the ‘net (i.e. is unreachable or not responding to email). A bad reason to transfer ownership is because the author doesn’t agree with the direction of the PEP. One aim of the PEP process is to try to build consensus around a PEP, but if that’s not possible, an author can always submit a competing PEP. If you are interested in assuming ownership of a PEP, you can also do this via pull request. Fork the PEP repository , make your ownership modification, and submit a pull request. You should mention both the original author and @python/pep-editors in a comment on the pull request. (If the original author’s GitHub username is unknown, use email.) If the original author doesn’t respond in a timely manner, the PEP editors will make a unilateral decision (it’s not like such decisions can’t be reversed :). PEP Editor Responsibilities & Workflow A PEP editor must be added to the @python/pep-editors group on GitHub and must watch the PEP repository . Note that developers with write access to the PEP repository may handle the tasks that would normally be taken care of by the PEP editors. Alternately, even developers may request assistance from PEP editors by mentioning @python/pep-editors on GitHub. For each new PEP that comes in an editor does the following: Make sure that the PEP is either co-authored by a core developer, has a core developer as a sponsor, or has a sponsor specifically approved for this PEP by the Steering Council. Read the PEP to check if it is ready: sound and complete. The ideas must make technical sense, even if they don’t seem likely to be accepted. The title should accurately describe the content. The file name extension is correct (i.e. .rst ). Ensure that everyone listed as a sponsor or co-author of the PEP who has write access to the PEP repository is added to .github/CODEOWNERS . Skim the PEP for obvious defects in language (spelling, grammar, sentence structure, etc.), and code style (examples should conform to PEP 7 & PEP 8 ). Editors may correct problems themselves, but are not required to do so (reStructuredText syntax is checked by the repo’s CI). If a project is portrayed as benefiting from or supporting the PEP, make sure there is some direct indication from the project included to make the support clear. This is to avoid a PEP accidentally portraying a project as supporting a PEP when in fact the support is based on conjecture. If the PEP isn’t ready, an editor will send it back to the author for revision, with specific instructions. If reST formatting is a problem, ask the author(s) to use PEP 12 as a template and resubmit. Once the PEP is ready for the repository, a PEP editor will: Check that the author has selected a valid PEP number or assign them a number if they have not (almost always just the next available number, but sometimes it’s a special/joke number, like 666 or 3141). Remember that numbers below 100 are meta-PEPs. Check that the author has correctly labeled the PEP’s type (“Standards Track”, “Informational”, or “Process”), and marked its status as “Draft”. Ensure all CI build and lint checks pass without errors, and there are no obvious issues in the rendered preview output. Merge the new (or updated) PEP. Inform the author of the next steps (open a discussion thread and update the PEP with it, post an announcement, etc). Updates to existing PEPs should be submitted as a GitHub pull request . Many PEPs are written and maintained by developers with write access to the Python codebase. The PEP editors monitor the PEP repository for changes, and correct any structure, grammar, spelling, or markup mistakes they see. PEP editors don’t pass judgment on PEPs. They merely do the administrative & editorial part (which is generally a low volume task). Resources: Index of Python Enhancement Proposals Following Python’s Development Python Developer’s Guide 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-0001.rst Last modified: 2025-08-09 01:23:33 GMT Contents What is a PEP? PEP Audience PEP Types PEP Workflow Python’s Steering Council Python’s Core Developers Python’s BDFL PEP Editors Start with an idea for Python Submitting a PEP Discussing a PEP PEP Review & Resolution PEP Maintenance What belongs in a successful PEP? PEP Formats and Templates PEP Header Preamble Auxiliary Files Changing Existing PEPs Transferring PEP Ownership PEP Editor Responsibilities & Workflow Copyright Page Source (GitHub) | 2026-01-13T08:49:06 |
https://twitter.com/intent/tweet?text=%22React%20Router%20V5%20vs%20V6%22%20by%20%40arunava_modak%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Farunavamodak%2Freact-router-v5-vs-v6-dp0 | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:06 |
https://peps.python.org/pep-0731/ | PEP 731 – C API Working Group Charter | peps.python.org Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals Python » PEP Index » PEP 731 Toggle light / dark / auto colour theme PEP 731 – C API Working Group Charter Author : Guido van Rossum <guido at python.org>, Petr Viktorin <encukou at gmail.com>, Victor Stinner <vstinner at python.org>, Steve Dower <steve.dower at python.org>, Irit Katriel <irit at python.org> Discussions-To : Discourse thread Status : Active Type : Process Topic : Governance Created : 11-Oct-2023 Post-History : 13-Oct-2023 , 23-May-2024 , 19-Jun-2024 Resolution : Discourse message Table of Contents Abstract Epigraph Motivation Specification Members Mandate Operations and process Relationship with the Steering Council Amendments Contact Copyright Abstract This PEP proposes to establish the C API Working Group: a small committee of Python core developers responsible for overseeing and coordinating the development and maintenance of the Python C API. The working group will maintain documentation, test suites and tooling related to Python’s C API. As delegated by the Steering Council it is the deciding body for changes to the C API, from the addition or removal of individual API functions, types, etc., to the acceptance of new designs of a more or less radical nature. The working group’s mandate is to represent the interests of all Python users, but especially all maintainers of code that uses Python’s C API, whether in the context of CPython, using an alternate Python implementation, or using a binding framework for other programming languages (such as C++ and Rust). The working group serves at the pleasure of the Python Steering Council. This document serves as the working group’s charter. Epigraph KEEPER Stop! Who would cross the Bridge of Death must answer me these questions three, ere the other side he see. What was Python named after? What was Python 2’s EOL? What is the optimal strategy to evolve the CPython C API? LANCELOT Auuuuuuuugh! Motivation Despite many discussions and in-person meetings at core developer sprints and Language Summits, and a thorough inventory of the problems and stakeholders of the C API, no consensus has been reached about many contentious issues, including, but not limited to: Conventions for designing new API functions; How to deal with compatibility; What’s the best strategy for handling errors; The future of the Stable ABI and the Limited API; Whether to switch to a handle-based API convention (and how). The general feeling is that there are too many stakeholders, proposals, requirements, constraints, and conventions, to make progress without having a small trusted group of deciders. At the 2023 Language Summit in Salt Lake City it was decided to start work on an inventory of problems . At the 2023 core developer sprint in Brno this work is more or less finished and after a discussion it appeared that the next step is to establish a working group to ensure that we’re not stymied forever. The Steering Council has indicated its desire to delegate decisions about the C API to such a working group, anticipating its formal establishment. Specification We propose the creation of a new group, the C API Working Group. This group will be responsible for overseeing and coordinating the development and maintenance of the Python C API. It will do this by establishing the principles underpinning the work and publishing guidelines that the core developers can refer to. The “operations and process” section below describes how the working group operates and how it is governed. Members The members of the working group are: Erlend Aasland Petr Viktorin Serhiy Storchaka Steve Dower Victor Stinner Mandate The working group’s mandate is to ensure that the Python C API is suitable for all users of and contributors to the API, without unduly preferencing one group over another. The working group will identify exemplar stakeholders, their needs and preferences, and will determine a plan for meeting these needs equitably and sustainably. It will oversee execution of the plan. Operations and process The working group has at least three members, comprised of prominent Python core developers. The members should consider the needs of the various stakeholders carefully. The Steering Council appoints the initial working group. There is no term limit for working group members. Working group members may resign their position at any time, for any reason. There is an expectation that the membership will change over time. To determine replacements, nominations will be collected from the core developer community. Self-nominations are allowed. The existing working group will then decide the replacement member(s) from the nominees. The expectation is that this will be done by fiat, but the working group can choose a replacement by any means they see fit, including a vote. The working group remains accountable to the Steering Council. At any point, for any reason, the Steering Council could (publicly or privately) make a specific change or request a non-specific change to the composition of the working group. We acknowledge that this is not a particularly democratic structure and puts a lot of faith in the working group. However, the Python community has a long history of success with structures that are not fully democratic! We believe that self-governance, cycling of membership, and accountability to the Steering Council will be sufficient to ensure that the C API workgroup is meeting the needs of the community. The working group may operate primarily through reviews of GitHub issues and PRs. Regular meetings are likely not necessary, but the working group may set up video calls, a private chat, or whatever other mechanism they decide upon internally. The working group should aim for transparency, posting all decisions publicly on discuss.python.org , with a rationale if possible. Before making a decision, the working group should give all interested community members (as examples of different categories of stakeholders) a chance to weigh in. There should be at least a week between the start of a discussion and the working group’s decision. Relationship with the Steering Council Just like today, the Python Steering Council remains responsible for the overall direction of the Python C API and continues to decide on PEPs related to the C API, using the standard PEP review process (community discussion, etc.). The C API working group provides written opinions and recommendations to the Steering Council on PEPs related to the C API. However, the working group can make smaller C API changes directly. The Steering Council may also choose to delegate decisions on some PEPs to the working group (exactly as any other PEP delegation). Amendments This PEP serves as a charter for the working group. Changes to its operation can be made either through a new PEP or through a change to this PEP. In either case, the change will be decided upon by the Steering Council after discussion in the community. Contact To ask the C API Working Group for a decision, community members may open an issue in the capi-workgroup/decisions repository. 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-0731.rst Last modified: 2025-10-08 12:21:13 GMT Contents Abstract Epigraph Motivation Specification Members Mandate Operations and process Relationship with the Steering Council Amendments Contact Copyright Page Source (GitHub) | 2026-01-13T08:49:06 |
https://www.python.org/community/logos/#site-map | 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://wiki.python.org/moin/PythonConferences | PythonConferences - Python Wiki Search: PythonConferences PythonConferences FrontPage RecentChanges FindPage HelpContents PythonConferences Page Immutable Page Comments Info Attachments More Actions: Raw Text Print View Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ ------------------------ Remove Spam Revert to this revision ------------------------ SlideShow User Login Python Conferences The Python community tends to organize regional events around the world. Established events such as PyCon US and EuroPython have since been joined by other regional conferences, and Python often features prominently in various open source conferences. This page aims to be the most complete list of Python conferences around the world and can be edited by the community . Want to organize an event in your community? Read our guide to running a conference . In particular, if you are considering starting a " PyCon " named conference, please see the PSF PyCon Trademark Guidelines and the PSF Trademark FAQs . If you are planning a Python conference event, please check the dates in the Python Event Calendars to see whether there are any overlaps and submit your event to the calendars . Also see the PythonEvents page for more schedule information. Please keep these lists mostly sorted alphabetically. It is fine to place the most prominent and largest events at the top of the respective listings. Contents Python Conferences Regional Python Conferences Africa Americas Asia Australasia Europe Online Topic Conferences AI & Data Science Django Education & Outreach Web Frameworks Science Python at Open Source Conferences Regional Python Conferences Africa PyCon Africa (Africa) PyCon Ghana (Ghana) PyCon Kenya (Kenya) PyCon MEA (Middle East & Africa) (Dubai, UAE) PyCon Namibia (Namibia) PyCon NG (Nigeria) PyCon Niger (Niger) PyCon Somalia (Somalia) PyCon ZA (South Africa) PyCon Tanzania (Tanzania) PyCon Togo (Togo) PyCon Uganda (Uganda) PyConZim (Zimbabwe) DjangoCon Africa (Africa) - focuses on the Django web framework Americas PyCon US (US and Canada) - largest international Python event; also see the wiki page: PyCon US AfroPython Conf (Brazil) DePy (Chicago, United States) inactive North Bay Python (California, United States) PyBay (California, United States) PyBeach (California, United States) PyCascades (West Coast United States and Canada) PyCon Argentina (Argentina) PyCon Bolivia (Bolivia) inactive PyCon Canada (Canada) inactive PyCon Chile (Chile) PyCon Colombia (Colombia) PyCon Latam (Mexiko) PyCon Panama (Panama) PyCon Uruguay (Uruguay) inactive PyCon Venezuela (Venezuela) inactive PyCarolinas (North and South Carolina, United States) inactive PyGotham (New York, United States) PyOhio (Ohio, United States) PyTexas (Texas, United States) PythonBrasil and Python Brazilian Community site (Brazil) SciPy (USA) - focuses on scientific applications Wagtail Space US (USA) - focuses on the Wagtail CMS, which is written in Python Asia PyCon APAC or Asia Pacific (Asia Pacific) - also see the wiki page: PyConAPAC PyCon Dhaka (Bangladesh) inactive PyCon Cameroon (Cameroon) inactive PyCon China (China) PyCon Hong Kong (Hong Kong) PyCon India (India) PyCon ID (Indonesia) PyCon Iran (Iran) PyCon Israel (Israel) PyCon Japan (Japan) PyCon Korea (South Korea) PyCon Malaysia (Malaysia) PyCon NP (Nepal) PyCon MEA (Middle East & Africa) (Dubai, UAE) inactive PyCon Pakistan (Pakistan) inactive PyCon Philippines (Philippines) PyCon Singapore (Singapore) PyCon Taiwan (Taiwan) PyCon Thailand (Thailand) PyCon Turkey (Turkey) PyDelhi Conference (Delhi, India) SciPy India (India) Australasia Kiwi PyCon (New Zealand) PyCon Australia (Australia) Europe EuroPython (Europe) - largest European event; also see the wiki page: EuroPython EuroSciPy conference (Germany, France) - focuses on scientific applications DjangoCon Europe (Europe) - focuses on the Django web framework DragonPy (Slovenia) GeoPython (Switzerland) - focuses on geo-spatial applications Moscow Python Conf (Moscow, Russia) PiterPy (Saint Petersburg, Russia) PyCon Balkan (Serbia) PyCon BY (Belarus) inactive PyCon CZ (Czechia) PyCon DK (Denmark) inactive PyCon DE (Germany) PyCon FI (Finland) inactive PyCon FR (France) PyCon Ireland (Ireland) PyCon Italia (Italy) PyCon LT (Lithuania) PyCon NL (The Netherlands) PyCon PL (Poland) PyCon PT (Portugal) PyCon Russia (Russia) PyCon SK (Slovakia) PyCon ES (Spain) PyCon SE (Sweden) PyCon UK (United Kingdom) PyCon UA (Ukraine) inactive PyGrunn (The Netherlands) PythonCamp (Germany) PythonFOSDEM (Belgium) - Python dev room at FOSDEM Python San Sebastian (Basque Country, Spain) inactive Python Unconference (Germany) inactive RuPy (Poland) - a hybrid Ruby/Python conference inactive Swiss Python Summit (Switzerland) Wagtail Space NL (The Netherlands) - focuses on the Wagtail CMS, which is written in Python Online XtremePython (Online) Topic Conferences Regularly happening larger topic events should also be listed in the above regional sections. AI & Data Science Focus on using Python for AI and data science. PyData - lists many events around the world Django Focus on the Django web framework . DjangoCon Africa (Africa) DjangoCon Europe (Europe) DjangoCon US (USA) DjangoCon Africa (Africa) DjangoGirls (world-wide) - DjangoGirls regularly organize smaller educational events for learning Django Education & Outreach Events focusing on Python education and outreach. DjangoGirls (world-wide) - DjangoGirls regularly organize smaller educational events for learning Django PyLadies (world-wide) - PyLadies chapters regularly organize meetups and workshops for learning Python PyLadiesCon (online) - PyLadies conference Web Frameworks Focus on the Plone web framework : Plone Conference Focus on the Wagtail CMS : Wagtail Space (world-wide) - Hub for Wagtail conferences Wagtail Space US (USA) Wagtail Space NL (The Netherlands) Science Focus on using Python in science. SciPy (USA) - focuses on scientific applications EuroSciPy conference (Germany, France) - focuses on scientific applications GeoPython (Switzerland) - focuses on geo and GIS applications PyHPC (world-wide) - focus on high performance computing PyHEP (world-wide, online) - focus on particle physics Python at Open Source Conferences Python has often been featured in the following conference series and events: ConFoo Web Techno Conference (Canada) - features a Python track EuroOSCON (Europe) - features a Python track inactive FOSDEM (Belgium) - features a Python dev room OSCON (USA) - features a Python track inactive OSDC AU (Australia) - a very strong Python track PythonConferences (last edited 2025-12-30 21:02:41 by MarcAndreLemburg ) MoinMoin Powered Python Powered GPL licensed Valid HTML 4.01 Unable to edit the page? See the FrontPage for instructions. | 2026-01-13T08:49:06 |
https://twitter.com/intent/tweet?text=%22CSS%20Modules%20vs%20CSS-in-JS.%20Who%20wins%3F%22%20by%20Sergey%20%23DEVCommunity%20https%3A%2F%2Fdev.to%2Falexsergey%2Fcss-modules-vs-css-in-js-who-wins-3n25 | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:06 |
https://dev.to/t/beginners/page/2#promotional-rules | Beginners Page 2 - 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 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 Advanced Spreadsheet Implementation with RevoGrid in React Michael Turner Michael Turner Michael Turner Follow Jan 12 Advanced Spreadsheet Implementation with RevoGrid in React # react # webdev # beginners # tutorial Comments Add Comment 6 min read Building Feature-Rich Data Tables with jQWidgets React Grid Michael Turner Michael Turner Michael Turner Follow Jan 12 Building Feature-Rich Data Tables with jQWidgets React Grid # react # webdev # javascript # beginners Comments Add Comment 6 min read Advanced Data Management with GigaTables React: Building Enterprise-Grade Tables Michael Turner Michael Turner Michael Turner Follow Jan 12 Advanced Data Management with GigaTables React: Building Enterprise-Grade Tables # webdev # programming # beginners # tutorial Comments Add Comment 6 min read Guide to get started with Retrieval-Augmented Generation (RAG) Neweraofcoding Neweraofcoding Neweraofcoding Follow Jan 12 Guide to get started with Retrieval-Augmented Generation (RAG) # beginners # llm # rag # tutorial Comments Add Comment 2 min read Building Advanced Data Tables with AG Grid in React Michael Turner Michael Turner Michael Turner Follow Jan 12 Building Advanced Data Tables with AG Grid in React # react # tutorial # beginners # programming Comments Add Comment 6 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 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 How I Would Learn Web3 From Scratch Today (Without Wasting a Year) Emir Taner Emir Taner Emir Taner Follow Jan 12 How I Would Learn Web3 From Scratch Today (Without Wasting a Year) # web3 # beginners # devops # machinelearning 2 reactions Comments Add Comment 2 min read Introduction to DevOps #5. DevOps Tooling Landscape Himanshu Bhatt Himanshu Bhatt Himanshu Bhatt Follow Jan 12 Introduction to DevOps #5. DevOps Tooling Landscape # discuss # devops # cloud # beginners 6 reactions Comments Add Comment 3 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 Understanding Okta Tokens Manikanta Yarramsetti Manikanta Yarramsetti Manikanta Yarramsetti Follow Jan 12 Understanding Okta Tokens # api # beginners # security Comments Add Comment 2 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 Inside Git: How It Works and the Role of the `.git` Folder Umar Hayat Umar Hayat Umar Hayat Follow Jan 12 Inside Git: How It Works and the Role of the `.git` Folder # git # beginners # tutorial # learning 1 reaction Comments Add Comment 4 min read Stop Building Ugly Apps: Create a Modern Python Dashboard in 15 Minutes 📊 Larry Larry Larry Follow Jan 12 Stop Building Ugly Apps: Create a Modern Python Dashboard in 15 Minutes 📊 # python # datavisualization # beginners # ui Comments Add Comment 3 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 Java Variables Kesavarthini Kesavarthini Kesavarthini Follow Jan 12 Java Variables # java # beginners # learning # programming Comments Add Comment 1 min read Python Selenium and Its Architecture, Significance of the python virtual environment NandithaShri S.k NandithaShri S.k NandithaShri S.k Follow Jan 12 Python Selenium and Its Architecture, Significance of the python virtual environment # webdev # beginners # python # career Comments Add Comment 3 min read Introduction to DevOps #2. Life Before DevOps Himanshu Bhatt Himanshu Bhatt Himanshu Bhatt Follow Jan 12 Introduction to DevOps #2. Life Before DevOps # discuss # devops # cloud # beginners 6 reactions Comments Add Comment 3 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 Cloud Computing for Beginners: A Simple Guide for Students & New Developers ☁️ Sahinur Sahinur Sahinur Follow Jan 12 Cloud Computing for Beginners: A Simple Guide for Students & New Developers ☁️ # cloud # azure # beginners # developer Comments Add Comment 2 min read Electric Industry Operation GeunWooJeon GeunWooJeon GeunWooJeon Follow Jan 12 Electric Industry Operation # beginners # devjournal # learning Comments Add Comment 4 min read Starting My Learning Journey in Tech Hassan Olamide Hassan Olamide Hassan Olamide Follow Jan 12 Starting My Learning Journey in Tech # beginners # devjournal # learning # webdev 1 reaction 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://twitter.com/pycon | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:49:06 |
https://dev.to/t/beginners/page/2#main-content | Beginners Page 2 - 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 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 Advanced Spreadsheet Implementation with RevoGrid in React Michael Turner Michael Turner Michael Turner Follow Jan 12 Advanced Spreadsheet Implementation with RevoGrid in React # react # webdev # beginners # tutorial Comments Add Comment 6 min read Building Feature-Rich Data Tables with jQWidgets React Grid Michael Turner Michael Turner Michael Turner Follow Jan 12 Building Feature-Rich Data Tables with jQWidgets React Grid # react # webdev # javascript # beginners Comments Add Comment 6 min read Advanced Data Management with GigaTables React: Building Enterprise-Grade Tables Michael Turner Michael Turner Michael Turner Follow Jan 12 Advanced Data Management with GigaTables React: Building Enterprise-Grade Tables # webdev # programming # beginners # tutorial Comments Add Comment 6 min read Guide to get started with Retrieval-Augmented Generation (RAG) Neweraofcoding Neweraofcoding Neweraofcoding Follow Jan 12 Guide to get started with Retrieval-Augmented Generation (RAG) # beginners # llm # rag # tutorial Comments Add Comment 2 min read Building Advanced Data Tables with AG Grid in React Michael Turner Michael Turner Michael Turner Follow Jan 12 Building Advanced Data Tables with AG Grid in React # react # tutorial # beginners # programming Comments Add Comment 6 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 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 How I Would Learn Web3 From Scratch Today (Without Wasting a Year) Emir Taner Emir Taner Emir Taner Follow Jan 12 How I Would Learn Web3 From Scratch Today (Without Wasting a Year) # web3 # beginners # devops # machinelearning 2 reactions Comments Add Comment 2 min read Introduction to DevOps #5. DevOps Tooling Landscape Himanshu Bhatt Himanshu Bhatt Himanshu Bhatt Follow Jan 12 Introduction to DevOps #5. DevOps Tooling Landscape # discuss # devops # cloud # beginners 6 reactions Comments Add Comment 3 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 Understanding Okta Tokens Manikanta Yarramsetti Manikanta Yarramsetti Manikanta Yarramsetti Follow Jan 12 Understanding Okta Tokens # api # beginners # security Comments Add Comment 2 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 Inside Git: How It Works and the Role of the `.git` Folder Umar Hayat Umar Hayat Umar Hayat Follow Jan 12 Inside Git: How It Works and the Role of the `.git` Folder # git # beginners # tutorial # learning 1 reaction Comments Add Comment 4 min read Stop Building Ugly Apps: Create a Modern Python Dashboard in 15 Minutes 📊 Larry Larry Larry Follow Jan 12 Stop Building Ugly Apps: Create a Modern Python Dashboard in 15 Minutes 📊 # python # datavisualization # beginners # ui Comments Add Comment 3 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 Java Variables Kesavarthini Kesavarthini Kesavarthini Follow Jan 12 Java Variables # java # beginners # learning # programming Comments Add Comment 1 min read Python Selenium and Its Architecture, Significance of the python virtual environment NandithaShri S.k NandithaShri S.k NandithaShri S.k Follow Jan 12 Python Selenium and Its Architecture, Significance of the python virtual environment # webdev # beginners # python # career Comments Add Comment 3 min read Introduction to DevOps #2. Life Before DevOps Himanshu Bhatt Himanshu Bhatt Himanshu Bhatt Follow Jan 12 Introduction to DevOps #2. Life Before DevOps # discuss # devops # cloud # beginners 6 reactions Comments Add Comment 3 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 Cloud Computing for Beginners: A Simple Guide for Students & New Developers ☁️ Sahinur Sahinur Sahinur Follow Jan 12 Cloud Computing for Beginners: A Simple Guide for Students & New Developers ☁️ # cloud # azure # beginners # developer Comments Add Comment 2 min read Electric Industry Operation GeunWooJeon GeunWooJeon GeunWooJeon Follow Jan 12 Electric Industry Operation # beginners # devjournal # learning Comments Add Comment 4 min read Starting My Learning Journey in Tech Hassan Olamide Hassan Olamide Hassan Olamide Follow Jan 12 Starting My Learning Journey in Tech # beginners # devjournal # learning # webdev 1 reaction 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/gikdev | Mohammad Mahdi Bahrami - 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 Mohammad Mahdi Bahrami A new teenage frontend developer... Location Qom, Iran Joined Joined on Mar 27, 2022 github website Work Student at highschool. Frontend dev at "ToloNajm" astrology-research company More info about @gikdev Badges 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 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 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 1 Week Community Wellness Streak For actively engaging with the community by posting at least 2 comments in a single week. Got it Close Skills/Languages Good at HTML, CSS, JS. Familiar to TS, TailwindCSS, ReactJS Currently learning React, Wouter, React Router, SWR.js, NextJS Post 0 posts published Comment 29 comments written Tag 61 tags followed Want to connect with Mohammad Mahdi Bahrami? Create an account to connect with Mohammad Mahdi Bahrami. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in 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/dinesh_04/learning-the-foliage-tool-in-unreal-engine-day-13-28p2 | Learning the Foliage Tool in Unreal Engine (Day 13) - 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 Dinesh Posted on Jan 8 Learning the Foliage Tool in Unreal Engine (Day 13) # gamedev # unrealengine # beginners # learning Game Designing and Development (9 Part Series) 1 🎮 Learning Game Development – Day 4 2 Understanding Starter Content and Selection Mode in Unreal Engine (Day 10) ... 5 more parts... 3 Actor Panel and Landscape Tool Basics in Unreal Engine (Day 11) 4 Learning Landscape Heightmaps and Sculpting Tools in Unreal Engine (Day 12) 5 Learning the Foliage Tool in Unreal Engine (Day 13) 6 Creating Materials in Unreal Engine 5 and Understanding ORM Textures (Day 14) 7 How I Turned a Static Character into a Moving One in Unreal Engine 8 Why My First Animation Blueprint Didn’t Work in Unreal Engine 9 How Speed Finally Made My Character Feel Alive I thought adding trees and grass would be easy. I just painted… and nothing appeared on slopes. Day 13 taught me why foliage doesn’t work everywhere by default. This post is part of my daily learning journey in game development. I’m sharing what I learn each day — the basics, the confusion, and the real progress — from the perspective of a beginner. What I tried / learned today On Day 13, I learned about the Foliage Tool in Unreal Engine . From the top-left menu, I opened Foliage Mode , or used the shortcut Shift + 3 . This opens the foliage panel, which is used to paint trees, grass, and plants directly in the viewport. Inside the foliage tool, I explored basic tools like: Paint (Brush) – to place foliage Erase – to remove foliage Select – to select placed foliage Below that, there are tool settings like brush size and strength. Further down, there is the Foliage List , which is empty at first. To add foliage, I: Dragged assets from the Content Browser , or Downloaded foliage assets from Fab and dragged them into the foliage list Once selected, I could paint foliage directly in the viewport. Each foliage type also has its own settings, like Density , Scale , and Random Rotation . What confused me When I tried painting foliage on slopes or hills , nothing appeared. It worked fine on flat ground, but not on angled surfaces. I thought something was broken. What worked or finally clicked A friend explained that foliage placement depends on slope angle settings . In the foliage instance settings, there is an option called Ground Slope Angle . By increasing the allowed slope angle, foliage can be painted on steeper surfaces. Once I adjusted that, foliage started appearing correctly on slopes. That small setting made everything clear. One lesson for beginners Foliage placement depends on surface angle Check Ground Slope Angle if foliage doesn’t appear Small settings can block big features Don’t assume tools are broken — check the options Slow progress — but I’m building a strong foundation. If you’re also learning game development, what was the first thing that confused you when you started? See you in the next post 🎮🚀 Game Designing and Development (9 Part Series) 1 🎮 Learning Game Development – Day 4 2 Understanding Starter Content and Selection Mode in Unreal Engine (Day 10) ... 5 more parts... 3 Actor Panel and Landscape Tool Basics in Unreal Engine (Day 11) 4 Learning Landscape Heightmaps and Sculpting Tools in Unreal Engine (Day 12) 5 Learning the Foliage Tool in Unreal Engine (Day 13) 6 Creating Materials in Unreal Engine 5 and Understanding ORM Textures (Day 14) 7 How I Turned a Static Character into a Moving One in Unreal Engine 8 Why My First Animation Blueprint Didn’t Work in Unreal Engine 9 How Speed Finally Made My Character Feel Alive 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 Dinesh Follow I am currently learning Game Designing and Development. I also share my learning journey on Medium site (profile link in website url). Location Chennai, India Education Monolith Research and Training labs Joined Dec 27, 2025 More from Dinesh How Speed Finally Made My Character Feel Alive # gamedev # unrealengine # beginners # animation Why My First Animation Blueprint Didn’t Work in Unreal Engine # gamedev # unrealengine # beginners # animation How I Turned a Static Character into a Moving One in Unreal Engine # gamedev # unrealengine # beginners # animation 💎 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://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies | Using HTTP cookies - HTTP | MDN Skip to main content Skip to search MDN HTML HTML: Markup language HTML reference Elements Global attributes Attributes See all… HTML guides Responsive images HTML cheatsheet Date & time formats See all… Markup languages SVG MathML XML CSS CSS: Styling language CSS reference Properties Selectors At-rules Values See all… CSS guides Box model Animations Flexbox Colors See all… Layout cookbook Column layouts Centering an element Card component See all… JavaScript JS JavaScript: Scripting language JS reference Standard built-in objects Expressions & operators Statements & declarations Functions See all… JS guides Control flow & error handing Loops and iteration Working with objects Using classes See all… Web APIs Web APIs: Programming interfaces Web API reference File system API Fetch API Geolocation API HTML DOM API Push API Service worker API See all… Web API guides Using the Web animation API Using the Fetch API Working with the History API Using the Web speech API Using web workers All All web technology Technologies Accessibility HTTP URI Web extensions WebAssembly WebDriver See all… Topics Media Performance Privacy Security Progressive web apps Learn Learn web development Frontend developer course Getting started modules Core modules MDN Curriculum Learn HTML Structuring content with HTML module Learn CSS CSS styling basics module CSS layout module Learn JavaScript Dynamic scripting with JavaScript module Tools Discover our tools Playground HTTP Observatory Border-image generator Border-radius generator Box-shadow generator Color format converter Color mixer Shape generator About Get to know MDN better About MDN Advertise with us Community MDN on GitHub Blog Toggle sidebar Web HTTP Guides Using HTTP cookies Theme OS default Light Dark English (US) Remember language Learn more Deutsch English (US) Español Français 日本語 한국어 Português (do Brasil) Русский 中文 (简体) 正體中文 (繁體) Using HTTP cookies A cookie (also known as a web cookie or browser cookie) is a small piece of data a server sends to a user's web browser. The browser may store cookies, create new cookies, modify existing ones, and send them back to the same server with later requests. Cookies enable web applications to store limited amounts of data and remember state information; by default the HTTP protocol is stateless . In this article we will explore the main uses of cookies, explain best practices for using them, and look at their privacy and security implications. In this article What cookies are used for Creating, removing, and updating cookies Security Privacy and tracking Cookie-related regulations See also What cookies are used for Typically, the server will use the contents of HTTP cookies to determine whether different requests come from the same browser/user and then issue a personalized or generic response as appropriate. The following describes a basic user sign-in system: The user sends sign-in credentials to the server, for example via a form submission. If the credentials are correct, the server updates the UI to indicate that the user is signed in, and responds with a cookie containing a session ID that records their sign-in status on the browser. At a later time, the user moves to a different page on the same site. The browser sends the cookie containing the session ID along with the corresponding request to indicate that it still thinks the user is signed in. The server checks the session ID and, if it is still valid, sends the user a personalized version of the new page. If it is not valid, the session ID is deleted and the user is shown a generic version of the page (or perhaps shown an "access denied" message and asked to sign in again). Cookies are mainly used for three purposes: Session management : User sign-in status, shopping cart contents, game scores, or any other user session-related details that the server needs to remember. Personalization : User preferences such as display language and UI theme. Tracking : Recording and analyzing user behavior. Data storage In the early days of the web when there was no other option, cookies were used for general client-side data storage purposes. Modern storage APIs are now recommended, for example the Web Storage API ( localStorage and sessionStorage ) and IndexedDB . They are designed with storage in mind, never send data to the server, and don't come with other drawbacks of using cookies for storage: Browsers are generally limited to a maximum number of cookies per domain (varies by browser, generally in the hundreds), and a maximum size per cookie (usually 4KB). Storage APIs can store larger amounts of data. Cookies are sent with every request, so they can worsen performance (for example on slow mobile data connections), especially if you have a lot of cookies set. Note: To see stored cookies (and other storage that a web page is using) you can use the Storage Inspector in Firefox Developer Tools, or the Application panel in Chrome Developer Tools. Creating, removing, and updating cookies After receiving an HTTP request, a server can send one or more Set-Cookie headers with the response, each one of which will set a separate cookie. A cookie is set by specifying a name-value pair like this: http Set-Cookie: <cookie-name>=<cookie-value> The following HTTP response instructs the receiving browser to store a pair of cookies: http HTTP/2.0 200 OK Content-Type: text/html Set-Cookie: yummy_cookie=chocolate Set-Cookie: tasty_cookie=strawberry [page content] Note: Find out how to use the Set-Cookie header in various server-side languages/frameworks: PHP , Node.js , Python , Ruby on Rails . When a new request is made, the browser usually sends previously stored cookies for the current domain back to the server within a Cookie HTTP header: http GET /sample_page.html HTTP/2.0 Host: www.example.org Cookie: yummy_cookie=chocolate; tasty_cookie=strawberry Removal: defining the lifetime of a cookie You can specify an expiration date or time period after which the cookie should be deleted and no longer sent. Depending on the attributes set within the Set-Cookie header when the cookies are created, they can be either permanent or session cookies: Permanent cookies are deleted after the date specified in the Expires attribute: http Set-Cookie: id=a3fWa; Expires=Thu, 31 Oct 2021 07:28:00 GMT; or after the period specified in the Max-Age attribute: http Set-Cookie: id=a3fWa; Max-Age=2592000 Note: Expires has been available for longer than Max-Age , however Max-Age is less error-prone, and takes precedence when both are set. The rationale behind this is that when you set an Expires date and time, they're relative to the client the cookie is being set on. If the server is set to a different time, this could cause errors. Session cookies — cookies without a Max-Age or Expires attribute – are deleted when the current session ends. The browser defines when the "current session" ends, and some browsers use session restoring when restarting. This can cause session cookies to last indefinitely. Note: If your site authenticates users, it should regenerate and resend session cookies, even ones that already exist, whenever a user authenticates. This approach helps prevent session fixation attacks, where a third-party can reuse a user's session. To immediately remove a cookie, set the cookie again with the same name, path, and domain (if specified), and set its Expires attribute to a date in the past or its Max-Age attribute to 0 or negative. This instructs the browser to delete the cookie right away. For example: http Set-Cookie: id=a3fWa; Max-Age=0 You can also clear all cookies associated with a registrable domain using the Clear-Site-Data response header. For example, the following header sent from https://foo.example.com/ would clear all cookies sent by example.com and all of its subdomains, such as all.bar.example.com . http Clear-Site-Data: "cookies" There are some techniques designed to recreate cookies after they're deleted. These are known as "zombie" cookies. These techniques violate the principles of user privacy and control, may violate data privacy regulations , and could expose a website using them to legal liability. Updating cookie values To update a cookie via HTTP, the server can send a Set-Cookie header with the existing cookie's name and a new value. For example: http Set-Cookie: id=new-value There are several reasons why you might want to do this, for example if a user has updated their preferences and the application wants to reflect the changes in client-side data (you could also do this with a client-side storage mechanism such as Web Storage ). Updating cookies via JavaScript In the browser, you can create new cookies via JavaScript using the Document.cookie property, or the asynchronous Cookie Store API . Note that all examples below use Document.cookie , as it is the most widely supported/established option. js document.cookie = "yummy_cookie=chocolate"; document.cookie = "tasty_cookie=strawberry"; You can also access existing cookies and set new values for them: js console.log(document.cookie); // logs "yummy_cookie=chocolate; tasty_cookie=strawberry" document.cookie = "yummy_cookie=blueberry"; console.log(document.cookie); // logs "tasty_cookie=strawberry; yummy_cookie=blueberry" For security purposes, you can't change cookie values by sending an updated Cookie header directly when initiating a request, for example, via fetch() or XMLHttpRequest . There are good reasons why you shouldn't allow JavaScript to modify cookies at all. You can prevent JavaScript from accessing a cookie by specifying the HttpOnly attribute during its creation. See the Security section for more details. Security When you store information in cookies, by default all cookie values are visible to, and can be changed by, the end user. You really don't want your cookies to be misused — for example accessed/modified by bad actors, or sent to domains where they shouldn't be sent. The potential consequences can range from annoying — apps not working or exhibiting strange behavior — to catastrophic. A criminal could for example steal a session ID and use it to set a cookie that makes it look like they are logged in as someone else, taking control of their bank or e-commerce account in the process. You can secure your cookies in a variety of ways, which are reviewed in this section. Block access to your cookies You can ensure that cookies are sent securely and aren't accessed by unintended parties or scripts in one of two ways: with the Secure attribute and the HttpOnly attribute: http Set-Cookie: id=a3fWa; Expires=Thu, 21 Oct 2021 07:28:00 GMT; Secure; HttpOnly A cookie with the Secure attribute is only sent to the server with an encrypted request over the HTTPS protocol. It's never sent with unsecured HTTP (except on localhost), which means man-in-the-middle attackers can't access it easily. Insecure sites (with http: in the URL) can't set cookies with the Secure attribute. However, don't assume that Secure prevents all access to sensitive information in cookies. For example, someone with access to the client's hard disk (or JavaScript if the HttpOnly attribute isn't set) can read and modify the information. A cookie with the HttpOnly attribute can't be accessed by JavaScript, for example using Document.cookie ; it can only be accessed when it reaches the server. Cookies that persist user sessions for example should have the HttpOnly attribute set — it would be really insecure to make them available to JavaScript. This precaution helps mitigate cross-site scripting ( XSS ) attacks. Note: Depending on the application, you may want to use an opaque identifier that the server looks up rather than storing sensitive information directly in cookies, or investigate alternative authentication/confidentiality mechanisms such as JSON Web Tokens . Define where cookies are sent The Domain and Path attributes define the scope of a cookie: what URLs the cookies are sent to. The Domain attribute specifies which server can receive a cookie. If specified, cookies are available on the specified server and its subdomains. For example, if you set Domain=mozilla.org from mozilla.org , cookies are available on that domain and subdomains like developer.mozilla.org . http Set-Cookie: id=a3fWa; Expires=Thu, 21 Oct 2021 07:28:00 GMT; Secure; HttpOnly; Domain=mozilla.org If the Set-Cookie header does not specify a Domain attribute, the cookies are available on the server that sets it but not on its subdomains . Therefore, specifying Domain is less restrictive than omitting it. Note that a server can only set the Domain attribute to its own domain or a parent domain, not to a subdomain or some other domain. So, for example, a server with domain foo.example.com could set the attribute to example.com or foo.example.com , but not bar.foo.example.com or elsewhere.com (the cookies would still be sent to subdomains such as bar.foo.example.com though). See Invalid domains for more details. The Path attribute indicates a URL path that must exist in the requested URL in order to send the Cookie header. For example: http Set-Cookie: id=a3fWa; Expires=Thu, 21 Oct 2021 07:28:00 GMT; Secure; HttpOnly; Path=/docs The %x2F ("/") character is considered a directory separator, and subdirectories match as well. For example, if you set Path=/docs , these request paths match: /docs /docs/ /docs/Web/ /docs/Web/HTTP But these request paths don't: / /docsets /fr/docs Note: The path attribute lets you control what cookies the browser sends based on the different parts of a site. It is not intended as a security measure, and does not protect against unauthorized reading of the cookie from a different path. Controlling third-party cookies with SameSite The SameSite attribute lets servers specify whether/when cookies are sent with cross-site requests — i.e., third-party cookies . Cross-site requests are requests where the site (the registrable domain) and/or the scheme (http or https) do not match the site the user is currently visiting. This includes requests sent when links are clicked on other sites to navigate to your site, and any request sent by embedded third-party content. SameSite helps to prevent leakage of information, preserving user privacy and providing some protection against cross-site request forgery attacks. It takes three possible values: Strict , Lax , and None : Strict causes the browser to only send the cookie in response to requests originating from the cookie's origin site. This should be used when you have cookies relating to functionality that will always be behind an initial navigation, such as authentication or storing shopping cart information. http Set-Cookie: cart=110045_77895_53420; SameSite=Strict Note: Cookies that are used for sensitive information should also have a short lifetime . Lax is similar, except the browser also sends the cookie when the user navigates to the cookie's origin site (even if the user is coming from a different site). This is useful for cookies affecting the display of a site — for example you might have partner product information along with an affiliate link on your website. When that link is followed to the partner website, they might want to set a cookie stating that the affiliate link was followed, which displays a reward banner and provides a discount if the product is purchased. http Set-Cookie: affiliate=e4rt45dw; SameSite=Lax None specifies that cookies are sent on both originating and cross-site requests. This is useful if you want to send cookies along with requests made from third-party content embedded in other sites, for example, ad-tech or analytics providers. Note that if SameSite=None is set then the Secure attribute must also be set — SameSite=None requires a secure context . http Set-Cookie: widget_session=7yjgj57e4n3d; SameSite=None; Secure; HttpOnly If no SameSite attribute is set, the cookie is treated as Lax by default. Cookie prefixes Because of the design of the cookie mechanism, a server can't confirm that a cookie was set from a secure origin or even tell where a cookie was originally set. An application on a subdomain can set a cookie with the Domain attribute, which gives access to that cookie on all other subdomains. This mechanism can be abused in a session fixation attack. As a defense-in-depth measure , you can use cookie prefixes to impose specific restrictions on a cookie's attributes in supporting user-agents. All cookie prefixes start with a double-underscore ( __ ) and end in a dash ( - ). Four prefixes are available: __Secure- : Cookies with names starting with __Secure- must be set with the Secure attribute by a secure page (HTTPS). __Host- : Cookies with names starting with __Host- must be set with the Secure attribute by a secure page (HTTPS). In addition, they must not have a Domain attribute specified, and the Path attribute must be set to / . This guarantees that such cookies are only sent to the host that set them, and not to any other host on the domain. It also guarantees that they are set host-wide and cannot be overridden on any path on that host. This combination yields a cookie that is as close as can be to treating the origin as a security boundary. __Http- : Cookies with names starting with __Http- must be set with the Secure flag by a secure page (HTTPS) and in addition must have the HttpOnly attribute set to prove that they were set via the Set-Cookie header (they can't be set or modified via JavaScript features such as Document.cookie or the Cookie Store API ). __Host-Http- : Cookies with names starting with __Host-Http- must be set with the Secure flag by a secure page (HTTPS) and must have the HttpOnly attribute set to prove that they were set via the Set-Cookie header. In addition, they also have the same restrictions as __Host- -prefixed cookies. This combination yields a cookie that is as close as can be to treating the origin as a security boundary while at the same time ensuring developers and server operators know that its scope is limited to HTTP requests. The browser will reject cookies with these prefixes that don't comply with their restrictions. As the application server only checks for a specific cookie name when determining if the user is authenticated or a CSRF token is correct, this effectively acts as a defense measure against session fixation . Note: On the server, the web application must check for the full cookie name including the prefix. User agents do not strip the prefix from the cookie before sending it in a request's Cookie header. For more information about cookie prefixes and the current state of browser support, see the Prefixes section of the Set-Cookie reference article . Privacy and tracking Earlier on we talked about how the SameSite attribute can be used to control when third-party cookies are sent, and that this can help preserve user privacy. Privacy is a very important consideration when building websites which, when done right, can build trust with your users. If done badly, it can completely erode that trust and cause all kinds of other problems. Third-party cookies can be set by third-party content embedded in sites via <iframe> s. They have many legitimate uses include sharing user profile information, counting ad impressions, or collecting analytics across different related domains. However, third-party cookies can also be used to create creepy, invasive user experiences. A third-party server can create a profile of a user's browsing history and habits based on cookies sent to it by the same browser when accessing multiple sites. The classic example is when you search for product information on one site and are then chased around the web by adverts for similar products wherever you go. Browser vendors know that users don't like this behavior, and as a result have all started to block third-party cookies by default, or at least made plans to go in that direction. Third-party cookies (or just tracking cookies) may also be blocked by other browser settings or extensions. Note: Cookie blocking can cause some third-party components (such as social media widgets) not to function as intended. As browsers impose further restrictions on third-party cookies, developers should start to look at ways to reduce their reliance on them. See our Third-party cookies article for detailed information on third-party cookies, the issues associated with them, and what alternatives are available. See our Privacy landing page for more information on privacy in general. Cookie-related regulations Legislation or regulations that cover the use of cookies include: The General Data Privacy Regulation (GDPR) in the European Union The ePrivacy Directive in the EU The California Consumer Privacy Act These regulations have global reach. They apply to any site on the World Wide Web that users from these jurisdictions access (the EU and California, with the caveat that California's law applies only to entities with gross revenue over 25 million USD, among things). These regulations include requirements such as: Notifying users that your site uses cookies. Allowing users to opt out of receiving some or all cookies. Allowing users to use the bulk of your service without receiving cookies. There may be other regulations that govern the use of cookies in your locality. The burden is on you to know and comply with these regulations. There are companies that offer "cookie banner" code that helps you comply with these regulations. Note: Companies should disclose the types of cookies they use on their sites for transparency purposes and to comply with regulations. For example, see Google's notice on the types of cookies it uses and Mozilla's Websites, Communications & Cookies Privacy Notice . See also Related HTTP headers: Set-Cookie , Cookie Related JavaScript APIs: Document.cookie , Navigator.cookieEnabled , Cookie Store API Third-party cookies Cookie specification: RFC 6265 Cookies, the GDPR, and the ePrivacy Directive Help improve MDN Was this page helpful to you? Yes No Learn how to contribute This page was last modified on Oct 8, 2025 by MDN contributors . View this page on GitHub • Report a problem with this content Filter sidebar HTTP Guides Overview of HTTP Evolution of HTTP A typical HTTP session HTTP messages Media types Common types Compression in HTTP HTTP caching HTTP authentication Using HTTP cookies Redirections in HTTP Conditional requests Range requests Client hints User-Agent reduction Compression Dictionary Transport Experimental Network Error Logging Experimental Content negotiation Default Accept values Browser detection using the UA string Connection management in HTTP/1.x Protocol upgrade mechanism Proxy servers and tunneling Proxy Auto-Configuration (PAC) file Security and privacy HTTP Observatory Practical implementation guides Permissions Policy Experimental Cross-Origin Resource Policy (CORP) IFrame credentialless Experimental Cross-Origin Resource Sharing (CORS) CORS errors Reason: CORS disabled Reason: CORS header 'Access-Control-Allow-Origin' does not match 'xyz' Reason: CORS header 'Access-Control-Allow-Origin' missing Reason: CORS header 'Origin' cannot be added Reason: CORS preflight channel did not succeed Reason: CORS request did not succeed Reason: CORS request external redirect not allowed Reason: CORS request not HTTP Reason: Credential is not supported if the CORS header 'Access-Control-Allow-Origin' is '*' Reason: Did not find method in CORS header 'Access-Control-Allow-Methods' Reason: expected 'true' in CORS header 'Access-Control-Allow-Credentials' Reason: invalid token 'xyz' in CORS header 'Access-Control-Allow-Headers' Reason: invalid token 'xyz' in CORS header 'Access-Control-Allow-Methods' Reason: missing token 'xyz' in CORS header 'Access-Control-Allow-Headers' from CORS preflight channel Reason: Multiple CORS header 'Access-Control-Allow-Origin' not allowed Content Security Policy (CSP) Errors and warnings Reference HTTP headers Accept Accept-CH Accept-Encoding Accept-Language Accept-Patch Accept-Post Accept-Ranges Access-Control-Allow-Credentials Access-Control-Allow-Headers Access-Control-Allow-Methods Access-Control-Allow-Origin Access-Control-Expose-Headers Access-Control-Max-Age Access-Control-Request-Headers Access-Control-Request-Method Activate-Storage-Access Age Allow Alt-Svc Alt-Used Attribution-Reporting-Eligible Deprecated Attribution-Reporting-Register-Source Deprecated Attribution-Reporting-Register-Trigger Deprecated Authorization Available-Dictionary Experimental Cache-Control Clear-Site-Data Connection Content-Digest Content-Disposition Content-DPR Non-standard Deprecated Content-Encoding Content-Language Content-Length Content-Location Content-Range Content-Security-Policy Content-Security-Policy-Report-Only Content-Type Cookie Critical-CH Experimental Cross-Origin-Embedder-Policy Cross-Origin-Opener-Policy Cross-Origin-Resource-Policy Date Device-Memory Non-standard Deprecated Dictionary-ID Experimental DNT Non-standard Deprecated Downlink Experimental DPR Non-standard Deprecated Early-Data Experimental ECT Experimental ETag Expect Expect-CT Deprecated Expires Forwarded From Host Idempotency-Key Experimental If-Match If-Modified-Since If-None-Match If-Range If-Unmodified-Since Integrity-Policy Integrity-Policy-Report-Only Keep-Alive Last-Modified Link Location Max-Forwards NEL Experimental No-Vary-Search Experimental Observe-Browsing-Topics Non-standard Deprecated Origin Origin-Agent-Cluster Permissions-Policy Experimental Pragma Deprecated Prefer Preference-Applied Priority Proxy-Authenticate Proxy-Authorization Range Referer Referrer-Policy Refresh Report-To Non-standard Deprecated Reporting-Endpoints Repr-Digest Retry-After RTT Experimental Save-Data Experimental Sec-Browsing-Topics Non-standard Deprecated Sec-CH-Device-Memory Experimental Sec-CH-DPR Experimental Sec-CH-Prefers-Color-Scheme Experimental Sec-CH-Prefers-Reduced-Motion Experimental Sec-CH-Prefers-Reduced-Transparency Experimental Sec-CH-UA Experimental Sec-CH-UA-Arch Experimental Sec-CH-UA-Bitness Experimental Sec-CH-UA-Form-Factors Experimental Sec-CH-UA-Full-Version Deprecated Sec-CH-UA-Full-Version-List Experimental Sec-CH-UA-Mobile Experimental Sec-CH-UA-Model Experimental Sec-CH-UA-Platform Experimental Sec-CH-UA-Platform-Version Experimental Sec-CH-UA-WoW64 Experimental Sec-CH-Viewport-Height Experimental Sec-CH-Viewport-Width Experimental Sec-CH-Width Experimental Sec-Fetch-Dest Sec-Fetch-Mode Sec-Fetch-Site Sec-Fetch-Storage-Access Sec-Fetch-User Sec-GPC Experimental Sec-Private-State-Token Experimental Sec-Private-State-Token-Crypto-Version Experimental Sec-Private-State-Token-Lifetime Experimental Sec-Purpose Sec-Redemption-Record Experimental Sec-Speculation-Tags Experimental Sec-WebSocket-Accept Sec-WebSocket-Extensions Sec-WebSocket-Key Sec-WebSocket-Protocol Sec-WebSocket-Version Server Server-Timing Service-Worker Service-Worker-Allowed Service-Worker-Navigation-Preload Set-Cookie Set-Login SourceMap Speculation-Rules Experimental Strict-Transport-Security Supports-Loading-Mode Experimental TE Timing-Allow-Origin Tk Non-standard Deprecated Trailer Transfer-Encoding Upgrade Upgrade-Insecure-Requests Use-As-Dictionary Experimental User-Agent Vary Via Viewport-Width Non-standard Deprecated Want-Content-Digest Want-Repr-Digest Warning Deprecated Width Non-standard Deprecated WWW-Authenticate X-Content-Type-Options X-DNS-Prefetch-Control Non-standard X-Forwarded-For Non-standard X-Forwarded-Host Non-standard X-Forwarded-Proto Non-standard X-Frame-Options X-Permitted-Cross-Domain-Policies Non-standard X-Powered-By Non-standard X-Robots-Tag Non-standard X-XSS-Protection Non-standard Deprecated HTTP request methods CONNECT DELETE GET HEAD OPTIONS PATCH POST PUT TRACE HTTP response status codes 100 Continue 101 Switching Protocols 102 Processing 103 Early Hints 200 OK 201 Created 202 Accepted 203 Non-Authoritative Information 204 No Content 205 Reset Content 206 Partial Content 207 Multi-Status 208 Already Reported 226 IM Used 300 Multiple Choices 301 Moved Permanently 302 Found 303 See Other 304 Not Modified 307 Temporary Redirect 308 Permanent Redirect 400 Bad Request 401 Unauthorized 402 Payment Required 403 Forbidden 404 Not Found 405 Method Not Allowed 406 Not Acceptable 407 Proxy Authentication Required 408 Request Timeout 409 Conflict 410 Gone 411 Length Required 412 Precondition Failed 413 Content Too Large 414 URI Too Long 415 Unsupported Media Type 416 Range Not Satisfiable 417 Expectation Failed 418 I'm a teapot 421 Misdirected Request 422 Unprocessable Content 423 Locked 424 Failed Dependency 425 Too Early 426 Upgrade Required 428 Precondition Required 429 Too Many Requests 431 Request Header Fields Too Large 451 Unavailable For Legal Reasons 500 Internal Server Error 501 Not Implemented 502 Bad Gateway 503 Service Unavailable 504 Gateway Timeout 505 HTTP Version Not Supported 506 Variant Also Negotiates 507 Insufficient Storage 508 Loop Detected 510 Not Extended 511 Network Authentication Required CSP directives base-uri block-all-mixed-content Deprecated child-src connect-src default-src fenced-frame-src Experimental font-src form-action frame-ancestors frame-src img-src manifest-src media-src object-src prefetch-src Non-standard Deprecated report-to report-uri Deprecated require-trusted-types-for sandbox script-src script-src-attr script-src-elem style-src style-src-attr style-src-elem trusted-types upgrade-insecure-requests worker-src Permissions-Policy directives Experimental accelerometer Experimental ambient-light-sensor Experimental aria-notify Experimental Non-standard attribution-reporting Deprecated autoplay Experimental bluetooth Experimental browsing-topics Non-standard Deprecated camera Experimental captured-surface-control Experimental compute-pressure Experimental cross-origin-isolated Experimental deferred-fetch Experimental deferred-fetch-minimal Experimental display-capture Experimental encrypted-media Experimental fullscreen Experimental gamepad Experimental geolocation Experimental gyroscope Experimental hid Experimental identity-credentials-get Experimental idle-detection Experimental language-detector Experimental local-fonts Experimental magnetometer Experimental microphone Experimental midi Experimental on-device-speech-recognition Experimental otp-credentials Experimental payment Experimental picture-in-picture Experimental private-state-token-issuance Experimental private-state-token-redemption Experimental publickey-credentials-create Experimental publickey-credentials-get Experimental screen-wake-lock Experimental serial Experimental speaker-selection Experimental storage-access Experimental summarizer Experimental translator Experimental usb Experimental web-share Experimental window-management Experimental xr-spatial-tracking Experimental HTTP resources and specifications Your blueprint for a better internet. MDN About Blog Mozilla careers Advertise with us MDN Plus Product help Contribute MDN Community Community resources Writing guidelines MDN Discord MDN on GitHub Developers Web technologies Learn web development Guides Tutorials Glossary Hacks blog Website Privacy Notice Telemetry Settings Legal Community Participation Guidelines Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation . Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license . | 2026-01-13T08:49:06 |
https://dev.to/iggredible/cookies-vs-local-storage-vs-session-storage-3gp3#local-storage-and-session-storage | Cookies vs Local Storage vs Session Storage - 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 Igor Irianto Posted on Mar 20, 2021 • Edited on Jun 3, 2021 Cookies vs Local Storage vs Session Storage # cookies # localstorage # sessionstorage # beginners Many of us have heard of Session Storage, Local Storage, and Cookies. But what exactly are they, what problems are they solving, and how are they different? Cookies In the beginning, the web used HTTP protocols to send messages (btw, SSL is more secure, you should use HTTPS instead of HTTP). These protocols are stateless protocols. In a stateless protocol, each request doesn't store any states, or "persisting information"; each request is its own island and it doesn't have idea about the other requests. Having a stateless protocol optimizes performance, but it also comes with a problem: what if you need to remember a user session? If you have darkMode: true or user_uuid: 12345abc , how can a server remember that if you're using a stateless protocol? With Cookies! A Cookie can be set from a HTTP header. Usually the server that you're trying to reach, if it has cookies, will send an HTTP header like this: Set-Cookie: choco_chip_cookie=its_delicious Enter fullscreen mode Exit fullscreen mode When your browser receives this header, it saves the choco_chip_cookie Cookie. Cookies are associated with websites. If websitea.com has cookie_a , you can't see cookie_a while you're in websiteb.com . You need to be in websitea.com . To see the Cookies you have, if you have Firefox, from your devtools, go to storage -> Cookies; if you have Chrome, from your devtools, go to Application -> storage -> Cookies. Most websites use Cookies, you should find some there (if not, go to a different site). Cookies can have an expiration date. Of course, you can set it to last effectively forever if you set it to a far future date: Set-Cookie: choco_chip_cookie=its_delicious; Expires=Mon, 28 Feb 2100 23:59:59GMT; Enter fullscreen mode Exit fullscreen mode One more Cookie behavior that you might need to know: your browser sends cookies on each request . When you visit https://example.com and you have to make 30 requests to download the HTML page and its 29 asset files, your browser will send your cookies (for https://example.com domain name) 30 times, one for each request. This only applies if you store your assets under the same domain name, like example.com/assets/images/cute-cats.svg , example.com/assets/stylesheets/widgets.css , etc. If you store your assets under a different domain / subdomain, like exampleassets.com/assets/stylesheets/widgets.css or static.example.com/assets/stylesheets/widgets.css , then your browser won't send the Cookies there. FYI, storing your assets in a different domain is a good strategy to improve your speed! The max size for Cookies are 4kb. This makes sense, because Cookies are being sent all the time. You don't want to send 3mb Cookie data to all 30 different requests when visiting a page. Even with this size cap, you should minimize Cookies as much as possible to reduce traffic. A popular usage for Cookie is to use a UUID for your website and run a separate server to store all the UUIDs to hold session information. A separate Redis server is a good alternative because it is fast. So when a user tries to go to example.com/user_settings , the user sends its Cookie for example.com , something like example_site_uuid=user_iggy_uuid , which then is read by your server, then your server can match it with the key in Redis to fetch the user session information for the server to use. Inside your Redis server, you would have something like: user_iggy_uuid: {darkMode: false, lastVisit: 01 January 2010, autoPayment: false, ...} . I highly encourage you to see it in action. Go to any web page (make sure it uses Cookies) using a Chrome / Firefox / any modern browser. Look at the cookies that you currently have. Now look at the Network tab and check out the request headers. You should see the same Cookies being sent. You can use Javascript to create cookies with document.cookie . document.cookie = "choco_chip_cookie=its_delicious"; document.cookie = "choco_donut=its_awesome"; console.log(document.cookie); Enter fullscreen mode Exit fullscreen mode In addition to Expires , Cookies have many more attribute you can give to do all sorts of things. If you want to learn more, check out the mozilla cookie page . Cookies can be accessed by third parties (if the site uses HTTP instead of HTTPs for example), so you need to use the Secure attribute to ensure that your Cookies are sent only if the request uses HTTPS protocol. Additionally, using the HttpOnly attribute makes your Cookies inaccessible to document.cookie to prevent XSS attacks. Set-Cookie: awesome_uuid=abc12345; Expires=Thu, 21 Oct 2100 11:59:59 GMT; Secure; HttpOnly Enter fullscreen mode Exit fullscreen mode In general, if you're in doubt, use the Secure and HttpOnly Cookie attributes. Local Storage and Session Storage Local Storage and Session Storage are more similar than different. Most modern browsers should support Local Storage and Session Storage features. They are used to store data in the browser. They are accessible from the client-side only (web servers can't access them directly). Also since they are a front-end tool, they have no SSL support. Unlike Cookies where all Cookies (for that domain) are sent on each request, Local and Session Storage data aren't sent on each HTTP request. They just sit in your browser until someone requests it. Each browser has a different specifications on how much data can be stored inside Local and Session Storage. Many popular literatures claim about 5mb limit for Local Storage and 5-10mb limit (to be safe, check with each browser). The main difference between Local and Session storage is that Local Storage has no expiration date while Session Storage data are gone when you close the browser tab - hence the name "session". Both storages are accessible via Javascript DOM. To set, get, and delete Local Storage data: localStorage.setItem('strawberry', 'pancake'); localStorage.getItems('strawberry'); // pancake` localStorage.chocolate = 'waffle'; localStorage.chocolate; // waffle localStorage['blueberry'] = 'donut'; localStorage['blueberry']; // donut; delete localStorage.strawberry; Enter fullscreen mode Exit fullscreen mode You can also store JSON-like object inside a Local Storage. Keep in mind that you need to pass them a JSON string (use JSON.stringify ). Also since you are passing it a JSON string, don't forget to run JSON.parse to get the value. localStorage.desserts = JSON.stringify({choco: "waffle", fruit: "pancake", sweet: "donut"}); const favDessert = JSON.parse(localStorage.desserts)['choco']; // waffle Enter fullscreen mode Exit fullscreen mode If you have Chrome, you can see the localStorage values you just entered in the devtool Application tab -> Storage -> Local Storage. If you have Firefox, in the devtool, you can find it in the Storage tab, under Local Storage. Accessing the Session Storage with Javascript is similar to Local Storage: sessionStorage.setItem('strawberry', 'pancake'); sessionStorage.getItems('strawberry'); // pancake` sessionStorage.chocolate = 'waffle'; sessionStorage.chocolate; // waffle sessionStorage['blueberry'] = 'donut'; sessionStorage['blueberry']; // donut; delete sessionStorage.strawberry; Enter fullscreen mode Exit fullscreen mode Both storages are scoped to the domain name, just like Cookies. If you run localStorage.setItem('choco', 'donut'); in https://example.com and you run localStorage.setItem('choco', 'bo'); in https://whatever.com , the Local Storage item choco donut is stored only in example.com while choco bo is stored in whatever.com . Both Local and Session Storage are scoped by browser vendors. If you store it using Chrome, you can't read it from Firefox. Cookies vs Local Storage vs Session Storage To summarize: Cookies Has different expiration dates (both the server or client can set up expiration date) The Client can't access the Cookies if the HttpOnly flag is true Has SSL Support Data are transferred on each HTTP request 4kb limit Local Storage Has no expiration date Client only Has no SSL support Data are not transferred on each HTTP request 5 mb limit (check with the browser) Session Storage Data is gone when you close the browser tab Client only Has no SSL support Data are not transferred on each HTTP request 5-10 mb limit (check with the browser) Top comments (8) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand VIMAL KUMAR VIMAL KUMAR VIMAL KUMAR Follow 404 bio not found Location INDIA Education Indian Institute of Information Technology Ranchi Work Associate @Cognizant Joined Apr 3, 2020 • Mar 21 '21 Dropdown menu Copy link Hide Thanks for sharing Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Mohammad Mahdi Bahrami Mohammad Mahdi Bahrami Mohammad Mahdi Bahrami Follow A new teenage frontend developer... Location Qom, Iran Work Student at highschool. Frontend dev at "ToloNajm" astrology-research company Joined Mar 27, 2022 • May 12 '22 Dropdown menu Copy link Hide I was stuck you helped me. Thank you. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Shuvo Shuvo Shuvo Follow I am a Frontend Developer. I love to write React.js,Vue.js,Nuxt.js,Next.js and awesome JavaScript Code. Thank you! Location Dhaka,Bangladesh Joined Jan 4, 2022 • Apr 26 '22 Dropdown menu Copy link Hide Thanks for sharing Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Moinul Islam Moinul Islam Moinul Islam Follow Email moinulilm10@gmail.com Location Nikunja, Dhaka Joined Oct 19, 2020 • Sep 12 '21 Dropdown menu Copy link Hide nice article Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand OKIEMUTE BADARE OKIEMUTE BADARE OKIEMUTE BADARE Follow Work Full Stack JavaScript Dev Joined Jun 9, 2021 • Jul 26 '22 Dropdown menu Copy link Hide Nice Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Klim Klim Klim Follow Location Russia Work Junior Frontend Engineer Joined Mar 7, 2020 • Jul 7 '21 Dropdown menu Copy link Hide Very useful article! Thank you 👍 Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Lilian Lilian Lilian Follow Joined May 18, 2021 • May 18 '21 Dropdown menu Copy link Hide thanks!! was super useful! Like comment: Like comment: 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 Igor Irianto Follow Vim, Rails, cheesy puns Location Dallas, TX Joined Apr 27, 2019 More from Igor Irianto Tmux Tutorial for Beginners # tmux # vim # tutorial # beginners Scalability For Beginners # scalability # beginners # 101 Redis For Beginners # redis # beginners # nosql 💎 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/news/page/4#main-content | News 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 News Follow Hide Expect to see announcements of new and updated products, services, and features for languages & frameworks. You also will find high-level news relevant to the tech and software development industry covered here. Create Post submission guidelines When to use this tag : new service or product launched service, product, framework, library or language itself got updated (brief summary must be included as well as the source) covering broader tech industry/development news When NOT to use this tag : general news from media to promote people political posts to talk about personal goals (for example "I started to meditate every morning to increase my productivity" is nothing for this tag). about #news Use this tag to announce new products, services, or tools recently launched or updated. Notable changes in frameworks, libraries, or languages are ideal to cover. General tech industry news with a software development slant is also acceptable. This tag is not to be used for promotion of people, personal goals, or news unrelated to software development. Older #news 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 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 Containerization 2025: Why containerd 2.0 and eBPF are Changing Everything DataFormatHub DataFormatHub DataFormatHub Follow Dec 22 '25 Containerization 2025: Why containerd 2.0 and eBPF are Changing Everything # news # docker # kubernetes # devops Comments Add Comment 9 min read I Built a News App Because Indian Media Made Me Angry Ojas Kale Ojas Kale Ojas Kale Follow Dec 26 '25 I Built a News App Because Indian Media Made Me Angry # news # startup # showdev # productivity Comments Add Comment 2 min read Your December 2025 AI Coffee Break: 5 Major Developments You Need to Know Ethan Zhang Ethan Zhang Ethan Zhang Follow Dec 22 '25 Your December 2025 AI Coffee Break: 5 Major Developments You Need to Know # news # ai # machinelearning # technology Comments Add Comment 5 min read YouTube launches AI-powered Playables Builder beta to let creators design andshare their own games Saiki Sarkar Saiki Sarkar Saiki Sarkar Follow Dec 23 '25 YouTube launches AI-powered Playables Builder beta to let creators design andshare their own games # news # ai # gamedev Comments Add Comment 2 min read dbt & Airflow in 2025: Why These Data Powerhouses Are Redefining Engineering DataFormatHub DataFormatHub DataFormatHub Follow Dec 21 '25 dbt & Airflow in 2025: Why These Data Powerhouses Are Redefining Engineering # news # dataengineering # etl # datapipeline Comments Add Comment 11 min read Alibaba Qwen Launches Open-Sourced Qwen-Image-Layered with Photoshop-GradeLayering Saiki Sarkar Saiki Sarkar Saiki Sarkar Follow Dec 22 '25 Alibaba Qwen Launches Open-Sourced Qwen-Image-Layered with Photoshop-GradeLayering # news # tooling # ai # opensource Comments Add Comment 2 min read AWS Lambda & S3 Express One Zone: A 2025 Deep Dive into re:Invent 2023's Impact DataFormatHub DataFormatHub DataFormatHub Follow Dec 21 '25 AWS Lambda & S3 Express One Zone: A 2025 Deep Dive into re:Invent 2023's Impact # news # aws # cloud # serverless Comments Add Comment 8 min read I Built an AI-Powered Trend Analysis Tool Using the Virlo API (Here's How It Works) Arjun Vijay Prakash Arjun Vijay Prakash Arjun Vijay Prakash Follow Jan 8 I Built an AI-Powered Trend Analysis Tool Using the Virlo API (Here's How It Works) # news # python # ai # api 26 reactions Comments 7 comments 5 min read GitHub Actions & Codespaces: Why 2025's Updates Are a Must-Know for Devs DataFormatHub DataFormatHub DataFormatHub Follow Dec 20 '25 GitHub Actions & Codespaces: Why 2025's Updates Are a Must-Know for Devs # news # github # devtools # automation Comments Add Comment 10 min read Your Morning AI Briefing: Major Funding Rounds, Security Concerns, and Industry Predictions for 2026 Ethan Zhang Ethan Zhang Ethan Zhang Follow Dec 20 '25 Your Morning AI Briefing: Major Funding Rounds, Security Concerns, and Industry Predictions for 2026 # news # ai # technology # webdev Comments Add Comment 5 min read AI Coding Assistants in 2025: Why They Still Fail at Complex Tasks DataFormatHub DataFormatHub DataFormatHub Follow Dec 20 '25 AI Coding Assistants in 2025: Why They Still Fail at Complex Tasks # news # ai # devtools # github Comments Add Comment 11 min read Introducing ProXPL: A Modern Programming Language Built from Scratch Prog. Kanishk Raj Prog. Kanishk Raj Prog. Kanishk Raj Follow Dec 22 '25 Introducing ProXPL: A Modern Programming Language Built from Scratch # news # programming # beginners # showdev 5 reactions Comments Add Comment 4 min read I built LoveToRead.ai – Create personalized children's books with AI Maxwell - IndieDev Maxwell - IndieDev Maxwell - IndieDev Follow Dec 20 '25 I built LoveToRead.ai – Create personalized children's books with AI # news # webdev # ai # education Comments Add Comment 3 min read Game Dev Digest — Issue #311 - Better Performance, and more Game Dev Digest - The Newsletter On Unity Game Dev Game Dev Digest - The Newsletter On Unity Game Dev Game Dev Digest - The Newsletter On Unity Game Dev Follow Dec 19 '25 Game Dev Digest — Issue #311 - Better Performance, and more # news # gamedev # unity3d # csharp Comments Add Comment 11 min read TypeScript 5.4-5.6: The Essential Features You Need to Master in 2025 DataFormatHub DataFormatHub DataFormatHub Follow Dec 19 '25 TypeScript 5.4-5.6: The Essential Features You Need to Master in 2025 # news # typescript # javascript # programming Comments Add Comment 8 min read Google DeepMind launches Gemma Scope 2 interpretability suite to boost AI safetyresearch Saiki Sarkar Saiki Sarkar Saiki Sarkar Follow Dec 20 '25 Google DeepMind launches Gemma Scope 2 interpretability suite to boost AI safetyresearch # news # google # ai # deeplearning Comments Add Comment 2 min read Has Ai Become Too Easy What MiMo-V2 Flash Reveals About the New Reality of AI Progress Michael Michael Michael Follow Dec 18 '25 Has Ai Become Too Easy What MiMo-V2 Flash Reveals About the New Reality of AI Progress # discuss # ai # news 1 reaction Comments Add Comment 3 min read Irish Techie Table Quiz 2025 - Update whykay 👩🏻💻🐈🏳️🌈 (she/her) whykay 👩🏻💻🐈🏳️🌈 (she/her) whykay 👩🏻💻🐈🏳️🌈 (she/her) Follow Dec 23 '25 Irish Techie Table Quiz 2025 - Update # news # community # watercooler Comments Add Comment 1 min read Mastering Customer Engagement: The Power of Asterisk & WebRTC Integration Ecosmob Technologies Ecosmob Technologies Ecosmob Technologies Follow Dec 19 '25 Mastering Customer Engagement: The Power of Asterisk & WebRTC Integration # news # voip # webrtc # productivity Comments Add Comment 3 min read npm Security 2025: Why Provenance and Sigstore Change Everything DataFormatHub DataFormatHub DataFormatHub Follow Dec 22 '25 npm Security 2025: Why Provenance and Sigstore Change Everything # news # npm # javascript # security Comments Add Comment 11 min read SAM 3 Is Here: Meta's Latest Vision AI Can Now Understand Your Words ARmedia ARmedia ARmedia Follow Dec 18 '25 SAM 3 Is Here: Meta's Latest Vision AI Can Now Understand Your Words # news # ai # deeplearning 5 reactions Comments 1 comment 4 min read The Evolving Landscape of Data Formats: JSON, YAML, and the Rise of Specialized Standards in 2025 DataFormatHub DataFormatHub DataFormatHub Follow Dec 18 '25 The Evolving Landscape of Data Formats: JSON, YAML, and the Rise of Specialized Standards in 2025 # news # json # data # standards Comments Add Comment 8 min read Is English the New Programming Language? Mariem Khedhiri Mariem Khedhiri Mariem Khedhiri Follow Jan 1 Is English the New Programming Language? # discuss # programming # ai # news 2 reactions Comments 5 comments 2 min read Kubernetes 1.35 Security: 7 Game-Changing Features Released Today (DevSecOps Must-Know) inboryn inboryn inboryn Follow Dec 17 '25 Kubernetes 1.35 Security: 7 Game-Changing Features Released Today (DevSecOps Must-Know) # news # kubernetes # devops # security Comments Add Comment 4 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.hostinger.com/tld/fun-domain | .fun domain | Buy and register a domain in minutes Don’t miss the New Year’s Sale deals! 00 D 23 H 10 M 55 S Explore Pricing Services Hosting Managed hosting for WordPress AI Optimized for the world’s most popular CMS Managed hosting for WooCommerce Build and grow an ecommerce website Web hosting Secure, speedy, reliable services Cloud hosting The tools to level-up your business Agency hosting Designed for professionals and agencies Node.js web apps hosting POPULAR Deploy modern web apps instantly Websites Website Builder AI Create a website in 3 easy steps Ecommerce Website Builder AI Get straight to business with an online store Horizons AI Launch a no-code site or web app with AI VPS VPS hosting AI Get a powerful AI-managed VPS Self-hosted n8n POPULAR Run n8n AI workflows with full control Domains Domain name search Find and register your website address Domain transfer Transfer a domain to Hostinger, fast Email Email marketing with Hostinger Reach NEW Create and send email campaigns with AI Business email Professional addresses to build your brand Google Workspace Transform teamwork and boost productivity Migrate a website Migrate a site from elsewhere, fast and free Explore Blog Our latest news and updates Features and tools Latest product releases and features Our story How we got here and where we’re going Client stories Our clients’ successes are our favorite stories Support Knowledge Base Advice and answers to all of your FAQs Tutorials Videos and articles to help you achieve your online success story Contact How to reach us How to make a website A step-by-step guide to building and launching a website Self-hosted n8n English Back Choose your country Argentina Español Australia English Brasil Português Canada English Canada Français Colombia Español Česko Čeština Danmark Dansk Deutschland Deutsch Eesti Eesti مصر العربية Ελλάδα Ελληνικά España Español France Français Hrvatska Hrvatski India English भारत हिंदी Indonesia Bahasa Indonesia Italia Italiano Japan 日本語 Latvija Latviešu Lietuva Lietuvių Magyarország Magyar المغرب العربية Maroc Français Malaysia English México Español Nigeria English Nederland Nederlands Norge Norsk Pakistan English Philippines English Polska Polski Portugal Português Română România Slovensko Slovenčina Suomi Suomi Sverige Svenska Türkiye Türkçe Україна Українська United Kingdom English United States English Việt Nam Tiếng Việt الدول العربية العربية יִשְׂרָאֵל עברית ประเทศไทย ไทย 대한민국 한국어 中国 中文 My account Show your light-hearted side with a .fun domain $ 32.99 SAVE 97% $ 0.99 /1st yr Register a .fun domain today and inject personality into your website. .fun Search Free WHOIS privacy protection 24/7 support No technical knowledge required Check more domain names Get a free .fun domain with premium web hosting for 12 months. Get free .fun domain What does a .fun domain mean? .fun is perfect for injecting excitement and playfulness into your website, whether for a video-sharing platform, party planning business, or gaming stream. Purchase a .fun domain and let your audience experience the fun and creativity you bring. Why choose a .fun domain? Instantly add excitement and playfulness to your website. Perfect for video platforms, party planning, gaming, or creative projects. More availability than .com, giving you a better chance at securing your name. Unlock unique and catchy URLs like have.fun or gamefor.fun. Stand out online with a domain that’s easy to remember and share. Explore the possibilities from our TLD list. .ai .blog .cc .cloud .com .live .me .net .online .org .pro .sbs .shop .site .space .store .studio .tech .academy .actor .ae .ag .agency .am .app .archi .army .art .asia .at .band .be .bet .bike .bio .biz .black .blue .bond .boutique .business .bz .ca .cab .cafe .camp .capital .cards .care .cat .center .cfd .ch .chat .church .city .cl .claims .cleaning .click .clinic .clothing .club .co .co.in .co.uk .coach .codes .coffee .com.au .com.br .community .company .computer .construction .consulting .contractors .cool .credit .cx .cyou .cz .de .deals .design .dev .digital .directory .dk .dog .education .email .energy .engineer .enterprises .es .estate .eu .events .expert .exposed .family .farm .fi .finance .financial .fish .fitness .fm .fr .fund .fyi .games .gg .gifts .glass .global .gmbh .gold .golf .gr .graphics .gratis .green .group .guide .guru .haus .healthcare .help .holdings .holiday .host .house .icu .id .immo .in .ind.in .industries .info .institute .insure .international .io .ist .it .jp .kim .la .land .lat .lease .legal .lgbt .li .life .limo .link .llc .lol .lt .ltd .lu .lv .management .market .marketing .mba .me.uk .media .mobi .money .mx .name .net.in .network .news .ninja .nl .org.in .org.uk .pe .pet .photography .photos .pictures .pk .pl .place .plus .pm .press .productions .properties .pt .pub .pw .re .red .restaurant .rip .ro .rocks .run .sale .school .se .services .show .ski .social .software .solar .solutions .style .support .systems .tax .taxi .team .technology .tf .tips .today .tools .top .town .toys .training .travel .tv .uk .university .uno .us .vc .ventures .vet .video .vin .vip .vision .vote .watch .website .wf .wine .works .world .ws .wtf .xyz .yt .zone View more Hostinger Domain Extensions fun Domain Hosting Web hosting Hosting for WordPress VPS hosting Self-hosted n8n Business email Cloud hosting Hosting for WooCommerce Hosting for agencies Minecraft hosting Game server hosting Google Workspace Domain Domain name search Cheap domain names Free domain WHOIS Lookup Free SSL certificate Domain transfer Domain extensions Personal domain name Tools Hostinger Horizons Website Builder AI Website Builder Ecommerce Website Builder Print on Demand Link in Bio Business Name Generator AI Logo Generator Migrate to Hostinger Hostinger API Information Pricing Reviews Affiliate program Referral program Roadmap Wall of fame System status Sitemap Company About Hostinger Our technology Newsroom Career Blog Student discount Sustainability Principles Support Tutorials Knowledge Base Hostinger Academy Contact us Report abuse NPRD request policy Privacy policy Refund policy Terms of service and more © 2004-2026 Hostinger – Launch, grow, and succeed online, supported by AI that puts the power in your hands. Prices are listed without VAT We care about your privacy This website uses cookies that are needed for the site to work properly and to get data on how you interact with it, as well as for marketing purposes. By accepting, you agree to store cookies on your device for ad targeting, personalization, and analytics as described in our Cookie policy . Accept all Reject all Cookie settings | 2026-01-13T08:49:06 |
https://hmpljs.forem.com/privacy#1-what-does-this-privacy-policy-apply-to | 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://future.forem.com/new/edgecomputing | New Post - 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 Join the Future Future is a community of 3,676,891 amazing enthusiasts 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 Future? 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 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/iggredible/cookies-vs-local-storage-vs-session-storage-3gp3#cookies | Cookies vs Local Storage vs Session Storage - 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 Igor Irianto Posted on Mar 20, 2021 • Edited on Jun 3, 2021 Cookies vs Local Storage vs Session Storage # cookies # localstorage # sessionstorage # beginners Many of us have heard of Session Storage, Local Storage, and Cookies. But what exactly are they, what problems are they solving, and how are they different? Cookies In the beginning, the web used HTTP protocols to send messages (btw, SSL is more secure, you should use HTTPS instead of HTTP). These protocols are stateless protocols. In a stateless protocol, each request doesn't store any states, or "persisting information"; each request is its own island and it doesn't have idea about the other requests. Having a stateless protocol optimizes performance, but it also comes with a problem: what if you need to remember a user session? If you have darkMode: true or user_uuid: 12345abc , how can a server remember that if you're using a stateless protocol? With Cookies! A Cookie can be set from a HTTP header. Usually the server that you're trying to reach, if it has cookies, will send an HTTP header like this: Set-Cookie: choco_chip_cookie=its_delicious Enter fullscreen mode Exit fullscreen mode When your browser receives this header, it saves the choco_chip_cookie Cookie. Cookies are associated with websites. If websitea.com has cookie_a , you can't see cookie_a while you're in websiteb.com . You need to be in websitea.com . To see the Cookies you have, if you have Firefox, from your devtools, go to storage -> Cookies; if you have Chrome, from your devtools, go to Application -> storage -> Cookies. Most websites use Cookies, you should find some there (if not, go to a different site). Cookies can have an expiration date. Of course, you can set it to last effectively forever if you set it to a far future date: Set-Cookie: choco_chip_cookie=its_delicious; Expires=Mon, 28 Feb 2100 23:59:59GMT; Enter fullscreen mode Exit fullscreen mode One more Cookie behavior that you might need to know: your browser sends cookies on each request . When you visit https://example.com and you have to make 30 requests to download the HTML page and its 29 asset files, your browser will send your cookies (for https://example.com domain name) 30 times, one for each request. This only applies if you store your assets under the same domain name, like example.com/assets/images/cute-cats.svg , example.com/assets/stylesheets/widgets.css , etc. If you store your assets under a different domain / subdomain, like exampleassets.com/assets/stylesheets/widgets.css or static.example.com/assets/stylesheets/widgets.css , then your browser won't send the Cookies there. FYI, storing your assets in a different domain is a good strategy to improve your speed! The max size for Cookies are 4kb. This makes sense, because Cookies are being sent all the time. You don't want to send 3mb Cookie data to all 30 different requests when visiting a page. Even with this size cap, you should minimize Cookies as much as possible to reduce traffic. A popular usage for Cookie is to use a UUID for your website and run a separate server to store all the UUIDs to hold session information. A separate Redis server is a good alternative because it is fast. So when a user tries to go to example.com/user_settings , the user sends its Cookie for example.com , something like example_site_uuid=user_iggy_uuid , which then is read by your server, then your server can match it with the key in Redis to fetch the user session information for the server to use. Inside your Redis server, you would have something like: user_iggy_uuid: {darkMode: false, lastVisit: 01 January 2010, autoPayment: false, ...} . I highly encourage you to see it in action. Go to any web page (make sure it uses Cookies) using a Chrome / Firefox / any modern browser. Look at the cookies that you currently have. Now look at the Network tab and check out the request headers. You should see the same Cookies being sent. You can use Javascript to create cookies with document.cookie . document.cookie = "choco_chip_cookie=its_delicious"; document.cookie = "choco_donut=its_awesome"; console.log(document.cookie); Enter fullscreen mode Exit fullscreen mode In addition to Expires , Cookies have many more attribute you can give to do all sorts of things. If you want to learn more, check out the mozilla cookie page . Cookies can be accessed by third parties (if the site uses HTTP instead of HTTPs for example), so you need to use the Secure attribute to ensure that your Cookies are sent only if the request uses HTTPS protocol. Additionally, using the HttpOnly attribute makes your Cookies inaccessible to document.cookie to prevent XSS attacks. Set-Cookie: awesome_uuid=abc12345; Expires=Thu, 21 Oct 2100 11:59:59 GMT; Secure; HttpOnly Enter fullscreen mode Exit fullscreen mode In general, if you're in doubt, use the Secure and HttpOnly Cookie attributes. Local Storage and Session Storage Local Storage and Session Storage are more similar than different. Most modern browsers should support Local Storage and Session Storage features. They are used to store data in the browser. They are accessible from the client-side only (web servers can't access them directly). Also since they are a front-end tool, they have no SSL support. Unlike Cookies where all Cookies (for that domain) are sent on each request, Local and Session Storage data aren't sent on each HTTP request. They just sit in your browser until someone requests it. Each browser has a different specifications on how much data can be stored inside Local and Session Storage. Many popular literatures claim about 5mb limit for Local Storage and 5-10mb limit (to be safe, check with each browser). The main difference between Local and Session storage is that Local Storage has no expiration date while Session Storage data are gone when you close the browser tab - hence the name "session". Both storages are accessible via Javascript DOM. To set, get, and delete Local Storage data: localStorage.setItem('strawberry', 'pancake'); localStorage.getItems('strawberry'); // pancake` localStorage.chocolate = 'waffle'; localStorage.chocolate; // waffle localStorage['blueberry'] = 'donut'; localStorage['blueberry']; // donut; delete localStorage.strawberry; Enter fullscreen mode Exit fullscreen mode You can also store JSON-like object inside a Local Storage. Keep in mind that you need to pass them a JSON string (use JSON.stringify ). Also since you are passing it a JSON string, don't forget to run JSON.parse to get the value. localStorage.desserts = JSON.stringify({choco: "waffle", fruit: "pancake", sweet: "donut"}); const favDessert = JSON.parse(localStorage.desserts)['choco']; // waffle Enter fullscreen mode Exit fullscreen mode If you have Chrome, you can see the localStorage values you just entered in the devtool Application tab -> Storage -> Local Storage. If you have Firefox, in the devtool, you can find it in the Storage tab, under Local Storage. Accessing the Session Storage with Javascript is similar to Local Storage: sessionStorage.setItem('strawberry', 'pancake'); sessionStorage.getItems('strawberry'); // pancake` sessionStorage.chocolate = 'waffle'; sessionStorage.chocolate; // waffle sessionStorage['blueberry'] = 'donut'; sessionStorage['blueberry']; // donut; delete sessionStorage.strawberry; Enter fullscreen mode Exit fullscreen mode Both storages are scoped to the domain name, just like Cookies. If you run localStorage.setItem('choco', 'donut'); in https://example.com and you run localStorage.setItem('choco', 'bo'); in https://whatever.com , the Local Storage item choco donut is stored only in example.com while choco bo is stored in whatever.com . Both Local and Session Storage are scoped by browser vendors. If you store it using Chrome, you can't read it from Firefox. Cookies vs Local Storage vs Session Storage To summarize: Cookies Has different expiration dates (both the server or client can set up expiration date) The Client can't access the Cookies if the HttpOnly flag is true Has SSL Support Data are transferred on each HTTP request 4kb limit Local Storage Has no expiration date Client only Has no SSL support Data are not transferred on each HTTP request 5 mb limit (check with the browser) Session Storage Data is gone when you close the browser tab Client only Has no SSL support Data are not transferred on each HTTP request 5-10 mb limit (check with the browser) Top comments (8) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand VIMAL KUMAR VIMAL KUMAR VIMAL KUMAR Follow 404 bio not found Location INDIA Education Indian Institute of Information Technology Ranchi Work Associate @Cognizant Joined Apr 3, 2020 • Mar 21 '21 Dropdown menu Copy link Hide Thanks for sharing Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Mohammad Mahdi Bahrami Mohammad Mahdi Bahrami Mohammad Mahdi Bahrami Follow A new teenage frontend developer... Location Qom, Iran Work Student at highschool. Frontend dev at "ToloNajm" astrology-research company Joined Mar 27, 2022 • May 12 '22 Dropdown menu Copy link Hide I was stuck you helped me. Thank you. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Shuvo Shuvo Shuvo Follow I am a Frontend Developer. I love to write React.js,Vue.js,Nuxt.js,Next.js and awesome JavaScript Code. Thank you! Location Dhaka,Bangladesh Joined Jan 4, 2022 • Apr 26 '22 Dropdown menu Copy link Hide Thanks for sharing Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Moinul Islam Moinul Islam Moinul Islam Follow Email moinulilm10@gmail.com Location Nikunja, Dhaka Joined Oct 19, 2020 • Sep 12 '21 Dropdown menu Copy link Hide nice article Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand OKIEMUTE BADARE OKIEMUTE BADARE OKIEMUTE BADARE Follow Work Full Stack JavaScript Dev Joined Jun 9, 2021 • Jul 26 '22 Dropdown menu Copy link Hide Nice Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Klim Klim Klim Follow Location Russia Work Junior Frontend Engineer Joined Mar 7, 2020 • Jul 7 '21 Dropdown menu Copy link Hide Very useful article! Thank you 👍 Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Lilian Lilian Lilian Follow Joined May 18, 2021 • May 18 '21 Dropdown menu Copy link Hide thanks!! was super useful! Like comment: Like comment: 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 Igor Irianto Follow Vim, Rails, cheesy puns Location Dallas, TX Joined Apr 27, 2019 More from Igor Irianto Tmux Tutorial for Beginners # tmux # vim # tutorial # beginners Scalability For Beginners # scalability # beginners # 101 Redis For Beginners # redis # beginners # nosql 💎 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://forem.com/t/aws/page/77 | Amazon Web Services Page 77 - 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 DEV Community Close Amazon Web Services Follow Hide Amazon Web Services (AWS) is a collection of web services for computing, storage, machine learning, security, and more There are over 200+ AWS services as of 2023. Create Post submission guidelines Articles which primary focus is AWS are permitted to used the #aws tag. Older #aws 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 ✅ Task — 3: Use Variables, Locals, and Outputs for a Simple EC2 Instance Setup Latchu@DevOps Latchu@DevOps Latchu@DevOps Follow Nov 15 '25 ✅ Task — 3: Use Variables, Locals, and Outputs for a Simple EC2 Instance Setup # terraform # devops # infrastructureascode # aws 6 reactions Comments Add Comment 2 min read Automatic Preview Environments with SST and GitHub Actions Danny Steenman Danny Steenman Danny Steenman Follow for AWS Community Builders Nov 14 '25 Automatic Preview Environments with SST and GitHub Actions # sst # nextjs # githubactions # aws 1 reaction Comments Add Comment 4 min read A Better Way to Write Production-Ready Terraform - Part 2 - Remote State Management Farouq Mousa Farouq Mousa Farouq Mousa Follow for AWS Community Builders Nov 12 '25 A Better Way to Write Production-Ready Terraform - Part 2 - Remote State Management # terraform # devops # cloud # aws 5 reactions Comments 4 comments 7 min read Securing AWS Credentials with Secrets Manager after Sanitizing Git History Chris Perry Chris Perry Chris Perry Follow Oct 24 '25 Securing AWS Credentials with Secrets Manager after Sanitizing Git History # aws # cloud # security # cloudskills Comments Add Comment 6 min read Setting Up NVIDIA Parakeet TDT 0.6B v3 for Speech Recognition on AWS EC2 Ubuntu Architect Alick Architect Alick Architect Alick Follow Nov 13 '25 Setting Up NVIDIA Parakeet TDT 0.6B v3 for Speech Recognition on AWS EC2 Ubuntu # ubuntu # aws # tutorial # deeplearning 1 reaction Comments Add Comment 8 min read How to Clean Up a Messy AWS Account: A Step-by-Step Cloud Hygiene Guide Nilesh A. Nilesh A. Nilesh A. Follow for AddWeb Solution Pvt Ltd Nov 14 '25 How to Clean Up a Messy AWS Account: A Step-by-Step Cloud Hygiene Guide # aws # cloud # cloudmanagement # costoptimization 65 reactions Comments Add Comment 5 min read Deploying a Flask App Across Multiple AWS Regions Haripriya Veluchamy Haripriya Veluchamy Haripriya Veluchamy Follow Nov 14 '25 Deploying a Flask App Across Multiple AWS Regions # aws # devops # cloud # flask 2 reactions Comments Add Comment 4 min read How to Launch AWS Stacks for Free — And What Happens When the Free Tier Ends Bradley Matera Bradley Matera Bradley Matera Follow Nov 14 '25 How to Launch AWS Stacks for Free — And What Happens When the Free Tier Ends # aws # cloud 9 reactions Comments 1 comment 4 min read 🏗️ 4 Estrategias para Procesar Mensajes SQS en Batch con AWS Lambda olcortesb olcortesb olcortesb Follow for AWS Español Oct 10 '25 🏗️ 4 Estrategias para Procesar Mensajes SQS en Batch con AWS Lambda # serverless # spanish # architecture # aws Comments Add Comment 5 min read How To Configure Multipart Upload to S3 Bucket using AWS CLI Thu Kha Kyawe Thu Kha Kyawe Thu Kha Kyawe Follow Nov 14 '25 How To Configure Multipart Upload to S3 Bucket using AWS CLI # aws # s3 # 2025 Comments Add Comment 3 min read IaC in Action: How Terraform & Ansible Deliver a Resilient Flask Application on AWS Hritik Raj Hritik Raj Hritik Raj Follow Nov 2 '25 IaC in Action: How Terraform & Ansible Deliver a Resilient Flask Application on AWS # terraform # ansible # flask # aws 2 reactions Comments Add Comment 4 min read The Biggest AWS Outage: December 7, 2021 US-East-1 Disruption Muhammad Zeeshan Muhammad Zeeshan Muhammad Zeeshan Follow Oct 10 '25 The Biggest AWS Outage: December 7, 2021 US-East-1 Disruption # aws # outage # cloud # cloudresilience Comments Add Comment 1 min read Deploying n8n to AWS with Defang Toki Toki Toki Follow Oct 9 '25 Deploying n8n to AWS with Defang # n8n # defang # automation # aws Comments Add Comment 4 min read Deploying EPicbook with Production-Grade Terraform Hajarat Hajarat Hajarat Follow Oct 9 '25 Deploying EPicbook with Production-Grade Terraform # aws # devops 1 reaction Comments Add Comment 2 min read ftpGrid Now Has a Free Tier Viggo Blum Viggo Blum Viggo Blum Follow Oct 15 '25 ftpGrid Now Has a Free Tier # webdev # aws # programming # cloudcomputing Comments Add Comment 1 min read The Ultimate Guide to Linux Command Line for Cloud Engineers Stella Achar Oiro Stella Achar Oiro Stella Achar Oiro Follow for AWS Community Builders Nov 13 '25 The Ultimate Guide to Linux Command Line for Cloud Engineers # aws # linux # cloudnative # tutorial 2 reactions Comments Add Comment 15 min read My journey through Amazon system design interview courses and the lessons that stuck Dev Loops Dev Loops Dev Loops Follow Nov 14 '25 My journey through Amazon system design interview courses and the lessons that stuck # aws # systemdesign # community # productivity Comments Add Comment 4 min read Multi-Modal Travel Planning Agent in Minutes Elizabeth Fuentes L Elizabeth Fuentes L Elizabeth Fuentes L Follow for AWS Nov 14 '25 Multi-Modal Travel Planning Agent in Minutes # aws # ai # python # tutorial 22 reactions Comments 1 comment 7 min read Strengthening Cloud Security: Authenticating Terraform to Azure Using a Service Principal Hajarat Hajarat Hajarat Follow Oct 9 '25 Strengthening Cloud Security: Authenticating Terraform to Azure Using a Service Principal # dev # aws # cloud Comments Add Comment 1 min read AWS Certified Developer - Associate (DVA-C02) Exam Guide Thu Kha Kyawe Thu Kha Kyawe Thu Kha Kyawe Follow Nov 13 '25 AWS Certified Developer - Associate (DVA-C02) Exam Guide # aws # certifications # 2025 Comments Add Comment 1 min read Securing LangChain APIs with AWS SSO and Active Directory Chandrani Mukherjee Chandrani Mukherjee Chandrani Mukherjee Follow Oct 9 '25 Securing LangChain APIs with AWS SSO and Active Directory # aws # security # langchain # python Comments Add Comment 4 min read Cloud Resume Challenge - Chunk 5 - The Final Write-Up Trinity Klein Trinity Klein Trinity Klein Follow Nov 11 '25 Cloud Resume Challenge - Chunk 5 - The Final Write-Up # portfolio # aws # cloud # career 2 reactions Comments Add Comment 6 min read The 'Lift-and-Shift' Trap: 5 Reasons Your Cloud Migration Is Doomed Before Day One Jerry Jerry Jerry Follow Oct 10 '25 The 'Lift-and-Shift' Trap: 5 Reasons Your Cloud Migration Is Doomed Before Day One # cloudmigration # cloudcomputing # aws # devops Comments Add Comment 4 min read How to stop and start EC2 using the AWS Instance Scheduler Thu Kha Kyawe Thu Kha Kyawe Thu Kha Kyawe Follow Nov 13 '25 How to stop and start EC2 using the AWS Instance Scheduler # aws # 2025 Comments Add Comment 5 min read The Production-Ready GenAI Platform: A Complete AWS Architecture for Codified Governance Deon Prinsloo Deon Prinsloo Deon Prinsloo Follow Nov 13 '25 The Production-Ready GenAI Platform: A Complete AWS Architecture for Codified Governance # aws # genai # mlops # security Comments Add Comment 4 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 — Your community HQ 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 . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:49:06 |
https://forem.com/t/aws/page/73 | Amazon Web Services Page 73 - 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 DEV Community Close Amazon Web Services Follow Hide Amazon Web Services (AWS) is a collection of web services for computing, storage, machine learning, security, and more There are over 200+ AWS services as of 2023. Create Post submission guidelines Articles which primary focus is AWS are permitted to used the #aws tag. Older #aws posts 70 71 72 73 74 75 76 77 78 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu The AI/ML Learning Path (Sprints-Based, Zero-Cost, Industry-Solid) Track Vernard Sharbney Vernard Sharbney Vernard Sharbney Follow for CDSA - Cross Domain Solution Architect Nov 22 '25 The AI/ML Learning Path (Sprints-Based, Zero-Cost, Industry-Solid) Track # ai # machinelearning # agriculture # aws Comments Add Comment 3 min read Event-Driven Batch Processing on AWS: From Scheduled Tasks to Auto-Scaling Workloads JM Rifkhan JM Rifkhan JM Rifkhan Follow for AWS Community Builders Nov 8 '25 Event-Driven Batch Processing on AWS: From Scheduled Tasks to Auto-Scaling Workloads # aws # ecs # eks # batchprocessing 8 reactions Comments Add Comment 25 min read Mastering Rsync: Your Essential Guide to Linux File Synchronization Md Shahjalal Md Shahjalal Md Shahjalal Follow Oct 18 '25 Mastering Rsync: Your Essential Guide to Linux File Synchronization # linux # backup # ubuntu # aws Comments Add Comment 4 min read Solar-App Deployment: From Node.js to Multi-Cloud CI/CD Nimesh Kulkarni Nimesh Kulkarni Nimesh Kulkarni Follow Nov 10 '25 Solar-App Deployment: From Node.js to Multi-Cloud CI/CD # node # devops # aws # cicd 1 reaction Comments Add Comment 2 min read Building a Scalable AWS E-Learning Platform for Government Use BAKRE JAMIU BAKRE JAMIU BAKRE JAMIU Follow Oct 18 '25 Building a Scalable AWS E-Learning Platform for Government Use # aws # architectengineer # cloudnative # nlp Comments Add Comment 3 min read Building a Real-Time Aircraft Landing Tracker for Kisumu Airport with AWS and OpenSky API Cloudev Cloudev Cloudev Follow Oct 18 '25 Building a Real-Time Aircraft Landing Tracker for Kisumu Airport with AWS and OpenSky API # lambda # aws # cloud # terraform Comments Add Comment 1 min read Build Your Own AWS DevOps CLI with Python & Boto3 Pravesh Sudha Pravesh Sudha Pravesh Sudha Follow for AWS Community Builders Oct 22 '25 Build Your Own AWS DevOps CLI with Python & Boto3 # aws # python # devops # programming 8 reactions Comments Add Comment 9 min read How AWS Powers the Internet and What Happened When It Went Down Faisal Ibrahim Sadiq Faisal Ibrahim Sadiq Faisal Ibrahim Sadiq Follow for AWS Community Builders Oct 23 '25 How AWS Powers the Internet and What Happened When It Went Down # cloud # aws # devops 6 reactions Comments Add Comment 4 min read Kubernetes Troubleshooting with K8sGPT + Amazon Bedrock Prithiviraj R Prithiviraj R Prithiviraj R Follow Nov 21 '25 Kubernetes Troubleshooting with K8sGPT + Amazon Bedrock # ai # aws # kubernetes # devops 1 reaction Comments Add Comment 3 min read How to Make Money with AWS Muhammad Zeeshan Muhammad Zeeshan Muhammad Zeeshan Follow Nov 9 '25 How to Make Money with AWS # aws # freelance # productivity # howto 5 reactions Comments 4 comments 2 min read AWS Organizations: The Hidden Backbone of Enterprise Security Amruta Pardeshi Amruta Pardeshi Amruta Pardeshi Follow for AWS Community Builders Nov 22 '25 AWS Organizations: The Hidden Backbone of Enterprise Security # cloud # security # devops # aws 8 reactions Comments Add Comment 3 min read HPC & Apollo Tyres Deep Dive | AWS Summit Bangalore 2025 N Chandra Prakash Reddy N Chandra Prakash Reddy N Chandra Prakash Reddy Follow for AWS Community Builders Oct 19 '25 HPC & Apollo Tyres Deep Dive | AWS Summit Bangalore 2025 # aws # hpc # ai # genai 2 reactions Comments Add Comment 5 min read Portfolio Management for Macro Hedging (Updated:2026-01-09) Kenny Chan Kenny Chan Kenny Chan Follow for AWS Community Builders Nov 21 '25 Portfolio Management for Macro Hedging (Updated:2026-01-09) # trading # ai # fintech # aws Comments Add Comment 12 min read After Asana's AI Breach: What It Takes to Deploy Production AI Agents Securely Abraham Arellano Tavara Abraham Arellano Tavara Abraham Arellano Tavara Follow Oct 19 '25 After Asana's AI Breach: What It Takes to Deploy Production AI Agents Securely # aws # machinelearning # security # cloudcomputing 1 reaction Comments Add Comment 5 min read A Developer’s Guide to Terminal Editors: Vim, Nano, and Emacs Explained Faizan Firdousi Faizan Firdousi Faizan Firdousi Follow Nov 21 '25 A Developer’s Guide to Terminal Editors: Vim, Nano, and Emacs Explained # devops # linux # aws # cloud 1 reaction Comments Add Comment 2 min read The Smart Way to Automate AWS Cost Audits Across Multiple Regions Prithiviraj R Prithiviraj R Prithiviraj R Follow Oct 17 '25 The Smart Way to Automate AWS Cost Audits Across Multiple Regions # automation # devops # tooling # aws Comments Add Comment 2 min read Handling Large Payloads in Event-Driven Architectures on AWS (with CDK + TypeScript) André Paris André Paris André Paris Follow Oct 17 '25 Handling Large Payloads in Event-Driven Architectures on AWS (with CDK + TypeScript) # aws # eventdriven # architecture # typescript Comments Add Comment 4 min read From Minikube to EKS: When "exec format error" Taught Me About Platform Jeff Graham Jeff Graham Jeff Graham Follow Oct 17 '25 From Minikube to EKS: When "exec format error" Taught Me About Platform # kubernetes # aws # devops # docker Comments Add Comment 6 min read How to host Neo4J on EC2 using Docker Anand Lahoti Anand Lahoti Anand Lahoti Follow Nov 20 '25 How to host Neo4J on EC2 using Docker # neo4j # aws # docker # cloud Comments Add Comment 3 min read Building a Real-Time Log Monitoring and Alerting System on AWS Using Terraform Cloudev Cloudev Cloudev Follow Oct 17 '25 Building a Real-Time Log Monitoring and Alerting System on AWS Using Terraform # aws # cloud # systemdesign Comments Add Comment 2 min read Event-Driven Control Planes That Scale | AWS Summit Bangalore 2025 N Chandra Prakash Reddy N Chandra Prakash Reddy N Chandra Prakash Reddy Follow for AWS Community Builders Oct 19 '25 Event-Driven Control Planes That Scale | AWS Summit Bangalore 2025 # aws # security # costoptimization # development 3 reactions Comments Add Comment 5 min read Route 53 in AWS - The What, Why, and How Made Easy for Beginners Josh Lee Josh Lee Josh Lee Follow Nov 10 '25 Route 53 in AWS - The What, Why, and How Made Easy for Beginners # aws # route53 # cloud # iam Comments Add Comment 4 min read How Serverless Architecture Cuts DevOps Costs Without Slowing Deployment Hasnain Khan Hasnain Khan Hasnain Khan Follow Oct 17 '25 How Serverless Architecture Cuts DevOps Costs Without Slowing Deployment # programming # aws # devops # awschallenge Comments Add Comment 5 min read Centralized EKS monitoring across multiple AWS accounts Kirill Kirill Kirill Follow for AWS Community Builders Nov 20 '25 Centralized EKS monitoring across multiple AWS accounts # aws # eks # kubernetes # observability Comments Add Comment 17 min read Sign your AWS Lambda Code SHAJAM SHAJAM SHAJAM Follow Oct 17 '25 Sign your AWS Lambda Code # lambda # aws # security 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 — Your community HQ 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 . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:49:06 |
https://forem.com/t/web3#main-content | Web3 - 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 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 … 75 … 208 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu DoraHacks Start-up Ideas 2026: Pt.1 Digital Finance in the Circle/Arc ecosystem DoraHacks DoraHacks DoraHacks Follow Jan 13 DoraHacks Start-up Ideas 2026: Pt.1 Digital Finance in the Circle/Arc ecosystem # cryptocurrency # startup # web3 Comments Add Comment 16 min read Observation State Made Simple Tensor Labs Tensor Labs Tensor Labs Follow Jan 13 Observation State Made Simple # algorithms # architecture # blockchain # web3 Comments Add Comment 3 min read Crafting a Stitch-Inspired Memecoin on Sui Jinali Pabasara Jinali Pabasara Jinali Pabasara Follow Jan 13 Crafting a Stitch-Inspired Memecoin on Sui # smartcontract # blockchain # web3 # programming Comments Add Comment 7 min read Solana Passkeys on the Web (No Extension Required) Fred Fred Fred Follow Jan 12 Solana Passkeys on the Web (No Extension Required) # react # security # tutorial # web3 Comments Add Comment 2 min read Smart Contracts on Midnight: Programming Visibility, Not Storage Henry Odinakachukwu Henry Odinakachukwu Henry Odinakachukwu Follow Jan 12 Smart Contracts on Midnight: Programming Visibility, Not Storage # architecture # blockchain # privacy # web3 Comments Add Comment 1 min read Enhancing Privacy with Stealth Addresses on Public Blockchains Jinali Pabasara Jinali Pabasara Jinali Pabasara Follow Jan 13 Enhancing Privacy with Stealth Addresses on Public Blockchains # blockchain # web3 # privacy 1 reaction Comments 3 comments 5 min read Ethereum-Solidity Quiz Q18: What type of modifiers are "view" and "pure"? MihaiHng MihaiHng MihaiHng Follow Jan 12 Ethereum-Solidity Quiz Q18: What type of modifiers are "view" and "pure"? # ethereum # web3 # solidity # blockchain 5 reactions Comments Add Comment 1 min read [Podcast] a16z Crypto's Latest Research: Four New Business Models at the Intersection of AI and Blockchain - Summary Evan Lin Evan Lin Evan Lin Follow Jan 11 [Podcast] a16z Crypto's Latest Research: Four New Business Models at the Intersection of AI and Blockchain - Summary # ai # startup # web3 Comments Add Comment 2 min read Ethereum-Solidity Quiz Q17: What visibility modifiers does Solidity use? MihaiHng MihaiHng MihaiHng Follow Jan 10 Ethereum-Solidity Quiz Q17: What visibility modifiers does Solidity use? # ethereum # web3 # solidity # blockchain 2 reactions Comments Add Comment 1 min read Building Your First Game on Midnight: A Complete Developer Tutorial UtkarshVarma UtkarshVarma UtkarshVarma Follow Jan 9 Building Your First Game on Midnight: A Complete Developer Tutorial # beginners # gamedev # tutorial # web3 Comments Add Comment 13 min read BTC, ADA, and Cardano Hydra Heads as Paperless Digital Cash An Rodriguez An Rodriguez An Rodriguez Follow Jan 10 BTC, ADA, and Cardano Hydra Heads as Paperless Digital Cash # blockchain # cryptocurrency # web3 Comments Add Comment 8 min read Rust Series01 - Ownership is what you need to know Kevin Sheeran Kevin Sheeran Kevin Sheeran Follow Jan 10 Rust Series01 - Ownership is what you need to know # programming # rust # web3 # blockchain Comments Add Comment 1 min read Reading Contract State at a Past Block Using Wagmi obiwale ayomide obiwale ayomide obiwale ayomide Follow Jan 8 Reading Contract State at a Past Block Using Wagmi # ethereum # react # tutorial # web3 1 reaction Comments Add Comment 3 min read bitcoin-wallet-connector: One API to Connect All Bitcoin Wallets c4605 c4605 c4605 Follow Jan 6 bitcoin-wallet-connector: One API to Connect All Bitcoin Wallets # bitcoin # wallet # web3 # react Comments Add Comment 4 min read Account Abstraction Explained Akshith Anand Akshith Anand Akshith Anand Follow Jan 8 Account Abstraction Explained # webdev # blockchain # web3 # programming Comments Add Comment 5 min read How I Would Learn Web3 From Scratch Today (Without Wasting a Year) Emir Taner Emir Taner Emir Taner Follow Jan 12 How I Would Learn Web3 From Scratch Today (Without Wasting a Year) # web3 # beginners # devops # machinelearning 3 reactions Comments Add Comment 2 min read Building a Production-Ready Prediction Market Smart Contract in Solidity: Complete Guide with Foundry Sivaram Sivaram Sivaram Follow Jan 8 Building a Production-Ready Prediction Market Smart Contract in Solidity: Complete Guide with Foundry # solidity # ethereum # smartcontract # web3 5 reactions Comments Add Comment 7 min read Passkey Login & Smart Wallet Creation on Solana with React Native and LazorKit — No More Seed Phrases! Onwuka David Onwuka David Onwuka David Follow Jan 7 Passkey Login & Smart Wallet Creation on Solana with React Native and LazorKit — No More Seed Phrases! # reactnative # security # tutorial # web3 Comments Add Comment 9 min read Ethereum-Solidity Quiz Q16: What is impermanent loss? MihaiHng MihaiHng MihaiHng Follow Jan 7 Ethereum-Solidity Quiz Q16: What is impermanent loss? # ethereum # web3 # solidity # cyfrin 2 reactions Comments Add Comment 2 min read Wallets Are the New Auth Layer Abdul-Qawi Laniyan Abdul-Qawi Laniyan Abdul-Qawi Laniyan Follow Jan 11 Wallets Are the New Auth Layer # webdev # programming # web3 # authjs 6 reactions Comments Add Comment 2 min read Ethereum UX: Account Abstraction (AA) Akim B. (mousticke.eth) Akim B. (mousticke.eth) Akim B. (mousticke.eth) Follow Jan 7 Ethereum UX: Account Abstraction (AA) # web3 # blockchain # ethereum # cryptocurrency Comments Add Comment 7 min read Tutorial: Understanding the "Proof of HODL" Consensus Mechanism georgina georgina georgina Follow Jan 6 Tutorial: Understanding the "Proof of HODL" Consensus Mechanism # cryptocurrency # blockchain # web3 # nft Comments Add Comment 2 min read Tutorial: Bridging Fiat and Crypto in Your dApp with On-Chain IBANs jack jack jack Follow Jan 6 Tutorial: Bridging Fiat and Crypto in Your dApp with On-Chain IBANs # bitcoin # web3 # cryptocurrency # webdev Comments Add Comment 2 min read Tutorial: How to Become a GPU Provider on a Decentralized Compute Network Peter Peter Peter Follow Jan 6 Tutorial: How to Become a GPU Provider on a Decentralized Compute Network # web3 # cryptocurrency # blockchain # nft Comments Add Comment 2 min read Tutorial: Rethinking dApp Onboarding with Account Abstraction Pierce Pierce Pierce Follow Jan 6 Tutorial: Rethinking dApp Onboarding with Account Abstraction # cryptocurrency # blockchain # web3 # webdev Comments Add Comment 2 min read loading... trending guides/resources Exploring XRP in DeFi and What It Teaches Us When Telegram Cocoon Goes Live: The Future of the AI Internet Gasless Transactions on Solana Building a Production-Ready Prediction Market Smart Contract in Solidity: Complete Guide with Fou... Surviving pnpm + React Native: How I Finally Stopped Metro from Screaming About `@babel/runtime` My first flash loan protocol: A Solana adventure Build a CLMM on Solana Building a Simple Crypto Trading Bot in Python & Node.js CrewAI e Crawl4AI: Revolucionando a Automação com Inteligência Artificial 10 AI Agents Powering Million-Dollar Businesses in 2026 An Overview of EIP-3009: Transfer With Authorisation From Request to Revenue with the New x402 Protocol Smart Contracts on XRPL's AlphaNet x402: Internet-Native Payments for the Modern Web Embedded wallets 101: a practical guide to digital wallet types for builders Kohaku: A Practical Privacy Framework for Ethereum Wallets Prompt Optimization: How to Write Prompts That Produce Predictable, Reliable Outputs Building a Gasless Marketplace on Polygon with x402 Protocol The Future of Private Networking: Top Self-Hosted VPN Tools in 2025 Smart Escrow Series #3: Security 💎 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 — Your community HQ 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 . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/iggredible/cookies-vs-local-storage-vs-session-storage-3gp3#main-content | Cookies vs Local Storage vs Session Storage - 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 Igor Irianto Posted on Mar 20, 2021 • Edited on Jun 3, 2021 Cookies vs Local Storage vs Session Storage # cookies # localstorage # sessionstorage # beginners Many of us have heard of Session Storage, Local Storage, and Cookies. But what exactly are they, what problems are they solving, and how are they different? Cookies In the beginning, the web used HTTP protocols to send messages (btw, SSL is more secure, you should use HTTPS instead of HTTP). These protocols are stateless protocols. In a stateless protocol, each request doesn't store any states, or "persisting information"; each request is its own island and it doesn't have idea about the other requests. Having a stateless protocol optimizes performance, but it also comes with a problem: what if you need to remember a user session? If you have darkMode: true or user_uuid: 12345abc , how can a server remember that if you're using a stateless protocol? With Cookies! A Cookie can be set from a HTTP header. Usually the server that you're trying to reach, if it has cookies, will send an HTTP header like this: Set-Cookie: choco_chip_cookie=its_delicious Enter fullscreen mode Exit fullscreen mode When your browser receives this header, it saves the choco_chip_cookie Cookie. Cookies are associated with websites. If websitea.com has cookie_a , you can't see cookie_a while you're in websiteb.com . You need to be in websitea.com . To see the Cookies you have, if you have Firefox, from your devtools, go to storage -> Cookies; if you have Chrome, from your devtools, go to Application -> storage -> Cookies. Most websites use Cookies, you should find some there (if not, go to a different site). Cookies can have an expiration date. Of course, you can set it to last effectively forever if you set it to a far future date: Set-Cookie: choco_chip_cookie=its_delicious; Expires=Mon, 28 Feb 2100 23:59:59GMT; Enter fullscreen mode Exit fullscreen mode One more Cookie behavior that you might need to know: your browser sends cookies on each request . When you visit https://example.com and you have to make 30 requests to download the HTML page and its 29 asset files, your browser will send your cookies (for https://example.com domain name) 30 times, one for each request. This only applies if you store your assets under the same domain name, like example.com/assets/images/cute-cats.svg , example.com/assets/stylesheets/widgets.css , etc. If you store your assets under a different domain / subdomain, like exampleassets.com/assets/stylesheets/widgets.css or static.example.com/assets/stylesheets/widgets.css , then your browser won't send the Cookies there. FYI, storing your assets in a different domain is a good strategy to improve your speed! The max size for Cookies are 4kb. This makes sense, because Cookies are being sent all the time. You don't want to send 3mb Cookie data to all 30 different requests when visiting a page. Even with this size cap, you should minimize Cookies as much as possible to reduce traffic. A popular usage for Cookie is to use a UUID for your website and run a separate server to store all the UUIDs to hold session information. A separate Redis server is a good alternative because it is fast. So when a user tries to go to example.com/user_settings , the user sends its Cookie for example.com , something like example_site_uuid=user_iggy_uuid , which then is read by your server, then your server can match it with the key in Redis to fetch the user session information for the server to use. Inside your Redis server, you would have something like: user_iggy_uuid: {darkMode: false, lastVisit: 01 January 2010, autoPayment: false, ...} . I highly encourage you to see it in action. Go to any web page (make sure it uses Cookies) using a Chrome / Firefox / any modern browser. Look at the cookies that you currently have. Now look at the Network tab and check out the request headers. You should see the same Cookies being sent. You can use Javascript to create cookies with document.cookie . document.cookie = "choco_chip_cookie=its_delicious"; document.cookie = "choco_donut=its_awesome"; console.log(document.cookie); Enter fullscreen mode Exit fullscreen mode In addition to Expires , Cookies have many more attribute you can give to do all sorts of things. If you want to learn more, check out the mozilla cookie page . Cookies can be accessed by third parties (if the site uses HTTP instead of HTTPs for example), so you need to use the Secure attribute to ensure that your Cookies are sent only if the request uses HTTPS protocol. Additionally, using the HttpOnly attribute makes your Cookies inaccessible to document.cookie to prevent XSS attacks. Set-Cookie: awesome_uuid=abc12345; Expires=Thu, 21 Oct 2100 11:59:59 GMT; Secure; HttpOnly Enter fullscreen mode Exit fullscreen mode In general, if you're in doubt, use the Secure and HttpOnly Cookie attributes. Local Storage and Session Storage Local Storage and Session Storage are more similar than different. Most modern browsers should support Local Storage and Session Storage features. They are used to store data in the browser. They are accessible from the client-side only (web servers can't access them directly). Also since they are a front-end tool, they have no SSL support. Unlike Cookies where all Cookies (for that domain) are sent on each request, Local and Session Storage data aren't sent on each HTTP request. They just sit in your browser until someone requests it. Each browser has a different specifications on how much data can be stored inside Local and Session Storage. Many popular literatures claim about 5mb limit for Local Storage and 5-10mb limit (to be safe, check with each browser). The main difference between Local and Session storage is that Local Storage has no expiration date while Session Storage data are gone when you close the browser tab - hence the name "session". Both storages are accessible via Javascript DOM. To set, get, and delete Local Storage data: localStorage.setItem('strawberry', 'pancake'); localStorage.getItems('strawberry'); // pancake` localStorage.chocolate = 'waffle'; localStorage.chocolate; // waffle localStorage['blueberry'] = 'donut'; localStorage['blueberry']; // donut; delete localStorage.strawberry; Enter fullscreen mode Exit fullscreen mode You can also store JSON-like object inside a Local Storage. Keep in mind that you need to pass them a JSON string (use JSON.stringify ). Also since you are passing it a JSON string, don't forget to run JSON.parse to get the value. localStorage.desserts = JSON.stringify({choco: "waffle", fruit: "pancake", sweet: "donut"}); const favDessert = JSON.parse(localStorage.desserts)['choco']; // waffle Enter fullscreen mode Exit fullscreen mode If you have Chrome, you can see the localStorage values you just entered in the devtool Application tab -> Storage -> Local Storage. If you have Firefox, in the devtool, you can find it in the Storage tab, under Local Storage. Accessing the Session Storage with Javascript is similar to Local Storage: sessionStorage.setItem('strawberry', 'pancake'); sessionStorage.getItems('strawberry'); // pancake` sessionStorage.chocolate = 'waffle'; sessionStorage.chocolate; // waffle sessionStorage['blueberry'] = 'donut'; sessionStorage['blueberry']; // donut; delete sessionStorage.strawberry; Enter fullscreen mode Exit fullscreen mode Both storages are scoped to the domain name, just like Cookies. If you run localStorage.setItem('choco', 'donut'); in https://example.com and you run localStorage.setItem('choco', 'bo'); in https://whatever.com , the Local Storage item choco donut is stored only in example.com while choco bo is stored in whatever.com . Both Local and Session Storage are scoped by browser vendors. If you store it using Chrome, you can't read it from Firefox. Cookies vs Local Storage vs Session Storage To summarize: Cookies Has different expiration dates (both the server or client can set up expiration date) The Client can't access the Cookies if the HttpOnly flag is true Has SSL Support Data are transferred on each HTTP request 4kb limit Local Storage Has no expiration date Client only Has no SSL support Data are not transferred on each HTTP request 5 mb limit (check with the browser) Session Storage Data is gone when you close the browser tab Client only Has no SSL support Data are not transferred on each HTTP request 5-10 mb limit (check with the browser) Top comments (8) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand VIMAL KUMAR VIMAL KUMAR VIMAL KUMAR Follow 404 bio not found Location INDIA Education Indian Institute of Information Technology Ranchi Work Associate @Cognizant Joined Apr 3, 2020 • Mar 21 '21 Dropdown menu Copy link Hide Thanks for sharing Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Mohammad Mahdi Bahrami Mohammad Mahdi Bahrami Mohammad Mahdi Bahrami Follow A new teenage frontend developer... Location Qom, Iran Work Student at highschool. Frontend dev at "ToloNajm" astrology-research company Joined Mar 27, 2022 • May 12 '22 Dropdown menu Copy link Hide I was stuck you helped me. Thank you. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Shuvo Shuvo Shuvo Follow I am a Frontend Developer. I love to write React.js,Vue.js,Nuxt.js,Next.js and awesome JavaScript Code. Thank you! Location Dhaka,Bangladesh Joined Jan 4, 2022 • Apr 26 '22 Dropdown menu Copy link Hide Thanks for sharing Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Moinul Islam Moinul Islam Moinul Islam Follow Email moinulilm10@gmail.com Location Nikunja, Dhaka Joined Oct 19, 2020 • Sep 12 '21 Dropdown menu Copy link Hide nice article Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand OKIEMUTE BADARE OKIEMUTE BADARE OKIEMUTE BADARE Follow Work Full Stack JavaScript Dev Joined Jun 9, 2021 • Jul 26 '22 Dropdown menu Copy link Hide Nice Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Klim Klim Klim Follow Location Russia Work Junior Frontend Engineer Joined Mar 7, 2020 • Jul 7 '21 Dropdown menu Copy link Hide Very useful article! Thank you 👍 Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Lilian Lilian Lilian Follow Joined May 18, 2021 • May 18 '21 Dropdown menu Copy link Hide thanks!! was super useful! Like comment: Like comment: 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 Igor Irianto Follow Vim, Rails, cheesy puns Location Dallas, TX Joined Apr 27, 2019 More from Igor Irianto Tmux Tutorial for Beginners # tmux # vim # tutorial # beginners Scalability For Beginners # scalability # beginners # 101 Redis For Beginners # redis # beginners # nosql 💎 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://forem.com/devwonder01 | Tensor Labs - 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 DEV Community Close Follow User actions Tensor Labs Research and Development Labs specializing in Quantitative finance and Private Defense Joined Joined on Oct 27, 2021 github website Education University of Lagos Work CoFounder of KyroPay More info about @devwonder01 Badges 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 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 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 Skills/Languages Golang, Solidity, Phython, Javascript (MERN), Rust Post 5 posts published Comment 2 comments written Tag 0 tags followed Observation State Made Simple Tensor Labs Tensor Labs Tensor Labs Follow Jan 13 Observation State Made Simple # algorithms # architecture # blockchain # web3 Comments Add Comment 3 min read Want to connect with Tensor Labs? Create an account to connect with Tensor Labs. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in Building a Simple Email Spam Classifier in Rust with SmartCore Tensor Labs Tensor Labs Tensor Labs Follow Jun 25 '25 Building a Simple Email Spam Classifier in Rust with SmartCore Comments Add Comment 3 min read Setting Up Your Ultimate Linux Dev Environment: Rust, Docker & More! Tensor Labs Tensor Labs Tensor Labs Follow Jun 4 '25 Setting Up Your Ultimate Linux Dev Environment: Rust, Docker & More! Comments Add Comment 5 min read Switching from Chainlink VRF to Pyth Entropy Tensor Labs Tensor Labs Tensor Labs Follow Nov 25 '24 Switching from Chainlink VRF to Pyth Entropy Comments Add Comment 4 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 — Your community HQ 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 . DEV Community © 2016 - 2026. We're a blogging-forward open source social network where we learn from one another Log in Create account | 2026-01-13T08:49:06 |
https://dev.to/t/localstorage | Localstorage - 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 # localstorage Follow Hide Create Post Older #localstorage posts 1 2 3 4 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Typescript wrapper class for browser storage Michal M. Michal M. Michal M. Follow Dec 5 '25 Typescript wrapper class for browser storage # javascript # localstorage # typescript Comments Add Comment 3 min read Understanding Local Storage and Session Storage in JavaScript (Beginner’s Guide) WISDOMUDO WISDOMUDO WISDOMUDO Follow Oct 21 '25 Understanding Local Storage and Session Storage in JavaScript (Beginner’s Guide) # javascript # programming # localstorage # beginners 2 reactions Comments 4 comments 4 min read Stop Manually Editing Local Storage: I Built a Tool to Manage Tab State Like Git old big old big old big Follow Aug 30 '25 Stop Manually Editing Local Storage: I Built a Tool to Manage Tab State Like Git # webdev # localstorage # sessionstorage # cookies Comments Add Comment 2 min read Build a Simple Notes App with HTML, CSS & JavaScript Gift Egbonyi Gift Egbonyi Gift Egbonyi Follow Aug 6 '25 Build a Simple Notes App with HTML, CSS & JavaScript # javascript # notesapp # dom # localstorage Comments Add Comment 3 min read The main difference between `localStorage` and `sessionStorage` Renuka Patil Renuka Patil Renuka Patil Follow Jul 7 '25 The main difference between `localStorage` and `sessionStorage` # localstorage # seesionstorage # webdev # javascript 8 reactions Comments 1 comment 1 min read Hive: The Lightning-Fast Local Storage Solution for Flutter Apps Kalana Heshan Kalana Heshan Kalana Heshan Follow May 29 '25 Hive: The Lightning-Fast Local Storage Solution for Flutter Apps # hive # localstorage # flutter # mobile Comments Add Comment 6 min read IndexedDB vs localStorage: When to Use Which? Oghenetega Adiri Oghenetega Adiri Oghenetega Adiri Follow May 11 '25 IndexedDB vs localStorage: When to Use Which? # webdev # indexdb # localstorage # offlineapps 1 reaction Comments Add Comment 5 min read Creating Storagefy: A Framework-Agnostic Tool for Front-End State Persistence Arthur Germano Arthur Germano Arthur Germano Follow Apr 25 '25 Creating Storagefy: A Framework-Agnostic Tool for Front-End State Persistence # react # vue # svelte # localstorage 1 reaction Comments Add Comment 3 min read 監聽 localStorage 事件：如何在同一頁面內偵測變更 Let's Write Let's Write Let's Write Follow Mar 3 '25 監聽 localStorage 事件：如何在同一頁面內偵測變更 # localstorage # event # listenter # webdev 1 reaction Comments Add Comment 1 min read Everything About Local Storage in JavaScript and React TinTin TinTin TinTin Follow Feb 19 '25 Everything About Local Storage in JavaScript and React # javascript # react # localstorage # beginners 2 reactions Comments 1 comment 3 min read Browser Storage Types and Their Maximum Limits Vishwas R Vishwas R Vishwas R Follow Feb 18 '25 Browser Storage Types and Their Maximum Limits # webdev # cookies # localstorage # indexeddb 1 reaction Comments 1 comment 3 min read What is LocalStorage and How to Use LocalStorage with Next.js? swhabitation swhabitation swhabitation Follow Jan 23 '25 What is LocalStorage and How to Use LocalStorage with Next.js? # nextjs # localstorage # react # webdev 10 reactions Comments Add Comment 5 min read É seguro guardar dados do usuário no localStorage? Breno Breno Breno Follow Nov 15 '24 É seguro guardar dados do usuário no localStorage? # supabase # authentication # localstorage # javascript Comments Add Comment 3 min read Understanding Local Storage and Session Storage in JavaScript Abhay Singh Kathayat Abhay Singh Kathayat Abhay Singh Kathayat Follow Dec 17 '24 Understanding Local Storage and Session Storage in JavaScript # javascript # localstorage # sessionstorage # codingtips Comments Add Comment 3 min read How to Make localStorage Data Reactive Rain9 Rain9 Rain9 Follow Dec 9 '24 How to Make localStorage Data Reactive # localstorage # react # webdev 13 reactions Comments 1 comment 3 min read Enhance React Native Security and Performance: with MMKV Storage Amit Kumar Amit Kumar Amit Kumar Follow Nov 27 '24 Enhance React Native Security and Performance: with MMKV Storage # reactnative # android # ios # localstorage 5 reactions Comments Add Comment 2 min read Efficient Data Management in Manufacturing: Leveraging localStorage in Angular Anas Karah Anas Karah Anas Karah Follow Aug 5 '24 Efficient Data Management in Manufacturing: Leveraging localStorage in Angular # angular # localstorage # industry40 Comments Add Comment 2 min read # Storing Data in the Database with JavaScript Michael Moranis Michael Moranis Michael Moranis Follow Aug 10 '24 # Storing Data in the Database with JavaScript # webdev # reactjsdevelopment # localstorage # softwaredevelopment Comments Add Comment 2 min read Securing Web Storage: LocalStorage and SessionStorage Best Practices Rigal Patel Rigal Patel Rigal Patel Follow Jul 15 '24 Securing Web Storage: LocalStorage and SessionStorage Best Practices # webstorage # localstorage # sessionstorage # webdev 10 reactions Comments Add Comment 3 min read Javascript Ls/ss/cookies BekmuhammadDev BekmuhammadDev BekmuhammadDev Follow Jun 28 '24 Javascript Ls/ss/cookies # engweb # aripovdev # javascript # localstorage 5 reactions Comments Add Comment 2 min read Javascript Ls/ss/cookies😎 BekmuhammadDev BekmuhammadDev BekmuhammadDev Follow Jun 27 '24 Javascript Ls/ss/cookies😎 # javascript # localstorage # cookies 5 reactions Comments Add Comment 2 min read Faking sessionStorage to keep sites from crashing 𒎏Wii 🏳️⚧️ 𒎏Wii 🏳️⚧️ 𒎏Wii 🏳️⚧️ Follow May 10 '24 Faking sessionStorage to keep sites from crashing # javascript # beginners # tutorial # localstorage 22 reactions Comments 2 comments 3 min read Elevating Data Integrity in Your React Application with Converters in Storage Management Saulo Dias Saulo Dias Saulo Dias Follow Feb 19 '24 Elevating Data Integrity in Your React Application with Converters in Storage Management # react # dataintegrity # localstorage # webdev Comments Add Comment 4 min read Storing and Testing State in localStorage with React Harpreet Kaur Harpreet Kaur Harpreet Kaur Follow Feb 4 '24 Storing and Testing State in localStorage with React # react # webdev # javascript # localstorage 1 reaction Comments Add Comment 2 min read Local Storage in 5 mins: A Beginner’s Guide to Cookies, localStorage, and sessionStorage ben ajaero ben ajaero ben ajaero Follow Jan 18 '24 Local Storage in 5 mins: A Beginner’s Guide to Cookies, localStorage, and sessionStorage # webdev # javascript # beginners # localstorage 5 reactions Comments Add Comment 4 min read loading... trending guides/resources Typescript wrapper class for browser storage 💎 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#terms-and-conditions-for-accessing-or-otherwise-using-python | 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://maker.forem.com/privacy#d-other-purposes | Privacy Policy - Maker 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 Maker 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 Maker Forem — A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much 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 . Maker Forem © 2016 - 2026. We're a space where makers create, share, and bring ideas to life. Log in Create account | 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.