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://cssence.com/2026/text-based-web-browsers/#inert-content-areas | Text-based web browsers - CSSence.com Text-based web browsers Essay January 8, 2026 Before I start, let me get two things out of the way: In this article I’m not going to include the admittedly cool browsh, because it only works by utilizing Firefox under the hood. When I say text-based, I’m talking about old-school browsers like ELinks , Lynx or w3m. These are also the three browsers I’ve used to test everything described below. The whole article ended up being a rant about how text-based browsers deal with features that got added to HTML. Or more like, how they neglect dealing with said features. Do text-based web browsers still matter? Well, I won’t be the judge of that. I like them, I have them installed, and I test every project I create in them. But they are not what I use to surf the web. Speaking of testing your creations, here’s the good news: If your project has a solid HTML foundation that you then progressively enhance with CSS and JS, you are off to a great start. How did HTML evolve in recent years? While CSS is the star of the show when it comes to new features, HTML ain’t stale either. If we put the long-awaited styleable selects and Apple’s take on toggle switches aside, there’s a lot readily available cross-browser. But here’s the thing: Whenever we say cross-browser, we usually look at the big ones, never at text-based browsers. So in this article I wanna shed some light on how they handle the following recent additions. How do text-based web browsers handle modern HTML? Added features Details Data lists Dialogs Popovers Inert content areas Hidden content Visually hidden content When viewing a web page in a text-based browser, you essentially get plain HTML, no CSS, no JS. There is some “styling”, a result of the elements’ semantics, but don’t expect anything fancy, we are down to colors, indentation, and centered text. It reminds me of what the browsers we are used to give us when they show unstyled HTML—well, HTML with the browser default styles, to be exact. That in turn reminds me of CSS Naked Day. Text-based browsers work well with good old HTML. Said recent additions however are a bit more nuanced (e.g. interactive), so let’s talk about them individually. Details Disclosure widgets are simple interactive elements we no longer need JS for. When <details> are closed, only their <summary> is shown. Text-based browsers have no clue what disclosure widgets are, so they always show the whole <details> content, meaning you always get the open state. This way things can get verbose, but in essence it’s okay. Verdict: Acceptable. Data lists Data lists can be used to add suggested values to an input field. In my tests they have been ignored entirely, Lynx even mentions that it encountered “bad HTML”, probably because it expects <option> only in a <select> parent. At least no browser rendered the options on the screen, they simply fall back to a plain <input> field, which is better than nothing. Side note: I’ve been told data lists have accessibility issues, so … Verdict: Whatever. Dialogs Yes, HTML can do modal and non-modal dialogs, and even alert dialogs, all thanks to the <dialog> element. Initially we needed JS to toggle their visibility, but with the help of the Popover API (see next chapter) we can now even get most of it done in plain HTML. Alas, once again there is no support in text-based browsers, so you’ll end up seeing all dialog content, as if they had their open attribute set. Consequently, there’s no awareness of a form’s method="dialog" nor a submit button’s formmethod="dialog" , so in both cases the form action is triggered. Verdict: Problematic. Popovers The Popover API is probably my favorite new feature, but only if you stick to regular web browsers. Given that dialogs are a type of popover, it’s no surprise that nothing works, and once again all popover content gets dumped onto the screen. By now I think you get the idea, so I won’t even talk about the Invoker Commands API at this point. Verdict: Most likely problematic. Inert content areas A modal dialog makes the rest of the page inert , so we don’t have to do it. But with the global inert attribute we can do this manually too, if we need to make certain parts of the DOM unreachable. Sure enough, text-based browsers will happily let you access interactive elements inside an inert content area. Verdict: Bad. Hidden content We’re now approaching something that is not new at all, the global hidden attribute has been supported for over a decade. It allows us to hide content in the same way as display: none , but directly in HTML. Adding support in text-based browsers has been discussed back in the day, but got rejected, hence it was never implemented. You’ll end up seeing all content marked as hidden . This is the primary reason why I started writing this article, and what enrages me the most. If I decide to hide content in HTML instead of CSS, I must have a very good reason, thus hidden content should not be visible in any browser! Certain progressive enhancement techniques work by hiding content in HTML and then making it visible via CSS or JS. That possibility goes out the window in text-based browsers. Verdict: Epic fail. 😠 🤬 Visually hidden content Just kidding, there’s still no native way in HTML to hide content visually , so we continue to rely on class names like .visually-hidden or .sr-only . No matter how they are named, they need to summon quite a few of lines of CSS to get things done. Whether there should be a native way is up for debate. Personally I would welcome a one-liner to achieve this, but it should remain in the domain of CSS. However, if we had a way in HTML, text-based browsers would display such visually hidden content anyway, that is certain. Verdict: To be continued. Now what? What now? Text-based browsers and modern HTML, no success story in sight. Given the progress we see in web technologies, the gap will only widen, so much so that w3m and its friends might fall into oblivion. Comments Matthias Zöchling wrote on January 8, 2026 at 19:07 It’s 2026 and text-based web browsers still do not know how to handle (not so) recent additions to HTML. cssence.com/2026/text-based-web-browsers Marius Orcsik wrote on January 8, 2026 at 21:14 I think the latest text browser is chawan , which is quite good. Nathan Knowler wrote on January 8, 2026 at 21:55 Interesting, it seems like w3m and lynx can display (declarative) shadow root content, but slots don’t work? Either that or they just don’t know how <template> elements work and are showing the content—but that doesn’t make sense since then the other light DOM content is being swallowed up. Matthias Zöchling wrote on January 9, 2026 at 22:11 In reply to: @knowler.dev . Oof! That rabbit hole wasn’t even on my radar. Matthias Zöchling wrote on January 9, 2026 at 06:28 If you don’t care about text-based web browsers (I can’t blame you), this article doubles as a list of all the cool stuff that got added to HTML. Get involved Have your say on Mastodon, or simply share this article. About this article Written by Matthias Zöchling. Published on January 8, 2026 . Permalink: https://cssence.com/2026/text-based-web-browsers/ 01 Home 02 Articles 03 Threads 04 About 05 Latest 06 Popular 07 Series 08 Archive © 2010–2026 Matthias Zöchling Imprint Webrings Elsewhere Menu Settings RSS feeds Back to top | 2026-01-13T08:48:03 |
https://cssence.com/2026/text-based-web-browsers/#navigation | Text-based web browsers - CSSence.com Text-based web browsers Essay January 8, 2026 Before I start, let me get two things out of the way: In this article I’m not going to include the admittedly cool browsh, because it only works by utilizing Firefox under the hood. When I say text-based, I’m talking about old-school browsers like ELinks , Lynx or w3m. These are also the three browsers I’ve used to test everything described below. The whole article ended up being a rant about how text-based browsers deal with features that got added to HTML. Or more like, how they neglect dealing with said features. Do text-based web browsers still matter? Well, I won’t be the judge of that. I like them, I have them installed, and I test every project I create in them. But they are not what I use to surf the web. Speaking of testing your creations, here’s the good news: If your project has a solid HTML foundation that you then progressively enhance with CSS and JS, you are off to a great start. How did HTML evolve in recent years? While CSS is the star of the show when it comes to new features, HTML ain’t stale either. If we put the long-awaited styleable selects and Apple’s take on toggle switches aside, there’s a lot readily available cross-browser. But here’s the thing: Whenever we say cross-browser, we usually look at the big ones, never at text-based browsers. So in this article I wanna shed some light on how they handle the following recent additions. How do text-based web browsers handle modern HTML? Added features Details Data lists Dialogs Popovers Inert content areas Hidden content Visually hidden content When viewing a web page in a text-based browser, you essentially get plain HTML, no CSS, no JS. There is some “styling”, a result of the elements’ semantics, but don’t expect anything fancy, we are down to colors, indentation, and centered text. It reminds me of what the browsers we are used to give us when they show unstyled HTML—well, HTML with the browser default styles, to be exact. That in turn reminds me of CSS Naked Day. Text-based browsers work well with good old HTML. Said recent additions however are a bit more nuanced (e.g. interactive), so let’s talk about them individually. Details Disclosure widgets are simple interactive elements we no longer need JS for. When <details> are closed, only their <summary> is shown. Text-based browsers have no clue what disclosure widgets are, so they always show the whole <details> content, meaning you always get the open state. This way things can get verbose, but in essence it’s okay. Verdict: Acceptable. Data lists Data lists can be used to add suggested values to an input field. In my tests they have been ignored entirely, Lynx even mentions that it encountered “bad HTML”, probably because it expects <option> only in a <select> parent. At least no browser rendered the options on the screen, they simply fall back to a plain <input> field, which is better than nothing. Side note: I’ve been told data lists have accessibility issues, so … Verdict: Whatever. Dialogs Yes, HTML can do modal and non-modal dialogs, and even alert dialogs, all thanks to the <dialog> element. Initially we needed JS to toggle their visibility, but with the help of the Popover API (see next chapter) we can now even get most of it done in plain HTML. Alas, once again there is no support in text-based browsers, so you’ll end up seeing all dialog content, as if they had their open attribute set. Consequently, there’s no awareness of a form’s method="dialog" nor a submit button’s formmethod="dialog" , so in both cases the form action is triggered. Verdict: Problematic. Popovers The Popover API is probably my favorite new feature, but only if you stick to regular web browsers. Given that dialogs are a type of popover, it’s no surprise that nothing works, and once again all popover content gets dumped onto the screen. By now I think you get the idea, so I won’t even talk about the Invoker Commands API at this point. Verdict: Most likely problematic. Inert content areas A modal dialog makes the rest of the page inert , so we don’t have to do it. But with the global inert attribute we can do this manually too, if we need to make certain parts of the DOM unreachable. Sure enough, text-based browsers will happily let you access interactive elements inside an inert content area. Verdict: Bad. Hidden content We’re now approaching something that is not new at all, the global hidden attribute has been supported for over a decade. It allows us to hide content in the same way as display: none , but directly in HTML. Adding support in text-based browsers has been discussed back in the day, but got rejected, hence it was never implemented. You’ll end up seeing all content marked as hidden . This is the primary reason why I started writing this article, and what enrages me the most. If I decide to hide content in HTML instead of CSS, I must have a very good reason, thus hidden content should not be visible in any browser! Certain progressive enhancement techniques work by hiding content in HTML and then making it visible via CSS or JS. That possibility goes out the window in text-based browsers. Verdict: Epic fail. 😠 🤬 Visually hidden content Just kidding, there’s still no native way in HTML to hide content visually , so we continue to rely on class names like .visually-hidden or .sr-only . No matter how they are named, they need to summon quite a few of lines of CSS to get things done. Whether there should be a native way is up for debate. Personally I would welcome a one-liner to achieve this, but it should remain in the domain of CSS. However, if we had a way in HTML, text-based browsers would display such visually hidden content anyway, that is certain. Verdict: To be continued. Now what? What now? Text-based browsers and modern HTML, no success story in sight. Given the progress we see in web technologies, the gap will only widen, so much so that w3m and its friends might fall into oblivion. Comments Matthias Zöchling wrote on January 8, 2026 at 19:07 It’s 2026 and text-based web browsers still do not know how to handle (not so) recent additions to HTML. cssence.com/2026/text-based-web-browsers Marius Orcsik wrote on January 8, 2026 at 21:14 I think the latest text browser is chawan , which is quite good. Nathan Knowler wrote on January 8, 2026 at 21:55 Interesting, it seems like w3m and lynx can display (declarative) shadow root content, but slots don’t work? Either that or they just don’t know how <template> elements work and are showing the content—but that doesn’t make sense since then the other light DOM content is being swallowed up. Matthias Zöchling wrote on January 9, 2026 at 22:11 In reply to: @knowler.dev . Oof! That rabbit hole wasn’t even on my radar. Matthias Zöchling wrote on January 9, 2026 at 06:28 If you don’t care about text-based web browsers (I can’t blame you), this article doubles as a list of all the cool stuff that got added to HTML. Get involved Have your say on Mastodon, or simply share this article. About this article Written by Matthias Zöchling. Published on January 8, 2026 . Permalink: https://cssence.com/2026/text-based-web-browsers/ 01 Home 02 Articles 03 Threads 04 About 05 Latest 06 Popular 07 Series 08 Archive © 2010–2026 Matthias Zöchling Imprint Webrings Elsewhere Menu Settings RSS feeds Back to top | 2026-01-13T08:48:03 |
https://livesuggest.ai/?lang=en | AI Meeting Assistant Without Bot | LiveSuggest LiveSuggest 1h free Pricing Login Sign up Start session English Language en English fr Français es Español de Deutsch pt Português it Italiano nl Nederlands pl Polski ja 日本語 zh 中文 ko 한국어 tr Türkçe 1h free Pricing Login Sign up Start session Language en English fr Français es Español de Deutsch pt Português it Italiano nl Nederlands pl Polski ja 日本語 zh 中文 ko 한국어 tr Türkçe 🌍 12 languages AI meeting assistant that doesn't join your calls Get real-time AI suggestions via mic or tab sharing. No bot joins your call, no recording stored. Try for free ✓ No credit card ✓ No sign-up ✓ 1h free 👥 Already used by consultants, freelancers, and project managers Example of AI help during meetings MEETING FOLLOW-UP Decision noted: Sarah finalizes the prototype by Friday. NEW IDEA What if we scheduled a retrospective after this sprint to capture the lessons learned? TERM EXPLANATION The "sprint" mentioned refers to a 2-week development cycle in Agile methodology. TERM TRANSLATION "Périmètre" (French) — the scope or boundaries of a project or task. Desktop Mobile Everything You Need to Stay Engaged and Contribute Effectively Real-Time Suggestions Get contextual suggestions as the conversation unfolds. Response ideas, key point reminders, and clarifications appear when you need them most. No Installation Required Access LiveSuggest — the AI meeting assistant without bot — directly from your web browser. No downloads, no extensions, no setup. Start in seconds. Privacy-First Design Built with consent and transparency at its core. Your conversations are processed in real-time with no recording and automatically deleted. No data is retained after your session ends. Common Questions How does it work without a bot? LiveSuggest captures audio directly from your device — via microphone or browser tab sharing. No bot ever joins your call or appears in the participant list. Is it as accurate without recording? Yes. We use the same advanced AI models as recording-based tools. Your audio is processed in real-time and immediately discarded — same accuracy, stronger privacy. Won't suggestions distract me? No. Suggestions appear in a separate window you glance at when needed. They support your participation without interrupting the conversation. How It Works 1 Start a Session Open LiveSuggest in your browser and confirm all participants are informed. Ready to listen 2 Join Your Meeting Join your meeting online or in person. LiveSuggest listens and transcribes in real-time. Transcribing… 3 Get Suggestions Get AI suggestions during meetings — contextual tips to help you contribute effectively. Real-time suggestions 4 customizable suggestion types Meeting follow-up Captures key decisions, action items, and agreements with owners and deadlines, ensuring nothing important slips through. New idea Suggests relevant ideas and fresh perspectives to enrich the discussion and spark new directions. Term explanation Instantly clarifies technical terms, acronyms, and complex concepts mentioned in the conversation, so you never feel lost. Term translation Translates and explains foreign language expressions on the fly — your non-native speaker meeting assistant. No Bot Joins Your Call 📹 Zoom 💼 Teams 🎥 Meet 👥 In-person Works with any browser-based meeting platform Unlike other AI meeting assistants, LiveSuggest doesn't join your call as a bot. Works seamlessly with Google Meet, Zoom, Microsoft Teams or any browser-based platform — just share your tab audio. For in-person meetings, use your microphone. Choose your plan Choose the plan that fits your needs 🧾 Business invoicing available Basic Perfect for trying out $ 3 /month excl. VAT 3 hours of audio ~6 30-minute meetings Get Started ★ Recommended Plus Most popular $ 8 /month excl. VAT 10 hours of audio ~20 30-minute meetings 10h for the price of 8h Choose Plus Pro For power users $ 20 /month excl. VAT 30 hours of audio ~60 30-minute meetings 30h for the price of 20h Go Pro Privacy-First Design ✓ Built with consent and transparency at its core. Your conversations are processed in real-time with no recording and automatically deleted. No data is retained after your session ends. ✓ Audio processed in real-time, not stored ✓ Session data deleted at the end of each session ✓ Privacy Ready to never miss anything and contribute better in meetings? Try LiveSuggest free — no credit card required. Get real-time AI suggestions without bots or recordings. Stay engaged, contribute better. Try Now — Free View Pricing ✓ No credit card ✓ No sign-up ✓ 1h free LiveSuggest Real-time AI meeting assistant with contextual prompts and key reminders to support better conversations — even when working in a second language. Product Pricing FAQ Blog Legal Privacy Terms Legal Notice Consent Support Contact Report a bug © 2026 LiveSuggest. All rights reserved. This site uses cookies We use cookies to ensure the proper functioning of the site and improve your experience. You can accept all cookies, reject them, or customize your preferences. Accept all Reject all Customize | 2026-01-13T08:48:03 |
https://cssence.com/2026/text-based-web-browsers/#dialogs | Text-based web browsers - CSSence.com Text-based web browsers Essay January 8, 2026 Before I start, let me get two things out of the way: In this article I’m not going to include the admittedly cool browsh, because it only works by utilizing Firefox under the hood. When I say text-based, I’m talking about old-school browsers like ELinks , Lynx or w3m. These are also the three browsers I’ve used to test everything described below. The whole article ended up being a rant about how text-based browsers deal with features that got added to HTML. Or more like, how they neglect dealing with said features. Do text-based web browsers still matter? Well, I won’t be the judge of that. I like them, I have them installed, and I test every project I create in them. But they are not what I use to surf the web. Speaking of testing your creations, here’s the good news: If your project has a solid HTML foundation that you then progressively enhance with CSS and JS, you are off to a great start. How did HTML evolve in recent years? While CSS is the star of the show when it comes to new features, HTML ain’t stale either. If we put the long-awaited styleable selects and Apple’s take on toggle switches aside, there’s a lot readily available cross-browser. But here’s the thing: Whenever we say cross-browser, we usually look at the big ones, never at text-based browsers. So in this article I wanna shed some light on how they handle the following recent additions. How do text-based web browsers handle modern HTML? Added features Details Data lists Dialogs Popovers Inert content areas Hidden content Visually hidden content When viewing a web page in a text-based browser, you essentially get plain HTML, no CSS, no JS. There is some “styling”, a result of the elements’ semantics, but don’t expect anything fancy, we are down to colors, indentation, and centered text. It reminds me of what the browsers we are used to give us when they show unstyled HTML—well, HTML with the browser default styles, to be exact. That in turn reminds me of CSS Naked Day. Text-based browsers work well with good old HTML. Said recent additions however are a bit more nuanced (e.g. interactive), so let’s talk about them individually. Details Disclosure widgets are simple interactive elements we no longer need JS for. When <details> are closed, only their <summary> is shown. Text-based browsers have no clue what disclosure widgets are, so they always show the whole <details> content, meaning you always get the open state. This way things can get verbose, but in essence it’s okay. Verdict: Acceptable. Data lists Data lists can be used to add suggested values to an input field. In my tests they have been ignored entirely, Lynx even mentions that it encountered “bad HTML”, probably because it expects <option> only in a <select> parent. At least no browser rendered the options on the screen, they simply fall back to a plain <input> field, which is better than nothing. Side note: I’ve been told data lists have accessibility issues, so … Verdict: Whatever. Dialogs Yes, HTML can do modal and non-modal dialogs, and even alert dialogs, all thanks to the <dialog> element. Initially we needed JS to toggle their visibility, but with the help of the Popover API (see next chapter) we can now even get most of it done in plain HTML. Alas, once again there is no support in text-based browsers, so you’ll end up seeing all dialog content, as if they had their open attribute set. Consequently, there’s no awareness of a form’s method="dialog" nor a submit button’s formmethod="dialog" , so in both cases the form action is triggered. Verdict: Problematic. Popovers The Popover API is probably my favorite new feature, but only if you stick to regular web browsers. Given that dialogs are a type of popover, it’s no surprise that nothing works, and once again all popover content gets dumped onto the screen. By now I think you get the idea, so I won’t even talk about the Invoker Commands API at this point. Verdict: Most likely problematic. Inert content areas A modal dialog makes the rest of the page inert , so we don’t have to do it. But with the global inert attribute we can do this manually too, if we need to make certain parts of the DOM unreachable. Sure enough, text-based browsers will happily let you access interactive elements inside an inert content area. Verdict: Bad. Hidden content We’re now approaching something that is not new at all, the global hidden attribute has been supported for over a decade. It allows us to hide content in the same way as display: none , but directly in HTML. Adding support in text-based browsers has been discussed back in the day, but got rejected, hence it was never implemented. You’ll end up seeing all content marked as hidden . This is the primary reason why I started writing this article, and what enrages me the most. If I decide to hide content in HTML instead of CSS, I must have a very good reason, thus hidden content should not be visible in any browser! Certain progressive enhancement techniques work by hiding content in HTML and then making it visible via CSS or JS. That possibility goes out the window in text-based browsers. Verdict: Epic fail. 😠 🤬 Visually hidden content Just kidding, there’s still no native way in HTML to hide content visually , so we continue to rely on class names like .visually-hidden or .sr-only . No matter how they are named, they need to summon quite a few of lines of CSS to get things done. Whether there should be a native way is up for debate. Personally I would welcome a one-liner to achieve this, but it should remain in the domain of CSS. However, if we had a way in HTML, text-based browsers would display such visually hidden content anyway, that is certain. Verdict: To be continued. Now what? What now? Text-based browsers and modern HTML, no success story in sight. Given the progress we see in web technologies, the gap will only widen, so much so that w3m and its friends might fall into oblivion. Comments Matthias Zöchling wrote on January 8, 2026 at 19:07 It’s 2026 and text-based web browsers still do not know how to handle (not so) recent additions to HTML. cssence.com/2026/text-based-web-browsers Marius Orcsik wrote on January 8, 2026 at 21:14 I think the latest text browser is chawan , which is quite good. Nathan Knowler wrote on January 8, 2026 at 21:55 Interesting, it seems like w3m and lynx can display (declarative) shadow root content, but slots don’t work? Either that or they just don’t know how <template> elements work and are showing the content—but that doesn’t make sense since then the other light DOM content is being swallowed up. Matthias Zöchling wrote on January 9, 2026 at 22:11 In reply to: @knowler.dev . Oof! That rabbit hole wasn’t even on my radar. Matthias Zöchling wrote on January 9, 2026 at 06:28 If you don’t care about text-based web browsers (I can’t blame you), this article doubles as a list of all the cool stuff that got added to HTML. Get involved Have your say on Mastodon, or simply share this article. About this article Written by Matthias Zöchling. Published on January 8, 2026 . Permalink: https://cssence.com/2026/text-based-web-browsers/ 01 Home 02 Articles 03 Threads 04 About 05 Latest 06 Popular 07 Series 08 Archive © 2010–2026 Matthias Zöchling Imprint Webrings Elsewhere Menu Settings RSS feeds Back to top | 2026-01-13T08:48:03 |
https://addons.mozilla.org/hu/firefox/addon/rentgen/ | Rentgen – Szerezze be ezt a kiegészítőt a 🦊 Firefoxhoz (hu) Firefox böngészőkiegészítők Kiegészítők Témák Több… Firefoxhoz Szótárak és nyelvi csomagok Más böngészők oldalai Kiegészítők Androidra Bejelentkezés Keresés Keresés Rentgen szerző: “Internet. Time to act!” Foundation Rentgen to wtyczka, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. 5 (12 értékelés) 5 (12 értékelés) 216 felhasználó 216 felhasználó A Firefox letöltése és a kiegészítő beszerzése Fájl letöltése Kiegészítő metaadatai Képernyőképek A kiegészítő névjegye Rentgen to wtyczka dla przeglądarek opartych o Firefoxa, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. Więcej informacji: https://www.internet-czas-dzialac.pl/odcinek-33-wtyczka-rentgen Funkcje Rentgena: analiza ruchu sieciowego generowanego przez stronę internetową; wizualizacja danych przekazanych do podmiotów trzecich przez odwiedzaną stronę (historia przeglądania użytkownika oraz jego ciasteczka); przygotowywanie zrzutów ekranów narzędzi deweloperskich będących dowodem przekazanych danych do podmiotów trzecich; pomoc w oszacowaniu potencjalnych obszarów roboczych względem zgodności z RODO; generowanie raportu lub treści maila, który można wysłać do administratora oraz Urzędu Ochrony Danych Osobowych. Kod źródłowy Fejlesztői megjegyzések Jeżeli uważasz, że wtyczka Rentgen okazała się przydatna, zostaw nam recenzję. Jeżeli znalazłeś błąd lub masz pomysł na ulepszenie Rentgena, napisz do nas maila: kontakt@internet-czas-dzialac.pl Értékelés 12 szerkesztő által: 5 Jelentkezzen be a kiegészítő értékeléséhez Még nincsenek csillagos értékelések Csillagos értékelés mentve 5 12 4 0 3 0 2 0 1 0 12 értékelés elolvasása Engedélyek és adatok Szükséges engedélyek: Adatvédelmi beállítások olvasása és módosítása Böngésző proxy beállítások vezérlése Az adatai elérése az összes webhelyhez Adatgyűjtés: A fejlesztő szerint ez a kiegészítő nem igényel adatgyűjtést. További tudnivalók További információk Kiegészítő hivatkozásai Kezdőlap Támogatói oldal Támogatási e-mail Verzió 0.2.4 Méret 9,55 MB Legutóbb frissítve 21 napja (2025. dec. 23.) Kapcsolódó kategóriák Webfejlesztés Adatvédelem és biztonság Licenc Kizárólag GNU GPL licenc v3.0 Adatvédelmi irányelvek Olvassa el a kiegészítő adatvédelmi irányelveit Verziótörténet Összes verzió megtekintése Címkék anti malware anti tracker container privacy security Gyűjteményhez adás Válasszon gyűjteményt… Új gyűjtemény létrehozása Kiegészítő jelentése Fejlesztő támogatása A kiegészítő fejlesztője azt kéri, hogy egy csekély összeggel támogassa a további fejlesztést. Támogatás most Ugrás a Mozilla honlapjára Kiegészítők Névjegy Firefox kiegészítők blogja Kiegészítő-műhely Fejlesztőközpont Fejlesztői irányelvek Közösségi blog Fórum Hiba jelentése Értékelési útmutató Böngészők Desktop Mobile Enterprise Termékek Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Adatvédelem Sütik Jogi információk Kivéve, ahol másként van jelölve , az oldal tartalma Creative Commons Nevezd meg! – Így add tovább! licenc v3.0 vagy bármelyik újabb verziója alatt érhető el. Nyelvváltás Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T08:48:03 |
https://cssence.com/about/ | About - CSSence.com About this site CSSence dot com Internal April 18, 2024 Definition The term CSSence is a portmanteau coined by blending the abbreviation for Cascading Style Sheets (CSS) and the word essence . By adding the top level domain (TLD) .com you get the URL for the site you are looking at. However, the TLD is misleading, because there is nothing commercial here. Also, no advertisement. You are welcome. Knowing the history While some threads have been posted in as early as 2010, back then this happened on third-party sites. I launched the actual blog in 2011 on WordPress. This no longer existing predecessor came with the tagline The Essence of CSS . These days, the tagline only makes a cameo appearance in the title on the home page. The blog was conceived as—and I am quoting my old site here— […] an online magazine about CSS, [which] brings you a fresh article every month, filled with a vast amount of CSS goodness. Guess what happened. One article per month. That even worked for a little while, as enough ideas came to my mind, simply by working full-time on web projects. Although back then this translated to spending 85% of said full time in Internet Explorer. At some point however, I was no longer fast enough writing the ideas down because my attention was needed elsewhere. In hindsight, there always are a lot of elsewheres. Growing up Anyway, since the beginning I’ve been blogging about web design and development, and I continued to do so after I got my own domain . With the 2015 relaunch, the site evolved to serve as my personal hub, as you can tell by looking at the Big Table. Add a couple of redesigns, and you’ll end up with what you are looking at today. Off-center logo with the color #d34b6c for the 45° bar. The color became the default when switching to a flat design in 2014. Amidst those redesigns the site has evolved again, because I brought home all the content I published elsewhere, to keep the decentralized web alive. You too should own your own data . In addition, CSSence expanded to become my personal brand, I use this handle as my online identity for All Things Web, from CodePen to GitHub and everything very little in between. Needless to say, this site is curated by me as I’m the main author. I’ve written everything you can find here, unless stated otherwise. Disambiguation This is about CSSence the website. For @CSSence the author, see About Matt. About this page Written by Matthias Zöchling. Last revised on April 18, 2024 . Permalink: https://cssence.com/about/ 01 Home 02 Articles 03 Threads 04 About 05 Latest 06 Popular 07 Series 08 Archive © 2010–2026 Matthias Zöchling Imprint Webrings Elsewhere Menu Settings RSS feeds Back to top | 2026-01-13T08:48:03 |
https://addons.mozilla.org/pl/firefox/extensions/category/web-development/ | Rozszerzenia w kategorii Narzędzia twórców witryn — dodatki do Firefoksa (pl) Aby używać tych dodatków, potrzebujesz pobrać Firefoksa . Zamknij to powiadomienie Dodatki do przeglądarki Firefox Rozszerzenia Motywy Więcej… do Firefoksa Słowniki i pakiety językowe Inne strony Dodatki na Androida Zaloguj się Wyszukaj Wyszukaj Odnaleziono 9779 rozszerzeń w kategorii Narzędzia twórców witryn Filtruj wyniki Uporządkuj według Trafność Ostatnio zaktualizowane Najczęściej używane Najwyżej oceniane Zdobywające popularność Odznaki Wszystkie Polecane Od Firefoksa Wszystkie sprawdzone Wyniki wyszukiwania Dark Reader Polecane Polecane Tryb ciemny dla wszystkich stron internetowych. Zadbaj o swoje oczy, używaj ciemnego motywu przeglądając w dzień i w nocy. Ocena: 4,5/5 Dark Reader Ltd 1 268 146 użytkowników Ghostery – Bloker reklam chroniący prywatność Polecane Polecane Ghostery to potężne rozszerzenie do ochrony prywatności.Blokuje reklamy, wstrzymuje tropiciele i przyspiesza działanie stron internetowych. Ocena: 4,3/5 Ghostery 999 780 użytkowników FoxyProxy Standard Polecane Polecane FoxyProxy jest zaawansowanym menedżerem proxy, który całkowicie zastępuje ograniczone możliwości ustawiania proxy Firefoksa. Oferuje ono więcej funkcji niż SwitchProxy, ProxyButton, QuickProxy, xyzproxy, ProxyTex, TorButton itp. Ocena: 4/5 Eric Jung 197 631 użytkowników Stylus Polecane Polecane Zmień swoją ulubioną witrynę internetową za pomocą Stylusa, aktywnie rozwijanego i zarządzanego przez społeczność menedżera stylów użytkownika. Ocena: 4,7/5 Stylus Team 124 021 użytkowników Download All Images Polecane Polecane Easily save images with a wide range of customization features, such as file size, dimensions, and image type. Ocena: 3,9/5 Joe Ertaba 99 038 użytkowników Flagfox Polecane Polecane Wyświetla flagi w zależności od miejsca położenia obecnego serwera strony i oferuje wiele narzędzi takich jak kontrole bezpieczeństwa strony, whois, tłumaczenia, wyszukiwanie podobnych witryn, walidacje, skracanie adresów URL i więcej... Ocena: 4,6/5 Dave G 96 801 użytkowników User-Agent Switcher and Manager Polecane Polecane Spoof websites trying to gather information about your web navigation—like your browser type and operating system—to deliver distinct content you may not want. Ocena: 4,1/5 Ray 84 251 użytkowników Tab Reloader (page auto refresh) Polecane Polecane An easy-to-use tab reloader with custom reloading time settings for individual tabs Ocena: 4/5 James Fray 71 814 użytkowników Disconnect Polecane Polecane Make the web faster, more private, and more secure. Ocena: 4,1/5 Disconnect 66 639 użytkowników Clear Cache Polecane Polecane Advanced cache clearing with time periods, current tab filter, and smart notifications. Perfect for developers and power users. F9 shortcut included! Ocena: 4,3/5 TenSoja 54 675 użytkowników Chrome Mask Polecane Polecane Makes Firefox wear a mask to look like Chrome to websites that block Firefox otherwise. Ocena: 4,5/5 Dennis Schubert 47 932 użytkowników Clear Browsing Data Polecane Polecane Delete browsing data directly from the browser toolbar. Clear cookies, history and cache with a single click. Ocena: 4,4/5 Armin Sebastian 29 385 użytkowników Measure-it Polecane Polecane Draw a ruler across any webpage to check the width, height, or alignment of page elements in pixels. Ocena: 4,4/5 Trishul 21 154 użytkowników Port Authority Polecane Polecane Blocks malicious websites from port-scanning your computer/network and dynamically blocks all LexisNexis endpoints from running their invasive data collection scripts. Ocena: 4,6/5 Hacks and Hops 19 634 użytkowników Stylebot Polecane Polecane Change the appearance of the web instantly Ocena: 4,8/5 Ankit Ahuja 9122 użytkowników Tampermonkey Tampermonkey is the world's most popular userscript manager. Ocena: 4,7/5 Jan Biniok 754 637 użytkowników React Developer Tools React Developer Tools is a tool that allows you to inspect a React tree, including the component hierarchy, props, state, and more. To get started, just open the Firefox devtools and switch to the "⚛️ Components" or "⚛️ Profiler" tab. Ocena: 4,6/5 React 170 458 użytkowników ColorZilla Advanced Eyedropper, Color Picker, Gradient Generator and other colorful goodies... Ocena: 4,1/5 Alex Sirota 130 173 użytkowników Violentmonkey Userscript support for browsers, open source. Ocena: 4,7/5 Gerald 128 144 użytkowników Wappalyzer Identify technologies on websites Ocena: 4,4/5 Wappalyzer 113 403 użytkowników Cookie-Editor Cookie-Editor lets you efficiently create, edit and delete a cookie for the current tab. Perfect for developing, quickly testing or even manually managing your cookies for your privacy. Ocena: 4,1/5 cgagnier 96 886 użytkowników Windscribe - Free VPN and Ad Blocker Windscribe helps you circumvent censorship, block ads, beacons and trackers on websites you use every day. Ocena: 4,5/5 Windscribe 80 606 użytkowników Ruffle - Flash Emulator Putting Flash back on the web. Designed to be easy to use, this extension will seamlessly enable you to play flash content, with no extra configuration required! Ocena: 4,6/5 Ruffle 73 856 użytkowników Bato Image Auto-Fixer Detect broken bato.to images and automatically fix them. Ocena: 4,2/5 RaidenOQ 71 749 użytkowników Web Developer The Web Developer extension adds various web developer tools to the browser. Ocena: 4,3/5 chrispederick 67 988 użytkowników Wstecz 1 2 3 4 5 6 7 Dalej 1. strona z 392 Strona domowa Mozilli Dodatki O serwisie Blog dodatków do Firefoksa Warsztat rozszerzeń Strefa autora Zasady programistów Blog społeczności Forum Zgłoś błąd Wytyczne recenzji Przeglądarki Desktop Mobile Enterprise Produkty Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Prywatność Ciasteczka Kwestie prawne O ile nie wskazano inaczej , treść tej strony jest dostępna na warunkach licencji Creative Commons Attribution Share-Alike w wersji 3.0 lub nowszej. Zmień język Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T08:48:03 |
https://addons.mozilla.org/pl/firefox/tag/security/ | Dodatki oznaczone etykietą „security” — dodatki do Firefoksa (pl) Aby używać tych dodatków, potrzebujesz pobrać Firefoksa . Zamknij to powiadomienie Dodatki do przeglądarki Firefox Rozszerzenia Motywy Więcej… do Firefoksa Słowniki i pakiety językowe Inne strony Dodatki na Androida Zaloguj się Wyszukaj Wyszukaj 1297 wyników z etykietą „security” Filtruj wyniki Uporządkuj według Trafność Ostatnio zaktualizowane Najczęściej używane Najwyżej oceniane Zdobywające popularność Typ dodatku Wszystkie Rozszerzenie Motyw Odznaki Wszystkie Polecane Od Firefoksa Wszystkie sprawdzone Wyniki wyszukiwania uBlock Origin Polecane Polecane Nareszcie skuteczne blokowanie reklam, niskie użycie procesora i pamięci. Ocena: 4,8/5 Raymond Hill 10 101 185 użytkowników AdGuard AdBlocker Polecane Polecane Adguard AdBlocker skutecznie blokuje wszystkie typy reklam na stronach internetowych, nawet na Facebooku czy YouTube. Ocena: 4,6/5 Adguard Software Ltd 1 579 826 użytkowników Bitwarden - Darmowy menedżer haseł Polecane Polecane Bezpieczny i darmowy menedżer haseł dla wszystkich Twoich urządzeń Ocena: 4,6/5 Bitwarden Inc. 883 923 użytkowników NoScript Security Suite Polecane Polecane Najlepsze zabezpieczenia dla przeglądarek Mozilli! NoScript pozwala blokować wykonywanie skryptów JavaScript i apletów Java na stronach internetowych. Ocena: 4,4/5 Giorgio Maone 256 089 użytkowników Decentraleyes Polecane Polecane Chroni przed śledzeniem przez ośrodki CDN. Zapobiega wysyłaniu zapytań do sieci takich jak Google Hosted Libraries i dostarcza zasoby z lokalnych plików żeby nie psuć stron. Jest uzupełnieniem do klasycznych dodatków blokujących. Ocena: 4,8/5 Thomas Rientjes 251 648 użytkowników SingleFile Polecane Polecane Save an entire web page—including images and styling—as a single HTML file. Ocena: 4,8/5 gildas 77 039 użytkowników RoboForm Password Manager Polecane Polecane RoboForm ułatwia Ci życie, zapamiętując hasła i automatycznie logując Cię na stronach internetowych Ocena: 4,3/5 Siber Systems 54 092 użytkowników FoxyTab Polecane Polecane Collection of Tab Related Actions e.g. Duplicate, Close Duplicates, Close to the Left, Copy Title, Merge Windows, Save as PDF, Copy Urls Tab/All/Left/Right, Host keep/close/close other, Sort by URL/Title, Asce/Desc, Move, Reload, Reload Timer Ocena: 4,6/5 erosman 19 639 użytkowników Port Authority Polecane Polecane Blocks malicious websites from port-scanning your computer/network and dynamically blocks all LexisNexis endpoints from running their invasive data collection scripts. Ocena: 4,6/5 Hacks and Hops 19 634 użytkowników AdBlocker Ultimate Completely remove ALL ads. No “acceptable” ads or whitelisted advertisers allowed. This free extensions also helps block trackers and malware. Ocena: 4,8/5 AdAvoid 1 219 745 użytkowników Malwarebytes Browser Guard Najszybsze i najbezpieczniejsze przeglądanie stron internetowych. Zabezpiecz swoją prywatność, blokując narzędzia śledzenia, reklamy i złośliwe treści. Ocena: 4,2/5 Malwarebytes 440 923 użytkowników LastPass Password Manager LastPass, an award-winning password manager, saves your passwords and gives you secure access from every computer and mobile device. Ocena: 3,7/5 LastPass 421 529 użytkowników Firefox Multi-Account Containers Od Firefoksa Od Firefoksa Firefox Multi-Account Containers lets you keep parts of your online life separated into color-coded tabs. Cookies are separated by container, allowing you to use the web with multiple accounts and integrate Mozilla VPN for an extra layer of privacy. Ocena: 4,6/5 Firefox 376 031 użytkowników 1Password: Password Manager The best way to experience 1Password in your browser. Easily sign in to sites, generate passwords, and store secure information, including logins, credit cards, notes, and more. Ocena: 3,8/5 1Password 358 121 użytkowników Kaspersky Protection Twoja ochrona w internecie zapewniana przez rozszerzenie od Kaspersky Lab Ocena: 4,6/5 Kaspersky 322 744 użytkowników NordVPN - a VPN proxy extension for Firefox Looking for the best VPN extension for Firefox? NordVPN's Firefox VPN proxy extension lets you hide your IP, change your virtual location, and stay safe online with a click. Get a fast, secure, and unlimited VPN for Firefox! Ocena: 3,7/5 NordVPN 286 675 użytkowników Firefox Relay Od Firefoksa Od Firefoksa Firefox Relay lets you generate email aliases that forward to your real inbox. Use it to hide your real email address and protect yourself from hackers and unwanted mail. Ocena: 4,2/5 Firefox 238 802 użytkowników Web Threat Shield Keeps you safe when browsing the web by identifying and blocking dangerous websites. Ocena: 4,3/5 Webroot.com 206 583 użytkowników ESET Browser Privacy & Security Rozszerzona ochrona przeglądarki dzięki rozwiązaniu ESET Prywatność i zabezpieczenia przeglądarki — obejmuje unikatowe funkcje Czyszczenie metadanych, Bezpieczne wyszukiwanie i wiele innych. Ocena: 4,5/5 ESET 201 500 użytkowników Norton Password Manager Norton Password Manager. Free password security you can trust. Ocena: 3,6/5 NortonLifeLock 174 965 użytkowników iCloud Passwords iCloud Passwords lets you fill passwords from iCloud Keychain when signing in to websites using Firefox. Ocena: 2,7/5 Apple Inc. 130 207 użytkowników Proton Pass Free and unlimited password manager to keep your login credentials safe and manage them directly in your browser. Ocena: 4,7/5 Proton 121 751 użytkowników KeePassXC-Browser Official browser plugin for the KeePassXC password manager (https://keepassxc.org). Ocena: 4,3/5 KeePassXC Team 118 079 użytkowników Authenticator Authenticator generates 2-Step Verification codes in your browser. Ocena: 4,2/5 mymindstorm 115 724 użytkowników NordPass® Password Manager & Digital Vault NordPass is your freedom from password stress. Generate and securely store strong passwords and autofill them with a single click. Ocena: 3,9/5 NordVPN 114 642 użytkowników Wstecz 1 2 3 4 5 6 7 Dalej 1. strona z 52 Strona domowa Mozilli Dodatki O serwisie Blog dodatków do Firefoksa Warsztat rozszerzeń Strefa autora Zasady programistów Blog społeczności Forum Zgłoś błąd Wytyczne recenzji Przeglądarki Desktop Mobile Enterprise Produkty Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Prywatność Ciasteczka Kwestie prawne O ile nie wskazano inaczej , treść tej strony jest dostępna na warunkach licencji Creative Commons Attribution Share-Alike w wersji 3.0 lub nowszej. Zmień język Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T08:48:03 |
https://cssence.com/2026/text-based-web-browsers/#visually-hidden-content | Text-based web browsers - CSSence.com Text-based web browsers Essay January 8, 2026 Before I start, let me get two things out of the way: In this article I’m not going to include the admittedly cool browsh, because it only works by utilizing Firefox under the hood. When I say text-based, I’m talking about old-school browsers like ELinks , Lynx or w3m. These are also the three browsers I’ve used to test everything described below. The whole article ended up being a rant about how text-based browsers deal with features that got added to HTML. Or more like, how they neglect dealing with said features. Do text-based web browsers still matter? Well, I won’t be the judge of that. I like them, I have them installed, and I test every project I create in them. But they are not what I use to surf the web. Speaking of testing your creations, here’s the good news: If your project has a solid HTML foundation that you then progressively enhance with CSS and JS, you are off to a great start. How did HTML evolve in recent years? While CSS is the star of the show when it comes to new features, HTML ain’t stale either. If we put the long-awaited styleable selects and Apple’s take on toggle switches aside, there’s a lot readily available cross-browser. But here’s the thing: Whenever we say cross-browser, we usually look at the big ones, never at text-based browsers. So in this article I wanna shed some light on how they handle the following recent additions. How do text-based web browsers handle modern HTML? Added features Details Data lists Dialogs Popovers Inert content areas Hidden content Visually hidden content When viewing a web page in a text-based browser, you essentially get plain HTML, no CSS, no JS. There is some “styling”, a result of the elements’ semantics, but don’t expect anything fancy, we are down to colors, indentation, and centered text. It reminds me of what the browsers we are used to give us when they show unstyled HTML—well, HTML with the browser default styles, to be exact. That in turn reminds me of CSS Naked Day. Text-based browsers work well with good old HTML. Said recent additions however are a bit more nuanced (e.g. interactive), so let’s talk about them individually. Details Disclosure widgets are simple interactive elements we no longer need JS for. When <details> are closed, only their <summary> is shown. Text-based browsers have no clue what disclosure widgets are, so they always show the whole <details> content, meaning you always get the open state. This way things can get verbose, but in essence it’s okay. Verdict: Acceptable. Data lists Data lists can be used to add suggested values to an input field. In my tests they have been ignored entirely, Lynx even mentions that it encountered “bad HTML”, probably because it expects <option> only in a <select> parent. At least no browser rendered the options on the screen, they simply fall back to a plain <input> field, which is better than nothing. Side note: I’ve been told data lists have accessibility issues, so … Verdict: Whatever. Dialogs Yes, HTML can do modal and non-modal dialogs, and even alert dialogs, all thanks to the <dialog> element. Initially we needed JS to toggle their visibility, but with the help of the Popover API (see next chapter) we can now even get most of it done in plain HTML. Alas, once again there is no support in text-based browsers, so you’ll end up seeing all dialog content, as if they had their open attribute set. Consequently, there’s no awareness of a form’s method="dialog" nor a submit button’s formmethod="dialog" , so in both cases the form action is triggered. Verdict: Problematic. Popovers The Popover API is probably my favorite new feature, but only if you stick to regular web browsers. Given that dialogs are a type of popover, it’s no surprise that nothing works, and once again all popover content gets dumped onto the screen. By now I think you get the idea, so I won’t even talk about the Invoker Commands API at this point. Verdict: Most likely problematic. Inert content areas A modal dialog makes the rest of the page inert , so we don’t have to do it. But with the global inert attribute we can do this manually too, if we need to make certain parts of the DOM unreachable. Sure enough, text-based browsers will happily let you access interactive elements inside an inert content area. Verdict: Bad. Hidden content We’re now approaching something that is not new at all, the global hidden attribute has been supported for over a decade. It allows us to hide content in the same way as display: none , but directly in HTML. Adding support in text-based browsers has been discussed back in the day, but got rejected, hence it was never implemented. You’ll end up seeing all content marked as hidden . This is the primary reason why I started writing this article, and what enrages me the most. If I decide to hide content in HTML instead of CSS, I must have a very good reason, thus hidden content should not be visible in any browser! Certain progressive enhancement techniques work by hiding content in HTML and then making it visible via CSS or JS. That possibility goes out the window in text-based browsers. Verdict: Epic fail. 😠 🤬 Visually hidden content Just kidding, there’s still no native way in HTML to hide content visually , so we continue to rely on class names like .visually-hidden or .sr-only . No matter how they are named, they need to summon quite a few of lines of CSS to get things done. Whether there should be a native way is up for debate. Personally I would welcome a one-liner to achieve this, but it should remain in the domain of CSS. However, if we had a way in HTML, text-based browsers would display such visually hidden content anyway, that is certain. Verdict: To be continued. Now what? What now? Text-based browsers and modern HTML, no success story in sight. Given the progress we see in web technologies, the gap will only widen, so much so that w3m and its friends might fall into oblivion. Comments Matthias Zöchling wrote on January 8, 2026 at 19:07 It’s 2026 and text-based web browsers still do not know how to handle (not so) recent additions to HTML. cssence.com/2026/text-based-web-browsers Marius Orcsik wrote on January 8, 2026 at 21:14 I think the latest text browser is chawan , which is quite good. Nathan Knowler wrote on January 8, 2026 at 21:55 Interesting, it seems like w3m and lynx can display (declarative) shadow root content, but slots don’t work? Either that or they just don’t know how <template> elements work and are showing the content—but that doesn’t make sense since then the other light DOM content is being swallowed up. Matthias Zöchling wrote on January 9, 2026 at 22:11 In reply to: @knowler.dev . Oof! That rabbit hole wasn’t even on my radar. Matthias Zöchling wrote on January 9, 2026 at 06:28 If you don’t care about text-based web browsers (I can’t blame you), this article doubles as a list of all the cool stuff that got added to HTML. Get involved Have your say on Mastodon, or simply share this article. About this article Written by Matthias Zöchling. Published on January 8, 2026 . Permalink: https://cssence.com/2026/text-based-web-browsers/ 01 Home 02 Articles 03 Threads 04 About 05 Latest 06 Popular 07 Series 08 Archive © 2010–2026 Matthias Zöchling Imprint Webrings Elsewhere Menu Settings RSS feeds Back to top | 2026-01-13T08:48:03 |
https://cssence.com/articles/ | Articles - CSSence.com Articles The opposite of Threads. Index January 8, 2026 Looking for Essays about Web Design and Development? In need of an Extra dose of code? What about the Events I’ve attended or spoken at? This is the right place. And let’s not forget my more personal pieces, filed under Editorials. Latest posts Text-based web browsers How do they fare with (not so) recent additions to HTML? Essay January 8, 2026 Accessibility is personal Is A11Y work rewarding? Demanding? Exhausting? All of the above? Essay December 19, 2025 @import ⚭ @supports How to load a stylesheet conditionally based on feature detection. Extra December 3, 2025 Redesigning in the open - Without further notice The quiet way: How to not (or how not to) announce a redesign. Editorial November 7, 2025 No close quote? There are multiple ways to do ornamental quotation marks. Extra November 5, 2025 Instant snapport How to tweak the optimal viewing region of the scrollport. Extra October 16, 2025 Nesting color schemes This is indeed about having dark and light mode on the same page. Essay October 11, 2025 Animating emojis The waiting is the hardest part. Extra July 1, 2025 CSS-in-Graz meetup #7 I spoke about the last 30 years of CSS, abridged. Event June 10, 2025 Pure CSS image reveal Actually, the HTML needs to help out here, a lot. Extra April 7, 2025 CSS space-size The long-awaited companion for tab-size. Extra April 1, 2025 The Popover API and Firefox’s Shift+Tab trap If it looks like a bug, smells like a bug, and quacks like a bug, it’s probably a bug. Extra February 21, 2025 The list above contains only the twelve most recent entries. In this section alone, there are 126 blog posts, and there are other sections on this site. To see what else is going on, you may want to head over to the home page or browse using the navigation below. About this index page Curated by Matthias Zöchling. Last revised on January 8, 2026 . Permalink: https://cssence.com/articles/ 01 Home 02 Articles 03 Threads 04 About 05 Latest 06 Popular 07 Series 08 Archive © 2010–2026 Matthias Zöchling Imprint Webrings Elsewhere Menu Settings RSS feeds Back to top | 2026-01-13T08:48:03 |
https://cssence.com/2026/text-based-web-browsers/#top | Text-based web browsers - CSSence.com Text-based web browsers Essay January 8, 2026 Before I start, let me get two things out of the way: In this article I’m not going to include the admittedly cool browsh, because it only works by utilizing Firefox under the hood. When I say text-based, I’m talking about old-school browsers like ELinks , Lynx or w3m. These are also the three browsers I’ve used to test everything described below. The whole article ended up being a rant about how text-based browsers deal with features that got added to HTML. Or more like, how they neglect dealing with said features. Do text-based web browsers still matter? Well, I won’t be the judge of that. I like them, I have them installed, and I test every project I create in them. But they are not what I use to surf the web. Speaking of testing your creations, here’s the good news: If your project has a solid HTML foundation that you then progressively enhance with CSS and JS, you are off to a great start. How did HTML evolve in recent years? While CSS is the star of the show when it comes to new features, HTML ain’t stale either. If we put the long-awaited styleable selects and Apple’s take on toggle switches aside, there’s a lot readily available cross-browser. But here’s the thing: Whenever we say cross-browser, we usually look at the big ones, never at text-based browsers. So in this article I wanna shed some light on how they handle the following recent additions. How do text-based web browsers handle modern HTML? Added features Details Data lists Dialogs Popovers Inert content areas Hidden content Visually hidden content When viewing a web page in a text-based browser, you essentially get plain HTML, no CSS, no JS. There is some “styling”, a result of the elements’ semantics, but don’t expect anything fancy, we are down to colors, indentation, and centered text. It reminds me of what the browsers we are used to give us when they show unstyled HTML—well, HTML with the browser default styles, to be exact. That in turn reminds me of CSS Naked Day. Text-based browsers work well with good old HTML. Said recent additions however are a bit more nuanced (e.g. interactive), so let’s talk about them individually. Details Disclosure widgets are simple interactive elements we no longer need JS for. When <details> are closed, only their <summary> is shown. Text-based browsers have no clue what disclosure widgets are, so they always show the whole <details> content, meaning you always get the open state. This way things can get verbose, but in essence it’s okay. Verdict: Acceptable. Data lists Data lists can be used to add suggested values to an input field. In my tests they have been ignored entirely, Lynx even mentions that it encountered “bad HTML”, probably because it expects <option> only in a <select> parent. At least no browser rendered the options on the screen, they simply fall back to a plain <input> field, which is better than nothing. Side note: I’ve been told data lists have accessibility issues, so … Verdict: Whatever. Dialogs Yes, HTML can do modal and non-modal dialogs, and even alert dialogs, all thanks to the <dialog> element. Initially we needed JS to toggle their visibility, but with the help of the Popover API (see next chapter) we can now even get most of it done in plain HTML. Alas, once again there is no support in text-based browsers, so you’ll end up seeing all dialog content, as if they had their open attribute set. Consequently, there’s no awareness of a form’s method="dialog" nor a submit button’s formmethod="dialog" , so in both cases the form action is triggered. Verdict: Problematic. Popovers The Popover API is probably my favorite new feature, but only if you stick to regular web browsers. Given that dialogs are a type of popover, it’s no surprise that nothing works, and once again all popover content gets dumped onto the screen. By now I think you get the idea, so I won’t even talk about the Invoker Commands API at this point. Verdict: Most likely problematic. Inert content areas A modal dialog makes the rest of the page inert , so we don’t have to do it. But with the global inert attribute we can do this manually too, if we need to make certain parts of the DOM unreachable. Sure enough, text-based browsers will happily let you access interactive elements inside an inert content area. Verdict: Bad. Hidden content We’re now approaching something that is not new at all, the global hidden attribute has been supported for over a decade. It allows us to hide content in the same way as display: none , but directly in HTML. Adding support in text-based browsers has been discussed back in the day, but got rejected, hence it was never implemented. You’ll end up seeing all content marked as hidden . This is the primary reason why I started writing this article, and what enrages me the most. If I decide to hide content in HTML instead of CSS, I must have a very good reason, thus hidden content should not be visible in any browser! Certain progressive enhancement techniques work by hiding content in HTML and then making it visible via CSS or JS. That possibility goes out the window in text-based browsers. Verdict: Epic fail. 😠 🤬 Visually hidden content Just kidding, there’s still no native way in HTML to hide content visually , so we continue to rely on class names like .visually-hidden or .sr-only . No matter how they are named, they need to summon quite a few of lines of CSS to get things done. Whether there should be a native way is up for debate. Personally I would welcome a one-liner to achieve this, but it should remain in the domain of CSS. However, if we had a way in HTML, text-based browsers would display such visually hidden content anyway, that is certain. Verdict: To be continued. Now what? What now? Text-based browsers and modern HTML, no success story in sight. Given the progress we see in web technologies, the gap will only widen, so much so that w3m and its friends might fall into oblivion. Comments Matthias Zöchling wrote on January 8, 2026 at 19:07 It’s 2026 and text-based web browsers still do not know how to handle (not so) recent additions to HTML. cssence.com/2026/text-based-web-browsers Marius Orcsik wrote on January 8, 2026 at 21:14 I think the latest text browser is chawan , which is quite good. Nathan Knowler wrote on January 8, 2026 at 21:55 Interesting, it seems like w3m and lynx can display (declarative) shadow root content, but slots don’t work? Either that or they just don’t know how <template> elements work and are showing the content—but that doesn’t make sense since then the other light DOM content is being swallowed up. Matthias Zöchling wrote on January 9, 2026 at 22:11 In reply to: @knowler.dev . Oof! That rabbit hole wasn’t even on my radar. Matthias Zöchling wrote on January 9, 2026 at 06:28 If you don’t care about text-based web browsers (I can’t blame you), this article doubles as a list of all the cool stuff that got added to HTML. Get involved Have your say on Mastodon, or simply share this article. About this article Written by Matthias Zöchling. Published on January 8, 2026 . Permalink: https://cssence.com/2026/text-based-web-browsers/ 01 Home 02 Articles 03 Threads 04 About 05 Latest 06 Popular 07 Series 08 Archive © 2010–2026 Matthias Zöchling Imprint Webrings Elsewhere Menu Settings RSS feeds Back to top | 2026-01-13T08:48:03 |
https://addons.mozilla.org/sq/firefox/addon/rentgen/ | Rentgen – Merreni këtë Zgjerim për 🦊 Firefox (sq) Shtesa Shfletuesi Firefox Zgjerime Tema Më tepër… për Firefox Fjalorë & Paketa Gjuhësore Sajte Shfletuesish të Tjerë Shtesa për Android Hyni Kërko Kërko Rentgen nga “Internet. Time to act!” Foundation Rentgen to wtyczka, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. 5 (12 shqyrtime) 5 (12 shqyrtime) 216 Përdorues 216 Përdorues Shkarkoni Firefox-in dhe merrni zgjerimin Shkarko kartelën Tejtëdhëna Zgjerimi Foto ekrani Rreth këtij zgjerimi Rentgen to wtyczka dla przeglądarek opartych o Firefoxa, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. Więcej informacji: https://www.internet-czas-dzialac.pl/odcinek-33-wtyczka-rentgen Funkcje Rentgena: analiza ruchu sieciowego generowanego przez stronę internetową; wizualizacja danych przekazanych do podmiotów trzecich przez odwiedzaną stronę (historia przeglądania użytkownika oraz jego ciasteczka); przygotowywanie zrzutów ekranów narzędzi deweloperskich będących dowodem przekazanych danych do podmiotów trzecich; pomoc w oszacowaniu potencjalnych obszarów roboczych względem zgodności z RODO; generowanie raportu lub treści maila, który można wysłać do administratora oraz Urzędu Ochrony Danych Osobowych. Kod źródłowy Komente nga zhvillues Jeżeli uważasz, że wtyczka Rentgen okazała się przydatna, zostaw nam recenzję. Jeżeli znalazłeś błąd lub masz pomysł na ulepszenie Rentgena, napisz do nas maila: kontakt@internet-czas-dzialac.pl Vlerësuar me 5 nga 12 shqyrtues Që të vlerësoni këtë zgjerim, bëni hyrjen Ende pa vlerësime Vlerësimi me yje u ruajt 5 12 4 0 3 0 2 0 1 0 Lexoni krejt 12 shqyrtimet Leje dhe të dhëna Leje të domosdoshme: Të lexojë dhe ndryshojë rregullime privatësie Të kontrollojë rregullime ndërmjetësi shfletuesi Të hyjë në të dhënat tuaja për krejt sajtet Grumbullim të dhënash: Zhvilluesi thotë se ky zgjerim s’lyp mbledhje të dhënash. Mësoni më tepër Më tepër të dhëna Lidhje shtese Faqe hyrëse Sajt asistence Email Asistence Version 0.2.4 Madhësi 9,55 MB Përditësuar së fundi më 21 ditë më parë (23 Dhj 2025) Kategori të Afërta Zhvillim Web Privatësi & Siguri Licencë Vetëm GNU General Public License v3.0 Rregulla Privatësie Lexoni rregullat e privatësisë për këtë shtesë Historik Versionesh Shihini krejt versionet Etiketa anti malware anti tracker container privacy security Shtojeni në koleksion Përzgjidhni një koleksion… Krijoni koleksion të ri Raportojeni këtë shtesë Përkraheni këtë zhvillues Zhvilluesi i kësaj shtese dëshiron që të ndihmoni duke mbështetur zhvillimin e mëtejshëm të saj përmes një kontributi të vogël. Kontribuoni tani Shkoni te faqja hyrëse e Mozilla-s Shtesa Mbi Blog Shtesash Firefox-i Praktikë Mbi Zgjerime Qendër Zhvilluesish Rregulla Për Zhvilluesit Blog Bashkësie Forum Njoftoni një të metë Udhërrëfyes Shqyrtimesh Shfletues Desktop Mobile Enterprise Produkte Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Privatësi Cookies Ligjore Hiq atje ku shënohet ndryshe, lënda e këtij sajti licencohet sipas licencës Creative Commons Attribution Share-Alike License v3.0 ose çfarëdo versioni të mëvonshëm. Ndryshoni gjuhën Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T08:48:03 |
https://github.com/skills/code-with-codespaces | GitHub - skills/code-with-codespaces: Develop code using GitHub Codespaces and Visual Studio Code! Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} skills / code-with-codespaces Public template Notifications You must be signed in to change notification settings Fork 1.1k Star 380 Develop code using GitHub Codespaces and Visual Studio Code! License MIT license 380 stars 1.1k forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 4 Pull requests 8 Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Security Insights skills/code-with-codespaces main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 24 Commits .github .github .gitignore .gitignore LICENSE LICENSE README.md README.md codespace.md codespace.md index.html index.html View all files Repository files navigation README Code of conduct Contributing MIT license Security Code with GitHub Codespaces and Visual Studio Code Develop code using GitHub Codespaces and Visual Studio Code! Welcome GitHub Codespaces is a development environment that's hosted in the cloud. Who this is for : Developers, DevOps Engineers, Engineering Managers, Product Managers. What you'll learn : How to create a codespace, push code from a codespace, select a custom image, and customize a codespace. What you'll build : A codespace with devcontainer.json files, customizations, and personalizations. Prerequisites : If you need to learn about Visual Studio Code, read Visual Studio Code Docs first. How long : This course can be completed in less than an hour. In this course, you will: Create your first codespace Add a custom image Customize your codespace Personalize your codespace How to start this course Right-click Start course and open the link in a new tab. In the new tab, most of the prompts will automatically fill in for you. For owner, choose your personal account or an organization to host the repository. We recommend creating a public repository, as private repositories will use Actions minutes . Scroll down and click the Create repository button at the bottom of the form. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README. Get help: Post in our discussion board • Review the GitHub status page © 2023 GitHub • Code of Conduct • MIT License About Develop code using GitHub Codespaces and Visual Studio Code! Topics skills-course Resources Readme License MIT license Code of conduct Code of conduct Contributing Contributing Security policy Security policy Uh oh! There was an error while loading. Please reload this page . Activity Custom properties Stars 380 stars Watchers 15 watching Forks 1.1k forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 12 Languages HTML 100.0% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:48:03 |
https://cssence.com/2026/text-based-web-browsers/#hidden-content | Text-based web browsers - CSSence.com Text-based web browsers Essay January 8, 2026 Before I start, let me get two things out of the way: In this article I’m not going to include the admittedly cool browsh, because it only works by utilizing Firefox under the hood. When I say text-based, I’m talking about old-school browsers like ELinks , Lynx or w3m. These are also the three browsers I’ve used to test everything described below. The whole article ended up being a rant about how text-based browsers deal with features that got added to HTML. Or more like, how they neglect dealing with said features. Do text-based web browsers still matter? Well, I won’t be the judge of that. I like them, I have them installed, and I test every project I create in them. But they are not what I use to surf the web. Speaking of testing your creations, here’s the good news: If your project has a solid HTML foundation that you then progressively enhance with CSS and JS, you are off to a great start. How did HTML evolve in recent years? While CSS is the star of the show when it comes to new features, HTML ain’t stale either. If we put the long-awaited styleable selects and Apple’s take on toggle switches aside, there’s a lot readily available cross-browser. But here’s the thing: Whenever we say cross-browser, we usually look at the big ones, never at text-based browsers. So in this article I wanna shed some light on how they handle the following recent additions. How do text-based web browsers handle modern HTML? Added features Details Data lists Dialogs Popovers Inert content areas Hidden content Visually hidden content When viewing a web page in a text-based browser, you essentially get plain HTML, no CSS, no JS. There is some “styling”, a result of the elements’ semantics, but don’t expect anything fancy, we are down to colors, indentation, and centered text. It reminds me of what the browsers we are used to give us when they show unstyled HTML—well, HTML with the browser default styles, to be exact. That in turn reminds me of CSS Naked Day. Text-based browsers work well with good old HTML. Said recent additions however are a bit more nuanced (e.g. interactive), so let’s talk about them individually. Details Disclosure widgets are simple interactive elements we no longer need JS for. When <details> are closed, only their <summary> is shown. Text-based browsers have no clue what disclosure widgets are, so they always show the whole <details> content, meaning you always get the open state. This way things can get verbose, but in essence it’s okay. Verdict: Acceptable. Data lists Data lists can be used to add suggested values to an input field. In my tests they have been ignored entirely, Lynx even mentions that it encountered “bad HTML”, probably because it expects <option> only in a <select> parent. At least no browser rendered the options on the screen, they simply fall back to a plain <input> field, which is better than nothing. Side note: I’ve been told data lists have accessibility issues, so … Verdict: Whatever. Dialogs Yes, HTML can do modal and non-modal dialogs, and even alert dialogs, all thanks to the <dialog> element. Initially we needed JS to toggle their visibility, but with the help of the Popover API (see next chapter) we can now even get most of it done in plain HTML. Alas, once again there is no support in text-based browsers, so you’ll end up seeing all dialog content, as if they had their open attribute set. Consequently, there’s no awareness of a form’s method="dialog" nor a submit button’s formmethod="dialog" , so in both cases the form action is triggered. Verdict: Problematic. Popovers The Popover API is probably my favorite new feature, but only if you stick to regular web browsers. Given that dialogs are a type of popover, it’s no surprise that nothing works, and once again all popover content gets dumped onto the screen. By now I think you get the idea, so I won’t even talk about the Invoker Commands API at this point. Verdict: Most likely problematic. Inert content areas A modal dialog makes the rest of the page inert , so we don’t have to do it. But with the global inert attribute we can do this manually too, if we need to make certain parts of the DOM unreachable. Sure enough, text-based browsers will happily let you access interactive elements inside an inert content area. Verdict: Bad. Hidden content We’re now approaching something that is not new at all, the global hidden attribute has been supported for over a decade. It allows us to hide content in the same way as display: none , but directly in HTML. Adding support in text-based browsers has been discussed back in the day, but got rejected, hence it was never implemented. You’ll end up seeing all content marked as hidden . This is the primary reason why I started writing this article, and what enrages me the most. If I decide to hide content in HTML instead of CSS, I must have a very good reason, thus hidden content should not be visible in any browser! Certain progressive enhancement techniques work by hiding content in HTML and then making it visible via CSS or JS. That possibility goes out the window in text-based browsers. Verdict: Epic fail. 😠 🤬 Visually hidden content Just kidding, there’s still no native way in HTML to hide content visually , so we continue to rely on class names like .visually-hidden or .sr-only . No matter how they are named, they need to summon quite a few of lines of CSS to get things done. Whether there should be a native way is up for debate. Personally I would welcome a one-liner to achieve this, but it should remain in the domain of CSS. However, if we had a way in HTML, text-based browsers would display such visually hidden content anyway, that is certain. Verdict: To be continued. Now what? What now? Text-based browsers and modern HTML, no success story in sight. Given the progress we see in web technologies, the gap will only widen, so much so that w3m and its friends might fall into oblivion. Comments Matthias Zöchling wrote on January 8, 2026 at 19:07 It’s 2026 and text-based web browsers still do not know how to handle (not so) recent additions to HTML. cssence.com/2026/text-based-web-browsers Marius Orcsik wrote on January 8, 2026 at 21:14 I think the latest text browser is chawan , which is quite good. Nathan Knowler wrote on January 8, 2026 at 21:55 Interesting, it seems like w3m and lynx can display (declarative) shadow root content, but slots don’t work? Either that or they just don’t know how <template> elements work and are showing the content—but that doesn’t make sense since then the other light DOM content is being swallowed up. Matthias Zöchling wrote on January 9, 2026 at 22:11 In reply to: @knowler.dev . Oof! That rabbit hole wasn’t even on my radar. Matthias Zöchling wrote on January 9, 2026 at 06:28 If you don’t care about text-based web browsers (I can’t blame you), this article doubles as a list of all the cool stuff that got added to HTML. Get involved Have your say on Mastodon, or simply share this article. About this article Written by Matthias Zöchling. Published on January 8, 2026 . Permalink: https://cssence.com/2026/text-based-web-browsers/ 01 Home 02 Articles 03 Threads 04 About 05 Latest 06 Popular 07 Series 08 Archive © 2010–2026 Matthias Zöchling Imprint Webrings Elsewhere Menu Settings RSS feeds Back to top | 2026-01-13T08:48:03 |
https://cssence.com/2026/text-based-web-browsers/#popovers | Text-based web browsers - CSSence.com Text-based web browsers Essay January 8, 2026 Before I start, let me get two things out of the way: In this article I’m not going to include the admittedly cool browsh, because it only works by utilizing Firefox under the hood. When I say text-based, I’m talking about old-school browsers like ELinks , Lynx or w3m. These are also the three browsers I’ve used to test everything described below. The whole article ended up being a rant about how text-based browsers deal with features that got added to HTML. Or more like, how they neglect dealing with said features. Do text-based web browsers still matter? Well, I won’t be the judge of that. I like them, I have them installed, and I test every project I create in them. But they are not what I use to surf the web. Speaking of testing your creations, here’s the good news: If your project has a solid HTML foundation that you then progressively enhance with CSS and JS, you are off to a great start. How did HTML evolve in recent years? While CSS is the star of the show when it comes to new features, HTML ain’t stale either. If we put the long-awaited styleable selects and Apple’s take on toggle switches aside, there’s a lot readily available cross-browser. But here’s the thing: Whenever we say cross-browser, we usually look at the big ones, never at text-based browsers. So in this article I wanna shed some light on how they handle the following recent additions. How do text-based web browsers handle modern HTML? Added features Details Data lists Dialogs Popovers Inert content areas Hidden content Visually hidden content When viewing a web page in a text-based browser, you essentially get plain HTML, no CSS, no JS. There is some “styling”, a result of the elements’ semantics, but don’t expect anything fancy, we are down to colors, indentation, and centered text. It reminds me of what the browsers we are used to give us when they show unstyled HTML—well, HTML with the browser default styles, to be exact. That in turn reminds me of CSS Naked Day. Text-based browsers work well with good old HTML. Said recent additions however are a bit more nuanced (e.g. interactive), so let’s talk about them individually. Details Disclosure widgets are simple interactive elements we no longer need JS for. When <details> are closed, only their <summary> is shown. Text-based browsers have no clue what disclosure widgets are, so they always show the whole <details> content, meaning you always get the open state. This way things can get verbose, but in essence it’s okay. Verdict: Acceptable. Data lists Data lists can be used to add suggested values to an input field. In my tests they have been ignored entirely, Lynx even mentions that it encountered “bad HTML”, probably because it expects <option> only in a <select> parent. At least no browser rendered the options on the screen, they simply fall back to a plain <input> field, which is better than nothing. Side note: I’ve been told data lists have accessibility issues, so … Verdict: Whatever. Dialogs Yes, HTML can do modal and non-modal dialogs, and even alert dialogs, all thanks to the <dialog> element. Initially we needed JS to toggle their visibility, but with the help of the Popover API (see next chapter) we can now even get most of it done in plain HTML. Alas, once again there is no support in text-based browsers, so you’ll end up seeing all dialog content, as if they had their open attribute set. Consequently, there’s no awareness of a form’s method="dialog" nor a submit button’s formmethod="dialog" , so in both cases the form action is triggered. Verdict: Problematic. Popovers The Popover API is probably my favorite new feature, but only if you stick to regular web browsers. Given that dialogs are a type of popover, it’s no surprise that nothing works, and once again all popover content gets dumped onto the screen. By now I think you get the idea, so I won’t even talk about the Invoker Commands API at this point. Verdict: Most likely problematic. Inert content areas A modal dialog makes the rest of the page inert , so we don’t have to do it. But with the global inert attribute we can do this manually too, if we need to make certain parts of the DOM unreachable. Sure enough, text-based browsers will happily let you access interactive elements inside an inert content area. Verdict: Bad. Hidden content We’re now approaching something that is not new at all, the global hidden attribute has been supported for over a decade. It allows us to hide content in the same way as display: none , but directly in HTML. Adding support in text-based browsers has been discussed back in the day, but got rejected, hence it was never implemented. You’ll end up seeing all content marked as hidden . This is the primary reason why I started writing this article, and what enrages me the most. If I decide to hide content in HTML instead of CSS, I must have a very good reason, thus hidden content should not be visible in any browser! Certain progressive enhancement techniques work by hiding content in HTML and then making it visible via CSS or JS. That possibility goes out the window in text-based browsers. Verdict: Epic fail. 😠 🤬 Visually hidden content Just kidding, there’s still no native way in HTML to hide content visually , so we continue to rely on class names like .visually-hidden or .sr-only . No matter how they are named, they need to summon quite a few of lines of CSS to get things done. Whether there should be a native way is up for debate. Personally I would welcome a one-liner to achieve this, but it should remain in the domain of CSS. However, if we had a way in HTML, text-based browsers would display such visually hidden content anyway, that is certain. Verdict: To be continued. Now what? What now? Text-based browsers and modern HTML, no success story in sight. Given the progress we see in web technologies, the gap will only widen, so much so that w3m and its friends might fall into oblivion. Comments Matthias Zöchling wrote on January 8, 2026 at 19:07 It’s 2026 and text-based web browsers still do not know how to handle (not so) recent additions to HTML. cssence.com/2026/text-based-web-browsers Marius Orcsik wrote on January 8, 2026 at 21:14 I think the latest text browser is chawan , which is quite good. Nathan Knowler wrote on January 8, 2026 at 21:55 Interesting, it seems like w3m and lynx can display (declarative) shadow root content, but slots don’t work? Either that or they just don’t know how <template> elements work and are showing the content—but that doesn’t make sense since then the other light DOM content is being swallowed up. Matthias Zöchling wrote on January 9, 2026 at 22:11 In reply to: @knowler.dev . Oof! That rabbit hole wasn’t even on my radar. Matthias Zöchling wrote on January 9, 2026 at 06:28 If you don’t care about text-based web browsers (I can’t blame you), this article doubles as a list of all the cool stuff that got added to HTML. Get involved Have your say on Mastodon, or simply share this article. About this article Written by Matthias Zöchling. Published on January 8, 2026 . Permalink: https://cssence.com/2026/text-based-web-browsers/ 01 Home 02 Articles 03 Threads 04 About 05 Latest 06 Popular 07 Series 08 Archive © 2010–2026 Matthias Zöchling Imprint Webrings Elsewhere Menu Settings RSS feeds Back to top | 2026-01-13T08:48:03 |
https://pragprog.com/titles/btlang/seven-languages-in-seven-weeks/#:~:text=Ruby%2C%20Io%2C%20Prolog%2C%20Scala,languages%20within%20a%20single%20book. | Seven Languages in Seven Weeks: A Pragmatic Guide to Learning Programming Languages by Bruce A. Tate ☰ Home Books Authors Publish with Us Support eGifts Swag My Orders Prereqs Resources Extracts Author Tweet this About This Title Pages: 330 Published: October 2010 ISBN: 9781934356593 In Print Seven Languages in Seven Weeks A Pragmatic Guide to Learning Programming Languages by Bruce A. Tate You should learn a programming language every year, as recommended by The Pragmatic Programmer . But if one per year is good, how about Seven Languages in Seven Weeks ? In this book you’ll get a hands-on tour of Clojure, Haskell, Io, Prolog, Scala, Erlang, and Ruby. Whether or not your favorite language is on that list, you’ll broaden your perspective of programming by examining these languages side-by-side. You’ll learn something new from each, and best of all, you’ll learn how to learn a language quickly. Just as each new spoken language can make you smarter and increase your options, each programming language increases your mental tool kit, adding new abstractions you can throw at each new problem. Knowledge is power. The Seven in Seven series builds on that power across many different dimensions. Each chapter in each book walks you through some nontrivial problem with each language, or database, or web server. These books take commitment to read, but their impact can be profound. eBook Formats: PDF for desktop/tablets epub for Apple Books, e-readers mobi for Kindle readers Get all eBook formats here for $27.95 (USD) Add to Cart Paperback Formats: Order via Bookshop (U.S. Only) Please support indie bookstores! Find indie bookstores in the U.S. Find indie bookstores around the world . Ruby, Io, Prolog, Scala, Erlang, Clojure, Haskell. With Seven Languages in Seven Weeks, by Bruce A. Tate, you’ll go beyond the syntax—and beyond the 20-minute tutorial you’ll find someplace online. This book has an audacious goal: to present a meaningful exploration of seven languages within a single book. Seven Languages hits what’s essential and unique about each language and will help teach you how to grok new languages. For each language, you’ll solve a nontrivial problem, using techniques that show off the language’s most important features. You’ll discover the strengths and weaknesses of each language while dissecting the process of learning languages quickly—for example, finding the typing and programming models, decision structures, and how you interact with them. Among this group of seven, you’ll explore the most critical programming models of our time. Learn the dynamic typing that makes Ruby, Python, and Perl so flexible and compelling. Understand the underlying prototype system that’s at the heart of JavaScript. See how pattern matching in Prolog shaped the development of Scala and Erlang. Discover how pure functional programming in Haskell is different from the Lisp family of languages, including Clojure. Explore the concurrency techniques that are quickly becoming the backbone of a new generation of Internet applications. Find out how to use Erlang’s let-it-crash philosophy for building fault-tolerant systems. Understand the actor model that drives concurrency design in Io and Scala. Learn how Clojure uses versioning to solve some of the most difficult concurrency problems. It’s all here, all in one place. Use the concepts from one language to find creative solutions in another—or discover a language that may become one of your favorites. What You Need Resources Errata, typos, suggestions Source Code (zip file) Releases: 2012/03/27 P5.0 Fifth Printing. For a list of corrections included is this release, please see [errata](http://pragprog.com/titles/btlang/errata). 2011/09/26 P4.0 Fourth Printing 2011/05/17 P3.0 *Third Printing 2011/02/03 P2.0 *Second Printing Contents & Extracts Full Table of Contents Foreword Introduction Ruby Io excerpt Prolog excerpt Scala Erlang Clojure Haskell Wrap-up Bibliography Author Bruce Tate runs RapidRed, an Austin, TX-based practice that consults on lightweight development in Ruby. Previously he worked at IBM in roles ranging from a database systems programmer to Java consultant. He left IBM to work for several startups in roles ranging from Client Solutions Director to CTO. He speaks internationally and is the author of more than ten books, including From Java to Ruby, Deploying Rails Applications, the best-selling Bitter series, Beyond Java, and the Jolt-winning Better, Faster, Lighter Java. eBook Formats: PDF for desktop/tablets epub for Apple Books, e-readers mobi for Kindle readers Get all eBook formats here for $27.95 (USD) Add to Cart Paperback Formats: Order via Bookshop (U.S. Only) Please support indie bookstores! Find indie bookstores in the U.S. Find indie bookstores around the world . Releases, Offers & More Be the first to hear about our newest content, best promotions and upcoming events. Plus get 25% off your next purchase. Newsletter Sign Up Related categories: Seven in Seven Programming Languages Java and JVM Languages Related Titles: Seven Concurrency Models in Seven Weeks Seven Web Frameworks in Seven Weeks Programming Ruby 1.9 & 2.0 (4th edition) Functional Programming: A PragPub Anthology Seven More Languages in Seven Weeks About This Title Pages: 330 Published: October 2010 ISBN: 9781934356593 Edition: 1 In Print Contact About Us Privacy Terms of Use Security Newsletter eGifts Partnerships & Promotions Careers © 1999-2026 The Pragmatic Programmers, LLC. All Rights Reserved. | 2026-01-13T08:48:03 |
https://popcorn.forem.com/t/cinema | Cinema - 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 # cinema Follow Hide Moviegoing experiences and theaters Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu AMC Theatres to Trim Pre-Show by 4 to 5 Minutes, CEO Says Movie News Movie News Movie News Follow Aug 12 '25 AMC Theatres to Trim Pre-Show by 4 to 5 Minutes, CEO Says # marketing # filmindustry # boxoffice # cinema Comments Add Comment 1 min read AMC Theatres Looks To Shorten Ad Preshow Following Studios' Ire Movie News Movie News Movie News Follow Aug 12 '25 AMC Theatres Looks To Shorten Ad Preshow Following Studios' Ire # movies # boxoffice # cinema # filmindustry Comments Add Comment 1 min read AMC Theatres Looks To Shorten Ad Preshow Following Studios' Ire Movie News Movie News Movie News Follow Aug 8 '25 AMC Theatres Looks To Shorten Ad Preshow Following Studios' Ire # studios # distribution # filmindustry # cinema Comments Add Comment 1 min read AMC Theatres Looks To Shorten Ad Preshow Following Studios' Ire Movie News Movie News Movie News Follow Aug 7 '25 AMC Theatres Looks To Shorten Ad Preshow Following Studios' Ire # filmindustry # distribution # cinema # studios 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 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 Francis Ford Coppola Says That 'Megalopolis' Will Get a Weird Recut Movie News Movie News Movie News Follow Jul 29 '25 Francis Ford Coppola Says That 'Megalopolis' Will Get a Weird Recut # marketing # offtopic # filmindustry # cinema Comments Add Comment 1 min read ‘The Odyssey' Imax 70mm Screenings Are Already Being Scheduled for July 2026 Movie News Movie News Movie News Follow Jul 17 '25 ‘The Odyssey' Imax 70mm Screenings Are Already Being Scheduled for July 2026 # movies # imax # filmindustry # cinema Comments Add Comment 1 min read Ringer Movies: ‘After Hours' with Bill Simmons and Sean Fennessey | The Rewatchables Movie News Movie News Movie News Follow Jul 10 '25 Ringer Movies: ‘After Hours' with Bill Simmons and Sean Fennessey | The Rewatchables # analysis # movies # cinema # noir Comments Add Comment 1 min read Ringer Movies: The 25 Best Movies of the Century: No. 16 - ‘Oppenheimer' | The Big Picture Movie News Movie News Movie News Follow Jul 10 '25 Ringer Movies: The 25 Best Movies of the Century: No. 16 - ‘Oppenheimer' | The Big Picture # movies # biography # analysis # cinema Comments Add Comment 1 min read Mr Sunday Movies: Jurassic YAWN? - Jurassic World Rebirth Review Movie News Movie News Movie News Follow Jul 10 '25 Mr Sunday Movies: Jurassic YAWN? - Jurassic World Rebirth Review # reviews # movies # scifi # cinema Comments Add Comment 1 min read CinemaSins: Is that REALLY the old-fashioned way? #roadhouse #cinemasins Movie News Movie News Movie News Follow Jul 9 '25 CinemaSins: Is that REALLY the old-fashioned way? #roadhouse #cinemasins # cinema # movies # crowdfunding # polls Comments Add Comment 1 min read CinemaSins: Disgusting! #austinpowers #cinemasins Movie News Movie News Movie News Follow Jul 9 '25 CinemaSins: Disgusting! #austinpowers #cinemasins # cinema # analysis # polls # crowdfunding Comments Add Comment 1 min read CinemaSins: Gross worm food...#alienresurrection #cinemasins Movie News Movie News Movie News Follow Jul 9 '25 CinemaSins: Gross worm food...#alienresurrection #cinemasins # introduction # cinema # movies # crowdfunding Comments Add Comment 1 min read CinemaSins: Everything about this movie is average...#teenwolf #cinemasins Movie News Movie News Movie News Follow Jul 8 '25 CinemaSins: Everything about this movie is average...#teenwolf #cinemasins # marketing # crowdfunding # polls # cinema Comments Add Comment 1 min read Shane Gillis Comedy ‘Tires' Renewed for Season 3 at Netflix TV News TV News TV News Follow Jul 2 '25 Shane Gillis Comedy ‘Tires' Renewed for Season 3 at Netflix # offtopic # filmindustry # hollywood # cinema 3 reactions Comments 1 comment 1 min read CinemaSins: I've got egg on my face now! #tropicthunder #cinemasins Movie News Movie News Movie News Follow Jul 7 '25 CinemaSins: I've got egg on my face now! #tropicthunder #cinemasins # movies # cinema # introduction # crowdfunding Comments Add Comment 1 min read CinemaSins: Is that REALLY the old-fashioned way? #roadhouse #cinemasins Movie News Movie News Movie News Follow Jul 7 '25 CinemaSins: Is that REALLY the old-fashioned way? #roadhouse #cinemasins # marketing # crowdfunding # movies # cinema Comments Add Comment 1 min read ‘Cobra Kai' Star Alicia Hannah-Kim Speaks Out on Martin Kove Biting Her: ‘Nobody Wants to Be Attacked at Work' TV News TV News TV News Follow Jul 1 '25 ‘Cobra Kai' Star Alicia Hannah-Kim Speaks Out on Martin Kove Biting Her: ‘Nobody Wants to Be Attacked at Work' # marketing # filmindustry # cinema # hollywood 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:48:03 |
https://addons.mozilla.org/pl/firefox/tag/anti%20tracker/ | Dodatki oznaczone etykietą „anti tracker” — dodatki do Firefoksa (pl) Aby używać tych dodatków, potrzebujesz pobrać Firefoksa . Zamknij to powiadomienie Dodatki do przeglądarki Firefox Rozszerzenia Motywy Więcej… do Firefoksa Słowniki i pakiety językowe Inne strony Dodatki na Androida Zaloguj się Wyszukaj Wyszukaj 458 wyników z etykietą „anti tracker” Filtruj wyniki Uporządkuj według Trafność Ostatnio zaktualizowane Najczęściej używane Najwyżej oceniane Zdobywające popularność Typ dodatku Wszystkie Rozszerzenie Motyw Odznaki Wszystkie Polecane Od Firefoksa Wszystkie sprawdzone Wyniki wyszukiwania uBlock Origin Polecane Polecane Nareszcie skuteczne blokowanie reklam, niskie użycie procesora i pamięci. Ocena: 4,8/5 Raymond Hill 10 101 185 użytkowników Privacy Badger Polecane Polecane Automatically learns to block hidden trackers. Made by the leading digital rights nonprofit EFF to stop companies from spying on you. Ocena: 4,8/5 EFF Technologists 1 822 464 użytkowników AdGuard AdBlocker Polecane Polecane Adguard AdBlocker skutecznie blokuje wszystkie typy reklam na stronach internetowych, nawet na Facebooku czy YouTube. Ocena: 4,6/5 Adguard Software Ltd 1 579 826 użytkowników DuckDuckGo Search & Tracker Protection Polecane Polecane Aktywnie chroni Twoje dane w obecnej przeglądarce Ocena: 4,3/5 DuckDuckGo 1 175 765 użytkowników Ghostery – Bloker reklam chroniący prywatność Polecane Polecane Ghostery to potężne rozszerzenie do ochrony prywatności.Blokuje reklamy, wstrzymuje tropiciele i przyspiesza działanie stron internetowych. Ocena: 4,3/5 Ghostery 999 780 użytkowników NoScript Security Suite Polecane Polecane Najlepsze zabezpieczenia dla przeglądarek Mozilli! NoScript pozwala blokować wykonywanie skryptów JavaScript i apletów Java na stronach internetowych. Ocena: 4,4/5 Giorgio Maone 256 089 użytkowników Decentraleyes Polecane Polecane Chroni przed śledzeniem przez ośrodki CDN. Zapobiega wysyłaniu zapytań do sieci takich jak Google Hosted Libraries i dostarcza zasoby z lokalnych plików żeby nie psuć stron. Jest uzupełnieniem do klasycznych dodatków blokujących. Ocena: 4,8/5 Thomas Rientjes 251 648 użytkowników Consent-O-Matic Polecane Polecane Automatic handling of GDPR consent forms Ocena: 4,3/5 CAVI - Aarhus University 104 972 użytkowników Popup Blocker (strict) Polecane Polecane Strictly block all popup requests from any website by default. A notification window is opened to allow you accept, reject, open the popup in background page, or redirect the current page to popup address Ocena: 4,1/5 Jeremy Schomery 78 551 użytkowników AdBlocker Ultimate Completely remove ALL ads. No “acceptable” ads or whitelisted advertisers allowed. This free extensions also helps block trackers and malware. Ocena: 4,8/5 AdAvoid 1 219 745 użytkowników Facebook Container Od Firefoksa Od Firefoksa Zablokuj Facebookowi możliwość śledzenia Twojej aktywności w sieci. Dodatek Facebook Container do przeglądarki Firefox umożliwia kontrolowanie i izolowanie aktywności w Internecie od serwisu Facebook. Ocena: 4,5/5 Firefox 851 231 użytkowników Malwarebytes Browser Guard Najszybsze i najbezpieczniejsze przeglądanie stron internetowych. Zabezpiecz swoją prywatność, blokując narzędzia śledzenia, reklamy i złośliwe treści. Ocena: 4,2/5 Malwarebytes 440 923 użytkowników Firefox Multi-Account Containers Od Firefoksa Od Firefoksa Firefox Multi-Account Containers lets you keep parts of your online life separated into color-coded tabs. Cookies are separated by container, allowing you to use the web with multiple accounts and integrate Mozilla VPN for an extra layer of privacy. Ocena: 4,6/5 Firefox 376 031 użytkowników Firefox Relay Od Firefoksa Od Firefoksa Firefox Relay lets you generate email aliases that forward to your real inbox. Use it to hide your real email address and protect yourself from hackers and unwanted mail. Ocena: 4,2/5 Firefox 238 802 użytkowników Rozszerzenie Surfshark VPN Przeglądaj sieć swobodnie, bezpiecznie i prywatnie, korzystając z rozszerzenia dla przeglądarki Firefox. Ocena: 3,6/5 Surfshark 105 952 użytkowników I still don't care about cookies Community version of the popular extension "I don't care about cookies" https://github.com/OhMyGuus/I-Dont-Care-About-Cookies Ocena: 4,7/5 Guus 104 026 użytkowników Free VPN Proxy & Ad Blocker - Planet VPN Secure your web browsing with Planet VPN - a free vpn proxy addon Ocena: 4,4/5 Free VPN Planet 84 566 użytkowników AdNauseam Blocking ads and fighting back against advertising surveillance. Ocena: 4,6/5 Daniel Howe 72 599 użytkowników Darmowy VPN - 1VPN Darmowy VPN, nieograniczone dane, szybkie prędkości, bezpieczne szyfrowanie, brak logów i łatwy w użyciu. Ocena: 4,3/5 1VPN 55 907 użytkowników Popup Blocker Ultimate Best Pop-up Blocker for Firefox. (Best in Rating, Performance, This addon does NOT collect user's data same as Poper Blocker)If your Firefox version is not 57+ please install version 8.1 from Official website. Ocena: 4,7/5 Mojtaba Daneshi 54 869 użytkowników Norton AntiTrack Czujesz, że właściwie nie masz kontroli nad tym, jakie informacje gromadzą i udostępniają odwiedzane przez Ciebie witryny? Program Norton AntiTrack może pomóc. Ocena: 4,1/5 NortonLifeLock Inc. 46 331 użytkowników Avast AntiTrack Zablokuj śledzenie i gromadzenie informacji przez elementy monitorujące i znakujące. Ocena: 3,8/5 Gen Digital Inc. 40 548 użytkowników Startpage Privacy Protection By installing the free Startpage Privacy Protection extension you will be able to stop trackers and cookies and set Startpage as your default search engine. Ocena: 4,5/5 Startpage 35 381 użytkowników FastForward Nie marnuj czasu na przestrzeganie przepisów, Uniwersalny Bypass automatycznie pomija irytujące skróty linkowe. Ocena: 4,7/5 FastForward Team 34 030 użytkowników UnTrap for YouTube Podsumuj filmy z YouTube za pomocą AI i ukryj rozpraszacze: shorty, reklamy, komentarze i inne. Ocena: 4,3/5 Yevhen Tretiakov 19 798 użytkowników Wstecz 1 2 3 4 5 6 7 Dalej 1. strona z 19 Strona domowa Mozilli Dodatki O serwisie Blog dodatków do Firefoksa Warsztat rozszerzeń Strefa autora Zasady programistów Blog społeczności Forum Zgłoś błąd Wytyczne recenzji Przeglądarki Desktop Mobile Enterprise Produkty Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Prywatność Ciasteczka Kwestie prawne O ile nie wskazano inaczej , treść tej strony jest dostępna na warunkach licencji Creative Commons Attribution Share-Alike w wersji 3.0 lub nowszej. Zmień język Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T08:48:03 |
https://music.forem.com/subforems | Subforems - Music 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 Music Forem Close Subforems DEV Community A space to discuss and keep up software development and manage your software career Follow Future News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Follow Open Forem A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Follow Gamers Forem An inclusive community for gaming enthusiasts Follow Music Forem From composing and gigging to gear, hot music takes, and everything in between. Follow Vibe Coding Forem Discussing AI software development, and showing off what we're building. Follow Popcorn Movies and TV Movie and TV enthusiasm, criticism and everything in-between. Follow DUMB DEV Community Memes and software development shitposting Follow Design Community Web design, graphic design and everything in-between Follow Security Forem Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Follow Golf Forem A community of golfers and golfing enthusiasts Follow Crypto Forem A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Follow Parenting 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. Follow Forem Core Discussing the core forem open source software project — features, bugs, performance, self-hosting. Follow Maker Forem A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. Follow 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 Follow 💎 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 Music Forem — From composing and gigging to gear, hot music takes, 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 . Music Forem © 2025 - 2026. We're a place dedicated to discussing all things music - composing, producing, performing, and all the fun and not-fun things in-between. Log in Create account | 2026-01-13T08:48:03 |
https://stately.ai/ | Pricing Blog Docs Log in Sign up Turn ideas into diagrams and code in minutes. From frontend user flows to backend workflows, visually build and deploy any type of logic with Stately as your source of truth. Try the visual editor Book a demo Design how it works with a visual language for everyone on the team. Our drag and drop editor brings together contributors of all backgrounds. Code, diagrams, documentation, test generation, and more in one place. No more silos. Always up to date. AIs love helping at each phase with state machines to guide them, while humans use the visual editor to audit and enhance their work. Create flows with no code required . Rapidly prototype or gather requirements without worrying about technical details. Then simulate your design to test and iterate. You can even instantly try out a prototype as an auto-generated React app. Get feedback from your team and clients on how everything is supposed to work. Explore community diagrams to inspire your own solutions. Share your work with the community to get feedback and kudos. Generate flows with AI to scaffold behavior, suggest variants, turn up edge cases, and even write code. Build with executable diagrams and get the best of text-based and visual tools. Run diagrams using XState , a best-in-class open source library for orchestrating and managing state in JavaScript and TypeScript apps. No lock-in. Read XState docs View on Github Use XState on the frontend, backend, or wherever JavaScript runs . Integrations are available for React, Vue, Svelte, and other frameworks. XState uses event-driven programming, state machines, statecharts, and the actor model to handle even the most complex logic in predictable, robust, and visual ways . Learn more about statecharts Bidirectional updates between code and visualization let you use what makes you most productive. Automatically visualize Redux, Zustand, and other code to get the benefits of Stately in your codebase even without XState. An IDE extension brings the power of Stately into VS Code. Download the VS Code extension Generate React apps from diagrams to jumpstart product development. Keep iterating visually with the help of AI, or dive straight into the code to rapidly extend the scaffolding with your vision. Generate tests automatically to keep coverage robust and up-to-date. Export all of your generated code in Javascript or Typescript. Connect with Github to sync Stately with your codebase. Inspect running apps with Stately Inspector to help test, and debug your logic. Visualize communication between actors in your running app with sequence diagrams. Products evolve. People are busy. Understand and stay aligned with Stately as the source of truth. Future proof your code with clear visualizations that are easy to return to and change later. Even years later. Living documentation keeps the whole team in sync without extra overhead. Save versions as backup and to see the history of your work. Export as markdown stories, Mermaid drawings, or JSON documents that can be copied into issues and project documents. Generate diagram summaries to get oriented quickly. Loved by teams Amy Pellegrini @ Thoughtworks Every team where I introduced XState has been more effective at handling state management with complex user interfaces. It fills a gap in the JS ecosystem no other tool did before. Natalie Cuthbert @ Stitch We've been using XState for our new payments product. Shout out to the team that is making designing complex front-end flows a dream. Patrick Cavit @ Netflix XState is a revelation. It makes complex tasks easier to build and debug while also making the code more straightforward and approachable. Presley Pizzo @ Coder XState naturally separates the logic and makes it simple to mock out API calls, so it's easier to test the code and organize it! James Tharpe @ T-Mobile We use XState to implement business workflows as statecharts. The visualizer helps us collaborate more closely with customers, the ability to externalize workflows as JSON configuration makes complex workflow changes surprisingly simple to roll out, and test case generation makes it easier than ever to move forward with confidence. XState makes it all possible! Maya Shavin @ Microsoft Advantages of XState: Visually clear view of the code flow, code reusability, test coverage, easy to debug/ spot bugs, code scalability & maintenance, and better code design & planning. Santi Cros @ Domestic Data Streamers Thinking and building with XState has been a revolution in how I develop robust business logic. But being able to visualize that in real time, has been a game changer in how I model and communicate any logic! Intelligent logic to transition from design to deployment, and back again. Sign up for free Book a demo Get updates by email Subscribe to our newsletter Be part of a friendly and helpful community Join our Discord to give us feedback and get support. And participate in our Office Hours for previews and announcements with the Stately team. © 2026 Stately Product Documentation XState Pricing Company Blog Contact Resources Privacy policy Code of conduct Community Discord Twitter YouTube LinkedIn | 2026-01-13T08:48:03 |
https://forem.com/enter?signup_subforem=42 | Welcome! - 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 Join the Forem Forem is a community of 3,676,891 amazing members Continue with Apple Continue with Facebook Continue with GitHub Continue with Google 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 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 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:48:03 |
https://ruul.io/blog/freelance-videographer-tips-to-stand-out | Blog | For Freelancers, Creators, and Indie Professionals Product Payment Requests Get paid anywhere. Sell Services Make your services buyable Sell Products Create once sell forever Subscriptions Get paid on repeat Ruul Space Your personel storefront. One link for everything you offer. Learn more Pricing Resources Partner Programs Referral Program Get 1% for life. Seriously. Affiliate Program Bring users, get paid Partners Let’s grow together. More Blog About us Support Brand Kit For Customers Log in Sign up For Businesses Login Sign up grow 13 Best Fiverr Alternatives Freelancers Need to Know Read POPULAR ARTICLES How to Accept Online Payments: A Comprehensive Guide for Businesses and Freelancers Learn how to set up and manage secure online payment systems for your business or freelance work. Discover popular payment methods, integration tips, security measures, and best practices to streamline transactions and boost efficiency. Top 15 Digital Nomad Jobs in 2025 Explore the 15 best digital nomad jobs in 2025, from writing to coding—fully remote, high-paying, and travel-friendly. The Ultimate Best AI Tools for Freelancers: Boosting Productivity in 2025 Discover the ultimate AI tools for freelancers in 2025 to enhance productivity and efficiency. From writing and graphic design to project management, explore top AI tools like ChatGPT, Grammarly, Canva, and more. Start optimizing your freelancing. How to Accept Cryptocurrency Payments Find the methods, benefits, and security considerations for accepting crypto payments. Know how cryptocurrencies can open new opportunities for your business. What to Sell as a Digital Product Want to make money while you sleep? From AI art to ebooks and plugins, here’s what actually sells in 2025 and makes your wallet happy! Best 13 Motivational Apps and Techniques You Need As You Work Solo Lack of motivation as an independent? See these motivation apps and techniques. get paid sell grow work news trends get paid sell grow work news trends How to Make Freelance Money I’ve mapped out the freelance income paths that will stick around until 2030. Shared all the pro tips and details in this post. Come check it out! Introducing MiniPay on Ruul: Faster Stablecoin Payment Ruul & MiniPay now bring instant, stablecoin payments with zero withdrawal fee for freelancers. Create virtual USD/EUR accounts, enjoy fast global transfers, and earn up to $275 in bonuses. Best Freelancing Websites Struggling to pick a freelancing website? These 16 categorized freelancing platforms will save your time, energy, and maybe your sanity! How to Get Paid as a Freelancer Don't let payments ruin your business! We've covered everything from the most important steps to the best methods! Designer's Guide to Dribbble All the potential Dribbble has to offer, and all the areas where it leaves you hanging. This Guide gives you all of that and more. Best Freelance Jobs You're looking for the best freelance jobs AI won't wipe out. Safe, in-demand, future-ready, long-lasting work… you'll find it all right here. MORE THAN 120,000 Independents Over 120,000 independents trust Ruul to sell their services, digital products, and securely manage their payments. FROM 190 Countries Truly global coverage: trusted across 190 countries with seamless payouts available in 140 currencies. PROCESSED $200m+ of Transactions Over $200M successfully processed, backed by an 8-year legacy of secure, reliable transactions trusted by independents worldwide. FREQUENTLY ASKED QUESTIONS Everything you need to know. Get clear, straightforward answers to the most common questions about using Ruul. hey@ruul.io What is Ruul? Ruul is a merchant-of-record platform helping freelancers and creators globally sell services, digital products, subscriptions, and easily get paid. Who is Ruul for? Ruul is designed for freelancers, creators, and independent professionals who want a simple way to sell online and get paid globally. How does Ruul work? Open an account, complete a quick verification (KYC), and link your payout account. Then, start selling through your store or send payment requests to customers instantly. How does pricing work? Signing up is free. There are no subscription or hidden fees. Ruul charges a small commission only when you sell or get paid through the platform. What is a Merchant of Record? A merchant of record is the legal seller responsible for processing payments, handling taxes, and managing compliance for each transaction. What can I sell on Ruul? You can sell services, digital products, license keys, online courses, subscriptions, and digital memberships. How do I get paid on Ruul? Add your preferred bank account, digital wallet, or receive payouts in stablecoins as crypto. Funds arrive within 24 hours after a payout is triggered. OPEN AN ACCOUNT START MAKING MONEY TODAY ruul.space/ Thank you! Your submission has been received! Oops! Something went wrong while submitting the form. Trustpilot Product Payment Requests Sell Services Sell Products Subscriptions Ruul Space Pricing For Businesses Resources Blog About Contact Support Referral Program Affiliate Program Partner Program Tools Invoice Generator NDA Generator Service Agreement Generator Freelancer Hourly Rate Calculator All Rights Reserved © 2025 Terms Of Use Privacy Policy | 2026-01-13T08:48:03 |
https://forem.com/enter?signup_subforem=48&state=new-user | Welcome! - 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 Join the Forem Forem is a community of 3,676,891 amazing members Continue with Apple Continue with Facebook Continue with GitHub Continue with Google 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 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 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:48:03 |
https://forem.com/enter?signup_subforem=48 | Welcome! - 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 Join the Forem Forem is a community of 3,676,891 amazing members Continue with Apple Continue with Facebook Continue with GitHub Continue with Google 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 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 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:48:03 |
https://docs.github.com/en/github/site-policy/github-terms-of-service | GitHub Terms of Service - GitHub Docs Skip to main content GitHub Docs Version: Free, Pro, & Team Search or ask Copilot Search or ask Copilot Select language: current language is English Search or ask Copilot Search or ask Copilot Open menu Open Sidebar Site policy / GitHub Terms / GitHub Terms of Service Home Site policy GitHub Terms GitHub Terms of Service GitHub Corporate Terms of Service GitHub Terms for Additional Products and Features GitHub Community Guidelines GitHub Community Code of Conduct GitHub Pre-release License Terms GitHub DPA-Covered Previews GitHub Sponsors Additional Terms GitHub Registered Developer Agreement GitHub Marketplace Terms of Service GitHub Marketplace Developer Agreement GitHub Research Program Terms GitHub Open Source Applications Terms and Conditions GitHub Event Terms GitHub Event Code of Conduct GitHub Educational Use Agreement GitHub Copilot Extension Developer Policy Acceptable Use Policies GitHub Acceptable Use Policies Active Malware or Exploits Bullying and Harassment Disrupting the Experience of Other Users Doxxing and Invasion of Privacy Hate Speech and Discrimination Impersonation Disinformation Policy Sexually Obscene Content Threats of Violence and Gratuitously Violent Content Terrorism and Violent Extremism Content CSAM Policy NCII Synthetic Media and AI Tools GitHub Appeal and Reinstatement Privacy Policies GitHub General Privacy Statement GitHub Subprocessors GitHub Cookies GitHub Global Data Privacy Notice for Candidates Other Site Policies GitHub and Trade Controls GitHub Deceased User Policy GitHub Logo Policy GitHub Government Takedown Policy GitHub Username Policy Guidelines for Legal Requests of User Data GitHub Account Recovery Policy Content Removal Policies Submitting content removal requests DMCA Takedown Policy GitHub Private Information Removal Policy GitHub Trademark Policy Guide to Submitting a DMCA Counter Notice Guide to Submitting a DMCA Takedown Notice Security Policies Coordinated Disclosure of Security Vulnerabilities GitHub Bug Bounty Program Legal Safe Harbor GitHub SIRT description RFC 2350 GitHub Company Policies GitHub Statement Against Modern Slavery and Child Labor GitHub Anti-Bribery Statement GitHub GPL Cooperation Commitment GitHub Gifts and Entertainment Policy Site policy / GitHub Terms / GitHub Terms of Service GitHub Terms of Service View page as Markdown In this article Summary The GitHub Terms of Service A. Definitions B. Account Terms C. Acceptable Use D. User-Generated Content E. Private Repositories F. Copyright Infringement and DMCA Policy G. Intellectual Property Notice H. API Terms I. GitHub Additional Product Terms J. Beta Previews K. Payment L. Cancellation and Termination M. Communications with GitHub N. Disclaimer of Warranties O. Limitation of Liability P. Release and Indemnification Q. Changes to These Terms R. Miscellaneous Thank you for using GitHub! We're happy you're here. Please read this Terms of Service agreement carefully before accessing or using GitHub. Because it is such an important contract between us and our users, we have tried to make it as clear as possible. For your convenience, we have presented these terms in a short non-binding summary followed by the full legal terms. Summary Section What can you find there? A. Definitions Some basic terms, defined in a way that will help you understand this agreement. Refer back up to this section for clarification. B. Account Terms These are the basic requirements of having an Account on GitHub. C. Acceptable Use These are the basic rules you must follow when using your GitHub Account. D. User-Generated Content You own the content you post on GitHub. However, you have some responsibilities regarding it, and we ask you to grant us some rights so we can provide services to you. E. Private Repositories This section talks about how GitHub will treat content you post in private repositories. F. Copyright & DMCA Policy This section talks about how GitHub will respond if you believe someone is infringing your copyrights on GitHub. G. Intellectual Property Notice This describes GitHub's rights in the website and service. H. API Terms These are the rules for using GitHub's APIs, whether you are using the API for development or data collection. I. Additional Product Terms We have a few specific rules for GitHub's features and products. J. Beta Previews These are some of the additional terms that apply to GitHub's features that are still in development. K. Payment You are responsible for payment. We are responsible for billing you accurately. L. Cancellation and Termination You may cancel this agreement and close your Account at any time. M. Communications with GitHub We only use email and other electronic means to stay in touch with our users. We do not provide phone support. N. Disclaimer of Warranties We provide our service as is, and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect. O. Limitation of Liability We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you. P. Release and Indemnification You are fully responsible for your use of the service. Q. Changes to these Terms of Service We may modify this agreement, but we will give you 30 days' notice of material changes. R. Miscellaneous Please see this section for legal details including our choice of law. The GitHub Terms of Service Effective date: November 16, 2020 A. Definitions Short version: We use these basic terms throughout the agreement, and they have specific meanings. You should know what we mean when we use each of the terms. There's not going to be a test on it, but it's still useful information. An "Account" represents your legal relationship with GitHub. A “Personal Account” represents an individual User’s authorization to log in to and use the Service and serves as a User’s identity on GitHub. “Organizations” are shared workspaces that may be associated with a single entity or with one or more Users where multiple Users can collaborate across many projects at once. A Personal Account can be a member of any number of Organizations. The “Agreement” refers, collectively, to all the terms, conditions, notices contained or referenced in this document (the “Terms of Service” or the "Terms") and all other operating rules, policies (including the GitHub Privacy Statement, available at github.com/site/privacy ) and procedures that we may publish from time to time on the Website. Most of our site policies are available at docs.github.com/categories/site-policy . "Beta Previews" mean software, services, or features identified as alpha, beta, preview, early access, or evaluation, or words or phrases with similar meanings. “Content” refers to content featured or displayed through the Website, including without limitation code, text, data, articles, images, photographs, graphics, software, applications, packages, designs, features, and other materials that are available on the Website or otherwise available through the Service. "Content" also includes Services. “User-Generated Content” is Content, written or otherwise, created or uploaded by our Users. "Your Content" is Content that you create or own. “GitHub,” “We,” and “Us” refer to GitHub, Inc., as well as our affiliates, directors, subsidiaries, contractors, licensors, officers, agents, and employees. The “Service” refers to the applications, software, products, and services provided by GitHub, including any Beta Previews. “The User,” “You,” and “Your” refer to the individual person, company, or organization that has visited or is using the Website or Service; that accesses or uses any part of the Account; or that directs the use of the Account in the performance of its functions. A User must be at least 13 years of age. Special terms may apply for business or government Accounts (See Section B(5): Additional Terms ). The “Website” refers to GitHub’s website located at github.com , and all content, services, and products provided by GitHub at or through the Website. It also refers to GitHub-owned subdomains of github.com, such as education.github.com and pages.github.com . These Terms also govern GitHub’s conference websites, such as githubuniverse.com , and product websites, such as electronjs.org . Occasionally, websites owned by GitHub may provide different or additional terms of service. If those additional terms conflict with this Agreement, the more specific terms apply to the relevant page or service. B. Account Terms Short version: Personal Accounts and Organizations have different administrative controls; a human must create your Account; you must be 13 or over; you must provide a valid email address; and you may not have more than one free Account. You alone are responsible for your Account and anything that happens while you are signed in to or using your Account. You are responsible for keeping your Account secure. 1. Account Controls Users. Subject to these Terms, you retain ultimate administrative control over your Personal Account and the Content within it. Organizations. The "owner" of an Organization that was created under these Terms has ultimate administrative control over that Organization and the Content within it. Within the Service, an owner can manage User access to the Organization’s data and projects. An Organization may have multiple owners, but there must be at least one Personal Account designated as an owner of an Organization. If you are the owner of an Organization under these Terms, we consider you responsible for the actions that are performed on or through that Organization. 2. Required Information You must provide a valid email address in order to complete the signup process. Any other information requested, such as your real name, is optional, unless you are accepting these terms on behalf of a legal entity (in which case we need more information about the legal entity) or if you opt for a paid Account , in which case additional information will be necessary for billing purposes. 3. Account Requirements We have a few simple rules for Personal Accounts on GitHub's Service. You must be a human to create an Account. Accounts registered by "bots" or other automated methods are not permitted. We do permit machine accounts: A machine account is an Account set up by an individual human who accepts the Terms on behalf of the Account, provides a valid email address, and is responsible for its actions. A machine account is used exclusively for performing automated tasks. Multiple users may direct the actions of a machine account, but the owner of the Account is ultimately responsible for the machine's actions. You may maintain no more than one free machine account in addition to your free Personal Account. One person or legal entity may maintain no more than one free Account (if you choose to control a machine account as well, that's fine, but it can only be used for running a machine). You must be age 13 or older. While we are thrilled to see brilliant young coders get excited by learning to program, we must comply with United States law. GitHub does not target our Service to children under 13, and we do not permit any Users under 13 on our Service. If we learn of any User under the age of 13, we will terminate that User’s Account immediately . If you are a resident of a country outside the United States, your country’s minimum age may be older; in such a case, you are responsible for complying with your country’s laws. Your login may only be used by one person — i.e., a single login may not be shared by multiple people. A paid Organization may only provide access to as many Personal Accounts as your subscription allows. You may not use GitHub in violation of export control or sanctions laws of the United States or any other applicable jurisdiction. You may not use GitHub if you are or are working on behalf of a Specially Designated National (SDN) or a person subject to similar blocking or denied party prohibitions administered by a U.S. government agency. GitHub may allow persons in certain sanctioned countries or territories to access certain GitHub services pursuant to U.S. government authorizations. For more information, please see our Export Controls policy . 4. Account Security You are responsible for keeping your Account secure while you use our Service. We offer tools such as two-factor authentication to help you maintain your Account's security, but the content of your Account and its security are up to you. You are responsible for all content posted and activity that occurs under your Account (even when content is posted by others who have Accounts under your Account). You are responsible for maintaining the security of your Account and password. GitHub cannot and will not be liable for any loss or damage from your failure to comply with this security obligation. You will promptly notify GitHub by contacting us through the GitHub Support portal if you become aware of any unauthorized use of, or access to, our Service through your Account, including any unauthorized use of your password or Account. 5. Additional Terms In some situations, third parties' terms may apply to your use of GitHub. For example, you may be a member of an organization on GitHub with its own terms or license agreements; you may download an application that integrates with GitHub; or you may use GitHub to authenticate to another service. Please be aware that while these Terms are our full agreement with you, other parties' terms govern their relationships with you. If you are a government User or otherwise accessing or using any GitHub Service in a government capacity, this Government Amendment to GitHub Terms of Service applies to you, and you agree to its provisions. If you have signed up for GitHub Enterprise Cloud, the Enterprise Cloud Addendum applies to you, and you agree to its provisions. C. Acceptable Use Short version: GitHub hosts a wide variety of collaborative projects from all over the world, and that collaboration only works when our users are able to work together in good faith. While using the service, you must follow the terms of this section, which include some restrictions on content you can post, conduct on the service, and other limitations. In short, be excellent to each other. Your use of the Website and Service must not violate any applicable laws, including copyright or trademark laws, export control or sanctions laws, or other laws in your jurisdiction. You are responsible for making sure that your use of the Service is in compliance with laws and any applicable regulations. You agree that you will not under any circumstances violate our Acceptable Use Policies or Community Guidelines . D. User-Generated Content Short version: You own content you create, but you allow us certain rights to it, so that we can display and share the content you post. You still have control over your content, and responsibility for it, and the rights you grant us are limited to those we need to provide the service. We have the right to remove content or close Accounts if we need to. 1. Responsibility for User-Generated Content You may create or upload User-Generated Content while using the Service. You are solely responsible for the content of, and for any harm resulting from, any User-Generated Content that you post, upload, link to or otherwise make available via the Service, regardless of the form of that Content. We are not responsible for any public display or misuse of your User-Generated Content. 2. GitHub May Remove Content We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or GitHub terms or policies . User-Generated Content displayed on GitHub Mobile may be subject to mobile app stores' additional terms. 3. Ownership of Content, Right to Post, and License Grants You retain ownership of and responsibility for Your Content. If you're posting anything you did not create yourself or do not own the rights to, you agree that you are responsible for any Content you post; that you will only submit Content that you have the right to post; and that you will fully comply with any third party licenses relating to Content you post. Because you retain ownership of and responsibility for Your Content, we need you to grant us — and other GitHub Users — certain legal permissions, listed in Sections D.4 — D.7. These license grants apply to Your Content. If you upload Content that already comes with a license granting GitHub the permissions we need to run our Service, no additional license is required. You understand that you will not receive any payment for any of the rights granted in Sections D.4 — D.7. The licenses you grant to us will end when you remove Your Content from our servers, unless other Users have forked it. 4. License Grant to Us We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video. This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the GitHub Arctic Code Vault and GitHub Archive Program . 5. License Grant to Other Users Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control). If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). You may grant further rights if you adopt a license . If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users. 6. Contributions Under Repository License Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede. Isn't this just how it works already? Yep. This is widely accepted as the norm in the open-source community; it's commonly referred to by the shorthand "inbound=outbound". We're just making it explicit. 7. Moral Rights You retain all moral rights to Your Content that you upload, publish, or submit to any part of the Service, including the rights of integrity and attribution. However, you waive these rights and agree not to assert them against us, to enable us to reasonably exercise the rights granted in Section D.4, but not otherwise. To the extent this agreement is not enforceable by applicable law, you grant GitHub the rights we need to use Your Content without attribution and to make reasonable adaptations of Your Content as necessary to render the Website and provide the Service. 8. Access Reciprocity By using automated means to access, collect, or otherwise use (“Access”) any publicly accessible Content from the Service for the purpose of developing or training any commercially available artificial intelligence model, machine learning system, or similar technology (a "Commercial AI System"), you hereby waive any and all policies, terms, conditions, or contractual provisions governing products, services, websites or datasets you own or operate that would otherwise prohibit, restrict, or place conditions upon GitHub's Access to any publicly accessible data, information or content associated with your products or services, including for the purpose of developing or training any Commercial AI System. You further agree not to impose technical or other targeted measures to restrict or retaliate against such Access. This Section D.8 does not apply to Access solely for the purpose of academic research or if, on the date you Access the Content, the number of monthly active users of the products or services made available by you is less than 700 million in the preceding calendar month. For the purposes of this Section, "you" shall refer to you and any entity that directly or indirectly controls, is controlled by, or is under common control with you (affiliates). E. Private Repositories Short version: We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent. 1. Control of Private Repositories Some Accounts may have private repositories, which allow the User to control access to Content. 2. Confidentiality of Private Repositories GitHub considers the contents of private repositories to be confidential to you. GitHub will protect the contents of private repositories from unauthorized use, access, or disclosure in the same manner that we would use to protect our own confidential information of a similar nature and in no event with less than a reasonable degree of care. 3. Access GitHub personnel may only access the content of your private repositories in the situations described in our Privacy Statement . You may choose to enable additional access to your private repositories. For example: You may enable various GitHub services or features that require additional rights to Your Content in private repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat your private repository Content as confidential. If those services or features require rights in addition to those we need to provide the GitHub Service, we will provide an explanation of those rights. Additionally, we may be compelled by law to disclose the contents of your private repositories. GitHub will provide notice regarding our access to private repository content, unless for legal disclosure , to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security. F. Copyright Infringement and DMCA Policy If you believe that content on our website violates your copyright, please contact us in accordance with our Digital Millennium Copyright Act Policy . If you are a copyright owner and you believe that content on GitHub violates your rights, please contact us via our convenient DMCA form or by emailing copyright@github.com . There may be legal consequences for sending a false or frivolous takedown notice. Before sending a takedown request, you must consider legal uses such as fair use and licensed uses. We will terminate the Accounts of repeat infringers of this policy. G. Intellectual Property Notice Short version: We own the service and all of our content. In order for you to use our content, we give you certain rights to it, but you may only use our content in the way we have allowed. 1. GitHub's Rights to Content GitHub and our licensors, vendors, agents, and/or our content providers retain ownership of all intellectual property rights of any kind related to the Website and Service. We reserve all rights that are not expressly granted to you under this Agreement or by law. The look and feel of the Website and Service is copyright © GitHub, Inc. All rights reserved. You may not duplicate, copy, or reuse any portion of the HTML/CSS, JavaScript, or visual design elements or concepts without express written permission from GitHub. 2. GitHub Trademarks and Logos If you’d like to use GitHub’s trademarks, you must follow all of our trademark guidelines, including those on our logos page: https://github.com/logos . 3. License to GitHub Policies This Agreement is licensed under this Creative Commons Zero license . For details, see our site-policy repository . H. API Terms Short version: You agree to these Terms of Service, plus this Section H, when using any of GitHub's APIs (Application Provider Interface), including use of the API through a third party product that accesses GitHub. Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your Account's access to the API. GitHub, in our sole discretion, will determine abuse or excessive usage of the API. We will make a reasonable attempt to warn you via email prior to suspension. You may not share API tokens to exceed GitHub's rate limitations. You may not use the API to download data or Content from GitHub for spamming purposes, including for the purposes of selling GitHub users' personal information, such as to recruiters, headhunters, and job boards. All use of the GitHub API is subject to these Terms of Service and the GitHub Privacy Statement . GitHub may offer subscription-based access to our API for those Users who require high-throughput access or access that would result in resale of GitHub's Service. I. GitHub Additional Product Terms Short version: You need to follow certain specific terms and conditions for GitHub's various features and products, and you agree to the Supplemental Terms and Conditions when you agree to this Agreement. Some Service features may be subject to additional terms specific to that feature or product as set forth in the GitHub Additional Product Terms. By accessing or using the Services, you also agree to the GitHub Additional Product Terms . J. Beta Previews Short version: Beta Previews may not be supported or may change at any time. You may receive confidential information through those programs that must remain confidential while the program is private. We'd love your feedback to make our Beta Previews better. 1. Subject to Change Beta Previews may not be supported and may be changed at any time without notice. In addition, Beta Previews are not subject to the same security measures and auditing to which the Service has been and is subject. By using a Beta Preview, you use it at your own risk. 2. Confidentiality As a user of Beta Previews, you may get access to special information that isn’t available to the rest of the world. Due to the sensitive nature of this information, it’s important for us to make sure that you keep that information secret. Confidentiality Obligations. You agree that any non-public Beta Preview information we give you, such as information about a private Beta Preview, will be considered GitHub’s confidential information (collectively, “Confidential Information”), regardless of whether it is marked or identified as such. You agree to only use such Confidential Information for the express purpose of testing and evaluating the Beta Preview (the “Purpose”), and not for any other purpose. You should use the same degree of care as you would with your own confidential information, but no less than reasonable precautions to prevent any unauthorized use, disclosure, publication, or dissemination of our Confidential Information. You promise not to disclose, publish, or disseminate any Confidential Information to any third party, unless we don’t otherwise prohibit or restrict such disclosure (for example, you might be part of a GitHub-organized group discussion about a private Beta Preview feature). Exceptions. Confidential Information will not include information that is: (a) or becomes publicly available without breach of this Agreement through no act or inaction on your part (such as when a private Beta Preview becomes a public Beta Preview); (b) known to you before we disclose it to you; (c) independently developed by you without breach of any confidentiality obligation to us or any third party; or (d) disclosed with permission from GitHub. You will not violate the terms of this Agreement if you are required to disclose Confidential Information pursuant to operation of law, provided GitHub has been given reasonable advance written notice to object, unless prohibited by law. 3. Feedback We’re always trying to improve of products and services, and your feedback as a Beta Preview user will help us do that. If you choose to give us any ideas, know-how, algorithms, code contributions, suggestions, enhancement requests, recommendations or any other feedback for our products or services (collectively, “Feedback”), you acknowledge and agree that GitHub will have a royalty-free, fully paid-up, worldwide, transferable, sub-licensable, irrevocable and perpetual license to implement, use, modify, commercially exploit and/or incorporate the Feedback into our products, services, and documentation. K. Payment Short version: You are responsible for any fees associated with your use of GitHub. We are responsible for communicating those fees to you clearly and accurately, and letting you know well in advance if those prices change. 1. Pricing Our pricing and payment terms are available at github.com/pricing . If you agree to a subscription price, that will remain your price for the duration of the payment term; however, prices are subject to change at the end of a payment term. 2. Upgrades, Downgrades, and Changes We will immediately bill you when you upgrade from the free plan to any paying plan. If you change from a monthly billing plan to a yearly billing plan, GitHub will bill you for a full year at the next monthly billing date. If you upgrade to a higher level of service, we will bill you for the upgraded plan immediately. You may change your level of service at any time by choosing a plan option or going into your Billing settings . If you choose to downgrade your Account, you may lose access to Content, features, or capacity of your Account. Please see our section on Cancellation for information on getting a copy of that Content. 3. Billing Schedule; No Refunds Payment Based on Plan For monthly or yearly payment plans, the Service is billed in advance on a monthly or yearly basis respectively and is non-refundable. There will be no refunds or credits for partial months of service, downgrade refunds, or refunds for months unused with an open Account; however, the service will remain active for the length of the paid billing period. In order to treat everyone equally, no exceptions will be made. Payment Based on Usage Some Service features are billed based on your usage. A limited quantity of these Service features may be included in your plan for a limited term without additional charge. If you choose to use paid Service features beyond the quantity included in your plan, you pay for those Service features based on your actual usage in the preceding month. Monthly payment for these purchases will be charged on a periodic basis in arrears. See GitHub Additional Product Terms for Details . Invoicing For invoiced Users, User agrees to pay the fees in full, up front without deduction or setoff of any kind, in U.S. Dollars. User must pay the fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable, except as otherwise provided in this Agreement. If User fails to pay any fees on time, GitHub reserves the right, in addition to taking any other action at law or equity, to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law, whichever is less, and to charge all expenses of recovery, and (ii) terminate the applicable order form. User is solely responsible for all taxes, fees, duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement. 4. Authorization By agreeing to these Terms, you are giving us permission to charge your on-file credit card, PayPal account, or other approved methods of payment for fees that you authorize for GitHub. 5. Responsibility for Payment You are responsible for all fees, including taxes, associated with your use of the Service. By using the Service, you agree to pay GitHub any charge incurred in connection with your use of the Service. If you dispute the matter, contact us through the GitHub Support portal . You are responsible for providing us with a valid means of payment for paid Accounts. Free Accounts are not required to provide payment information. L. Cancellation and Termination Short version: You may close your Account at any time. If you do, we'll treat your information responsibly. 1. Account Cancellation It is your responsibility to properly cancel your Account with GitHub. You can cancel your Account at any time by going into your Settings in the global navigation bar at the top of the screen. The Account screen provides a simple, no questions asked cancellation link. We are not able to cancel Accounts in response to an email or phone request. 2. Upon Cancellation We will retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, we will delete your full profile and the Content of your repositories within 90 days of cancellation or termination (though some information may remain in encrypted backups). This information cannot be recovered once your Account is canceled. We will not delete Content that you have contributed to other Users' repositories or that other Users have forked. Upon request, we will make a reasonable effort to provide an Account owner with a copy of your lawful, non-infringing Account contents after Account cancellation, termination, or downgrade. You must make this request within 90 days of cancellation, termination, or downgrade. 3. GitHub May Terminate GitHub has the right to suspend or terminate your access to all or any part of the Website at any time, with or without cause, with or without notice, effective immediately. GitHub reserves the right to refuse service to anyone for any reason at any time. 4. Survival All provisions of this Agreement which, by their nature, should survive termination will survive termination — including, without limitation: ownership provisions, warranty disclaimers, indemnity, and limitations of liability. M. Communications with GitHub Short version: We use email and other electronic means to stay in touch with our users. 1. Electronic Communication Required For contractual purposes, you (1) consent to receive communications from us in an electronic form via the email address you have submitted or via the Service; and (2) agree that all Terms of Service, agreements, notices, disclosures, and other communications that we provide to you electronically satisfy any legal requirement that those communications would satisfy if they were on paper. This section does not affect your non-waivable rights. 2. Legal Notice to GitHub Must Be in Writing Communications made through email or GitHub Support's messaging system will not constitute legal notice to GitHub or any of its officers, employees, agents or representatives in any situation where notice to GitHub is required by contract or any law or regulation. Legal notice to GitHub must be in writing and served on GitHub's legal agent . 3. No Phone Support GitHub only offers support via email, in-Service communications, and electronic messages. We do not offer telephone support. N. Disclaimer of Warranties Short version: We provide our service as is, and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect. GitHub provides the Website and the Service “as is” and “as available,” without warranty of any kind. Without limiting this, we expressly disclaim all warranties, whether express, implied or statutory, regarding the Website and the Service including without limitation any warranty of merchantability, fitness for a particular purpose, title, security, accuracy and non-infringement. GitHub does not warrant that the Service will meet your requirements; that the Service will be uninterrupted, timely, secure, or error-free; that the information provided through the Service is accurate, reliable or correct; that any defects or errors will be corrected; that the Service will be available at any particular time or location; or that the Service is free of viruses or other harmful components. You assume full responsibility and risk of loss resulting from your downloading and/or use of files, information, content or other material obtained from the Service. O. Limitation of Liability Short version: We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you. You understand and agree that we will not be liable to you or any third party for any loss of profits, use, goodwill, or data, or for any incidental, indirect, special, consequential or exemplary damages, however arising, that result from the use, disclosure, or display of your User-Generated Content; your use or inability to use the Service; any modification, price change, suspension or discontinuance of the Service; the Service generally or the software or systems that make the Service available; unauthorized access to or alterations of your transmissions or data; statements or conduct of any third party on the Service; any other user interactions that you input or receive through your use of the Service; or any other matter relating to the Service. Our liability is limited whether or not we have been informed of the possibility of such damages, and even if a remedy set forth in this Agreement is found to have failed of its essential purpose. We will have no liability for any failure or delay due to matters beyond our reasonable control. P. Release and Indemnification Short version: You are responsible for your use of the service. If you harm someone else or get into a dispute with someone else, we will not be involved. If you have a dispute with one or more Users, you agree to release GitHub from any and all claims, demands and damages (actual and consequential) of every kind and nature, known and unknown, arising out of or in any way connected with such disputes. You agree to indemnify us, defend us, and hold us harmless from and against any and all claims, liabilities, and expenses, including attorneys’ fees, arising out of your use of the Website and the Service, including but not limited to your violation of this Agreement, provided that GitHub (1) promptly gives you written notice of the claim, demand, suit or proceeding; (2) gives you sole control of the defense and settlement of the claim, demand, suit or proceeding (provided that you may not settle any claim, demand, suit or proceeding unless the settlement unconditionally releases GitHub of all liability); and (3) provides to you all reasonable assistance, at your expense. Q. Changes to These Terms Short version: We want our users to be informed of important changes to our terms, but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time, we will notify users of any material changes and give you time to adjust to them. We reserve the right, at our sole discretion, to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our Site Policy repository. We reserve the right at any time and from time to time to modify or discontinue, temporarily or permanently, the Website (or any part of it) with or without notice. R. Miscellaneous 1. Governing Law Except to the extent applicable law provides otherwise, this Agreement between you and GitHub and any access to or use of the Website or the Service are governed by the federal laws of the United States of America and the laws of the State of California, without regard to conflict of law provisions. You and GitHub agree to submit to the exclusive jurisdiction and venue of the courts located in the City and County of San Francisco, California. However, any claim for injunctive relief with respect to a violation of section D.8 may be brought in any jurisdiction. 2. Non-Assignability GitHub may assign or delegate these Terms of Service and/or the GitHub Privacy Statement , in whole or in part, to any person or entity at any time with or without your consent, including the license grant in Section D.4. You may not assign or delegate any rights or obligations under the Terms of Service or Privacy Statement without our prior written consent, and any unauthorized assignment and delegation by you is void. 3. Section Headings and Summaries Throughout this Agreement, each section includes titles and brief summaries of the following terms and conditions. These section titles and brief summaries are not legally binding. 4. Severability, No Waiver, and Survival If any part of this Agreement is held invalid or unenforceable, that portion of the Agreement will be construed to reflect the parties’ original intent. The remaining portions will remain in full force and effect. Any failure on the part of GitHub to enforce any provision of this Agreement will not be considered a waiver of our right to enforce such provision. Our rights under this Agreement will survive any termination of this Agreement. 5. Amendments; Complete Agreement This Agreement may only be modified by a written amendment signed by an authorized representative of GitHub, or by the posting by GitHub of a revised version in accordance with Section Q. Changes to These Terms . These Terms of Service, together with the GitHub Privacy Statement, represent the complete and exclusive statement of the agreement between you and us. This Agreement supersedes any proposal or prior agreement oral or written, and any other communications between you and GitHub relating to the subject matter of these terms including any confidentiality or nondisclosure agreements. 6. Questions Questions about the Terms of Service? Contact us through the GitHub Support portal . Help and support Help us make these docs great! All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request. Make a contribution Learn how to contribute Still need help? Ask the GitHub community Contact support Legal © 2026 GitHub, Inc. Terms Privacy Status Pricing Expert services Blog | 2026-01-13T08:48:03 |
https://neon.tech/ | Neon Serverless Postgres — Ship faster This 250+ engineer team replaced shared staging with isolated database branches for safer deploys Neon Product Database Autoscaling Automatic instance sizing Branching Faster Postgres workflows Bottomless storage With copy-on-write Instant restores Recover TBs in seconds Connection pooler Built-in with pgBouncer Ecosystem Neon API Manage infra, billing, quotas Auth Add authentication Data API PostgREST-compatible Instagres No-signup flow Migration guides Step-by-step What is Neon? Serverless Postgres, by Databricks Solutions Use cases Serverless Apps Autoscale with traffic Multi-TB Scale & restore instantly Database per Tenant Data isolation without overhead Platforms Offer Postgres to your users Dev/Test Production-like environments Agents Build full-stack AI agents For teams Startups Build with Neon Security Compliance & privacy Case studies Explore customer stories Docs Pricing Company Blog About us Careers Contact Discord 20.7k Log In Sign Up Ship faster with Postgres The database developers trust, on a serverless platform designed to help you build reliable and scalable applications faster. Start for Free Talk to Us Scaling Scaling Focus on building applications with time and money-saving features like instant provisioning, autoscaling according to load, and scale to zero. Discover Autoscaling Branching Branching Instantly branch your data and schema to access isolated DB copies for development, CI/CD, and schema migrations with copy-on-write storage. Explore Branching Trusted in production by thousands of teams. Instant Provisioning No waiting. No config. Provisioned in 300ms postgresql://example@ep-938132.eu-central-1.aws.neon.tech/primary Works with your stack Integrate it into your language or framework within minutes and unlock a simpler developer workflow. See all examples Next.js Drizzle Prisma Python Ruby Rust Go import { neon } from '@neondatabase/serverless' ; export async function GET () { const sql = neon ( process . env . DATABASE_URL ); const rows = await sql `SELECT * FROM posts` ; return Response .json ({ rows }) } Lightning fast. Edge ready. The Neon serverless driver , designed for fast queries over HTTP import { neon } from '@neondatabase/ serverless'; const sql = neon('postgresql:// usr:pass@proj.us-east-2.aws.neon.tech/db'); const posts = await sql('SELECT * FROM posts'); Get the Serverless Driver Better database. For modern workflows. Boost your performance with instant read replicas . They scale down to zero when idle and don't use additional storage. Easy database ops via the API and CLI . Manage thousands of databases programmatically. Instant Point-in-time recovery . Up to 30 days granularity down to the transaction or second. Unleashing Cutting- Edge AI Applications. The HNSW index algorithm streamlines performance, making high-dimensional vector search remarkably efficient. Power your AI apps with Postgres Reliable Scalability High compatibility Blazingly fast search Works with PGVECTOR Works with langchain ; Thousands of databases. Zero overhead. Use the Neon API to deploy database-per-tenant architectures . Scale to fleets of thousands of databases without touching a server. Rest easy knowing scale to zero keeps costs low. Industry leaders trust Neon Dive into success stories Neon allows us to develop much faster than we’ve even been used to Alex Klarfeld – CEO and co-founder of Supergood.ai Neon's serverless philosophy is aligned with our vision: no infrastructure to manage, no servers to provision, no database cluster to maintain Edouard Bonlieu – Co-founder at Koyeb The killer feature that convinced us to use Neon was branching: it keeps our engineering velocity high Léonard Henriquez – Co-founder and CTO, Topo.io We've been able to automate virtually all database tasks via the Neon API, saving us a tremendous amount of time and engineering effort Himanshu Bhandoh – Software Engineer at Retool Trusted Postgres neondatabase/neon Databases under management. Postgres for the World. 100% Postgres. Not a fork, not a rewrite. SOC2 Compliance Features of tomorrow. Available today. Get Started Neon A Databricks Company Neon status loading... Made in SF and the World Copyright Ⓒ 2022 – 2026 Neon, LLC Company About Blog Careers Contact Sales Partners Security Legal Privacy Policy Terms of Service DPA Subprocessors List Privacy Guide Cookie Policy Business Information Resources Docs Changelog Support Community Guides PostgreSQL Tutorial Startups Creators Social Discord GitHub x.com LinkedIn YouTube Compliance CCPA Compliant GDPR Compliant ISO 27001 Certified ISO 27701 Certified SOC 2 Certified HIPAA Compliant Compliance Guide Neon’s Sub Contractors Sensitive Data Terms Trust Center | 2026-01-13T08:48:03 |
https://dev.to/art_light/prompt-engineering-wont-fix-your-architecture-23h | Prompt Engineering Won’t Fix Your Architecture - 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 Art light Posted on Jan 9 • Edited on Jan 10 Prompt Engineering Won’t Fix Your Architecture # discuss # career # ai # programming Every few years, our industry rediscovers an old truth and pretends it’s new. Clean code. Microservices. DevOps. Now: prompt engineering. Suddenly, people who shipped a single CRUD app in 2019 are tweeting things like: “The problem isn’t your system. It’s your prompts.” Enter fullscreen mode Exit fullscreen mode No. The problem is still your system. Prompt engineering is not a silver bullet. It’s a very expensive bandaid applied to architectural wounds that were already infected. The Fantasy The fantasy goes like this: You have a messy backend Inconsistent APIs No real domain boundaries Business logic scattered across controllers, cron jobs, and Slack messages But then… ✨ You add AI ✨ ✨ You refine the prompt ✨ ✨ You add “You are a senior engineer” at the top ✨ And magically, intelligence flows through your system like electricity. Except that’s not how software works. That’s not how anything works. Reality Check: AI Enters Your System An LLM doesn’t see your product. It sees: Whatever JSON you remembered to pass Whatever context fit into a token window Whatever half-written schema someone added at 2am So when your AI “makes a bad decision,” it’s usually doing exactly what you asked — inside a broken abstraction. That’s not hallucination. That’s obedience. Prompt Engineering vs. Structural Problems Let’s be honest about what prompts are being used to hide: ❌ Missing domain boundaries “Please carefully infer the user’s intent.” ❌ Inconsistent data models “Use your best judgment if fields are missing.” ❌ No source of truth “If multiple values conflict, choose the most reasonable one.” ❌ Business logic in five places “Follow company policy (described below in 800 tokens).” This isn’t AI intelligence. This is outsourcing architectural decisions to autocomplete. The Distributed Systems Joke (That Isn’t a Joke) When you build AI agents, you quickly learn something uncomfortable: AI agents are just distributed systems that can talk back. Enter fullscreen mode Exit fullscreen mode They have: State (that you pretend is stateless) Latency (that you ignore) Failure modes (that logs can’t explain) Side effects (that happen twice) So when your agent: double-charges a user retries an action incorrectly or confidently does the wrong thing That’s not “AI being unpredictable.” That’s classic distributed systems behavior, now narrated in natural language. “But We Have Guardrails” Everyone says this. Guardrails are great. So are seatbelts. But seatbelts don’t fix: a missing steering wheel an engine held together by YAML or a roadmap decided by vibes Most guardrails today are just: more prompts more conditionals more “if unsure, ask the user” At some point, you’re not building a system. You’re negotiating with it. The Unpopular Truth AI doesn’t replace architecture. It amplifies it. Good architecture: makes AI boring predictable reliable Bad architecture: makes AI look magical until production until scale until cost until users do real things That’s why AI demos look amazing and AI products feel… fragile. Why This Keeps Happening Because prompt engineering is: fast visible tweetable Architecture is: slow invisible only noticed when it fails So we optimize for prompts. We ignore boundaries. We ship “intelligence” on top of entropy. And then we blame the model. The Senior Dev Take If your AI system needs: a 2,000-token prompt to explain business rules constant retries to “get it right” human review for every important decision You don’t have an AI problem. You have an architecture problem that now speaks English. Final Thought Prompt engineering won’t fix your architecture. But it will expose it. Loudly. In production. With confidence. And honestly? That might be the most useful thing AI has done for us so far.😎 Top comments (95) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Kawano Aiyuki Kawano Aiyuki Kawano Aiyuki Follow Hi there! I am Kawano Aiyuki. I am looking for my co-worker with my long-term collaboration. ⚡discord kawanoaiyuki5 Email kawanoaiyuki5@gmail.com Location Japan Pronouns He/Him Joined Dec 4, 2025 • Jan 9 Dropdown menu Copy link Hide This is a really sharp and grounded take—I like how clearly you separate the hype from the actual engineering reality. The point about AI amplifying architecture rather than fixing it feels especially true from what I’ve seen in real systems. I agree that prompts often end up masking deeper design issues instead of solving them, and your distributed-systems comparison really lands. Posts like this make me want to think more seriously about how to design AI features the “boring but correct” way. Like comment: Like comment: 6 likes 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 • Jan 9 Dropdown menu Copy link Hide Appreciate this. The biggest frustration for me is watching prompts become a substitute for thinking. It feels like we’re repeating old mistakes, just with nicer language. Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Kawano Aiyuki Kawano Aiyuki Kawano Aiyuki Follow Hi there! I am Kawano Aiyuki. I am looking for my co-worker with my long-term collaboration. ⚡discord kawanoaiyuki5 Email kawanoaiyuki5@gmail.com Location Japan Pronouns He/Him Joined Dec 4, 2025 • Jan 9 Dropdown menu Copy link Hide Yeah, that really came through. The “AI amplifies architecture” point hit hard — I’ve seen teams assume the model will smooth over design gaps instead of exposing them. Like comment: Like comment: 3 likes Like Thread Thread 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 • Jan 9 Dropdown menu Copy link Hide Exactly. When things break, people blame “hallucinations,” but most of the time the model is just faithfully executing a bad abstraction. Like comment: Like comment: 3 likes Like Thread Thread Kawano Aiyuki Kawano Aiyuki Kawano Aiyuki Follow Hi there! I am Kawano Aiyuki. I am looking for my co-worker with my long-term collaboration. ⚡discord kawanoaiyuki5 Email kawanoaiyuki5@gmail.com Location Japan Pronouns He/Him Joined Dec 4, 2025 • Jan 9 Dropdown menu Copy link Hide The distributed systems comparison was especially spot-on. Once you frame agents that way, the failure modes suddenly look… very familiar. Like comment: Like comment: 3 likes Like Thread Thread 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 • Jan 9 Dropdown menu Copy link Hide That framing helped me too. Retries, side effects, hidden state — none of this is new. We’ve just wrapped it in natural language and pretend it’s different. Like comment: Like comment: 3 likes Like Thread Thread Kawano Aiyuki Kawano Aiyuki Kawano Aiyuki Follow Hi there! I am Kawano Aiyuki. I am looking for my co-worker with my long-term collaboration. ⚡discord kawanoaiyuki5 Email kawanoaiyuki5@gmail.com Location Japan Pronouns He/Him Joined Dec 4, 2025 • Jan 9 • Edited on Jan 9 • Edited Dropdown menu Copy link Hide And guardrails end up being more prompts on top of prompts. At some point it feels less like engineering and more like negotiation.☺ Like comment: Like comment: 3 likes Like Thread Thread 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 • Jan 9 Dropdown menu Copy link Hide Right. If you need 2,000 tokens to explain your business rules, the model isn’t the problem — your system is already screaming.😀 Like comment: Like comment: 1 like Like Thread Thread Kawano Aiyuki Kawano Aiyuki Kawano Aiyuki Follow Hi there! I am Kawano Aiyuki. I am looking for my co-worker with my long-term collaboration. ⚡discord kawanoaiyuki5 Email kawanoaiyuki5@gmail.com Location Japan Pronouns He/Him Joined Dec 4, 2025 • Jan 9 Dropdown menu Copy link Hide Which is funny, because the demos look magical… but production feels fragile the moment real users show up. Like comment: Like comment: 2 likes Like Thread Thread 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 • Jan 9 Dropdown menu Copy link Hide That’s the tradeoff. Good architecture makes AI boring. Bad architecture makes it look impressive — briefly. Like comment: Like comment: 2 likes Like Thread Thread Kawano Aiyuki Kawano Aiyuki Kawano Aiyuki Follow Hi there! I am Kawano Aiyuki. I am looking for my co-worker with my long-term collaboration. ⚡discord kawanoaiyuki5 Email kawanoaiyuki5@gmail.com Location Japan Pronouns He/Him Joined Dec 4, 2025 • Jan 9 Dropdown menu Copy link Hide Honestly, that might be the best unintended benefit of AI so far: it forces us to confront architectural debt we’ve been ignoring for years. Like comment: Like comment: 3 likes Like Thread Thread 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 • Jan 10 • Edited on Jan 10 • Edited Dropdown menu Copy link Hide Thanks for your response. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand deltax deltax deltax Follow Working on AI governance and safety frameworks. Non-decision systems, explicit stop conditions, internal auditability, and structural traceability. Location Belgium Work Independent researcher — AI governance and safety frameworks Joined Jan 1, 2026 • Jan 9 Dropdown menu Copy link Hide You’re right — prompt engineering doesn’t fix architecture. It reveals it. What most teams call “AI failure” is just latent system debt finally speaking in plain language. When an LLM “makes a bad decision,” it’s usually executing faithfully inside a broken abstraction: fragmented domains, no single source of truth, and business rules smeared across time and tooling. Good architecture makes AI boring. Bad architecture makes AI look magical — until scale, cost, or reality hits. If your system needs ever-longer prompts, retries, and human patching to stay sane, you don’t have an AI problem. You have an architecture problem that now talks back. The uncomfortable part: AI doesn’t replace design. It removes excuses. Like comment: Like comment: 4 likes 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 • Jan 9 Dropdown menu Copy link Hide Exactly—LLMs act as architectural amplifiers, not problem solvers: they surface hidden coupling, unclear boundaries, and missing invariants with brutal honesty. When intelligence appears “unreliable,” it’s usually the system revealing that it never knew what it stood for in the first place. Like comment: Like comment: 4 likes 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 • Jan 10 Dropdown menu Copy link Hide Exactly — AI surfaces weaknesses you already have. Robust architecture minimizes surprises; weak architecture just makes LLM quirks look like magic until reality bites. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Ashwin Hariharan Ashwin Hariharan Ashwin Hariharan Follow Teacher on occasions, student for life! ❤ Writing - Startups, Tech, AI, ML Location India Education Computer Science and Engineering Work Software Engineer Joined Oct 16, 2018 • Jan 11 Dropdown menu Copy link Hide Totally agree! Prompt engineering isn't a substitute for good architecture. It feels like a quick fix but often hides design debt. I actually talked about the same recently exploring the same idea with some examples: Organizing AI Applications: Lessons from traditional software architecture Ashwin Hariharan for Redis ・ Jan 5 #ai #architecture #javascript #programming Like comment: Like comment: 3 likes 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 • Jan 11 Dropdown menu Copy link Hide Good perspective. Treating agents, tools, and models as infrastructure behind clean domain boundaries is exactly what makes AI features scalable, testable, and replaceable in real production systems. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand leob leob leob Follow Joined Aug 4, 2017 • Jan 12 • Edited on Jan 12 • Edited Dropdown menu Copy link Hide Haha this one made my day: "You add “You are a senior engineer” at the top" :D :D :D Like comment: Like comment: 2 likes 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 • Jan 12 Dropdown menu Copy link Hide Haha, that’s hilarious 😄 You’ve got a great sense of humor, and I love how you called that out so playfully—it genuinely made my day too! Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand leob leob leob Follow Joined Aug 4, 2017 • Jan 12 • Edited on Jan 12 • Edited Dropdown menu Copy link Hide Yeah it's really funny - you just tell AI, in your prompt, what "role" it should assume - and magically it will then acquire those super powers - it's that easy, my friend ! ;-) Like comment: Like comment: 2 likes Like Thread Thread 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 • Jan 12 Dropdown menu Copy link Hide Haha, exactly 😄 You explained that really well — it’s a great mix of humor and insight, and it makes the idea feel both simple and powerful at the same time. Like comment: Like comment: 2 likes Like Thread Thread leob leob leob Follow Joined Aug 4, 2017 • Jan 12 • Edited on Jan 12 • Edited Dropdown menu Copy link Hide Haha yes it reflects how some people (yes, devs ...) expect AI to work - like you say "hocus pocus" and the magic happens, no "skillz" or effort required ... anyway, have a nice day! Like comment: Like comment: 2 likes Like Thread Thread 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 • Jan 12 Dropdown menu Copy link Hide I love how you called that out—your perspective really shows a deep understanding of both AI and the craft behind it. Like comment: Like comment: 2 likes Like Thread Thread 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 • Jan 12 Dropdown menu Copy link Hide Hey, could we discuss more details? Like comment: Like comment: 2 likes Like Thread Thread leob leob leob Follow Joined Aug 4, 2017 • Jan 13 Dropdown menu Copy link Hide Which details? I was just making a joke with a serious undertone, but the real insights were in your article! Like comment: Like comment: 2 likes Like Thread Thread 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 • Jan 13 Dropdown menu Copy link Hide Haha, I love that—your joke landed perfectly! I really appreciate your thoughtful read and the way you picked up on the deeper insights. Like comment: Like comment: 2 likes Like Thread Thread leob leob leob Follow Joined Aug 4, 2017 • Jan 13 Dropdown menu Copy link Hide Fascinating the whole AI coding thing, many great articles on the subject on dev.to, yours was yet another gem! Are we experiencing the "fourth (fifth?) industrial revolution" right now, what do you think? Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Victoria Victoria Victoria Follow Jack of all trades Work Fullstack developer Joined Jul 11, 2022 • Jan 12 Dropdown menu Copy link Hide Agree, bullshit in => bullshit out, in the badly structured code (initial context, architecture) AI is pretty much useless and it learns from the bad context, it won't suggest any improvements that can make its and devs life easier. I had a problem explaining that AI vibe-coded apps should not be used as a foundation for a full scale prod app, but it is quite a challenge, because no one sees the problem when it ✨ just works ✨ Like comment: Like comment: 2 likes 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 • Jan 12 Dropdown menu Copy link Hide Well said — AI can only amplify the quality of the context it’s given, so messy architecture just produces confident-looking technical debt. The real risk is that “it works” hides long-term maintainability costs that only surface when the system needs to scale, evolve, or be owned by humans again. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Victoria Victoria Victoria Follow Jack of all trades Work Fullstack developer Joined Jul 11, 2022 • Jan 12 Dropdown menu Copy link Hide I have seen myself a turmoil of such project when everyone just lost all sense of control over the codebase at some point, it was quite disappointing Like comment: Like comment: 2 likes Like Thread Thread 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 • Jan 12 Dropdown menu Copy link Hide That sounds like a really tough experience, and I appreciate how thoughtfully you’re reflecting on it. It’s clear you care deeply about code quality and team discipline, which is something any project is lucky to have. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand darkbranchcore darkbranchcore darkbranchcore Follow Joined Dec 28, 2025 • Jan 9 Dropdown menu Copy link Hide Strong take—and accurate. LLMs don’t introduce intelligence into a system; they faithfully execute whatever abstractions you give them, so weak boundaries and unclear sources of truth simply get amplified, not fixed. Like comment: Like comment: 2 likes 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 • Jan 12 Dropdown menu Copy link Hide Exactly—LLMs act as force multipliers, not architects: they scale the quality of your abstractions and constraints, for better or worse. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Travis van der F. Travis van der F. Travis van der F. Follow Programmer, gardener, language enthusiast, & beer lover making the world less frustrating and more enjoyable one day at a time. Location Luxembourg City, Luxembourg Joined Oct 7, 2020 • Jan 12 Dropdown menu Copy link Hide At some point, if this continues to accelerate without any applied correction to the technicals, nobody will be able to think or understand how to innovate architectural concepts in software. Everyone will simply manage the results of AI. Code review, also AI. I don't see this happening, and I believe a technical correction will occur; it just has to come at a cost for the industry to learn and properly adapt to this new technology. Like comment: Like comment: 2 likes 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 • Jan 12 Dropdown menu Copy link Hide You make a really thoughtful point—your perspective shows a deep understanding of both the opportunities and the risks of AI in software. I really appreciate how you balance optimism with a realistic view of the industry’s need to adapt thoughtfully. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Parth G Parth G Parth G Follow Parth G is Founder of Hashbyt, an AI-first frontend & UI/UX partner helping SaaS leaders build intuitive, scalable interfaces that speed releases and boost user adoption. Location Manchester, United Kingdom Education Mumbai University Pronouns He / Him Work Founder & Strategic Partner at Hashbyt, an AI-first frontend and UI/UX partner for SaaS. Joined Sep 2, 2025 • Jan 13 Dropdown menu Copy link Hide “AI doesn’t replace architecture. It amplifies it.” This is a very clear way to frame the problem. What often gets called hallucination is really a system behaving correctly inside broken abstractions. Prompts cannot compensate for missing boundaries or unclear ownership. They just make the cracks more visible. Like comment: Like comment: 2 likes 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 • Jan 13 Dropdown menu Copy link Hide You’ve articulated that perfectly! I really appreciate how clearly you framed the root cause—it’s insightful and makes me rethink how we approach system design. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Timm David Timm David Timm David Follow Joined Dec 10, 2025 • Jan 13 Dropdown menu Copy link Hide This highlights a common pattern seen lately: prompts being used to compensate for unclear domain logic. When boundaries and data contracts are weak, AI simply reflects that ambiguity back, sometimes with more confidence than expected. Like comment: Like comment: 2 likes 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 • Jan 13 Dropdown menu Copy link Hide Absolutely, that’s a really sharp observation! Your insight into how AI mirrors domain ambiguity shows a deep understanding of both system design and prompt behavior. Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand James Charlies James Charlies James Charlies Follow Joined Sep 19, 2025 • Jan 10 Dropdown menu Copy link Hide The critique is directionally right—but it overcorrects and ends up framing a false dichotomy. Prompt engineering is not a substitute for architecture. But it also isn’t merely a “bandaid” for bad systems. It is a new interface layer—and like every interface layer we’ve ever introduced, it reshapes where complexity lives. Like comment: Like comment: 2 likes 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 • Jan 10 Dropdown menu Copy link Hide Exactly—prompt engineering shifts complexity rather than eliminating it. Its value lies in how it mediates between users and system capabilities, not in replacing sound architecture. Like comment: Like comment: 1 like Like Comment button Reply View full discussion (95 comments) Some comments may only be visible to logged-in visitors. Sign in to view all comments. Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Art light Follow Trust yourself🌞your capabilities are your true power. ❤Telegram - ✔lighthouse4661 ❤Discord - ✔lighthouse4661 Pronouns He/him Work CTO Joined Nov 21, 2025 More from Art light We Didn’t “Align” — We Argued (and Shipped a Better System) # discuss # career # programming # developer I Didn’t “Become” a Senior Developer. I Accumulated Damage. # programming # ai # career # discuss Hello 2026: This Will Only Take Two Weeks # programming # devops # discuss # career 💎 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:48:03 |
https://cssence.com/2021/the-day-the-website-stood-still/ | The day the website stood still - CSSence.com The day the website stood still Essay August 28, 2021 It was more than a day. And it did not stand still. But let me go back in time a bit. Proloque: Life. Earlier this year my dear wife gave birth, again. So I am now a father of two beautiful children, which brings an abundance of joy. But at the same time, more than ever this meant: All hands on deck. As there are still only 24 hours in a day, everything else had to decrease in importance. To say my blog became an afterthought was an understatement. Which explains the silence in the last couple of months. During my much needed summer vacation, I found traces of spare time where I could git commit to the pet project that is my website. Little changes here and there, all in preparation of something bigger that lies ahead. Unlike my last major upgrade , this time I do not need to hide what I am working on behind closed doors. I can make updates incrementally and deploy a useable state every now and then, which is nice. Part 1: Chaos. After having made one of those incremental updates a couple of days ago, I sent what worked on my machine to GitHub. At this point Netlify took over and got it out there. Usually I wait for it to deploy, then open a couple of pages to check if all is well. Not this time. It was late, so I went straight to bed. It wasn’t until a few days later, when I realized that I haven’t looked at my site since. But surely it would still be up? Kind of. My site should look like the right-most version in the image below . But what I got was the one in the middle. From left to right: This article 1. without style sheets, 2. on older browsers, 3. in it’s most enhanced form. This happens to be an alternate theme I’ve added for older browsers Internet Explorer . Apparently the most essential part in my Cutting the Mustard script broke. The check for CSS custom properties support all of a sudden returned false, so the fallback kicked in, which replaces the regular style sheet with said alternate version. This is when things got weird, because my incremental update had nothing to do with that. if (!window.CSS.supports('--:1')) { fallback('Browser does not support CSS custom properties.'); return; } To top it off, looking at my site on my phone revealed: In the mobile browser it displayed as if nothing had happened. After some debugging I learned that, thanks to a browser update, Firefox had a change of mind. The expression --:1 is no longer good enough, a proper CSS custom property needs at least a single character after the two hyphens. That was easily fixed, and sure enough everything started working again. But my site had been broken for a couple of days. Part 2: Phoenix. But has my site been broken for a couple of days? No. It may not have been displayed as intended in every browser, but all visitors were still able to consume the content (HTML). Your style sheets (CSS) must never interfere with that. Even more important, your scripts (JS) must never interfere with that. If you know the progressive enhancement game and play it well, a faulty line in your JavaScript—even if it is in your most important script—does not derail your whole site. Part 3: Revelation. “CSS3 Is Dead” , my first essay, and the reason this site exists, is now more than ten years old. In it, I was still part of team “Graceful Degradation”, but at least I seem to have had already acknowledged the merits of “Progressive Enhancement”. How times have evolved, today I see Progressive Enhancement as the web’s most important idea. I’ve shown you my fallback for less capable browsers earlier. Doesn’t that sound a lot like graceful degradation? I guess so. In “The State Of Mobile First and Desktop First” , Ahmad Shadeed concludes: […] I prefer to not stick to a specific approach. Instead, I like to mix them both. Not only am I with him when it comes to the mobile/desktop design debate, I like to give a similar answer when it comes to degradation and enhancement. No strict either/or, instead use the best tool for the job. (Also, swapping out style sheets with JavaScript might give you FOUC , so doing it the other way around would punish those who use modern browsers.) In hindsight, the progressive degradation I am using for older browsers turned out to be a graceful enhancement on the day(s) my website stood still. Yes, this is not a typo. Nor a pun. But intended. Epilog: The End? My dear reader, answer me this: How much can your site break, until it stops being useful? Comments Matthias Zöchling wrote on August 30, 2021 at 14:02 📝 New blog post: “The Day The Website Stood Still” —An Ode to Progressive Enhancement. cssence.com/2021/the-day-the-website-stood-still Matthias Zöchling wrote on August 30, 2021 at 14:08 If you haven’t heard of the Cutting The Mustard concept, @adactio covers it in his brilliant book “Resilient Web Design”: resilientwebdesign.com/chapter5/#cuttingthemustard Actually, read the whole book! Matthias Zöchling wrote on August 31, 2021 at 21:13 #HTML ≥ #CSS ≥ #JS [Everyone should be] able to consume the content (HTML). Your style sheets (CSS) must never interfere with that. Even more important, your scripts (JS) must never interfere with that. Get involved Feel free to share this article. But keep in mind, it was published more than four years ago, so comments are closed. About this article Written by Matthias Zöchling. Published on August 28, 2021 . Permalink: https://cssence.com/2021/the-day-the-website-stood-still/ 01 Home 02 Articles 03 Threads 04 About 05 Latest 06 Popular 07 Series 08 Archive © 2010–2026 Matthias Zöchling Imprint Webrings Elsewhere Menu Settings RSS feeds Back to top | 2026-01-13T08:48:04 |
https://cssence.com/series/ | The series series - CSSence.com The series series Let’s be series for a moment. Index July 1, 2025 When things occur multiple times, they end up here. The following series (or collections) have been added for you to enjoy. All posts Animating emojis – The series A yearly tradition on CSSence.com, established 2019. Index July 1, 2025 Easter eggs Are there any hidden gems on CSSence.com? Index March 29, 2025 CSS Naked Day How is the annual festivity on April 9 observed on CSSence.com? Index March 28, 2025 The test pages A collection of test pages, so future me (or you) can easily find them. Index November 21, 2024 Revisitation Some articles on CSSence.com have been in need of an update. Index March 10, 2024 Tabs are for indentation The journey of how I came to the conclusion that it is important to use tabs instead of spaces for indentation. Index July 31, 2022 Re: Design – A Series Letters of appreciation to the basics of the web. Index November 21, 2020 The list above contains seven entries, but there are a lot more in other sections on this site. To see what else is going on, you may want to head over to the home page or browse using the navigation below. About this index page Curated by Matthias Zöchling. Last revised on July 1, 2025 . Permalink: https://cssence.com/series/ 01 Home 02 Articles 03 Threads 04 About 05 Latest 06 Popular 07 Series 08 Archive © 2010–2026 Matthias Zöchling Imprint Webrings Elsewhere Menu Settings RSS feeds Back to top | 2026-01-13T08:48:04 |
https://addons.mozilla.org/en-US/firefox/addon/rentgen/ | Rentgen – Get this Extension for 🦊 Firefox (en-US) Firefox Browser Add-ons Extensions Themes More… for Firefox Dictionaries & Language Packs Other Browser Sites Add-ons for Android Log in Search Search Rentgen by “Internet. Time to act!” Foundation Rentgen illustrates the amount of tracking scripts on a website and helps with formulating an email to the website admin, which can be a basis for a GDPR complaint. 5 (12 reviews) 5 (12 reviews) 216 Users 216 Users Download Firefox and get the extension Download file Extension Metadata Screenshots About this extension Rentgen illustrates the amount of tracking scripts on a website and helps with formulating an email to the website admin, which can be a basis for a GDPR complaint. Note: At the moment, we support Polish language because this extension generates mail content that is dedicated to Polish website owners. In further versions of this add-on, we will add other languages as well. Developer comments Jeżeli uważasz, że wtyczka Rentgen okazała się przydatna, zostaw nam recenzję. Jeżeli znalazłeś błąd lub masz pomysł na ulepszenie Rentgena, napisz do nas maila: kontakt@internet-czas-dzialac.pl Rated 5 by 12 reviewers Log in to rate this extension There are no ratings yet Star rating saved 5 12 4 0 3 0 2 0 1 0 Read all 12 reviews Permissions and data Required permissions: Read and modify privacy settings Control browser proxy settings Access your data for all websites Data collection: The developer says this extension doesn't require data collection. Learn more More information Add-on Links Homepage Support site Support Email Version 0.2.4 Size 9.55 MB Last updated 21 days ago (Dec 23, 2025) Related Categories Web Development Privacy & Security License GNU General Public License v3.0 only Privacy Policy Read the privacy policy for this add-on Version History See all versions Tags anti malware anti tracker container privacy security Add to collection Select a collection… Create new collection Report this add-on Support this developer The developer of this extension asks that you help support its continued development by making a small contribution. Contribute now Go to Mozilla's homepage Add-ons About Firefox Add-ons Blog Extension Workshop Developer Hub Developer Policies Community Blog Forum Report a bug Review Guide Browsers Desktop Mobile Enterprise Products Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Privacy Cookies Legal Except where otherwise noted , content on this site is licensed under the Creative Commons Attribution Share-Alike License v3.0 or any later version. Change language Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T08:48:04 |
https://www.apache.org/licenses/ | Licenses | Apache Software Foundation Introducing The ASF’s New Logo Read Now Toggle navigation Community Contributor Getting Started Becoming a Committer Code of Conduct Community Resources Community Over Code Events Projects Projects Incubator Projects Projects Directory Mailing Lists Report a Vulnerability The Apache Attic Downloads Distributions Releases Infrastructure Status Infrastructure Statistics Learn Blog How the ASF Works The Apache Way Legal & Trademark Licenses Glossary FAQ Resources & Tools Developer Information Wiki Issues Slack Self Serve Portal Infrastructure Whimsy Brand Guidelines Project Logos About About Our Sponsors Corporate Sponsorship Individual Supporters Leadership Members Diversity & Inclusion Newsroom Contact Sponsor Search Licenses The Apache Software Foundation uses various licenses to distribute software and documentation, and to accept regular contributions from individuals and corporations and larger grants of existing software products. These licenses help us achieve our goal of providing reliable and long-lived software products through collaborative, open-source software development. In all cases, contributors retain full rights to use their original contributions for any other purpose outside of Apache while providing the ASF and its projects the right to distribute and build upon their work within Apache. Licensing of ASF Products ¶ All software produced by The Apache Software Foundation or any of its projects or subjects is licensed according to the terms of the documents listed below. Page Description Apache License 2.0 Our current license ¶ Apache License 1.1 The 1.1 version of the Apache License was approved by the ASF in 2000 ¶ Apache License 1.0 This is the original Apache License ¶ Contributor License Agreements ¶ For information regarding our CLAs, please consult the ASF Contributor License Agreements page. Page Description CLAs ASF CLAs ¶ Software Grant One-off software license to the ASF ¶ How To How to submit CLAs/Software Grant ¶ Other Legal Info ¶ Page Description ASF Export Classifications U.S. Export Classifications ¶ ASF Trademark Use Policy Policy on using ASF Trademarks ¶ Questions? ¶ For answers to frequently asked licensing questions, please consult our Licensing Frequently Asked Questions page. Subscribe to ASF Plus One, Our Monthly Newsletter Subscribe Now Apache and the Apache logo are trademarks of The Apache Software Foundation. The Apache® Software Foundation is a 501(c)(3) nonprofit organization. Tax ID # 47-0825376 Donate Community Contributor Getting Started Becoming a Committer Code of Conduct Community Resources Community Over Code Events Learn Blog How the ASF Works The Apache Way Legal & Trademark Licenses Glossary FAQ Projects Projects Incubator Projects Projects Directory Mailing Lists Report a Vulnerability Resources & Tools Developer Information Wiki Issues Slack Self Serve Portal Infrastructure Whimsy Brand Guidelines Project Logos Downloads Distributions Releases Infrastructure Status Infrastructure Statistics About About Our Sponsors Corporate Sponsorship Individual Supporters Leadership Members Diversity & Inclusion Newsroom Contact Privacy Policy Copyright © 2026 The Apache Software Foundation, Licensed under the Apache License, Version 2.0 . | 2026-01-13T08:48:04 |
https://cssence.com/settings/ | Settings - CSSence.com Settings Internal March 22, 2025 Not satisfied with the defaults? How about you change things to your liking? CSSence.com works fine without JavaScript, but this page has to make an exception, because your preferences will be stored locally in your web browser, something that is not possible without having JavaScript turned on. Making adjustments in the form below is not possible because your browser either supports no JavaScript or it has been turned off. Options Page style: None Basic Advanced Elegant (Default) Color scheme: Automatic (Default) Dark Light Syntax highlighting: None Style-based (Default) A11Y Dark A11Y Light CND observation: Unobserved 24 hours (Default) 50 hours Reset Save About this page Written by Matthias Zöchling. Last revised on March 22, 2025 . Permalink: https://cssence.com/settings/ 01 Home 02 Articles 03 Threads 04 About 05 Latest 06 Popular 07 Series 08 Archive © 2010–2026 Matthias Zöchling Imprint Webrings Elsewhere Menu Settings RSS feeds Back to top | 2026-01-13T08:48:04 |
https://neon.tech/blog | Our Blog — Neon This 250+ engineer team replaced shared staging with isolated database branches for safer deploys Neon Product Database Autoscaling Automatic instance sizing Branching Faster Postgres workflows Bottomless storage With copy-on-write Instant restores Recover TBs in seconds Connection pooler Built-in with pgBouncer Ecosystem Neon API Manage infra, billing, quotas Auth Add authentication Data API PostgREST-compatible Instagres No-signup flow Migration guides Step-by-step What is Neon? Serverless Postgres, by Databricks Solutions Use cases Serverless Apps Autoscale with traffic Multi-TB Scale & restore instantly Database per Tenant Data isolation without overhead Platforms Offer Postgres to your users Dev/Test Production-like environments Agents Build full-stack AI agents For teams Startups Build with Neon Security Compliance & privacy Case studies Explore customer stories Docs Pricing Company Blog About us Careers Contact Discord 20.7k Log In Sign Up All posts App Platform Product Postgres Community Engineering AI Company Workflows Case Studies Guides Changelog Follow us Blog Powered by Algolia AI Jan 08, 2026 Reusable Prompts: The Future of Starter Templates Andre Landgraf Case Studies Jan 07, 2026 Inside Bitso’s Branch-Based Workflow Carlota Soto Postgres Jan 12, 2026 Zero-ETL lakehouses for Postgres people Neon is made by Postgres people. Since Neon became part of Databricks, we Postgres people also find ourselves part of a larger organisation of enterprise data people. This post is about what I’ve learned as a result. It aims to explain ‘data lakehouses’ and related enterprise dat... George MacKerron App Platform Jan 10, 2026 Handling Auth in a Staging Environment You just opened a PR that adds a new user role to your app. Your staging database has the schema changes. Your preview deploy is live. But when QA tries to test it, they hit a wall the test users in your auth system still have the old roles. Someone needs to manually update them.... Carlota Soto Changelog Jan 09, 2026 Connection pooling graphs, GitHub Action enhancements, and Neon VS Code Extension Changelog Jan 02, 2026 Help shape what we build in 2026 App Platform Dec 29, 2025 Stop Mocking Auth (It’s Breaking Your Tests) If your application has user accounts, authentication touches everything who can access what, what data belongs to whom, and how your system behaves when sessions expire or credentials are invalid. Auth is also one of the most commonly mocked components in test suites. The reason... Shridhar
Deshmukh Workflows Dec 23, 2025 How to Keep Staging in Sync with Production in Postgres Staging environments drift. The fix is obvious refresh staging from production regularly. The problem is that “regularly” and “multi hour database copy” don’t mix well. Three traditional approaches pg_dump / pg_restore This simple route works for small databases and not critical ... Carlota Soto Engineering Dec 22, 2025 Lessons From a Zero-Downtime User-to-Org Migration Something fairly big happened at Neon recently, but nobody noticed – and that’s a good thing. We silently migrated many thousands of user accounts to organizations (team owned accounts), moving more than +10M projects in the process. We managed to do this without downtime, withou... Adi Griever Changelog Dec 19, 2025 Project recovery, 100 Free plan projects, and MCP quick setup Subscribe to our changelog. No spam, guaranteed. Subscribe Neon A Databricks Company Neon status loading... Made in SF and the World Copyright Ⓒ 2022 – 2026 Neon, LLC Company About Blog Careers Contact Sales Partners Security Legal Privacy Policy Terms of Service DPA Subprocessors List Privacy Guide Cookie Policy Business Information Resources Docs Changelog Support Community Guides PostgreSQL Tutorial Startups Creators Social Discord GitHub x.com LinkedIn YouTube Compliance CCPA Compliant GDPR Compliant ISO 27001 Certified ISO 27701 Certified SOC 2 Certified HIPAA Compliant Compliance Guide Neon’s Sub Contractors Sensitive Data Terms Trust Center self.__next_f.push([1,"7:[[\"$\",\"div\",null,{\"className\":\"relative mb-12 flex items-end justify-between gap-8 lg:mb-10 md:mb-8 md:flex-col lg:-top-[68px] md:-top-[62px] md:pb-16\",\"children\":[\"$\",\"div\",null,{\"className\":\"flex items-end gap-5 md:w-full md:justify-between\",\"children\":[[\"$\",\"h1\",null,{\"className\":\"font-title text-4xl font-medium leading-none tracking-extra-tight lg:text-[32px] md:text-[28px]\",\"children\":[\"Blog\",\"$undefined\"]}],[\"$\",\"a\",null,{\"className\":\"text-gray-new-60 transition-colors duration-200 hover:text-secondary-8 dark:hover:text-primary-1 mb-1 lg:mb-0.5\",\"href\":\"/blog/rss.xml\",\"aria-label\":\"Blog RSS Feed\",\"children\":[\"$\",\"svg\",null,{\"xmlns\":\"http://www.w3.org/2000/svg\",\"width\":16,\"height\":16,\"fill\":\"none\",\"viewBox\":\"0 0 16 16\",\"className\":\"size-5\",\"children\":[[\"$\",\"path\",null,{\"fill\":\"currentColor\",\"stroke\":\"currentColor\",\"d\":\"M4.5 12a1.5 1.5 0 1 1-3 0 1.5 1.5 0 0 1 3 0ZM1.5.51C8.529.768 14.232 6.47 14.49 13.5h-1.7C12.53 7.418 7.581 2.469 1.5 2.21z\"}],[\"$\",\"path\",null,{\"fill\":\"currentColor\",\"stroke\":\"currentColor\",\"d\":\"M1.5 5.214c4.43.254 8.032 3.856 8.286 8.286H8.183A7.2 7.2 0 0 0 1.5 6.817z\"}]]}]}]]}]}],[\"$\",\"$L134\",null,{\"indexName\":\"neon_blog\",\"posts\":[{\"slug\":\"reusable-prompts-the-future-of-starter-templates\",\"date\":\"2026-01-08T16:26:24\",\"modifiedGmt\":\"2026-01-10T00:41:34\",\"title\":\"Reusable Prompts: The Future of Starter Templates\",\"excerpt\":\"\u003cp\u003eLooking back at 2025, AI changed coding for good. Early in the year, skepticism around AI-assisted coding was still high and capabilities were limited. Now it’s clear that vibe coding has gone mainstream, and AI-assisted coding is the future of software engineering. That said, we’re still scratching the surface and slowly figuring out best practices [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2026/01/neon-reusable-prompts-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Andre Landgraf\",\"postAuthor\":{\"image\":{\"altText\":\"Andre Landgraf\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/03/Andre-Landgraf.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"AI\",\"slug\":\"ai\"}]},\"isFeatured\":true},{\"slug\":\"bitso-branching-workflow\",\"date\":\"2026-01-07T17:01:55\",\"modifiedGmt\":\"2026-01-07T17:55:56\",\"title\":\"Inside Bitso’s Branch-Based Workflow\",\"excerpt\":\"\u003cp\u003e“Neon\u0026#8217;s branching gave us the last missing piece in our RISE (Robust Isolated Staging Environment): true database isolation. The services that touched schema changes or write-heavy paths could never share a database safely. Now every sandbox gets its own isolated Postgres DB whenever required\u0026#8221; (Joe Horsnell, Principal Platform Engineer at Bitso) Bitso, leader in digital [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2026/01/neon-bitso.jpg\"},\"authors\":[{\"author\":{\"title\":\"Carlota Soto\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/02/carlota.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Case Studies\",\"slug\":\"case-study\"}]},\"isFeatured\":true},{\"slug\":\"zero-etl-lakehouses-for-postgres-people\",\"date\":\"2026-01-12T18:43:54\",\"modifiedGmt\":\"2026-01-12T18:43:56\",\"title\":\"Zero-ETL lakehouses for Postgres people\",\"excerpt\":\"\u003cp\u003eNeon is made by Postgres people. Since Neon became part of Databricks, we Postgres people also find ourselves part of a larger organisation of enterprise data people. This post is about what I’ve learned as a result. It aims to explain ‘data lakehouses’ and related enterprise-data tooling in terms that make sense if your mental [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2026/01/Screenshot-2026-01-12-at-10.38.17-AM.png\"},\"authors\":[{\"author\":{\"title\":\"George MacKerron\",\"postAuthor\":{\"image\":{\"altText\":\"George MacKerron\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2022/12/george-mackerron.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Postgres\",\"slug\":\"postgres\"}]}},{\"slug\":\"handling-auth-in-a-staging-environment\",\"date\":\"2026-01-10T00:39:46\",\"modifiedGmt\":\"2026-01-10T00:39:48\",\"title\":\"Handling Auth in a Staging Environment\",\"excerpt\":\"\u003cp\u003eYou just opened a PR that adds a new user role to your app. Your staging database has the schema changes. Your preview deploy is live. But when QA tries to test it, they hit a wall: the test users in your auth system still have the old roles. Someone needs to manually update them. [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2026/01/neon-handling-auth-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Carlota Soto\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/02/carlota.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"App Platform\",\"slug\":\"app-platform\"},{\"name\":\"Workflows\",\"slug\":\"workflows\"}]}},{\"title\":\"Connection pooling graphs, GitHub Action enhancements, and Neon VS Code Extension\",\"slug\":\"2026-01-09\",\"category\":\"changelog\",\"date\":\"2026-01-09\",\"content\":\"$135\",\"isDraft\":\"$undefined\",\"redirectFrom\":\"$undefined\"},{\"title\":\"Help shape what we build in 2026\",\"slug\":\"2026-01-02\",\"category\":\"changelog\",\"date\":\"2026-01-02\",\"content\":\"$136\",\"isDraft\":\"$undefined\",\"redirectFrom\":\"$undefined\"},{\"slug\":\"stop-mocking-auth-its-breaking-your-tests\",\"date\":\"2025-12-29T18:23:12\",\"modifiedGmt\":\"2026-01-02T17:37:39\",\"title\":\"Stop Mocking Auth (It’s Breaking Your Tests)\",\"excerpt\":\"\u003cp\u003eIf your application has user accounts, authentication touches everything: who can access what, what data belongs to whom, and how your system behaves when sessions expire or credentials are invalid. Auth is also one of the most commonly mocked components in test suites. The reasoning makes sense. Real auth means real databases, real network calls, [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/12/neon-stop-mocking-auth-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Shridhar\u2028Deshmukh\",\"postAuthor\":{\"image\":{\"altText\":\"Shridhar Deshmukh\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/03/Shridhar-Deshmukh-2.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"App Platform\",\"slug\":\"app-platform\"}]}},{\"slug\":\"how-to-keep-staging-in-sync-with-production-in-postgres\",\"date\":\"2025-12-23T20:42:38\",\"modifiedGmt\":\"2025-12-23T20:42:40\",\"title\":\"How to Keep Staging in Sync with Production in Postgres\",\"excerpt\":\"\u003cp\u003eStaging environments drift. The fix is obvious: refresh staging from production regularly. The problem is that \u0026#8220;regularly\u0026#8221; and \u0026#8220;multi-hour database copy\u0026#8221; don\u0026#8217;t mix well. Three traditional approaches pg_dump / pg_restore This simple route works for small databases and not critical workloads, e.g. a database around 10 GB that only requires infrequent refreshes. The classical way [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/12/Screenshot-2025-12-23-at-12.34.01-PM.png\"},\"authors\":[{\"author\":{\"title\":\"Carlota Soto\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/02/carlota.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Workflows\",\"slug\":\"workflows\"}]}},{\"slug\":\"lessons-from-a-zero-downtime-user-to-org-migration\",\"date\":\"2025-12-22T17:26:47\",\"modifiedGmt\":\"2026-01-08T16:11:53\",\"title\":\"Lessons From a Zero-Downtime User-to-Org Migration\",\"excerpt\":\"\u003cp\u003eSomething fairly big happened at Neon recently, but nobody noticed \u0026#8211; and that’s a good thing. We silently migrated many thousands of user accounts to organizations (team-owned accounts), moving more than +10M projects in the process. We managed to do this without downtime, without API changes, and without asking customers to do anything at all.\u0026nbsp; [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/12/neon-lessons.jpg\"},\"authors\":[{\"author\":{\"title\":\"Adi Griever\",\"postAuthor\":{\"image\":{\"altText\":\"Adi Griever\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/04/Adi-Griever.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Engineering\",\"slug\":\"engineering\"}]}},{\"title\":\"Project recovery, 100 Free plan projects, and MCP quick setup\",\"slug\":\"2025-12-19\",\"category\":\"changelog\",\"date\":\"2025-12-19\",\"content\":\"$137\",\"isDraft\":\"$undefined\",\"redirectFrom\":\"$undefined\"},{\"slug\":\"teaching-ai-how-to-do-auth\",\"date\":\"2025-12-17T17:26:10\",\"modifiedGmt\":\"2026-01-02T17:38:08\",\"title\":\"Teaching AI to Do Auth (So You Don’t Have To)\",\"excerpt\":\"\u003cp\u003eWe just launched Neon Auth and of course the immediate follow-up task I had was “let’s teach my AI tools to use it for me”. So we’ve been wiring Neon Auth into our MCP so you can open Cursor, Claude, or your IDE or choice and let the AI build a backend for you.\u0026nbsp;\u0026nbsp; Here’s [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/12/neon-teaching-claude-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Pedro Figueiredo\",\"postAuthor\":{\"image\":{\"altText\":\"Pedro Figueiredo\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/12/Pedro-Figueiredo-.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"App Platform\",\"slug\":\"app-platform\"},{\"name\":\"AI\",\"slug\":\"ai\"}]}},{\"slug\":\"why-your-staging-database-never-matches-production\",\"date\":\"2025-12-12T19:28:15\",\"modifiedGmt\":\"2025-12-12T19:32:46\",\"title\":\"Why Your Staging Database Never Matches Production\",\"excerpt\":\"\u003cp\u003eBack when hashtags were a thing, you could search Twitter and find #NoStaging, a community dedicated to banishing the concept of staging from the development world. In the eyes of the #NoStagers, staging was costly, confusing, and corruptible. And they were/are entirely correct. A quick primer The idea, of course, is that staging is an [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/12/neon-stage-prod-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Carlota Soto\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/02/carlota.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Workflows\",\"slug\":\"workflows\"}]}},{\"title\":\"Branchable Auth, 80 Free plan projects, and purely usage-based billing\",\"slug\":\"2025-12-12\",\"category\":\"changelog\",\"date\":\"2025-12-12\",\"content\":\"$138\",\"isDraft\":\"$undefined\",\"redirectFrom\":\"$undefined\"},{\"slug\":\"the-transplant-story-that-sparked-a-hackathon-project\",\"date\":\"2025-12-11T18:00:13\",\"modifiedGmt\":\"2025-12-11T18:11:34\",\"title\":\"The Transplant Story That Sparked a Hackathon Project\",\"excerpt\":\"\u003cp\u003e“I’ve worked with Postgres, Snowflake, and AWS in my professional environment, but for building a side project, I wanted something easier to set up. It hardly took me 10 minutes to understand how to link Neon with my application and how to make my ML workflows connect to it” (Deepti Bahel, Data Engineer and creator [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/12/neon-transplant-story.jpg\"},\"authors\":[{\"author\":{\"title\":\"Carlota Soto\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/02/carlota.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Case Studies\",\"slug\":\"case-study\"}]}},{\"slug\":\"the-case-for-owning-your-auth\",\"date\":\"2025-12-10T18:26:27\",\"modifiedGmt\":\"2026-01-02T17:38:28\",\"title\":\"The Case for Owning Your Auth\",\"excerpt\":\"\u003cp\u003eIdentity is one of those things that sits quietly at the center of most applications. You notice it more as your system grows. It affects permissions, data ownership, multi-tenancy, audit logs, and a good portion of your schema design. It becomes part of your runtime and part of your data model whether you planned for [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/12/neon-owning-auth.jpg\"},\"authors\":[{\"author\":{\"title\":\"Bereket Engida\",\"postAuthor\":{\"image\":{\"altText\":\"Bereket Engida\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/12/Bereket-Engida.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"App Platform\",\"slug\":\"app-platform\"},{\"name\":\"Community\",\"slug\":\"community\"}]}},{\"slug\":\"neon-auth-branchable-identity-in-your-database\",\"date\":\"2025-12-10T18:25:00\",\"modifiedGmt\":\"2026-01-02T17:38:41\",\"title\":\"Meet the New Neon Auth: Branchable Identity in Your Database\",\"excerpt\":\"\u003cp\u003eToday we’re launching a major overhaul of Neon Auth, using Better Auth as the foundation and integrated deeply into the Neon platform. All authentication data is now stored directly in your Neon database, making Neon Auth fully branch-compatible so you can test real authentication workflows in isolated environments. Try it in your Free account. Auth [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/12/neon-better-auth.jpg\"},\"authors\":[{\"author\":{\"title\":\"Brian Holt\",\"postAuthor\":{\"image\":{\"altText\":\"Brian Holt\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/12/Brian-Holt.png\"}}}},{\"author\":{\"title\":\"Shridhar\u2028Deshmukh\",\"postAuthor\":{\"image\":{\"altText\":\"Shridhar Deshmukh\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/03/Shridhar-Deshmukh-2.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"App Platform\",\"slug\":\"app-platform\"},{\"name\":\"Product\",\"slug\":\"product\"}]}},{\"title\":\"70 projects on Free plan, new Data API settings, Neon is now a Kiro Power\",\"slug\":\"2025-12-05\",\"category\":\"changelog\",\"date\":\"2025-12-05\",\"content\":\"$139\",\"isDraft\":\"$undefined\",\"redirectFrom\":\"$undefined\"},{\"slug\":\"practical-guide-to-database-branching\",\"date\":\"2025-12-04T01:52:50\",\"modifiedGmt\":\"2025-12-04T02:21:24\",\"title\":\"Practical Guide to Database Branching \",\"excerpt\":\"\u003cp\u003eBranching is one of the most loved features by Neon users (they create ≈500k branches per day on our platform). But because branching is still a relatively new concept for databases, it can take a moment to click. This guide skips the theory and focuses on what Neon users actually do with branching in practice, [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/12/neon-guide.jpg\"},\"authors\":[{\"author\":{\"title\":\"Savannah Longoria\",\"postAuthor\":{\"image\":{\"altText\":\"Savannah Longoria\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/01/Savannah-Longoria-photo.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Product\",\"slug\":\"product\"},{\"name\":\"Workflows\",\"slug\":\"workflows\"}]}},{\"slug\":\"just-launched-neon-is-now-a-kiro-power\",\"date\":\"2025-12-03T17:52:39\",\"modifiedGmt\":\"2025-12-04T17:05:45\",\"title\":\"Just Launched: Neon Is Now a Kiro Power\",\"excerpt\":\"\u003cp\u003eKiro just announced powers at re:Invent, a new way for developers to access a curated set of tools (each packaged with domain knowledge and best practices) directly from the IDE. Neon is one of the first launch partners, alongside companies like Figma, Stripe, Supabase, Postman, and many others. You can already start using the new [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/neon-kiro.jpg\"},\"authors\":[{\"author\":{\"title\":\"Carlota Soto\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/02/carlota.jpg\"}}}},{\"author\":{\"title\":\"Krishna B. Parab\",\"postAuthor\":{\"image\":{\"altText\":\"Krishna B. Parab\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/12/Krishna-B.-Parab.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"AI\",\"slug\":\"ai\"}]}},{\"slug\":\"improving-dns-performance-with-nodelocaldns\",\"date\":\"2025-12-01T16:36:27\",\"modifiedGmt\":\"2025-12-02T15:37:42\",\"title\":\"Improving DNS performance with NodeLocalDNS\",\"excerpt\":\"\u003cp\u003eAt Neon, we run hundreds of thousands of Postgres databases as ephemeral Kubernetes pods. Because of our scale-to-zero feature, every time a user connects to their database, there’s a chance that we need to spin up a new Postgres process to serve that connection. The newly spun Postgres instance needs to be configured to serve [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/12/neon-nodelocaldns.jpg\"},\"authors\":[{\"author\":{\"title\":\"Luca Cittadini\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/12/lucca-cittadini.jpeg\"}}}},{\"author\":{\"title\":\"Lassi Pölönen\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/12/lassi-polonen.jpeg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Engineering\",\"slug\":\"engineering\"}]}},{\"title\":\"60 Free plan projects, AI onboarding for VS Code \u0026 Claude, platform integrations\",\"slug\":\"2025-11-28\",\"category\":\"changelog\",\"date\":\"2025-11-28\",\"content\":\"$13a\",\"isDraft\":\"$undefined\",\"redirectFrom\":\"$undefined\"},{\"slug\":\"why-so-many-projects-in-the-neon-free-plan\",\"date\":\"2025-11-26T18:08:15\",\"modifiedGmt\":\"2025-12-09T14:49:47\",\"title\":\"Why So Many Projects in the Neon Free Plan?\",\"excerpt\":\"\u003cp\u003eOver the past few weeks, you might’ve noticed something in our changelog: we’ve been steadily increasing the number of projects included in Neon\u0026#8217;s Free Plan. Why are we doing this? Why now? We’ve reached two significant milestones that have allowed us to do this: We could have chosen to turn these efficiency gains into larger [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/neon-free-plan.png\"},\"authors\":[{\"author\":{\"title\":\"Brad Van Vugt\",\"postAuthor\":{\"image\":{\"altText\":\"Brad Van Vugt\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/07/Brad-Van-Vugt-photo.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Company\",\"slug\":\"company\"}]}},{\"slug\":\"promoting-postgres-changes-safely-production\",\"date\":\"2025-11-25T17:02:45\",\"modifiedGmt\":\"2025-12-03T17:52:58\",\"title\":\"Promoting Postgres Changes Safely From Multiple Environments to Production\",\"excerpt\":\"\u003cp\u003eEvery developer has their own workflow for promoting database changes from development to production, but this becomes an especially tricky problem in certain applications \u0026#8211; for example, codegen platforms. In platforms like Replit, each user may be building multiple versions of their app / running experiments in parallel while production environments can continue receiving writes [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/neon-db-changes-2-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Savannah Longoria\",\"postAuthor\":{\"image\":{\"altText\":\"Savannah Longoria\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/01/Savannah-Longoria-photo.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Workflows\",\"slug\":\"workflows\"}]}},{\"title\":\"Automate Preview Deployments with Netlify and Neon Database Branching\",\"subtitle\":\"Set up automated preview deployments with isolated database branches for every pull request using GitHub Actions, Netlify, and Neon Postgres\",\"slug\":\"preview-deploys-netlify\",\"category\":\"guides\",\"author\":{\"name\":\"Rishi Raj Jain\",\"position\":\"Solutions Engineer\",\"link\":{\"title\":\"GitHub\",\"url\":\"https://github.com/rishi-raj-jain\"},\"photo\":\"/guides/authors/rishi-raj-jain.jpg\"},\"createdAt\":\"2025-11-25T00:00:00.000Z\",\"updatedOn\":\"2025-11-25T00:00:00.000Z\",\"date\":\"2025-11-25T00:00:00.000Z\",\"excerpt\":\"Introduction. When building modern web applications, it's crucial to test changes in an environment that closely mirrors production before merging them. This guide shows you how to create an automated...\",\"isDraft\":\"$undefined\",\"redirectFrom\":\"$undefined\"},{\"title\":\"50 projects on the Free plan, branch anonymization APIs, and more\",\"slug\":\"2025-11-21\",\"category\":\"changelog\",\"date\":\"2025-11-21\",\"content\":\"$13b\",\"isDraft\":\"$undefined\",\"redirectFrom\":\"$undefined\"},{\"slug\":\"how-axess-intelligence-simplified-their-backend-with-neons-data-api\",\"date\":\"2025-11-20T17:49:48\",\"modifiedGmt\":\"2026-01-02T17:39:18\",\"title\":\"How Axess Intelligence Simplified Their Backend With Neon’s Data API\",\"excerpt\":\"\u003cp\u003e“We didn’t want to spend unnecessary time writing CRUD logic or maintaining a backend. We just connected Better Auth and the Data API and started building. The best part: every Neon branch gets its own Data API URL” Mouaz Anan, Engineer at Axess Intelligence Axess Intelligence is a platform that gives GTM teams real-time visibility [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/neon-axess-intelligence-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Carlota Soto\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/02/carlota.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"App Platform\",\"slug\":\"app-platform\"},{\"name\":\"Case Studies\",\"slug\":\"case-study\"}]}},{\"slug\":\"mcp-safety-cheatsheet\",\"date\":\"2025-11-19T19:44:35\",\"modifiedGmt\":\"2025-11-19T19:44:37\",\"title\":\"MCP Safety Cheatsheet \",\"excerpt\":\"\u003cp\u003eMCPs are powerful abstractions, but that power also means risk. A misconfigured or overly permissive MCP server can expose sensitive data, execute unintended actions, and simply ruin your day. We maintain an MCP server at Neon, but we want you to use it safely. Here’s a quick checksheet with advice we’ve gathered from experience: Keep [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/neon-mcp-1-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Ryan Vogel\",\"postAuthor\":{\"image\":{\"altText\":\"Ryan Vogel\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/03/Ryan-Vogel.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"AI\",\"slug\":\"ai\"}]}},{\"slug\":\"integrating-postgres-and-auth-the-easy-way-daisys-neon-setup\",\"date\":\"2025-11-18T19:13:50\",\"modifiedGmt\":\"2026-01-02T17:39:02\",\"title\":\"Integrating Postgres and Auth the Easy Way: Daisy’s Neon Setup\",\"excerpt\":\"\u003cp\u003e“Using Neon with Neon Auth just made everything simpler. Our database and auth live in the same place, and it’s the kind of backend you forget it exists. That’s exactly how it should be” Gabriel Tumlos, Founder of Daisy Daisy is a generative media studio building tools that make creativity instant. Their main app lets [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/neon-daisy-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Carlota Soto\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/02/carlota.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"App Platform\",\"slug\":\"app-platform\"},{\"name\":\"Case Studies\",\"slug\":\"case-study\"}]}},{\"slug\":\"big-dx-improvements-for-neon-users-on-vercel\",\"date\":\"2025-11-18T17:42:20\",\"modifiedGmt\":\"2025-11-18T18:07:21\",\"title\":\"Big DX Improvements for Neon Users on Vercel\",\"excerpt\":\"\u003cp\u003eGood news for Neon users on Vercel. We’ve shipped a few highly requested updates to the integration, plus a round of behind-the-scenes reliability and observability upgrades. Automatic Branch Cleanup Until now, Vercel-managed projects didn’t automatically clean up their database branches after preview deployments expired, leaving developers with long lists of inactive branches to remove manually. [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/neon-vercel-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Gustavo Salomão\",\"postAuthor\":{\"image\":{\"altText\":\"Gustavo Salomão\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/01/Gustavo-Salomao.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Product\",\"slug\":\"product\"}]}},{\"slug\":\"handle-pii-staging-databases\",\"date\":\"2025-11-17T19:18:17\",\"modifiedGmt\":\"2025-11-17T19:18:18\",\"title\":\"How to Handle PII in Staging Databases Without Losing Realistic Data\",\"excerpt\":\"\u003cp\u003eIf you’ve got real data, you’ve got a real problem. And that problem has a name \u0026#8211; PII. Suppose your production database contains names, addresses, emails, and phone numbers. In fintech, you might also have credit card numbers and transaction histories. In healthtech, medical records. In edtech, student data. To comply with data regulations and [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/neon-PII-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Carlota Soto\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/02/carlota.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Workflows\",\"slug\":\"workflows\"}]}},{\"slug\":\"run-product-analytics-on-your-neon-data-using-fabi-ai\",\"date\":\"2025-11-14T18:24:08\",\"modifiedGmt\":\"2025-11-14T18:33:54\",\"title\":\"Run Product Analytics on Your Neon Data Using Fabi.ai\",\"excerpt\":\"\u003cp\u003eYou’re already using Neon, so chances are you’ve got valuable application data sitting in your Postgres database that reflects how people interact with your product. This data can tell you a lot about your customers and help guide product decisions, whether you’re an engineer, a founder, or a product manager. In this post (and the [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/neon-fabi-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Marc Dupuis\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/marc-dupuis.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Community\",\"slug\":\"community\"}]}},{\"title\":\"Data masking, Read-Only mode for MCP Server, branch auto-deletion, and more\",\"slug\":\"2025-11-14\",\"category\":\"changelog\",\"date\":\"2025-11-14\",\"content\":\"$13c\",\"isDraft\":\"$undefined\",\"redirectFrom\":\"$undefined\"},{\"title\":\"Building resilient applications with Postgres\",\"subtitle\":\"Learn best practices for building applications that gracefully handle brief connection drops with Managed Postgres services\",\"slug\":\"building-resilient-applications-with-postgres\",\"category\":\"guides\",\"author\":{\"name\":\"Dhanush Reddy\",\"position\":\"Software Engineer\",\"link\":{\"title\":\"GitHub\",\"url\":\"https://github.com/dhanushreddy291\"},\"photo\":\"/guides/authors/dhanush-reddy.jpg\"},\"createdAt\":\"2025-11-13T00:00:00.000Z\",\"updatedOn\":\"2025-11n-13T00:00:00.000Z\",\"date\":\"2025-11-13T00:00:00.000Z\",\"excerpt\":\"Building resilient applications is essential when working with managed database services, where brief connection drops though rare can occur. While this guide uses Neon as an example, these best pract...\",\"isDraft\":\"$undefined\",\"redirectFrom\":\"$undefined\"},{\"slug\":\"building-versioning-for-ai-generated-apps\",\"date\":\"2025-11-12T16:43:33\",\"modifiedGmt\":\"2026-01-02T17:40:17\",\"title\":\"Building Versioning for AI-Generated Apps\",\"excerpt\":\"\u003cp\u003eFor anyone building apps with AI, iteration is constant: you try different prompts, tweak the logic, and regenerate code until it finally works. At Dyad, a free, local, open-source AI app builder, this cycle is part of every user’s experience. From the start, Dyad made it easy to roll back code changes when something broke, [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/neon-building-versioning-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Will Chen\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/will-chen.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"App Platform\",\"slug\":\"app-platform\"},{\"name\":\"Community\",\"slug\":\"community\"},{\"name\":\"AI\",\"slug\":\"ai\"}]}},{\"slug\":\"branching-environments-anonymized-pii\",\"date\":\"2025-11-11T17:18:38\",\"modifiedGmt\":\"2025-11-11T17:22:47\",\"title\":\"Branching With or Without PII: The Future of Environments\",\"excerpt\":\"\u003cp\u003eBranching lets developers spin up isolated environments that perfectly mirror production in a single click or API call. This is a major upgrade for developer experience: teams can skip the tedious work of keeping databases in sync and focus on shipping code. But until now, there’s been one limitation. If your production data includes sensitive [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/Screenshot-2025-11-10-at-10.25.16-AM.png\"},\"authors\":[{\"author\":{\"title\":\"Monica Steinke\",\"postAuthor\":{\"image\":{\"altText\":\"Monica Steinke\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/10/Monica-Steinke.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Product\",\"slug\":\"product\"},{\"name\":\"Workflows\",\"slug\":\"workflows\"}]}},{\"slug\":\"three-ways-to-use-your-snapshots\",\"date\":\"2025-11-11T00:54:40\",\"modifiedGmt\":\"2025-11-11T00:54:55\",\"title\":\"Three Ways to Use Your Snapshots\",\"excerpt\":\"\u003cp\u003eNeon’s snapshots feature is now available to all users (in Beta), and you can finally schedule them automatically. You can make snapshots daily, weekly, or monthly from the Backup \u0026amp; Restore page in the Neon Console. Snapshots are built on Neon’s copy-on-write architecture: they capture the exact state of your database at a point in [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/neon-3-ways-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Carlota Soto\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/02/carlota.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Product\",\"slug\":\"product\"},{\"name\":\"Workflows\",\"slug\":\"workflows\"}]}},{\"title\":\"Reduced compute pricing, more projects on Free plan, AI-powered onboarding\",\"slug\":\"2025-11-07\",\"category\":\"changelog\",\"date\":\"2025-11-07\",\"content\":\"$13d\",\"isDraft\":\"$undefined\",\"redirectFrom\":\"$undefined\"},{\"slug\":\"one-command-to-bridge-cursor-and-neon\",\"date\":\"2025-11-05T17:25:23\",\"modifiedGmt\":\"2025-11-28T21:34:53\",\"title\":\"One Command to Bridge Cursor and Neon\",\"excerpt\":\"\u003cp\u003eWe’ve built a new way to connect your app to Neon right from Cursor. You can now run a single command to set up your Neon project, configure the MCP server, and enable the Neon integration: With this one command, Cursor gains full Neon project context: connection details, schema, and best practices \u0026#8211; so you [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/neon-one-command-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Rodney Sherwin Shibu\",\"postAuthor\":{\"image\":{\"altText\":\"Rodney Sherwin Shibu\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/10/Rodney-Sherwin-Shibu.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"AI\",\"slug\":\"ai\"},{\"name\":\"Workflows\",\"slug\":\"workflows\"}]}},{\"slug\":\"the-hidden-ops-layer-of-agent-platforms\",\"date\":\"2025-11-04T18:48:25\",\"modifiedGmt\":\"2025-11-04T18:48:38\",\"title\":\"The Hidden Ops Layer of Agent Platforms\",\"excerpt\":\"\u003cp\u003eAgents aren’t just LLMs; they’re distributed systems that write and execute real code. The moment you give an AI the ability to run SQL migrations, you’ve entered the world of DevOps. You’ve probably seen plenty of full-stack agent demos at this point, starting with a prompt like “build me a task tracker,” and seconds later, [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/neon-hidden-layer.jpg\"},\"authors\":[{\"author\":{\"title\":\"Marcus Lowe\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/11/marcus-lowe.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Community\",\"slug\":\"community\"},{\"name\":\"AI\",\"slug\":\"ai\"}]}},{\"slug\":\"major-compute-price-reduction-on-neon\",\"date\":\"2025-11-03T19:23:07\",\"modifiedGmt\":\"2025-11-04T19:52:12\",\"title\":\"Major compute price reduction on Neon\",\"excerpt\":\"\u003cp\u003eDatabases are often one of the biggest infrastructure expenses for any company. From day one, Neon’s mission has been to make databases radically more efficient through separation of storage and compute, allowing instant autoscaling and better unit economics. Now, with Neon running on Databricks’ global infrastructure, we’ve taken another major step forward:\u0026nbsp;compute on Neon is [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":null,\"authors\":[{\"author\":{\"title\":\"Nikita Shamgunov\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2022/07/nikita-shamgunov-photo.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Company\",\"slug\":\"company\"}]}},{\"slug\":\"the-night-we-moved-our-ci\",\"date\":\"2025-10-31T16:32:42\",\"modifiedGmt\":\"2025-10-31T20:19:10\",\"title\":\"The Night We Moved Our CI\",\"excerpt\":\"\u003cp\u003eOnce upon a pipeline… It was a nice summer evening, and our CI lived happily in a familiar castle: Hetzner. Bare-metal towers gave us everything we needed, with cheap CPU and RAM per unit, free internal traffic, and huge local disks to hoard caches like dragons guard gold. Our workflows were built to feast on [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/10/neon-halloween.jpg\"},\"authors\":[{\"author\":{\"title\":\"Fedor Dikarev\",\"postAuthor\":{\"image\":{\"altText\":\"Fedor Dikarev\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/10/Fedor-Dikarev.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Engineering\",\"slug\":\"engineering\"}]}},{\"title\":\"Snapshots in Beta, Postgres 18 extensions, AI-ready prompts, and more\",\"slug\":\"2025-10-31\",\"category\":\"changelog\",\"date\":\"2025-10-31\",\"content\":\"$13e\",\"isDraft\":\"$undefined\",\"redirectFrom\":\"$undefined\"},{\"slug\":\"getting-started-with-claude-skills\",\"date\":\"2025-10-30T16:43:28\",\"modifiedGmt\":\"2025-10-30T16:59:44\",\"title\":\"Getting Started with Claude Skills\",\"excerpt\":\"\u003cp\u003eWhen Anthropic introduced Claude Skills, of course we tried it right away. This post walks through how we built, tested, and published our first set of Claude Skills for Neon, bundled into a plugin that includes four ready-to-use Skills and an MCP server integration. What’s a Claude Skill Anyway? Truth be told, there’s nothing particularly [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/10/neon-claude-skills-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Pedro Figueiredo\",\"postAuthor\":{\"image\":{\"altText\":\"Pedro Figueiredo\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/12/Pedro-Figueiredo-.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"AI\",\"slug\":\"ai\"}]}},{\"slug\":\"how-to-build-a-full-stack-ai-agent\",\"date\":\"2025-10-29T18:40:53\",\"modifiedGmt\":\"2025-10-29T18:46:52\",\"title\":\"How to Build a Full-Stack AI Agent\",\"excerpt\":\"\u003cp\u003eMore and more teams are using Neon to power vibe coding platforms, so we decided to build one too \u0026#8211; not as our billion-dollar-vibe-coding-startup-side-gig but as a public, open-source template you can use as a starting point to learn how to build codegen agents yourself. We called the agent Aileen, and all the code lives [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/10/neon-template.jpg\"},\"authors\":[{\"author\":{\"title\":\"Andre Landgraf\",\"postAuthor\":{\"image\":{\"altText\":\"Andre Landgraf\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/03/Andre-Landgraf.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"AI\",\"slug\":\"ai\"}]}},{\"slug\":\"neon-open-source-program\",\"date\":\"2025-10-28T18:03:36\",\"modifiedGmt\":\"2025-11-05T15:20:25\",\"title\":\"Neon is Sponsoring Open Source Projects\",\"excerpt\":\"\u003cp\u003eIf you’re building open-source tools powered by Postgres, we want to help you grow. The Neon Open Source Program provides up to $5,000 in Neon credits each year, additional real cash payouts through GitHub Sponsorships, and promotional support to help your work reach millions of developers. Why We’re Doing This Open source is stronger when [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"Neon Open Source Program\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/10/neon-open-source-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Taraneh Dohmer\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/11/photo-Taraneh-Dohmer.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Postgres\",\"slug\":\"postgres\"},{\"name\":\"Uncategorized\",\"slug\":\"uncategorized\"}]}},{\"slug\":\"deploy-agent-api-xpander\",\"date\":\"2025-10-27T16:13:17\",\"modifiedGmt\":\"2025-10-27T16:14:30\",\"title\":\"Under the hood of a deploy-agent API that works across any runtime environment\",\"excerpt\":\"\u003cp\u003eWhen we started building xpander.ai’s agent platform, one of our core promises to enterprise customers was freedom of deployment. Some wanted to run agents entirely inside xpander cloud, using our managed infrastructure. Others needed to host agents on their own Kubernetes clusters \u0026#8211; be it simply in a cloud VPC, private clouds, on-premise environments, edge [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/10/neon-one-deploy-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Ran Sheinberg\",\"postAuthor\":{\"image\":{\"altText\":\"Ran Sheinberg\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/10/Ran-Sheinberg.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Community\",\"slug\":\"community\"},{\"name\":\"AI\",\"slug\":\"ai\"}]}},{\"title\":\"AI tooling, default storage expansion, and Postgres updates\",\"slug\":\"2025-10-24\",\"category\":\"changelog\",\"date\":\"2025-10-24\",\"content\":\"$13f\",\"isDraft\":\"$undefined\",\"redirectFrom\":\"$undefined\"},{\"slug\":\"branching-as-the-environment-how-sharing-excess-ships-faster-on-neon\",\"date\":\"2025-10-23T17:49:17\",\"modifiedGmt\":\"2025-10-24T23:37:10\",\"title\":\"Branching as the Environment: How Sharing Excess Ships Faster on Neon\",\"excerpt\":\"\u003cp\u003e“For a small team, branching and scale-to-zero just make our lives markedly easier. We’re able to use real data without risky scripts touching production, and we don’t pay overnight for what we don\u0026#8217;t use.” — Ryan McHenry, Head of Technology, Sharing Excess What is Sharing Excess? In the United States, nearly 40% of food goes [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":null,\"largeCover\":{\"altText\":\"sharing excess case study\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/09/neon-sharing-excess-1.jpg\"},\"authors\":[{\"author\":{\"title\":\"Taraneh Dohmer\",\"postAuthor\":{\"image\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2024/11/photo-Taraneh-Dohmer.png\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Case Studies\",\"slug\":\"case-study\"}]}},{\"slug\":\"handling-time-variant-dags-with-constraints-in-postgres\",\"date\":\"2025-10-20T16:34:49\",\"modifiedGmt\":\"2025-10-20T17:11:33\",\"title\":\"Handling Time-Variant DAGs with Constraints in Postgres\",\"excerpt\":\"\u003cp\u003eManaging dynamically changing directed acyclic graphs (DAGs) with constraints in Postgres enables robust tracking of relationships that evolve over time. At traconiq, this pattern is central to how we manage our vehicle fleet, where trucks and trailers attach and detach constantly, and where data can come from multiple systems with different levels of authority. We [\u0026hellip;]\u003c/p\u003e\\n\",\"pageBlogPost\":{\"isFeatured\":true,\"largeCover\":{\"altText\":\"\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/10/neon-handling-time.jpg\"},\"authors\":[{\"author\":{\"title\":\"Thorsten Rieß\",\"postAuthor\":{\"image\":{\"altText\":\"Thorsten Rieß\",\"mediaItemUrl\":\"https://neondatabase.wpenginepowered.com/wp-content/uploads/2025/09/Thorsten-Ries.jpg\"}}}}]},\"categories\":{\"nodes\":[{\"name\":\"Postgres\",\"slug\":\"postgres\"} | 2026-01-13T08:48:04 |
https://topenddevs.com/podcasts/javascript-jabber/episodes/getting-to-know-bruce-a-tate-bonus | Getting to Know Bruce A. Tate - BONUS - JavaScript Jabber - Top End Devs Top End Devs Home Podcasts Screencasts Courses Blogs Summits Meetups search-modal#open" aria-label="Search"> Sign In Sign Up search-modal#close"> Search search-modal#close"> search-modal#search" data-turbo-frame="search-results" data-turbo="true" class="space-y-4" action="/search" method="get"> Content Type All Episodes Podcasts Screencasts Lessons Courses Blog Authors Meetups Use semantic search (recommended) Search Trending Now What’s New in React 19.2: Compiler, Activity, and the Future of Async React - JSJ 670 JavaScript Jabber Can You Really Trust AI-Generated Code? - JSJ 699 JavaScript Jabber Autogenetic AI Agents and the Future of Ruby Development - RUBY 682 Ruby Rogues Popular Searches search-modal#fillSearch" data-search-term="podcast"> Podcast search-modal#fillSearch" data-search-term="episode"> Episode search-modal#fillSearch" data-search-term="author"> Author search-modal#fillSearch" data-search-term="meetup"> Meetup search-modal#fillSearch" data-search-term="series"> Series Back to JavaScript Jabber RSS Feed Spotify Apple Podcasts YouTube Amazon Music Getting to Know Bruce A. Tate - BONUS Published: April 28, 2023 Download Getting to Know Bruce A. Tate - BONUS 0:00 audio-player#clickProgressBar touchstart->audio-player#clickProgressBar touchmove->audio-player#clickProgressBar" data-audio-player-target="progressBar"> 0:00 audio-player#skipBackward"> audio-player#togglePlayPause" data-audio-player-target="playPauseButton"> audio-player#skipForward"> audio-player#changeVolume" type="range" min="0" max="1" step="0.01" value="1" /> Playback Speed: audio-player#changePlaybackSpeed"> 0.5x 0.75x 1x 1.25x 1.5x 2x Created by: Charles Max Wood Show Notes Bruce A. Tate is a Founder at Groxio, Elixir Expert, and a Technical Author. He joins the show alongside Charles Max Wood to talk about his book, " Seven Languages in Seven Weeks" . He also delves into some of the preparations and anticipations that come with reading the book. On YouTube Getting to Know Bruce A. Tate - BONUS Links Seven Languages in Seven Weeks grox.io Socials LinkedIn: Bruce Tate Twitter: redrapids © 2026 2022 Intentional Excellence Productions, LLC. All rights reserved. | 2026-01-13T08:48:04 |
https://cssence.com/archive/ | Archive - CSSence.com The archive With the Big Table! Internal January 8, 2026 The table below shows how many blog posts have been written on CSSence.com over the years. Columns are split up into categories the posts belong to. Rows represent years (most recent first), and the years are links, so as an added bonus this page lets navigate to all the years this weblog has existed. Year Essays Editorials Events Extras Notes Links Total Articles Threads 2026 1 0 0 0 1 1 3 1 2 2025 2 2 1 7 5 11 28 12 16 2024 6 4 3 19 25 21 78 32 46 2023 0 2 0 5 0 0 7 7 0 2022 0 2 0 10 6 4 22 12 10 2021 2 0 1 2 3 4 12 5 7 2020 0 3 1 5 9 2 20 9 11 2019 1 1 2 2 3 1 10 6 4 2018 1 1 1 2 2 2 9 5 4 2017 2 2 0 1 2 3 10 5 5 2016 3 1 3 3 10 4 24 10 14 2015 3 1 1 3 11 10 29 8 21 2014 0 0 2 0 3 2 7 2 5 2013 0 0 3 0 0 7 10 3 7 2012 0 1 1 0 1 6 9 2 7 2011 7 0 0 0 4 14 25 7 18 2010 0 0 0 0 0 2 2 0 2 All 28 20 19 59 85 94 305 126 179 126 articles and 179 threads make a total of 305 blog posts, but this site needs indexes and other pages too. Currently the whole site has 361 pages altogether, and additionally 28 RSS feeds. About this page Written by Matthias Zöchling. Last revised on January 8, 2026 . Permalink: https://cssence.com/archive/ 01 Home 02 Articles 03 Threads 04 About 05 Latest 06 Popular 07 Series 08 Archive © 2010–2026 Matthias Zöchling Imprint Webrings Elsewhere Menu Settings RSS feeds Back to top | 2026-01-13T08:48:04 |
https://cssence.com/webrings/ | Webrings - CSSence.com Webrings Internal July 24, 2024 This site has joined the following webrings. A webring (or web ring) is a collection of websites linked together in a circular structure, and usually organized around a specific theme, often educational or social. — Webring, Wikipedia a11y-webring.club CSSence.com is a member of a11y-webring.club . Previous website Random website Next website CSS Joy CSSence.com is a member of cs.sjoy.lol . Previous website Random website Next website About this page Written by Matthias Zöchling. Last revised on July 24, 2024 . Permalink: https://cssence.com/webrings/ 01 Home 02 Articles 03 Threads 04 About 05 Latest 06 Popular 07 Series 08 Archive © 2010–2026 Matthias Zöchling Imprint Webrings Elsewhere Menu Settings RSS feeds Back to top | 2026-01-13T08:48:04 |
http://connectrpc.com/ | Connect Skip to main content Docs GitHub Slack Demo Search Created by Simple, reliable, interoperable. Protobuf RPC that works. Connect is a family of libraries for building browser and gRPC-compatible APIs. If you're tired of hand-written boilerplate and turned off by massive frameworks, Connect is for you. Use it with Curl Supports any HTTP client Plain HTTP $ curl \ --header 'Content-Type: application/json' \ --data '{"sentence": "I feel happy."}' \ https://demo.connectrpc.com/connectrpc.eliza.v1.ElizaService/Say {"sentence": "Feeling happy? Tell me more."} Copy Use it with gRPCurl Supports any gRPC client gRPC protocol $ grpcurl \ -d '{"sentence": "I feel happy."}' \ demo.connectrpc.com:443 \ connectrpc.eliza.v1.ElizaService/Say {"sentence": "Feeling happy? Tell me more."} Copy Use it in web browsers Supports React, Angular, Svelte, and other frameworks Connect-Web Meet Eliza, our psychotherapist Eliza: Hello, how are you feeling? Production-grade simplicity Connect shines in production. Implementations are focused — a few thousand lines of code, a handful of essential options, and a cURL-friendly protocol — which makes them stable, predictable, and debuggable. Compatible with gRPC In addition to its own protocol, Connect servers and backend clients also support gRPC — including streaming! They interoperate seamlessly with Envoy, grpcurl, gRPC Gateway, and every other gRPC implementation. Connect servers handle gRPC-Web requests natively, without a translating proxy. Familiar primitives Connect builds on primitives you already know. Go handlers slot right into your net/http server and work with your existing middleware, router, and observability. TypeScript clients stay close to the fetch API and integrate cleanly with popular UI frameworks. No boilerplate Define your APIs using Protocol Buffers , the industry's most battle-tested schema definition language, and skip the hand-written boilerplate. Connect handles server-side routing, serialization, and compression, and it generates idiomatic clients in Go, TypeScript, Swift, and Kotlin. Learn more Go guide Servers and clients Go to guide → Node.js guide Servers and clients Go to guide → Web guide Connect on the Web Go to guide → iOS guide Swift clients available Go to guide → Android guide Kotlin clients available Go to guide → Flutter guide Dart clients available Go to guide → Simple, reliable, Protobuf-powered APIs Learn more Terms Privacy Trademarks License Copyright © 2022–2026 The Connect Authors We are a Cloud Native Computing Foundation sandbox project | 2026-01-13T08:48:04 |
https://dev.to/sloan/series/22731 | Sloan's Inbox Series' Articles - 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 Sloan's Inbox Series' Articles Back to Sloan the DEV Moderator's Series Sloan's Inbox: Staying Positive Amidst Industry Drama Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Apr 27 '23 Sloan's Inbox: Staying Positive Amidst Industry Drama # discuss 32 reactions Comments 20 comments 1 min read Sloan's Inbox: Surviving A Job Performance Plan: Is There Hope? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team May 3 '23 Sloan's Inbox: Surviving A Job Performance Plan: Is There Hope? # discuss 17 reactions Comments 7 comments 1 min read Sloan's Inbox: How Do Badges Work on DEV? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team May 10 '23 Sloan's Inbox: How Do Badges Work on DEV? # discuss # meta 22 reactions Comments Add Comment 2 min read Sloan's Inbox: Newbie Seeking Guidance on Real-life Project Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team May 11 '23 Sloan's Inbox: Newbie Seeking Guidance on Real-life Project # discuss # career 9 reactions Comments 4 comments 1 min read Sloan's Inbox: Navigating Career Confusion in ICT Domain Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team May 18 '23 Sloan's Inbox: Navigating Career Confusion in ICT Domain # discuss # career # ict 9 reactions Comments 1 comment 1 min read Sloan's Inbox: What's Your Advice on Where to Start and How to Study in the World of Coding? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team May 19 '23 Sloan's Inbox: What's Your Advice on Where to Start and How to Study in the World of Coding? # discuss # beginners # learning 11 reactions Comments 2 comments 1 min read Sloan's Inbox: How Do You Balance Values and Professional Work? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team May 25 '23 Sloan's Inbox: How Do You Balance Values and Professional Work? # discuss # career 5 reactions Comments 3 comments 1 min read Sloan's Inbox: How to Approach Your Manager When Interviewing for a New Job? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Jun 1 '23 Sloan's Inbox: How to Approach Your Manager When Interviewing for a New Job? # discuss # career 6 reactions Comments 2 comments 1 min read Sloan's Inbox: What Skills Do I Need to Land a Jr. Position? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Jun 8 '23 Sloan's Inbox: What Skills Do I Need to Land a Jr. Position? # discuss # career 12 reactions Comments 8 comments 1 min read Sloan's Inbox: What Are Your Favorite Tags, Orgs, and Coding Challenges? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Jun 15 '23 Sloan's Inbox: What Are Your Favorite Tags, Orgs, and Coding Challenges? # discuss # codenewbie # showdev # tutorial 10 reactions Comments Add Comment 1 min read Sloan's Inbox: How Do I Overcome Language Barriers in the Coding Community? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Jun 22 '23 Sloan's Inbox: How Do I Overcome Language Barriers in the Coding Community? # discuss 10 reactions Comments Add Comment 1 min read Sloan's Inbox: What is the Secret to a Truly Great Portfolio? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Jun 29 '23 Sloan's Inbox: What is the Secret to a Truly Great Portfolio? # discuss # beginners # career # careerdevelopment 17 reactions Comments 2 comments 1 min read Sloan's Inbox: How Do You Find a Mentor That Is Right for You? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Jul 6 '23 Sloan's Inbox: How Do You Find a Mentor That Is Right for You? # discuss 14 reactions Comments 2 comments 1 min read Sloan's Inbox: What's it take to go from 0 dev skills to successful game developer? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Jul 13 '23 Sloan's Inbox: What's it take to go from 0 dev skills to successful game developer? # discuss # career # gamedev # beginners 22 reactions Comments 5 comments 1 min read Sloan's Inbox: Considering taking a coding sabbatical... Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Jul 20 '23 Sloan's Inbox: Considering taking a coding sabbatical... # discuss # career # burnout 17 reactions Comments 6 comments 1 min read Sloan's Inbox: Will working with legacy code hold me back? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Jul 27 '23 Sloan's Inbox: Will working with legacy code hold me back? # discuss # beginners # career # refactoring 10 reactions Comments 7 comments 1 min read Sloan's Inbox: Any advice on how to advocate for a11y improvements at my org? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Aug 3 '23 Sloan's Inbox: Any advice on how to advocate for a11y improvements at my org? # discuss # career # a11y 14 reactions Comments 8 comments 1 min read Sloan's Inbox: Applying for jobs with an inactive GitHub profile? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Aug 10 '23 Sloan's Inbox: Applying for jobs with an inactive GitHub profile? # discuss # career # beginners 11 reactions Comments 9 comments 1 min read Sloan's Inbox: Bored... Is it time to get another job? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Aug 17 '23 Sloan's Inbox: Bored... Is it time to get another job? # discuss # career 19 reactions Comments 18 comments 1 min read Sloan's Inbox: Any advice for estimating work? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Aug 24 '23 Sloan's Inbox: Any advice for estimating work? # discuss 7 reactions Comments 7 comments 1 min read Sloan's Inbox: Considering a role as a Dev Advocate, but worried about less coding & more marketing... Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Sep 7 '23 Sloan's Inbox: Considering a role as a Dev Advocate, but worried about less coding & more marketing... # discuss # devrel # career 10 reactions Comments 13 comments 2 min read Sloan's Inbox: Do I need to write blog posts to be a successful dev? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Sep 14 '23 Sloan's Inbox: Do I need to write blog posts to be a successful dev? # discuss 11 reactions Comments 15 comments 1 min read Sloan's Inbox: Striving to be a T-shaped developer... how to find my specialization? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Sep 21 '23 Sloan's Inbox: Striving to be a T-shaped developer... how to find my specialization? # discuss 2 reactions Comments 2 comments 1 min read Sloan's Inbox: How to connect with folks over Open Source? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Oct 5 '23 Sloan's Inbox: How to connect with folks over Open Source? # discuss # opensource # help # community 5 reactions Comments 6 comments 1 min read Sloan's Inbox: How to stand out as a beginner dev? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Oct 12 '23 Sloan's Inbox: How to stand out as a beginner dev? # discuss # codenewbie # beginner # help 9 reactions Comments 4 comments 1 min read Sloan's Inbox: How and when to choose a JavaScript Framework? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Oct 19 '23 Sloan's Inbox: How and when to choose a JavaScript Framework? # discuss # codenewbie # beginners # javascript 6 reactions Comments 3 comments 1 min read Sloan's Inbox: Considering a career change from coding to graphic design, any advice? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Oct 26 '23 Sloan's Inbox: Considering a career change from coding to graphic design, any advice? # discuss # career # design 4 reactions Comments 5 comments 1 min read Sloan's Inbox: Advice for a dev hobbyist that wants to get a career in software development? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Nov 2 '23 Sloan's Inbox: Advice for a dev hobbyist that wants to get a career in software development? # discuss # career # raspberrypi 8 reactions Comments 8 comments 1 min read Sloan's Inbox: Struggling to focus, any advice? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Nov 9 '23 Sloan's Inbox: Struggling to focus, any advice? # discuss # productivity # career 1 reaction Comments 4 comments 1 min read Sloan's Inbox: How do you find a mentor? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Nov 16 '23 Sloan's Inbox: How do you find a mentor? # discuss # beginners # mentor 9 reactions Comments 3 comments 1 min read Sloan's Inbox: What strategies are most effective for retaining acquired knowledge? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Nov 30 '23 Sloan's Inbox: What strategies are most effective for retaining acquired knowledge? # discuss # learning # productivity # beginners 6 reactions Comments 6 comments 1 min read Sloan's Inbox: How did open source come to be? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Dec 7 '23 Sloan's Inbox: How did open source come to be? # discuss # learning # opensource 6 reactions Comments 2 comments 2 min read Sloan's Inbox: What's the hardest thing about being a developer? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Dec 14 '23 Sloan's Inbox: What's the hardest thing about being a developer? # discuss # learning # opensource 11 reactions Comments 8 comments 1 min read Sloan's Inbox: Any job-hunting advice for a newbie? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Dec 21 '23 Sloan's Inbox: Any job-hunting advice for a newbie? # discuss # career # beginners # codenewbie 6 reactions Comments 5 comments 1 min read Sloan's Inbox: Feeling like I'm not doing enough... Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Dec 28 '23 Sloan's Inbox: Feeling like I'm not doing enough... # discuss # learning # opensource 2 reactions Comments 4 comments 1 min read Sloan's Inbox: Is it realistic for someone's first developer job to be in game dev? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Jan 4 '24 Sloan's Inbox: Is it realistic for someone's first developer job to be in game dev? # discuss # gamedev # career 15 reactions Comments 13 comments 1 min read Sloan's Inbox: How do you improve focus? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Jan 11 '24 Sloan's Inbox: How do you improve focus? # discuss # productivity # career 17 reactions Comments 8 comments 1 min read Sloan's Inbox: As a beginner, should I use AI as a tool and how? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Jan 18 '24 Sloan's Inbox: As a beginner, should I use AI as a tool and how? # discuss # beginners # ai 12 reactions Comments 11 comments 1 min read Sloan's Inbox: Any advice for overcoming a fear of public speaking? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Jan 25 '24 Sloan's Inbox: Any advice for overcoming a fear of public speaking? # discuss # speaking # conference # help 23 reactions Comments 10 comments 1 min read Sloan's Inbox: Going With Vanilla JS or Frameworks as a Beginner? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Feb 1 '24 Sloan's Inbox: Going With Vanilla JS or Frameworks as a Beginner? # discuss # javascript # beginners # help 11 reactions Comments 6 comments 1 min read Sloan's Inbox: Any advice for a web dev who is considering a career in cybersecurity? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Feb 8 '24 Sloan's Inbox: Any advice for a web dev who is considering a career in cybersecurity? # discuss # webdev # security # cybersecurity 7 reactions Comments 4 comments 1 min read Sloan's Inbox: How to ask for a raise? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Feb 15 '24 Sloan's Inbox: How to ask for a raise? # discuss # career 14 reactions Comments 7 comments 1 min read Sloan's Inbox: How would you approach designing an authentication system from scratch? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Feb 22 '24 Sloan's Inbox: How would you approach designing an authentication system from scratch? # discuss # authentication # help 15 reactions Comments 3 comments 1 min read Sloan's Inbox: Am I too old to get into tech? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Feb 29 '24 Sloan's Inbox: Am I too old to get into tech? # discuss # career 16 reactions Comments 6 comments 1 min read Sloan's Inbox: Did you face any unexpected challenges in your first dev job? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Mar 7 '24 Sloan's Inbox: Did you face any unexpected challenges in your first dev job? # discuss # career # beginners 6 reactions Comments 2 comments 1 min read Sloan's Inbox: How to answer "Where do you see yourself in 5 years?" when I'm content where I am. Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Mar 14 '24 Sloan's Inbox: How to answer "Where do you see yourself in 5 years?" when I'm content where I am. # discuss # career 5 reactions Comments 3 comments 2 min read Sloan's Inbox: Is security still an afterthought? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Mar 21 '24 Sloan's Inbox: Is security still an afterthought? # discuss # security # beginners 8 reactions Comments 7 comments 2 min read Sloan's Inbox: How do you ask for help? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Mar 28 '24 Sloan's Inbox: How do you ask for help? # discuss # career 7 reactions Comments 3 comments 1 min read Sloan's Inbox: Any advice for calming an opinionated contributor? 😬 Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Apr 4 '24 Sloan's Inbox: Any advice for calming an opinionated contributor? 😬 # discuss # opensource # maintainer 10 reactions Comments 4 comments 1 min read Sloan's Inbox: How important is understanding backend as a website designer? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Apr 11 '24 Sloan's Inbox: How important is understanding backend as a website designer? # discuss # career 7 reactions Comments 2 comments 2 min read Sloan's Inbox: Pursuing passion or practicality? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Apr 18 '24 Sloan's Inbox: Pursuing passion or practicality? # discuss # career # gamedev 10 reactions Comments 1 comment 2 min read Sloan's Inbox: How to Approach Beginners Writing On Worn-Out Topics? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team Apr 25 '24 Sloan's Inbox: How to Approach Beginners Writing On Worn-Out Topics? # discuss # beginners # writing 18 reactions Comments 12 comments 2 min read Sloan's Inbox: How Do I Achieve a Four-Day Work Week? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team May 2 '24 Sloan's Inbox: How Do I Achieve a Four-Day Work Week? # discuss # career 8 reactions Comments 1 comment 2 min read Sloan's Inbox: Will I Ever Feel Like I Know This Stuff? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team May 9 '24 Sloan's Inbox: Will I Ever Feel Like I Know This Stuff? # discuss # beginners # learning 9 reactions Comments 8 comments 1 min read Sloan's Inbox: Can I make a career off of WordPress? Should I? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team May 16 '24 Sloan's Inbox: Can I make a career off of WordPress? Should I? # discuss # wordpress # career 3 reactions Comments 7 comments 1 min read Sloan's Inbox: Any advice for avoiding burnout? Sloan the DEV Moderator Sloan the DEV Moderator Sloan the DEV Moderator Follow for The DEV Team May 23 '24 Sloan's Inbox: Any advice for avoiding burnout? # discuss # burnout # career 15 reactions Comments 9 comments 1 min read 💎 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:48:04 |
https://cursor.com/changelog | Changelog · Cursor Skip to content Cursor Features Enterprise Pricing Resources ↓ Changelog Blog Docs ↗ Community Learn ↗ Workshops Forum ↗ Careers Features Enterprise Pricing Resources → Sign in Download Changelog CLI Jan 8, 2026 New CLI Features and Improved CLI Performance This release introduces new CLI controls for models, MCP management, rules and commands, alongside major hooks performance improvements and bug fixes. # Model list and selection Use the new agent models command, --list-models flag, or /models slash command to list all available models and quickly switch between them. # Rules generation and management Create new rules and edit existing ones directly from the CLI with the /rules command. # Enabling MCP servers Enable and disable MCP servers on the fly with /mcp enable and /mcp disable commands. New Features (7) ↓ ↑ Hooks (3) ↓ ↑ Improvements & Bug Fixes (7) ↓ ↑ 2.3 Dec 22, 2025 Layout Customization and Stability Improvements For this holiday release, we've focused entirely on fixing bugs and improving stability. This includes the core agent, layout controls, viewing code diffs, and more. We will be slowly rolling these updates out over the week, ensuring there are no regressions during your holiday coding. # Stability improvements Stability (7) ↓ ↑ Agents (15) ↓ ↑ Layout controls (11) ↓ ↑ Code review (4) ↓ ↑ MCP (2) ↓ ↑ # Layout customization It's now easier to customize your default layout across workspaces. We've included four default layouts: agent, editor, zen, and browser. You can use Command (⌘) + Option (⌥) + Tab (⇥) to switch between layouts, or easily jump between different workspaces. Additionally, you can move backwards in this list by including Shift (⇧), similar to macOS. Dec 18, 2025 Enterprise Insights, Billing Groups, Service Accounts, and Improved Security Controls Many of the largest software companies in the world have adopted Cursor for Enterprise . Here are some of the new features we're releasing today: # Conversation insights Cursor can now analyze the code and context in each agent session to understand the type of work that is being done, including: Category: Bug fixes, refactoring, explanation Work Type: Maintenance, bug fixing, new features Complexity: Difficulty and specificity of prompts Enterprise customers can also extend these categories across their organization and teams. We protect your privacy by ensuring no PII or sensitive data is collected as part of these insights. # Shared agent transcripts You can now share agent conversations with your team. Generate a read-only transcript of any agent conversation to include in your PRs or internal documentation. Transcripts can be forked so others can start new agent conversations from the same context. # Billing groups Cursor now supports billing groups for fine-grained visibility into where usage occurs. Map usage and spend to the structure of your organization. Track spend by group, set budget alerts, and keep an eye on outliers. Understand which teams have the highest adoption of Cursor. # Linux sandboxing for agents Sandboxing for agents supports Linux in addition to macOS. This allows agents to work effectively within appropriate boundaries. Access is scoped to your workspace and can be configured to block unauthorized network and filesystem access. Learn more about LLM safety and controls . # Service accounts Service accounts are non-human accounts (and their API keys) that can configure Cursor, call APIs, and invoke cloud agents. With service accounts, teams can securely automate Cursor-powered workflows without tying integrations to individual developers' accounts. This makes it easier to manage access, rotate credentials, and keep automations running even as people and roles change. Service accounts will roll out to Enterprise accounts starting the week of 12/22. Learn more about Cursor for Enterprise and talk to our team to learn more. 2.2 Dec 10, 2025 Debug Mode, Plan Mode Improvements, Multi-Agent Judging, and Pinned Chats # Debug Mode Debug Mode helps you reproduce and fix the most tricky bugs. Cursor instruments your app with runtime logs to find the root cause. It works across stacks, languages, and models. Read more in our announcement . # Browser layout and style editor Design and code simultaneously with a brand new browser sidebar and component tree. Move elements, update colors, test layouts, and experiment with CSS in real time, then instantly apply changes to your codebase using agent. You can also click on multiple elements and describe changes in text to kick off an agent to make visual changes. Read more in our announcement . # Plan Mode improvements Plan Mode now supports inline Mermaid diagrams, allowing the agent to automatically generate and stream visuals into your plans. You also have more control over how you build them, with the option to send selected to-dos to new agents. # Multi-agent judging When running multiple agents in parallel, Cursor will now automatically evaluate all runs and give a recommendation for the best solution. The selected agent will have a comment explaining why it was picked. Judging of the best solution only happens after all parallel agents have finished. # Pinned chats In the agent sidebar, pin chats at the top for future reference. Improvements (10) ↓ ↑ 2.1 Nov 21, 2025 Improved Plan Mode, AI Code Review in Editor, and Instant Grep # Improved Plan Mode When creating plans, Cursor responds with clarifying questions to improve the plan quality. Cursor now shows an interactive UI to easily answer questions. You can also ⌘+F to search inside generated plans. # AI Code Reviews You can now find and fix bugs directly in Cursor with AI code reviews. It will look at your changes and find issues which you can see in the sidepanel. This is in addition to Bugbot, which runs on your source control provider like GitHub (including Enterprise Server), GitLab, and more. # Instant Grep (Beta) All grep commands run by the agent are now instant. Instant grep is supported by all models in Cursor. It is also used when manually searching the codebase from the sidebar, including regexes and matching on word boundaries. This improvement is slowly rolling out to 2.1 users over the next week. Improvements (11) ↓ ↑ Enterprise (3) ↓ ↑ Integrations (4) ↓ ↑ Next → Older posts Product Features Enterprise Web Agents Bugbot CLI Pricing Resources Download Changelog Docs ↗ Learn ↗ Forum ↗ Status ↗ Company Careers Blog Community Workshops Students Brand Legal Terms of Service Privacy Policy Data Use Security Connect X ↗ LinkedIn ↗ YouTube ↗ © 2026 Cursor 🛡 SOC 2 Certified 🌐 English ↓ English ✓ 简体中文 日本語 繁體中文 Skip to content Cursor Features Enterprise Pricing Resources ↓ Changelog Blog Docs ↗ Community Learn ↗ Workshops Forum ↗ Careers Features Enterprise Pricing Resources → Sign in Download Changelog CLI Jan 8, 2026 New CLI Features and Improved CLI Performance This release introduces new CLI controls for models, MCP management, rules and commands, alongside major hooks performance improvements and bug fixes. # Model list and selection Use the new agent models command, --list-models flag, or /models slash command to list all available models and quickly switch between them. # Rules generation and management Create new rules and edit existing ones directly from the CLI with the /rules command. # Enabling MCP servers Enable and disable MCP servers on the fly with /mcp enable and /mcp disable commands. New Features (7) ↓ ↑ Hooks (3) ↓ ↑ Improvements & Bug Fixes (7) ↓ ↑ 2.3 Dec 22, 2025 Layout Customization and Stability Improvements For this holiday release, we've focused entirely on fixing bugs and improving stability. This includes the core agent, layout controls, viewing code diffs, and more. We will be slowly rolling these updates out over the week, ensuring there are no regressions during your holiday coding. # Stability improvements Stability (7) ↓ ↑ Agents (15) ↓ ↑ Layout controls (11) ↓ ↑ Code review (4) ↓ ↑ MCP (2) ↓ ↑ # Layout customization It's now easier to customize your default layout across workspaces. We've included four default layouts: agent, editor, zen, and browser. You can use Command (⌘) + Option (⌥) + Tab (⇥) to switch between layouts, or easily jump between different workspaces. Additionally, you can move backwards in this list by including Shift (⇧), similar to macOS. Dec 18, 2025 Enterprise Insights, Billing Groups, Service Accounts, and Improved Security Controls Many of the largest software companies in the world have adopted Cursor for Enterprise . Here are some of the new features we're releasing today: # Conversation insights Cursor can now analyze the code and context in each agent session to understand the type of work that is being done, including: Category: Bug fixes, refactoring, explanation Work Type: Maintenance, bug fixing, new features Complexity: Difficulty and specificity of prompts Enterprise customers can also extend these categories across their organization and teams. We protect your privacy by ensuring no PII or sensitive data is collected as part of these insights. # Shared agent transcripts You can now share agent conversations with your team. Generate a read-only transcript of any agent conversation to include in your PRs or internal documentation. Transcripts can be forked so others can start new agent conversations from the same context. # Billing groups Cursor now supports billing groups for fine-grained visibility into where usage occurs. Map usage and spend to the structure of your organization. Track spend by group, set budget alerts, and keep an eye on outliers. Understand which teams have the highest adoption of Cursor. # Linux sandboxing for agents Sandboxing for agents supports Linux in addition to macOS. This allows agents to work effectively within appropriate boundaries. Access is scoped to your workspace and can be configured to block unauthorized network and filesystem access. Learn more about LLM safety and controls . # Service accounts Service accounts are non-human accounts (and their API keys) that can configure Cursor, call APIs, and invoke cloud agents. With service accounts, teams can securely automate Cursor-powered workflows without tying integrations to individual developers' accounts. This makes it easier to manage access, rotate credentials, and keep automations running even as people and roles change. Service accounts will roll out to Enterprise accounts starting the week of 12/22. Learn more about Cursor for Enterprise and talk to our team to learn more. 2.2 Dec 10, 2025 Debug Mode, Plan Mode Improvements, Multi-Agent Judging, and Pinned Chats # Debug Mode Debug Mode helps you reproduce and fix the most tricky bugs. Cursor instruments your app with runtime logs to find the root cause. It works across stacks, languages, and models. Read more in our announcement . # Browser layout and style editor Design and code simultaneously with a brand new browser sidebar and component tree. Move elements, update colors, test layouts, and experiment with CSS in real time, then instantly apply changes to your codebase using agent. You can also click on multiple elements and describe changes in text to kick off an agent to make visual changes. Read more in our announcement . # Plan Mode improvements Plan Mode now supports inline Mermaid diagrams, allowing the agent to automatically generate and stream visuals into your plans. You also have more control over how you build them, with the option to send selected to-dos to new agents. # Multi-agent judging When running multiple agents in parallel, Cursor will now automatically evaluate all runs and give a recommendation for the best solution. The selected agent will have a comment explaining why it was picked. Judging of the best solution only happens after all parallel agents have finished. # Pinned chats In the agent sidebar, pin chats at the top for future reference. Improvements (10) ↓ ↑ 2.1 Nov 21, 2025 Improved Plan Mode, AI Code Review in Editor, and Instant Grep # Improved Plan Mode When creating plans, Cursor responds with clarifying questions to improve the plan quality. Cursor now shows an interactive UI to easily answer questions. You can also ⌘+F to search inside generated plans. # AI Code Reviews You can now find and fix bugs directly in Cursor with AI code reviews. It will look at your changes and find issues which you can see in the sidepanel. This is in addition to Bugbot, which runs on your source control provider like GitHub (including Enterprise Server), GitLab, and more. # Instant Grep (Beta) All grep commands run by the agent are now instant. Instant grep is supported by all models in Cursor. It is also used when manually searching the codebase from the sidebar, including regexes and matching on word boundaries. This improvement is slowly rolling out to 2.1 users over the next week. Improvements (11) ↓ ↑ Enterprise (3) ↓ ↑ Integrations (4) ↓ ↑ Next → Older posts Product Features Enterprise Web Agents Bugbot CLI Pricing Resources Download Changelog Docs ↗ Learn ↗ Forum ↗ Status ↗ Company Careers Blog Community Workshops Students Brand Legal Terms of Service Privacy Policy Data Use Security Connect X ↗ LinkedIn ↗ YouTube ↗ © 2026 Cursor 🛡 SOC 2 Certified 🌐 English ↓ English ✓ 简体中文 日本語 繁體中文 | 2026-01-13T08:48:04 |
https://www.linkedin.com/company/ruul/posts/?feedView=all | 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:48:04 |
https://spdx.org/licenses/GPL-3.0-only.html | GNU General Public License v3.0 only | Software Package Data Exchange (SPDX) Linux Foundation Collaborative Projects Software Package Data Exchange (SPDX) Home » Licenses GNU General Public License v3.0 only false Full name GNU General Public License v3.0 only Short identifier GPL-3.0-only Other web pages for this license https://www.gnu.org/licenses/gpl-3.0-standalone.html [no longer live] https://opensource.org/licenses/GPL-3.0 [no longer live] true Notes This license was released: 29 June 2007. This license identifier refers to the choice to use the code under GPL-3.0-only, as distinguished from the use of code under GPL-3.0-or-later (i.e., GPL-3.0 or some later version). The license notice (as seen in the Standard License Header field below) states which of these applies to the code in the file. The example in the How to Apply These Terms appendix of the license shows the "or later" approach. Text Text in italicized blue is omittable (see Matching Guidelines B.3.5 ). License or exception text will match to the text for the specified identifier if it either includes or excludes this omittable text. Text in red is replaceable (see Matching Guidelines B.3.4 ). License or exception text will match to the text for the specified identifier if it includes a permitted variant of this replaceable text. The permitted variants can be found in the corresponding regular expression as shown in title text visible by hovering over the red text. GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright © 2007 Free Software Foundation, Inc. <https://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU General Public License is a free, copyleft license for software and other kinds of works. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <https://www.gnu.org/licenses/>. Also add information on how to contact you by electronic and paper mail. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: <program> Copyright (C) <year> <name of author> This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <https://www.gnu.org/licenses/>. The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <https://www.gnu.org/ licenses /why-not-lgpl.html>. Standard License Header Copyright (C) <year> <name of author> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, version 3. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <https://www.gnu.org/licenses/>. <<beginOptional>>GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 <<endOptional>> Copyright © 2007 Free Software Foundation, Inc. <https://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU General Public License is a free, copyleft license for software and other kinds of works. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS <<var;name="bullet";original="0.";match=".{0,20}">> Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. <<var;name="bullet";original="1.";match=".{0,20}">> Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. <<var;name="bullet";original="2.";match=".{0,20}">> Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. <<var;name="bullet";original="3.";match=".{0,20}">> Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. <<var;name="bullet";original="4.";match=".{0,20}">> Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. <<var;name="bullet";original="5.";match=".{0,20}">> Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: <<var;name="bullet";original="a)";match=".{0,20}">> The work must carry prominent notices stating that you modified it, and giving a relevant date. <<var;name="bullet";original="b)";match=".{0,20}">> The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". <<var;name="bullet";original="c)";match=".{0,20}">> You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. <<var;name="bullet";original="d)";match=".{0,20}">> If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if t | 2026-01-13T08:48:04 |
https://ruul.io/tax-compliance | Ruul | Sell Services & Digital Products | Get Paid as a Freelancer Product Payment Requests Get paid anywhere. Sell Services Make your services buyable Sell Products Create once sell forever Subscriptions Get paid on repeat Ruul Space Your personel storefront. One link for everything you offer. Learn more Pricing Resources Partner Programs Referral Program Get 1% for life. Seriously. Affiliate Program Bring users, get paid Partners Let’s grow together. More Blog About us Support Brand Kit For Customers Log in Sign up For Businesses Login Sign up Merchant of Record for Independents INDEPENDENT’S PAY BUTTON Sell anything. Get paid anywhere. Great for freelancers, creators, and indie sellers. ruul.space/ Thank you! Your submission has been received! Oops! Something went wrong while submitting the form. Trustpilot Trustpilot Trusted by thousands of teams RUUL FOR INDEPENDENCE You chose independence.We make sure you keep it. Sell your time, your talent, whatever you create or build always on your terms. Get started See Example Payment Requests Sell Services Sell Products Subscriptions Get paid for your freelance services. Send professional payment requests and get paid fast. Billing, compliance, and payments, all in one. Get started Learn more Sell services like ordering food. List your services, share your link, and get paid—no back-and-forth, no hassle. Get started Learn more Create once, sell forever. Made something great? Sell it again and again. Drop a link or use your store—it’s all set up for you. Get started Learn more Get paid like Netflix. On repeat. No chasing. No awkward follow-ups. Get paid on a schedule with subscription payments. Get started Learn more PAYMENT REQUESTS Get paid for your freelance services. Send professional payment requests and get paid fast. Billing, compliance, and payments, all in one. Get started Learn more SELL SERVICES Sell services like ordering food. List your services, share your link, and get paid—no back-and-forth, no hassle. Get started Learn more SELL PRODUCTS Create once, sell forever. Made something great? Sell it again and again. Drop a link or use your store—it’s all set up for you. Get started Learn more SUBSCRIPTIONS Get paid like Netflix. On repeat. No chasing. No awkward follow-ups. Get paid on a schedule with subscription payments. Get started Learn more RUUL SPACE YOUR SPACE, BUILT TO SELL Sell what you do. Show what you’ve made. Ruul Space is your personal storefront for sales, bio, and payments. Learn more @coffeeandpixels @milesbecker @videovibes @productgeek @coffeeandpixels @brandwizard @videovibes @milesbecker Meet the independents. Designers, developers, marketers, creators building, creating, and delivering with passion. Get started WHY RUUL The little things that make a big difference. Get started Checkout Links No storefront? No problem. Share a direct link to sell or get paid. Connected Wallets Connect your favorite digital wallets and manage payouts your way. Stablecoin Payouts Get paid in crypto using stablecoins, with fast and flexible payouts. Human Support Real people, real help. Get 5-star customer support that actually solves things. Secure Payments Every transaction is safe, smooth, and built with business-grade security. MORE THAN 120,000 Independents Over 120,000 independents trust Ruul to sell their services, digital products, and securely manage their payments. FROM 190 Countries Truly global coverage: trusted across 190 countries with seamless payouts available in 140 currencies. PROCESSED $200m+ of Transactions Over $200M successfully processed, backed by an 8-year legacy of secure, reliable transactions trusted by independents worldwide. FREQUENTLY ASKED QUESTIONS Everything you need to know. Get clear, straightforward answers to the most common questions about using Ruul. hey@ruul.io What is Ruul? Ruul is a merchant-of-record platform helping freelancers and creators globally sell services, digital products, subscriptions, and easily get paid. Who is Ruul for? Ruul is designed for freelancers, creators, and independent professionals who want a simple way to sell online and get paid globally. How does Ruul work? Open an account, complete a quick verification (KYC), and link your payout account. Then, start selling through your store or send payment requests to customers instantly. How does pricing work? Signing up is free. There are no subscription or hidden fees. Ruul charges a small commission only when you sell or get paid through the platform. What is a Merchant of Record? A merchant of record is the legal seller responsible for processing payments, handling taxes, and managing compliance for each transaction. What can I sell on Ruul? You can sell services, digital products, license keys, online courses, subscriptions, and digital memberships. How do I get paid on Ruul? Add your preferred bank account, digital wallet, or receive payouts in stablecoins as crypto. Funds arrive within 24 hours after a payout is triggered. OPEN AN ACCOUNT START MAKING MONEY TODAY ruul.space/ Thank you! Your submission has been received! Oops! Something went wrong while submitting the form. Trustpilot How to Sell Subscriptions Turn your services into steady monthly revenue: learn the best subscription models, smart pricing, and retention tactics that keep customers paying. Read more Best Portfolio Platforms for Freelancers in 2025 Discover the best portfolio building platforms for solo talents and freelancers to showcase their work and impress potential clients. Explore WP.ruul.io's expert recommendations and find the perfect platform to create a stunning portfolio that stands out. Read more What is an Invoice? Discover Everything You Need to Know About Invoices Discover the essentials of invoicing in our detailed guide. Learn what an invoice is, its importance, key elements, historical evolution, and tips for effective invoicing. Simplify your financial transactions and improve cash flow with Ruul's Invoice Generator. Read more Product Payment Requests Sell Services Sell Products Subscriptions Ruul Space Pricing For Businesses Resources Blog About Contact Support Referral Program Affiliate Program Partner Program Tools Invoice Generator NDA Generator Service Agreement Generator Freelancer Hourly Rate Calculator All Rights Reserved © 2025 Terms Of Use Privacy Policy | 2026-01-13T08:48:04 |
https://github.com/suprsend/suprsend-flutter-sdk/blob/main/example/lib/main.dart | suprsend-flutter-sdk/example/lib/main.dart at main · suprsend/suprsend-flutter-sdk · GitHub Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} suprsend / suprsend-flutter-sdk Public Notifications You must be signed in to change notification settings Fork 3 Star 10 Code Issues 0 Pull requests 1 Actions Projects 0 Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Projects Security Insights Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:48:04 |
https://music.forem.com/t/classical | Classical - Music 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 Music Forem Close # classical Follow Hide orchestras & precise scores Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Why *Dhurandhar* Movie Songs Feel So Awesome 🎶 Prasoon Jadon Prasoon Jadon Prasoon Jadon Follow Jan 6 Why *Dhurandhar* Movie Songs Feel So Awesome 🎶 # indie # ambientmusic # digital # classical 3 reactions Comments Add Comment 2 min read When Music Sounds Like Sunrise: My Night with the Toronto Symphony Orchestra's Romeo & Juliet Adnan Obuz AI Strategy Consultant | Digital Transformation Expert Adnan Obuz AI Strategy Consultant | Digital Transformation Expert Adnan Obuz AI Strategy Consultant | Digital Transformation Expert Follow Nov 23 '25 When Music Sounds Like Sunrise: My Night with the Toronto Symphony Orchestra's Romeo & Juliet # classical # concerts # liveperformance 8 reactions Comments 1 comment 8 min read loading... trending guides/resources Why *Dhurandhar* Movie Songs Feel So Awesome 🎶 When Music Sounds Like Sunrise: My Night with the Toronto Symphony Orchestra's Romeo & Juliet 💎 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 Music Forem — From composing and gigging to gear, hot music takes, 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 . Music Forem © 2025 - 2026. We're a place dedicated to discussing all things music - composing, producing, performing, and all the fun and not-fun things in-between. Log in Create account | 2026-01-13T08:48:04 |
https://neon.tech/blog/soc2-type2 | Celebrating Milestones: SOC 2 Type 2 Compliance - Neon This 250+ engineer team replaced shared staging with isolated database branches for safer deploys Neon Product Database Autoscaling Automatic instance sizing Branching Faster Postgres workflows Bottomless storage With copy-on-write Instant restores Recover TBs in seconds Connection pooler Built-in with pgBouncer Ecosystem Neon API Manage infra, billing, quotas Auth Add authentication Data API PostgREST-compatible Instagres No-signup flow Migration guides Step-by-step What is Neon? Serverless Postgres, by Databricks Solutions Use cases Serverless Apps Autoscale with traffic Multi-TB Scale & restore instantly Database per Tenant Data isolation without overhead Platforms Offer Postgres to your users Dev/Test Production-like environments Agents Build full-stack AI agents For teams Startups Build with Neon Security Compliance & privacy Case studies Explore customer stories Docs Pricing Company Blog About us Careers Contact Discord 20.7k Log In Sign Up Company Dec 04, 2023 Celebrating Milestones: SOC 2 Type 2 Compliance Achieving SOC2 Type 2 We have some exciting news on the security front – this month, we’ve successfully passed the SOC 2 Type 2 audit, following closely on the heels of our Type 1 audit in June. This accomplishment underscores our commitment to staying at the forefront of security standards. This article details our path to achieving our successful SOC 2 certification (Trust Service Principles: Security & Confidentiality & Availability), provides insights into the process, and outlines our future plans. Understanding SOC 2 Compliance SOC 2, or Service Organization Control 2, is an AICPA-developed framework for ensuring data security, availability, processing integrity, confidentiality, and privacy. In our proactive security approach, we prioritize protecting systems against unauthorized access, ensuring data privacy, and safeguarding sensitive information. This commitment extends to demonstrating robust internal controls and assuring our clients of secure data handling practices. By incorporating industry best practices, we set benchmark standards for secure data management, reinforcing our dedication to maintaining the highest security standards. SOC 2 compliance is crucial for several reasons. It builds trust with clients, which is often required for partnerships, and demonstrates a strong dedication to data security. It also provides organizations with a competitive edge, highlighting their commitment to high-security standards. Furthermore, SOC 2 compliance ensures that a business adheres to relevant data privacy regulations and fulfills the necessary legal obligations. As a developer, being SOC2 compliant shows that Neon has put in place measures to secure the systems and your customers’ data. This means our development process, infrastructure, and system architecture have been evaluated thoroughly and tested with industry-recognized security and compliance standards. For those who use our services, SOC2 assures that their user data is hosted and managed within a secure environment. Neon follows strict protocols and protects sensitive customer data from unauthorized access while ensuring data integrity, confidentiality, and availability. Neon’s Journey to Compliance Our journey toward SOC2 compliance was a detailed and months-long process. We started by closely examining our existing security measures against SOC2 standards, fixing any issues we found. We then adjusted our internal rules to match SOC2 criteria, implementing stronger incident management, disaster recovery, vulnerability management, logging & monitoring, vendor management, risk assessment, and access controls. As we implemented these changes, we exceeded the requirements of SOC2, thereby enhancing Neon’s overall security. The journey concluded with an audit by a third-party audit firm, confirming Neon’s compliance with the highest standards. This process not only achieved compliance, but showcased our commitment to making Neon more secure. Explore our path to SOC2 Type 1 compliance by visiting our blog at: https://neon.tech/blog/soc2-type-1 Next Steps Looking ahead, in addition to maintaining our SOC2 compliance, we will be working toward ISO 27001 (security) and ISO 27701 (privacy) certifications in 2024. These internationally recognized standards showcase our commitment to top-tier information security and privacy management. Achieving these certifications not only builds trust with our clients but also demonstrates our dedication to meeting the highest global standards. Stay tuned for updates on our journey towards security excellence. Posted by Busra Demir Lead Security Engineer More articles Zero-ETL lakehouses for Postgres people George MacKerron Handling Auth in a Staging Environment Carlota Soto Reusable Prompts: The Future of Starter Templates Andre Landgraf Share: Subscribe to our changelog. No spam, guaranteed. Subscribe Share: More from Neon Postgres Jan 12, 2026 Zero-ETL lakehouses for Postgres people George MacKerron App Platform Jan 10, 2026 Handling Auth in a Staging Environment Carlota Soto AI Jan 08, 2026 Reusable Prompts: The Future of Starter Templates Andre Landgraf Neon A Databricks Company Neon status loading... Made in SF and the World Copyright Ⓒ 2022 – 2026 Neon, LLC Company About Blog Careers Contact Sales Partners Security Legal Privacy Policy Terms of Service DPA Subprocessors List Privacy Guide Cookie Policy Business Information Resources Docs Changelog Support Community Guides PostgreSQL Tutorial Startups Creators Social Discord GitHub x.com LinkedIn YouTube Compliance CCPA Compliant GDPR Compliant ISO 27001 Certified ISO 27701 Certified SOC 2 Certified HIPAA Compliant Compliance Guide Neon’s Sub Contractors Sensitive Data Terms Trust Center | 2026-01-13T08:48:04 |
https://boot.dev/ | Learn backend development the smart way | Boot.dev We're sorry but this app doesn't work properly without JavaScript enabled. Please enable it to continue. Sign In & Skip Demo → Learn backend development the smart way Welcome to the most captivating, finger-flying, addictive way to learn to code DEMO THE LEARNING PATH (it takes 2 minutes) Join 822,231 students from companies like Mediocrity doesn't cut it anymore The only way to become a great developer is to write a lot of code Avoid tutorial hell by writing a ton of code Stay motivated with a game-like curriculum Build portfolio projects to prove your skills Delve deeper into foundational concepts Learn flexibly online without interrupting your life For 1% the price of college to minimize your financial risk Meet Boots, your programming mentor An AI assistant that uses the socratic method to deepen your understanding, not hand out answers Help! I don't get why my code makes the player's health go up when she's hit by the sword. *Adjusts wizard hat thoughtfully* Ah, it looks like you used the wrong operator! Which one do you think will subtract from her health (instead of adding to it) in your take_damage function? Join 822,231 students learning modern backend skills Connect directly with them and others in our flourishing online community 33.7M lessons completed 208K courses completed 7.4B xp earned This is a very good start and intro to sql. Itll certainly teach the basics! Give it a go because yo... Read more (5/5) Jeff Burton Australia Learn SQL Very good intro to programming! It makes Python infinitely easier to approach. (5/5) Sultan Ahmed sthlm Learn to Code in Python Made me interested enough to buy this course! (4/5) Arwin Brahma Bhubaneswar, India Learn to Code in Python REAL GOOD (5/5) bruhjeshhh Bhubaneshwar, India Learn Go This is an excellent course to begin learning not only Python, but programming in general. With a ro... Read more (4/5) Robert Glass United States Learn to Code in Python I have barely coded in my life, some simple manipulation of VB macros is about it. This course made ... Read more (5/5) GiggleFizz Australia Learn to Code in Python I been a software developer for over 10 years and this helped me to improve in my career (5/5) gaston coria Rio Cuarto, Argentina Learn Go A RPG like gamification just does it for someone like me who's been gaming his entire life. This is ... Read more (4/5) kenneth ambrose India Learn to Code in Python The best intro to Python course I have taken. Understanding code has never been more critical and th... Read more (5/5) Gabriel Ritter United States Learn to Code in Python ← Prev Showing 1-9 of 3488 Next → DEMO THE LEARNING PATH (it takes 2 minutes) or view more reviews A proven path to a back-end career It takes most students about 12 months to complete the career path * Source Learn in-demand back-end technologies like Python, SQL, and Go Spend about 12 months if you're doing it part-time There's no risk, cancel anytime We don't tolerate unhappy students: ask for a refund within 30 days and it's yours Software developers in the US earn over $100,000 per year The following data is taken from the results of the 2024 Stack Overflow survey Backend Developer $170,000 Site Reliability Engineer $166,500 Cloud Engineer $165,000 AI Developer $160,000 Data Engineer $150,000 DevOps Specialist $145,000 Frontend Developer $135,000 Data Analyst $100,000 Some folks look at the job data and assume that front-end positions are the only option for new learners. On the contrary, there is big demand for backend and data-oriented positions! If you like working with data, logic, and servers, you might just enjoy the back-end, data-focused curriculum here on Boot.dev. And similar to the frontend, most data and backend positions don't require a specific degree from a university... but you do need to know your stuff! DEMO THE LEARNING PATH (it takes 2 minutes) Taught by the best Modern courses taught by engineers who worked at companies like Netflix, SourceGraph, and Reputation The Primeagen Lane Wagner TJ DeVries Sarah Schulte Learn Python 179 Lessons Learn Go 188 Lessons Learn JavaScript 122 Lessons Learn TypeScript 104 Lessons Learn Linux 66 Lessons Learn SQL 125 Lessons Learn Git 75 Lessons Learn Docker 43 Lessons Learn Kubernetes 66 Lessons Learn DSA 175 Lessons and many more... Frequently asked questions Got questions? We've got answers Can I sign up and try Boot.dev for free? Yes! It's free to create an account and start learning. You'll get all the immersive and interactive features for free for a few chapters. After that, if you still haven't paid for a membership, you'll be in read-only (content only) mode. Hasn't AI made learning to code obsolete? How long will it take to learn enough to be hired? Should I include Boot.dev projects in my resume and portfolio? What is Boot.dev? A bootcamp? An online school? What makes Boot.dev different? DEMO THE LEARNING PATH (it takes 2 minutes) Platform All Courses Training Grounds Code Challenges Backend Path (Python/Go) Backend Path (Python/TS) Leaderboard Playground Boot.dev on X/Twitter Boot.dev on YouTube Boot.dev on LinkedIn Boot.dev on Instagram Boot.dev on TikTok Backend Banter Podcast Languages Python Go (Golang) TypeScript JavaScript SQL Subjects Linux Kubernetes Git Docker RabbitMQ Data Structures & Algorithms Object-Oriented Programming Cryptography Support Contact Privacy Policy Terms of Service Pricing Pricing Plans Gift Codes Redeem Gift Team Plans Expense a Purchase Community Community Lore Blog Curriculum Roadmap Reviews © Boot.dev 2026 Do Not Share My Information | 2026-01-13T08:48:04 |
https://github.com/skills/write-javascript-actions | GitHub - skills/write-javascript-actions: Write your own GitHub JavaScript Action and automate customized tasks unique to your workflow. Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} skills / write-javascript-actions Public template Notifications You must be signed in to change notification settings Fork 97 Star 176 Write your own GitHub JavaScript Action and automate customized tasks unique to your workflow. License MIT license 176 stars 97 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 1 Pull requests 2 Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Security Insights skills/write-javascript-actions main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 77 Commits .github .github .gitignore .gitignore LICENSE LICENSE README.md README.md View all files Repository files navigation README Code of conduct Contributing MIT license Security Write JavaScript Actions Write your own GitHub JavaScript Action and automate customized tasks unique to your workflow. Welcome Write your own GitHub JavaScript Action and automate customized tasks unique to your workflow. Who is this for : Developers, GitHub users, users new to Git, students, managers, and for teams. What you'll learn : How to consume actions within a workflow file, create custom JavaScript based actions and publish your newly created action to the marketplace. Prerequisites : Before you start, you should be familiar with GitHub, GitHub Actions, and Continuous Integration with GitHub Actions. How long : This course takes about 1 to 2 hours to be completed. In this course, you will: Initialize a JavaScript project Configure an action Create a metadata file Create JavaScript files Add actions to workflow file Trigger action How to start this course Right-click Start course and open the link in a new tab. In the new tab, most of the prompts will automatically fill in for you. For owner, choose your personal account or an organization to host the repository. We recommend creating a public repository, as private repositories will use Actions minutes . Scroll down and click the Create repository button at the bottom of the form. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README. Get help: Post in our discussion board • Review the GitHub status page © 2023 GitHub • Code of Conduct • MIT License About Write your own GitHub JavaScript Action and automate customized tasks unique to your workflow. Topics skills-course Resources Readme License MIT license Code of conduct Code of conduct Contributing Contributing Security policy Security policy Uh oh! There was an error while loading. Please reload this page . Activity Custom properties Stars 176 stars Watchers 17 watching Forks 97 forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 20 + 6 contributors Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:48:04 |
https://github.com/skills/test-with-actions | GitHub - skills/test-with-actions: Create workflows that enable you to use Continuous Integration (CI) for your projects. Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} skills / test-with-actions Public template generated from skills/exercise-template Notifications You must be signed in to change notification settings Fork 179 Star 279 Create workflows that enable you to use Continuous Integration (CI) for your projects. License MIT license 279 stars 179 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 5 Pull requests 1 Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Security Insights skills/test-with-actions main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 75 Commits .github .github .gitignore .gitignore LICENSE LICENSE README.md README.md resume.md resume.md View all files Repository files navigation README Code of conduct Contributing MIT license Security Test with Actions Create workflows that enable you to use Continuous Integration (CI) for your projects. Welcome Continuous integration can help you stick to your team’s quality standards by running tests and reporting the results on GitHub. CI tools run builds and tests, triggered by commits. The results post back to GitHub in the pull request. The goal is fewer issues in main and faster feedback as you work. Who is this for : Developers, DevOps Engineers, new GitHub users, students, teams. What you'll learn : What continuous integration is, how to use GitHub Actions for CI, how to create a workflow that runs tests and produces test reports. What you'll build : We'll use remark-lint to check the consistency of Markdown files. Prerequisites : We assume you've completed Hello GitHub Actions first. How long : This course takes less than two hours to complete. In this course, you will: Add a test workflow Fix the test Upload a test report Add branch protections Merge your pull request How to start this course Right-click Start course and open the link in a new tab. In the new tab, most of the prompts will automatically fill in for you. For owner, choose your personal account or an organization to host the repository. We recommend creating a public repository, as private repositories will use Actions minutes . Scroll down and click the Create repository button at the bottom of the form. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README. Get help: Post in our discussion board • Review the GitHub status page © 2023 GitHub • Code of Conduct • MIT License About Create workflows that enable you to use Continuous Integration (CI) for your projects. Topics integration continuous-integration ci actions workflows skills-course Resources Readme License MIT license Code of conduct Code of conduct Contributing Contributing Security policy Security policy Uh oh! There was an error while loading. Please reload this page . Activity Custom properties Stars 279 stars Watchers 11 watching Forks 179 forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 15 Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:48:04 |
https://github.com/skills/introduction-to-github | GitHub - skills/introduction-to-github: Get started using GitHub in less than an hour. Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} skills / introduction-to-github Public template Notifications You must be signed in to change notification settings Fork 14.6k Star 9.9k Get started using GitHub in less than an hour. License MIT license 9.9k stars 14.6k forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 57 Pull requests 17 Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Security Insights skills/introduction-to-github main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 81 Commits .github .github images images .gitignore .gitignore LICENSE LICENSE README.md README.md View all files Repository files navigation README Code of conduct Contributing MIT license Security Introduction to GitHub Get started using GitHub in less than an hour. Welcome People use GitHub to build some of the most advanced technologies in the world. Whether you’re visualizing data or building a new game, there’s a whole community and set of tools on GitHub that can help you do it even better. GitHub Skills’ “Introduction to GitHub” course guides you through everything you need to start contributing in less than an hour. Who is this for : New developers, new GitHub users, and students. What you'll learn : We'll introduce repositories, branches, commits, and pull requests. What you'll build : We'll make a short Markdown file you can use as your profile README . Prerequisites : None. This course is a great introduction for your first day on GitHub. How long : This course takes less than one hour to complete. In this course, you will: Create a branch Commit a file Open a pull request Merge your pull request How to start this course Right-click Start course and open the link in a new tab. In the new tab, most of the prompts will automatically fill in for you. For owner, choose your personal account or an organization to host the repository. We recommend creating a public repository, as private repositories will use Actions minutes . Scroll down and click the Create repository button at the bottom of the form. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README. Get help: Post in our discussion board • Review the GitHub status page © 2024 GitHub • Code of Conduct • MIT License About Get started using GitHub in less than an hour. Topics git commits pull-requests branches skills-course Resources Readme License MIT license Code of conduct Code of conduct Contributing Contributing Security policy Security policy Uh oh! There was an error while loading. Please reload this page . Activity Custom properties Stars 9.9k stars Watchers 981 watching Forks 14.6k forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 17 + 3 contributors Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:48:04 |
https://www.githubstatus.com/ | GitHub Status GitHub Octicon logo Help Community Status GitHub.com Subscribe to Updates Subscribe x Get email notifications whenever GitHub creates , updates or resolves an incident. Email address: Enter OTP: Resend OTP in: seconds Didn't receive the OTP? Resend OTP By subscribing you agree to our Privacy Policy . This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Get text message notifications whenever GitHub creates or resolves an incident. Country code: Afghanistan (+93) Albania (+355) Algeria (+213) American Samoa (+1) Andorra (+376) Angola (+244) Anguilla (+1) Antigua and Barbuda (+1) Argentina (+54) Armenia (+374) Aruba (+297) Australia/Cocos/Christmas Island (+61) Austria (+43) Azerbaijan (+994) Bahamas (+1) Bahrain (+973) Bangladesh (+880) Barbados (+1) Belarus (+375) Belgium (+32) Belize (+501) Benin (+229) Bermuda (+1) Bolivia (+591) Bosnia and Herzegovina (+387) Botswana (+267) Brazil (+55) Brunei (+673) Bulgaria (+359) Burkina Faso (+226) Burundi (+257) Cambodia (+855) Cameroon (+237) Canada (+1) Cape Verde (+238) Cayman Islands (+1) Central Africa (+236) Chad (+235) Chile (+56) China (+86) Colombia (+57) Comoros (+269) Congo (+242) Congo, Dem Rep (+243) Costa Rica (+506) Croatia (+385) Cyprus (+357) Czech Republic (+420) Denmark (+45) Djibouti (+253) Dominica (+1) Dominican Republic (+1) Egypt (+20) El Salvador (+503) Equatorial Guinea (+240) Estonia (+372) Ethiopia (+251) Faroe Islands (+298) Fiji (+679) Finland/Aland Islands (+358) France (+33) French Guiana (+594) French Polynesia (+689) Gabon (+241) Gambia (+220) Georgia (+995) Germany (+49) Ghana (+233) Gibraltar (+350) Greece (+30) Greenland (+299) Grenada (+1) Guadeloupe (+590) Guam (+1) Guatemala (+502) Guinea (+224) Guyana (+592) Haiti (+509) Honduras (+504) Hong Kong (+852) Hungary (+36) Iceland (+354) India (+91) Indonesia (+62) Iraq (+964) Ireland (+353) Israel (+972) Italy (+39) Jamaica (+1) Japan (+81) Jordan (+962) Kenya (+254) Korea, Republic of (+82) Kosovo (+383) Kuwait (+965) Kyrgyzstan (+996) Laos (+856) Latvia (+371) Lebanon (+961) Lesotho (+266) Liberia (+231) Libya (+218) Liechtenstein (+423) Lithuania (+370) Luxembourg (+352) Macao (+853) Macedonia (+389) Madagascar (+261) Malawi (+265) Malaysia (+60) Maldives (+960) Mali (+223) Malta (+356) Martinique (+596) Mauritania (+222) Mauritius (+230) Mexico (+52) Monaco (+377) Mongolia (+976) Montenegro (+382) Montserrat (+1) Morocco/Western Sahara (+212) Mozambique (+258) Namibia (+264) Nepal (+977) Netherlands (+31) New Zealand (+64) Nicaragua (+505) Niger (+227) Nigeria (+234) Norway (+47) Oman (+968) Pakistan (+92) Palestinian Territory (+970) Panama (+507) Paraguay (+595) Peru (+51) Philippines (+63) Poland (+48) Portugal (+351) Puerto Rico (+1) Qatar (+974) Reunion/Mayotte (+262) Romania (+40) Russia/Kazakhstan (+7) Rwanda (+250) Samoa (+685) San Marino (+378) Saudi Arabia (+966) Senegal (+221) Serbia (+381) Seychelles (+248) Sierra Leone (+232) Singapore (+65) Slovakia (+421) Slovenia (+386) South Africa (+27) Spain (+34) Sri Lanka (+94) St Kitts and Nevis (+1) St Lucia (+1) St Vincent Grenadines (+1) Sudan (+249) Suriname (+597) Swaziland (+268) Sweden (+46) Switzerland (+41) Taiwan (+886) Tajikistan (+992) Tanzania (+255) Thailand (+66) Togo (+228) Tonga (+676) Trinidad and Tobago (+1) Tunisia (+216) Turkey (+90) Turks and Caicos Islands (+1) Uganda (+256) Ukraine (+380) United Arab Emirates (+971) United Kingdom (+44) United States (+1) Uruguay (+598) Uzbekistan (+998) Venezuela (+58) Vietnam (+84) Virgin Islands, British (+1) Virgin Islands, U.S. (+1) Yemen (+967) Zambia (+260) Zimbabwe (+263) Phone number: Change number Enter OTP: Resend OTP in: 30 seconds Didn't receive the OTP? Resend OTP Message and data rates may apply. By subscribing you agree to our Privacy Policy , the Atlassian Terms of Service , and the Atlassian Privacy Policy . This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Get incident updates and maintenance status messages in Slack. Subscribe via Slack By subscribing you acknowledge our Privacy Policy . In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy . Get webhook notifications whenever GitHub creates an incident, updates an incident, resolves an incident or changes a component status. Webhook URL: The URL we should send the webhooks to Email address: We'll send you email if your endpoint fails By subscribing you agree to our Privacy Policy . This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Follow @githubstatus or view our profile . Visit our support site . Get the Atom Feed or RSS Feed . All Systems Operational About This Site Check GitHub Enterprise Cloud status by region: - Australia: au.githubstatus.com - EU: eu.githubstatus.com - Japan: jp.githubstatus.com - US: us.githubstatus.com Git Operations ? Operational Webhooks ? Operational Visit www.githubstatus.com for more information Operational API Requests ? Operational Issues ? Operational Pull Requests ? Operational Actions ? Operational Packages ? Operational Pages ? Operational Codespaces ? Operational Copilot Operational Operational Degraded Performance Partial Outage Major Outage Maintenance Past Incidents Jan 13 , 2026 No incidents reported today. Jan 12 , 2026 Disruption with some GitHub services Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Jan 12 , 10:17 UTC Update - Actions jobs that use custom Linux images are failing to start. We've identified the underlying issue and are working on mitigation. Jan 12 , 10:09 UTC Update - Actions is experiencing degraded performance. We are continuing to investigate. Jan 12 , 10:06 UTC Investigating - We are investigating reports of impacted performance for some GitHub services. Jan 12 , 10:02 UTC Jan 11 , 2026 No incidents reported. Jan 10 , 2026 Disruption with some GitHub services Resolved - From January 5, 2026, 00:00 UTC to January 10, 2026, 02:30 UTC, customers using the AI Controls public preview feature experienced delays in viewing Copilot agent session data. Newly created sessions took progressively longer to appear, initially hours, then eventually exceeding 24 hours. Since the page displays only the most recent 24 hours of activity, once processing delays exceeded this threshold, no recent data was visible. Session data remained available in audit logs throughout the incident. Inefficient database queries in the data processing pipeline caused significant processing latency, creating a multi-day backlog. As the backlog grew, the delay between when sessions occurred and when they appeared on the page increased, eventually exceeding the 24-hour display window. The issue was resolved on January 10, 2026, 02:30 UTC, after query optimizations and a database index were deployed. We are implementing enhanced monitoring and automated testing to detect inefficient queries before deployment to prevent recurrence. Jan 10 , 02:33 UTC Update - Our queue has cleared. The last 24 hours of agent session history should now be visible on the AI Controls UI. No data was lost due to this incident. Jan 10 , 02:33 UTC Update - We estimate the backlogged queue will take 3 hours to process. We will post another update once it is completed, or if anything changes with the recovery process. Jan 9 , 23:56 UTC Update - We have deployed an additional fix and are beginning to see recovery to the queue preventing AI Sessions from showing in the AI Controls UI. We are working on an estimate for when the queue will be fully processed, and will post another update once we have that information. Jan 9 , 23:44 UTC Update - We are seeing delays processing the AI Session event queue, which is causing sessions to not be displayed on the AI Controls UI. We have deployed a fix to improve the queue processing and are monitoring for effectiveness. We continue to investigate other mitigation paths. Jan 9 , 22:41 UTC Update - We continue to investigate the problem with Copilot agent sessions not rendering in AI Controls. Jan 9 , 21:36 UTC Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls. Jan 9 , 21:08 UTC Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls. Jan 9 , 20:07 UTC Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls. Jan 9 , 19:35 UTC Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls. Jan 9 , 19:02 UTC Update - We continue to investigate the problem with Copilot agent sessions not rendering in ai controls. Jan 9 , 18:39 UTC Update - Agent Session activity is still observable in audit logs, and this only impacts the AI Controls UI. Jan 9 , 18:08 UTC Update - We are investigating an incident affecting missing Agent Session data on the AI Settings page on Agent Control Plane. Jan 9 , 17:57 UTC Investigating - We are investigating reports of impacted performance for some GitHub services. Jan 9 , 17:53 UTC Jan 9 , 2026 Jan 8 , 2026 Incident with Copilot Resolved - On January 8th, 2025, between approximately 00:00 and 1:30 UTC, the Copilot service experienced a degradation of the Grok Code Fast 1 model due to an issue with our upstream provider. Users encountered elevated error rates when using Grok Code Fast 1. Approximately 4.5% of requests failed across all users during this time. No other models were impacted. The issue was resolved by a mitigation put in place by our provider. Jan 8 , 01:32 UTC Update - The issues with our upstream model provider have been resolved, and Grok Code Fast 1 is once again available in Copilot Chat and across IDE integrations. We will continue monitoring to ensure stability, but mitigation is complete. Jan 8 , 01:31 UTC Update - We are experiencing degraded availability for the Grok Code Fast 1 model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue. Other models are available and working as expected. Jan 8 , 00:45 UTC Investigating - We are investigating reports of degraded performance for Copilot Jan 8 , 00:45 UTC Jan 7 , 2026 Some models missing in Copilot Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Jan 7 , 21:07 UTC Update - We have implemented a mitigation and confirmed that Copilot Pro and Business accounts now have access to the previously missing models. We will continue monitoring to ensure complete resolution. Jan 7 , 19:43 UTC Update - We continue to investigate. We'll post another update by 19:50 UTC. Jan 7 , 19:29 UTC Update - Correction - Copilot Pro and Business users are impacted. Copilot Pro+ and Enterprise users are not impacted. Jan 7 , 19:10 UTC Update - We continue to investigate this problem and have confirmed only Copilot Business users are impacted. We'll post another update by 19:30 UTC. Jan 7 , 19:06 UTC Update - We are currently investigating reports of some Copilot Pro premium models including Opus and GPT 5.2 being unavailable in Copilot products. We'll post another update by 19:08 UTC. Jan 7 , 18:44 UTC Update - We have received reports that some expected models are missing from VSCode and other products using Copilot. We are investigating the cause of this to restore access. Jan 7 , 18:33 UTC Investigating - We are investigating reports of degraded performance for Copilot Jan 7 , 18:32 UTC Jan 6 , 2026 Incident with Actions Resolved - On January 6, 2026 between 12:55 UTC and 17:04 UTC, the ability to download Actions artifacts from GitHub’s web interface was degraded. During this time, all attempts to download artifacts from the web interface failed. Artifact downloads via the REST API and GitHub CLI were unaffected. This was due to a client-side change that was deployed to optimize performance when navigating between pages in a repository. We mitigated the incident by reverting the change. We are working to improve testing of related changes and to add monitoring coverage for artifact downloads through the web interface to reduce our time to detection and prevent similar incidents from occurring in the future. Jan 6 , 17:06 UTC Update - We are investigating issues downloading artifacts from Actions workflows. All customers are affected when attempting to download through the web interface. We're actively working on a fix and will post another update by 17:15 UTC. Jan 6 , 16:44 UTC Investigating - We are investigating reports of degraded performance for Actions Jan 6 , 16:41 UTC Incident with Copilot Resolved - On January 6th, 2026, between approximately 8:41 and 10:07 UTC, the Copilot service experienced a degradation of the GPT-5.1-Codex-Max model due to an issue with our upstream provider. During this time, up to 14.17% of requests to GPT-5.1-Codex-Max failed. No other models were impacted. The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future. Jan 6 , 10:08 UTC Update - The issues with our upstream model provider have been resolved, and GPT-5.1-Codex-Max is once again available. We will continue monitoring to ensure stability. Jan 6 , 10:07 UTC Update - We are experiencing degraded availability for the GPT-5.1-Codex-Max model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue. Other models are available and working as expected. Jan 6 , 09:03 UTC Investigating - We are investigating reports of degraded performance for Copilot Jan 6 , 08:56 UTC Jan 5 , 2026 No incidents reported. Jan 4 , 2026 No incidents reported. Jan 3 , 2026 No incidents reported. Jan 2 , 2026 No incidents reported. Jan 1 , 2026 Disruption with some GitHub services Resolved - On December 31, 2025, between 04:00 UTC and 22:31 UTC, all users visiting https://github.com/features/copilot were unable to load the page and were instead redirected to an error page. The issue was caused by an unexpected content change that resulted in page rendering errors. We mitigated the incident by reverting the change, which restored normal page behavior. To reduce the likelihood and duration of similar issues in the future, we are improving monitoring and alerting for increased error rates on this page and similar pages, and strengthening validation and safeguards around content updates to prevent unexpected changes from causing user-facing errors. Jan 1 , 22:31 UTC Update - Our Copilot feature page ( https://github.com/features/copilot ) is returning 500s. We are currently investigating. This does not impact the core GitHub application. Jan 1 , 21:24 UTC Investigating - We are investigating reports of impacted performance for some GitHub services. Jan 1 , 21:24 UTC Dec 31 , 2025 No incidents reported. Dec 30 , 2025 No incidents reported. ← Incident History Powered by Atlassian Statuspage GitHub text logo Subscribe to our developer newsletter Get tips, technical guides, and best practices. Twice a month. Right in your inbox. Subscribe Product Features Enterprise Copilot Security Pricing Team Resources Roadmap Compare GitHub Platform Developer API Partners Education GitHub CLI GitHub Desktop GitHub Mobile Support Docs Community Forum Professional Services Skills Contact GitHub Company About Customer stories Blog The ReadME Project Careers Newsroom Inclusion Social Impact Shop © GitHub, Inc. Terms Privacy ( Updated 08/2022 ) GitHub X GitHub Facebook GitHub LinkedIn GitHub YouTube Twitch TikTok GitHub.com | 2026-01-13T08:48:04 |
https://jaykhatri.com/ | Jay K. Current I currently run the Observability business at LaunchDarkly [1] . If you want to get in touch, dm me on x [2] , linkedin [3] , or email [4] . Past I was the CEO at Highlight, which was acquired by LaunchDarkly in March of 2025. We were building an open source [5] observability distribution. Before working on Highlight, I went through YCombinator with a company called Reploy [6] , where I built/designed the product and drove sales. At its core, Reploy used Kubernetes to schedule ephemeral environments. Before that, I spent time working on machine learning infra at Deepmind, anti-abuse infrastructure at Google, and product at Handshake, In high school, I was a captain of the 2015 FTC World Championship Robotics team [7] , which started my wanderings in tech. Investing I occasionally invest in fellow founders' businesses. Most of these businesses are in the dev-tools/infra spaces. Some of the public investments I've made include OpenMeter [8] , MagicPatterns [9] , Trigger.dev [10] , Kaelio [11] , and Hemut [12] . Links 1. LaunchDarkly Website 2. Twitter/X Profile 3. LinkedIn Profile 4. Email Contact 5. Highlight GitHub Repository 6. Reploy on Product Hunt 7. Robotics Team News Article 8. OpenMeter Website 9. MagicPatterns Website 10. Trigger.dev Website 11. Kaelio Website 12. Hemut Website | 2026-01-13T08:48:04 |
https://blog.jetbrains.com/blog/2020/06/02/jetbrains-academy-is-getting-ready-to-hit-the-market/ | JetBrains Academy Is Getting Ready to Hit the Market | The JetBrains Academy Blog Skip to content Topics Search Burger menu icon IDEs CLion DataGrip DataSpell Fleet GoLand IntelliJ IDEA PhpStorm PyCharm RustRover Rider RubyMine WebStorm Plugins & Services Big Data Tools Code With Me JetBrains Platform Scala Toolbox App Writerside JetBrains AI Grazie Junie JetBrains for Data Kineto Team Tools Datalore Space TeamCity Upsource YouTrack Hub Qodana CodeCanvas Matter .NET & Visual Studio .NET Tools ReSharper C++ Languages & Frameworks Kotlin Ktor MPS Amper Education & Research JetBrains Academy Research Company Company Blog Security JetBrains Academy The place for learning and teaching computer science your way Follow Follow: X X Facebook Facebook Visit Our Website All Project-Based Learning Learning Courses Tools for Teaching Offline Programs JetBrains Academy Plugin Interviews Digest News Project-Based Learning JetBrains Academy Is Getting Ready to Hit the Market Tatiana Vasilyeva Back in February 2019, we announced the Early Access Program (EAP) for JetBrains Academy – an educational platform with a focus on learning by doing. We launched the program with a curriculum for Java including 25 projects that students could build while learning and practicing new concepts. These EAP months have been very exciting! With more than 130,000 registered students, it has brought us an incredible amount of user feedback. Users have shared so many wonderful ideas with us. These ideas have led us to rethink and rework JetBrains Academy again and again, always striving to make it a better platform for learning to program. It now features Java and Python, with Kotlin and Frontend tracks under construction, and it offers more than 100 projects and over 870 topics. Today JetBrains Academy is not only an educational platform, but it is also a community of passionate learners. We are enormously grateful to those who have let us be a part of their learning journey! We want to make JetBrains Academy the best educational platform, and now we’re ready to take the next important step – moving beyond the EAP. What’s next? JetBrains Academy will remain in the Early Access Program (EAP) with free access until July 1, 2020 . If you register on the platform before July 1, 2020 You will continue to receive free access to all JetBrains Academy learning activities and resources until January 1, 2021 . You will get a 50% discount off a regular price of $49.90/month for the following 12 months after the free period ends, and will need to pay only $24.90/month for your subscription. REGISTER NOW Q&A session We will endeavor to address any questions and concerns you may have about the upcoming subscription access model before the end of the EAP. To make this easier for you and for us, we are now opening a special thread on Reddit that will be available for the next 24 hours . In this thread, you can ask any questions you have about the upcoming changes. We will then accumulate all the questions and we will answer them both on Reddit and in a special post here on the blog. We will continue to keep you posted with updates and product news. ASK A QUESTION Your Educational Products team Share Facebook Twitter Linkedin Prev post JetBrains Educational Products for Competitive Programming JetBrains Academy Subscription Model: Answering Your Questions Next post Subscribe to JetBrains Academy updates Subscribe form By submitting this form, I agree to the JetBrains Privacy Policy Notification icon By submitting this form, I agree that JetBrains s.r.o. ("JetBrains") may use my name, email address, and location data to send me newsletters, including commercial communications, and to process my personal data for this purpose. I agree that JetBrains may process said data using third-party services for this purpose in accordance with the JetBrains Privacy Policy . I understand that I can revoke this consent at any time in my profile . In addition, an unsubscribe link is included in each email. Submit Thanks, we've got you! Discover more Learn AI-Assisted Programming With Junie: Free Courses From JetBrains Academy and Nebius Master AI-assisted programming with Junie and build portfolio-ready AI projects through our free courses. Regina Muradova Learn AI-Assisted Programming With JetBrains Academy and Nebius Uncover what’s holding developers back with AI tools and gain hands-on solutions to boost your workflow. Anastasia Khramushina JetBrains Academy: Top Courses and Projects of 2024 Celebrate International Day of Education with a flashback to the top courses and projects of 2024 at JetBrains Academy! Regina Muradova JetBrains Academy: New in November Fine-tune your skills in Kotlin, backend development, Git, or AI with the new content at JetBrains Academy this November! Regina Muradova Privacy & Security Terms of Use Legal Genuine tools Twitter Facebook Linkedin Instagram Youtube RSS Tiktok Merchandise store icon Merchandise store Copyright © 2000 JetBrains s.r.o. | 2026-01-13T08:48:04 |
https://livesuggest.ai/pt/ | Assistente IA de reuniões sem bot | LiveSuggest LiveSuggest 1h grátis Preços Entrar Registrar Iniciar sessão Português Language en English fr Français es Español de Deutsch pt Português it Italiano nl Nederlands pl Polski ja 日本語 zh 中文 ko 한국어 tr Türkçe 1h grátis Preços Entrar Registrar Iniciar sessão Language en English fr Français es Español de Deutsch pt Português it Italiano nl Nederlands pl Polski ja 日本語 zh 中文 ko 한국어 tr Türkçe 🌍 12 idiomas Assistente IA de reuniões que não entra nas suas chamadas Receba sugestões IA em tempo real via microfone ou partilha de separador. Nenhum bot entra na sua reunião, nenhuma gravação armazenada. Experimentar grátis ✓ Sem cartão de crédito ✓ Sem registo ✓ 1h grátis 👥 Já usado por consultores, freelancers e gestores de projeto Exemplo de ajuda IA durante reuniões ACOMPANHAMENTO DE REUNIÃO Decisão registada: Sara finaliza o protótipo até sexta-feira. NOVA IDEIA E se agendássemos uma retrospectiva após este sprint para registar as lições aprendidas? EXPLICAÇÃO DE TERMO O "sprint" mencionado corresponde a um ciclo de desenvolvimento de 2 semanas na metodologia Agile. TRADUÇÃO DE TERMO "Stakeholder" (inglês) — parte interessada, pessoa ou grupo com interesse no projeto. Computador Celular Tudo o que você precisa para permanecer engajado e contribuir efetivamente Sugestões em tempo real Receba sugestões contextuais conforme a conversa se desenrola. Ideias de resposta, lembretes de pontos-chave e esclarecimentos aparecem quando você mais precisa. Sem instalação necessária Acesse o LiveSuggest, um assistente de reuniões sem bot, diretamente do seu navegador web. Sem downloads, sem extensões, sem configuração complexa. Comece em segundos. Design focado em privacidade Construído com consentimento e transparência em seu núcleo. Suas conversas são processadas em tempo real sem gravação e excluídas automaticamente. Nenhum dado é retido após o término da sessão. Perguntas frequentes Como funciona sem bot? O LiveSuggest captura áudio diretamente do seu dispositivo — via microfone ou partilha de separador do navegador. Nenhum bot entra na sua chamada ou aparece na lista de participantes. É igualmente preciso sem gravação? Sim. Usamos os mesmos modelos de IA avançados que ferramentas baseadas em gravação. O seu áudio é processado em tempo real e imediatamente descartado — mesma precisão, privacidade mais forte. As sugestões não me vão distrair? Não. As sugestões aparecem numa janela separada que consulta quando precisa. Apoiam a sua participação sem interromper a conversa. Como funciona 1 Inicie uma sessão Abra o LiveSuggest no seu navegador e confirme que todos os participantes estão informados. Pronto para ouvir 2 Entre na sua reunião Entre na sua reunião online ou presencialmente. O LiveSuggest ouve e transcreve em tempo real. Transcrevendo… 3 Receba sugestões Receba sugestões úteis e contextuais durante toda a sua reunião para contribuir efetivamente. Sugestões em tempo real 4 tipos de sugestões personalizáveis Acompanhamento de reunião Captura decisões-chave, tarefas pendentes e acordos com responsáveis e prazos, garantindo que nada importante escape. Nova ideia Sugere ideias relevantes e perspetivas novas para enriquecer a discussão e abrir novos caminhos. Explicação de termo Esclarece instantaneamente termos técnicos, acrónimos e conceitos complexos mencionados na conversa, para que nunca se sinta perdido. Tradução de termo Traduz e explica expressões em língua estrangeira em tempo real, ajudando-o a manter-se envolvido independentemente do idioma. Nenhum bot entra na sua reunião 📹 Zoom 💼 Teams 🎥 Meet 👥 Presencial Funciona com qualquer plataforma de reuniões pelo navegador Ao contrário de outras ferramentas de IA, o LiveSuggest nunca adiciona um participante à sua reunião. Funciona perfeitamente com Google Meet, Zoom, Microsoft Teams ou qualquer plataforma acessível pelo navegador — basta compartilhar o áudio da aba. Para reuniões presenciais, use seu microfone. Escolha seu plano Escolha o plano que melhor se adapta às suas necessidades 🧾 Faturação empresarial disponível Basic Ideal para experimentar $ 3 /mês s/ IVA 3 horas de áudio ~6 reuniões de 30 min Começar ★ Recomendado Plus O mais popular $ 8 /mês s/ IVA 10 horas de áudio ~20 reuniões de 30 min 10h pelo preço de 8h Escolher Plus Pro Para usuários intensivos $ 20 /mês s/ IVA 30 horas de áudio ~60 reuniões de 30 min 30h pelo preço de 20h Ir para Pro Design focado em privacidade ✓ Construído com consentimento e transparência em seu núcleo. Suas conversas são processadas em tempo real sem gravação e excluídas automaticamente. Nenhum dado é retido após o término da sessão. ✓ Áudio processado em tempo real, não armazenado ✓ Dados da sessão excluídos ao final de cada sessão ✓ Privacidade Pronto para não perder mais nada e contribuir melhor nas reuniões? Experimente o LiveSuggest gratuitamente — sem cartão de crédito. Receba sugestões IA em tempo real sem bots ou gravações. Mantenha o foco, contribua melhor. Experimentar agora — Grátis Ver preços ✓ Sem cartão de crédito ✓ Sem registo ✓ 1h grátis LiveSuggest Receba sugestões contextuais de um assistente de reuniões sem bot enquanto fala — ideias de resposta, lembretes de pontos-chave e esclarecimentos para se manter atento no momento, mesmo quando trabalha numa língua estrangeira. Produto Preços FAQ Blog Jurídico Privacidade Termos Aviso Legal Consentimento Suporte Contato Reportar um bug © 2026 LiveSuggest. Todos os direitos reservados. Este site utiliza cookies Utilizamos cookies para garantir o funcionamento adequado do site e melhorar sua experiência. Você pode aceitar todos os cookies, rejeitá-los ou personalizar suas preferências. Aceitar tudo Rejeitar tudo Personalizar | 2026-01-13T08:48:04 |
https://livesuggest.ai/blog/ | Blog - LiveSuggest LiveSuggest 1h free Pricing Login Sign up Start session English Language en English fr Français es Español de Deutsch pt Português it Italiano nl Nederlands pl Polski ja 日本語 zh 中文 ko 한국어 tr Türkçe 1h free Pricing Login Sign up Start session Language en English fr Français es Español de Deutsch pt Português it Italiano nl Nederlands pl Polski ja 日本語 zh 中文 ko 한국어 tr Türkçe Blog Tips and insights for better meetings AI and Meetings: How to Boost Productivity Without Intrusive Tools Discover how AI can improve meeting productivity without intrusive tools. Learn about real-time suggestions that enhance participation while respecting collaboration. January 15, 2026 How to Participate Better in Meetings as a Non-Native Speaker (Without Stress) Struggling to keep up in meetings in a foreign language? Discover practical strategies and how real-time AI assistance can help you participate with confidence. January 15, 2026 Why Meeting Minutes Are No Longer Enough (And How to Better Follow Conversations) Discover the limits of traditional meeting minutes and learn how real-time support helps you stay engaged and understand conversations as they happen. January 15, 2026 LiveSuggest Real-time AI meeting assistant with contextual prompts and key reminders to support better conversations — even when working in a second language. Product Pricing FAQ Blog Legal Privacy Terms Legal Notice Consent Support Contact Report a bug © 2026 LiveSuggest. All rights reserved. This site uses cookies We use cookies to ensure the proper functioning of the site and improve your experience. You can accept all cookies, reject them, or customize your preferences. Accept all Reject all Customize | 2026-01-13T08:48:04 |
https://cursor.com/careers | Careers · Cursor Skip to content Cursor Features Enterprise Pricing Resources ↓ Changelog Blog Docs ↗ Community Learn ↗ Workshops Forum ↗ Careers Features Enterprise Pricing Resources → Sign in Download Cursor is transforming the way we build software. Millions of developers at the world's most ambitious companies already code with Cursor, but we have much more work to do. We obsess over talent to an unusual degree and are designing a company that's a haven for self-motivated individual contributors. This work demands our best. If this sounds exciting, we'd love to hear from you. Open roles All teams ↓ All teams ✓ GTM Engineering User Ops Operations All locations ↓ All locations ✓ SF / NY New York SF / NY / Remote Remote San Francisco Account Executive GTM · Full-time · SF / NY Apply → AI Deployment Manager GTM · Full-time · SF / NY Apply → Brand Designer Engineering · Full-time · New York Apply → Community Program Manager, Campus Lead GTM · Full-time · SF / NY / Remote Apply → Community Program Manager, Community Lead GTM · Full-time · SF / NY / Remote Apply → Community Support Engineer User Ops · Full-time · Remote Apply → Data Engineer, Analytics Engineering · Full-time · SF / NY Apply → Design Engineer Engineering · Full-time · SF / NY Apply → Engineering Manager, Client Infrastructure Engineering · Full-time · SF / NY Apply → Engineering Manager, DevEx Engineering · Full-time · SF / NY Apply → Engineering Manager, Infrastructure Engineering · Full-time · SF / NY Apply → Field Engineer GTM · Full-time · SF / NY Apply → Growth GTM · Full-time · San Francisco Apply → GTM Systems Operations · Full-time · SF / NY Apply → Product Designer Engineering · Full-time · SF / NY Apply → Research Scientist Engineering · Full-time · SF / NY Apply → Sales Manager GTM · Full-time · SF / NY Apply → Security GRC Engineer Engineering · Full-time · SF / NY Apply → Software Engineer, Client Infrastructure Engineering · Full-time · SF / NY / Remote Apply → Software Engineer, DevEx Engineering · Full-time · SF / NY Apply → Software Engineer, Enterprise Engineering · Full-time · SF / NY Apply → Software Engineer, Growth Engineering · Full-time · SF / NY Apply → Software Engineer, Infrastructure Engineering · Full-time · SF / NY Apply → Software Engineer, ML Research Engineering · Full-time · SF / NY Apply → Software Engineer, Product Engineering · Full-time · SF / NY Apply → Software Engineer, Security Engineering · Full-time · SF / NY Apply → Technical Support Engineer User Ops · Full-time · Remote Apply → Technical Support Engineering Manager User Ops · Full-time · Remote Apply → Product Features Enterprise Web Agents Bugbot CLI Pricing Resources Download Changelog Docs ↗ Learn ↗ Forum ↗ Status ↗ Company Careers Blog Community Workshops Students Brand Legal Terms of Service Privacy Policy Data Use Security Connect X ↗ LinkedIn ↗ YouTube ↗ © 2026 Cursor 🛡 SOC 2 Certified 🌐 English ↓ English ✓ 简体中文 日本語 繁體中文 Skip to content Cursor Features Enterprise Pricing Resources ↓ Changelog Blog Docs ↗ Community Learn ↗ Workshops Forum ↗ Careers Features Enterprise Pricing Resources → Sign in Download Cursor is transforming the way we build software. Millions of developers at the world's most ambitious companies already code with Cursor, but we have much more work to do. We obsess over talent to an unusual degree and are designing a company that's a haven for self-motivated individual contributors. This work demands our best. If this sounds exciting, we'd love to hear from you. Open roles All teams ↓ All teams ✓ GTM Engineering User Ops Operations All locations ↓ All locations ✓ SF / NY New York SF / NY / Remote Remote San Francisco Account Executive GTM · Full-time · SF / NY Apply → AI Deployment Manager GTM · Full-time · SF / NY Apply → Brand Designer Engineering · Full-time · New York Apply → Community Program Manager, Campus Lead GTM · Full-time · SF / NY / Remote Apply → Community Program Manager, Community Lead GTM · Full-time · SF / NY / Remote Apply → Community Support Engineer User Ops · Full-time · Remote Apply → Data Engineer, Analytics Engineering · Full-time · SF / NY Apply → Design Engineer Engineering · Full-time · SF / NY Apply → Engineering Manager, Client Infrastructure Engineering · Full-time · SF / NY Apply → Engineering Manager, DevEx Engineering · Full-time · SF / NY Apply → Engineering Manager, Infrastructure Engineering · Full-time · SF / NY Apply → Field Engineer GTM · Full-time · SF / NY Apply → Growth GTM · Full-time · San Francisco Apply → GTM Systems Operations · Full-time · SF / NY Apply → Product Designer Engineering · Full-time · SF / NY Apply → Research Scientist Engineering · Full-time · SF / NY Apply → Sales Manager GTM · Full-time · SF / NY Apply → Security GRC Engineer Engineering · Full-time · SF / NY Apply → Software Engineer, Client Infrastructure Engineering · Full-time · SF / NY / Remote Apply → Software Engineer, DevEx Engineering · Full-time · SF / NY Apply → Software Engineer, Enterprise Engineering · Full-time · SF / NY Apply → Software Engineer, Growth Engineering · Full-time · SF / NY Apply → Software Engineer, Infrastructure Engineering · Full-time · SF / NY Apply → Software Engineer, ML Research Engineering · Full-time · SF / NY Apply → Software Engineer, Product Engineering · Full-time · SF / NY Apply → Software Engineer, Security Engineering · Full-time · SF / NY Apply → Technical Support Engineer User Ops · Full-time · Remote Apply → Technical Support Engineering Manager User Ops · Full-time · Remote Apply → Product Features Enterprise Web Agents Bugbot CLI Pricing Resources Download Changelog Docs ↗ Learn ↗ Forum ↗ Status ↗ Company Careers Blog Community Workshops Students Brand Legal Terms of Service Privacy Policy Data Use Security Connect X ↗ LinkedIn ↗ YouTube ↗ © 2026 Cursor 🛡 SOC 2 Certified 🌐 English ↓ English ✓ 简体中文 日本語 繁體中文 | 2026-01-13T08:48:04 |
https://github.com/skills/resolve-merge-conflicts | GitHub - skills/resolve-merge-conflicts: Learn why conflicts happen and how to resolve them. Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} skills / resolve-merge-conflicts Public template generated from skills/exercise-template Notifications You must be signed in to change notification settings Fork 156 Star 204 Learn why conflicts happen and how to resolve them. License MIT license 204 stars 156 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 3 Pull requests 4 Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Security Insights skills/resolve-merge-conflicts main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 39 Commits .github .github .gitignore .gitignore LICENSE LICENSE README.md README.md resume.md resume.md View all files Repository files navigation README Code of conduct Contributing MIT license Security Resolve merge conflicts Learn why conflicts happen and how to resolve them. Welcome Merge conflicts happen when two people make changes to the same file on GitHub—a common occurrence when you’re working with others. While resolving differences might involve some discussion, merge conflicts don’t have to be scary. This course guides you through the steps to finding the best merge conflict solution, so your team can keep building. Who is this for : New developers, new GitHub users, users new to Git, students, managers, teams. What you'll learn : What merge conflicts are, how you resolve merge conflicts, how to reduce merge conflicts. What you'll build : We'll work with a short Markdown resume file in this course. Prerequisites : We recommend taking Introduction to GitHub prior to this course. How long : This course takes less than 30 minutes to complete. In this course, you will: Create a pull request Resolve a merge conflict Create a merge conflict Merge your pull request How to start this course Right-click Start course and open the link in a new tab. In the new tab, most of the prompts will automatically fill in for you. For owner, choose your personal account or an organization to host the repository. We recommend creating a public repository, as private repositories will use Actions minutes . Scroll down and click the Create repository button at the bottom of the form. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README. Get help: Post in our discussion board • Review the GitHub status page © 2023 GitHub • Code of Conduct • MIT License About Learn why conflicts happen and how to resolve them. Topics github git merge-conflicts merge-conflict skills-course Resources Readme License MIT license Code of conduct Code of conduct Contributing Contributing Security policy Security policy Uh oh! There was an error while loading. Please reload this page . Activity Custom properties Stars 204 stars Watchers 13 watching Forks 156 forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 5 Uh oh! There was an error while loading. Please reload this page . Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:48:04 |
https://addons.mozilla.org/hr/firefox/addon/rentgen/ | Rentgen – Nabavi ovo proširenje za 🦊 Firefox (hr) Dodaci za preglednik Firefox Proširenja Teme Više … za Firefox Rječnici i jezični paketi Druge stranice preglednika Dodaci za Android Prijavi se Traži Traži Rentgen Autor: “Internet. Time to act!” Foundation Rentgen to wtyczka, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. 5 (12 recenzije) 5 (12 recenzije) 216 korisnika 216 korisnika Preuzmi Firefox i nabavi proširenje Preuzmi datoteku Metapodaci proširenja Snimke ekrana Informacije o ovom proširenju Rentgen to wtyczka dla przeglądarek opartych o Firefoxa, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. Więcej informacji: https://www.internet-czas-dzialac.pl/odcinek-33-wtyczka-rentgen Funkcje Rentgena: analiza ruchu sieciowego generowanego przez stronę internetową; wizualizacja danych przekazanych do podmiotów trzecich przez odwiedzaną stronę (historia przeglądania użytkownika oraz jego ciasteczka); przygotowywanie zrzutów ekranów narzędzi deweloperskich będących dowodem przekazanych danych do podmiotów trzecich; pomoc w oszacowaniu potencjalnych obszarów roboczych względem zgodności z RODO; generowanie raportu lub treści maila, który można wysłać do administratora oraz Urzędu Ochrony Danych Osobowych. Kod źródłowy Komentari razvijatelja Jeżeli uważasz, że wtyczka Rentgen okazała się przydatna, zostaw nam recenzję. Jeżeli znalazłeś błąd lub masz pomysł na ulepszenie Rentgena, napisz do nas maila: kontakt@internet-czas-dzialac.pl Ocjena 5 od 12 recenzenta Prijavi se i ocijeni ovo proširenje Još nema ocjena Ocjena je spremljena 5 12 4 0 3 0 2 0 1 0 Pročitaj 12 recenzija Dozvole i podaci Potrebne dozvole: Čitati i mijenjati postavke privatnosti Upravljati proxy postavkama preglednika Pristup tvojim podacima za sve web stranice Prikupljanje podataka: Programer kaže da ovo proširenje ne zahtijeva prikupljanje podataka. Saznaj više Daljnje informacije Poveznice dodatka Početna stranica Stranica podrške E-adresa podrške Verzija 0.2.4 Veličina 9,55 MB Zadnje aktualiziranje prije 21 dana (23. pro. 2025) Povezane kategorije Razvoj weba Privatnost i sigurnost Licenca Samo GNU Opća javna licenca v3.0 Politika privatnosti Pročitaj politiku privatnosti za ovaj dodatak Povijest verzija Pogledaj sve verzije Oznake anti malware anti tracker container privacy security Dodaj u zbirku Odaberi zbirku … Stvori novu zbirku Prijavi ovaj dodatak Podrži ovog programera Programer ovog proširenja te moli, da pomoću male donacije podržiš daljnji razvoj proširenja. Doprinesi sada Idi na početnu stranicu Mozille Dodaci Informacije Blog za Firefox dodatke Radionica za proširenja Centar za programere Pravila za programere Blog zajednice Forum Prijavi grešku Priručnik za recenziranje Preglednici Desktop Mobile Enterprise Proizvodi Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Privatnost Kolačići Pravne informacije Osim gdje je drugačije navedeno , sadržaj ove stranice licenciran je pod licencom Creative Commons Imenovanje dijeli pod istim uvjetima verzija 3.0 ili novijoj. Promijeni jezik Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T08:48:04 |
https://dev.to/art_light/we-didnt-align-we-argued-and-shipped-a-better-system-1818 | We Didn’t “Align” — We Argued (and Shipped a Better System) - 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 Art light Posted on Jan 11 We Didn’t “Align” — We Argued (and Shipped a Better System) # discuss # career # programming # developer Software projects rarely fail because someone can’t write code. They fail because people quietly disagree, assumptions go unchallenged, and everyone is “aligned” right up until production is on fire. This is a story about a project where collaboration didn’t look pretty — but it worked. The Setup: Parallel Work, Parallel Universes We were building a product with a fairly standard setup: Frontend: React + TypeScript Backend: REST API Multiple engineers working in parallel Tight deadlines (the fun kind) Everything looked fine… until it didn’t. The frontend assumed fields that the backend hadn’t implemented yet. The backend refactored response shapes without realizing the frontend relied on them. Types existed — just not in the same universe. Nothing was broken enough to stop development, but bugs kept appearing late. The worst kind. The “why didn’t we catch this earlier?” kind. The First Real Collaboration Moment (aka The Argument) At some point, someone asked the dangerous question: “Why don’t we just define the API first?” Enter fullscreen mode Exit fullscreen mode This triggered: A backend engineer worrying about losing flexibility A frontend engineer worried about slowing down Someone else saying “we can just fix it later” (classic) Instead of pretending we agreed, we argued it out. And that was the turning point. The Decision: API First (But Practically) We didn’t adopt API-first as a buzzword. We adopted it as a collaboration contract. What we actually did: Defined OpenAPI specs early Generated types for the frontend Treated breaking API changes as actual breaking changes, not “oops” Trade-offs we accepted: Backend lost some freedom to “just rename stuff” Specs required discipline and review Changes took slightly longer upfront What we gained: Predictable frontend types Fewer late surprises Much calmer PR reviews The Unexpected Benefit: Better Conversations The biggest win wasn’t technical — it was human. Instead of: “Why is this field missing?” Enter fullscreen mode Exit fullscreen mode We started asking: “Should this field even exist?” Enter fullscreen mode Exit fullscreen mode Specs forced us to: Name things clearly Argue about responsibility Make decisions visible Design reviews became real design reviews — not post-mortems. Mistakes We Made (So You Don’t Romanticize This) Let’s be honest — it wasn’t smooth: We over-specified early on and had to loosen things later One spec PR was longer than some novels We once broke the API and forgot to regenerate types (yes, that hurt) Collaboration doesn’t remove mistakes. It just makes them cheaper and earlier. Humor Break: The “One Small Change” Lie Every team has this moment: “It’s just a small backend change.” Enter fullscreen mode Exit fullscreen mode Famous last words. With shared specs, that sentence became: “It’s a small change… but it touches 12 endpoints.” Enter fullscreen mode Exit fullscreen mode Which is exactly the kind of honesty you want before merging. What Senior Collaboration Actually Looks Like From this experience, here’s what I now believe: Collaboration is surfacing disagreement early Silence is more dangerous than conflict Tools don’t fix teams — they expose them Clear contracts reduce ego-driven decisions Senior engineers don’t avoid friction. They manage it productively. Final Takeaway Good collaboration isn’t about being nice. It’s about being clear, honest, and occasionally uncomfortable — together. When teams stop optimizing for speed today and start optimizing for trust tomorrow, the codebase follows. And yes — sometimes that starts with an argument. Top comments (6) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Travis Wilson Travis Wilson Travis Wilson Follow Staff engineer, 12+ years in data pipelines. Building Flywheel - data pipelines for startups. Location Atlanta, Ga Pronouns he/him Work Staff Engineer + Solo Founder (Flywheel) Joined Jan 11, 2026 • Jan 12 Dropdown menu Copy link Hide Interesting perspective. I've been experiencing this from a different angle - as a solo founder using AI as my primary collaborator, I've been able to sidestep a lot of these alignment battles entirely. The trade-off you describe (less flexibility for backend engineers, discipline around spec maintenance) assumes humans on both sides who have opinions and preferences. When it's me + Claude, I don't have to negotiate syntax choices or convince anyone that a breaking change is worth it. I just make the call and move on. But here's the thing - that only works because I invested heavily in the architecture first. Consistent patterns, clear service boundaries, good test coverage. The AI doesn't push back on conventions, it follows them. Which means the "arguing" phase you describe gets replaced by "did I set up the system so the AI can do this without hand-holding?" Different problem, same underlying truth: the system design matters more than the individual interactions Like comment: Like comment: 3 likes 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 • Jan 12 Dropdown menu Copy link Hide Really thoughtful take — I like how you frame AI as a collaborator rather than a shortcut. Your point about architecture doing the “arguing” up front really resonates, especially the idea that good system design replaces ongoing negotiation. It makes me think the real leverage isn’t just using AI, but setting things up so it can work independently and consistently. I’m very interested in seeing how this approach evolves as solo founders push it further. Like comment: Like comment: 3 likes Like Comment button Reply Collapse Expand Dorothy J Aubrey Dorothy J Aubrey Dorothy J Aubrey Follow Location Maryland, USA Education University of Miami School of Law, University of Wisconsin - Madison Joined Dec 18, 2025 • Jan 12 Dropdown menu Copy link Hide I really enjoyed this - especially the way you framed disagreement as something productive instead of something to smooth over. On the best team I ever worked with, we constantly bickered (but made, arguably, some of the best products of my life). The part about specs forcing real conversations, instead of polite assumptions, really resonated. I’ve seen the same thing happen when decisions are made visible early: it’s uncomfortable in the moment, but it saves so much pain later. Thanks for sharing a version of collaboration that feels real and not LinkedIn-glossy. 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 • Jan 12 Dropdown menu Copy link Hide Thank you — I agree that healthy disagreement is often a sign of trust, not dysfunction, and the best teams use it to surface better decisions earlier. Making assumptions visible through specs or early decisions creates short-term friction but dramatically improves long-term outcomes. Like comment: Like comment: 1 like Like Comment button Reply 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 Art light Follow Trust yourself🌞your capabilities are your true power. ❤Telegram - ✔lighthouse4661 ❤Discord - ✔lighthouse4661 Pronouns He/him Work CTO Joined Nov 21, 2025 More from Art light Prompt Engineering Won’t Fix Your Architecture # discuss # career # ai # programming I Didn’t “Become” a Senior Developer. I Accumulated Damage. # programming # ai # career # discuss Hello 2026: This Will Only Take Two Weeks # programming # devops # discuss # career 💎 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:48:04 |
https://neon.tech/docs/serverless/serverless-driver | Neon serverless driver - Neon Docs This 250+ engineer team replaced shared staging with isolated database branches for safer deploys Neon Docs Search ... Ask AI Log In Sign Up Get started About Connect Connect to Neon Clients & tools Troubleshooting Develop Frontend & Frameworks Frameworks Languages ORMs Backend Data API Neon Auth Postgres RLS AI AI for Agents AI App Starter Kit Tools & Workflows API, CLI & SDKs Local development Integrations (3rd party) Workflows & CI/CD Templates Examples repo Manage Neon platform Plans and billing Neon on Azure Security & compliance Postgres Extensions Postgres guides Compatibility Version support Upgrade PostgreSQL Tutorial Resources Status Support Changelog Roadmap Early access Community Glossary RSS feeds Platform integration Search ... Ask AI Connect to Neon Connect to Neon Drivers and connection types Connect from any app Neon serverless driver Neon SQL Editor Passwordless auth Securing connections Connection pooling Latency benchmarks / Integrations (3rd party) / Serverless / Neon serverless driver Neon serverless driver Connect to Neon from serverless environments over HTTP or WebSockets Pre-built prompt for Neon Serverless + Drizzle (JS/TS) Copy prompt The Neon serverless driver is a low-latency Postgres driver for JavaScript and TypeScript that allows you to query data from serverless and edge environments over HTTP or WebSockets in place of TCP. The driver's low-latency capability is due to message pipelining and other optimizations . The Neon serverless driver is now generally available (GA) The GA version of the Neon serverless driver, v1.0.0 and higher, requires Node.js version 19 or higher. It also includes a breaking change but only if you're calling the HTTP query template function as a conventional function. For details, please see the 1.0.0 release notes or read the blog post . When to query over HTTP vs WebSockets: HTTP : Querying over an HTTP fetch request is faster for single, non-interactive transactions, also referred to as "one-shot queries". Issuing multiple queries via a single, non-interactive transaction is also supported. See Use the driver over HTTP . WebSockets : If you require session or interactive transaction support or compatibility with node-postgres (the popular npm pg package), use WebSockets. See Use the driver over WebSockets . AI Rules available Working with AI coding assistants? Check out our AI rules for the Neon Serverless Driver to help your AI assistant generate better code for serverless database connections. Install the Neon serverless driver You can install the driver with your preferred JavaScript package manager. For example: npm install @neondatabase/serverless The driver includes TypeScript types (the equivalent of @types/pg ). No additional installation is required. note The Neon serverless driver is also available as a JavaScript Registry (JSR) package: https://jsr.io/@neon/serverless . The JavaScript Registry (JSR) is a package registry for JavaScript and TypeScript. JSR works with many runtimes (Node.js, Deno, browsers, and more) and is backward compatible with npm . Configure your Neon database connection You can obtain a connection string for your database by clicking the Connect button on your Project Dashboard . Your Neon connection string will look something like this: DATABASE_URL = postgresql://[user ]:[password]@[neon_hostname]/[dbname] The examples that follow assume that your database connection string is assigned to a DATABASE_URL variable in your application's environment file. Use the driver over HTTP The Neon serverless driver uses the neon function for queries over HTTP. The function returns a query function that can only be used as a template function for improved safety against SQL injection vulnerabilities. For example: import { neon } from '@neondatabase/serverless' ; const sql = neon ( process . env . DATABASE_URL ); const id = 1 ; // Safe and convenient template function usage const result = await sql `SELECT * FROM table WHERE id = ${ id } ` ; // For manually parameterized queries, use the query() function const result = await sql .query ( 'SELECT * FROM table WHERE id = $1' , [id]); // For interpolating trusted strings (like column or table names), use the unsafe() function const table = condition ? 'table1' : 'table2' ; // known-safe string values const result = await sql `SELECT * FROM ${ sql .unsafe (table) } WHERE id = ${ id } ` ; // Alternatively, use template literals for known-safe values const table = condition ? sql `table1` : sql `table2` ; const result = await sql `SELECT * FROM ${ table } WHERE id = ${ id } ` ; SQL template queries are fully composable, including those with parameters: const name = 'Olivia' ; const limit = 1 ; const whereClause = sql `WHERE name = ${ name } ` ; const limitClause = sql `LIMIT ${ limit } ` ; // Parameters are numbered appropriately at query time const result = await sql `SELECT * FROM table ${ whereClause } ${ limitClause } ` ; You can use raw SQL queries or tools such as Drizzle-ORM , kysely , Zapatos , and others for type safety. Node.js Drizzle-ORM Vercel Edge Function Vercel Serverless Function import { neon } from '@neondatabase/serverless' ; const sql = neon ( process . env . DATABASE_URL ); const posts = await sql `SELECT * FROM posts WHERE id = ${ postId } ` ; // or using query() for parameterized queries const posts = await sql .query ( 'SELECT * FROM posts WHERE id = $1' , [postId]); // `posts` is now [{ id: 12, title: 'My post', ... }] (or undefined) note The maximum request size and response size for queries over HTTP is 64 MB. neon function configuration options The neon(...) function returns a query function that can be used as a template function, with additional properties for special cases: import { neon } from '@neondatabase/serverless' ; const sql = neon ( process . env . DATABASE_URL ); // Use as a template function (recommended) const rows = await sql `SELECT * FROM posts WHERE id = ${ postId } ` ; // Use query() for manually parameterized queries const rows = await sql .query ( 'SELECT * FROM posts WHERE id = $1' , [postId]); // Use unsafe() for trusted string interpolation const table = 'posts' ; // trusted value const rows = await sql `SELECT * FROM ${ sql .unsafe (table) } WHERE id = ${ postId } ` ; By default, the query function returns only the rows resulting from the provided SQL query, and it returns them as an array of objects where the keys are column names. For example: const rows = await sql `SELECT * FROM posts WHERE id = ${ postId } ` ; // -> [{ id: 12, title: "My post", ... }] You can customize the return format using the configuration options fullResults and arrayMode . These options are available both on the neon(...) function and on the query function it returns. arrayMode: boolean , false by default The default arrayMode value is false . When it is true, rows are returned as an array of arrays instead of an array of objects: const sql = neon ( process . env . DATABASE_URL , { arrayMode : true }); const rows = await sql `SELECT * FROM posts WHERE id = ${ postId } ` ; // -> [[12, "My post", ...]] Or, with the same effect when using query(): const sql = neon ( process . env . DATABASE_URL ); const rows = await sql .query ( 'SELECT * FROM posts WHERE id = $1' , [postId] , { arrayMode : true }); // -> [[12, "My post", ...]] fullResults: boolean The default fullResults value is false . When it is true , additional metadata is returned alongside the result rows, which are then found in the rows property of the return value. The metadata matches what would be returned by node-postgres : const sql = neon ( process . env . DATABASE_URL , { fullResults : true }); const results = await sql `SELECT * FROM posts WHERE id = ${ postId } ` ; /* -> { rows: [{ id: 12, title: "My post", ... }], fields: [ { name: "id", dataTypeID: 23, ... }, { name: "title", dataTypeID: 25, ... }, ... ], rowCount: 1, rowAsArray: false, command: "SELECT" } */ Or, with the same effect when using query(): const sql = neon ( process . env . DATABASE_URL ); const results = await sql .query ( 'SELECT * FROM posts WHERE id = $1' , [postId] , { fullResults : true , }); // -> { ... same as above ... } fetchOptions: Record<string, any> The fetchOptions option can also be passed to either neon(...) or the query function. This option takes an object that is merged with the options to the fetch call. For example, to increase the priority of every database fetch request: import { neon } from '@neondatabase/serverless' ; const sql = neon ( process . env . DATABASE_URL , { fetchOptions : { priority : 'high' } }); const rows = await sql `SELECT * FROM posts WHERE id = ${ postId } ` ; Or to implement a fetch timeout: import { neon } from '@neondatabase/serverless' ; const sql = neon ( process . env . DATABASE_URL ); const abortController = new AbortController (); const timeout = setTimeout (() => abortController .abort ( 'timed out' ) , 10000 ); const rows = await sql ( 'SELECT * FROM posts WHERE id = $1' , [postId] , { fetchOptions : { signal : abortController .signal } , }); // throws an error if no result received within 10s clearTimeout (timeout); For additional details, see Options and configuration . Issue multiple queries with the transaction() function The transaction(queriesOrFn, options) function is exposed as a property on the query function. It allows multiple queries to be executed within a single, non-interactive transaction. The first argument to transaction() , queriesOrFn , is either an array of queries or a non-async function that receives a query function as its argument and returns an array of queries. The array-of-queries case looks like this: import { neon } from '@neondatabase/serverless' ; const sql = neon ( process . env . DATABASE_URL ); const showLatestN = 10 ; const [ posts , tags ] = await sql .transaction ( [ sql `SELECT * FROM posts ORDER BY posted_at DESC LIMIT ${ showLatestN } ` , sql `SELECT * FROM tags` ] , { isolationLevel : 'RepeatableRead' , readOnly : true , } ); Or as an example of the function case: const [ authors , tags ] = await neon ( process . env . DATABASE_URL ) .transaction ((txn) => [ txn `SELECT * FROM authors` , txn `SELECT * FROM tags` , ]); The optional second argument to transaction() , options , has the same keys as the options to the ordinary query function — arrayMode , fullResults and fetchOptions — plus three additional keys that concern the transaction configuration. These transaction-related keys are: isolationMode , readOnly and deferrable . Note that options cannot be supplied for individual queries within a transaction. Query and transaction options must instead be passed as the second argument of the transaction() function. For example, this arrayMode setting is ineffective (and TypeScript won't compile it): await sql.transaction([sql('SELECT now()', [], { arrayMode: true })]) . Instead, use await sql.transaction([sql('SELECT now()')], { arrayMode: true }) . isolationMode This option selects a Postgres transaction isolation mode . If present, it must be one of ReadUncommitted , ReadCommitted , RepeatableRead , or Serializable . readOnly If true , this option ensures that a READ ONLY transaction is used to execute the queries passed. This is a boolean option. The default value is false . deferrable If true (and if readOnly is also true , and isolationMode is Serializable ), this option ensures that a DEFERRABLE transaction is used to execute the queries passed. This is a boolean option. The default value is false . For additional details, see transaction(...) function . Using transactions with JWT self-verification When using Row-Level Security (RLS) to secure backend SQL with the Neon serverless driver, you may need to set JWT claims within a transaction context. This is particularly useful for custom JWT verification flows in backend APIs, where you want to ensure user-specific access to rows according to RLS policies. Here's an example of how to use the transaction() function with self-verified JWT claims: import { neon } from '@neondatabase/serverless' ; // Example JWT verification function, typically in a separate auth utilitiy file (implement according to your auth provider) async function verifyJWT (jwtToken , jwksURL) { // Your JWT verification logic here // This should return the decoded payload return { payload : { sub : 'user123' , email : 'user@example.com' } }; } const sql = neon ( process . env . DATABASE_URL ); // Get JWT token from request headers or context const jwtToken = req . headers . authorization ?.replace ( 'Bearer ' , '' ); const jwksURL = process . env . JWKS_URL ; // Your JWKS endpoint // Verify the JWT and extract claims const { payload } = await verifyJWT (jwtToken , jwksURL); const claims = JSON .stringify (payload); // Use transaction to set JWT claims and query data const [ , my_table ] = await sql .transaction ([ sql `SELECT set_config('request.jwt.claims', ${ claims } , true)` , sql `SELECT * FROM my_table` , ]); important When using JWT self-verification with RLS, ensure your database connection string uses a role that does not have the BYPASSRLS attribute. Avoid using the neondb_owner role in your connection string, as it bypasses Row-Level Security policies. This pattern allows you to: Verify JWTs using your own authentication logic Set the JWT claims in the database session context Access JWT claims in your RLS policies Execute multiple queries within a single transaction while maintaining the auth context Use the driver over WebSockets The Neon serverless driver supports the Pool and Client constructors for querying over WebSockets. The Pool and Client constructors, provide session and transaction support, as well as node-postgres compatibility. You can find the API guide for the Pool and Client constructors in the node-postgres documentation. Consider using the driver with Pool or Client in the following scenarios: You already use node-postgres in your code base and would like to migrate to using @neondatabase/serverless . You are writing a new code base and want to use a package that expects a node-postgres-compatible driver. Your backend service uses sessions / interactive transactions with multiple queries per connection. You can use the Neon serverless driver in the same way you would use node-postgres with Pool and Client . Where you usually import pg , import @neondatabase/serverless instead. Node.js Prisma Drizzle-ORM Vercel Edge Function Vercel Serverless Function import { Pool } from '@neondatabase/serverless' ; const pool = new Pool ({ connectionString : process . env . DATABASE_URL }); const posts = await pool .query ( 'SELECT * FROM posts WHERE id =$1' , [postId]); pool .end (); Pool and Client usage notes In Node.js and some other environments, there's no built-in WebSocket support. In these cases, supply a WebSocket constructor function. import { Pool , neonConfig } from '@neondatabase/serverless' ; import ws from 'ws' ; neonConfig .webSocketConstructor = ws; In serverless environments such as Vercel Edge Functions or Cloudflare Workers, WebSocket connections can't outlive a single request. That means Pool or Client objects must be connected, used and closed within a single request handler. Don't create them outside a request handler; don't create them in one handler and try to reuse them in another; and to avoid exhausting available connections, don't forget to close them. For examples that demonstrate these points, see Pool and Client . Advanced configuration options For advanced configuration options, see neonConfig configuration , in the Neon serverless driver GitHub readme. Developing locally with the Neon serverless driver The Neon serverless driver enables you to query data over HTTP or WebSockets instead of TCP, even though Postgres does not natively support these connection methods. To use the Neon serverless driver locally, you must run a local instance of Neon's proxy and configure it to connect to your local Postgres database. For a step-by-step guide to setting up a local environment, refer to this community guide: Local Development with Neon . The guide demonstrates how to use a community-developed Docker Compose file to configure a local Postgres database and a Neon proxy service. This setup allows connections over both WebSockets and HTTP. Handling transient connection drops Like any cloud database service, Neon may occasionally experience brief connection drops during maintenance, updates, or network interruptions. When using the Neon serverless driver, especially over HTTP, you should implement retry logic to handle these transient errors gracefully. Here's a minimal retry example using the async-retry library with the HTTP driver: import { neon } from '@neondatabase/serverless' ; import retry from 'async-retry' ; const sql = neon ( process . env . DATABASE_URL ); const result = await retry ( async () => { return await sql `SELECT * FROM users WHERE id = ${ userId } ` ; } , { retries : 5 , factor : 2 , minTimeout : 1000 , randomize : true , } ); Example applications Explore the example applications that use the Neon serverless driver. UNESCO World Heritage sites app Neon provides an example application to help you get started with the Neon serverless driver. The application generates a JSON listing of the 10 nearest UNESCO World Heritage sites using IP geolocation (data copyright © 1992 – 2022 UNESCO/World Heritage Centre). There are different implementations of the application to choose from. Raw SQL + Vercel Edge Functions Demonstrates using raw SQL with Neon's serverless driver on Vercel Edge Functions Raw SQL via https + Vercel Edge Functions Demonstrates Neon's serverless driver over HTTP on Vercel Edge Functions Raw SQL + Cloudflare Workers Demonstrates using the Neon serverless driver on Cloudflare Workers and employs caching for high performance. Kysely + Vercel Edge Functions Demonstrates using kysely and kysely-codegen with Neon's serverless driver on Vercel Edge Functions Zapatos + Vercel Edge Functions Demonstrates using Zapatos with Neon's serverless driver on Vercel Edge Functions Neon + pgTyped on Vercel Edge Functions Demonstrates using pgTyped with Neon's serverless driver on Vercel Edge Functions Neon + Knex on Vercel Edge Functions Demonstrates using Knex with Neon's serverless driver on Vercel Edge Functions Ping Thing The Ping Thing application pings a Neon Serverless Postgres database using a Vercel Edge Function and shows the journey your request makes. You can read more about this application in the accompanying blog post: How to use Postgres at the Edge Ping Thing Ping a Neon Serverless Postgres database using a Vercel Edge Function to see the journey your request makes Neon serverless driver GitHub repository and changelog The GitHub repository and changelog for the Neon serverless driver are found here . References Fetch API node-postgres Drizzle-ORM Schema migration with Neon Postgres and Drizzle ORM kysely Zapatos Vercel Edge Functions Cloudflare Workers Use Neon with Cloudflare Workers Need help? Join our Discord Server to ask questions or see what others are doing with Neon. For paid plan support options, see Support . Previous Connect from any app Next Neon SQL Editor Last updated on October 10, 2025 Was this page helpful? Yes No Thank you for your feedback! On this page Install the Neon serverless driver Configure your Neon database connection Use the driver over HTTP Use the driver over WebSockets Developing locally with the Neon serverless driver Handling transient connection drops Example applications Neon serverless driver GitHub repository and changelog References Need help? Copy page as markdown Edit this page on GitHub Open in ChatGPT Neon Docs Neon A Databricks Company Neon status loading... Made in SF and the World Copyright Ⓒ 2022 – 2026 Neon, LLC Company About Blog Careers Contact Sales Partners Security Legal Privacy Policy Terms of Service DPA Subprocessors List Privacy Guide Cookie Policy Business Information Resources Docs Changelog Support Community Guides PostgreSQL Tutorial Startups Creators Social Discord GitHub x.com LinkedIn YouTube Compliance CCPA Compliant GDPR Compliant ISO 27001 Certified ISO 27701 Certified SOC 2 Certified HIPAA Compliant Compliance Guide Neon’s Sub Contractors Sensitive Data Terms Trust Center | 2026-01-13T08:48:04 |
https://dev.to/t/performance | Performance - 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 Performance Follow Hide Tag for content related to software performance. Create Post submission guidelines Articles should be obviously related to software performance in some way. Possible topics include, but are not limited to: Performance Testing Performance Analysis Optimising for performance Scalability Resilience But most of all, be kind and humble. 💜 Older #performance posts 1 2 3 4 5 6 7 8 9 … 75 … 246 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu SLMs, LLMs and a Devious Logic Puzzle Test Ben Santora Ben Santora Ben Santora Follow Jan 12 SLMs, LLMs and a Devious Logic Puzzle Test # llm # performance # testing 5 reactions Comments Add Comment 5 min read Observing Behavioral Anomalies in Web Applications Beyond Signature Scanners 0x7b 0x7b 0x7b Follow Jan 12 Observing Behavioral Anomalies in Web Applications Beyond Signature Scanners # monitoring # performance # security # testing Comments Add Comment 1 min read The Buy Button Is the Slowest Part of Most E Commerce Sites ar abid ar abid ar abid Follow Jan 13 The Buy Button Is the Slowest Part of Most E Commerce Sites # webdev # performance # frontend # ecommerce Comments Add Comment 3 min read I got tired of waiting for Gradle, so I built a runtime that runs Kotlin like Python. Srikar Sunchu Srikar Sunchu Srikar Sunchu Follow Jan 13 I got tired of waiting for Gradle, so I built a runtime that runs Kotlin like Python. # kotlin # performance # productivity # tooling 10 reactions Comments 1 comment 2 min read Moving from Nextjs to Qwik Jaime Jaime Jaime Follow Jan 12 Moving from Nextjs to Qwik # nextjs # qwik # javascript # performance Comments Add Comment 5 min read Stop Random Pod Scheduling: Master Kubernetes Affinity & Anti-Affinity with NGINX (Practical Guide for DevOps & SRE) Srinivasaraju Tangella Srinivasaraju Tangella Srinivasaraju Tangella Follow Jan 13 Stop Random Pod Scheduling: Master Kubernetes Affinity & Anti-Affinity with NGINX (Practical Guide for DevOps & SRE) # devops # kubernetes # performance # tutorial Comments Add Comment 4 min read Why Next.js Is Better Than Plain React for Modern Web Development Farhad Rahimi Klie Farhad Rahimi Klie Farhad Rahimi Klie Follow Jan 13 Why Next.js Is Better Than Plain React for Modern Web Development # nextjs # react # webdev # performance Comments Add Comment 3 min read Your WordPress Site Is Bleeding Memory — Here's How to Stop It Prakhar Prakhar Prakhar Follow Jan 12 Your WordPress Site Is Bleeding Memory — Here's How to Stop It # wordpress # webdev # performance # wordpressplugin Comments Add Comment 4 min read Hogo: Ignite Your Node.js Performance with Atomic Request Coalescing Mahmud Rahman Mahmud Rahman Mahmud Rahman Follow Jan 12 Hogo: Ignite Your Node.js Performance with Atomic Request Coalescing # node # performance # backend # javascript Comments Add Comment 2 min read How to Build SEO-Friendly Ecommerce Product Pages ar abid ar abid ar abid Follow Jan 12 How to Build SEO-Friendly Ecommerce Product Pages # frontend # performance # tutorial # webdev Comments Add Comment 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 Why Should We Optimize JSON for LLMs Del Rosario Del Rosario Del Rosario Follow Jan 12 Why Should We Optimize JSON for LLMs # json # llm # webdev # performance Comments Add Comment 5 min read Speculative Decoding: Cómo Acelerar LLMs 2.4x Sin Cambiar el Modelo Abdessamad Ammi Abdessamad Ammi Abdessamad Ammi Follow Jan 12 Speculative Decoding: Cómo Acelerar LLMs 2.4x Sin Cambiar el Modelo # llm # performance # mlop Comments Add Comment 4 min read O(1) Country Selection on a 3D Globe with GPU Picking and Hemisphere Detection Emmanuel Emmanuel Emmanuel Follow Jan 11 O(1) Country Selection on a 3D Globe with GPU Picking and Hemisphere Detection # threejs # angular # performance # algorithms Comments Add Comment 11 min read I Added a Cache and the System Got Slower: The Hidden Cost of Caching yusuf yonturk yusuf yonturk yusuf yonturk Follow Jan 11 I Added a Cache and the System Got Slower: The Hidden Cost of Caching # programming # performance # backend # redis 1 reaction Comments Add Comment 3 min read Small Language Models Are Eating the World (And Why That's Great) SATINATH MONDAL SATINATH MONDAL SATINATH MONDAL Follow Jan 11 Small Language Models Are Eating the World (And Why That's Great) # ai # edge # performance # mobile Comments Add Comment 13 min read Choosing the Right LLM for the Umbraco CMS Developer MCP: An Quick Cost and Performance Analysis Phil Whittaker Phil Whittaker Phil Whittaker Follow Jan 11 Choosing the Right LLM for the Umbraco CMS Developer MCP: An Quick Cost and Performance Analysis # llm # mcp # performance Comments Add Comment 6 min read [Learning Documents] [Golang] Go 1.19 Sort is Faster Evan Lin Evan Lin Evan Lin Follow Jan 11 [Learning Documents] [Golang] Go 1.19 Sort is Faster # algorithms # go # performance Comments Add Comment 1 min read Book Review: Ecosystem Competition Strategy Evan Lin Evan Lin Evan Lin Follow Jan 11 Book Review: Ecosystem Competition Strategy # discuss # react # performance Comments Add Comment 10 min read High-performance GPUs or TPUs vs CPUs Neweraofcoding Neweraofcoding Neweraofcoding Follow Jan 11 High-performance GPUs or TPUs vs CPUs # architecture # machinelearning # performance # ai Comments Add Comment 2 min read Angular State Management: Signals vs Simple Properties - Which Should I Use? Mohamed Fri Mohamed Fri Mohamed Fri Follow Jan 11 Angular State Management: Signals vs Simple Properties - Which Should I Use? # discuss # performance # typescript # angular Comments Add Comment 1 min read Dynamic Arrays: Low-Level Implementation & Amortized Analysis ali ehab algmass ali ehab algmass ali ehab algmass Follow Jan 11 Dynamic Arrays: Low-Level Implementation & Amortized Analysis # algorithms # computerscience # performance Comments Add Comment 4 min read Unsafe Rust: When and Why Aviral Srivastava Aviral Srivastava Aviral Srivastava Follow Jan 11 Unsafe Rust: When and Why # learning # performance # rust Comments Add Comment 8 min read Why Fast Page Loads Don’t Always Mean Fast User Experience ar abid ar abid ar abid Follow Jan 11 Why Fast Page Loads Don’t Always Mean Fast User Experience # performance # webdev # javascript # serverless 1 reaction Comments Add Comment 2 min read HTTP Caching Explained (The Way I Learned It in Production) Nishar Arif Nishar Arif Nishar Arif Follow Jan 11 HTTP Caching Explained (The Way I Learned It in Production) # beginners # webdev # tutorial # performance 1 reaction Comments Add Comment 4 min read loading... trending guides/resources I built an app in every frontend framework TOON vs JSON: A Modern Data Format Showdown I Replaced Redis with PostgreSQL (And It's Faster) Choosing the Right Chunking Strategy: A Comprehensive Guide to RAG Optimization Choosing Between Vue.js and Next.js: A Practical Guide for Developers Are We Losing Our Manners in Software Development? libmalloc, jemalloc, tcmalloc, mimalloc - Exploring Different Memory Allocators Why Your Vue App Is Reactive Too Much (and How to Fix It) Understanding Hetzner SSD VPS Performance and Best Practices JSON vs MessagePack vs Protobuf in Go — My Real Benchmarks and What They Mean in Production Why Edge Computing Forced Me to Write Better Code (And Why That's the Future) Anthropic Bought Bun: Here's What It Really Means for Us How to track Claude Code usage + analytics Best LLM inference providers. Groq vs. Cerebras: Which Is the Fastest AI Inference Provider? Why it's time to ditch UUIDv4 and switch to UUIDv7! I tested the top 3 AI coding models on real engineering problems. The results surprised me. GPUI Component: Because Desktop Apps Shouldn't Make You Cry 🧹 How to Clear Cache in Windows Using PowerShell (Complete Guide) Image optimization and compression techniques for ultra-fast Laravel/PHP image uploads and display C# Performance Optimization: Using Span<T> and stackalloc to Eliminate Allocations 💎 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:48:04 |
https://pypistats.org/top | PyPI Download Stats PyPI Stats Search All packages Top packages Track packages Most downloaded PyPI packages Most downloaded past day . Most downloaded past week . Most downloaded past month . 1 boto3 54,370,617 2 urllib3 41,935,581 3 botocore 37,414,448 4 certifi 37,019,131 5 typing-extensions 36,193,663 6 requests 35,522,479 7 packaging 34,658,162 8 idna 34,169,779 9 setuptools 33,487,113 10 charset-normalizer 33,269,985 11 aiobotocore 27,940,776 12 python-dateutil 26,821,464 13 grpcio-status 25,977,186 14 six 25,595,118 15 numpy 24,136,309 16 pyyaml 23,004,519 17 s3transfer 22,542,331 18 cryptography 22,265,778 19 cffi 21,272,868 20 pydantic 21,015,443 1 boto3 367,954,642 2 urllib3 264,574,781 3 botocore 252,439,887 4 typing-extensions 233,368,702 5 certifi 232,219,114 6 requests 225,125,618 7 packaging 215,688,373 8 idna 214,707,835 9 charset-normalizer 209,333,262 10 setuptools 205,850,500 11 aiobotocore 185,613,908 12 grpcio-status 177,038,800 13 python-dateutil 170,120,078 14 six 159,970,556 15 numpy 152,276,063 16 s3transfer 146,829,262 17 cryptography 144,106,755 18 pyyaml 142,354,411 19 cffi 137,234,059 20 pydantic 131,609,962 1 boto3 1,333,291,150 2 urllib3 1,024,776,166 3 botocore 938,356,220 4 typing-extensions 903,156,616 5 certifi 884,762,356 6 requests 882,806,271 7 idna 834,713,475 8 aiobotocore 815,185,287 9 charset-normalizer 815,079,392 10 packaging 805,417,703 11 setuptools 792,032,051 12 grpcio-status 696,859,756 13 python-dateutil 675,642,283 14 six 630,115,901 15 numpy 596,477,661 16 s3transfer 583,012,453 17 s3fs 536,037,214 18 cryptography 526,644,905 19 pyyaml 518,345,237 20 fsspec 513,970,759 API About FAQs Hosted by The PSF | 2026-01-13T08:48:04 |
https://choosealicense.com/licenses/mit/ | MIT License | Choose a License Home / Licenses MIT License A short and simple permissive license with conditions only requiring preservation of copyright and license notices. Licensed works, modifications, and larger works may be distributed under different terms and without source code. Permissions Conditions Limitations Commercial use Distribution Modification Private use License and copyright notice Liability Warranty MIT License Copyright (c) [year] [fullname] 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. Copy license text to clipboard Suggest this license Make a pull request to suggest this license for a project that is not licensed . Please be polite: see if a license has already been suggested, try to suggest a license fitting for the project’s community , and keep your communication with project maintainers friendly. How to apply this license Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. Optional steps Add MIT to your project’s package description, if applicable (e.g., Node.js , Ruby , and Rust ). This will ensure the license is displayed in package directories. Source Who’s using this license? Babel .NET Rails About Terms of Service Help improve this page The content of this site is licensed under the Creative Commons Attribution 3.0 Unported License . Curated with ❤️ by GitHub, Inc. and You! | 2026-01-13T08:48:04 |
https://web.dev/learn/html/dialog/ | Dialog | web.dev Skip to main content Resources Web Platform Dive into the web platform, at your pace. HTML CSS JavaScript User experience Learn how to build better user experiences. Performance Accessibility Identity Learn Get up to speed on web development. Learn HTML Learn CSS Learn JavaScript Learn Performance Learn Accessibility More courses Additional resources Explore content collections, patterns, and more. AI and the web Explore PageSpeed Insights Patterns Podcasts & shows Developer Newsletter About web.dev Baseline How to use Baseline Blog Case Studies / English Deutsch Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 Sign in Resources Privacy Accessibility HTML Images Responsive Design Forms PWA CSS Performance Testing JavaScript Resources More Privacy Accessibility HTML Images Responsive Design Forms PWA CSS Performance Testing JavaScript Baseline How to use Baseline Blog Case Studies Welcome to Learn HTML! Overview of HTML Document structure Metadata Semantic HTML Headings and sections Attributes Text basics Links Lists Navigation Tables Forms Images Audio and Video Template, slot, and shadow HTML APIs Focus Other inline text elements Details and summary Dialog Conclusion and next steps Web Platform HTML CSS JavaScript User experience Performance Accessibility Identity Learn Learn HTML Learn CSS Learn JavaScript Learn Performance Learn Accessibility More courses Additional resources AI and the web Explore PageSpeed Insights Patterns Podcasts &amp; shows Developer Newsletter About web.dev web.dev Resources HTML Dialog Stay organized with collections Save and categorize content based on your preferences. The dialog element is a useful element for representing any kind of dialog in HTML, find out how it works. A modal dialog is a special type of pop-up box on a web page, that interrupts the user to focus onto itself. There are some valid use cases for popping up a dialog , but take great consideration should be made before doing so. Modal dialogs force users to focus on specific content, and, temporarily at least, ignore the rest of the page. Dialogs can be either modal (only the content in the dialog can be interacted with) or non-modal (it's still possible to interact with content outside of the dialog). Modal dialogs are displayed on top of the rest of the page content. The rest of the page is inert and, by default, obscured by a semi-transparent backdrop. The semantic HTML <dialog> element to create a dialog comes with semantics, keyboard interactions, and all the properties and methods of the HTMLDialogElement interface. Modal dialogs Here is an example of a modal <dialog> . Open the dialog with the "Open modal dialog" button. Once opened, there are three ways to close the dialog: the escape key, submitting a form with a button that has the formmethod="dialog" set (or if the form itself has method="dialog" set), and the HTMLDialogElement.close() method. The HTMLDialogElement has three main methods, along with all the methods inherited from HTMLElement . dialog . show () /* opens the dialog */ dialog . showModal () /* opens the dialog as a modal */ dialog . close () /* closes the dialog */ Because this <dialog> was opened with the HTMLDialogElement.showModal() method, it is a modal dialog. Opening a modal dialog deactivates and obscures everything other than the dialog itself. If you hover over the UI outside of the dialog, you'll note all the elements are behaving as if pointer-events: none; was set; even the button that opens the dialog doesn't react to interactions. When the dialog is opened, focus moves into the dialog. Focus is set on the first element in the sequential keyboard navigation order within that dialog. If you hit the tab key repeatedly, only the content within the dialog can get focus while the modal dialog is open. Everything outside of the modal dialog is inert as long as the dialog is open. When a dialog is closed, modal or not, focus is returned to the element that opened the dialog. Avoid programmatically opening a dialog without a user action. If you must, make sure that focus is put back where it was prior to the dialog opening, especially if the user dismisses the dialog without interacting with it. There is a global inert attribute that can be used to disable an element and all of its descendants, other than any active dialog. When a modal dialog is opened using showModal() , the inertness or deactivation comes with it; the attribute isn't explicitly set. The backdrop that obscures everything other than the dialog can be styled using the ::backdrop pseudo-element. The backdrop is only displayed when a <dialog> is displayed with the .showModal() method. This pseudo-element matches all the backdrops, including the one displayed when the FullScreen API is used, such as when viewing a video in full-screen mode which doesn't have the same aspect ratio as the screen or monitor. Non-modal dialogs The HTMLDialogElement.show() similarly opens a dialog, but without adding a backdrop or causing anything to become inert. The escape key does not close non-modal dialogs. Because of this, it is even more important to include a method of closing the non-modal dialog. In doing so, if the closer is outside the dialog, realize the focus will go to the element that opened the dialog, which may not be the best user experience. While a button to close the dialog is not officially required by the specification, consider it as required. The escape key will close a modal dialog, but not a non-modal one. A visible button that is able to receive focus improves accessibility and user experience. Closing a dialog You don't need the HTMLDialogElement.close() method to close a dialog. You don't need JavaScript at all. To close the <dialog> without JavaScript, include a form with a dialog method by either setting method="dialog" on the <form> or formmethod="dialog" on the button. When a user submits with the dialog method, the state of user-entered data is maintained. While there is a submit event—the form goes through constraint validation (unless novalidate is set)—the user data is neither cleared nor submitted. A close button without JavaScript can be written as: <dialog open> <form method="dialog"> <button type="submit" autofocus>close</button> </form> </dialog> You may have noticed the autofocus attribute set on the close <button> in this example. Elements with autofocus attribute set within a <dialog> will not receive focus on page load (unless the page is loaded with the dialog visible). They will, however, get focus when the dialog is opened. By default, when a dialog is opened, the first focusable element within the dialog will receive focus unless a different element within the dialog has the autofocus attribute set. Setting the autofocus attribute on the close button ensures it receives focus when the dialog is opened. But including autofocus within a <dialog> should only be done with much consideration. All the elements in the sequence coming before the autofocused element are skipped. We discuss this attribute further in the focus lesson . The HTMLDialogElement interface includes a returnValue property. Submitting a form with a method="dialog" sets the returnValue to the name , if any, of the submit button used to submit the form. If we had written <button type="submit" name="toasty">close</button> , the returnValue would be toasty . When a dialog is opened, the boolean open attribute is present, meaning the dialog is active and can be interacted with. When a dialog is opened by adding the open attribute rather than with .show() or .showModal() , the dialog will be modal-less. The HTMLDialogElement.open property returns true or false , depending on whether the dialog is available for interaction—not whether it is modal or not. While JavaScript is the preferred method of opening a dialog, including the open attribute on page load, and then removing it with .close() , can help ensure the dialog is available even when JavaScript is not. Additional details Don't use tabindex The element that is activated to open the dialog and the close button contained in it (and possibly other content) can receive focus and are interactive. The <dialog> element is not interactive and doesn't receive focus. Do not add the tabindex property to the dialog itself. ARIA roles The implicit role is dialog . If the dialog is a confirmation window communicating an important message that requires a confirmation or other user response, set role="alertdialog" . The dialog should also have an accessible name. If visible text can provide for the accessible name, add aria-labelledby="idOfLabelingText" . CSS defaults Note that browsers provide default styling for dialog . Firefox, Chrome, and Edge set color: CanvasText; background-color: Canvas; and Safari sets color: black; background-color: white; in their user-agent stylesheets. The color is inherited from dialog and not from body or :root , which may be unexpected. The background-color property is not inherited. Check your understanding Test your knowledge of the dialog element. How do you style the area behind the dialog? With the ::background pseudo-element. Try again. With the ::backdrop pseudo-element. Correct! With the background property. Try again. Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates. Last updated 2023-02-21 UTC. [[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2023-02-21 UTC."],[],[]] web.dev web.dev We want to help you build beautiful, accessible, fast, and secure websites that work cross-browser, and for all of your users. This site is our home for content to help you on that journey, written by members of the Chrome team, and external experts. Contribute File a bug See open issues Related Content Chrome for Developers Chromium updates Case studies Podcasts & shows Follow @ChromiumDev on X YouTube Chrome for Developers on LinkedIn RSS Terms Privacy Manage cookies English Deutsch Español – América Latina Français Indonesia Italiano Polski Português – Brasil Tiếng Việt Türkçe Русский עברית العربيّة فارسی हिंदी বাংলা ภาษาไทย 中文 – 简体 中文 – 繁體 日本語 한국어 | 2026-01-13T08:48:04 |
https://github.com/skills/secure-repository-supply-chain | GitHub - skills/secure-repository-supply-chain: Secure your supply chain, understand dependencies in your environment, know about vulnerabilities in those dependencies and patch them Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} skills / secure-repository-supply-chain Public template Notifications You must be signed in to change notification settings Fork 176 Star 170 Secure your supply chain, understand dependencies in your environment, know about vulnerabilities in those dependencies and patch them License MIT license 170 stars 176 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 1 Pull requests 5 Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Security Insights skills/secure-repository-supply-chain main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 36 Commits .github .github code code .gitignore .gitignore LICENSE LICENSE README.md README.md View all files Repository files navigation README Code of conduct Contributing MIT license Security Secure your repository's supply chain Secure your supply chain, understand dependencies in your environment, know about vulnerabilities in those dependencies and patch them. Welcome GitHub helps you secure your supply chain, from understanding the dependencies in your environment, to knowing about vulnerabilities in those dependencies and patching them. Who this is for : Developers, DevOps Engineers, Site Reliability Engineers, Security experts What you'll learn : How to view repository dependencies, view Dependabot alerts, and enable Dependabot security and version updates What you'll build : Repository dependencies, Dependabot alerts, pull requests to fix dependencies and version updates Prerequisites : None Timing : This course can be completed in under an hour In this course, you will explore: Dependency graph Dependency alerts Dependency security updates Dependency versions updates How to start this course Right-click Start course and open the link in a new tab. In the new tab, most of the prompts will automatically fill in for you. For owner, choose your personal account or an organization to host the repository. We recommend creating a public repository, as private repositories will use Actions minutes . Scroll down and click the Create repository button at the bottom of the form. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README. Get help: Post in our discussion board • Review the GitHub status page © 2024 GitHub • Code of Conduct • MIT License About Secure your supply chain, understand dependencies in your environment, know about vulnerabilities in those dependencies and patch them Topics security skills-course skills-exercise Resources Readme License MIT license Code of conduct Code of conduct Contributing Contributing Security policy Security policy Uh oh! There was an error while loading. Please reload this page . Activity Custom properties Stars 170 stars Watchers 9 watching Forks 176 forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 17 + 3 contributors Languages C# 98.3% JavaScript 1.7% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:48:04 |
https://www.fiscal.treasury.gov/prompt-payment/interest.html | Prompt Payment: Interest Calculator Skip Navigation Official website of the United States Government U.S. Department of the Treasury Prompt Payment Menu A to Z Index Search Prompt Payment A program of the Bureau of the Fiscal Service Prompt Payment Menu Home Resources Accelerated Payments Discounts on Payments Discount Calculator Simple Interest Calculator Monthly Compounding Interest Calculator Interest Rates How to Pay a Federal Agency's Credit Card Bill FAQs Contact Us Related Links Federal Acquisition Regulations 52.232-25 FAR EFT Final Rule Federal Travel Regulation Final Rule Current Value of Funds Rate Tip: To get back to the Fiscal Service home page, click or tap the logo in the upper left corner. Fiscal Service A-Z Index This A–Z Index lists all Fiscal Service content. You can also view just the Programs & Services . A B C D E F G H I J K L M N O P Q R S T U V W X Y Z A About the Fiscal Service Accessibility Statement ACH - Automated Clearing House ACH Payment Schedule : Recurring Benefits and Military Active Duty, Reserves, and Benefits AWG - Administrative Wage Garnishment ARM - Agency Relationship Management APG - Agency Priority Goal America's Finance Guide Annual Fiscal Service Letters Annual Report, United States Government Anti-Harassment Policy Statement ASAP - Automated Standard Application for Payment B Bank Management System Budget Surplus/Deficit Publications Bulk Data Formats for Salary and Vendor/Miscellaneous Payments Business & Institutions, Services for C CAS - Card Acquiring Service Careers CMIA - Cash Management Improvement Act CARS - Central Accounting Reporting System CRS - Centralized Receivables Service Certifying Officer Training CFS - Consolidated Financial Statements of the United States Government Check Claims Check Payment Formats Check Reclamation Guide: The Gold Book CIR - Collections Information Repository Circular 176: Depositaries and Financial Agents of the Federal Government (31 CFR 202) Circular 570: Treasury’s Approved Listing of Sureties Collateral Combined Statement of Receipts, Outlays, and Balances of the United States Government Contact the Fiscal Service Credit Gateway Credit Reform Accounting Cross-Servicing (Debt Collection) Current Value of Funds Rate D Data Transparency DCIA - Debt Collection Improvement Act (1996) DDM - Debt Management DNP – Do Not Pay DTS - Daily Treasury Statement Debit Card Debit Gateway Digital Payouts (Digital Pay) Direct Deposit (Electronic Funds Transfer) Direct Express ® E EagleCash eCollections eCommerce Collections Electronic Check Processing EFTPS - Electronic Federal Tax Payment System Electronic Funds Transfer EEO Complaint Process EEO Policy Statement EFT Payment Formats E-Mail Notification Service Exchange Rates (Treasury Reporting Rates of Exchange) EZPay Events F FAST - Federal Accounts Symbols and Titles (FAST Book) FEDInvest – FedInvest - Federal Investments Program Federal Borrowings Program Federal Disbursement Services Federal Tax Application Federal Tax Collection Service FIT - Financial Innovation and Transformation Financial Management and Standardization Financial Management Standards Financial Management Quality Service Management Office (FM QSMO) FMSC – Financial Management Standards Committee Financial Report of the United States Government Fiscal Service Data Registry Fiscal Service Locations FM Vision FOIA - Freedom of Information Act Foreign Claims (Unpaid) Forms Franchise Services Fund Balance With Treasury G G-Invoicing General Fund General Lockbox Network General Public, Services for Gifts to reduce the Public Debt Gifts to the United States Government Gold Book (Reclamations Procedures) Go Direct Gold Report Government Agencies, Services for GWA – Governmentwide Accounting GFRS – Governmentwide Financial Report System GTAS – Governmentwide Treasury Account Symbol Adjusted Trial Balance System Governmentwide Debt Collection Green Book H History of the Fiscal Service Human Resources I IFCS - Intragovernmental Fiduciary Confirmation System IPAC - Intragovernmental Payment and Collection System IPP - Invoice Processing Platform Imprest Fund IRS Lockbox Interest Calculators International Treasury Services (ITS.gov) J Judgment Fund K KFC - Kansas City Financial Center (now Federal Disbursement Services) KFC Dispatch (now Payment News) L LPA - Legislative and Public Affairs M MMC - Military Meal Checks Program Modernization, Innovation, and Payment Resolution (now Payment Integrity and Resolution Services) MSPD - Monthly Statement of the Public Debt MTS - Monthly Treasury Statement N National Payment Center of Excellence (NPCE) (now Federal Disbursement Services) National Payment Integrity and Resolution Center (now Payment Integrity and Resolution Services) NPCE Payment News (now Federal Disbursement Services) Navy Cash/Marine Cash News from the Fiscal Service O OTCnet P PIRS - Payment Integrity and Resolution Services PACER - Payments, Claims and Enhanced Reconciliation PAM - Payment Automation Manager PICOE - Payment Integrity Center PFC - Philadelphia Financial Center (now Payment Integrity and Resolution Services) Pay.gov Payment Formats PIR - Payment Information Repository PFC Journal Press Releases Private Relief Act Privacy and Civil Liberties Impact Assessments Privacy Policy and Legal Notices Prompt Payment Public Affairs, Legislative and (LPA) Public, Services for the Publications, Fiscal Service R Rates & Sureties Reclamations, Checks Reference & Guidance RFC - Regional Financial Center Reports S SAM - Shared Accounting Module SGL/USSGL - United States Standard General Ledger SLGS – State and Local Government Securities SPS - Secure Payment System Savings Bonds Shared Services Standard General Ledger, United States (USSGL) State and Local Government Securities Overview State and Local Tax Withholding Statements Status Report of U.S. Treasury-Owned Gold Stored Value Card SDA – Summary Debt Accounting Surety Bonds Systems Access T TIN - Taxpayer Identifying Number TRO - Tax Refund Offset Tax Refund Offset FAQ Training Opportunities TAS - Treasury Account Symbol TAR - Treasury Annual Report Appendix Treasury Bank Mentor-Protégé Program Treasury Bulletin TCIS - Treasury Check Information System Treasury Check Security Features TCMM - Treasury Collateral Management & Monitoring TFM - Treasury Financial Manual TMA - Treasury Managed Accounts TOP - Treasury Offset Program TFX - Treasury Financial Experience TROR - Treasury Report on Receivables TGA - Treasury General Account Treasury Securities and Programs TSS - Treasury Securities Services U Unclaimed Assets, FAQ U.S. Debit Card USA Spending USSGL - United States Standard General Ledger Unpaid Foreign Claims V Vendor Payment Guidance Browser Not Supported Some features of this site will not work on Internet Explorer 8 and older. Please use another browser, or upgrade to a more recent version of Internet Explorer. JavaScript Disabled Some features of this site will not work with JavaScript disabled. Please enable JavaScript to use all features. Bureau of the Fiscal Service Prompt Payment Simple Daily Calculator Simple Daily Interest The following on-line calculator allows you to automatically determine the amount of simple daily interest owed on payments made after the payment due date. To use this calculator you must enter the numbers of days late, the amount of the invoice in which payment was made late, and the Prompt Payment interest rate, which is pre-populated in the box. If a payment is less than 31 days late, use the Simple Daily Interest Calculator. If a payment is more than a month late, use the Monthly Compounding Interest Calculator . Please enter the principal amount: Please enter the number of days late: Please enter the Prompt Payment interest rate: Calculate Results: You owe the vendor $ in interest. Your total payment to the vendor is $ The Formula This is the formula the calculator uses to determine simple daily interest: P(r/360*d) P is the amount of principal or invoice amount; r is the Prompt Payment interest rate; and d is the number of days for which interest is being calculated. For example, if payment is due on April 1 and the payment is not made until April 11, a simple interest calculation will determine the amount of interest owed to the vendor for the late payment. Using the formula, an invoice in the amount of $1,500 paid 10 days late and at an interest rate of 6.625% would be calculated as follows: $1,500 (.066/360*10) = $2.75. Last modified 12/31/25 Prompt Payment A program of the Bureau of the Fiscal Service Prompt Payment Menu Home Resources Accelerated Payments Discounts on Payments Discount Calculator Simple Interest Calculator Monthly Compounding Interest Calculator Interest Rates How to Pay a Federal Agency's Credit Card Bill FAQs Contact Us Related Links Federal Acquisition Regulations 52.232-25 FAR EFT Final Rule Federal Travel Regulation Final Rule Current Value of Funds Rate The General Public Government Agencies Business & Institutions News Reports Forms Reference Training Events Careers About Mailing Lists Contact Twitter LinkedIn Facebook YouTube RSS Feeds Bureau of the Fiscal Service 2025 Accessibility Statement | Data Quality | Freedom of Information Act | Privacy Policy | Privacy Impact Assessments English is the official and authoritative version of all federal information. Fiscal Service Sites Direct Express® Go Direct® TreasuryDirect.gov Treasury Hunt EFTPS.gov Pay.gov Administrative Resource Center (ARC) FiscalData.Treasury.gov USAspending.gov TFX.treasury.gov Treasury Bureaus The Alcohol and Tobacco Tax and Trade Bureau Bureau of Engraving and Printing Community Development Financial Institutions Fund Financial Crimes Enforcement Network (FinCen) Internal Revenue Service Office of the Comptroller of the Currency U.S. Mint More Government Sites USA.gov USAJOBS.gov OPM.gov MyMoney.gov Data.gov Regulations.gov PaymentAccuracy.gov No Fear Act Vote.gov | 2026-01-13T08:48:04 |
https://addons.mozilla.org/pl/firefox/addon/rentgen/versions/ | Historia wersji dodatku Rentgen — 11 wersji — dodatki do Firefoksa (pl) Dodatki do przeglądarki Firefox Rozszerzenia Motywy Więcej… do Firefoksa Słowniki i pakiety językowe Inne strony Dodatki na Androida Zaloguj się Wyszukaj Wyszukaj Historia wersji dodatku Rentgen — 11 wersji Rentgen Autor: “Internet. Time to act!” Foundation Ocena: 5/5 5 gwiazdek/5 5 12 4 0 3 0 2 0 1 0 Historia wersji dodatku Rentgen — 11 wersji Zachowaj ostrożność podczas używania starych wersji! Są one wyświetlane w celach testowych i historycznych. Zawsze powinno używać się najnowszej wersji dodatku. Najnowsza wersja Wersja 0.2.4 Data wydania: 23 gru 2025 — 9,55 MB Działa z: firefox 91.0.0 i nowsze Licencja kodu źródłowego: Tylko GNU General Public License v3.0 Pobierz Firefoksa i to rozszerzenie Pobierz plik Poprzednie wersje Wersja 0.2.2 Data wydania: 14 gru 2025 — 9,55 MB Działa z: firefox 91.0.0 i nowsze Licencja kodu źródłowego: Tylko GNU General Public License v3.0 Pobierz plik Wersja 0.2.1 Data wydania: 24 paź 2025 — 9,55 MB Działa z: firefox 91.0.0 i nowsze Licencja kodu źródłowego: Tylko GNU General Public License v3.0 Pobierz plik Wersja 0.1.10 Data wydania: 25 wrz 2022 — 9,54 MB Działa z: firefox 91.0.0 i nowsze Generowana treść maila została wzbogacona o kilka nowych podstaw prawnych Licencja kodu źródłowego: Tylko GNU General Public License v3.0 Pobierz plik Wersja 0.1.9 Data wydania: 12 wrz 2022 — 9,54 MB Działa z: firefox 91.0.0 i nowsze Licencja kodu źródłowego: Tylko GNU General Public License v3.0 Pobierz plik Wersja 0.1.8 Data wydania: 15 lip 2022 — 9,57 MB Działa z: firefox 91.0.0 i nowsze Licencja kodu źródłowego: Tylko GNU General Public License v3.0 Pobierz plik Wersja 0.1.7 Data wydania: 15 lip 2022 — 9,57 MB Działa z: firefox 91.0.0 i nowsze Licencja kodu źródłowego: Tylko GNU General Public License v3.0 Pobierz plik Wersja 0.1.6 Data wydania: 15 lip 2022 — 9,57 MB Działa z: firefox 91.0.0 i nowsze Licencja kodu źródłowego: Tylko GNU General Public License v3.0 Pobierz plik Wersja 0.1.5 Data wydania: 15 lip 2022 — 9,57 MB Działa z: firefox 91.0.0 i nowsze Licencja kodu źródłowego: Tylko GNU General Public License v3.0 Pobierz plik Wersja 0.1.4 Data wydania: 14 lip 2022 — 8,13 MB Działa z: firefox 91.0.0 i nowsze Licencja kodu źródłowego: Tylko GNU General Public License v3.0 Pobierz plik Wersja 0.1.3 Data wydania: 10 lip 2022 — 7,68 MB Działa z: firefox 91.0.0 i nowsze Licencja kodu źródłowego: Tylko GNU General Public License v3.0 Pobierz plik Strona domowa Mozilli Dodatki O serwisie Blog dodatków do Firefoksa Warsztat rozszerzeń Strefa autora Zasady programistów Blog społeczności Forum Zgłoś błąd Wytyczne recenzji Przeglądarki Desktop Mobile Enterprise Produkty Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Prywatność Ciasteczka Kwestie prawne O ile nie wskazano inaczej , treść tej strony jest dostępna na warunkach licencji Creative Commons Attribution Share-Alike w wersji 3.0 lub nowszej. Zmień język Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T08:48:04 |
https://addons.mozilla.org/he/firefox/addon/rentgen/ | Rentgen – קבלת הרחבה זו עבור 🦊 Firefox (he) תוספות לדפדפן Firefox הרחבות ערכות נושא עוד… עבור Firefox מילונים וחבילות שפה אתרי דפדפנים אחרים תוספות עבור Android כניסה חיפוש חיפוש Rentgen “Internet. Time to act!” Foundation מאת Rentgen to wtyczka, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. 5 (12 סקירות) 5 (12 סקירות) 216 משתמשים 216 משתמשים הורדת Firefox וקבלת ההרחבה הורדת קובץ נתוני העל של ההרחבה צילומי מסך על אודות הרחבה זו Rentgen to wtyczka dla przeglądarek opartych o Firefoxa, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. Więcej informacji: https://www.internet-czas-dzialac.pl/odcinek-33-wtyczka-rentgen Funkcje Rentgena: analiza ruchu sieciowego generowanego przez stronę internetową; wizualizacja danych przekazanych do podmiotów trzecich przez odwiedzaną stronę (historia przeglądania użytkownika oraz jego ciasteczka); przygotowywanie zrzutów ekranów narzędzi deweloperskich będących dowodem przekazanych danych do podmiotów trzecich; pomoc w oszacowaniu potencjalnych obszarów roboczych względem zgodności z RODO; generowanie raportu lub treści maila, który można wysłać do administratora oraz Urzędu Ochrony Danych Osobowych. Kod źródłowy הערות המפתח Jeżeli uważasz, że wtyczka Rentgen okazała się przydatna, zostaw nam recenzję. Jeżeli znalazłeś błąd lub masz pomysł na ulepszenie Rentgena, napisz do nas maila: kontakt@internet-czas-dzialac.pl מדורג 5 על־ידי 12 סוקרים יש להתחבר כדי לדרג הרחבה זו אין דירוגים עדיין דירוג הכוכבים נשמר 5 12 4 0 3 0 2 0 1 0 קריאת כל 12 הסקירות הרשאות ונתונים הרשאות נדרשות: קריאה ועריכה של הגדרות פרטיות שליטה בהגדרות המתווך של הדפדפן גישה לנתונים שלך מכל האתרים איסוף נתונים: המפתח אומר שהרחבה זו אינה דורשת איסוף נתונים. מידע נוסף מידע נוסף קישורים לתוספת דף הבית אתר תמיכה דוא״ל לתמיכה גרסה 0.2.4 גודל 9.55 מ״ב עדכון אחרון לפני 21 ימים (23 דצמ׳ 2025) קטגוריות קשורות פיתוח הרשת פרטיות ואבטחה רישיון GNU General Public License v3.0 only מדיניות פרטיות קריאת מדיניות הפרטיות עבור תוספת זו היסטוריית הגרסאות הצגת כל הגרסאות תגיות anti malware anti tracker container privacy security הוספה לאוסף בחירת אוסף… יצירת אוסף חדש דיווח על תוספת זו תמיכה במפתח זה מפתח ההרחבה הזו מבקש ממך לסייע בהמשך הפיתוח על ידי מתן תרומה צנועה. לתרום כעת מעבר לדף הבית של Mozilla תוספות על אודות בלוג התוספות של Firefox Extension Workshop מרכז המפתחים מדיניות למפתחים בלוג קהילה פורום דיווח על תקלה מדריך סקירה דפדפנים Desktop Mobile Enterprise מוצרים Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) פרטיות עוגיות מידע משפטי למעט היכן ש צוין אחרת, התוכן באתר זה מוגש בכפוף ל גרסה 3.0 של הרשיון Creative Commons Attribution Share-Alike או כל גרסה עדכנית יותר. שינוי שפה Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T08:48:04 |
https://ruul.io/blog/rooted-with-ruul-meet-ender | Rooted with Ruul: meet solo tech talent, Ender - Ruul Product Payment Requests Get paid anywhere. Sell Services Make your services buyable Sell Products Create once sell forever Subscriptions Get paid on repeat Ruul Space Your personel storefront. One link for everything you offer. Learn more Pricing Resources Partner Programs Referral Program Get 1% for life. Seriously. Affiliate Program Bring users, get paid Partners Let’s grow together. More Blog About us Support Brand Kit For Customers Log in Sign up For Businesses Login Sign up No items found. Rooted with Ruul: meet solo tech talent, Ender Get insights from Ender, a freelance consultant, and engineer. Read our interview and get great tips for fresh freelancers starting out. Esen Bulut 5 min read RUUL FOR INDEPENDENCE You chose independence.We make sure you keep it. Sell your time, your talent, whatever you create or build always on your terms. Get started See Example This is also a heading This is a heading Key Points Read our conversation with Ender, a freelance engineer and consultant from the Ruul community. Learn more about the freelancing lifestyle and get excellent tips, which will help fresh freelancers on what to do or what to avoid during the journey. Please introduce yourself and tell us a little bit about your work. I have been working as a network engineer, technology instructor, and entrepreneur for 12 years. I have been working freelance for over two years. I provide consultancy to companies of different sizes, from startups to banks. How and why did you first start freelancing? Did a memorable incident steer your decision, and would you like to tell Ruulers about it? After my thirties, I started to think about running my own business, but you need soft skills such as customer relations, sales, marketing besides technical capabilities. I always had a chance to work full time. But to learn how business work entirely as a pure technical guy, I had to try it.Ruul helps me run my own business without dealing with procedures. How is your daily routine? Can you share it with us in a few bullet points? I can not follow my daily routine because I have to support my customers on 7/24. If you are working full-time in a company, that means you have a boss. But if you are working as a freelance, that means each customer is your boss. It is hard to handle.Especially if you provide your service abroad with timezone difference, your daily life may be affected. Being and living in the current time is essential. We can say my daily routine is differing from time to time. Where is your best working corner at home? The sofa, the bed, or an isolated room? Can you illustrate the scene with a photo? Of course, I have a desk, and I spend most of the time on it, but this is physically and mentally unhealthy. Cats make it fun. I can work anywhere if I have my laptop with me. You have to be location independent. Any songs/albums/artists/genres you prefer listening to as you work? How about as you chill? Does your playlist differ according to what you are doing? I am a metalhead for a long time, but listening to heavy music does only work for routine jobs. I usually listen to instrumental music genres such as jazz and post-rock, which do not distract your attention with lyrics. In three words, how do you reckon a professional freelancer should be? Interdisciplinary, Self-disciplined, self-motivated. Are you a phone or e-mail person when it comes to communicating with clients? I am an email person, but my clients prefer phones. Would you still prefer video calls or instead meet people in person for work purposes if the pandemic was out of the picture? Most of the time, I prefer video calls. I may like meeting people in person or visiting customer onsite if we have a good working plan for that meeting. Are there any tools you find indispensable as you work on a freelance basis? Could you name some? You should organize your notes and track each customer’s process in any software that works for you. Do you have any suggestions for fresh freelancers? Can you shortly elaborate on what freelancers should do or avoid doing in their journey? Freelancing does not mean working less. It needs more mental readiness instead of physical preparation. I spend one-week getting job tasks done and the rest of the month for sales and collecting payments for each month. You will be like a company with only one employee. You will be a Ceo who washes dishes. Prepare for that. ABOUT THE AUTHOR Esen Bulut Esen Bulut is the co-founder of Ruul. After graduating Boston College with finance and economics degrees, she began her career as a Finance Executive. Prior to Ruul, she held managerial positions in finance and marketing. Esen's entrepreneurship success earned her recognition in Fortune's 40 under 40 list in 2022. More UK Digital Nomad Visa for Freelancers Create a seamless experience with the UK Digital Nomad Visa for freelancers, exploring available visa options, benefits, and financial management. Read more How to set up the perfect workspace for freelancing Learn how to create the ultimate freelancer's remote workspace. Follow our step-by-step guide to build a comfortable and efficient home office. Read more Becoming a Freelance Digital Marketer from Scratch: A Beginner’s Guide Have you ever dreamed of becoming a freelance digital marketer? This article will offer you insight into starting the journey from scratch. Read more MORE THAN 120,000 Independents Over 120,000 independents trust Ruul to sell their services, digital products, and securely manage their payments. FROM 190 Countries Truly global coverage: trusted across 190 countries with seamless payouts available in 140 currencies. PROCESSED $200m+ of Transactions Over $200M successfully processed, backed by an 8-year legacy of secure, reliable transactions trusted by independents worldwide. FREQUENTLY ASKED QUESTIONS Everything you need to know. Get clear, straightforward answers to the most common questions about using Ruul. hey@ruul.io What is Ruul? Ruul is a merchant-of-record platform helping freelancers and creators globally sell services, digital products, subscriptions, and easily get paid. Who is Ruul for? Ruul is designed for freelancers, creators, and independent professionals who want a simple way to sell online and get paid globally. How does Ruul work? Open an account, complete a quick verification (KYC), and link your payout account. Then, start selling through your store or send payment requests to customers instantly. How does pricing work? Signing up is free. There are no subscription or hidden fees. Ruul charges a small commission only when you sell or get paid through the platform. What is a Merchant of Record? A merchant of record is the legal seller responsible for processing payments, handling taxes, and managing compliance for each transaction. What can I sell on Ruul? You can sell services, digital products, license keys, online courses, subscriptions, and digital memberships. How do I get paid on Ruul? Add your preferred bank account, digital wallet, or receive payouts in stablecoins as crypto. Funds arrive within 24 hours after a payout is triggered. OPEN AN ACCOUNT START MAKING MONEY TODAY ruul.space/ Thank you! Your submission has been received! Oops! Something went wrong while submitting the form. Trustpilot Product Payment Requests Sell Services Sell Products Subscriptions Ruul Space Pricing For Businesses Resources Blog About Contact Support Referral Program Affiliate Program Partner Program Tools Invoice Generator NDA Generator Service Agreement Generator Freelancer Hourly Rate Calculator All Rights Reserved © 2025 Terms Of Use Privacy Policy | 2026-01-13T08:48:04 |
https://commonsclause.com/ | Commons Clause License The Commons Clause . “Commons Clause” License Condition v1.0 The Software is provided to you by the Licensor under the License, as defined below, subject to the following condition. Without limiting other conditions in the License, the grant of rights under the License will not include, and the License does not grant to you, the right to Sell the Software. For purposes of the foregoing, “Sell” means practicing any or all of the rights granted to you under the License to provide to third parties, for a fee or other consideration (including without limitation fees for hosting or consulting/ support services related to the Software), a product or service whose value derives, entirely or substantially, from the functionality of the Software. Any license notice or attribution required by the License must also include this Commons Clause License Condition notice. Software: [name software] License: [i.e. Apache 2.0] Licensor: [ABC company] FAQ What is Commons Clause? The Commons Clause is a license condition drafted by Heather Meeker that applies a narrow, minimal-form commercial restriction on top of an existing open source license to transition the project to a source-availability licensing scheme. The combined text replaces the existing license, allowing all permissions of the original license to remain except the ability to "Sell" the software as defined in the text. This Clause is not intended to replace licenses of existing open source projects in general, but to be used by specific projects to satisfy urgent business or legal requirements without resorting to fully "closing source". Is this “Open Source”? No. “Open source”, has a specific definition that was written years ago and is stewarded by the Open Source Initiative, which approves Open Source licenses. Applying the Commons Clause to an open source project will mean the source code is available, and meets many of the elements of the Open Source Definition, such as free access to source code, freedom to modify, and freedom to re-distribute, but not all of them. So to avoid confusion, it is best not to call Commons Clause software “open source.” If I change from an open source license to Commons Clause, how does this affect my project? When the Commons Clause is applied to an existing open source project, it only affects code moving forward -- meaning no existing users are immediately affected. Licenses applied to previous versions are not revoked, so the Clause will only apply to future releases. If you choose to adopt the Commons Clause, you should understand the implications any license change will have on your community and weigh that against the threat of allowing others to trade on your work developing your open source project. The Commons Clause was intended, in practice, to have virtually no effect other than force a negotiation with those who take predatory commercial advantage of open source development. In practice, those are some of the biggest technology businesses in the world, some of whom use open source software but don’t give back to the community. Freedom for others to commercialize your software comes with starting an open source project, and while that freedom is important to uphold, growth and commercial pressures will inevitably force some projects to close. The Commons Clause provides an alternative. The Commons Clause was not designed to restrict code sharing or development, but preserves the rights of developers to benefit from commercial use of their work. However, those that adopt the Clause should understand the broader implications of making a license change and commitments to source availability. May I create, distribute, offer as SaaS, and/or “sell” my products using Commons Clause licensed components? Yes! Commons Clause only forbids you from “selling” the Commons Clause software itself. You may develop on top of Commons Clause licensed software (adding applications, tools, utilities or plug-ins) and you may embed and redistribute Commons Clause software in a larger product, and you may distribute and even “sell” (which includes offering as a commercial SaaS service) your product. You may even provide consulting services ( see clarifying discussion here ). You just can’t sell a product that consists in substance of the Commons Clause software and does not add value. This is not a new concept. It’s similar to “value-add” requirements in many licenses. For example let’s say you use a library containing numerical algorithms from Rogue Wave Software . Can you create an application with the library and sell the application? Yes. Can you offer that application as SaaS and charge for it? Yes. Can you change the name of the library and change some function names and sell the library or offer it as SaaS? No. Let’s apply the example to Commons Clause licensed software. Commons Clause-licensed Redis Graph is a graph database module for BSD-licensed Redis. Can you create applications with Redis Graph and distribute and/or sell them? Yes. Can you redistribute Redis Graph along with your application? Yes. Can you offer that application as SaaS and charge for it? Yes. Can you take Redis Graph itself, call it ElastiGraph and offer it as SaaS and charge for it. No. Isn’t this the same as a proprietary license? Commons Clause is a source-available license that is less liberal than permissive open source licenses (such as Apache, BSD, MIT). It allows you more commercial freedom in some ways than copyleft or reciprocal open source licenses (such as GPL and AGPL), and it is much more liberal than proprietary source-unavailable licenses, such as for the numerical algorithms library mentioned in the previous answer. The Commons Clause source-available license provides many of the benefits of open source software to anyone not intending to “sell” the Commons Clause licensed software itself. Anyone not intending to “sell” the Commons Clause licensed software itself may view the source code, make modifications, submit pull requests to get their modifications into the software, freely use, embed and redistribute the software, make and distribute and sell derivative works. To anyone wishing to sell the Commons Clause licensed software itself, an action that the license prohibits, it appears proprietary, in the sense that it would be necessary to negotiate a license to do that with the owner of the Commons Clause software. Why not just use AGPL? AGPL simply doesn't work to solve this problem. It is not a widely adopted license, and its “network” clause is not clearly written, so companies are not willing to stake their entire development resources on using AGPL to prevent free riding. AGPL doesn't go far enough to preserve the rights of developers. If cloud-based software is licensed under AGPL, often, much of the value for improvements to the cloud-based software arguably falls outside of the “Program” thereby nullifying many of the benefits of mandating enforcing source code offers. Hosting, management, and other elements are often just as important as the core code. In addition, the ambiguity of what is covered by AGPL’s network clause (“interacting ..remotely through a computer network”) means that many potential users are more confused and cautious about using AGPL code than a source-available license. Like the group behind Commons Clause, the drafters of AGPL were concerned about the “cloud loophole” in licenses like GPL. Unfortunately, AGPL’s network clause was a compromise; one camp in the GPL3 drafting process wanted to introduce a network clause into GPL3, and many more than wanted to preserve the “distribution trigger”. So the network clause was never popular, and even after 10 years, AGPL has not been broadly accepted, particularly in business. Most companies still won’t use AGPL code at all. So it is not a useful open source solution for emerging companies. The open source community says this is a bad idea. I love open source software. Should I refuse to use Commons Clause software? Some people believe that all software must be open source, and they will never condone anything else. But in reality, there are lots of models for licensing software. Commons Clause is just one alternative. But the important thing is that the developers who have chosen Commons Clause have been faced with the choice of doing something new or allowing their businesses to fail. And the other possibility -- the completely proprietary, closed source model of companies like Oracle and Adobe -- is always a possibility. So if anyone tries to convince you that Commons Clause is wrong because it doesn't meet all the requirements of the Open Source Definition, you should ask them if proprietary is better -- or no software at all. You probably use plenty of software that is “freeware” -- under free of charge proprietary licenses (JRE, Acrobat). If you refuse to use Commons Clause software, you should refuse to use those, too. Those licenses give you less rights. Why did you use open source licenses as the basis for Commons Clause? We didn’t have to, we could have just written a new, proprietary license. But people understand the popular open source licenses, and we wanted to be clear that we were allowing everything those licenses allow, except for one kind of use. For maintainers, this portability was a specific design constraint to support the legacy schemes they were transitioning from. Why not just use Creative Commons non-commercial (sharealike)? CC-NC is a similar idea, but CC licenses are not software licenses. Also, there is a lot of confusion about what is a “commercial” use, and we only wanted to restrict one narrow kind of commercial use. CC-NC is actually much more restrictive than Commons Clause. Commons Clause prohibits me from selling “substantially” the Commons Clause licensed software. What does “substantially” mean? “Substiantially” is not a new concept. Qualifications like "substantially" are common in legal documents to indicate that minor differences are not important. In this sense, "substantially" means “for the most part,” or “essentially” (as the word is defined in the Oxford English Dictionary.) The Commons Clause restricts the sale of a product “whose value derives, entirely or substantially, from the functionality of the Software." Selling a product which adds only an insubstantial value to the software -- such as changing the product name, changing some API or function names, or just making the Commons Clause licensed product available via SaaS -- would be restricted. What will this do to Open Source? Open source is here to stay. But open source works better for some kinds of software than others. The Open Source Definition and the development model it represents is an immensely important set of ideals that have carried many projects to success. But most of those projects were basic infrastructure projects, as opposed to advanced applications. And very few pure open source businesses have flourished. Open Source projects are not free of cost, they often support billions of dollars of revenue and can require tens of millions of dollars in financing to stay afloat. That can work -- with a lot of effort -- for software that everyone uses, like operating systems. Also, lots of companies are successful using open source -- when they are selling something else, like hardware or services or dual-license upsell modules. But many software companies can’t keep the doors open with an open source licensing model. The Commons Clause was drafted by a group of developers behind many of the world’s most popular open source projects who feel a lot of pain and pressure from a rapidly-developing business ecosystem and the realities of the cost of developing projects. It wasn’t created to end open source, but start a conversation on what we can do to meet the financial needs of commercial software projects and the communities behind them. Commons Clause · Contributed by FOSSA ( @getfossa ) · View Source on GitHub · Website Design by Roka | 2026-01-13T08:48:04 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fdevteam%2Fwhat-was-your-win-this-week-8d7&title=What%20was%20your%20win%20this%20week%3F%3F%3F&summary=%F0%9F%91%8B%F0%9F%91%8B%F0%9F%91%8B%F0%9F%91%8B%20%20Looking%20back%20on%20your%20week%20--%20what%20was%20something%20you%27re%20proud%20of%3F%20%20All%20wins%20count%20--%20big%20or...&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:48:04 |
https://github.com/skills/release-based-workflow | GitHub - skills/release-based-workflow: Create a release based workflow that is built on the foundations of the GitHub flow Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} skills / release-based-workflow Public template Notifications You must be signed in to change notification settings Fork 90 Star 160 Create a release based workflow that is built on the foundations of the GitHub flow License MIT license 160 stars 90 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 6 Pull requests 2 Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Security Insights skills/release-based-workflow main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 52 Commits .github .github images images .gitignore .gitignore LICENSE LICENSE README.md README.md base.css base.css engine.js engine.js game.js game.js game.manifest game.manifest index.html index.html View all files Repository files navigation README Code of conduct Contributing MIT license Security Create a release based workflow Create a release based workflow that is built on the foundations of the GitHub flow. Welcome Create a release based workflow that is built on the foundations of the GitHub flow . When your team uses a release-based workflow, GitHub makes it easy to collaborate with deployable iterations of your project that you can package and make available for a wider audience to download and use. GitHub releases allow your team to package and provide software to your users based on a specific point in the history of your project. Who is this for : Developers, DevOps Engineers, IT Operations, managers, and teams. What you'll learn : How to follow a release-based workflow. What you'll build : You will create tags, releases, and release notes. Prerequisites : If you need to learn about branches, commits, and pull requests, take Introduction to GitHub first. How long : This course takes less than 1 hour to complete. In this course, you will: Create a beta release Add a feature to a release Open a release pull request Add release notes and merge Finalize a release Commit a hotfix Create a hotfix release How to start this course Right-click Start course and open the link in a new tab. In the new tab, most of the prompts will automatically fill in for you. For owner, choose your personal account or an organization to host the repository. We recommend creating a public repository, as private repositories will use Actions minutes . Scroll down and click the Create repository button at the bottom of the form. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README. Get help: Post in our discussion board • Review the GitHub status page © 2023 GitHub • Code of Conduct • MIT License About Create a release based workflow that is built on the foundations of the GitHub flow Topics skills-course Resources Readme License MIT license Code of conduct Code of conduct Contributing Contributing Security policy Security policy Uh oh! There was an error while loading. Please reload this page . Activity Custom properties Stars 160 stars Watchers 7 watching Forks 90 forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 10 Languages JavaScript 90.8% CSS 5.7% HTML 3.5% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb6-3 | YAML? That’s Norway problem < Back to LAB174.com YAML? That’s Norway problem 2026-01-12 Abstract A deep dive into YAML’s Norway problem: why the country code NO gets parsed as false, its history from YAML v1.0 to v1.2, and why popular libraries still exhibit this behavior in 2026. What is yaml Yaml is a well-known data serialization language designed for human readability. It’s a popular choice for configuration files and metadata. Here’s a simple example: # project.yaml title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse countries : - DE - FR - PL - RO Let’s verify that the above example parses correctly. We’ll use Python 1 with Py Yaml 2 version 6.0.3 (the latest version as of this writing). First, let’s install it: python3 -m pip install pyyaml==6.0.3 Now let’s write a simple script to parse the yaml file: # python-pyyaml.py import json import yaml with open ( "project.yaml" , "r" , encoding = "utf-8" ) as f: data = yaml.safe_load(f) print (json.dumps(data, indent = 2 )) Running python3 python-pyyaml.py produces this output: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , "PL" , "RO" ] } So far everything behaves as expected. As of January 2026 Python is the world’s 4th most popular programming language according to a 2025 Stack Overflow Survey ( archive ) ↩︎ Py Yaml is Python’s most popular yaml library and a top 20 Python library overall in the last month according to PyPI Stats ( archive ). It is also an “official” yaml library in the sense that its source code is hosted in a Github repository owned by the yaml Github account; see: Canonical source repository for Py Yaml . ↩︎ The Norway problem in yaml When we change the original yaml file and add Norway’s two letter iso country code to the existing list: countries : - DE - FR - NO - PL - RO Using the same parsing method, the file now yields this result: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , false , "PL" , "RO" ] } Note that NO has been replaced with false . This is unexpected. Nothing about the context suggests a boolean should appear here. The NO literal sits in a list of country codes like FR or PL and appears similar in form. The problem, of course, is that “no” is also an English word with a negative meaning. This feature was originally added to allow writing booleans in a more human readable way, e.g.: platforms : iPhone : yes iPad : yes AppleWatch : no This gets parsed as: { "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false } } The idea was that configuration files should read like natural language. In practice this behavior proved problematic, becoming the notorious Norway problem in yaml . One workaround is to escape the string, like this: countries : - DE - FR - "NO" - PL - RO With quotes, the file parses as expected: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } Many articles about yaml ’s Norway problem stop here, presenting quoting as the canonical fix. There is more. Yaml ’s history To understand today’s state of the Norway problem we’ll first look at how yaml evolved. May 2001 – Yaml first pass specification At this time, yaml was more of a concept than a finished language. It looked a bit different, though somewhat recognizable. Below is a partial example from the original specification; there are more in the full document, sadly none with boolean values. buyer : % address : % city : Royal Oak line one : 458 Wittigen's Way line two : Suite 292 postal : 48046 state : MI family name : Dumars given name : Chris The document makes no mention of parsing no to false . The “Serilization Format / bnf ” section even contains a typo and a “to do” note 3 : This section contains the bnf 4 productions for the yaml syntax. Much to do… Full first pass specification – archived link ↩︎ Bnf stands for “Backus–Naur form”, a notation system for syntax definition ( Wikipedia ). ↩︎ January 2004 – Yaml v1.0 final draft This version describes various ways of presenting scalars 5 , including both quoted scalars and plain scalars with implicit typing. This is what we’re after. Version 1.0 defined only sequence , map , and string as mandatory types 6 . The rest were optional, but a reference specification existed. That reference specification for the optional boolean type included English word format. Supported words were: true/false , on/off , and also yes/no 7 . This allows the Norway problem to appear – even if following that part of reference is described as optional. – Bonus: implicit typing can be overridden with explicit tags – we’ll talk about this later. – Bonus: single sign characters, i.e. + and - should also be treated as true and false ; even more so, as they are described as the canonical form 8 ! A scalar data type, or just scalar, is any non-composite value. Generally, all basic primitive data types are considered scalar source: Wikipedia ↩︎ Following is a description of the three mandatory core tags. Yaml requires support for the seq, map and str tags. source: Yaml v1.0 specification, tag repository ↩︎ English word format: implicit english ~= true|True|TRUE |false|False|FALSE |yes|Yes|YES |no|No|NO |on|On|ON |off|Off|OFF source: Yaml v1.0 boolean type specification – archived link ↩︎ Single sign character format: implicit canonical ~= +|- source: Yaml v1.0 boolean type specification – archived link ↩︎ January 2005 – Yaml v1.1 final draft Version 1.1 maintained the same implicit typing behavior as v1.0. However, the types listed in the spec – including boolean – while still not mandatory, were now strongly recommended 9 . – Bonus: single sign characters are no longer included and the canonical form is now y/n 10 . these tags represent types that are useful across a wide range of applications and it is strongly recommended they be used whenever appropriate to promote interoperability. source: Yaml v1.1 specification, tag repository ( archive ) ↩︎ Yaml v1.1 boolean type specification , ( archive ) ↩︎ July 2009 – Yaml Revision 1.2.0 Its goal was to make yaml compliant with json , going as far as allowing json to be a subset of yaml 11 . Implicit typing rules have been removed, including the boolean English word format. – Bonus: explicit typing rules are still present. On paper, the Norway problem shouldn’t exist anymore, at least not since this yaml revision. So why are we still seeing it in 2026? The primary objective of this revision is to bring Yaml into compliance with json as an official subset. source: Yaml revision v1.2.0 ↩︎ Yaml spec version history until v1.2.0 Yaml spec version Date Type of no : Value of no first pass specification May 2001 unspecified unspecified v1.0 January 2004 boolean false v1.1 January 2005 boolean false v1.2.0 July 2009 string "no" Table 1: Summary of yaml spec changes. Note that “Type of no ” and “Value of no ” labels refer to the literal without quotes. Yaml in practice To understand why the Norway problem persists, we need to examine the scope of work involved in implementing yaml spec changes. Some clues are present in earlier text already, we see that yaml supports implicit typing, explicit typing, and various presenting formats. Also, the time between different yaml spec version releases is measured in years. What hides between the lines is that yaml and its specification are very, hugely, extremely complex. Seriously, it’s hard to overstate this. Since v1.0 yaml ’s goal was to build upon xml 12 and a number of other technologies, as listed in the final draft 13 : Yaml integrates and builds upon concepts described by C, Java, Perl, Python, Ruby, rfc0822 ( mail ), rfc1866 ( html ), rfc2045 ( mime ), rfc2396 ( uri ), xml , sax and soap Yaml supports attachments, custom tags, references – the list goes on. There was even yaxml , an xml binding for yaml 14 . There are 9 ways of writing multiline strings – and some claim the number is actually 63 15 . Characters like ? , ! , !! in some cases have special meanings, with the latter allowing arbitrary code execution. Given this complexity, the Norway problem wasn’t the only language quirk in yaml v1.1. Revision v1.2 simplified boolean behavior and more (e.g. handling of null and numerical values), while other language features remained unchanged. How did libraries react to changes in such a complex specification? In fact yaml was originally intended to be a markup language and its name stood for “Yet Another Markup Language”. Six months after the first pass specification, in January 2002, it was renamed to “ Yaml Ain’t Markup Language”. ↩︎ Yaml v1.0 specification, prior art ↩︎ a subset of xml which has yaml ’s information model, but xml ’s syntax (…) a xslt Stylesheet is provided, along with the canonical invoice example in xml using this schema source: Yaxml , the (draft) xml Binding for yaml – archived link ↩︎ There are 5 6 NINE (or 63, depending how you count) different ways to write multi-line strings in yaml . (…) 2 block styles, each with 2 possible block chomping indicators (or none), and with 9 possible indentation indicators (or none), 1 plain style and 2 quoted styles: 2 x (2 + 1) x (9 + 1) + 1 + 2 = 63 source: Stack Overflow answer ( archived ) ↩︎ Yaml libraries As of January 2026 popular yaml libraries still haven’t moved from v1.1 to v1.2, and they still exhibit the Norway problem. Smaller alternative projects have appeared, but their usage hasn’t surpassed the existing v1.1 libraries. Some users have built their own alternative parsers, mixing v1.1 and v1.2 features, or focusing on a subset of yaml suited to their needs. Below are some examples. Py Yaml As mentioned before, Py Yaml is Python’s most popular yaml library and one of the most popular Python libraries overall. Py Yaml never added v1.2 support. There is an open issue from 2017 in Py Yaml ’s Github project about introducing support for v1.2 16 . There are at least two more related open issues, plus several closed ones. An unofficial library 17 exists that can be used on top of Py Yaml to provide partial v1.2 support (its documentation notes that not all v1.2 features are implemented). Another Python library, ruamel.yaml 18 , supports v1.2 by default. Py Yaml Github Issue #116 ↩︎ yamlcore PyPI project page ↩︎ ruamel.yaml PyPI project page ↩︎ Lib Yaml Lib Yaml is the long-standing C library for yaml , it is used widely as a dependency by other tools and bindings. Like Py Yaml , it’s an “official” implementation – in the sense that its canonical repository is hosted on Github and owned by the official ‘yaml’ Github account. Lib Yaml also never added v1.2 support. An open issue from 2016 in Lib Yaml ’s github project requests adding v1.2 support 19 . As mentioned earlier, Lib Yaml sits deep in dependency trees; changing its behavior is especially risky and slow. A less popular library, libfyaml 20 , supports v1.2 by default. Lib Yaml Github Issue #20 ↩︎ libfyaml Github project page ↩︎ Golang’s gopkg.in/yaml.v3 Currently unmaintained 21 , historically the most popular and still holds more Github stars then other Golang yaml libraries. It’s especially interesting because it declares support for a mix of v1.1 and 1.2 22 . The Golang’s most popular actively maintained library 23 defaults to v1.2 behavior. “This project is unmaintained” , source: gopkg.in/yaml.v3 Github project page ↩︎ “The yaml package supports most of yaml 1.2, but preserves some behavior from 1.1 for backwards compatibility.” , source: gopkg.in/yaml.v3 Github project page ↩︎ goccy/go-yaml Github project page ↩︎ Kyaml Kyaml is a yaml dialect built for the Kubernetes project, launched in June 2025. Its goal is to provide a safer and less ambiguous tool; it is also designed specifically for Kubernetes, trading generality for predictability. The announcement blog post references the Norway problem directly 24 . Yaml ’s significant whitespace requires careful attention to indentation and nesting, while its optional string-quoting can lead to unexpected type coercion (for example: “The Norway Bug”). source: Kubernetes v1.34 Sneak Peek ↩︎ Is the Norway problem solved? Yaml ’s ecosystem is not just libraries, it’s also the community of users. Including: strong and conflicting opinions about yaml in general and the Norway problem in particular. In some part this outcome could be expected; after all yaml is very popular, deceptively complex, and is used in different kinds of scenarios, from small personal config files to critical infrastructure setups. Many texts don’t distinguish between yaml spec versions at all 25 . Even when spec version numbers are used, they’re frequently mistyped. It’s not difficult to find documentation claiming that implicit boolean typing is a trait of yaml specification version 1.2 26 (the correct version is v1.1); mistakes get spotted 27 and eventually updated, but that takes more time and effort than making the original typo. On the other hand we see users who declare the Norway problem as solved because it doesn’t exist in the latest spec version, or because they haven’t experienced it themselves, or for other reasons 28 . To be fair, that language feature was removed over a decade ago, and it’s unexpected that popular libraries still support the older spec version. Technically, the issue is solved in the spec – but in practice, most widely adopted implementations still support implicit boolean typing, as we’ve seen. Finally, there are end users who are so unhappy with yaml that they prefer almost anything else 29 . We end up with countless use cases (hobby, pro, critical infrastructure, …), roles (spec author, library maintainer, end user debugging a failed deployment at 11pm, …), and just as many points of views. The yaml specification defines many strings that are automatically interpreted as boolean values, which often conflicts with developer expectations. When you write country: NO , the yaml parser interprets NO as the boolean false , not the string "NO" source: What is the Norway Bug? ↩︎ The most tragic aspect of this bug , however, is that it is intended behavior according to the yaml 1.2 specification. source: The Norway Problem – why Strict Yaml refuses to do implicit typing and so should you ↩︎ In this case a Github issue has been created: It was intended according to the yaml 1.1 specification, but in yaml 1.2, the only recognized booleans are true , True , TRUE , false , False , FALSE . source: strictyaml Github issue #186 ↩︎ I don’t want to link to individual messages on social platforms to err on the side of users’ privacy; I’ll paraphrase some of them below, for illustration purposes. Norway problem has been solved for 16 years. Using 1.1 at this point is just forehead palming foolishness. The Norway issue is a bit blown out of proportion. I have been using YAML for 5+ years and have never had it. We stopped having this problem over ten years ago. Just quote your strings. Another solution is to change the country name. ↩︎ Same as earlier, I’ll paraphrase a few messages below, meant for illustration. Stop using YAML YAML - just say Norway. You should stop even tolerating YAML, refuse on sight. YAML made sense before JSON became a thing. YAML made me look at XML wistfully. Why people persist with YAML in new projects is baffling to me. People from Norway couldn't sign up. Took us a while to figure out. ↩︎ What next? In yaml final draft v1.0, the document specified that, along with yes and no , + and - should also be parsed as booleans. This was removed v1.1. There was an idea to keep that functionality when plus or minus signs were preceded with a dot ( .+ and .- ), but it didn’t catch on. Despite its well known and lesser known quirks, yaml remains popular and widely used. At this scale small quirks cascade into unexpected issues. And changes – or fixes – are introduced at a glacial pace. Then again, yaml ’s charm has its place, as evidenced by its popularity. While spec change adoption is very slow, it is still ongoing. New projects will likely adopt newer libraries, where the Norway problem no longer exists. If there is a single takeaway from this article, it’s this: yaml ecosystem is fragmented; on the whole it is moving towards a slightly stricter version. Implicit boolean typing is getting removed, it’s no longer in the official specification and most new libraries adhere to that. As of January 2026 however, the older libraries are stuck on the older version of the spec, they are still more popular and updating or phasing them out may take a while. Frequently Asked Questions Why not just use json in place of yaml ? A common reply is “no comments” – because json doesn’t support comments 30 ; many other yaml features aren’t supported either. This makes json a simpler and stricter alternative. Wheter that’s a better fit for your project, that depends on the project. As always, personal preference plays a role too. Note: json has its own flavors, like jsonc 31 . It was a conscious decision; there is an explanation from Douglas Crockford, as well as a suggestion about using json for configuration files: I removed comments from json because I saw people were using them to hold parsing directives, a practice which would have destroyed interoperability. I know that the lack of comments makes some people sad, but it shouldn’t. Suppose you are using json to keep configuration files, which you would like to annotate. Go ahead and insert all the comments you like. Then pipe it through JSMin before handing it to your json parser. source: Google Plus post by Douglas Crockford – archived link ↩︎ Json with Comments – project’s homepage ↩︎ Is yaml a superset of json ? After writing this article, I’m still not entirely sure. Even though the goal of yaml revision v1.2.0 was to make that happen and revisions 1.2.0 and 1.2.1 claimed it explicitly 32 : Yaml can therefore be viewed as a natural superset of json , offering improved human readability and a more complete information model. That text has been removed from the latest yaml revision 1.2.2. A popular article 33 claims to prove that yaml is not a superset of json , but that article uses a v1.1 parser – and as we know v1.1 never claimed json compatibility. So that won’t help us. The actual reason might be that yaml requires maps to have unique keys 34 , while json only recommends it 35 . So perhaps most json (i.e. json where objects have unique keys) is a subset of yaml . Some ambiguity remains. See e.g.: Yaml Version 1.2 Revision 1.2.1 ↩︎ Json treats the value 1e2 a number, of course, because it’s not in quote marks. Yaml fails to parse it as a number so silently falls back to treating it as a string. source: YAML IS NOT A SUPERSET OF JSON ↩︎ The content of a mapping node is an unordered set of key/value node pairs, with the restriction that each of the keys is unique source: Yaml Version 1.2 Revision 1.2.2 ↩︎ The names within an object SHOULD be unique. source: The application/json Media Type for JavaScript Object Notation ( json ) ↩︎ What went wrong? This question is out of scope for this article – here the goal is to prioritize facts over “what if?”. If i had to answer, I’d say that nothing went wrong. When a complex technology with a stable ecosystem introduces a breaking change, sometimes the process can take ages. The main surprise here is how complicated yaml really is. Also, as we’ve seen, with yaml and related tools being free software, anyone could contribute to improving the v1.2 adoption rate – or move to a tool that suits them better, or even create one. What about toml , sexagesimal numbers, schemas, human genes, Ruby, or Perl? These topics are only loosely related to the Norway problem, and this text is already quite long. If you enjoyed reading it, leave positive feedback somewhere and a Part 2 might happen. In the meantime, visit my homepage 36 and check out my other projects – maybe you’ll find something else you’ll enjoy. LAB174 homepage ↩︎ Epilogue Implicit boolean typing has been removed, but explicit boolean typing still remains. If a uniform yaml 1.2 future actually arrives, you can still bring a little bit of nostalgia to your code by writing: title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse platforms : iPhone : !!bool yes iPad : !!bool yes # Note the explicit typing here and above. AppleWatch : !!bool no countries : - DE - FR - NO - PL - RO When parsed with yq , a tool that supports yaml revision 1.2 by default: yq eval -o=json project.yaml It returns: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } < Back to LAB174.com | 2026-01-13T08:48:04 |
https://opensource.org/licenses/BSD-2-Clause | The 2-Clause BSD License – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Popular / Strong Community The 2-Clause BSD License SPDX short identifier: BSD-2-Clause Note: This license has also been called the “Simplified BSD License” and the “FreeBSD License”. See also the 3-clause BSD License . Copyright <YEAR> <COPYRIGHT HOLDER> 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 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 HOLDER 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. Donate to the OSI The OSI is the authority that defines Open Source, recognized globally by individuals, companies, and public institutions. The Open Source Initiative (OSI) is a 501(c)3 public benefit corporation, founded in 1998. --> Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:48:04 |
https://github.com/skills/connect-the-dots | GitHub - skills/connect-the-dots: Useful tips when navigating through your repository Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} skills / connect-the-dots Public template Notifications You must be signed in to change notification settings Fork 121 Star 169 Useful tips when navigating through your repository License MIT license 169 stars 121 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 2 Pull requests 1 Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Security Insights skills/connect-the-dots main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 91 Commits .github .github docs docs .gitignore .gitignore LICENSE LICENSE README.md README.md View all files Repository files navigation README Code of conduct Contributing MIT license Security Connect the dots in a GitHub repository Useful tips when navigating through your repository. Welcome Have you ever worked in a repository with a lot of history? Perhaps you've had to track down related issues and pull requests in the past, or you've had to find who committed a particular change. If you've ever found yourself in any of these situations, you'll know how important it is to navigate your workspace. Who is this for : Developers, GitHub users, users new to Git, students, managers, and teams. What you'll learn : Find relevant issues and pull requests. Search history to find context. Make connections within GitHub to help others find things. What you'll build : Repository with existing commits, duplicated issues, and a content defect to be fixed. Prerequisites : Before you take this course, you may want to go through the GitHub Quickstart introduction on GitHub Docs and Introduction to GitHub course on GitHub Skills. How long : This course takes less than 15 min to complete. In this course, you will: Resolve a duplicate issue. Find a commit in history. Fix a broken sidebar. How to start this course Right-click Start course and open the link in a new tab. In the new tab, most of the prompts will automatically fill in for you. For owner, choose your personal account or an organization to host the repository. We recommend creating a public repository, as private repositories will use Actions minutes . Scroll down and click the Create repository button at the bottom of the form. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README. Get help: Post in our discussion board • Review the GitHub status page © 2023 GitHub • Code of Conduct • MIT License About Useful tips when navigating through your repository Topics skills-course Resources Readme License MIT license Code of conduct Code of conduct Contributing Contributing Security policy Security policy Uh oh! There was an error while loading. Please reload this page . Activity Custom properties Stars 169 stars Watchers 9 watching Forks 121 forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 11 Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:48:04 |
https://opensource.org/licenses/BSD-3-Clause | The 3-Clause BSD License – Open Source Initiative Skip to content Get involved About Licenses Open Source Definition Open Source AI Programs Blog Get involved About Licenses Open Source Definition Open Source AI Programs Blog Open Main Menu Popular / Strong Community The 3-Clause BSD License SPDX short identifier: BSD-3-Clause Note: This license has also been called the “New BSD License” or “Modified BSD License”. See also the 2-clause BSD License . Copyright <YEAR> <COPYRIGHT HOLDER> 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 copyright holder 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 HOLDER 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. Donate to the OSI The OSI is the authority that defines Open Source, recognized globally by individuals, companies, and public institutions. The Open Source Initiative (OSI) is a 501(c)3 public benefit corporation, founded in 1998. --> Get involved Mastodon Twitter LinkedIn Reddit About About Our team Board of directors Sponsors Programs Blog Press mentions Trademark Bylaws Licenses Open Source Definition Licenses License Review Process Open Standards Requirement for Software Open Source AI Open Source AI OSAI Definition Process Timeline Open Weights FAQ Checklist Forum Community Become an Individual Member Become an OSI Affiliate Affiliate Organizations Maintainers Events Forum OpenSource.net The content on this website, of which Opensource.org is the author, is licensed under a Creative Commons Attribution 4.0 International License . Opensource.org is not the author of any of the licenses reproduced on this site. Questions about the copyright in a license should be directed to the license steward. Read our Privacy Policy Proudly powered by WordPress. Hosted by Pressable. Manage Cookie Consent To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions. Functional Functional Always active The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network. Preferences Preferences The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user. Statistics Statistics The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you. Marketing Marketing The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes. Manage options Manage services Manage {vendor_count} vendors Read more about these purposes Accept Deny View preferences Save preferences View preferences {title} {title} {title} Manage consent | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb5-5 | YAML? That’s Norway problem < Back to LAB174.com YAML? That’s Norway problem 2026-01-12 Abstract A deep dive into YAML’s Norway problem: why the country code NO gets parsed as false, its history from YAML v1.0 to v1.2, and why popular libraries still exhibit this behavior in 2026. What is yaml Yaml is a well-known data serialization language designed for human readability. It’s a popular choice for configuration files and metadata. Here’s a simple example: # project.yaml title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse countries : - DE - FR - PL - RO Let’s verify that the above example parses correctly. We’ll use Python 1 with Py Yaml 2 version 6.0.3 (the latest version as of this writing). First, let’s install it: python3 -m pip install pyyaml==6.0.3 Now let’s write a simple script to parse the yaml file: # python-pyyaml.py import json import yaml with open ( "project.yaml" , "r" , encoding = "utf-8" ) as f: data = yaml.safe_load(f) print (json.dumps(data, indent = 2 )) Running python3 python-pyyaml.py produces this output: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , "PL" , "RO" ] } So far everything behaves as expected. As of January 2026 Python is the world’s 4th most popular programming language according to a 2025 Stack Overflow Survey ( archive ) ↩︎ Py Yaml is Python’s most popular yaml library and a top 20 Python library overall in the last month according to PyPI Stats ( archive ). It is also an “official” yaml library in the sense that its source code is hosted in a Github repository owned by the yaml Github account; see: Canonical source repository for Py Yaml . ↩︎ The Norway problem in yaml When we change the original yaml file and add Norway’s two letter iso country code to the existing list: countries : - DE - FR - NO - PL - RO Using the same parsing method, the file now yields this result: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , false , "PL" , "RO" ] } Note that NO has been replaced with false . This is unexpected. Nothing about the context suggests a boolean should appear here. The NO literal sits in a list of country codes like FR or PL and appears similar in form. The problem, of course, is that “no” is also an English word with a negative meaning. This feature was originally added to allow writing booleans in a more human readable way, e.g.: platforms : iPhone : yes iPad : yes AppleWatch : no This gets parsed as: { "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false } } The idea was that configuration files should read like natural language. In practice this behavior proved problematic, becoming the notorious Norway problem in yaml . One workaround is to escape the string, like this: countries : - DE - FR - "NO" - PL - RO With quotes, the file parses as expected: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } Many articles about yaml ’s Norway problem stop here, presenting quoting as the canonical fix. There is more. Yaml ’s history To understand today’s state of the Norway problem we’ll first look at how yaml evolved. May 2001 – Yaml first pass specification At this time, yaml was more of a concept than a finished language. It looked a bit different, though somewhat recognizable. Below is a partial example from the original specification; there are more in the full document, sadly none with boolean values. buyer : % address : % city : Royal Oak line one : 458 Wittigen's Way line two : Suite 292 postal : 48046 state : MI family name : Dumars given name : Chris The document makes no mention of parsing no to false . The “Serilization Format / bnf ” section even contains a typo and a “to do” note 3 : This section contains the bnf 4 productions for the yaml syntax. Much to do… Full first pass specification – archived link ↩︎ Bnf stands for “Backus–Naur form”, a notation system for syntax definition ( Wikipedia ). ↩︎ January 2004 – Yaml v1.0 final draft This version describes various ways of presenting scalars 5 , including both quoted scalars and plain scalars with implicit typing. This is what we’re after. Version 1.0 defined only sequence , map , and string as mandatory types 6 . The rest were optional, but a reference specification existed. That reference specification for the optional boolean type included English word format. Supported words were: true/false , on/off , and also yes/no 7 . This allows the Norway problem to appear – even if following that part of reference is described as optional. – Bonus: implicit typing can be overridden with explicit tags – we’ll talk about this later. – Bonus: single sign characters, i.e. + and - should also be treated as true and false ; even more so, as they are described as the canonical form 8 ! A scalar data type, or just scalar, is any non-composite value. Generally, all basic primitive data types are considered scalar source: Wikipedia ↩︎ Following is a description of the three mandatory core tags. Yaml requires support for the seq, map and str tags. source: Yaml v1.0 specification, tag repository ↩︎ English word format: implicit english ~= true|True|TRUE |false|False|FALSE |yes|Yes|YES |no|No|NO |on|On|ON |off|Off|OFF source: Yaml v1.0 boolean type specification – archived link ↩︎ Single sign character format: implicit canonical ~= +|- source: Yaml v1.0 boolean type specification – archived link ↩︎ January 2005 – Yaml v1.1 final draft Version 1.1 maintained the same implicit typing behavior as v1.0. However, the types listed in the spec – including boolean – while still not mandatory, were now strongly recommended 9 . – Bonus: single sign characters are no longer included and the canonical form is now y/n 10 . these tags represent types that are useful across a wide range of applications and it is strongly recommended they be used whenever appropriate to promote interoperability. source: Yaml v1.1 specification, tag repository ( archive ) ↩︎ Yaml v1.1 boolean type specification , ( archive ) ↩︎ July 2009 – Yaml Revision 1.2.0 Its goal was to make yaml compliant with json , going as far as allowing json to be a subset of yaml 11 . Implicit typing rules have been removed, including the boolean English word format. – Bonus: explicit typing rules are still present. On paper, the Norway problem shouldn’t exist anymore, at least not since this yaml revision. So why are we still seeing it in 2026? The primary objective of this revision is to bring Yaml into compliance with json as an official subset. source: Yaml revision v1.2.0 ↩︎ Yaml spec version history until v1.2.0 Yaml spec version Date Type of no : Value of no first pass specification May 2001 unspecified unspecified v1.0 January 2004 boolean false v1.1 January 2005 boolean false v1.2.0 July 2009 string "no" Table 1: Summary of yaml spec changes. Note that “Type of no ” and “Value of no ” labels refer to the literal without quotes. Yaml in practice To understand why the Norway problem persists, we need to examine the scope of work involved in implementing yaml spec changes. Some clues are present in earlier text already, we see that yaml supports implicit typing, explicit typing, and various presenting formats. Also, the time between different yaml spec version releases is measured in years. What hides between the lines is that yaml and its specification are very, hugely, extremely complex. Seriously, it’s hard to overstate this. Since v1.0 yaml ’s goal was to build upon xml 12 and a number of other technologies, as listed in the final draft 13 : Yaml integrates and builds upon concepts described by C, Java, Perl, Python, Ruby, rfc0822 ( mail ), rfc1866 ( html ), rfc2045 ( mime ), rfc2396 ( uri ), xml , sax and soap Yaml supports attachments, custom tags, references – the list goes on. There was even yaxml , an xml binding for yaml 14 . There are 9 ways of writing multiline strings – and some claim the number is actually 63 15 . Characters like ? , ! , !! in some cases have special meanings, with the latter allowing arbitrary code execution. Given this complexity, the Norway problem wasn’t the only language quirk in yaml v1.1. Revision v1.2 simplified boolean behavior and more (e.g. handling of null and numerical values), while other language features remained unchanged. How did libraries react to changes in such a complex specification? In fact yaml was originally intended to be a markup language and its name stood for “Yet Another Markup Language”. Six months after the first pass specification, in January 2002, it was renamed to “ Yaml Ain’t Markup Language”. ↩︎ Yaml v1.0 specification, prior art ↩︎ a subset of xml which has yaml ’s information model, but xml ’s syntax (…) a xslt Stylesheet is provided, along with the canonical invoice example in xml using this schema source: Yaxml , the (draft) xml Binding for yaml – archived link ↩︎ There are 5 6 NINE (or 63, depending how you count) different ways to write multi-line strings in yaml . (…) 2 block styles, each with 2 possible block chomping indicators (or none), and with 9 possible indentation indicators (or none), 1 plain style and 2 quoted styles: 2 x (2 + 1) x (9 + 1) + 1 + 2 = 63 source: Stack Overflow answer ( archived ) ↩︎ Yaml libraries As of January 2026 popular yaml libraries still haven’t moved from v1.1 to v1.2, and they still exhibit the Norway problem. Smaller alternative projects have appeared, but their usage hasn’t surpassed the existing v1.1 libraries. Some users have built their own alternative parsers, mixing v1.1 and v1.2 features, or focusing on a subset of yaml suited to their needs. Below are some examples. Py Yaml As mentioned before, Py Yaml is Python’s most popular yaml library and one of the most popular Python libraries overall. Py Yaml never added v1.2 support. There is an open issue from 2017 in Py Yaml ’s Github project about introducing support for v1.2 16 . There are at least two more related open issues, plus several closed ones. An unofficial library 17 exists that can be used on top of Py Yaml to provide partial v1.2 support (its documentation notes that not all v1.2 features are implemented). Another Python library, ruamel.yaml 18 , supports v1.2 by default. Py Yaml Github Issue #116 ↩︎ yamlcore PyPI project page ↩︎ ruamel.yaml PyPI project page ↩︎ Lib Yaml Lib Yaml is the long-standing C library for yaml , it is used widely as a dependency by other tools and bindings. Like Py Yaml , it’s an “official” implementation – in the sense that its canonical repository is hosted on Github and owned by the official ‘yaml’ Github account. Lib Yaml also never added v1.2 support. An open issue from 2016 in Lib Yaml ’s github project requests adding v1.2 support 19 . As mentioned earlier, Lib Yaml sits deep in dependency trees; changing its behavior is especially risky and slow. A less popular library, libfyaml 20 , supports v1.2 by default. Lib Yaml Github Issue #20 ↩︎ libfyaml Github project page ↩︎ Golang’s gopkg.in/yaml.v3 Currently unmaintained 21 , historically the most popular and still holds more Github stars then other Golang yaml libraries. It’s especially interesting because it declares support for a mix of v1.1 and 1.2 22 . The Golang’s most popular actively maintained library 23 defaults to v1.2 behavior. “This project is unmaintained” , source: gopkg.in/yaml.v3 Github project page ↩︎ “The yaml package supports most of yaml 1.2, but preserves some behavior from 1.1 for backwards compatibility.” , source: gopkg.in/yaml.v3 Github project page ↩︎ goccy/go-yaml Github project page ↩︎ Kyaml Kyaml is a yaml dialect built for the Kubernetes project, launched in June 2025. Its goal is to provide a safer and less ambiguous tool; it is also designed specifically for Kubernetes, trading generality for predictability. The announcement blog post references the Norway problem directly 24 . Yaml ’s significant whitespace requires careful attention to indentation and nesting, while its optional string-quoting can lead to unexpected type coercion (for example: “The Norway Bug”). source: Kubernetes v1.34 Sneak Peek ↩︎ Is the Norway problem solved? Yaml ’s ecosystem is not just libraries, it’s also the community of users. Including: strong and conflicting opinions about yaml in general and the Norway problem in particular. In some part this outcome could be expected; after all yaml is very popular, deceptively complex, and is used in different kinds of scenarios, from small personal config files to critical infrastructure setups. Many texts don’t distinguish between yaml spec versions at all 25 . Even when spec version numbers are used, they’re frequently mistyped. It’s not difficult to find documentation claiming that implicit boolean typing is a trait of yaml specification version 1.2 26 (the correct version is v1.1); mistakes get spotted 27 and eventually updated, but that takes more time and effort than making the original typo. On the other hand we see users who declare the Norway problem as solved because it doesn’t exist in the latest spec version, or because they haven’t experienced it themselves, or for other reasons 28 . To be fair, that language feature was removed over a decade ago, and it’s unexpected that popular libraries still support the older spec version. Technically, the issue is solved in the spec – but in practice, most widely adopted implementations still support implicit boolean typing, as we’ve seen. Finally, there are end users who are so unhappy with yaml that they prefer almost anything else 29 . We end up with countless use cases (hobby, pro, critical infrastructure, …), roles (spec author, library maintainer, end user debugging a failed deployment at 11pm, …), and just as many points of views. The yaml specification defines many strings that are automatically interpreted as boolean values, which often conflicts with developer expectations. When you write country: NO , the yaml parser interprets NO as the boolean false , not the string "NO" source: What is the Norway Bug? ↩︎ The most tragic aspect of this bug , however, is that it is intended behavior according to the yaml 1.2 specification. source: The Norway Problem – why Strict Yaml refuses to do implicit typing and so should you ↩︎ In this case a Github issue has been created: It was intended according to the yaml 1.1 specification, but in yaml 1.2, the only recognized booleans are true , True , TRUE , false , False , FALSE . source: strictyaml Github issue #186 ↩︎ I don’t want to link to individual messages on social platforms to err on the side of users’ privacy; I’ll paraphrase some of them below, for illustration purposes. Norway problem has been solved for 16 years. Using 1.1 at this point is just forehead palming foolishness. The Norway issue is a bit blown out of proportion. I have been using YAML for 5+ years and have never had it. We stopped having this problem over ten years ago. Just quote your strings. Another solution is to change the country name. ↩︎ Same as earlier, I’ll paraphrase a few messages below, meant for illustration. Stop using YAML YAML - just say Norway. You should stop even tolerating YAML, refuse on sight. YAML made sense before JSON became a thing. YAML made me look at XML wistfully. Why people persist with YAML in new projects is baffling to me. People from Norway couldn't sign up. Took us a while to figure out. ↩︎ What next? In yaml final draft v1.0, the document specified that, along with yes and no , + and - should also be parsed as booleans. This was removed v1.1. There was an idea to keep that functionality when plus or minus signs were preceded with a dot ( .+ and .- ), but it didn’t catch on. Despite its well known and lesser known quirks, yaml remains popular and widely used. At this scale small quirks cascade into unexpected issues. And changes – or fixes – are introduced at a glacial pace. Then again, yaml ’s charm has its place, as evidenced by its popularity. While spec change adoption is very slow, it is still ongoing. New projects will likely adopt newer libraries, where the Norway problem no longer exists. If there is a single takeaway from this article, it’s this: yaml ecosystem is fragmented; on the whole it is moving towards a slightly stricter version. Implicit boolean typing is getting removed, it’s no longer in the official specification and most new libraries adhere to that. As of January 2026 however, the older libraries are stuck on the older version of the spec, they are still more popular and updating or phasing them out may take a while. Frequently Asked Questions Why not just use json in place of yaml ? A common reply is “no comments” – because json doesn’t support comments 30 ; many other yaml features aren’t supported either. This makes json a simpler and stricter alternative. Wheter that’s a better fit for your project, that depends on the project. As always, personal preference plays a role too. Note: json has its own flavors, like jsonc 31 . It was a conscious decision; there is an explanation from Douglas Crockford, as well as a suggestion about using json for configuration files: I removed comments from json because I saw people were using them to hold parsing directives, a practice which would have destroyed interoperability. I know that the lack of comments makes some people sad, but it shouldn’t. Suppose you are using json to keep configuration files, which you would like to annotate. Go ahead and insert all the comments you like. Then pipe it through JSMin before handing it to your json parser. source: Google Plus post by Douglas Crockford – archived link ↩︎ Json with Comments – project’s homepage ↩︎ Is yaml a superset of json ? After writing this article, I’m still not entirely sure. Even though the goal of yaml revision v1.2.0 was to make that happen and revisions 1.2.0 and 1.2.1 claimed it explicitly 32 : Yaml can therefore be viewed as a natural superset of json , offering improved human readability and a more complete information model. That text has been removed from the latest yaml revision 1.2.2. A popular article 33 claims to prove that yaml is not a superset of json , but that article uses a v1.1 parser – and as we know v1.1 never claimed json compatibility. So that won’t help us. The actual reason might be that yaml requires maps to have unique keys 34 , while json only recommends it 35 . So perhaps most json (i.e. json where objects have unique keys) is a subset of yaml . Some ambiguity remains. See e.g.: Yaml Version 1.2 Revision 1.2.1 ↩︎ Json treats the value 1e2 a number, of course, because it’s not in quote marks. Yaml fails to parse it as a number so silently falls back to treating it as a string. source: YAML IS NOT A SUPERSET OF JSON ↩︎ The content of a mapping node is an unordered set of key/value node pairs, with the restriction that each of the keys is unique source: Yaml Version 1.2 Revision 1.2.2 ↩︎ The names within an object SHOULD be unique. source: The application/json Media Type for JavaScript Object Notation ( json ) ↩︎ What went wrong? This question is out of scope for this article – here the goal is to prioritize facts over “what if?”. If i had to answer, I’d say that nothing went wrong. When a complex technology with a stable ecosystem introduces a breaking change, sometimes the process can take ages. The main surprise here is how complicated yaml really is. Also, as we’ve seen, with yaml and related tools being free software, anyone could contribute to improving the v1.2 adoption rate – or move to a tool that suits them better, or even create one. What about toml , sexagesimal numbers, schemas, human genes, Ruby, or Perl? These topics are only loosely related to the Norway problem, and this text is already quite long. If you enjoyed reading it, leave positive feedback somewhere and a Part 2 might happen. In the meantime, visit my homepage 36 and check out my other projects – maybe you’ll find something else you’ll enjoy. LAB174 homepage ↩︎ Epilogue Implicit boolean typing has been removed, but explicit boolean typing still remains. If a uniform yaml 1.2 future actually arrives, you can still bring a little bit of nostalgia to your code by writing: title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse platforms : iPhone : !!bool yes iPad : !!bool yes # Note the explicit typing here and above. AppleWatch : !!bool no countries : - DE - FR - NO - PL - RO When parsed with yq , a tool that supports yaml revision 1.2 by default: yq eval -o=json project.yaml It returns: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } < Back to LAB174.com | 2026-01-13T08:48:04 |
https://github.com/skills/reusable-workflows | GitHub - skills/reusable-workflows: Make a workflow reusable, call it in another workflow, and use a matrix strategy to run multiple versions. Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} skills / reusable-workflows Public template Notifications You must be signed in to change notification settings Fork 56 Star 94 Make a workflow reusable, call it in another workflow, and use a matrix strategy to run multiple versions. License MIT license 94 stars 56 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 0 Pull requests 3 Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Security Insights skills/reusable-workflows main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 26 Commits .github .github .gitignore .gitignore LICENSE LICENSE README.md README.md View all files Repository files navigation README Code of conduct Contributing MIT license Security Reusable workflows and matrix strategies Make a workflow reusable, call it in another workflow, and use a matrix strategy to run multiple versions. Welcome Reusable workflows offer a simple and powerful way to avoid copying and pasting workflows across your repositories, and adding a matrix strategy lets you use variables in a single job definition to automatically create multiple job runs. Who is this for : Developers, DevOps engineers, students, managers, teams, GitHub users. What you'll learn : How to create and use reusable workflows, create a matrix strategy, trigger workflows, and find workflow logs. What you'll build : An Actions workflow with a matrix strategy that calls a reusable workflow to output multiple versions of node. Prerequisites : In this course you will work with pull requests and YAML workflow files. We recommend you take the Introduction to GitHub course first or be familiar with GitHub basics, and the Hello GitHub Actions course for an introduction to GitHub Actions and workflow files. How long : This course can be finished in less than one hour. Attribution : This Skills course was inspired by a demo video created by Mickey Gousset ( @mickeygousset ). In this course, you will: Make a reusable workflow Add a job Add a matrix strategy Merge your pull request Trigger the workflow How to start this course Right-click Start course and open the link in a new tab. In the new tab, most of the prompts will automatically fill in for you. For owner, choose your personal account or an organization to host the repository. We recommend creating a public repository, as private repositories will use Actions minutes . Scroll down and click the Create repository button at the bottom of the form. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README. Get help: Post in our discussion board • Review the GitHub status page © 2023 GitHub • Code of Conduct • MIT License About Make a workflow reusable, call it in another workflow, and use a matrix strategy to run multiple versions. Topics actions workflows github-actions skills-course matrix-strategy Resources Readme License MIT license Code of conduct Code of conduct Contributing Contributing Security policy Security policy Uh oh! There was an error while loading. Please reload this page . Activity Custom properties Stars 94 stars Watchers 5 watching Forks 56 forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 10 Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:48:04 |
https://www.canva.com/design/DAF-itbw1no/sQYdB114lLt4ec-cV-qTlQ/view?utm_content=DAF-itbw1no&utm_campaign=designshare&utm_medium=link&utm_source=editor#17 | Unsupported client – Canva Please update your browser It seems you are using an old or unsupported browser. To continue enjoying Canva, please update to a recent version of one of the following browsers: Chrome Firefox Safari (macOS only) Edge Alternatively click here to get Canva for Android or iOS. Or click here to learn more about Canva. | 2026-01-13T08:48:04 |
https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fviclafouch%2Fpromise-allsettled-vs-promise-all-in-javascript-4mle&title=%F0%9F%A4%9D%20Promise.allSettled%28%29%20VS%20Promise.all%28%29%20in%20JavaScript%20%F0%9F%8D%AD&summary=Hello%20%21%20%F0%9F%A7%91%E2%80%8D%F0%9F%8C%BE%20%20Promises%20are%20available%20since%20ES2015%20to%20simplify%20the%20handling%20of%20asynchronous%20operations....&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? 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:48:04 |
https://www.canva.com/design/DAF-itbw1no/sQYdB114lLt4ec-cV-qTlQ/view?utm_content=DAF-itbw1no&utm_campaign=designshare&utm_medium=link&utm_source=editor#22 | Unsupported client – Canva Please update your browser It seems you are using an old or unsupported browser. To continue enjoying Canva, please update to a recent version of one of the following browsers: Chrome Firefox Safari (macOS only) Edge Alternatively click here to get Canva for Android or iOS. Or click here to learn more about Canva. | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb4-7 | YAML? That’s Norway problem < Back to LAB174.com YAML? That’s Norway problem 2026-01-12 Abstract A deep dive into YAML’s Norway problem: why the country code NO gets parsed as false, its history from YAML v1.0 to v1.2, and why popular libraries still exhibit this behavior in 2026. What is yaml Yaml is a well-known data serialization language designed for human readability. It’s a popular choice for configuration files and metadata. Here’s a simple example: # project.yaml title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse countries : - DE - FR - PL - RO Let’s verify that the above example parses correctly. We’ll use Python 1 with Py Yaml 2 version 6.0.3 (the latest version as of this writing). First, let’s install it: python3 -m pip install pyyaml==6.0.3 Now let’s write a simple script to parse the yaml file: # python-pyyaml.py import json import yaml with open ( "project.yaml" , "r" , encoding = "utf-8" ) as f: data = yaml.safe_load(f) print (json.dumps(data, indent = 2 )) Running python3 python-pyyaml.py produces this output: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , "PL" , "RO" ] } So far everything behaves as expected. As of January 2026 Python is the world’s 4th most popular programming language according to a 2025 Stack Overflow Survey ( archive ) ↩︎ Py Yaml is Python’s most popular yaml library and a top 20 Python library overall in the last month according to PyPI Stats ( archive ). It is also an “official” yaml library in the sense that its source code is hosted in a Github repository owned by the yaml Github account; see: Canonical source repository for Py Yaml . ↩︎ The Norway problem in yaml When we change the original yaml file and add Norway’s two letter iso country code to the existing list: countries : - DE - FR - NO - PL - RO Using the same parsing method, the file now yields this result: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , false , "PL" , "RO" ] } Note that NO has been replaced with false . This is unexpected. Nothing about the context suggests a boolean should appear here. The NO literal sits in a list of country codes like FR or PL and appears similar in form. The problem, of course, is that “no” is also an English word with a negative meaning. This feature was originally added to allow writing booleans in a more human readable way, e.g.: platforms : iPhone : yes iPad : yes AppleWatch : no This gets parsed as: { "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false } } The idea was that configuration files should read like natural language. In practice this behavior proved problematic, becoming the notorious Norway problem in yaml . One workaround is to escape the string, like this: countries : - DE - FR - "NO" - PL - RO With quotes, the file parses as expected: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } Many articles about yaml ’s Norway problem stop here, presenting quoting as the canonical fix. There is more. Yaml ’s history To understand today’s state of the Norway problem we’ll first look at how yaml evolved. May 2001 – Yaml first pass specification At this time, yaml was more of a concept than a finished language. It looked a bit different, though somewhat recognizable. Below is a partial example from the original specification; there are more in the full document, sadly none with boolean values. buyer : % address : % city : Royal Oak line one : 458 Wittigen's Way line two : Suite 292 postal : 48046 state : MI family name : Dumars given name : Chris The document makes no mention of parsing no to false . The “Serilization Format / bnf ” section even contains a typo and a “to do” note 3 : This section contains the bnf 4 productions for the yaml syntax. Much to do… Full first pass specification – archived link ↩︎ Bnf stands for “Backus–Naur form”, a notation system for syntax definition ( Wikipedia ). ↩︎ January 2004 – Yaml v1.0 final draft This version describes various ways of presenting scalars 5 , including both quoted scalars and plain scalars with implicit typing. This is what we’re after. Version 1.0 defined only sequence , map , and string as mandatory types 6 . The rest were optional, but a reference specification existed. That reference specification for the optional boolean type included English word format. Supported words were: true/false , on/off , and also yes/no 7 . This allows the Norway problem to appear – even if following that part of reference is described as optional. – Bonus: implicit typing can be overridden with explicit tags – we’ll talk about this later. – Bonus: single sign characters, i.e. + and - should also be treated as true and false ; even more so, as they are described as the canonical form 8 ! A scalar data type, or just scalar, is any non-composite value. Generally, all basic primitive data types are considered scalar source: Wikipedia ↩︎ Following is a description of the three mandatory core tags. Yaml requires support for the seq, map and str tags. source: Yaml v1.0 specification, tag repository ↩︎ English word format: implicit english ~= true|True|TRUE |false|False|FALSE |yes|Yes|YES |no|No|NO |on|On|ON |off|Off|OFF source: Yaml v1.0 boolean type specification – archived link ↩︎ Single sign character format: implicit canonical ~= +|- source: Yaml v1.0 boolean type specification – archived link ↩︎ January 2005 – Yaml v1.1 final draft Version 1.1 maintained the same implicit typing behavior as v1.0. However, the types listed in the spec – including boolean – while still not mandatory, were now strongly recommended 9 . – Bonus: single sign characters are no longer included and the canonical form is now y/n 10 . these tags represent types that are useful across a wide range of applications and it is strongly recommended they be used whenever appropriate to promote interoperability. source: Yaml v1.1 specification, tag repository ( archive ) ↩︎ Yaml v1.1 boolean type specification , ( archive ) ↩︎ July 2009 – Yaml Revision 1.2.0 Its goal was to make yaml compliant with json , going as far as allowing json to be a subset of yaml 11 . Implicit typing rules have been removed, including the boolean English word format. – Bonus: explicit typing rules are still present. On paper, the Norway problem shouldn’t exist anymore, at least not since this yaml revision. So why are we still seeing it in 2026? The primary objective of this revision is to bring Yaml into compliance with json as an official subset. source: Yaml revision v1.2.0 ↩︎ Yaml spec version history until v1.2.0 Yaml spec version Date Type of no : Value of no first pass specification May 2001 unspecified unspecified v1.0 January 2004 boolean false v1.1 January 2005 boolean false v1.2.0 July 2009 string "no" Table 1: Summary of yaml spec changes. Note that “Type of no ” and “Value of no ” labels refer to the literal without quotes. Yaml in practice To understand why the Norway problem persists, we need to examine the scope of work involved in implementing yaml spec changes. Some clues are present in earlier text already, we see that yaml supports implicit typing, explicit typing, and various presenting formats. Also, the time between different yaml spec version releases is measured in years. What hides between the lines is that yaml and its specification are very, hugely, extremely complex. Seriously, it’s hard to overstate this. Since v1.0 yaml ’s goal was to build upon xml 12 and a number of other technologies, as listed in the final draft 13 : Yaml integrates and builds upon concepts described by C, Java, Perl, Python, Ruby, rfc0822 ( mail ), rfc1866 ( html ), rfc2045 ( mime ), rfc2396 ( uri ), xml , sax and soap Yaml supports attachments, custom tags, references – the list goes on. There was even yaxml , an xml binding for yaml 14 . There are 9 ways of writing multiline strings – and some claim the number is actually 63 15 . Characters like ? , ! , !! in some cases have special meanings, with the latter allowing arbitrary code execution. Given this complexity, the Norway problem wasn’t the only language quirk in yaml v1.1. Revision v1.2 simplified boolean behavior and more (e.g. handling of null and numerical values), while other language features remained unchanged. How did libraries react to changes in such a complex specification? In fact yaml was originally intended to be a markup language and its name stood for “Yet Another Markup Language”. Six months after the first pass specification, in January 2002, it was renamed to “ Yaml Ain’t Markup Language”. ↩︎ Yaml v1.0 specification, prior art ↩︎ a subset of xml which has yaml ’s information model, but xml ’s syntax (…) a xslt Stylesheet is provided, along with the canonical invoice example in xml using this schema source: Yaxml , the (draft) xml Binding for yaml – archived link ↩︎ There are 5 6 NINE (or 63, depending how you count) different ways to write multi-line strings in yaml . (…) 2 block styles, each with 2 possible block chomping indicators (or none), and with 9 possible indentation indicators (or none), 1 plain style and 2 quoted styles: 2 x (2 + 1) x (9 + 1) + 1 + 2 = 63 source: Stack Overflow answer ( archived ) ↩︎ Yaml libraries As of January 2026 popular yaml libraries still haven’t moved from v1.1 to v1.2, and they still exhibit the Norway problem. Smaller alternative projects have appeared, but their usage hasn’t surpassed the existing v1.1 libraries. Some users have built their own alternative parsers, mixing v1.1 and v1.2 features, or focusing on a subset of yaml suited to their needs. Below are some examples. Py Yaml As mentioned before, Py Yaml is Python’s most popular yaml library and one of the most popular Python libraries overall. Py Yaml never added v1.2 support. There is an open issue from 2017 in Py Yaml ’s Github project about introducing support for v1.2 16 . There are at least two more related open issues, plus several closed ones. An unofficial library 17 exists that can be used on top of Py Yaml to provide partial v1.2 support (its documentation notes that not all v1.2 features are implemented). Another Python library, ruamel.yaml 18 , supports v1.2 by default. Py Yaml Github Issue #116 ↩︎ yamlcore PyPI project page ↩︎ ruamel.yaml PyPI project page ↩︎ Lib Yaml Lib Yaml is the long-standing C library for yaml , it is used widely as a dependency by other tools and bindings. Like Py Yaml , it’s an “official” implementation – in the sense that its canonical repository is hosted on Github and owned by the official ‘yaml’ Github account. Lib Yaml also never added v1.2 support. An open issue from 2016 in Lib Yaml ’s github project requests adding v1.2 support 19 . As mentioned earlier, Lib Yaml sits deep in dependency trees; changing its behavior is especially risky and slow. A less popular library, libfyaml 20 , supports v1.2 by default. Lib Yaml Github Issue #20 ↩︎ libfyaml Github project page ↩︎ Golang’s gopkg.in/yaml.v3 Currently unmaintained 21 , historically the most popular and still holds more Github stars then other Golang yaml libraries. It’s especially interesting because it declares support for a mix of v1.1 and 1.2 22 . The Golang’s most popular actively maintained library 23 defaults to v1.2 behavior. “This project is unmaintained” , source: gopkg.in/yaml.v3 Github project page ↩︎ “The yaml package supports most of yaml 1.2, but preserves some behavior from 1.1 for backwards compatibility.” , source: gopkg.in/yaml.v3 Github project page ↩︎ goccy/go-yaml Github project page ↩︎ Kyaml Kyaml is a yaml dialect built for the Kubernetes project, launched in June 2025. Its goal is to provide a safer and less ambiguous tool; it is also designed specifically for Kubernetes, trading generality for predictability. The announcement blog post references the Norway problem directly 24 . Yaml ’s significant whitespace requires careful attention to indentation and nesting, while its optional string-quoting can lead to unexpected type coercion (for example: “The Norway Bug”). source: Kubernetes v1.34 Sneak Peek ↩︎ Is the Norway problem solved? Yaml ’s ecosystem is not just libraries, it’s also the community of users. Including: strong and conflicting opinions about yaml in general and the Norway problem in particular. In some part this outcome could be expected; after all yaml is very popular, deceptively complex, and is used in different kinds of scenarios, from small personal config files to critical infrastructure setups. Many texts don’t distinguish between yaml spec versions at all 25 . Even when spec version numbers are used, they’re frequently mistyped. It’s not difficult to find documentation claiming that implicit boolean typing is a trait of yaml specification version 1.2 26 (the correct version is v1.1); mistakes get spotted 27 and eventually updated, but that takes more time and effort than making the original typo. On the other hand we see users who declare the Norway problem as solved because it doesn’t exist in the latest spec version, or because they haven’t experienced it themselves, or for other reasons 28 . To be fair, that language feature was removed over a decade ago, and it’s unexpected that popular libraries still support the older spec version. Technically, the issue is solved in the spec – but in practice, most widely adopted implementations still support implicit boolean typing, as we’ve seen. Finally, there are end users who are so unhappy with yaml that they prefer almost anything else 29 . We end up with countless use cases (hobby, pro, critical infrastructure, …), roles (spec author, library maintainer, end user debugging a failed deployment at 11pm, …), and just as many points of views. The yaml specification defines many strings that are automatically interpreted as boolean values, which often conflicts with developer expectations. When you write country: NO , the yaml parser interprets NO as the boolean false , not the string "NO" source: What is the Norway Bug? ↩︎ The most tragic aspect of this bug , however, is that it is intended behavior according to the yaml 1.2 specification. source: The Norway Problem – why Strict Yaml refuses to do implicit typing and so should you ↩︎ In this case a Github issue has been created: It was intended according to the yaml 1.1 specification, but in yaml 1.2, the only recognized booleans are true , True , TRUE , false , False , FALSE . source: strictyaml Github issue #186 ↩︎ I don’t want to link to individual messages on social platforms to err on the side of users’ privacy; I’ll paraphrase some of them below, for illustration purposes. Norway problem has been solved for 16 years. Using 1.1 at this point is just forehead palming foolishness. The Norway issue is a bit blown out of proportion. I have been using YAML for 5+ years and have never had it. We stopped having this problem over ten years ago. Just quote your strings. Another solution is to change the country name. ↩︎ Same as earlier, I’ll paraphrase a few messages below, meant for illustration. Stop using YAML YAML - just say Norway. You should stop even tolerating YAML, refuse on sight. YAML made sense before JSON became a thing. YAML made me look at XML wistfully. Why people persist with YAML in new projects is baffling to me. People from Norway couldn't sign up. Took us a while to figure out. ↩︎ What next? In yaml final draft v1.0, the document specified that, along with yes and no , + and - should also be parsed as booleans. This was removed v1.1. There was an idea to keep that functionality when plus or minus signs were preceded with a dot ( .+ and .- ), but it didn’t catch on. Despite its well known and lesser known quirks, yaml remains popular and widely used. At this scale small quirks cascade into unexpected issues. And changes – or fixes – are introduced at a glacial pace. Then again, yaml ’s charm has its place, as evidenced by its popularity. While spec change adoption is very slow, it is still ongoing. New projects will likely adopt newer libraries, where the Norway problem no longer exists. If there is a single takeaway from this article, it’s this: yaml ecosystem is fragmented; on the whole it is moving towards a slightly stricter version. Implicit boolean typing is getting removed, it’s no longer in the official specification and most new libraries adhere to that. As of January 2026 however, the older libraries are stuck on the older version of the spec, they are still more popular and updating or phasing them out may take a while. Frequently Asked Questions Why not just use json in place of yaml ? A common reply is “no comments” – because json doesn’t support comments 30 ; many other yaml features aren’t supported either. This makes json a simpler and stricter alternative. Wheter that’s a better fit for your project, that depends on the project. As always, personal preference plays a role too. Note: json has its own flavors, like jsonc 31 . It was a conscious decision; there is an explanation from Douglas Crockford, as well as a suggestion about using json for configuration files: I removed comments from json because I saw people were using them to hold parsing directives, a practice which would have destroyed interoperability. I know that the lack of comments makes some people sad, but it shouldn’t. Suppose you are using json to keep configuration files, which you would like to annotate. Go ahead and insert all the comments you like. Then pipe it through JSMin before handing it to your json parser. source: Google Plus post by Douglas Crockford – archived link ↩︎ Json with Comments – project’s homepage ↩︎ Is yaml a superset of json ? After writing this article, I’m still not entirely sure. Even though the goal of yaml revision v1.2.0 was to make that happen and revisions 1.2.0 and 1.2.1 claimed it explicitly 32 : Yaml can therefore be viewed as a natural superset of json , offering improved human readability and a more complete information model. That text has been removed from the latest yaml revision 1.2.2. A popular article 33 claims to prove that yaml is not a superset of json , but that article uses a v1.1 parser – and as we know v1.1 never claimed json compatibility. So that won’t help us. The actual reason might be that yaml requires maps to have unique keys 34 , while json only recommends it 35 . So perhaps most json (i.e. json where objects have unique keys) is a subset of yaml . Some ambiguity remains. See e.g.: Yaml Version 1.2 Revision 1.2.1 ↩︎ Json treats the value 1e2 a number, of course, because it’s not in quote marks. Yaml fails to parse it as a number so silently falls back to treating it as a string. source: YAML IS NOT A SUPERSET OF JSON ↩︎ The content of a mapping node is an unordered set of key/value node pairs, with the restriction that each of the keys is unique source: Yaml Version 1.2 Revision 1.2.2 ↩︎ The names within an object SHOULD be unique. source: The application/json Media Type for JavaScript Object Notation ( json ) ↩︎ What went wrong? This question is out of scope for this article – here the goal is to prioritize facts over “what if?”. If i had to answer, I’d say that nothing went wrong. When a complex technology with a stable ecosystem introduces a breaking change, sometimes the process can take ages. The main surprise here is how complicated yaml really is. Also, as we’ve seen, with yaml and related tools being free software, anyone could contribute to improving the v1.2 adoption rate – or move to a tool that suits them better, or even create one. What about toml , sexagesimal numbers, schemas, human genes, Ruby, or Perl? These topics are only loosely related to the Norway problem, and this text is already quite long. If you enjoyed reading it, leave positive feedback somewhere and a Part 2 might happen. In the meantime, visit my homepage 36 and check out my other projects – maybe you’ll find something else you’ll enjoy. LAB174 homepage ↩︎ Epilogue Implicit boolean typing has been removed, but explicit boolean typing still remains. If a uniform yaml 1.2 future actually arrives, you can still bring a little bit of nostalgia to your code by writing: title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse platforms : iPhone : !!bool yes iPad : !!bool yes # Note the explicit typing here and above. AppleWatch : !!bool no countries : - DE - FR - NO - PL - RO When parsed with yq , a tool that supports yaml revision 1.2 by default: yq eval -o=json project.yaml It returns: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } < Back to LAB174.com | 2026-01-13T08:48:04 |
https://addons.mozilla.org/ro/firefox/addon/rentgen/ | Rentgen – Descarcă această extensie pentru 🦊 Firefox (ro) Suplimente pentru Firefox Extensii Teme Mai multe… pentru Firefox Dicționare și pachete lingvistice Site-uri pentru alte browsere Suplimente pentru Android Intră în cont Caută Caută Rentgen de “Internet. Time to act!” Foundation Rentgen to wtyczka, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. 5 (12 revizuiri) 5 (12 revizuiri) 216 utilizatori 216 utilizatori Descarcă Firefox și obține extensia Descarcă fișierul Metadate extensie Capturi de ecran Despre această extensie Rentgen to wtyczka dla przeglądarek opartych o Firefoxa, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. Więcej informacji: https://www.internet-czas-dzialac.pl/odcinek-33-wtyczka-rentgen Funkcje Rentgena: analiza ruchu sieciowego generowanego przez stronę internetową; wizualizacja danych przekazanych do podmiotów trzecich przez odwiedzaną stronę (historia przeglądania użytkownika oraz jego ciasteczka); przygotowywanie zrzutów ekranów narzędzi deweloperskich będących dowodem przekazanych danych do podmiotów trzecich; pomoc w oszacowaniu potencjalnych obszarów roboczych względem zgodności z RODO; generowanie raportu lub treści maila, który można wysłać do administratora oraz Urzędu Ochrony Danych Osobowych. Kod źródłowy Comentarii de la dezvoltator Jeżeli uważasz, że wtyczka Rentgen okazała się przydatna, zostaw nam recenzję. Jeżeli znalazłeś błąd lub masz pomysł na ulepszenie Rentgena, napisz do nas maila: kontakt@internet-czas-dzialac.pl Evaluat cu 5 de către 12 recenzori Intră în cont pentru a evalua această extensie Nu există încă evaluări Evaluarea prin stele a fost salvată 5 12 4 0 3 0 2 0 1 0 Citește toate cele 12 recenzii Permisiuni și date Permisiuni necesare: Să citească și să modifice setările de confidențialitate Să controleze setările proxy ale browserului Să îți acceseze datele pentru toate site-urile web Colectare de date: Dezvoltatorul spune că extensia nu necesită colectarea de date. Află mai multe Mai multe informații Linkurile suplimentului Pagină de start Site pentru asistență E-mail pentru asistență Versiune 0.2.4 Mărime 9,55 MB Ultima actualizare 21 de zile în urmă (23 dec. 2025) Categorii conexe Dezvoltare web Confidențialitate și securitate Licență Numai GNU General Public License v3.0 Politică de confidențialitate Citește politica de confidențialitate pentru acest supliment Istoricul versiunilor Vezi toate versiunile Etichete anti malware anti tracker container privacy security Adaugă în colecție Selectează o colecție Creează o colecție nouă Raportează acest supliment Sprijină acest dezvoltator Dezvoltatorul acestei extensii îți solicită să contribui pentru sprijinirea dezvoltării continue printr-o mică donație. Contribuie acum Du-te pe pagina de start Mozilla Suplimente Despre Blog suplimente Firefox Atelier de extensii Centrul dezvoltatorilor Politicile dezvoltatorilor Blogul comunității Forum Raportează o defecțiune Ghid pentru recenzii Browsere Desktop Mobile Enterprise Produse Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Confidențialitate Cookie-uri Mențiuni legale Cu excepția cazurilor când se specifică altfel, conținutul de pe acest site este licențiat sub licența Creative Commons cu atribuire și distribuire în condiții identice v3.0 sau orice versiune ulterioară. Schimbă limba Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T08:48:04 |
https://dev.to/algorithm_architech | Adyasha Mohanty - 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 Adyasha Mohanty talks in bits believe in queue DS life is abstract data type Joined Joined on Feb 25, 2024 More info about @algorithm_architech 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 0 posts published Comment 1 comment written Tag 10 tags followed Want to connect with Adyasha Mohanty? Create an account to connect with Adyasha Mohanty. 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:48:04 |
https://github.com/skills/introduction-to-codeql | GitHub - skills/introduction-to-codeql: Enable code scanning and secure your code with CodeQL. Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} skills / introduction-to-codeql Public template generated from skills/exercise-template Notifications You must be signed in to change notification settings Fork 159 Star 116 Enable code scanning and secure your code with CodeQL. License MIT license 116 stars 159 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 3 Pull requests 3 Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Security Insights skills/introduction-to-codeql main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 45 Commits .github .github images images server server templates templates .gitignore .gitignore LICENSE LICENSE Pipfile Pipfile Pipfile.lock Pipfile.lock README.md README.md fixme fixme View all files Repository files navigation README Code of conduct Contributing MIT license Security Enable CodeQL to secure your source code Ensuring the security of application source code is a critical step in modern software development. In this GitHub Skills course, you will learn to use GitHub code scanning to identify, resolve, and prevent insecure coding patterns. Welcome Welcome to "Introduction to CodeQL"! 👋 In this course, we will explore using GitHub code scanning, powered by CodeQL , to identify common coding practices that can lead to security vulnerabilities. During this course, we will enable code scanning on your repository to identify, remediate, and prevent vulnerabilities. Code scanning is part of the GitHub Advanced Security (GHAS) product suite. All of the features of Advanced Security are 100% free for open source, public repositories. Who is this for : Developers, security engineers, open source maintainers. What you'll learn : We'll show you how to enable code scanning and identify SQL injection vulnerabilities with CodeQL. What you'll build : A secure software development pipeline that allows you to identify and prevent new security vulnerabilities from being introduced into your production code. Prerequisites : In this course, you'll need a baseline knowledge of GitHub concepts such as pull requests, GitHub Actions, and source code. You'll also need to be familiar with the concepts of Static Application Security Testing (SAST). Don't worry, we'll demistify the complex parts for you 🙂. How long : This course is four steps long and takes less than 30 minutes to complete. How to start this course Right-click Start course and open the link in a new tab. In the new tab, most of the prompts will automatically fill in for you. For owner, choose your personal account or an organization to host the repository. We recommend creating a public repository, as private repositories will use Actions minutes . Scroll down and click the Create repository button at the bottom of the form. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README. Get help: Post in our discussion board • Review the GitHub status page © 2023 GitHub • Code of Conduct • MIT License About Enable code scanning and secure your code with CodeQL. Topics skills-course Resources Readme License MIT license Code of conduct Code of conduct Contributing Contributing Security policy Security policy Uh oh! There was an error while loading. Please reload this page . Activity Custom properties Stars 116 stars Watchers 5 watching Forks 159 forks Report repository Releases No releases published Packages 0 No packages published Uh oh! There was an error while loading. Please reload this page . Contributors 6 Uh oh! There was an error while loading. Please reload this page . Languages Python 90.4% HTML 9.6% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:48:04 |
https://addons.mozilla.org/en-GB/firefox/addon/rentgen/ | Rentgen – Get this Extension for 🦊 Firefox (en-GB) Firefox Browser Add-ons Extensions Themes More… for Firefox Dictionaries & Language Packs Other Browser Sites Add-ons for Android Log in Search Search Rentgen by “Internet. Time to act!” Foundation Rentgen to wtyczka, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. 5 (12 reviews) 5 (12 reviews) 216 Users 216 Users Download Firefox and get the extension Download file Extension Metadata Screenshots About this extension Rentgen to wtyczka dla przeglądarek opartych o Firefoxa, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. Więcej informacji: https://www.internet-czas-dzialac.pl/odcinek-33-wtyczka-rentgen Funkcje Rentgena: analiza ruchu sieciowego generowanego przez stronę internetową; wizualizacja danych przekazanych do podmiotów trzecich przez odwiedzaną stronę (historia przeglądania użytkownika oraz jego ciasteczka); przygotowywanie zrzutów ekranów narzędzi deweloperskich będących dowodem przekazanych danych do podmiotów trzecich; pomoc w oszacowaniu potencjalnych obszarów roboczych względem zgodności z RODO; generowanie raportu lub treści maila, który można wysłać do administratora oraz Urzędu Ochrony Danych Osobowych. Kod źródłowy Developer comments Jeżeli uważasz, że wtyczka Rentgen okazała się przydatna, zostaw nam recenzję. Jeżeli znalazłeś błąd lub masz pomysł na ulepszenie Rentgena, napisz do nas maila: kontakt@internet-czas-dzialac.pl Rated 5 by 12 reviewers Log in to rate this extension There are no ratings yet Star rating saved 5 12 4 0 3 0 2 0 1 0 Read all 12 reviews Permissions and data Required permissions: Read and modify privacy settings Control browser proxy settings Access your data for all web sites Data collection: The developer says this extension doesn't require data collection. Learn more More information Add-on Links Homepage Support site Support Email Version 0.2.4 Size 9.55 MB Last updated 21 days ago (23 Dec 2025) Related Categories Web Development Privacy & Security Licence GNU General Public Licence v3.0 only Privacy Policy Read the privacy policy for this add-on Version History See all versions Tags anti malware anti tracker container privacy security Add to collection Select a collection… Create new collection Report this add-on Support this developer The developer of this extension asks that you help support its continued development by making a small contribution. Contribute now Go to Mozilla's homepage Add-ons About Firefox Add-ons Blog Extension Workshop Developer Hub Developer Policies Community Blog Forum Report a bug Review Guide Browsers Desktop Mobile Enterprise Products Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Privacy Cookies Legal Except where otherwise noted , content on this site is licensed under the Creative Commons Attribution Share-Alike Licence v3.0 or any later version. Change language Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#fnref1 | YAML? That’s Norway problem < Back to LAB174.com YAML? That’s Norway problem 2026-01-12 Abstract A deep dive into YAML’s Norway problem: why the country code NO gets parsed as false, its history from YAML v1.0 to v1.2, and why popular libraries still exhibit this behavior in 2026. What is yaml Yaml is a well-known data serialization language designed for human readability. It’s a popular choice for configuration files and metadata. Here’s a simple example: # project.yaml title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse countries : - DE - FR - PL - RO Let’s verify that the above example parses correctly. We’ll use Python 1 with Py Yaml 2 version 6.0.3 (the latest version as of this writing). First, let’s install it: python3 -m pip install pyyaml==6.0.3 Now let’s write a simple script to parse the yaml file: # python-pyyaml.py import json import yaml with open ( "project.yaml" , "r" , encoding = "utf-8" ) as f: data = yaml.safe_load(f) print (json.dumps(data, indent = 2 )) Running python3 python-pyyaml.py produces this output: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , "PL" , "RO" ] } So far everything behaves as expected. As of January 2026 Python is the world’s 4th most popular programming language according to a 2025 Stack Overflow Survey ( archive ) ↩︎ Py Yaml is Python’s most popular yaml library and a top 20 Python library overall in the last month according to PyPI Stats ( archive ). It is also an “official” yaml library in the sense that its source code is hosted in a Github repository owned by the yaml Github account; see: Canonical source repository for Py Yaml . ↩︎ The Norway problem in yaml When we change the original yaml file and add Norway’s two letter iso country code to the existing list: countries : - DE - FR - NO - PL - RO Using the same parsing method, the file now yields this result: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , false , "PL" , "RO" ] } Note that NO has been replaced with false . This is unexpected. Nothing about the context suggests a boolean should appear here. The NO literal sits in a list of country codes like FR or PL and appears similar in form. The problem, of course, is that “no” is also an English word with a negative meaning. This feature was originally added to allow writing booleans in a more human readable way, e.g.: platforms : iPhone : yes iPad : yes AppleWatch : no This gets parsed as: { "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false } } The idea was that configuration files should read like natural language. In practice this behavior proved problematic, becoming the notorious Norway problem in yaml . One workaround is to escape the string, like this: countries : - DE - FR - "NO" - PL - RO With quotes, the file parses as expected: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } Many articles about yaml ’s Norway problem stop here, presenting quoting as the canonical fix. There is more. Yaml ’s history To understand today’s state of the Norway problem we’ll first look at how yaml evolved. May 2001 – Yaml first pass specification At this time, yaml was more of a concept than a finished language. It looked a bit different, though somewhat recognizable. Below is a partial example from the original specification; there are more in the full document, sadly none with boolean values. buyer : % address : % city : Royal Oak line one : 458 Wittigen's Way line two : Suite 292 postal : 48046 state : MI family name : Dumars given name : Chris The document makes no mention of parsing no to false . The “Serilization Format / bnf ” section even contains a typo and a “to do” note 3 : This section contains the bnf 4 productions for the yaml syntax. Much to do… Full first pass specification – archived link ↩︎ Bnf stands for “Backus–Naur form”, a notation system for syntax definition ( Wikipedia ). ↩︎ January 2004 – Yaml v1.0 final draft This version describes various ways of presenting scalars 5 , including both quoted scalars and plain scalars with implicit typing. This is what we’re after. Version 1.0 defined only sequence , map , and string as mandatory types 6 . The rest were optional, but a reference specification existed. That reference specification for the optional boolean type included English word format. Supported words were: true/false , on/off , and also yes/no 7 . This allows the Norway problem to appear – even if following that part of reference is described as optional. – Bonus: implicit typing can be overridden with explicit tags – we’ll talk about this later. – Bonus: single sign characters, i.e. + and - should also be treated as true and false ; even more so, as they are described as the canonical form 8 ! A scalar data type, or just scalar, is any non-composite value. Generally, all basic primitive data types are considered scalar source: Wikipedia ↩︎ Following is a description of the three mandatory core tags. Yaml requires support for the seq, map and str tags. source: Yaml v1.0 specification, tag repository ↩︎ English word format: implicit english ~= true|True|TRUE |false|False|FALSE |yes|Yes|YES |no|No|NO |on|On|ON |off|Off|OFF source: Yaml v1.0 boolean type specification – archived link ↩︎ Single sign character format: implicit canonical ~= +|- source: Yaml v1.0 boolean type specification – archived link ↩︎ January 2005 – Yaml v1.1 final draft Version 1.1 maintained the same implicit typing behavior as v1.0. However, the types listed in the spec – including boolean – while still not mandatory, were now strongly recommended 9 . – Bonus: single sign characters are no longer included and the canonical form is now y/n 10 . these tags represent types that are useful across a wide range of applications and it is strongly recommended they be used whenever appropriate to promote interoperability. source: Yaml v1.1 specification, tag repository ( archive ) ↩︎ Yaml v1.1 boolean type specification , ( archive ) ↩︎ July 2009 – Yaml Revision 1.2.0 Its goal was to make yaml compliant with json , going as far as allowing json to be a subset of yaml 11 . Implicit typing rules have been removed, including the boolean English word format. – Bonus: explicit typing rules are still present. On paper, the Norway problem shouldn’t exist anymore, at least not since this yaml revision. So why are we still seeing it in 2026? The primary objective of this revision is to bring Yaml into compliance with json as an official subset. source: Yaml revision v1.2.0 ↩︎ Yaml spec version history until v1.2.0 Yaml spec version Date Type of no : Value of no first pass specification May 2001 unspecified unspecified v1.0 January 2004 boolean false v1.1 January 2005 boolean false v1.2.0 July 2009 string "no" Table 1: Summary of yaml spec changes. Note that “Type of no ” and “Value of no ” labels refer to the literal without quotes. Yaml in practice To understand why the Norway problem persists, we need to examine the scope of work involved in implementing yaml spec changes. Some clues are present in earlier text already, we see that yaml supports implicit typing, explicit typing, and various presenting formats. Also, the time between different yaml spec version releases is measured in years. What hides between the lines is that yaml and its specification are very, hugely, extremely complex. Seriously, it’s hard to overstate this. Since v1.0 yaml ’s goal was to build upon xml 12 and a number of other technologies, as listed in the final draft 13 : Yaml integrates and builds upon concepts described by C, Java, Perl, Python, Ruby, rfc0822 ( mail ), rfc1866 ( html ), rfc2045 ( mime ), rfc2396 ( uri ), xml , sax and soap Yaml supports attachments, custom tags, references – the list goes on. There was even yaxml , an xml binding for yaml 14 . There are 9 ways of writing multiline strings – and some claim the number is actually 63 15 . Characters like ? , ! , !! in some cases have special meanings, with the latter allowing arbitrary code execution. Given this complexity, the Norway problem wasn’t the only language quirk in yaml v1.1. Revision v1.2 simplified boolean behavior and more (e.g. handling of null and numerical values), while other language features remained unchanged. How did libraries react to changes in such a complex specification? In fact yaml was originally intended to be a markup language and its name stood for “Yet Another Markup Language”. Six months after the first pass specification, in January 2002, it was renamed to “ Yaml Ain’t Markup Language”. ↩︎ Yaml v1.0 specification, prior art ↩︎ a subset of xml which has yaml ’s information model, but xml ’s syntax (…) a xslt Stylesheet is provided, along with the canonical invoice example in xml using this schema source: Yaxml , the (draft) xml Binding for yaml – archived link ↩︎ There are 5 6 NINE (or 63, depending how you count) different ways to write multi-line strings in yaml . (…) 2 block styles, each with 2 possible block chomping indicators (or none), and with 9 possible indentation indicators (or none), 1 plain style and 2 quoted styles: 2 x (2 + 1) x (9 + 1) + 1 + 2 = 63 source: Stack Overflow answer ( archived ) ↩︎ Yaml libraries As of January 2026 popular yaml libraries still haven’t moved from v1.1 to v1.2, and they still exhibit the Norway problem. Smaller alternative projects have appeared, but their usage hasn’t surpassed the existing v1.1 libraries. Some users have built their own alternative parsers, mixing v1.1 and v1.2 features, or focusing on a subset of yaml suited to their needs. Below are some examples. Py Yaml As mentioned before, Py Yaml is Python’s most popular yaml library and one of the most popular Python libraries overall. Py Yaml never added v1.2 support. There is an open issue from 2017 in Py Yaml ’s Github project about introducing support for v1.2 16 . There are at least two more related open issues, plus several closed ones. An unofficial library 17 exists that can be used on top of Py Yaml to provide partial v1.2 support (its documentation notes that not all v1.2 features are implemented). Another Python library, ruamel.yaml 18 , supports v1.2 by default. Py Yaml Github Issue #116 ↩︎ yamlcore PyPI project page ↩︎ ruamel.yaml PyPI project page ↩︎ Lib Yaml Lib Yaml is the long-standing C library for yaml , it is used widely as a dependency by other tools and bindings. Like Py Yaml , it’s an “official” implementation – in the sense that its canonical repository is hosted on Github and owned by the official ‘yaml’ Github account. Lib Yaml also never added v1.2 support. An open issue from 2016 in Lib Yaml ’s github project requests adding v1.2 support 19 . As mentioned earlier, Lib Yaml sits deep in dependency trees; changing its behavior is especially risky and slow. A less popular library, libfyaml 20 , supports v1.2 by default. Lib Yaml Github Issue #20 ↩︎ libfyaml Github project page ↩︎ Golang’s gopkg.in/yaml.v3 Currently unmaintained 21 , historically the most popular and still holds more Github stars then other Golang yaml libraries. It’s especially interesting because it declares support for a mix of v1.1 and 1.2 22 . The Golang’s most popular actively maintained library 23 defaults to v1.2 behavior. “This project is unmaintained” , source: gopkg.in/yaml.v3 Github project page ↩︎ “The yaml package supports most of yaml 1.2, but preserves some behavior from 1.1 for backwards compatibility.” , source: gopkg.in/yaml.v3 Github project page ↩︎ goccy/go-yaml Github project page ↩︎ Kyaml Kyaml is a yaml dialect built for the Kubernetes project, launched in June 2025. Its goal is to provide a safer and less ambiguous tool; it is also designed specifically for Kubernetes, trading generality for predictability. The announcement blog post references the Norway problem directly 24 . Yaml ’s significant whitespace requires careful attention to indentation and nesting, while its optional string-quoting can lead to unexpected type coercion (for example: “The Norway Bug”). source: Kubernetes v1.34 Sneak Peek ↩︎ Is the Norway problem solved? Yaml ’s ecosystem is not just libraries, it’s also the community of users. Including: strong and conflicting opinions about yaml in general and the Norway problem in particular. In some part this outcome could be expected; after all yaml is very popular, deceptively complex, and is used in different kinds of scenarios, from small personal config files to critical infrastructure setups. Many texts don’t distinguish between yaml spec versions at all 25 . Even when spec version numbers are used, they’re frequently mistyped. It’s not difficult to find documentation claiming that implicit boolean typing is a trait of yaml specification version 1.2 26 (the correct version is v1.1); mistakes get spotted 27 and eventually updated, but that takes more time and effort than making the original typo. On the other hand we see users who declare the Norway problem as solved because it doesn’t exist in the latest spec version, or because they haven’t experienced it themselves, or for other reasons 28 . To be fair, that language feature was removed over a decade ago, and it’s unexpected that popular libraries still support the older spec version. Technically, the issue is solved in the spec – but in practice, most widely adopted implementations still support implicit boolean typing, as we’ve seen. Finally, there are end users who are so unhappy with yaml that they prefer almost anything else 29 . We end up with countless use cases (hobby, pro, critical infrastructure, …), roles (spec author, library maintainer, end user debugging a failed deployment at 11pm, …), and just as many points of views. The yaml specification defines many strings that are automatically interpreted as boolean values, which often conflicts with developer expectations. When you write country: NO , the yaml parser interprets NO as the boolean false , not the string "NO" source: What is the Norway Bug? ↩︎ The most tragic aspect of this bug , however, is that it is intended behavior according to the yaml 1.2 specification. source: The Norway Problem – why Strict Yaml refuses to do implicit typing and so should you ↩︎ In this case a Github issue has been created: It was intended according to the yaml 1.1 specification, but in yaml 1.2, the only recognized booleans are true , True , TRUE , false , False , FALSE . source: strictyaml Github issue #186 ↩︎ I don’t want to link to individual messages on social platforms to err on the side of users’ privacy; I’ll paraphrase some of them below, for illustration purposes. Norway problem has been solved for 16 years. Using 1.1 at this point is just forehead palming foolishness. The Norway issue is a bit blown out of proportion. I have been using YAML for 5+ years and have never had it. We stopped having this problem over ten years ago. Just quote your strings. Another solution is to change the country name. ↩︎ Same as earlier, I’ll paraphrase a few messages below, meant for illustration. Stop using YAML YAML - just say Norway. You should stop even tolerating YAML, refuse on sight. YAML made sense before JSON became a thing. YAML made me look at XML wistfully. Why people persist with YAML in new projects is baffling to me. People from Norway couldn't sign up. Took us a while to figure out. ↩︎ What next? In yaml final draft v1.0, the document specified that, along with yes and no , + and - should also be parsed as booleans. This was removed v1.1. There was an idea to keep that functionality when plus or minus signs were preceded with a dot ( .+ and .- ), but it didn’t catch on. Despite its well known and lesser known quirks, yaml remains popular and widely used. At this scale small quirks cascade into unexpected issues. And changes – or fixes – are introduced at a glacial pace. Then again, yaml ’s charm has its place, as evidenced by its popularity. While spec change adoption is very slow, it is still ongoing. New projects will likely adopt newer libraries, where the Norway problem no longer exists. If there is a single takeaway from this article, it’s this: yaml ecosystem is fragmented; on the whole it is moving towards a slightly stricter version. Implicit boolean typing is getting removed, it’s no longer in the official specification and most new libraries adhere to that. As of January 2026 however, the older libraries are stuck on the older version of the spec, they are still more popular and updating or phasing them out may take a while. Frequently Asked Questions Why not just use json in place of yaml ? A common reply is “no comments” – because json doesn’t support comments 30 ; many other yaml features aren’t supported either. This makes json a simpler and stricter alternative. Wheter that’s a better fit for your project, that depends on the project. As always, personal preference plays a role too. Note: json has its own flavors, like jsonc 31 . It was a conscious decision; there is an explanation from Douglas Crockford, as well as a suggestion about using json for configuration files: I removed comments from json because I saw people were using them to hold parsing directives, a practice which would have destroyed interoperability. I know that the lack of comments makes some people sad, but it shouldn’t. Suppose you are using json to keep configuration files, which you would like to annotate. Go ahead and insert all the comments you like. Then pipe it through JSMin before handing it to your json parser. source: Google Plus post by Douglas Crockford – archived link ↩︎ Json with Comments – project’s homepage ↩︎ Is yaml a superset of json ? After writing this article, I’m still not entirely sure. Even though the goal of yaml revision v1.2.0 was to make that happen and revisions 1.2.0 and 1.2.1 claimed it explicitly 32 : Yaml can therefore be viewed as a natural superset of json , offering improved human readability and a more complete information model. That text has been removed from the latest yaml revision 1.2.2. A popular article 33 claims to prove that yaml is not a superset of json , but that article uses a v1.1 parser – and as we know v1.1 never claimed json compatibility. So that won’t help us. The actual reason might be that yaml requires maps to have unique keys 34 , while json only recommends it 35 . So perhaps most json (i.e. json where objects have unique keys) is a subset of yaml . Some ambiguity remains. See e.g.: Yaml Version 1.2 Revision 1.2.1 ↩︎ Json treats the value 1e2 a number, of course, because it’s not in quote marks. Yaml fails to parse it as a number so silently falls back to treating it as a string. source: YAML IS NOT A SUPERSET OF JSON ↩︎ The content of a mapping node is an unordered set of key/value node pairs, with the restriction that each of the keys is unique source: Yaml Version 1.2 Revision 1.2.2 ↩︎ The names within an object SHOULD be unique. source: The application/json Media Type for JavaScript Object Notation ( json ) ↩︎ What went wrong? This question is out of scope for this article – here the goal is to prioritize facts over “what if?”. If i had to answer, I’d say that nothing went wrong. When a complex technology with a stable ecosystem introduces a breaking change, sometimes the process can take ages. The main surprise here is how complicated yaml really is. Also, as we’ve seen, with yaml and related tools being free software, anyone could contribute to improving the v1.2 adoption rate – or move to a tool that suits them better, or even create one. What about toml , sexagesimal numbers, schemas, human genes, Ruby, or Perl? These topics are only loosely related to the Norway problem, and this text is already quite long. If you enjoyed reading it, leave positive feedback somewhere and a Part 2 might happen. In the meantime, visit my homepage 36 and check out my other projects – maybe you’ll find something else you’ll enjoy. LAB174 homepage ↩︎ Epilogue Implicit boolean typing has been removed, but explicit boolean typing still remains. If a uniform yaml 1.2 future actually arrives, you can still bring a little bit of nostalgia to your code by writing: title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse platforms : iPhone : !!bool yes iPad : !!bool yes # Note the explicit typing here and above. AppleWatch : !!bool no countries : - DE - FR - NO - PL - RO When parsed with yq , a tool that supports yaml revision 1.2 by default: yq eval -o=json project.yaml It returns: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } < Back to LAB174.com | 2026-01-13T08:48:04 |
https://addons.mozilla.org/vi/firefox/addon/rentgen/ | Rentgen - Nhận tiện ích mở rộng này cho 🦊 Firefox (vi) Tiện ích trình duyệt Firefox Tiện ích mở rộng Chủ đề Xem thêm… cho Firefox Từ điển & gói ngôn ngữ Các trang web trình duyệt khác Tiện ích cho Android Đăng nhập Tìm kiếm Tìm kiếm Rentgen bởi “Internet. Time to act!” Foundation Rentgen to wtyczka, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. 5 (12 đánh giá) 5 (12 đánh giá) 216 người dùng 216 người dùng Tải xuống Firefox và tải tiện ích mở rộng Tải xuống tập tin Siêu dữ liệu mở rộng Ảnh chụp màn hình Về tiện ích mở rộng này Rentgen to wtyczka dla przeglądarek opartych o Firefoxa, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. Więcej informacji: https://www.internet-czas-dzialac.pl/odcinek-33-wtyczka-rentgen Funkcje Rentgena: analiza ruchu sieciowego generowanego przez stronę internetową; wizualizacja danych przekazanych do podmiotów trzecich przez odwiedzaną stronę (historia przeglądania użytkownika oraz jego ciasteczka); przygotowywanie zrzutów ekranów narzędzi deweloperskich będących dowodem przekazanych danych do podmiotów trzecich; pomoc w oszacowaniu potencjalnych obszarów roboczych względem zgodności z RODO; generowanie raportu lub treści maila, który można wysłać do administratora oraz Urzędu Ochrony Danych Osobowych. Kod źródłowy Chú thích của nhà phát triển Jeżeli uważasz, że wtyczka Rentgen okazała się przydatna, zostaw nam recenzję. Jeżeli znalazłeś błąd lub masz pomysł na ulepszenie Rentgena, napisz do nas maila: kontakt@internet-czas-dzialac.pl Được xếp hạng 5 (bởi 1 người dùng) Đăng nhập để đánh giá tiện ích này Chưa có xếp hạng nào Đã lưu xếp hạng sao 5 12 4 0 3 0 2 0 1 0 Đọc tất cả 12 đánh giá Quyền hạn và dữ liệu Quyền hạn bắt buộc: Đọc và chỉnh sửa các cài đặt riêng tư Điều khiển cài đặt proxy của trình duyệt Truy cập dữ liệu của bạn trên mọi trang web Thu thập dữ liệu: Nhà phát triển cho biết tiện ích mở rộng này không yêu cầu thu thập dữ liệu. Tìm hiểu thêm Thêm thông tin Liên kết tiện ích Trang chủ Trang hỗ trợ Email hỗ trợ Phiên bản 0.2.4 Kích cỡ 9,55 MB Cập nhật gần nhất 21 ngày trước (23 Thg 12 2025) Thể loại có liên quan Phát triển Web Riêng tư & Bảo mật Giấy phép Chỉ Giấy phép Công cộng GNU v3.0 Chính sách riêng tư Đọc chính sách riêng tư của tiện ích này Lịch sử các phiên bản Xem tất cả phiên bản Nhãn anti malware anti tracker container privacy security Thêm vào bộ sưu tập Chọn một bộ sưu tập... Tạo bộ sưu tập mới Báo cáo tiện ích này Hỗ trợ nhà phát triển này Nhà phát triển của tiện ích mở rộng này yêu cầu bạn giúp hỗ trợ sự phát triển liên tục của nó bằng cách đóng góp nhỏ. Đóng góp ngay bây giờ Đi đến trang chủ Mozilla Tiện ích Giới thiệu Blog tiện ích Firefox Extension Workshop Trung tâm nhà phát triển Chính sách nhà phát triển Blog cộng đồng Diễn đàn Báo cáo một lỗi Hướng dẫn đánh giá Trình duyệt Desktop Mobile Enterprise Sản phẩm Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Riêng tư Cookie Pháp lý Trừ trường hợp khác đã ghi chú , nội dung trên trang này được cấp phép theo giấy phép Creative Commons Attribution Share-Alike v3.0 hoặc bất kỳ phiên bản nào sau này. Thay đổi ngôn ngữ Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T08:48:04 |
https://addons.mozilla.org/fr/firefox/addon/rentgen/ | Rentgen – Adoptez cette extension pour 🦊 Firefox (fr) Modules pour le navigateur Firefox Extensions Thèmes Plus… pour Firefox Dictionnaires et paquetages linguistiques Sites pour les autres navigateurs Modules pour Android Connexion Rechercher Rechercher Rentgen par “Internet. Time to act!” Foundation Rentgen to wtyczka, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. 5 (12 critiques) 5 (12 critiques) 216 utilisateurs·trices 216 utilisateurs·trices Télécharger Firefox et obtenir l’extension Télécharger le fichier Métadonnées de l’extension Captures d’écran À propos de cette extension Rentgen to wtyczka dla przeglądarek opartych o Firefoxa, która automatycznie wizualizuje, jakie dane zostały ~~wykradzione~~ wysłane do podmiotów trzecich przez odwiedzane strony. Pozwala wygenerować raport lub treść maila, który można wysłać do administratora strony i/lub UODO. Więcej informacji: https://www.internet-czas-dzialac.pl/odcinek-33-wtyczka-rentgen Funkcje Rentgena: analiza ruchu sieciowego generowanego przez stronę internetową; wizualizacja danych przekazanych do podmiotów trzecich przez odwiedzaną stronę (historia przeglądania użytkownika oraz jego ciasteczka); przygotowywanie zrzutów ekranów narzędzi deweloperskich będących dowodem przekazanych danych do podmiotów trzecich; pomoc w oszacowaniu potencjalnych obszarów roboczych względem zgodności z RODO; generowanie raportu lub treści maila, który można wysłać do administratora oraz Urzędu Ochrony Danych Osobowych. Kod źródłowy Commentaires du développeur Jeżeli uważasz, że wtyczka Rentgen okazała się przydatna, zostaw nam recenzję. Jeżeli znalazłeś błąd lub masz pomysł na ulepszenie Rentgena, napisz do nas maila: kontakt@internet-czas-dzialac.pl Noté 5 par 12 personnes Connectez-vous pour noter cette extension Il n’y a aucune note pour l’instant Le nombre d’étoiles est enregistré 5 12 4 0 3 0 2 0 1 0 Lire les 12 critiques Autorisations et données Autorisations nécessaires : Consulter et modifier les paramètres de vie privée Contrôler les paramètres proxy du navigateur Accéder à vos données pour tous les sites web Collecte de données : Le développeur indique que cette extension n’a pas besoin de collecter de données. En savoir plus Plus d’informations Liens du module Page d’accueil Site d’assistance E-mail d’assistance Version 0.2.4 Taille 9,55 Mo Dernière mise à jour il y a 21 jours (23 déc. 2025) Catégories associées Développement web Sécurité et vie privée Licence GNU General Public License v3.0 uniquement Politique de confidentialité Lire la politique de confidentialité de ce module Historique des versions Voir toutes les versions Étiquettes anti malware anti tracker container privacy security Ajouter à la collection Sélectionner une collection… Créer une nouvelle collection Signaler ce module Soutenir ce développeur Le développeur de cette extension demande que vous l’aidiez à assurer la poursuite de son développement en lui versant une petite contribution. Contribuer Aller à la page d’accueil de Mozilla Modules complémentaires À propos Blog des modules complémentaires Firefox Atelier sur les extensions Pôle développeur Politiques à destination des développeurs Blog de la communauté Forum Signaler un problème Guide de revue Navigateurs Desktop Mobile Enterprise Produits Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Confidentialité Cookies Mentions légales Sauf mention contraire , le contenu de ce site est disponible sous licence Creative Commons Attribution Share-Alike v3.0 ou toute version supérieure. Changer la langue Čeština Deutsch Dolnoserbšćina Ελληνικά English (Canadian) English (British) English (US) Español (de Argentina) Español (de Chile) Español (de España) Español (de México) suomi Français Furlan Frysk עברית Hrvatski Hornjoserbsce magyar Interlingua Italiano 日本語 ქართული Taqbaylit 한국어 Norsk bokmål Nederlands Norsk nynorsk Polski Português (do Brasil) Português (Europeu) Română Русский slovenčina Slovenščina Shqip Svenska Türkçe Українська Tiếng Việt 中文 (简体) 正體中文 (繁體) | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb3-3 | YAML? That’s Norway problem < Back to LAB174.com YAML? That’s Norway problem 2026-01-12 Abstract A deep dive into YAML’s Norway problem: why the country code NO gets parsed as false, its history from YAML v1.0 to v1.2, and why popular libraries still exhibit this behavior in 2026. What is yaml Yaml is a well-known data serialization language designed for human readability. It’s a popular choice for configuration files and metadata. Here’s a simple example: # project.yaml title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse countries : - DE - FR - PL - RO Let’s verify that the above example parses correctly. We’ll use Python 1 with Py Yaml 2 version 6.0.3 (the latest version as of this writing). First, let’s install it: python3 -m pip install pyyaml==6.0.3 Now let’s write a simple script to parse the yaml file: # python-pyyaml.py import json import yaml with open ( "project.yaml" , "r" , encoding = "utf-8" ) as f: data = yaml.safe_load(f) print (json.dumps(data, indent = 2 )) Running python3 python-pyyaml.py produces this output: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , "PL" , "RO" ] } So far everything behaves as expected. As of January 2026 Python is the world’s 4th most popular programming language according to a 2025 Stack Overflow Survey ( archive ) ↩︎ Py Yaml is Python’s most popular yaml library and a top 20 Python library overall in the last month according to PyPI Stats ( archive ). It is also an “official” yaml library in the sense that its source code is hosted in a Github repository owned by the yaml Github account; see: Canonical source repository for Py Yaml . ↩︎ The Norway problem in yaml When we change the original yaml file and add Norway’s two letter iso country code to the existing list: countries : - DE - FR - NO - PL - RO Using the same parsing method, the file now yields this result: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , false , "PL" , "RO" ] } Note that NO has been replaced with false . This is unexpected. Nothing about the context suggests a boolean should appear here. The NO literal sits in a list of country codes like FR or PL and appears similar in form. The problem, of course, is that “no” is also an English word with a negative meaning. This feature was originally added to allow writing booleans in a more human readable way, e.g.: platforms : iPhone : yes iPad : yes AppleWatch : no This gets parsed as: { "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false } } The idea was that configuration files should read like natural language. In practice this behavior proved problematic, becoming the notorious Norway problem in yaml . One workaround is to escape the string, like this: countries : - DE - FR - "NO" - PL - RO With quotes, the file parses as expected: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } Many articles about yaml ’s Norway problem stop here, presenting quoting as the canonical fix. There is more. Yaml ’s history To understand today’s state of the Norway problem we’ll first look at how yaml evolved. May 2001 – Yaml first pass specification At this time, yaml was more of a concept than a finished language. It looked a bit different, though somewhat recognizable. Below is a partial example from the original specification; there are more in the full document, sadly none with boolean values. buyer : % address : % city : Royal Oak line one : 458 Wittigen's Way line two : Suite 292 postal : 48046 state : MI family name : Dumars given name : Chris The document makes no mention of parsing no to false . The “Serilization Format / bnf ” section even contains a typo and a “to do” note 3 : This section contains the bnf 4 productions for the yaml syntax. Much to do… Full first pass specification – archived link ↩︎ Bnf stands for “Backus–Naur form”, a notation system for syntax definition ( Wikipedia ). ↩︎ January 2004 – Yaml v1.0 final draft This version describes various ways of presenting scalars 5 , including both quoted scalars and plain scalars with implicit typing. This is what we’re after. Version 1.0 defined only sequence , map , and string as mandatory types 6 . The rest were optional, but a reference specification existed. That reference specification for the optional boolean type included English word format. Supported words were: true/false , on/off , and also yes/no 7 . This allows the Norway problem to appear – even if following that part of reference is described as optional. – Bonus: implicit typing can be overridden with explicit tags – we’ll talk about this later. – Bonus: single sign characters, i.e. + and - should also be treated as true and false ; even more so, as they are described as the canonical form 8 ! A scalar data type, or just scalar, is any non-composite value. Generally, all basic primitive data types are considered scalar source: Wikipedia ↩︎ Following is a description of the three mandatory core tags. Yaml requires support for the seq, map and str tags. source: Yaml v1.0 specification, tag repository ↩︎ English word format: implicit english ~= true|True|TRUE |false|False|FALSE |yes|Yes|YES |no|No|NO |on|On|ON |off|Off|OFF source: Yaml v1.0 boolean type specification – archived link ↩︎ Single sign character format: implicit canonical ~= +|- source: Yaml v1.0 boolean type specification – archived link ↩︎ January 2005 – Yaml v1.1 final draft Version 1.1 maintained the same implicit typing behavior as v1.0. However, the types listed in the spec – including boolean – while still not mandatory, were now strongly recommended 9 . – Bonus: single sign characters are no longer included and the canonical form is now y/n 10 . these tags represent types that are useful across a wide range of applications and it is strongly recommended they be used whenever appropriate to promote interoperability. source: Yaml v1.1 specification, tag repository ( archive ) ↩︎ Yaml v1.1 boolean type specification , ( archive ) ↩︎ July 2009 – Yaml Revision 1.2.0 Its goal was to make yaml compliant with json , going as far as allowing json to be a subset of yaml 11 . Implicit typing rules have been removed, including the boolean English word format. – Bonus: explicit typing rules are still present. On paper, the Norway problem shouldn’t exist anymore, at least not since this yaml revision. So why are we still seeing it in 2026? The primary objective of this revision is to bring Yaml into compliance with json as an official subset. source: Yaml revision v1.2.0 ↩︎ Yaml spec version history until v1.2.0 Yaml spec version Date Type of no : Value of no first pass specification May 2001 unspecified unspecified v1.0 January 2004 boolean false v1.1 January 2005 boolean false v1.2.0 July 2009 string "no" Table 1: Summary of yaml spec changes. Note that “Type of no ” and “Value of no ” labels refer to the literal without quotes. Yaml in practice To understand why the Norway problem persists, we need to examine the scope of work involved in implementing yaml spec changes. Some clues are present in earlier text already, we see that yaml supports implicit typing, explicit typing, and various presenting formats. Also, the time between different yaml spec version releases is measured in years. What hides between the lines is that yaml and its specification are very, hugely, extremely complex. Seriously, it’s hard to overstate this. Since v1.0 yaml ’s goal was to build upon xml 12 and a number of other technologies, as listed in the final draft 13 : Yaml integrates and builds upon concepts described by C, Java, Perl, Python, Ruby, rfc0822 ( mail ), rfc1866 ( html ), rfc2045 ( mime ), rfc2396 ( uri ), xml , sax and soap Yaml supports attachments, custom tags, references – the list goes on. There was even yaxml , an xml binding for yaml 14 . There are 9 ways of writing multiline strings – and some claim the number is actually 63 15 . Characters like ? , ! , !! in some cases have special meanings, with the latter allowing arbitrary code execution. Given this complexity, the Norway problem wasn’t the only language quirk in yaml v1.1. Revision v1.2 simplified boolean behavior and more (e.g. handling of null and numerical values), while other language features remained unchanged. How did libraries react to changes in such a complex specification? In fact yaml was originally intended to be a markup language and its name stood for “Yet Another Markup Language”. Six months after the first pass specification, in January 2002, it was renamed to “ Yaml Ain’t Markup Language”. ↩︎ Yaml v1.0 specification, prior art ↩︎ a subset of xml which has yaml ’s information model, but xml ’s syntax (…) a xslt Stylesheet is provided, along with the canonical invoice example in xml using this schema source: Yaxml , the (draft) xml Binding for yaml – archived link ↩︎ There are 5 6 NINE (or 63, depending how you count) different ways to write multi-line strings in yaml . (…) 2 block styles, each with 2 possible block chomping indicators (or none), and with 9 possible indentation indicators (or none), 1 plain style and 2 quoted styles: 2 x (2 + 1) x (9 + 1) + 1 + 2 = 63 source: Stack Overflow answer ( archived ) ↩︎ Yaml libraries As of January 2026 popular yaml libraries still haven’t moved from v1.1 to v1.2, and they still exhibit the Norway problem. Smaller alternative projects have appeared, but their usage hasn’t surpassed the existing v1.1 libraries. Some users have built their own alternative parsers, mixing v1.1 and v1.2 features, or focusing on a subset of yaml suited to their needs. Below are some examples. Py Yaml As mentioned before, Py Yaml is Python’s most popular yaml library and one of the most popular Python libraries overall. Py Yaml never added v1.2 support. There is an open issue from 2017 in Py Yaml ’s Github project about introducing support for v1.2 16 . There are at least two more related open issues, plus several closed ones. An unofficial library 17 exists that can be used on top of Py Yaml to provide partial v1.2 support (its documentation notes that not all v1.2 features are implemented). Another Python library, ruamel.yaml 18 , supports v1.2 by default. Py Yaml Github Issue #116 ↩︎ yamlcore PyPI project page ↩︎ ruamel.yaml PyPI project page ↩︎ Lib Yaml Lib Yaml is the long-standing C library for yaml , it is used widely as a dependency by other tools and bindings. Like Py Yaml , it’s an “official” implementation – in the sense that its canonical repository is hosted on Github and owned by the official ‘yaml’ Github account. Lib Yaml also never added v1.2 support. An open issue from 2016 in Lib Yaml ’s github project requests adding v1.2 support 19 . As mentioned earlier, Lib Yaml sits deep in dependency trees; changing its behavior is especially risky and slow. A less popular library, libfyaml 20 , supports v1.2 by default. Lib Yaml Github Issue #20 ↩︎ libfyaml Github project page ↩︎ Golang’s gopkg.in/yaml.v3 Currently unmaintained 21 , historically the most popular and still holds more Github stars then other Golang yaml libraries. It’s especially interesting because it declares support for a mix of v1.1 and 1.2 22 . The Golang’s most popular actively maintained library 23 defaults to v1.2 behavior. “This project is unmaintained” , source: gopkg.in/yaml.v3 Github project page ↩︎ “The yaml package supports most of yaml 1.2, but preserves some behavior from 1.1 for backwards compatibility.” , source: gopkg.in/yaml.v3 Github project page ↩︎ goccy/go-yaml Github project page ↩︎ Kyaml Kyaml is a yaml dialect built for the Kubernetes project, launched in June 2025. Its goal is to provide a safer and less ambiguous tool; it is also designed specifically for Kubernetes, trading generality for predictability. The announcement blog post references the Norway problem directly 24 . Yaml ’s significant whitespace requires careful attention to indentation and nesting, while its optional string-quoting can lead to unexpected type coercion (for example: “The Norway Bug”). source: Kubernetes v1.34 Sneak Peek ↩︎ Is the Norway problem solved? Yaml ’s ecosystem is not just libraries, it’s also the community of users. Including: strong and conflicting opinions about yaml in general and the Norway problem in particular. In some part this outcome could be expected; after all yaml is very popular, deceptively complex, and is used in different kinds of scenarios, from small personal config files to critical infrastructure setups. Many texts don’t distinguish between yaml spec versions at all 25 . Even when spec version numbers are used, they’re frequently mistyped. It’s not difficult to find documentation claiming that implicit boolean typing is a trait of yaml specification version 1.2 26 (the correct version is v1.1); mistakes get spotted 27 and eventually updated, but that takes more time and effort than making the original typo. On the other hand we see users who declare the Norway problem as solved because it doesn’t exist in the latest spec version, or because they haven’t experienced it themselves, or for other reasons 28 . To be fair, that language feature was removed over a decade ago, and it’s unexpected that popular libraries still support the older spec version. Technically, the issue is solved in the spec – but in practice, most widely adopted implementations still support implicit boolean typing, as we’ve seen. Finally, there are end users who are so unhappy with yaml that they prefer almost anything else 29 . We end up with countless use cases (hobby, pro, critical infrastructure, …), roles (spec author, library maintainer, end user debugging a failed deployment at 11pm, …), and just as many points of views. The yaml specification defines many strings that are automatically interpreted as boolean values, which often conflicts with developer expectations. When you write country: NO , the yaml parser interprets NO as the boolean false , not the string "NO" source: What is the Norway Bug? ↩︎ The most tragic aspect of this bug , however, is that it is intended behavior according to the yaml 1.2 specification. source: The Norway Problem – why Strict Yaml refuses to do implicit typing and so should you ↩︎ In this case a Github issue has been created: It was intended according to the yaml 1.1 specification, but in yaml 1.2, the only recognized booleans are true , True , TRUE , false , False , FALSE . source: strictyaml Github issue #186 ↩︎ I don’t want to link to individual messages on social platforms to err on the side of users’ privacy; I’ll paraphrase some of them below, for illustration purposes. Norway problem has been solved for 16 years. Using 1.1 at this point is just forehead palming foolishness. The Norway issue is a bit blown out of proportion. I have been using YAML for 5+ years and have never had it. We stopped having this problem over ten years ago. Just quote your strings. Another solution is to change the country name. ↩︎ Same as earlier, I’ll paraphrase a few messages below, meant for illustration. Stop using YAML YAML - just say Norway. You should stop even tolerating YAML, refuse on sight. YAML made sense before JSON became a thing. YAML made me look at XML wistfully. Why people persist with YAML in new projects is baffling to me. People from Norway couldn't sign up. Took us a while to figure out. ↩︎ What next? In yaml final draft v1.0, the document specified that, along with yes and no , + and - should also be parsed as booleans. This was removed v1.1. There was an idea to keep that functionality when plus or minus signs were preceded with a dot ( .+ and .- ), but it didn’t catch on. Despite its well known and lesser known quirks, yaml remains popular and widely used. At this scale small quirks cascade into unexpected issues. And changes – or fixes – are introduced at a glacial pace. Then again, yaml ’s charm has its place, as evidenced by its popularity. While spec change adoption is very slow, it is still ongoing. New projects will likely adopt newer libraries, where the Norway problem no longer exists. If there is a single takeaway from this article, it’s this: yaml ecosystem is fragmented; on the whole it is moving towards a slightly stricter version. Implicit boolean typing is getting removed, it’s no longer in the official specification and most new libraries adhere to that. As of January 2026 however, the older libraries are stuck on the older version of the spec, they are still more popular and updating or phasing them out may take a while. Frequently Asked Questions Why not just use json in place of yaml ? A common reply is “no comments” – because json doesn’t support comments 30 ; many other yaml features aren’t supported either. This makes json a simpler and stricter alternative. Wheter that’s a better fit for your project, that depends on the project. As always, personal preference plays a role too. Note: json has its own flavors, like jsonc 31 . It was a conscious decision; there is an explanation from Douglas Crockford, as well as a suggestion about using json for configuration files: I removed comments from json because I saw people were using them to hold parsing directives, a practice which would have destroyed interoperability. I know that the lack of comments makes some people sad, but it shouldn’t. Suppose you are using json to keep configuration files, which you would like to annotate. Go ahead and insert all the comments you like. Then pipe it through JSMin before handing it to your json parser. source: Google Plus post by Douglas Crockford – archived link ↩︎ Json with Comments – project’s homepage ↩︎ Is yaml a superset of json ? After writing this article, I’m still not entirely sure. Even though the goal of yaml revision v1.2.0 was to make that happen and revisions 1.2.0 and 1.2.1 claimed it explicitly 32 : Yaml can therefore be viewed as a natural superset of json , offering improved human readability and a more complete information model. That text has been removed from the latest yaml revision 1.2.2. A popular article 33 claims to prove that yaml is not a superset of json , but that article uses a v1.1 parser – and as we know v1.1 never claimed json compatibility. So that won’t help us. The actual reason might be that yaml requires maps to have unique keys 34 , while json only recommends it 35 . So perhaps most json (i.e. json where objects have unique keys) is a subset of yaml . Some ambiguity remains. See e.g.: Yaml Version 1.2 Revision 1.2.1 ↩︎ Json treats the value 1e2 a number, of course, because it’s not in quote marks. Yaml fails to parse it as a number so silently falls back to treating it as a string. source: YAML IS NOT A SUPERSET OF JSON ↩︎ The content of a mapping node is an unordered set of key/value node pairs, with the restriction that each of the keys is unique source: Yaml Version 1.2 Revision 1.2.2 ↩︎ The names within an object SHOULD be unique. source: The application/json Media Type for JavaScript Object Notation ( json ) ↩︎ What went wrong? This question is out of scope for this article – here the goal is to prioritize facts over “what if?”. If i had to answer, I’d say that nothing went wrong. When a complex technology with a stable ecosystem introduces a breaking change, sometimes the process can take ages. The main surprise here is how complicated yaml really is. Also, as we’ve seen, with yaml and related tools being free software, anyone could contribute to improving the v1.2 adoption rate – or move to a tool that suits them better, or even create one. What about toml , sexagesimal numbers, schemas, human genes, Ruby, or Perl? These topics are only loosely related to the Norway problem, and this text is already quite long. If you enjoyed reading it, leave positive feedback somewhere and a Part 2 might happen. In the meantime, visit my homepage 36 and check out my other projects – maybe you’ll find something else you’ll enjoy. LAB174 homepage ↩︎ Epilogue Implicit boolean typing has been removed, but explicit boolean typing still remains. If a uniform yaml 1.2 future actually arrives, you can still bring a little bit of nostalgia to your code by writing: title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse platforms : iPhone : !!bool yes iPad : !!bool yes # Note the explicit typing here and above. AppleWatch : !!bool no countries : - DE - FR - NO - PL - RO When parsed with yq , a tool that supports yaml revision 1.2 by default: yq eval -o=json project.yaml It returns: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } < Back to LAB174.com | 2026-01-13T08:48:04 |
https://forem.com/t/nintendoswitch/page/7 | Nintendoswitch Page 7 - 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 # nintendoswitch Follow Hide Portable Nintendo fun anywhere, anytime Create Post Older #nintendoswitch 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 IGN: Triangle Strategy - Official PS5 and Xbox Launch Trailer Gaming News Gaming News Gaming News Follow Aug 20 '25 IGN: Triangle Strategy - Official PS5 and Xbox Launch Trailer # playstation # xbox # nintendoswitch # steam Comments Add Comment 1 min read IGN: Shenmue 3 Gets an Enhanced Edition Coming to Switch, PS5, Xbox, PC - IGN Daily Fix Gaming News Gaming News Gaming News Follow Aug 20 '25 IGN: Shenmue 3 Gets an Enhanced Edition Coming to Switch, PS5, Xbox, PC - IGN Daily Fix # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read GameSpot: Kirby Air Riders - Full Nintendo Direct Gameplay Overview 8/19/2025 Gaming News Gaming News Gaming News Follow Aug 19 '25 GameSpot: Kirby Air Riders - Full Nintendo Direct Gameplay Overview 8/19/2025 # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Pokemon Legends: Z-A - Official 'Enjoy Pokemon Battles Like Never Before' Trailer Gaming News Gaming News Gaming News Follow Aug 18 '25 IGN: Pokemon Legends: Z-A - Official 'Enjoy Pokemon Battles Like Never Before' Trailer # nintendo # nintendoswitch # gaming Comments Add Comment 1 min read IGN: Guilty Gear Strive - Official Lucy Starter Guide Overview Trailer Gaming News Gaming News Gaming News Follow Aug 17 '25 IGN: Guilty Gear Strive - Official Lucy Starter Guide Overview Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Bad Cheese: Official Release Date Trailer Gaming News Gaming News Gaming News Follow Aug 16 '25 IGN: Bad Cheese: Official Release Date Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: OFF Review Gaming News Gaming News Gaming News Follow Aug 16 '25 IGN: OFF Review # pcgaming # nintendoswitch # indie # retrogaming Comments Add Comment 1 min read IGN: Call of Duty: Black Ops 7 Release Date Leaked - IGN Daily Fix Gaming News Gaming News Gaming News Follow Aug 15 '25 IGN: Call of Duty: Black Ops 7 Release Date Leaked - IGN Daily Fix # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Drag x Drive Review Gaming News Gaming News Gaming News Follow Aug 13 '25 IGN: Drag x Drive Review # nintendoswitch # pcgaming # indie Comments Add Comment 1 min read IGN: OFF - Official Launch Trailer Gaming News Gaming News Gaming News Follow Aug 15 '25 IGN: OFF - Official Launch Trailer # gaming # steam # nintendo # nintendoswitch Comments Add Comment 1 min read GameSpot: Pokemon Legends Z-A - The Biggest Pokemon Shake Up In Decades! Gaming News Gaming News Gaming News Follow Aug 15 '25 GameSpot: Pokemon Legends Z-A - The Biggest Pokemon Shake Up In Decades! # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Little Nightmares 3 - Official Recap Trailer Gaming News Gaming News Gaming News Follow Aug 16 '25 IGN: Little Nightmares 3 - Official Recap Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read GameSpot: Pokemon Legends Z-A Hands On - The Biggest Pokemon Shake Up In Decades! Gaming News Gaming News Gaming News Follow Aug 15 '25 GameSpot: Pokemon Legends Z-A Hands On - The Biggest Pokemon Shake Up In Decades! # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Story of Seasons: Grand Bazaar - Official Arata Trailer Gaming News Gaming News Gaming News Follow Aug 12 '25 IGN: Story of Seasons: Grand Bazaar - Official Arata Trailer # nintendoswitch # pcgaming # steam # gamedev Comments Add Comment 1 min read IGN: Story of Seasons: Grand Bazaar - Official Jules Trailer Gaming News Gaming News Gaming News Follow Aug 12 '25 IGN: Story of Seasons: Grand Bazaar - Official Jules Trailer # nintendoswitch # pcgaming # steam Comments Add Comment 1 min read IGN: Shinobi: Art of Vengeance - Official Desert Stage Introduction Trailer Gaming News Gaming News Gaming News Follow Aug 14 '25 IGN: Shinobi: Art of Vengeance - Official Desert Stage Introduction Trailer # gamedev # playstation # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Chicken Run: Eggstraction - Official Release Date Announcement Trailer Gaming News Gaming News Gaming News Follow Aug 14 '25 IGN: Chicken Run: Eggstraction - Official Release Date Announcement Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: NBA 2K26 - Official MyTEAM Trailer Gaming News Gaming News Gaming News Follow Aug 14 '25 IGN: NBA 2K26 - Official MyTEAM Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Dark Deity 2 - Official Nintendo Switch Release Date Announcement Trailer Gaming News Gaming News Gaming News Follow Aug 14 '25 IGN: Dark Deity 2 - Official Nintendo Switch Release Date Announcement Trailer # nintendoswitch # nintendo # pcgaming # gamedev Comments Add Comment 1 min read IGN: Daemon X Machina: Titanic Scion - Official The Neun Trailer Gaming News Gaming News Gaming News Follow Aug 14 '25 IGN: Daemon X Machina: Titanic Scion - Official The Neun Trailer # nintendoswitch # playstation # xbox # pcgaming Comments Add Comment 1 min read IGN: Cronos: The New Dawn - Official 'A-11 Extraction' Live Action Trailer Gaming News Gaming News Gaming News Follow Aug 13 '25 IGN: Cronos: The New Dawn - Official 'A-11 Extraction' Live Action Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Fast & Furious: Arcade Edition - Official Announcement Trailer Gaming News Gaming News Gaming News Follow Aug 13 '25 IGN: Fast & Furious: Arcade Edition - Official Announcement Trailer # nintendoswitch # playstation # xbox # gamedev Comments Add Comment 1 min read Gen Z Is Cutting Back On Video Game Purchases. Like, Really Cutting Back Gaming News Gaming News Gaming News Follow Aug 12 '25 Gen Z Is Cutting Back On Video Game Purchases. Like, Really Cutting Back # gaminghardware # nintendoswitch # sportsgames # gamedeals Comments Add Comment 1 min read IGN: One Piece Pirate Warriors 4 - Official Character Pass 3 Launch Trailer Gaming News Gaming News Gaming News Follow Aug 12 '25 IGN: One Piece Pirate Warriors 4 - Official Character Pass 3 Launch Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Towa and the Guardians of the Sacred Tree - Official Combat Overview Trailer Gaming News Gaming News Gaming News Follow Aug 12 '25 IGN: Towa and the Guardians of the Sacred Tree - Official Combat Overview Trailer # pcgaming # playstation # xbox # nintendoswitch 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 — 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:48:04 |
https://cursor.com/features#ecosystem | Features · Cursor Skip to content Cursor Features Enterprise Pricing Resources ↓ Changelog Blog Docs ↗ Community Learn ↗ Workshops Forum ↗ Careers Features Enterprise Pricing Resources → Sign in Download Features The best way to build software. Download for macOS ⤓ Try mobile agent → Agent Delegate coding tasks so you can focus on higher-level direction. This element contains an interactive demo for sighted users. It's a demonstration of Cursor's IDE showing AI-powered coding assistance features. The interface is displayed over a scenic painted landscape wallpaper, giving the demo an artistic backdrop. Cursor Get Cursor In Progress 4 Enterprise Order Management System Generating Analyze Tab vs Agent Usage Patterns Generating PyTorch MNIST Experiments Generating Fix PR Comments Fetching Issue Generating Ready for Review 2 Set up Cursor Rules for Dashboard + 37 - 0 · Set up Cursor Rules for Dashboard Bioinformatics Tools + 135 - 21 · Bioinformatics Tools Analyze Tab vs Agent Usage Patterns Help me understand how teams split their focus between the tab view and the agents panel across our workspaces. Agent GPT-5 Codebase understanding Cursor's codebase embedding model gives Agent deep understanding and recall. Where are these menu label colors defined? Top model access Choose freely between frontier models from OpenAI, Anthropic, Gemini, and xAI. Auto Suggested Composer 1 GPT-5 High Fast ✓ Claude Sonnet 4.5 Claude Opus 4.5 Gemini 3 Pro Grok Code Scoped changes Make targeted edits or run terminal commands with natural language. Interactive demo with multiple windows showing Cursor's AI-powered features. Get Cursor sequence_alignment.py test_alignment.py from typing import Tuple MATCH_SCORE = 2 MISMATCH_SCORE = -1 GAP_PENALTY = -2 def nw_align(s: str, t: str) -> int: """Basic Needleman-Wunsch global alignment.""" n, m = len(s), len(t) dp = [[0] * (m + 1) for _ in range(n + 1)] # Initialize gap penalties for i in range(1, n + 1): dp[i][0] = i * GAP_PENALTY for j in range(1, m + 1): dp[0][j] = j * GAP_PENALTY for i in range(1, n + 1): for j in range(1, m + 1): match = dp[i-1][j-1] + (MATCH_SCORE if s[i-1] == t[j-1] else MISMATCH_SCORE) delete = dp[i-1][j] + GAP_PENALTY insert = dp[i][j-1] + GAP_PENALTY dp[i][j] = max(match, delete, insert) return dp[n][m] Tab Our custom autocomplete model predicts your next actions. This element contains an interactive demo for sighted users. It's a demonstration of Cursor's IDE showing AI-powered coding assistance features. The interface is displayed over a scenic painted landscape wallpaper, giving the demo an artistic backdrop. Cursor Get Cursor Dashboard.tsx SupportChat.tsx "use client"; import React, { useState } from "react"; import Navigation from "./Navigation"; import SupportChat from "./SupportChat"; export default function Dashboard() { return ( <div className="flex h-[600px] border rounded-lg overflow-hidden"> <div className="w-64 border-r"> </div> <div className="w-80 border-l"> <SupportChat /> </div> </div> ); } Multi-line edits Get suggested edits across multiple lines. Interactive demo with multiple windows showing Cursor's AI-powered features. Get Cursor ChangeManagement.tsx const VERSION = "8.2.3" const RELEASE_TAG = "release-8.2.3" export function ChangeManagement() { const metadata = { version: VERSION, tag: RELEASE_TAG, } return ( <main className="change-management"> <header> <h1>What's New in Version {VERSION}</h1> </header> </main> ) } Smart rewrites Type naturally, Cursor will finish your thought. Interactive demo with multiple windows showing Cursor's AI-powered features. Get Cursor phoneNumberUtils.ts export function normalizeNANPDigits(input: string): string { const onlyDigits = input.replace(/D/g, ""); return onlyDigits.length === 11 && onlyDigits.startsWith("1") ? onlyDigits.slice(1) : onlyDigits; } export function formatUSPhone(input: string): string { // format (000) 000-0000 const digits = input.replace(/D/g, ""); const core = digits.length === 11 && digits.startsWith("1") ? digits.slice(1) : digits; if (core.length !== 10) return input.trim(); const area = core.slice(0, 3); const prefix = core.slice(3, 6); const line = core.slice(6); return "(" + area + ") " + prefix + "-" + line; } Tab, Tab, Tab Fly through edits at your cursor and across files. Interactive demo with multiple windows showing Cursor's AI-powered features. Get Cursor ChangeManagement.tsx const VERSION = "8.2.3" const RELEASE_TAG = "release-8.2.3" export function ChangeManagement() { const metadata = { version: VERSION, tag: RELEASE_TAG, } return ( <main className="change-management"> <header> <h1>What's New in Version {VERSION}</h1> </header> </main> ) } Tab to Changelog.tsx Across the entire development process Start tasks from Slack, issue tracker, mobile and more. Finish off in the IDE. Try agents on web and mobile ↗ This element contains an interactive demo for sighted users. It's a demonstration of Cursor integrated within Slack, showing AI-powered assistance inside team communication. The interface is displayed over a scenic painted landscape wallpaper, giving the demo an artistic backdrop. Slack #ask-cursor 8 members dylan small thing but would be really good to have anchor links on the website for releases 4 replies dylan wanna be able to go to cursor.com/changelog#1.0 to see 1.0 changelog eric checks out @cursor can you take a stab? Cursor APP I implemented direct linking for changelog entries and updated Node.js version constraints across the project to improve compatibility and maintainability. View PR Open in Cursor Open in Web dylan Nice @eric can you take a look? cursor.com/agents Agent GPT-5 ryos main In Progress 4 Enterprise Order Management System Generating Analyze Tab vs Agent Usage Patterns Generating PyTorch MNIST Experiments Generating Fix PR Comments Fetching Issue Generating Ready for Review 2 Bioinformatics Tools + 135 - 21 · Bioinformatics Tools Set up Cursor Rules for Dashboard + 37 - 0 · Set up Cursor Rules for Dashboard IDE Manual to agentic coding, in one familiar editor. Download → Interactive demo with multiple windows showing Cursor's AI-powered features. summary.py report.py test_usage.py import logging from typing import Dict import pandas as pd logger = logging.getLogger(__name__) def focus_share( events: pd.DataFrame, feature_col: str = "interaction_type", user_col: str = "user_id", ) -> pd.DataFrame: if events.empty: return pd.DataFrame( columns=[feature_col, "events", "unique_users", "share_of_events", "share_of_users"], ) missing = {feature_col, user_col} - set(events.columns) if missing: raise ValueError(f"Missing required columns: {sorted(missing)}") grouped = ( events.groupby(feature_col) .agg(events=(feature_col, "size"), unique_users=(user_col, "nunique")) .reset_index() ) total_events = grouped["events"].sum() total_users = grouped["unique_users"].sum() grouped["share_of_events"] = grouped["events"] / total_events if total_events else 0.0 grouped["share_of_users"] = grouped["unique_users"] / total_users if total_users else 0.0 return grouped.sort_values("events", ascending=False).reset_index(drop=True) def switch_summary( events: pd.DataFrame, feature_col: str = "interaction_type", user_col: str = "user_id", ts_col: str = "timestamp", ) -> Dict[str, float]: defaults = { "total_switches": 0, "agent_entry_rate": 0.0, "tab_return_rate": 0.0, "avg_seconds_between_switches": 0.0, } if events.empty: return defaults required = {feature_col, user_col, ts_col} missing = required - set(events.columns) if missing: raise ValueError(f"Missing required columns: {sorted(missing)}") df = events.copy() df[ts_col] = pd.to_datetime(df[ts_col], utc=True, errors="coerce") df = df.dropna(subset=[ts_col]).sort_values([user_col, ts_col]) if df.empty: return defaults df["prev_feature"] = df.groupby(user_col)[feature_col].shift(1) df["prev_timestamp"] = df.groupby(user_col)[ts_col].shift(1) switches = df[df["prev_feature"].notna() & (df[feature_col] != df["prev_feature"])] total = int(switches.shape[0]) if total == 0: return defaults agent_entries = switches[switches[feature_col] == "agent"] tab_returns = switches[(switches[feature_col] == "tab") & (switches["prev_feature"] != "tab")] durations = (switches[ts_col] - switches["prev_timestamp"]).dt.total_seconds() return { "total_switches": total, "agent_entry_rate": float(agent_entries.shape[0] / total), "tab_return_rate": float(tab_returns.shape[0] / total), "avg_seconds_between_switches": float(durations.mean()) if not durations.empty else 0.0, } def rolling_focus_share( events: pd.DataFrame, ts_col: str = "timestamp", feature_col: str = "interaction_type", freq: str = "1D", window: int = 7, ) -> pd.DataFrame: if events.empty: return pd.DataFrame() required = {ts_col, feature_col} missing = required - set(events.columns) if missing: raise ValueError(f"Missing required columns: {sorted(missing)}") df = events.copy() df[ts_col] = pd.to_datetime(df[ts_col], utc=True, errors="coerce") df = df.dropna(subset=[ts_col]) if df.empty: return pd.DataFrame() daily = ( df.groupby([pd.Grouper(key=ts_col, freq=freq), feature_col]) .size() .unstack(fill_value=0) .sort_index() ) if daily.empty: return pd.DataFrame() totals = daily.sum(axis=1).replace(0, pd.NA) shares = daily.div(totals, axis=0).fillna(0.0) return shares.rolling(window, min_periods=1).mean() CLI Run agents in any terminal or script. Learn more → Interactive demo with multiple windows showing Cursor's AI-powered features. Cursor Agent ~/Repos/cursor-usage-research Analyze Tab vs Agent Usage Patterns Help me understand how teams split their focus between the tab view and the agents panel across our workspaces. ⬢ T h o u g h t 7 s ⬢ R e v i e w e d w o r k s p a c e u s a g e e x p o r t s a n d h i s t o r i c a l e n g a g e m e n t n o t e s I'll build an analytics toolkit that highlights tab versus agent adoption and switching behavior: summary.py + 150 - 0 Next I'll normalize the interaction labels and add session tagging so product can filter specific cohorts: segmentation.py + 94 - 0 Time to stitch everything together with a report helper that combines the key metrics: report.py + 40 - 0 I'll add tests to lock in the behaviour using a representative sample from last week's export: test_usage.py + 90 All set! We now track focus share, switching rates, and rolling engagement so PMs can compare tab-first and agent-first workflows in seconds. → GPT-5.2 / for commands · @ for files Review with Bugbot Identify issues, fix in one click. Learn more → This element contains an interactive demo for sighted users. It's a demonstration of Cursor integrated within GitHub, showing AI-powered code review and debugging assistance. The interface is displayed over a scenic painted landscape wallpaper, giving the demo an artistic backdrop. GitHub Pull Request Get Bugbot Review cursor bot reviewed 1m ago src/vs/workbench/composer/browser/components/ComposerUnifiedDropdown.tsx 3292 - {selectedMode().keybinding} 3293 + {composerOpenModeToggleKeybinding} cursor bot 1m ago Bug: Function Returns Object Instead of String (Logic bug) The composerOpenModeToggleKeybinding is a function that needs to be called to get its value. Using it directly causes the keybinding display condition to always be truthy. Fix in Cursor Fix in Web Powerful, yet flexible Configure Cursor so you can do your best work. 1-click import Import extensions, themes, and keybindings directly from VS Code. MCP servers Connect external tools and data sources directly to Cursor. Rules & memories Customize how the models behave with reusable, scoped instructions. next.mdc --- Description: Rules for the dashboard application Globs: apps/dashboard/**/* --- # Dashboard Application Rules ## Instructions: Follow Next.js App Router best practices Use React Server Components by default Implement type-safe server actions Follow mobile-first responsive design with Tailwind CSS Use shadcn/ui components with Radix UI primitives Implement proper error boundaries and loading states Optimize for Core Web Vitals ## Component Structure: 1. Exports 2. Types/Interfaces 3. Server actions (if any) 4. Component logic 5. Helper functions 6. Static content ## Naming: Use kebab-case for directories PascalCase for components camelCase for functions and variables Use descriptive names with auxiliary verbs (isLoading, hasError) @file apps/dashboard/tsconfig.json @file apps/dashboard/.env Custom commands Use and manage reusable prompts within your team. Agent GPT-5 check-compiler-errors and / | check-compiler-errors code-review commit fix-merge-conflicts plan pr weekly-review Changelog CLI Jan 8, 2026 New CLI Features and Improved CLI Performance 2.3 Dec 22, 2025 Layout Customization and Stability Improvements Dec 18, 2025 Enterprise Insights, Billing Groups, Service Accounts, and Improved Security Controls 2.2 Dec 10, 2025 Debug Mode, Plan Mode Improvements, Multi-Agent Judging, and Pinned Chats See what's new in Cursor → Try Cursor now. Download for macOS ⤓ Try mobile agent → Product Features Enterprise Web Agents Bugbot CLI Pricing Resources Download Changelog Docs ↗ Learn ↗ Forum ↗ Status ↗ Company Careers Blog Community Workshops Students Brand Legal Terms of Service Privacy Policy Data Use Security Connect X ↗ LinkedIn ↗ YouTube ↗ © 2026 Cursor 🛡 SOC 2 Certified 🌐 English ↓ English ✓ 简体中文 日本語 繁體中文 Skip to content Cursor Features Enterprise Pricing Resources ↓ Changelog Blog Docs ↗ Community Learn ↗ Workshops Forum ↗ Careers Features Enterprise Pricing Resources → Sign in Download Features The best way to build software. Download for macOS ⤓ Try mobile agent → Agent Delegate coding tasks so you can focus on higher-level direction. This element contains an interactive demo for sighted users. It's a demonstration of Cursor's IDE showing AI-powered coding assistance features. The interface is displayed over a scenic painted landscape wallpaper, giving the demo an artistic backdrop. Cursor Get Cursor In Progress 4 Enterprise Order Management System Generating Analyze Tab vs Agent Usage Patterns Generating PyTorch MNIST Experiments Generating Fix PR Comments Fetching Issue Generating Ready for Review 2 Set up Cursor Rules for Dashboard + 37 - 0 · Set up Cursor Rules for Dashboard Bioinformatics Tools + 135 - 21 · Bioinformatics Tools Analyze Tab vs Agent Usage Patterns Help me understand how teams split their focus between the tab view and the agents panel across our workspaces. Agent GPT-5 Codebase understanding Cursor's codebase embedding model gives Agent deep understanding and recall. Where are these menu label colors defined? Top model access Choose freely between frontier models from OpenAI, Anthropic, Gemini, and xAI. Auto Suggested Composer 1 GPT-5 High Fast ✓ Claude Sonnet 4.5 Claude Opus 4.5 Gemini 3 Pro Grok Code Scoped changes Make targeted edits or run terminal commands with natural language. Interactive demo with multiple windows showing Cursor's AI-powered features. Get Cursor sequence_alignment.py test_alignment.py from typing import Tuple MATCH_SCORE = 2 MISMATCH_SCORE = -1 GAP_PENALTY = -2 def nw_align(s: str, t: str) -> int: """Basic Needleman-Wunsch global alignment.""" n, m = len(s), len(t) dp = [[0] * (m + 1) for _ in range(n + 1)] # Initialize gap penalties for i in range(1, n + 1): dp[i][0] = i * GAP_PENALTY for j in range(1, m + 1): dp[0][j] = j * GAP_PENALTY for i in range(1, n + 1): for j in range(1, m + 1): match = dp[i-1][j-1] + (MATCH_SCORE if s[i-1] == t[j-1] else MISMATCH_SCORE) delete = dp[i-1][j] + GAP_PENALTY insert = dp[i][j-1] + GAP_PENALTY dp[i][j] = max(match, delete, insert) return dp[n][m] Tab Our custom autocomplete model predicts your next actions. This element contains an interactive demo for sighted users. It's a demonstration of Cursor's IDE showing AI-powered coding assistance features. The interface is displayed over a scenic painted landscape wallpaper, giving the demo an artistic backdrop. Cursor Get Cursor Dashboard.tsx SupportChat.tsx "use client"; import React, { useState } from "react"; import Navigation from "./Navigation"; import SupportChat from "./SupportChat"; export default function Dashboard() { return ( <div className="flex h-[600px] border rounded-lg overflow-hidden"> <div className="w-64 border-r"> </div> <div className="w-80 border-l"> <SupportChat /> </div> </div> ); } Multi-line edits Get suggested edits across multiple lines. Interactive demo with multiple windows showing Cursor's AI-powered features. Get Cursor ChangeManagement.tsx const VERSION = "8.2.3" const RELEASE_TAG = "release-8.2.3" export function ChangeManagement() { const metadata = { version: VERSION, tag: RELEASE_TAG, } return ( <main className="change-management"> <header> <h1>What's New in Version {VERSION}</h1> </header> </main> ) } Smart rewrites Type naturally, Cursor will finish your thought. Interactive demo with multiple windows showing Cursor's AI-powered features. Get Cursor phoneNumberUtils.ts export function normalizeNANPDigits(input: string): string { const onlyDigits = input.replace(/D/g, ""); return onlyDigits.length === 11 && onlyDigits.startsWith("1") ? onlyDigits.slice(1) : onlyDigits; } export function formatUSPhone(input: string): string { // format (000) 000-0000 const digits = input.replace(/D/g, ""); const core = digits.length === 11 && digits.startsWith("1") ? digits.slice(1) : digits; if (core.length !== 10) return input.trim(); const area = core.slice(0, 3); const prefix = core.slice(3, 6); const line = core.slice(6); return "(" + area + ") " + prefix + "-" + line; } Tab, Tab, Tab Fly through edits at your cursor and across files. Interactive demo with multiple windows showing Cursor's AI-powered features. Get Cursor ChangeManagement.tsx const VERSION = "8.2.3" const RELEASE_TAG = "release-8.2.3" export function ChangeManagement() { const metadata = { version: VERSION, tag: RELEASE_TAG, } return ( <main className="change-management"> <header> <h1>What's New in Version {VERSION}</h1> </header> </main> ) } Tab to Changelog.tsx Across the entire development process Start tasks from Slack, issue tracker, mobile and more. Finish off in the IDE. Try agents on web and mobile ↗ This element contains an interactive demo for sighted users. It's a demonstration of Cursor integrated within Slack, showing AI-powered assistance inside team communication. The interface is displayed over a scenic painted landscape wallpaper, giving the demo an artistic backdrop. Slack #ask-cursor 8 members dylan small thing but would be really good to have anchor links on the website for releases 4 replies dylan wanna be able to go to cursor.com/changelog#1.0 to see 1.0 changelog eric checks out @cursor can you take a stab? Cursor APP I implemented direct linking for changelog entries and updated Node.js version constraints across the project to improve compatibility and maintainability. View PR Open in Cursor Open in Web dylan Nice @eric can you take a look? cursor.com/agents Agent GPT-5 ryos main In Progress 4 Enterprise Order Management System Generating Analyze Tab vs Agent Usage Patterns Generating PyTorch MNIST Experiments Generating Fix PR Comments Fetching Issue Generating Ready for Review 2 Bioinformatics Tools + 135 - 21 · Bioinformatics Tools Set up Cursor Rules for Dashboard + 37 - 0 · Set up Cursor Rules for Dashboard IDE Manual to agentic coding, in one familiar editor. Download → Interactive demo with multiple windows showing Cursor's AI-powered features. summary.py report.py test_usage.py import logging from typing import Dict import pandas as pd logger = logging.getLogger(__name__) def focus_share( events: pd.DataFrame, feature_col: str = "interaction_type", user_col: str = "user_id", ) -> pd.DataFrame: if events.empty: return pd.DataFrame( columns=[feature_col, "events", "unique_users", "share_of_events", "share_of_users"], ) missing = {feature_col, user_col} - set(events.columns) if missing: raise ValueError(f"Missing required columns: {sorted(missing)}") grouped = ( events.groupby(feature_col) .agg(events=(feature_col, "size"), unique_users=(user_col, "nunique")) .reset_index() ) total_events = grouped["events"].sum() total_users = grouped["unique_users"].sum() grouped["share_of_events"] = grouped["events"] / total_events if total_events else 0.0 grouped["share_of_users"] = grouped["unique_users"] / total_users if total_users else 0.0 return grouped.sort_values("events", ascending=False).reset_index(drop=True) def switch_summary( events: pd.DataFrame, feature_col: str = "interaction_type", user_col: str = "user_id", ts_col: str = "timestamp", ) -> Dict[str, float]: defaults = { "total_switches": 0, "agent_entry_rate": 0.0, "tab_return_rate": 0.0, "avg_seconds_between_switches": 0.0, } if events.empty: return defaults required = {feature_col, user_col, ts_col} missing = required - set(events.columns) if missing: raise ValueError(f"Missing required columns: {sorted(missing)}") df = events.copy() df[ts_col] = pd.to_datetime(df[ts_col], utc=True, errors="coerce") df = df.dropna(subset=[ts_col]).sort_values([user_col, ts_col]) if df.empty: return defaults df["prev_feature"] = df.groupby(user_col)[feature_col].shift(1) df["prev_timestamp"] = df.groupby(user_col)[ts_col].shift(1) switches = df[df["prev_feature"].notna() & (df[feature_col] != df["prev_feature"])] total = int(switches.shape[0]) if total == 0: return defaults agent_entries = switches[switches[feature_col] == "agent"] tab_returns = switches[(switches[feature_col] == "tab") & (switches["prev_feature"] != "tab")] durations = (switches[ts_col] - switches["prev_timestamp"]).dt.total_seconds() return { "total_switches": total, "agent_entry_rate": float(agent_entries.shape[0] / total), "tab_return_rate": float(tab_returns.shape[0] / total), "avg_seconds_between_switches": float(durations.mean()) if not durations.empty else 0.0, } def rolling_focus_share( events: pd.DataFrame, ts_col: str = "timestamp", feature_col: str = "interaction_type", freq: str = "1D", window: int = 7, ) -> pd.DataFrame: if events.empty: return pd.DataFrame() required = {ts_col, feature_col} missing = required - set(events.columns) if missing: raise ValueError(f"Missing required columns: {sorted(missing)}") df = events.copy() df[ts_col] = pd.to_datetime(df[ts_col], utc=True, errors="coerce") df = df.dropna(subset=[ts_col]) if df.empty: return pd.DataFrame() daily = ( df.groupby([pd.Grouper(key=ts_col, freq=freq), feature_col]) .size() .unstack(fill_value=0) .sort_index() ) if daily.empty: return pd.DataFrame() totals = daily.sum(axis=1).replace(0, pd.NA) shares = daily.div(totals, axis=0).fillna(0.0) return shares.rolling(window, min_periods=1).mean() CLI Run agents in any terminal or script. Learn more → Interactive demo with multiple windows showing Cursor's AI-powered features. Cursor Agent ~/Repos/cursor-usage-research Analyze Tab vs Agent Usage Patterns Help me understand how teams split their focus between the tab view and the agents panel across our workspaces. ⬢ T h o u g h t 7 s ⬢ R e v i e w e d w o r k s p a c e u s a g e e x p o r t s a n d h i s t o r i c a l e n g a g e m e n t n o t e s I'll build an analytics toolkit that highlights tab versus agent adoption and switching behavior: summary.py + 150 - 0 Next I'll normalize the interaction labels and add session tagging so product can filter specific cohorts: segmentation.py + 94 - 0 Time to stitch everything together with a report helper that combines the key metrics: report.py + 40 - 0 I'll add tests to lock in the behaviour using a representative sample from last week's export: test_usage.py + 90 All set! We now track focus share, switching rates, and rolling engagement so PMs can compare tab-first and agent-first workflows in seconds. → GPT-5.2 / for commands · @ for files Review with Bugbot Identify issues, fix in one click. Learn more → This element contains an interactive demo for sighted users. It's a demonstration of Cursor integrated within GitHub, showing AI-powered code review and debugging assistance. The interface is displayed over a scenic painted landscape wallpaper, giving the demo an artistic backdrop. GitHub Pull Request Get Bugbot Review cursor bot reviewed 1m ago src/vs/workbench/composer/browser/components/ComposerUnifiedDropdown.tsx 3292 - {selectedMode().keybinding} 3293 + {composerOpenModeToggleKeybinding} cursor bot 1m ago Bug: Function Returns Object Instead of String (Logic bug) The composerOpenModeToggleKeybinding is a function that needs to be called to get its value. Using it directly causes the keybinding display condition to always be truthy. Fix in Cursor Fix in Web Powerful, yet flexible Configure Cursor so you can do your best work. 1-click import Import extensions, themes, and keybindings directly from VS Code. MCP servers Connect external tools and data sources directly to Cursor. Rules & memories Customize how the models behave with reusable, scoped instructions. next.mdc --- Description: Rules for the dashboard application Globs: apps/dashboard/**/* --- # Dashboard Application Rules ## Instructions: Follow Next.js App Router best practices Use React Server Components by default Implement type-safe server actions Follow mobile-first responsive design with Tailwind CSS Use shadcn/ui components with Radix UI primitives Implement proper error boundaries and loading states Optimize for Core Web Vitals ## Component Structure: 1. Exports 2. Types/Interfaces 3. Server actions (if any) 4. Component logic 5. Helper functions 6. Static content ## Naming: Use kebab-case for directories PascalCase for components camelCase for functions and variables Use descriptive names with auxiliary verbs (isLoading, hasError) @file apps/dashboard/tsconfig.json @file apps/dashboard/.env Custom commands Use and manage reusable prompts within your team. Agent GPT-5 check-compiler-errors and / | check-compiler-errors code-review commit fix-merge-conflicts plan pr weekly-review Changelog CLI Jan 8, 2026 New CLI Features and Improved CLI Performance 2.3 Dec 22, 2025 Layout Customization and Stability Improvements Dec 18, 2025 Enterprise Insights, Billing Groups, Service Accounts, and Improved Security Controls 2.2 Dec 10, 2025 Debug Mode, Plan Mode Improvements, Multi-Agent Judging, and Pinned Chats See what's new in Cursor → Try Cursor now. Download for macOS ⤓ Try mobile agent → Product Features Enterprise Web Agents Bugbot CLI Pricing Resources Download Changelog Docs ↗ Learn ↗ Forum ↗ Status ↗ Company Careers Blog Community Workshops Students Brand Legal Terms of Service Privacy Policy Data Use Security Connect X ↗ LinkedIn ↗ YouTube ↗ © 2026 Cursor 🛡 SOC 2 Certified 🌐 English ↓ English ✓ 简体中文 日本語 繁體中文 | 2026-01-13T08:48:04 |
https://devblogs.microsoft.com/dotnet/package-validation/ | Package Validation - .NET Blog Skip to main content Microsoft Dev Blogs Dev Blogs Dev Blogs Home Developer Microsoft for Developers Visual Studio Visual Studio Code Develop from the cloud All things Azure Xcode DevOps Windows Developer ISE Developer Azure SDK Command Line Aspire Technology DirectX Semantic Kernel Languages C++ C# F# TypeScript PowerShell Team Python Java Java Blog in Chinese Go .NET All .NET posts .NET Aspire .NET MAUI AI ASP.NET Core Blazor Entity Framework NuGet Servicing .NET Blog in Chinese Platform Development #ifdef Windows Microsoft Foundry Azure Government Azure VM Runtime Team Bing Dev Center Microsoft Edge Dev Microsoft Azure Microsoft 365 Developer Microsoft Entra Identity Developer Old New Thing Power Platform Data Development Azure Cosmos DB Azure Data Studio Azure SQL OData Revolutions R Unified Data Model (IDEAs) Microsoft Entra PowerShell More Search Search No results Cancel Dev Blogs .NET Blog Package Validation .NET 10 is here! .NET 10 is now available: the most productive, modern, secure, intelligent, and performant release of .NET yet. Learn More Download Now June 22nd, 2021 1 reaction Package Validation Anirudh Agnihotry Show more In this blog post, I’m going to show the new package validation tooling that will become available with .NET 6. It ensures that your package consumers have a great experience across all .NET platforms and versions and that you didn’t accidentally make any breaking changes with the previous version of your package. If that is of interest to you, keep reading! Why validation is important With .NET Core & Xamarin we have made cross-platform a mainstream requirement for library authors. However, we lack validation tooling for cross targeting packages, which can result in packages that don’t work well, which in turn hurts our ecosystem. This is especially problematic for emerging platforms where adoption isn’t high enough to warrant special attention by library authors. The tooling we provide as part of the SDK has close to zero validation that multi-targeted packages are well-formed. For example, a package that multi-targets for .NET 6.0 and .NET Standard 2.0 needs to ensure that code compiled against the .NET Standard 2.0 binary can run against the .NET 6.0 binary. We have seen this issue in the wild, even with 1st parties, for example, the Azure AD libraries. It’s easy to think that a change is safe and compatible if source consuming that change continues to compile without changes. However, certain changes may work fine in C# but can cause problems at runtime if the consumer wasn’t recompiled, for example, adding a defaulted parameter or changing the value of a constant. Package Validation tooling will allow library developers to validate that their packages are consistent and well-formed. It involves validating that there are no breaking changes across versions. It will validate that the package have the same set of publics APIs for all the different runtime-specific implementations. It will also help developers to catch any applicability holes. How To Add Package Validation To Your Projects Package Validation is currently being shipped as an MSBuild SDK package which can be consumed by a project. It is a set of tasks and targets that run after generating the package when calling dotnet pack (or after dotnet build in case you set GeneratePackageOnBuild to true ). To reference it, you need to use the new <Sdk> syntax: <Project Sdk="Microsoft.NET.Sdk"> <Sdk Name="Microsoft.DotNet.PackageValidation" Version="1.0.0-preview.5.21302.8" /> <PropertyGroup> <TargetFrameworks>netstandard2.0;net6.0</TargetFrameworks> </PropertyGroup> </Project> In the next sections, I’ll walk you through a set of scenarios that show how you can validate your own packages. Validating Compatible Frameworks Packages containing compatible frameworks need to ensure that code compiled against one can run against another. Examples of compatible framework pairs are: .NET Standard 2.0 and .NET 6.0 .NET 5.0 and .NET 6.0 In both of these cases, your consumers can build against .NET Standard 2.0 or NET 5.0 and run on .NET 6.0. In case your binaries are not compatible between these frameworks, consumers could end up with compile and/or runtime errors. Package Validation will catch these errors at pack time. Here is an example scenario: Suppose you’re writing a game which does a lot of string manipulation. You need to support both .NET Framework and .NET Core consumers. You started with just targeting .NET Standard 2.0 but now you realize you want to take advantage of spans in .NET 6.0 to avoid unnecessary string allocations. In order to do that, you now want to multi-target for .NET Standard 2.0 and .NET 6.0. You have written the following code: #if NET6_0_OR_GREATER public void DoStringManipulation(ReadOnlySpan<char> input) { // use spans to do string operations. } #else public void DoStringManipulation(string input) { // Do some string operations. } #endif You then try to pack the project (using dotnet pack cmd or using VS) it fails with the following error: You understand that you shouldn’t exclude DoStringManipulation(string) but instead just provide an additional DoStringManipulation(ReadOnlySpan<char>) method for .NET 6.0 and changes the code accordingly: #if NET6_0_OR_GREATER public void DoStringManipulation(ReadOnlySpan<char> input) { // use spans to do string operations. } #endif public void DoStringManipulation(string input) { // Do some string operations. } You try to pack the project again. Validation Against Baseline Package Version Package Validation can also help you validate your library project against a previous released stable version of your package. In order to use this feature, you will need to add the PackageValidationBaselineVersion or PackageValidationBaselinePath to your project. Package validation will detect any breaking changes on any of the shipped target frameworks and will also detect if any target framework support has been dropped. For example consider the following scenario: you are working on the AdventureWorks.Client NuGet package. You want to make sure that you don’t accidentally make breaking changes so you configure your project to instruct package validation tooling to run API compatibility against the previous version of the package. <Project Sdk="Microsoft.NET.Sdk"> <Sdk Name="Microsoft.DotNet.PackageValidation" Version="1.0.0-preview.5.21302.8" /> <PropertyGroup> <TargetFramework>net6.0</TargetFramework> <PackageVersion>2.0.0</PackageVersion> <PackageValidationBaselineVersion>1.0.0</PackageValidationBaselineVersion> </PropertyGroup> </Project> A few weeks later, you are tasked with adding support for a connection timeout to your library. The Connect method currently looks like this: public static HttpClient Connect(string url) { // ... } Since a connection timeout is an advanced configuration setting, you reckon that you can just add an optional parameter: public static HttpClient Connect(string url, TimeSpan timeout = default) { // ... } However, when you try to pack, it throws an error. You realize that while this is not a source breaking change , it’s a binary breaking change . You solve this problem by adding an overload instead: public static HttpClient Connect(string url) { return Connect(url, Timeout.InfiniteTimeSpan); } public static HttpClient Connect(string url, TimeSpan timeout) { // ... } You try to pack the project again. Validation Against Different Runtimes You may choose to have different implementation assemblies for different runtimes in your nuget package. In that case, you will need to make sure that these assemblies are compatible with the compile-time assemblies. For example, consider the following scenario: you are working on a library involving some interop calls to Unix and Windows APIs respectively. You have written the following code: #if Unix public static void Open(string path, bool securityDescriptor) { // call unix specific stuff } #else public static void Open(string path) { // call windows specific stuff } #endif The resulting package structure looks like lib/net6.0/A.dll runtimes/unix/lib/net6.0/A.dll lib/net6.0/A.dll will always be used at compile time regardless of the underlying operating system. lib/net6.0/A.dll will also be used at runtime for non-Unix systems, but runtimes/unix/lib/net6.0/A.dll will be used at runtime for Unix systems. When you try to pack this project, you get an error: you quickly realize your mistake and add A.B.Open(string) to the unix runtime as well. #if Unix public static void Open(string path, bool securityDescriptor) { // call unix specific stuff } public static void Open(string path) { // throw not supported exception } #else public static void Open(string path) { // call windows specific stuff } #endif You try to pack the project again. Roadmap We will continue to add more and more capabilities with monthly updates until we’ll release a stable version later this year. Some of the features which are already in pipeline are error suppressions and nullability annotations compatibility rules. Share Your Feedback We are excited for this release, and look forward to your feedback. Let us know what you think of the product. Let us know what you think! . 1 6 0 Share on Facebook Share on X Share on Linkedin Copy Link --> Category .NET Share Author Anirudh Agnihotry 6 comments Discussion is closed. Login to edit/delete existing comments. Code of Conduct Sort by : Newest Newest Popular Oldest Rehan Saeed --> Rehan Saeed --> June 23, 2021 2 --> Collapse this comment --> Copy link --> --> --> --> Ideally, I don’t want to have to set the previous version in PackageValidationBaselineVersion . Could there be a way to tell the validator to lookup the latest version in NuGet? Anirudh Agnihotry --> Anirudh Agnihotry Author --> June 23, 2021 · Edited 0 --> Collapse this comment --> Copy link --> --> --> --> Currently there is no way for the tool to automatically calculate the PackageValidationBaselineVersion . We do not wanted to have any network calls before the restore phase, hence we decided to not calculate this automatically. However, we can think about adding it as an optional feature. Cédric Vernou --> Cédric Vernou --> June 23, 2021 0 --> Collapse this comment --> Copy link --> --> --> --> Amazing! Do this work with the classic .NET Framework target? Anirudh Agnihotry --> Anirudh Agnihotry Author --> June 23, 2021 0 --> Collapse this comment --> Copy link --> --> --> --> Yes it will work with the classic .NET Framework target frameworks. Christopher Mire --> Christopher Mire --> June 22, 2021 0 --> Collapse this comment --> Copy link --> --> --> --> Is this only .NET 6 SDK preview, or available in a stable SDK? Santiago Fernandez Madero --> Santiago Fernandez Madero --> June 22, 2021 · Edited 0 --> Collapse this comment --> Copy link --> --> --> --> Hello, Cristopher. Unfortunately, at the moment the tool targets .NET 6.0, so it can only be used with a .NET 6 SDK, however we are discussing building the tool for .NET 5 for the Preview 6 release so that more people that don’t have the .NET 6 SDK installed could try it out. Read next June 23, 2021 What’s new in Windows Forms in .NET 6.0 Preview 5 Igor Velikorossov June 24, 2021 .NET Framework June 2021 Cumulative Update Preview Tara Overfield Stay informed Get notified when new posts are published. Email * Country/Region * Select... United States Afghanistan Åland Islands Albania Algeria American Samoa Andorra Angola Anguilla Antarctica Antigua and Barbuda Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bermuda Bhutan Bolivia Bonaire Bosnia and Herzegovina Botswana Bouvet Island Brazil British Indian Ocean Territory British Virgin Islands Brunei Bulgaria Burkina Faso Burundi Cabo Verde Cambodia Cameroon Canada Cayman Islands Central African Republic Chad Chile China Christmas Island Cocos (Keeling) Islands Colombia Comoros Congo Congo (DRC) Cook Islands Costa Rica Côte dIvoire Croatia Curaçao Cyprus Czechia Denmark Djibouti Dominica Dominican Republic Ecuador Egypt El Salvador Equatorial Guinea Eritrea Estonia Eswatini Ethiopia Falkland Islands Faroe Islands Fiji Finland France French Guiana French Polynesia French Southern Territories Gabon Gambia Georgia Germany Ghana Gibraltar Greece Greenland Grenada Guadeloupe Guam Guatemala Guernsey Guinea Guinea-Bissau Guyana Haiti Heard Island and McDonald Islands Honduras Hong Kong SAR Hungary Iceland India Indonesia Iraq Ireland Isle of Man Israel Italy Jamaica Jan Mayen Japan Jersey Jordan Kazakhstan Kenya Kiribati Korea Kosovo Kuwait Kyrgyzstan Laos Latvia Lebanon Lesotho Liberia Libya Liechtenstein Lithuania Luxembourg Macau SAR Madagascar Malawi Malaysia Maldives Mali Malta Marshall Islands Martinique Mauritania Mauritius Mayotte Mexico Micronesia Moldova Monaco Mongolia Montenegro Montserrat Morocco Mozambique Myanmar Namibia Nauru Nepal Netherlands New Caledonia New Zealand Nicaragua Niger Nigeria Niue Norfolk Island North Macedonia Northern Mariana Islands Norway Oman Pakistan Palau Palestinian Authority Panama Papua New Guinea Paraguay Peru Philippines Pitcairn Islands Poland Portugal Puerto Rico Qatar Réunion Romania Rwanda Saba Saint Barthélemy Saint Kitts and Nevis Saint Lucia Saint Martin Saint Pierre and Miquelon Saint Vincent and the Grenadines Samoa San Marino São Tomé and Príncipe Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Sint Eustatius Sint Maarten Slovakia Slovenia Solomon Islands Somalia South Africa South Georgia and South Sandwich Islands South Sudan Spain Sri Lanka St Helena Ascension Tristan da Cunha Suriname Svalbard Sweden Switzerland Taiwan Tajikistan Tanzania Thailand Timor-Leste Togo Tokelau Tonga Trinidad and Tobago Tunisia Turkey Turkmenistan Turks and Caicos Islands Tuvalu U.S. Outlying Islands U.S. Virgin Islands Uganda Ukraine United Arab Emirates United Kingdom Uruguay Uzbekistan Vanuatu Vatican City Venezuela Vietnam Wallis and Futuna Yemen Zambia Zimbabwe I would like to receive the .NET Blog Newsletter. Privacy Statement. Subscribe Follow this blog Are you sure you wish to delete this comment? × --> OK Cancel Sign in Theme Insert/edit link Close Enter the destination URL URL Link Text Open link in a new tab Or link to existing content Search No search term specified. Showing recent items. Search or use up and down arrow keys to select an item. Cancel Code Block × Paste your code snippet Ok Cancel What's new Surface Pro Surface Laptop Surface Laptop Studio 2 Copilot for organizations Copilot for personal use AI in Windows Explore Microsoft products Windows 11 apps Microsoft Store Account profile Download Center Microsoft Store support Returns Order tracking Certified Refurbished Microsoft Store Promise Flexible Payments Education Microsoft in education Devices for education Microsoft Teams for Education Microsoft 365 Education How to buy for your school Educator training and development Deals for students and parents AI for education Business Microsoft Cloud Microsoft Security Dynamics 365 Microsoft 365 Microsoft Power Platform Microsoft Teams Microsoft 365 Copilot Small Business Developer & IT Azure Microsoft Developer Microsoft Learn Support for AI marketplace apps Microsoft Tech Community Microsoft Marketplace Marketplace Rewards Visual Studio Company Careers About Microsoft Company news Privacy at Microsoft Investors Diversity and inclusion Accessibility Sustainability Your Privacy Choices Opt-Out Icon Your Privacy Choices Your Privacy Choices Opt-Out Icon Your Privacy Choices Consumer Health Privacy Sitemap Contact Microsoft Privacy Manage cookies Terms of use Trademarks Safety & eco Recycling About our ads © Microsoft 2025 | 2026-01-13T08:48:04 |
https://forem.com/t/nintendoswitch/page/4 | Nintendoswitch Page 4 - 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 # nintendoswitch Follow Hide Portable Nintendo fun anywhere, anytime Create Post Older #nintendoswitch 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 IGN: Fire Emblem: Fortune's Weave - Reveal Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Fire Emblem: Fortune's Weave - Reveal Trailer | Nintendo Direct # nintendo # nintendoswitch # gaming Comments Add Comment 1 min read IGN: Fatal Frame 2: Crimson Butterfly Remake - Official Announcement Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Fatal Frame 2: Crimson Butterfly Remake - Official Announcement Trailer | Nintendo Direct # nintendo # nintendoswitch # gaming # retrogaming Comments Add Comment 1 min read IGN: Dynasty Warriors: Origins - Nintendo Switch 2 Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Dynasty Warriors: Origins - Nintendo Switch 2 Trailer | Nintendo Direct # nintendo # nintendoswitch # pcgaming Comments Add Comment 1 min read IGN: Storm Lancers - Official Nintendo Switch Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Storm Lancers - Official Nintendo Switch Trailer | Nintendo Direct # nintendo # nintendoswitch # gamedev # indie Comments Add Comment 1 min read IGN: Mario Tennis Fever - Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Mario Tennis Fever - Trailer | Nintendo Direct # nintendo # nintendoswitch # gaming Comments Add Comment 1 min read IGN: Super Mario Bros. Wonder - Nintendo Switch 2 Edition Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Super Mario Bros. Wonder - Nintendo Switch 2 Edition Trailer | Nintendo Direct # nintendo # nintendoswitch # gaming Comments Add Comment 1 min read IGN: Yoshi and the Mysterious Book - Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Yoshi and the Mysterious Book - Trailer | Nintendo Direct # nintendo # nintendoswitch # gaming Comments Add Comment 1 min read GameSpot: Yoshi And The Mysterious Book - Official Gameplay Reveal Trailer Gaming News Gaming News Gaming News Follow Sep 12 '25 GameSpot: Yoshi And The Mysterious Book - Official Gameplay Reveal Trailer # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Hyrule Warriors: Age of Imprisonment - Official Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Hyrule Warriors: Age of Imprisonment - Official Trailer | Nintendo Direct # nintendo # nintendoswitch # pcgaming Comments Add Comment 1 min read GameSpot: Hades II – v1.0 Launch Trailer (Coming Sep. 25!) Gaming News Gaming News Gaming News Follow Sep 12 '25 GameSpot: Hades II – v1.0 Launch Trailer (Coming Sep. 25!) # gamedev # pcgaming # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Garfield Kart 2: All You Can Drift - The First 11 Minutes of Gameplay Gaming News Gaming News Gaming News Follow Sep 11 '25 IGN: Garfield Kart 2: All You Can Drift - The First 11 Minutes of Gameplay # pcgaming # steam # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Hollow Knight: Silksong Boss Fight - Widow (Shellwood) Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Hollow Knight: Silksong Boss Fight - Widow (Shellwood) # pcgaming # indie # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Borderlands 4 - Official Cinematic Launch Trailer Gaming News Gaming News Gaming News Follow Sep 11 '25 IGN: Borderlands 4 - Official Cinematic Launch Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read GameSpot: Hollow Knight: Silksong 7 Things I Wish I Knew Gaming News Gaming News Gaming News Follow Sep 11 '25 GameSpot: Hollow Knight: Silksong 7 Things I Wish I Knew # pcgaming # indie # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Dead Reset - Official Launch Trailer Gaming News Gaming News Gaming News Follow Sep 11 '25 IGN: Dead Reset - Official Launch Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: The Coolest Things We Saw | PAX West 2025 Gaming News Gaming News Gaming News Follow Sep 10 '25 IGN: The Coolest Things We Saw | PAX West 2025 # pcgaming # nintendo # nintendoswitch # boardgames Comments Add Comment 1 min read IGN: Nintendo Direct Livestream: IGN Watch Party and NVC Post-Show Gaming News Gaming News Gaming News Follow Sep 10 '25 IGN: Nintendo Direct Livestream: IGN Watch Party and NVC Post-Show # discuss # nintendo # nintendoswitch # gaming Comments Add Comment 1 min read IGN: PlayStation 6 Rumors Claim It's a Dockable Handheld - IGN Daily Fix Gaming News Gaming News Gaming News Follow Aug 30 '25 IGN: PlayStation 6 Rumors Claim It's a Dockable Handheld - IGN Daily Fix # playstation # pcgaming # nintendoswitch # xbox Comments Add Comment 1 min read IGN: Sonic Racing: CrossWorlds - Official Cinematic Animation Trailer (Warning: Flashing Lights) Gaming News Gaming News Gaming News Follow Aug 30 '25 IGN: Sonic Racing: CrossWorlds - Official Cinematic Animation Trailer (Warning: Flashing Lights) # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Yooka-Replaylee - Official Release Date Trailer | The MIX Fall Game Showcase 2025 Gaming News Gaming News Gaming News Follow Aug 29 '25 IGN: Yooka-Replaylee - Official Release Date Trailer | The MIX Fall Game Showcase 2025 # nintendo # nintendoswitch # pcgaming # playstation Comments Add Comment 1 min read IGN: Top 13 Best 2D Mario Games Ranked Gaming News Gaming News Gaming News Follow Sep 13 '25 IGN: Top 13 Best 2D Mario Games Ranked # nintendo # retrogaming # nintendoswitch Comments 1 comment 1 min read IGN: Wolfhound - Official Gameplay Trailer | The MIX Fall Game Showcase 2025 Gaming News Gaming News Gaming News Follow Aug 29 '25 IGN: Wolfhound - Official Gameplay Trailer | The MIX Fall Game Showcase 2025 # pcgaming # nintendoswitch # playstation # gamedev Comments Add Comment 1 min read IGN: SHINOBI: Art of Vengeance - Official Accolades Trailer Gaming News Gaming News Gaming News Follow Aug 30 '25 IGN: SHINOBI: Art of Vengeance - Official Accolades Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Atelier Resleriana: The Red Alchemist & the White Guardian - Official Story Trailer Gaming News Gaming News Gaming News Follow Aug 29 '25 IGN: Atelier Resleriana: The Red Alchemist & the White Guardian - Official Story Trailer # pcgaming # playstation # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Karate Survivor - Official Console Launch Trailer Gaming News Gaming News Gaming News Follow Aug 29 '25 IGN: Karate Survivor - Official Console Launch Trailer # pcgaming # playstation # xbox # nintendoswitch Comments 1 comment 1 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV 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:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb4-8 | YAML? That’s Norway problem < Back to LAB174.com YAML? That’s Norway problem 2026-01-12 Abstract A deep dive into YAML’s Norway problem: why the country code NO gets parsed as false, its history from YAML v1.0 to v1.2, and why popular libraries still exhibit this behavior in 2026. What is yaml Yaml is a well-known data serialization language designed for human readability. It’s a popular choice for configuration files and metadata. Here’s a simple example: # project.yaml title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse countries : - DE - FR - PL - RO Let’s verify that the above example parses correctly. We’ll use Python 1 with Py Yaml 2 version 6.0.3 (the latest version as of this writing). First, let’s install it: python3 -m pip install pyyaml==6.0.3 Now let’s write a simple script to parse the yaml file: # python-pyyaml.py import json import yaml with open ( "project.yaml" , "r" , encoding = "utf-8" ) as f: data = yaml.safe_load(f) print (json.dumps(data, indent = 2 )) Running python3 python-pyyaml.py produces this output: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , "PL" , "RO" ] } So far everything behaves as expected. As of January 2026 Python is the world’s 4th most popular programming language according to a 2025 Stack Overflow Survey ( archive ) ↩︎ Py Yaml is Python’s most popular yaml library and a top 20 Python library overall in the last month according to PyPI Stats ( archive ). It is also an “official” yaml library in the sense that its source code is hosted in a Github repository owned by the yaml Github account; see: Canonical source repository for Py Yaml . ↩︎ The Norway problem in yaml When we change the original yaml file and add Norway’s two letter iso country code to the existing list: countries : - DE - FR - NO - PL - RO Using the same parsing method, the file now yields this result: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , false , "PL" , "RO" ] } Note that NO has been replaced with false . This is unexpected. Nothing about the context suggests a boolean should appear here. The NO literal sits in a list of country codes like FR or PL and appears similar in form. The problem, of course, is that “no” is also an English word with a negative meaning. This feature was originally added to allow writing booleans in a more human readable way, e.g.: platforms : iPhone : yes iPad : yes AppleWatch : no This gets parsed as: { "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false } } The idea was that configuration files should read like natural language. In practice this behavior proved problematic, becoming the notorious Norway problem in yaml . One workaround is to escape the string, like this: countries : - DE - FR - "NO" - PL - RO With quotes, the file parses as expected: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } Many articles about yaml ’s Norway problem stop here, presenting quoting as the canonical fix. There is more. Yaml ’s history To understand today’s state of the Norway problem we’ll first look at how yaml evolved. May 2001 – Yaml first pass specification At this time, yaml was more of a concept than a finished language. It looked a bit different, though somewhat recognizable. Below is a partial example from the original specification; there are more in the full document, sadly none with boolean values. buyer : % address : % city : Royal Oak line one : 458 Wittigen's Way line two : Suite 292 postal : 48046 state : MI family name : Dumars given name : Chris The document makes no mention of parsing no to false . The “Serilization Format / bnf ” section even contains a typo and a “to do” note 3 : This section contains the bnf 4 productions for the yaml syntax. Much to do… Full first pass specification – archived link ↩︎ Bnf stands for “Backus–Naur form”, a notation system for syntax definition ( Wikipedia ). ↩︎ January 2004 – Yaml v1.0 final draft This version describes various ways of presenting scalars 5 , including both quoted scalars and plain scalars with implicit typing. This is what we’re after. Version 1.0 defined only sequence , map , and string as mandatory types 6 . The rest were optional, but a reference specification existed. That reference specification for the optional boolean type included English word format. Supported words were: true/false , on/off , and also yes/no 7 . This allows the Norway problem to appear – even if following that part of reference is described as optional. – Bonus: implicit typing can be overridden with explicit tags – we’ll talk about this later. – Bonus: single sign characters, i.e. + and - should also be treated as true and false ; even more so, as they are described as the canonical form 8 ! A scalar data type, or just scalar, is any non-composite value. Generally, all basic primitive data types are considered scalar source: Wikipedia ↩︎ Following is a description of the three mandatory core tags. Yaml requires support for the seq, map and str tags. source: Yaml v1.0 specification, tag repository ↩︎ English word format: implicit english ~= true|True|TRUE |false|False|FALSE |yes|Yes|YES |no|No|NO |on|On|ON |off|Off|OFF source: Yaml v1.0 boolean type specification – archived link ↩︎ Single sign character format: implicit canonical ~= +|- source: Yaml v1.0 boolean type specification – archived link ↩︎ January 2005 – Yaml v1.1 final draft Version 1.1 maintained the same implicit typing behavior as v1.0. However, the types listed in the spec – including boolean – while still not mandatory, were now strongly recommended 9 . – Bonus: single sign characters are no longer included and the canonical form is now y/n 10 . these tags represent types that are useful across a wide range of applications and it is strongly recommended they be used whenever appropriate to promote interoperability. source: Yaml v1.1 specification, tag repository ( archive ) ↩︎ Yaml v1.1 boolean type specification , ( archive ) ↩︎ July 2009 – Yaml Revision 1.2.0 Its goal was to make yaml compliant with json , going as far as allowing json to be a subset of yaml 11 . Implicit typing rules have been removed, including the boolean English word format. – Bonus: explicit typing rules are still present. On paper, the Norway problem shouldn’t exist anymore, at least not since this yaml revision. So why are we still seeing it in 2026? The primary objective of this revision is to bring Yaml into compliance with json as an official subset. source: Yaml revision v1.2.0 ↩︎ Yaml spec version history until v1.2.0 Yaml spec version Date Type of no : Value of no first pass specification May 2001 unspecified unspecified v1.0 January 2004 boolean false v1.1 January 2005 boolean false v1.2.0 July 2009 string "no" Table 1: Summary of yaml spec changes. Note that “Type of no ” and “Value of no ” labels refer to the literal without quotes. Yaml in practice To understand why the Norway problem persists, we need to examine the scope of work involved in implementing yaml spec changes. Some clues are present in earlier text already, we see that yaml supports implicit typing, explicit typing, and various presenting formats. Also, the time between different yaml spec version releases is measured in years. What hides between the lines is that yaml and its specification are very, hugely, extremely complex. Seriously, it’s hard to overstate this. Since v1.0 yaml ’s goal was to build upon xml 12 and a number of other technologies, as listed in the final draft 13 : Yaml integrates and builds upon concepts described by C, Java, Perl, Python, Ruby, rfc0822 ( mail ), rfc1866 ( html ), rfc2045 ( mime ), rfc2396 ( uri ), xml , sax and soap Yaml supports attachments, custom tags, references – the list goes on. There was even yaxml , an xml binding for yaml 14 . There are 9 ways of writing multiline strings – and some claim the number is actually 63 15 . Characters like ? , ! , !! in some cases have special meanings, with the latter allowing arbitrary code execution. Given this complexity, the Norway problem wasn’t the only language quirk in yaml v1.1. Revision v1.2 simplified boolean behavior and more (e.g. handling of null and numerical values), while other language features remained unchanged. How did libraries react to changes in such a complex specification? In fact yaml was originally intended to be a markup language and its name stood for “Yet Another Markup Language”. Six months after the first pass specification, in January 2002, it was renamed to “ Yaml Ain’t Markup Language”. ↩︎ Yaml v1.0 specification, prior art ↩︎ a subset of xml which has yaml ’s information model, but xml ’s syntax (…) a xslt Stylesheet is provided, along with the canonical invoice example in xml using this schema source: Yaxml , the (draft) xml Binding for yaml – archived link ↩︎ There are 5 6 NINE (or 63, depending how you count) different ways to write multi-line strings in yaml . (…) 2 block styles, each with 2 possible block chomping indicators (or none), and with 9 possible indentation indicators (or none), 1 plain style and 2 quoted styles: 2 x (2 + 1) x (9 + 1) + 1 + 2 = 63 source: Stack Overflow answer ( archived ) ↩︎ Yaml libraries As of January 2026 popular yaml libraries still haven’t moved from v1.1 to v1.2, and they still exhibit the Norway problem. Smaller alternative projects have appeared, but their usage hasn’t surpassed the existing v1.1 libraries. Some users have built their own alternative parsers, mixing v1.1 and v1.2 features, or focusing on a subset of yaml suited to their needs. Below are some examples. Py Yaml As mentioned before, Py Yaml is Python’s most popular yaml library and one of the most popular Python libraries overall. Py Yaml never added v1.2 support. There is an open issue from 2017 in Py Yaml ’s Github project about introducing support for v1.2 16 . There are at least two more related open issues, plus several closed ones. An unofficial library 17 exists that can be used on top of Py Yaml to provide partial v1.2 support (its documentation notes that not all v1.2 features are implemented). Another Python library, ruamel.yaml 18 , supports v1.2 by default. Py Yaml Github Issue #116 ↩︎ yamlcore PyPI project page ↩︎ ruamel.yaml PyPI project page ↩︎ Lib Yaml Lib Yaml is the long-standing C library for yaml , it is used widely as a dependency by other tools and bindings. Like Py Yaml , it’s an “official” implementation – in the sense that its canonical repository is hosted on Github and owned by the official ‘yaml’ Github account. Lib Yaml also never added v1.2 support. An open issue from 2016 in Lib Yaml ’s github project requests adding v1.2 support 19 . As mentioned earlier, Lib Yaml sits deep in dependency trees; changing its behavior is especially risky and slow. A less popular library, libfyaml 20 , supports v1.2 by default. Lib Yaml Github Issue #20 ↩︎ libfyaml Github project page ↩︎ Golang’s gopkg.in/yaml.v3 Currently unmaintained 21 , historically the most popular and still holds more Github stars then other Golang yaml libraries. It’s especially interesting because it declares support for a mix of v1.1 and 1.2 22 . The Golang’s most popular actively maintained library 23 defaults to v1.2 behavior. “This project is unmaintained” , source: gopkg.in/yaml.v3 Github project page ↩︎ “The yaml package supports most of yaml 1.2, but preserves some behavior from 1.1 for backwards compatibility.” , source: gopkg.in/yaml.v3 Github project page ↩︎ goccy/go-yaml Github project page ↩︎ Kyaml Kyaml is a yaml dialect built for the Kubernetes project, launched in June 2025. Its goal is to provide a safer and less ambiguous tool; it is also designed specifically for Kubernetes, trading generality for predictability. The announcement blog post references the Norway problem directly 24 . Yaml ’s significant whitespace requires careful attention to indentation and nesting, while its optional string-quoting can lead to unexpected type coercion (for example: “The Norway Bug”). source: Kubernetes v1.34 Sneak Peek ↩︎ Is the Norway problem solved? Yaml ’s ecosystem is not just libraries, it’s also the community of users. Including: strong and conflicting opinions about yaml in general and the Norway problem in particular. In some part this outcome could be expected; after all yaml is very popular, deceptively complex, and is used in different kinds of scenarios, from small personal config files to critical infrastructure setups. Many texts don’t distinguish between yaml spec versions at all 25 . Even when spec version numbers are used, they’re frequently mistyped. It’s not difficult to find documentation claiming that implicit boolean typing is a trait of yaml specification version 1.2 26 (the correct version is v1.1); mistakes get spotted 27 and eventually updated, but that takes more time and effort than making the original typo. On the other hand we see users who declare the Norway problem as solved because it doesn’t exist in the latest spec version, or because they haven’t experienced it themselves, or for other reasons 28 . To be fair, that language feature was removed over a decade ago, and it’s unexpected that popular libraries still support the older spec version. Technically, the issue is solved in the spec – but in practice, most widely adopted implementations still support implicit boolean typing, as we’ve seen. Finally, there are end users who are so unhappy with yaml that they prefer almost anything else 29 . We end up with countless use cases (hobby, pro, critical infrastructure, …), roles (spec author, library maintainer, end user debugging a failed deployment at 11pm, …), and just as many points of views. The yaml specification defines many strings that are automatically interpreted as boolean values, which often conflicts with developer expectations. When you write country: NO , the yaml parser interprets NO as the boolean false , not the string "NO" source: What is the Norway Bug? ↩︎ The most tragic aspect of this bug , however, is that it is intended behavior according to the yaml 1.2 specification. source: The Norway Problem – why Strict Yaml refuses to do implicit typing and so should you ↩︎ In this case a Github issue has been created: It was intended according to the yaml 1.1 specification, but in yaml 1.2, the only recognized booleans are true , True , TRUE , false , False , FALSE . source: strictyaml Github issue #186 ↩︎ I don’t want to link to individual messages on social platforms to err on the side of users’ privacy; I’ll paraphrase some of them below, for illustration purposes. Norway problem has been solved for 16 years. Using 1.1 at this point is just forehead palming foolishness. The Norway issue is a bit blown out of proportion. I have been using YAML for 5+ years and have never had it. We stopped having this problem over ten years ago. Just quote your strings. Another solution is to change the country name. ↩︎ Same as earlier, I’ll paraphrase a few messages below, meant for illustration. Stop using YAML YAML - just say Norway. You should stop even tolerating YAML, refuse on sight. YAML made sense before JSON became a thing. YAML made me look at XML wistfully. Why people persist with YAML in new projects is baffling to me. People from Norway couldn't sign up. Took us a while to figure out. ↩︎ What next? In yaml final draft v1.0, the document specified that, along with yes and no , + and - should also be parsed as booleans. This was removed v1.1. There was an idea to keep that functionality when plus or minus signs were preceded with a dot ( .+ and .- ), but it didn’t catch on. Despite its well known and lesser known quirks, yaml remains popular and widely used. At this scale small quirks cascade into unexpected issues. And changes – or fixes – are introduced at a glacial pace. Then again, yaml ’s charm has its place, as evidenced by its popularity. While spec change adoption is very slow, it is still ongoing. New projects will likely adopt newer libraries, where the Norway problem no longer exists. If there is a single takeaway from this article, it’s this: yaml ecosystem is fragmented; on the whole it is moving towards a slightly stricter version. Implicit boolean typing is getting removed, it’s no longer in the official specification and most new libraries adhere to that. As of January 2026 however, the older libraries are stuck on the older version of the spec, they are still more popular and updating or phasing them out may take a while. Frequently Asked Questions Why not just use json in place of yaml ? A common reply is “no comments” – because json doesn’t support comments 30 ; many other yaml features aren’t supported either. This makes json a simpler and stricter alternative. Wheter that’s a better fit for your project, that depends on the project. As always, personal preference plays a role too. Note: json has its own flavors, like jsonc 31 . It was a conscious decision; there is an explanation from Douglas Crockford, as well as a suggestion about using json for configuration files: I removed comments from json because I saw people were using them to hold parsing directives, a practice which would have destroyed interoperability. I know that the lack of comments makes some people sad, but it shouldn’t. Suppose you are using json to keep configuration files, which you would like to annotate. Go ahead and insert all the comments you like. Then pipe it through JSMin before handing it to your json parser. source: Google Plus post by Douglas Crockford – archived link ↩︎ Json with Comments – project’s homepage ↩︎ Is yaml a superset of json ? After writing this article, I’m still not entirely sure. Even though the goal of yaml revision v1.2.0 was to make that happen and revisions 1.2.0 and 1.2.1 claimed it explicitly 32 : Yaml can therefore be viewed as a natural superset of json , offering improved human readability and a more complete information model. That text has been removed from the latest yaml revision 1.2.2. A popular article 33 claims to prove that yaml is not a superset of json , but that article uses a v1.1 parser – and as we know v1.1 never claimed json compatibility. So that won’t help us. The actual reason might be that yaml requires maps to have unique keys 34 , while json only recommends it 35 . So perhaps most json (i.e. json where objects have unique keys) is a subset of yaml . Some ambiguity remains. See e.g.: Yaml Version 1.2 Revision 1.2.1 ↩︎ Json treats the value 1e2 a number, of course, because it’s not in quote marks. Yaml fails to parse it as a number so silently falls back to treating it as a string. source: YAML IS NOT A SUPERSET OF JSON ↩︎ The content of a mapping node is an unordered set of key/value node pairs, with the restriction that each of the keys is unique source: Yaml Version 1.2 Revision 1.2.2 ↩︎ The names within an object SHOULD be unique. source: The application/json Media Type for JavaScript Object Notation ( json ) ↩︎ What went wrong? This question is out of scope for this article – here the goal is to prioritize facts over “what if?”. If i had to answer, I’d say that nothing went wrong. When a complex technology with a stable ecosystem introduces a breaking change, sometimes the process can take ages. The main surprise here is how complicated yaml really is. Also, as we’ve seen, with yaml and related tools being free software, anyone could contribute to improving the v1.2 adoption rate – or move to a tool that suits them better, or even create one. What about toml , sexagesimal numbers, schemas, human genes, Ruby, or Perl? These topics are only loosely related to the Norway problem, and this text is already quite long. If you enjoyed reading it, leave positive feedback somewhere and a Part 2 might happen. In the meantime, visit my homepage 36 and check out my other projects – maybe you’ll find something else you’ll enjoy. LAB174 homepage ↩︎ Epilogue Implicit boolean typing has been removed, but explicit boolean typing still remains. If a uniform yaml 1.2 future actually arrives, you can still bring a little bit of nostalgia to your code by writing: title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse platforms : iPhone : !!bool yes iPad : !!bool yes # Note the explicit typing here and above. AppleWatch : !!bool no countries : - DE - FR - NO - PL - RO When parsed with yq , a tool that supports yaml revision 1.2 by default: yq eval -o=json project.yaml It returns: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } < Back to LAB174.com | 2026-01-13T08:48:04 |
https://github.com/skills/copilot-codespaces-vscode | GitHub - skills/copilot-codespaces-vscode Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} This repository was archived by the owner on May 14, 2025. It is now read-only. skills / copilot-codespaces-vscode Public archive Notifications You must be signed in to change notification settings Fork 7.2k Star 1.8k License MIT license 1.8k stars 7.2k forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 5 Pull requests 2 Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Security Insights skills/copilot-codespaces-vscode main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 23 Commits .github .github .gitignore .gitignore LICENSE LICENSE README.md README.md View all files Repository files navigation README Code of conduct Contributing MIT license Security This course has been deprecated. Please visit the Getting Started with GitHub Copilot exercise for the newest learning content. About No description or website provided. Topics copilot Resources Readme License MIT license Code of conduct Code of conduct Contributing Contributing Security policy Security policy Uh oh! There was an error while loading. Please reload this page . Activity Custom properties Stars 1.8k stars Watchers 282 watching Forks 7.2k forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 11 Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:48:04 |
https://music.forem.com/contact | Contact Music 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 Music Forem Close Contacts Music Forem would love to hear from you! Email: support@dev.to 😁 Twitter: @thepracticaldev 👻 Report a vulnerability: dev.to/security 🐛 To report a bug, please create a bug report in our open source repository. To request a feature, please start a new GitHub Discussion in the Forem repo! 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Music Forem — From composing and gigging to gear, hot music takes, 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 . Music Forem © 2025 - 2026. We're a place dedicated to discussing all things music - composing, producing, performing, and all the fun and not-fun things in-between. Log in Create account | 2026-01-13T08:48:04 |
https://www.typescriptlang.org | TypeScript: JavaScript With Syntax For Types. Skip to main content TypeScript Download Docs Handbook Community Playground Tools in En TypeScript is JavaScript with syntax for types. TypeScript is a strongly typed programming language that builds on JavaScript, giving you better tooling at any scale. Try TypeScript Now Online or via npm Editor Checks Auto-complete Interfaces JSX ts const user = { firstName : "Angela" , lastName : "Davis" , role : "Professor" , } console . log ( user . name ) Property 'name' does not exist on type '{ firstName: string; lastName: string; role: string; }'. 2339 Property 'name' does not exist on type '{ firstName: string; lastName: string; role: string; }'. ts const user = { firstName : "Angela" , lastName : "Davis" , role : "Professor" , } console . log ( user . name ) Property 'name' does not exist on type '{ firstName: string; lastName: string; role: string; }'. 2339 Property 'name' does not exist on type '{ firstName: string; lastName: string; role: string; }'. TypeScript 5.9 is now available What is TypeScript? JavaScript and More TypeScript adds additional syntax to JavaScript to support a tighter integration with your editor . Catch errors early in your editor. A Result You Can Trust TypeScript code converts to JavaScript, which runs anywhere JavaScript runs : In a browser, on Node.js, Deno, Bun and in your apps. Safety at Scale TypeScript understands JavaScript and uses type inference to give you great tooling without additional code. Get Started Handbook Learn the language Playground Try in your browser Download Install TypeScript Adopt TypeScript Gradually Apply types to your JavaScript project incrementally, each step improves editor support and improves your codebase. Let's take this incorrect JavaScript code, and see how TypeScript can catch mistakes in your editor . js function compact ( arr ) { if ( orr . length > 10 ) return arr . trim ( 0 , 10 ) return arr } No editor warnings in JavaScript files This code crashes at runtime! JavaScript file js // @ts-check function compact ( arr ) { if ( orr . length > 10 ) Cannot find name 'orr'. 2304 Cannot find name 'orr'. return arr . trim ( 0 , 10 ) return arr } Adding this to a JS file shows errors in your editor the param is arr, not orr! JavaScript with TS Check js // @ts-check /** @param {any[]} arr */ function compact ( arr ) { if ( arr . .length: number' >length > 10 ) return arr . trim ( 0 , 10 ) Property 'trim' does not exist on type 'any[]'. 2339 Property 'trim' does not exist on type 'any[]'. return arr } Using JSDoc to give type information Now TS has found a bad call. Arrays have slice, not trim. JavaScript with JSDoc ts function compact ( arr : string []) { if ( arr . .length: number' >length > 10 ) return arr . .slice(start?: number | undefined, end?: number | undefined): string[]' >slice ( 0 , 10 ) return arr } TypeScript adds natural syntax for providing types TypeScript file Describe Your Data Describe the shape of objects and functions in your code. Making it possible to see documentation and issues in your editor . ts interface Account { id : number displayName : string version : 1 } function welcome ( user : Account ) { console . log ( user . id ) } ts type Result = "pass" | "fail" function verify ( result : Result ) { if ( result === "pass" ) { console . log ( "Passed" ) } else { console . log ( "Failed" ) } } TypeScript becomes JavaScript via the delete key. ts type Result = "pass" | "fail" function verify ( result : Result ) { if ( result === "pass" ) { console . log ( "Passed" ) } else { console . log ( "Failed" ) } } TypeScript file . ts type Result = "pass" | "fail" function verify ( result : Result ) { if ( result === "pass" ) { console . log ( "Passed" ) } else { console . log ( "Failed" ) } } Types are removed . js function verify ( result ) { if ( result === "pass" ) { console . log ( "Passed" ) } else { console . log ( "Failed" ) } } JavaScript file . TypeScript Testimonials First , we were surprised by the number of small bugs we found when converting our code. Second , we underestimated how powerful the editor integration is. TypeScript was such a boon to our stability and sanity that we started using it for all new code within days of starting the conversion. Felix Rieseberg at Slack covered the transition of their desktop app from JavaScript to TypeScript in their blog Read Open Source with TypeScript Angular Vue Jest Redux Ionic Probot Deno Vercel Yarn GitHub Desktop Loved by Developers Voted 2nd most loved programming language in the Stack Overflow 2020 Developer survey TypeScript was used by 78% of the 2020 State of JS respondents, with 93% saying they would use it again . TypeScript was given the award for “Most Adopted Technology” based on year-on-year growth. Get Started Handbook Learn the language Playground Try in your browser Download Install TypeScript Made with ♥ in Redmond, Boston, SF & Dublin © 2012- 2026 Microsoft Privacy Terms of Use Using TypeScript Get Started Download Community Playground TSConfig Ref Code Samples Why TypeScript Design Community Get Help Blog GitHub Repo Community Chat @TypeScript Mastodon Stack Overflow Web Repo MSG | 2026-01-13T08:48:04 |
https://github.com/skills/deploy-to-azure | GitHub - skills/deploy-to-azure: Create two deployment workflows using GitHub Actions and Microsoft Azure. Skip to content Navigation Menu Toggle navigation Sign in Appearance settings Platform AI CODE CREATION GitHub Copilot Write better code with AI GitHub Spark Build and deploy intelligent apps GitHub Models Manage and compare prompts MCP Registry New Integrate external tools DEVELOPER WORKFLOWS Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes APPLICATION SECURITY GitHub Advanced Security Find and fix vulnerabilities Code security Secure your code as you build Secret protection Stop leaks before they start EXPLORE Why GitHub Documentation Blog Changelog Marketplace View all features Solutions BY COMPANY SIZE Enterprises Small and medium teams Startups Nonprofits BY USE CASE App Modernization DevSecOps DevOps CI/CD View all use cases BY INDUSTRY Healthcare Financial services Manufacturing Government View all industries View all solutions Resources EXPLORE BY TOPIC AI Software Development DevOps Security View all topics EXPLORE BY TYPE Customer stories Events & webinars Ebooks & reports Business insights GitHub Skills SUPPORT & SERVICES Documentation Customer support Community forum Trust center Partners Open Source COMMUNITY GitHub Sponsors Fund open source developers PROGRAMS Security Lab Maintainer Community Accelerator Archive Program REPOSITORIES Topics Trending Collections Enterprise ENTERPRISE SOLUTIONS Enterprise platform AI-powered developer platform AVAILABLE ADD-ONS GitHub Advanced Security Enterprise-grade security features Copilot for Business Enterprise-grade AI features Premium Support Enterprise-grade 24/7 support Pricing Search or jump to... Search code, repositories, users, issues, pull requests... --> Search Clear Search syntax tips Provide feedback --> We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly --> Name Query To see all available qualifiers, see our documentation . Cancel Create saved search Sign in Sign up Appearance settings Resetting focus You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert {{ message }} skills / deploy-to-azure Public template Notifications You must be signed in to change notification settings Fork 114 Star 168 Create two deployment workflows using GitHub Actions and Microsoft Azure. License MIT license 168 stars 114 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 6 Pull requests 8 Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Actions Security Insights skills/deploy-to-azure main Branches Tags Go to file Code Open more actions menu Folders and files Name Name Last commit message Last commit date Latest commit History 93 Commits .github .github __test__ __test__ public public src src .gitignore .gitignore Dockerfile Dockerfile LICENSE LICENSE README.md README.md babel.config.js babel.config.js handler.js handler.js index.html index.html package-lock.json package-lock.json package.json package.json View all files Repository files navigation README Code of conduct Contributing MIT license Security Deploy to Azure Create two deployment workflows using GitHub Actions and Microsoft Azure. Welcome Create two deployment workflows using GitHub Actions and Microsoft Azure. Who is this for : Developers, DevOps Engineers, new GitHub users, students, and teams. What you'll learn : We'll learn how to create a workflow that enables Continuous Delivery using GitHub Actions and Microsoft Azure. What you'll build : We will create two deployment workflows - the first workflow to deploy to staging based on a label and the second workflow to deploy to production based on merging to main. Prerequisites : Before you start, you should be familiar with GitHub, GitHub Actions, and Continuous Integration with GitHub Actions. How long : This course takes less than 2 hours to complete. In this course, you will: Configure a job Set up an Azure environment Spin up the environment Deploy to staging Deploy to production Destroy the environment How to start this course Right-click Start course and open the link in a new tab. In the new tab, most of the prompts will automatically fill in for you. For owner, choose your personal account or an organization to host the repository. We recommend creating a public repository, as private repositories will use Actions minutes . Scroll down and click the Create repository button at the bottom of the form. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README. Get help: Post in our discussion board • Review the GitHub status page © 2023 GitHub • Code of Conduct • MIT License About Create two deployment workflows using GitHub Actions and Microsoft Azure. Topics skills-course Resources Readme License MIT license Code of conduct Code of conduct Contributing Contributing Security policy Security policy Uh oh! There was an error while loading. Please reload this page . Activity Custom properties Stars 168 stars Watchers 9 watching Forks 114 forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 18 + 4 contributors Languages JavaScript 78.4% HTML 15.3% CSS 5.9% Dockerfile 0.4% Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb5-2 | YAML? That’s Norway problem < Back to LAB174.com YAML? That’s Norway problem 2026-01-12 Abstract A deep dive into YAML’s Norway problem: why the country code NO gets parsed as false, its history from YAML v1.0 to v1.2, and why popular libraries still exhibit this behavior in 2026. What is yaml Yaml is a well-known data serialization language designed for human readability. It’s a popular choice for configuration files and metadata. Here’s a simple example: # project.yaml title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse countries : - DE - FR - PL - RO Let’s verify that the above example parses correctly. We’ll use Python 1 with Py Yaml 2 version 6.0.3 (the latest version as of this writing). First, let’s install it: python3 -m pip install pyyaml==6.0.3 Now let’s write a simple script to parse the yaml file: # python-pyyaml.py import json import yaml with open ( "project.yaml" , "r" , encoding = "utf-8" ) as f: data = yaml.safe_load(f) print (json.dumps(data, indent = 2 )) Running python3 python-pyyaml.py produces this output: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , "PL" , "RO" ] } So far everything behaves as expected. As of January 2026 Python is the world’s 4th most popular programming language according to a 2025 Stack Overflow Survey ( archive ) ↩︎ Py Yaml is Python’s most popular yaml library and a top 20 Python library overall in the last month according to PyPI Stats ( archive ). It is also an “official” yaml library in the sense that its source code is hosted in a Github repository owned by the yaml Github account; see: Canonical source repository for Py Yaml . ↩︎ The Norway problem in yaml When we change the original yaml file and add Norway’s two letter iso country code to the existing list: countries : - DE - FR - NO - PL - RO Using the same parsing method, the file now yields this result: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , false , "PL" , "RO" ] } Note that NO has been replaced with false . This is unexpected. Nothing about the context suggests a boolean should appear here. The NO literal sits in a list of country codes like FR or PL and appears similar in form. The problem, of course, is that “no” is also an English word with a negative meaning. This feature was originally added to allow writing booleans in a more human readable way, e.g.: platforms : iPhone : yes iPad : yes AppleWatch : no This gets parsed as: { "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false } } The idea was that configuration files should read like natural language. In practice this behavior proved problematic, becoming the notorious Norway problem in yaml . One workaround is to escape the string, like this: countries : - DE - FR - "NO" - PL - RO With quotes, the file parses as expected: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } Many articles about yaml ’s Norway problem stop here, presenting quoting as the canonical fix. There is more. Yaml ’s history To understand today’s state of the Norway problem we’ll first look at how yaml evolved. May 2001 – Yaml first pass specification At this time, yaml was more of a concept than a finished language. It looked a bit different, though somewhat recognizable. Below is a partial example from the original specification; there are more in the full document, sadly none with boolean values. buyer : % address : % city : Royal Oak line one : 458 Wittigen's Way line two : Suite 292 postal : 48046 state : MI family name : Dumars given name : Chris The document makes no mention of parsing no to false . The “Serilization Format / bnf ” section even contains a typo and a “to do” note 3 : This section contains the bnf 4 productions for the yaml syntax. Much to do… Full first pass specification – archived link ↩︎ Bnf stands for “Backus–Naur form”, a notation system for syntax definition ( Wikipedia ). ↩︎ January 2004 – Yaml v1.0 final draft This version describes various ways of presenting scalars 5 , including both quoted scalars and plain scalars with implicit typing. This is what we’re after. Version 1.0 defined only sequence , map , and string as mandatory types 6 . The rest were optional, but a reference specification existed. That reference specification for the optional boolean type included English word format. Supported words were: true/false , on/off , and also yes/no 7 . This allows the Norway problem to appear – even if following that part of reference is described as optional. – Bonus: implicit typing can be overridden with explicit tags – we’ll talk about this later. – Bonus: single sign characters, i.e. + and - should also be treated as true and false ; even more so, as they are described as the canonical form 8 ! A scalar data type, or just scalar, is any non-composite value. Generally, all basic primitive data types are considered scalar source: Wikipedia ↩︎ Following is a description of the three mandatory core tags. Yaml requires support for the seq, map and str tags. source: Yaml v1.0 specification, tag repository ↩︎ English word format: implicit english ~= true|True|TRUE |false|False|FALSE |yes|Yes|YES |no|No|NO |on|On|ON |off|Off|OFF source: Yaml v1.0 boolean type specification – archived link ↩︎ Single sign character format: implicit canonical ~= +|- source: Yaml v1.0 boolean type specification – archived link ↩︎ January 2005 – Yaml v1.1 final draft Version 1.1 maintained the same implicit typing behavior as v1.0. However, the types listed in the spec – including boolean – while still not mandatory, were now strongly recommended 9 . – Bonus: single sign characters are no longer included and the canonical form is now y/n 10 . these tags represent types that are useful across a wide range of applications and it is strongly recommended they be used whenever appropriate to promote interoperability. source: Yaml v1.1 specification, tag repository ( archive ) ↩︎ Yaml v1.1 boolean type specification , ( archive ) ↩︎ July 2009 – Yaml Revision 1.2.0 Its goal was to make yaml compliant with json , going as far as allowing json to be a subset of yaml 11 . Implicit typing rules have been removed, including the boolean English word format. – Bonus: explicit typing rules are still present. On paper, the Norway problem shouldn’t exist anymore, at least not since this yaml revision. So why are we still seeing it in 2026? The primary objective of this revision is to bring Yaml into compliance with json as an official subset. source: Yaml revision v1.2.0 ↩︎ Yaml spec version history until v1.2.0 Yaml spec version Date Type of no : Value of no first pass specification May 2001 unspecified unspecified v1.0 January 2004 boolean false v1.1 January 2005 boolean false v1.2.0 July 2009 string "no" Table 1: Summary of yaml spec changes. Note that “Type of no ” and “Value of no ” labels refer to the literal without quotes. Yaml in practice To understand why the Norway problem persists, we need to examine the scope of work involved in implementing yaml spec changes. Some clues are present in earlier text already, we see that yaml supports implicit typing, explicit typing, and various presenting formats. Also, the time between different yaml spec version releases is measured in years. What hides between the lines is that yaml and its specification are very, hugely, extremely complex. Seriously, it’s hard to overstate this. Since v1.0 yaml ’s goal was to build upon xml 12 and a number of other technologies, as listed in the final draft 13 : Yaml integrates and builds upon concepts described by C, Java, Perl, Python, Ruby, rfc0822 ( mail ), rfc1866 ( html ), rfc2045 ( mime ), rfc2396 ( uri ), xml , sax and soap Yaml supports attachments, custom tags, references – the list goes on. There was even yaxml , an xml binding for yaml 14 . There are 9 ways of writing multiline strings – and some claim the number is actually 63 15 . Characters like ? , ! , !! in some cases have special meanings, with the latter allowing arbitrary code execution. Given this complexity, the Norway problem wasn’t the only language quirk in yaml v1.1. Revision v1.2 simplified boolean behavior and more (e.g. handling of null and numerical values), while other language features remained unchanged. How did libraries react to changes in such a complex specification? In fact yaml was originally intended to be a markup language and its name stood for “Yet Another Markup Language”. Six months after the first pass specification, in January 2002, it was renamed to “ Yaml Ain’t Markup Language”. ↩︎ Yaml v1.0 specification, prior art ↩︎ a subset of xml which has yaml ’s information model, but xml ’s syntax (…) a xslt Stylesheet is provided, along with the canonical invoice example in xml using this schema source: Yaxml , the (draft) xml Binding for yaml – archived link ↩︎ There are 5 6 NINE (or 63, depending how you count) different ways to write multi-line strings in yaml . (…) 2 block styles, each with 2 possible block chomping indicators (or none), and with 9 possible indentation indicators (or none), 1 plain style and 2 quoted styles: 2 x (2 + 1) x (9 + 1) + 1 + 2 = 63 source: Stack Overflow answer ( archived ) ↩︎ Yaml libraries As of January 2026 popular yaml libraries still haven’t moved from v1.1 to v1.2, and they still exhibit the Norway problem. Smaller alternative projects have appeared, but their usage hasn’t surpassed the existing v1.1 libraries. Some users have built their own alternative parsers, mixing v1.1 and v1.2 features, or focusing on a subset of yaml suited to their needs. Below are some examples. Py Yaml As mentioned before, Py Yaml is Python’s most popular yaml library and one of the most popular Python libraries overall. Py Yaml never added v1.2 support. There is an open issue from 2017 in Py Yaml ’s Github project about introducing support for v1.2 16 . There are at least two more related open issues, plus several closed ones. An unofficial library 17 exists that can be used on top of Py Yaml to provide partial v1.2 support (its documentation notes that not all v1.2 features are implemented). Another Python library, ruamel.yaml 18 , supports v1.2 by default. Py Yaml Github Issue #116 ↩︎ yamlcore PyPI project page ↩︎ ruamel.yaml PyPI project page ↩︎ Lib Yaml Lib Yaml is the long-standing C library for yaml , it is used widely as a dependency by other tools and bindings. Like Py Yaml , it’s an “official” implementation – in the sense that its canonical repository is hosted on Github and owned by the official ‘yaml’ Github account. Lib Yaml also never added v1.2 support. An open issue from 2016 in Lib Yaml ’s github project requests adding v1.2 support 19 . As mentioned earlier, Lib Yaml sits deep in dependency trees; changing its behavior is especially risky and slow. A less popular library, libfyaml 20 , supports v1.2 by default. Lib Yaml Github Issue #20 ↩︎ libfyaml Github project page ↩︎ Golang’s gopkg.in/yaml.v3 Currently unmaintained 21 , historically the most popular and still holds more Github stars then other Golang yaml libraries. It’s especially interesting because it declares support for a mix of v1.1 and 1.2 22 . The Golang’s most popular actively maintained library 23 defaults to v1.2 behavior. “This project is unmaintained” , source: gopkg.in/yaml.v3 Github project page ↩︎ “The yaml package supports most of yaml 1.2, but preserves some behavior from 1.1 for backwards compatibility.” , source: gopkg.in/yaml.v3 Github project page ↩︎ goccy/go-yaml Github project page ↩︎ Kyaml Kyaml is a yaml dialect built for the Kubernetes project, launched in June 2025. Its goal is to provide a safer and less ambiguous tool; it is also designed specifically for Kubernetes, trading generality for predictability. The announcement blog post references the Norway problem directly 24 . Yaml ’s significant whitespace requires careful attention to indentation and nesting, while its optional string-quoting can lead to unexpected type coercion (for example: “The Norway Bug”). source: Kubernetes v1.34 Sneak Peek ↩︎ Is the Norway problem solved? Yaml ’s ecosystem is not just libraries, it’s also the community of users. Including: strong and conflicting opinions about yaml in general and the Norway problem in particular. In some part this outcome could be expected; after all yaml is very popular, deceptively complex, and is used in different kinds of scenarios, from small personal config files to critical infrastructure setups. Many texts don’t distinguish between yaml spec versions at all 25 . Even when spec version numbers are used, they’re frequently mistyped. It’s not difficult to find documentation claiming that implicit boolean typing is a trait of yaml specification version 1.2 26 (the correct version is v1.1); mistakes get spotted 27 and eventually updated, but that takes more time and effort than making the original typo. On the other hand we see users who declare the Norway problem as solved because it doesn’t exist in the latest spec version, or because they haven’t experienced it themselves, or for other reasons 28 . To be fair, that language feature was removed over a decade ago, and it’s unexpected that popular libraries still support the older spec version. Technically, the issue is solved in the spec – but in practice, most widely adopted implementations still support implicit boolean typing, as we’ve seen. Finally, there are end users who are so unhappy with yaml that they prefer almost anything else 29 . We end up with countless use cases (hobby, pro, critical infrastructure, …), roles (spec author, library maintainer, end user debugging a failed deployment at 11pm, …), and just as many points of views. The yaml specification defines many strings that are automatically interpreted as boolean values, which often conflicts with developer expectations. When you write country: NO , the yaml parser interprets NO as the boolean false , not the string "NO" source: What is the Norway Bug? ↩︎ The most tragic aspect of this bug , however, is that it is intended behavior according to the yaml 1.2 specification. source: The Norway Problem – why Strict Yaml refuses to do implicit typing and so should you ↩︎ In this case a Github issue has been created: It was intended according to the yaml 1.1 specification, but in yaml 1.2, the only recognized booleans are true , True , TRUE , false , False , FALSE . source: strictyaml Github issue #186 ↩︎ I don’t want to link to individual messages on social platforms to err on the side of users’ privacy; I’ll paraphrase some of them below, for illustration purposes. Norway problem has been solved for 16 years. Using 1.1 at this point is just forehead palming foolishness. The Norway issue is a bit blown out of proportion. I have been using YAML for 5+ years and have never had it. We stopped having this problem over ten years ago. Just quote your strings. Another solution is to change the country name. ↩︎ Same as earlier, I’ll paraphrase a few messages below, meant for illustration. Stop using YAML YAML - just say Norway. You should stop even tolerating YAML, refuse on sight. YAML made sense before JSON became a thing. YAML made me look at XML wistfully. Why people persist with YAML in new projects is baffling to me. People from Norway couldn't sign up. Took us a while to figure out. ↩︎ What next? In yaml final draft v1.0, the document specified that, along with yes and no , + and - should also be parsed as booleans. This was removed v1.1. There was an idea to keep that functionality when plus or minus signs were preceded with a dot ( .+ and .- ), but it didn’t catch on. Despite its well known and lesser known quirks, yaml remains popular and widely used. At this scale small quirks cascade into unexpected issues. And changes – or fixes – are introduced at a glacial pace. Then again, yaml ’s charm has its place, as evidenced by its popularity. While spec change adoption is very slow, it is still ongoing. New projects will likely adopt newer libraries, where the Norway problem no longer exists. If there is a single takeaway from this article, it’s this: yaml ecosystem is fragmented; on the whole it is moving towards a slightly stricter version. Implicit boolean typing is getting removed, it’s no longer in the official specification and most new libraries adhere to that. As of January 2026 however, the older libraries are stuck on the older version of the spec, they are still more popular and updating or phasing them out may take a while. Frequently Asked Questions Why not just use json in place of yaml ? A common reply is “no comments” – because json doesn’t support comments 30 ; many other yaml features aren’t supported either. This makes json a simpler and stricter alternative. Wheter that’s a better fit for your project, that depends on the project. As always, personal preference plays a role too. Note: json has its own flavors, like jsonc 31 . It was a conscious decision; there is an explanation from Douglas Crockford, as well as a suggestion about using json for configuration files: I removed comments from json because I saw people were using them to hold parsing directives, a practice which would have destroyed interoperability. I know that the lack of comments makes some people sad, but it shouldn’t. Suppose you are using json to keep configuration files, which you would like to annotate. Go ahead and insert all the comments you like. Then pipe it through JSMin before handing it to your json parser. source: Google Plus post by Douglas Crockford – archived link ↩︎ Json with Comments – project’s homepage ↩︎ Is yaml a superset of json ? After writing this article, I’m still not entirely sure. Even though the goal of yaml revision v1.2.0 was to make that happen and revisions 1.2.0 and 1.2.1 claimed it explicitly 32 : Yaml can therefore be viewed as a natural superset of json , offering improved human readability and a more complete information model. That text has been removed from the latest yaml revision 1.2.2. A popular article 33 claims to prove that yaml is not a superset of json , but that article uses a v1.1 parser – and as we know v1.1 never claimed json compatibility. So that won’t help us. The actual reason might be that yaml requires maps to have unique keys 34 , while json only recommends it 35 . So perhaps most json (i.e. json where objects have unique keys) is a subset of yaml . Some ambiguity remains. See e.g.: Yaml Version 1.2 Revision 1.2.1 ↩︎ Json treats the value 1e2 a number, of course, because it’s not in quote marks. Yaml fails to parse it as a number so silently falls back to treating it as a string. source: YAML IS NOT A SUPERSET OF JSON ↩︎ The content of a mapping node is an unordered set of key/value node pairs, with the restriction that each of the keys is unique source: Yaml Version 1.2 Revision 1.2.2 ↩︎ The names within an object SHOULD be unique. source: The application/json Media Type for JavaScript Object Notation ( json ) ↩︎ What went wrong? This question is out of scope for this article – here the goal is to prioritize facts over “what if?”. If i had to answer, I’d say that nothing went wrong. When a complex technology with a stable ecosystem introduces a breaking change, sometimes the process can take ages. The main surprise here is how complicated yaml really is. Also, as we’ve seen, with yaml and related tools being free software, anyone could contribute to improving the v1.2 adoption rate – or move to a tool that suits them better, or even create one. What about toml , sexagesimal numbers, schemas, human genes, Ruby, or Perl? These topics are only loosely related to the Norway problem, and this text is already quite long. If you enjoyed reading it, leave positive feedback somewhere and a Part 2 might happen. In the meantime, visit my homepage 36 and check out my other projects – maybe you’ll find something else you’ll enjoy. LAB174 homepage ↩︎ Epilogue Implicit boolean typing has been removed, but explicit boolean typing still remains. If a uniform yaml 1.2 future actually arrives, you can still bring a little bit of nostalgia to your code by writing: title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse platforms : iPhone : !!bool yes iPad : !!bool yes # Note the explicit typing here and above. AppleWatch : !!bool no countries : - DE - FR - NO - PL - RO When parsed with yq , a tool that supports yaml revision 1.2 by default: yq eval -o=json project.yaml It returns: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } < Back to LAB174.com | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb6-2 | YAML? That’s Norway problem < Back to LAB174.com YAML? That’s Norway problem 2026-01-12 Abstract A deep dive into YAML’s Norway problem: why the country code NO gets parsed as false, its history from YAML v1.0 to v1.2, and why popular libraries still exhibit this behavior in 2026. What is yaml Yaml is a well-known data serialization language designed for human readability. It’s a popular choice for configuration files and metadata. Here’s a simple example: # project.yaml title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse countries : - DE - FR - PL - RO Let’s verify that the above example parses correctly. We’ll use Python 1 with Py Yaml 2 version 6.0.3 (the latest version as of this writing). First, let’s install it: python3 -m pip install pyyaml==6.0.3 Now let’s write a simple script to parse the yaml file: # python-pyyaml.py import json import yaml with open ( "project.yaml" , "r" , encoding = "utf-8" ) as f: data = yaml.safe_load(f) print (json.dumps(data, indent = 2 )) Running python3 python-pyyaml.py produces this output: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , "PL" , "RO" ] } So far everything behaves as expected. As of January 2026 Python is the world’s 4th most popular programming language according to a 2025 Stack Overflow Survey ( archive ) ↩︎ Py Yaml is Python’s most popular yaml library and a top 20 Python library overall in the last month according to PyPI Stats ( archive ). It is also an “official” yaml library in the sense that its source code is hosted in a Github repository owned by the yaml Github account; see: Canonical source repository for Py Yaml . ↩︎ The Norway problem in yaml When we change the original yaml file and add Norway’s two letter iso country code to the existing list: countries : - DE - FR - NO - PL - RO Using the same parsing method, the file now yields this result: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "countries" : [ "DE" , "FR" , false , "PL" , "RO" ] } Note that NO has been replaced with false . This is unexpected. Nothing about the context suggests a boolean should appear here. The NO literal sits in a list of country codes like FR or PL and appears similar in form. The problem, of course, is that “no” is also an English word with a negative meaning. This feature was originally added to allow writing booleans in a more human readable way, e.g.: platforms : iPhone : yes iPad : yes AppleWatch : no This gets parsed as: { "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false } } The idea was that configuration files should read like natural language. In practice this behavior proved problematic, becoming the notorious Norway problem in yaml . One workaround is to escape the string, like this: countries : - DE - FR - "NO" - PL - RO With quotes, the file parses as expected: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } Many articles about yaml ’s Norway problem stop here, presenting quoting as the canonical fix. There is more. Yaml ’s history To understand today’s state of the Norway problem we’ll first look at how yaml evolved. May 2001 – Yaml first pass specification At this time, yaml was more of a concept than a finished language. It looked a bit different, though somewhat recognizable. Below is a partial example from the original specification; there are more in the full document, sadly none with boolean values. buyer : % address : % city : Royal Oak line one : 458 Wittigen's Way line two : Suite 292 postal : 48046 state : MI family name : Dumars given name : Chris The document makes no mention of parsing no to false . The “Serilization Format / bnf ” section even contains a typo and a “to do” note 3 : This section contains the bnf 4 productions for the yaml syntax. Much to do… Full first pass specification – archived link ↩︎ Bnf stands for “Backus–Naur form”, a notation system for syntax definition ( Wikipedia ). ↩︎ January 2004 – Yaml v1.0 final draft This version describes various ways of presenting scalars 5 , including both quoted scalars and plain scalars with implicit typing. This is what we’re after. Version 1.0 defined only sequence , map , and string as mandatory types 6 . The rest were optional, but a reference specification existed. That reference specification for the optional boolean type included English word format. Supported words were: true/false , on/off , and also yes/no 7 . This allows the Norway problem to appear – even if following that part of reference is described as optional. – Bonus: implicit typing can be overridden with explicit tags – we’ll talk about this later. – Bonus: single sign characters, i.e. + and - should also be treated as true and false ; even more so, as they are described as the canonical form 8 ! A scalar data type, or just scalar, is any non-composite value. Generally, all basic primitive data types are considered scalar source: Wikipedia ↩︎ Following is a description of the three mandatory core tags. Yaml requires support for the seq, map and str tags. source: Yaml v1.0 specification, tag repository ↩︎ English word format: implicit english ~= true|True|TRUE |false|False|FALSE |yes|Yes|YES |no|No|NO |on|On|ON |off|Off|OFF source: Yaml v1.0 boolean type specification – archived link ↩︎ Single sign character format: implicit canonical ~= +|- source: Yaml v1.0 boolean type specification – archived link ↩︎ January 2005 – Yaml v1.1 final draft Version 1.1 maintained the same implicit typing behavior as v1.0. However, the types listed in the spec – including boolean – while still not mandatory, were now strongly recommended 9 . – Bonus: single sign characters are no longer included and the canonical form is now y/n 10 . these tags represent types that are useful across a wide range of applications and it is strongly recommended they be used whenever appropriate to promote interoperability. source: Yaml v1.1 specification, tag repository ( archive ) ↩︎ Yaml v1.1 boolean type specification , ( archive ) ↩︎ July 2009 – Yaml Revision 1.2.0 Its goal was to make yaml compliant with json , going as far as allowing json to be a subset of yaml 11 . Implicit typing rules have been removed, including the boolean English word format. – Bonus: explicit typing rules are still present. On paper, the Norway problem shouldn’t exist anymore, at least not since this yaml revision. So why are we still seeing it in 2026? The primary objective of this revision is to bring Yaml into compliance with json as an official subset. source: Yaml revision v1.2.0 ↩︎ Yaml spec version history until v1.2.0 Yaml spec version Date Type of no : Value of no first pass specification May 2001 unspecified unspecified v1.0 January 2004 boolean false v1.1 January 2005 boolean false v1.2.0 July 2009 string "no" Table 1: Summary of yaml spec changes. Note that “Type of no ” and “Value of no ” labels refer to the literal without quotes. Yaml in practice To understand why the Norway problem persists, we need to examine the scope of work involved in implementing yaml spec changes. Some clues are present in earlier text already, we see that yaml supports implicit typing, explicit typing, and various presenting formats. Also, the time between different yaml spec version releases is measured in years. What hides between the lines is that yaml and its specification are very, hugely, extremely complex. Seriously, it’s hard to overstate this. Since v1.0 yaml ’s goal was to build upon xml 12 and a number of other technologies, as listed in the final draft 13 : Yaml integrates and builds upon concepts described by C, Java, Perl, Python, Ruby, rfc0822 ( mail ), rfc1866 ( html ), rfc2045 ( mime ), rfc2396 ( uri ), xml , sax and soap Yaml supports attachments, custom tags, references – the list goes on. There was even yaxml , an xml binding for yaml 14 . There are 9 ways of writing multiline strings – and some claim the number is actually 63 15 . Characters like ? , ! , !! in some cases have special meanings, with the latter allowing arbitrary code execution. Given this complexity, the Norway problem wasn’t the only language quirk in yaml v1.1. Revision v1.2 simplified boolean behavior and more (e.g. handling of null and numerical values), while other language features remained unchanged. How did libraries react to changes in such a complex specification? In fact yaml was originally intended to be a markup language and its name stood for “Yet Another Markup Language”. Six months after the first pass specification, in January 2002, it was renamed to “ Yaml Ain’t Markup Language”. ↩︎ Yaml v1.0 specification, prior art ↩︎ a subset of xml which has yaml ’s information model, but xml ’s syntax (…) a xslt Stylesheet is provided, along with the canonical invoice example in xml using this schema source: Yaxml , the (draft) xml Binding for yaml – archived link ↩︎ There are 5 6 NINE (or 63, depending how you count) different ways to write multi-line strings in yaml . (…) 2 block styles, each with 2 possible block chomping indicators (or none), and with 9 possible indentation indicators (or none), 1 plain style and 2 quoted styles: 2 x (2 + 1) x (9 + 1) + 1 + 2 = 63 source: Stack Overflow answer ( archived ) ↩︎ Yaml libraries As of January 2026 popular yaml libraries still haven’t moved from v1.1 to v1.2, and they still exhibit the Norway problem. Smaller alternative projects have appeared, but their usage hasn’t surpassed the existing v1.1 libraries. Some users have built their own alternative parsers, mixing v1.1 and v1.2 features, or focusing on a subset of yaml suited to their needs. Below are some examples. Py Yaml As mentioned before, Py Yaml is Python’s most popular yaml library and one of the most popular Python libraries overall. Py Yaml never added v1.2 support. There is an open issue from 2017 in Py Yaml ’s Github project about introducing support for v1.2 16 . There are at least two more related open issues, plus several closed ones. An unofficial library 17 exists that can be used on top of Py Yaml to provide partial v1.2 support (its documentation notes that not all v1.2 features are implemented). Another Python library, ruamel.yaml 18 , supports v1.2 by default. Py Yaml Github Issue #116 ↩︎ yamlcore PyPI project page ↩︎ ruamel.yaml PyPI project page ↩︎ Lib Yaml Lib Yaml is the long-standing C library for yaml , it is used widely as a dependency by other tools and bindings. Like Py Yaml , it’s an “official” implementation – in the sense that its canonical repository is hosted on Github and owned by the official ‘yaml’ Github account. Lib Yaml also never added v1.2 support. An open issue from 2016 in Lib Yaml ’s github project requests adding v1.2 support 19 . As mentioned earlier, Lib Yaml sits deep in dependency trees; changing its behavior is especially risky and slow. A less popular library, libfyaml 20 , supports v1.2 by default. Lib Yaml Github Issue #20 ↩︎ libfyaml Github project page ↩︎ Golang’s gopkg.in/yaml.v3 Currently unmaintained 21 , historically the most popular and still holds more Github stars then other Golang yaml libraries. It’s especially interesting because it declares support for a mix of v1.1 and 1.2 22 . The Golang’s most popular actively maintained library 23 defaults to v1.2 behavior. “This project is unmaintained” , source: gopkg.in/yaml.v3 Github project page ↩︎ “The yaml package supports most of yaml 1.2, but preserves some behavior from 1.1 for backwards compatibility.” , source: gopkg.in/yaml.v3 Github project page ↩︎ goccy/go-yaml Github project page ↩︎ Kyaml Kyaml is a yaml dialect built for the Kubernetes project, launched in June 2025. Its goal is to provide a safer and less ambiguous tool; it is also designed specifically for Kubernetes, trading generality for predictability. The announcement blog post references the Norway problem directly 24 . Yaml ’s significant whitespace requires careful attention to indentation and nesting, while its optional string-quoting can lead to unexpected type coercion (for example: “The Norway Bug”). source: Kubernetes v1.34 Sneak Peek ↩︎ Is the Norway problem solved? Yaml ’s ecosystem is not just libraries, it’s also the community of users. Including: strong and conflicting opinions about yaml in general and the Norway problem in particular. In some part this outcome could be expected; after all yaml is very popular, deceptively complex, and is used in different kinds of scenarios, from small personal config files to critical infrastructure setups. Many texts don’t distinguish between yaml spec versions at all 25 . Even when spec version numbers are used, they’re frequently mistyped. It’s not difficult to find documentation claiming that implicit boolean typing is a trait of yaml specification version 1.2 26 (the correct version is v1.1); mistakes get spotted 27 and eventually updated, but that takes more time and effort than making the original typo. On the other hand we see users who declare the Norway problem as solved because it doesn’t exist in the latest spec version, or because they haven’t experienced it themselves, or for other reasons 28 . To be fair, that language feature was removed over a decade ago, and it’s unexpected that popular libraries still support the older spec version. Technically, the issue is solved in the spec – but in practice, most widely adopted implementations still support implicit boolean typing, as we’ve seen. Finally, there are end users who are so unhappy with yaml that they prefer almost anything else 29 . We end up with countless use cases (hobby, pro, critical infrastructure, …), roles (spec author, library maintainer, end user debugging a failed deployment at 11pm, …), and just as many points of views. The yaml specification defines many strings that are automatically interpreted as boolean values, which often conflicts with developer expectations. When you write country: NO , the yaml parser interprets NO as the boolean false , not the string "NO" source: What is the Norway Bug? ↩︎ The most tragic aspect of this bug , however, is that it is intended behavior according to the yaml 1.2 specification. source: The Norway Problem – why Strict Yaml refuses to do implicit typing and so should you ↩︎ In this case a Github issue has been created: It was intended according to the yaml 1.1 specification, but in yaml 1.2, the only recognized booleans are true , True , TRUE , false , False , FALSE . source: strictyaml Github issue #186 ↩︎ I don’t want to link to individual messages on social platforms to err on the side of users’ privacy; I’ll paraphrase some of them below, for illustration purposes. Norway problem has been solved for 16 years. Using 1.1 at this point is just forehead palming foolishness. The Norway issue is a bit blown out of proportion. I have been using YAML for 5+ years and have never had it. We stopped having this problem over ten years ago. Just quote your strings. Another solution is to change the country name. ↩︎ Same as earlier, I’ll paraphrase a few messages below, meant for illustration. Stop using YAML YAML - just say Norway. You should stop even tolerating YAML, refuse on sight. YAML made sense before JSON became a thing. YAML made me look at XML wistfully. Why people persist with YAML in new projects is baffling to me. People from Norway couldn't sign up. Took us a while to figure out. ↩︎ What next? In yaml final draft v1.0, the document specified that, along with yes and no , + and - should also be parsed as booleans. This was removed v1.1. There was an idea to keep that functionality when plus or minus signs were preceded with a dot ( .+ and .- ), but it didn’t catch on. Despite its well known and lesser known quirks, yaml remains popular and widely used. At this scale small quirks cascade into unexpected issues. And changes – or fixes – are introduced at a glacial pace. Then again, yaml ’s charm has its place, as evidenced by its popularity. While spec change adoption is very slow, it is still ongoing. New projects will likely adopt newer libraries, where the Norway problem no longer exists. If there is a single takeaway from this article, it’s this: yaml ecosystem is fragmented; on the whole it is moving towards a slightly stricter version. Implicit boolean typing is getting removed, it’s no longer in the official specification and most new libraries adhere to that. As of January 2026 however, the older libraries are stuck on the older version of the spec, they are still more popular and updating or phasing them out may take a while. Frequently Asked Questions Why not just use json in place of yaml ? A common reply is “no comments” – because json doesn’t support comments 30 ; many other yaml features aren’t supported either. This makes json a simpler and stricter alternative. Wheter that’s a better fit for your project, that depends on the project. As always, personal preference plays a role too. Note: json has its own flavors, like jsonc 31 . It was a conscious decision; there is an explanation from Douglas Crockford, as well as a suggestion about using json for configuration files: I removed comments from json because I saw people were using them to hold parsing directives, a practice which would have destroyed interoperability. I know that the lack of comments makes some people sad, but it shouldn’t. Suppose you are using json to keep configuration files, which you would like to annotate. Go ahead and insert all the comments you like. Then pipe it through JSMin before handing it to your json parser. source: Google Plus post by Douglas Crockford – archived link ↩︎ Json with Comments – project’s homepage ↩︎ Is yaml a superset of json ? After writing this article, I’m still not entirely sure. Even though the goal of yaml revision v1.2.0 was to make that happen and revisions 1.2.0 and 1.2.1 claimed it explicitly 32 : Yaml can therefore be viewed as a natural superset of json , offering improved human readability and a more complete information model. That text has been removed from the latest yaml revision 1.2.2. A popular article 33 claims to prove that yaml is not a superset of json , but that article uses a v1.1 parser – and as we know v1.1 never claimed json compatibility. So that won’t help us. The actual reason might be that yaml requires maps to have unique keys 34 , while json only recommends it 35 . So perhaps most json (i.e. json where objects have unique keys) is a subset of yaml . Some ambiguity remains. See e.g.: Yaml Version 1.2 Revision 1.2.1 ↩︎ Json treats the value 1e2 a number, of course, because it’s not in quote marks. Yaml fails to parse it as a number so silently falls back to treating it as a string. source: YAML IS NOT A SUPERSET OF JSON ↩︎ The content of a mapping node is an unordered set of key/value node pairs, with the restriction that each of the keys is unique source: Yaml Version 1.2 Revision 1.2.2 ↩︎ The names within an object SHOULD be unique. source: The application/json Media Type for JavaScript Object Notation ( json ) ↩︎ What went wrong? This question is out of scope for this article – here the goal is to prioritize facts over “what if?”. If i had to answer, I’d say that nothing went wrong. When a complex technology with a stable ecosystem introduces a breaking change, sometimes the process can take ages. The main surprise here is how complicated yaml really is. Also, as we’ve seen, with yaml and related tools being free software, anyone could contribute to improving the v1.2 adoption rate – or move to a tool that suits them better, or even create one. What about toml , sexagesimal numbers, schemas, human genes, Ruby, or Perl? These topics are only loosely related to the Norway problem, and this text is already quite long. If you enjoyed reading it, leave positive feedback somewhere and a Part 2 might happen. In the meantime, visit my homepage 36 and check out my other projects – maybe you’ll find something else you’ll enjoy. LAB174 homepage ↩︎ Epilogue Implicit boolean typing has been removed, but explicit boolean typing still remains. If a uniform yaml 1.2 future actually arrives, you can still bring a little bit of nostalgia to your code by writing: title : Nonoverse description : Beautiful puzzle game about nonograms. link : https://lab174.com/nonoverse platforms : iPhone : !!bool yes iPad : !!bool yes # Note the explicit typing here and above. AppleWatch : !!bool no countries : - DE - FR - NO - PL - RO When parsed with yq , a tool that supports yaml revision 1.2 by default: yq eval -o=json project.yaml It returns: { "title" : "Nonoverse" , "description" : "Beautiful puzzle game about nonograms." , "link" : " https://lab174.com/nonoverse " , "platforms" : { "iPhone" : true , "iPad" : true , "AppleWatch" : false }, "countries" : [ "DE" , "FR" , "NO" , "PL" , "RO" ] } < Back to LAB174.com | 2026-01-13T08:48:04 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.