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://livesuggest.ai/es/ | Asistente IA de reuniones sin bot | LiveSuggest LiveSuggest 1h gratis Precios Iniciar sesión Registrarse Comenzar sesión Español 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 gratis Precios Iniciar sesión Registrarse Comenzar sesión 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 Asistente IA de reuniones que no se une a tus llamadas Recibe sugerencias IA en tiempo real vía micrófono o compartiendo una pestaña. Ningún bot entra en tu reunión, ninguna grabación almacenada. Probar gratis ✓ Sin tarjeta de crédito ✓ Sin registro ✓ 1h gratis 👥 Ya lo utilizan consultores, freelancers y gerentes de proyecto Ejemplo de ayuda IA durante reuniones SEGUIMIENTO DE REUNIÓN Decisión acordada: Sara termina el prototipo el viernes. NUEVA IDEA ¿Y si programamos una retrospectiva después de este sprint para recoger las lecciones aprendidas? EXPLICACIÓN DE TÉRMINO El "sprint" mencionado corresponde a un ciclo de desarrollo de 2 semanas en metodología Agile. TRADUCCIÓN DE TÉRMINO "Stakeholder" (inglés) — parte interesada, persona o grupo con interés en el proyecto. Escritorio Móvil Todo lo que necesitas para mantenerte comprometido y contribuir efectivamente Sugerencias en tiempo real Recibe sugerencias contextuales mientras la conversación avanza. Ideas de respuestas, recordatorios de puntos clave y aclaraciones aparecen cuando más los necesitas. Sin instalación necesaria Accede a LiveSuggest, un asistente de reuniones sin bot, directamente desde tu navegador web. Sin descargas, sin extensiones, sin configuración compleja. Comienza en segundos. Diseño centrado en la privacidad Diseñado con el consentimiento y la transparencia en su núcleo. Tus conversaciones se procesan en tiempo real sin grabación y se eliminan automáticamente. No se conserva ningún dato una vez que termina tu sesión. Preguntas frecuentes ¿Cómo funciona sin bot? LiveSuggest captura el audio directamente desde tu dispositivo — vía micrófono o compartiendo una pestaña del navegador. Ningún bot se une a tu llamada ni aparece en la lista de participantes. ¿Es igual de preciso sin grabación? Sí. Usamos los mismos modelos de IA avanzados que las herramientas basadas en grabaciones. Tu audio se procesa en tiempo real y se descarta inmediatamente — misma precisión, mayor privacidad. ¿No me distraerán las sugerencias? No. Las sugerencias aparecen en una ventana separada que consultas cuando lo necesitas. Apoyan tu participación sin interrumpir la conversación. Cómo funciona 1 Inicia una sesión Abre LiveSuggest en tu navegador y confirma que todos los participantes están informados. Listo para escuchar 2 Únete a tu reunión Únete a tu reunión en línea o en persona. LiveSuggest escucha y transcribe en tiempo real. Transcribiendo… 3 Recibe sugerencias Recibe sugerencias útiles y contextuales durante toda tu reunión para contribuir efectivamente. Sugerencias en tiempo real 4 tipos de sugerencias personalizables Seguimiento de reunión Captura decisiones clave, acciones pendientes y acuerdos con responsables y plazos, asegurando que nada importante se escape. Nueva idea Sugiere ideas relevantes y perspectivas frescas para enriquecer la discusión y abrir nuevas direcciones. Explicación de término Aclara al instante términos técnicos, acrónimos y conceptos complejos mencionados en la conversación, para que nunca te pierdas. Traducción de término Traduce y explica expresiones en otros idiomas sobre la marcha, ayudándote a mantenerte conectado sin importar el idioma. Ningún bot en tu reunión 📹 Zoom 💼 Teams 🎥 Meet 👥 En persona Funciona con cualquier plataforma de reuniones desde el navegador A diferencia de otras herramientas de IA, LiveSuggest nunca añade un participante a tu reunión. Funciona perfectamente con Google Meet, Zoom, Microsoft Teams o cualquier plataforma accesible desde el navegador — solo comparte el audio de la pestaña. Para reuniones presenciales, usa tu micrófono. Elige tu plan Elige el plan que se adapte a tus necesidades 🧾 Facturación empresarial disponible Basic Para descubrir $ 3 /mes sin IVA 3 horas de audio ~6 reuniones de 30 min Empezar ★ Recomendado Plus El más popular $ 8 /mes sin IVA 10 horas de audio ~20 reuniones de 30 min 10h al precio de 8h Elegir Plus Pro Para usuarios avanzados $ 20 /mes sin IVA 30 horas de audio ~60 reuniones de 30 min 30h al precio de 20h Pasar a Pro Diseño centrado en la privacidad ✓ Diseñado con el consentimiento y la transparencia en su núcleo. Tus conversaciones se procesan en tiempo real sin grabación y se eliminan automáticamente. No se conserva ningún dato una vez que termina tu sesión. ✓ Audio procesado en tiempo real, no almacenado ✓ Datos de sesión eliminados al final de cada sesión ✓ Privacidad ¿Listo para no olvidar nada y contribuir mejor en las reuniones? Prueba LiveSuggest gratis — no se requiere tarjeta de crédito. Recibe sugerencias IA en tiempo real sin bots ni grabaciones. Mantente enfocado, contribuye mejor. Probar ahora — Gratis Ver precios ✓ Sin tarjeta de crédito ✓ Sin registro ✓ 1h gratis LiveSuggest Recibe sugerencias contextuales de un asistente de reuniones sin bot mientras hablas — ideas de respuestas, recordatorios de puntos clave y aclaraciones para mantenerte alerta en el momento, incluso cuando trabajas en otro idioma. Producto Precios FAQ Blog Legales Privacidad Términos Aviso legal Consentimiento Soporte Contacto Reportar un error © 2026 LiveSuggest. Todos los derechos reservados. Este sitio utiliza cookies Utilizamos cookies para garantizar el correcto funcionamiento del sitio y mejorar su experiencia. Puede aceptar todas las cookies, rechazarlas o personalizar sus preferencias. Aceptar todo Rechazar todo Personalizar | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb3-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://lab174.com/blog/202601-yaml-norway/#cb4-11 | 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/#cb5-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://www.highlight.io/customers/motion | How Highlight Enables Motion's Investigation into the User Journey Star us on GitHub Star Migrate your Highlight account to LaunchDarkly by February 28, 2026. Learn more on our blog. Product Integrations Pricing Resources Docs Sign in Sign up All customers Customer Case Study How Highlight Enables Motion's Investigation into the User Journey Onboarding Experience One of the many needs of Motion was to better understand the nuances of the user journey during their customers onboarding process. Highlight.io stepped in with its Session Replay tool, offering Motion a high-definition perspective on user experiences. This replaced the need for conventional user interviews, providing Motion with direct, actionable insights on how their user's experience was influenced by their product. “ Highlight.io enabled Motion to identify and understand the behavioral patterns of their users, effectively distinguishing between those who successfully used the platform and those who did not. ” Ethan Yu , Motion Check out our documentation here to learn more about the benefits and features of Highlight's Session Replay product. Seamless Implementation and Product Usage With details such as Highlight’s Amplitude integration and a variety of SDKs available, Motion was able to quickly integrate the product. Once they began using the tool, they were able to swiftly identify and resolve user issues. “ We have rarely used support, and on the few occasions we did, we received near instantaneous responses. I was reassured that my team’s problems were being taken very seriously. ” Ethan Yu , Motion Giving Confidence The collaboration between Highlight.io and Motion highlights the importance of insightful, user-friendly observability tools in understanding and improving user experiences. This partnership has been instrumental in optimizing Motion’s approach to user engagement and product development - it is now a requirement to watch Highlight’s Session Replays to monitor that a given launch goes successfully. “ I would absolutely recommend Highlight. They ship quickly, often, and are reliable - these were my main concerns when evaluating vendors. ” Ethan Yu , Motion Previous Customer Next Customer About the company Individual and team productivity tool that helps busy people effectively plan their day and get their most important work done on time. Founded 2019 Using Highlight since Jul 2022 Try Highlight Today Get the visibility you need Get started for free Product Pricing Sign up Features Privacy & Security Customers Session Replay Error Monitoring Logging Competitors LogRocket Hotjar Fullstory Smartlook Inspectlet Datadog Sentry Site24x7 Sprig Mouseflow Pendo Heap LogicMonitor Last9 Axiom Better Stack HyperDX Dash0 Developers Changelog Documentation Ambassadors Frameworks React Next.js Angular Gatsby.js Svelte.js Vue.js Express Golang Next.js Node.js Rails Hono Contact & Legal Terms of Service Privacy Policy Careers sales@highlight.io security@highlight.io [object Object] | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb1-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://livesuggest.ai/de/ | KI-Meeting-Assistent ohne Bot | LiveSuggest LiveSuggest 1h kostenlos Preise Anmelden Registrieren Sitzung starten Deutsch 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 kostenlos Preise Anmelden Registrieren Sitzung starten 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 Sprachen KI-Meeting-Assistent, der Ihren Anrufen nicht beitritt Erhalten Sie Echtzeit-KI-Vorschläge per Mikrofon oder Tab-Sharing. Kein Bot tritt Ihrem Meeting bei, keine Aufnahme gespeichert. Kostenlos testen ✓ Keine Kreditkarte ✓ Keine Registrierung ✓ 1 Stunde gratis 👥 Bereits von Beratern, Freelancern und Projektmanagern genutzt Beispiel für KI-Hilfe während Meetings MEETING-FOLLOW-UP Beschluss: Sarah stellt den Prototyp bis Freitag fertig. NEUE IDEE Wie wäre es, nach diesem Sprint eine Retrospektive einzuplanen, um die Erkenntnisse festzuhalten? BEGRIFFSERKLÄRUNG Der erwähnte "Sprint" entspricht einem 2-wöchigen Entwicklungszyklus in der Agile-Methodik. BEGRIFFSÜBERSETZUNG "Stakeholder" (Englisch) — Interessenvertreter, Person oder Gruppe mit Interesse am Projekt. Desktop Mobil Alles, was Sie brauchen, um engagiert zu bleiben und effektiv beizutragen Echtzeit-Vorschläge Erhalten Sie kontextbezogene Vorschläge, während das Gespräch fortschreitet. Antwortideen, Erinnerungen an wichtige Punkte und Klarstellungen erscheinen, wenn Sie sie am meisten brauchen. Keine Installation erforderlich Greifen Sie auf LiveSuggest, einen bot-freien Meeting-Assistenten, direkt über Ihren Webbrowser zu. Keine Downloads, keine Erweiterungen, keine komplexe Einrichtung. Starten Sie in Sekunden. Datenschutz-orientiertes Design Mit Zustimmung und Transparenz als Kern entwickelt. Ihre Gespräche werden in Echtzeit ohne Aufnahme verarbeitet und automatisch gelöscht. Keine Daten werden nach Ende Ihrer Sitzung gespeichert. Häufige Fragen Wie funktioniert es ohne Bot? LiveSuggest erfasst Audio direkt von Ihrem Gerät — per Mikrofon oder Browser-Tab-Sharing. Kein Bot tritt Ihrem Anruf bei oder erscheint in der Teilnehmerliste. Ist es ohne Aufnahme genauso genau? Ja. Wir verwenden dieselben fortschrittlichen KI-Modelle wie aufnahmebasierte Tools. Ihr Audio wird in Echtzeit verarbeitet und sofort verworfen — gleiche Genauigkeit, stärkerer Datenschutz. Werden mich die Vorschläge ablenken? Nein. Vorschläge erscheinen in einem separaten Fenster, das Sie bei Bedarf ansehen. Sie unterstützen Ihre Teilnahme, ohne das Gespräch zu unterbrechen. So funktioniert es 1 Starten Sie eine Sitzung Öffnen Sie LiveSuggest in Ihrem Browser und bestätigen Sie, dass alle Teilnehmer informiert sind. Bereit zum Zuhören 2 Treten Sie Ihrem Meeting bei Nehmen Sie an Ihrem Meeting online oder persönlich teil. LiveSuggest hört zu und transkribiert in Echtzeit. Transkription läuft… 3 Erhalten Sie Vorschläge Erhalten Sie hilfreiche, kontextbezogene Vorschläge während Ihres gesamten Meetings, um effektiv beizutragen. Echtzeit-Vorschläge 4 anpassbare Vorschlagstypen Meeting-Follow-up Erfasst wichtige Entscheidungen, Aufgaben und Vereinbarungen mit Verantwortlichen und Fristen, damit nichts Wichtiges untergeht. Neue Idee Schlägt relevante Ideen und neue Perspektiven vor, um die Diskussion zu bereichern und neue Richtungen anzustoßen. Begriffserklärung Erklärt sofort Fachbegriffe, Akronyme und komplexe Konzepte im Gespräch, damit Sie nie den Überblick verlieren. Begriffsübersetzung Übersetzt und erklärt fremdsprachige Ausdrücke spontan, damit Sie sprachübergreifend immer dabei bleiben. Kein Bot in Ihrem Meeting 📹 Zoom 💼 Teams 🎥 Meet 👥 Persönlich Funktioniert mit jeder browserbasierten Meeting-Plattform Anders als andere KI-Tools fügt LiveSuggest niemals einen Teilnehmer zu Ihrem Meeting hinzu. Funktioniert nahtlos mit Google Meet, Zoom, Microsoft Teams oder jeder browserbasierten Plattform – teilen Sie einfach den Tab-Audio. Für persönliche Meetings nutzen Sie Ihr Mikrofon. Wählen Sie Ihren Plan Wählen Sie den Plan, der zu Ihren Bedürfnissen passt 🧾 Geschäftsrechnungen verfügbar Basic Zum Ausprobieren $ 3 /Monat zzgl. MwSt. 3 Stunden Audio ~6 Meetings von je 30 Min. Loslegen ★ Empfohlen Plus Am beliebtesten $ 8 /Monat zzgl. MwSt. 10 Stunden Audio ~20 Meetings von je 30 Min. 10h zum Preis von 8h Plus wählen Pro Für Power-User $ 20 /Monat zzgl. MwSt. 30 Stunden Audio ~60 Meetings von je 30 Min. 30h zum Preis von 20h Pro werden Datenschutz-orientiertes Design ✓ Mit Zustimmung und Transparenz als Kern entwickelt. Ihre Gespräche werden in Echtzeit ohne Aufnahme verarbeitet und automatisch gelöscht. Keine Daten werden nach Ende Ihrer Sitzung gespeichert. ✓ Audio wird in Echtzeit verarbeitet, nicht gespeichert ✓ Sitzungsdaten werden am Ende jeder Sitzung gelöscht ✓ Datenschutz Bereit, nichts mehr zu vergessen und besser in Meetings beizutragen? Probieren Sie LiveSuggest kostenlos — keine Kreditkarte erforderlich. Erhalten Sie Echtzeit-KI-Vorschläge ohne Bots oder Aufnahmen. Bleiben Sie engagiert, tragen Sie besser bei. Jetzt testen — Kostenlos Preise ansehen ✓ Keine Kreditkarte ✓ Keine Registrierung ✓ 1 Stunde gratis LiveSuggest Erhalten Sie kontextbezogene Vorschläge von einem bot-freien Meeting-Assistenten während Sie sprechen — Antwortideen, Erinnerungen an wichtige Punkte und Klärungen, um im Moment konzentriert zu bleiben, auch wenn Sie in einer Fremdsprache arbeiten. Produkt Preise FAQ Blog Rechtliches Datenschutz AGB Impressum Einwilligung Support Kontakt Fehler melden © 2026 LiveSuggest. Alle Rechte vorbehalten. Diese Website verwendet Cookies Wir verwenden Cookies, um die ordnungsgemäße Funktionsweise der Website sicherzustellen und Ihr Erlebnis zu verbessern. Sie können alle Cookies akzeptieren, ablehnen oder Ihre Einstellungen anpassen. Alle akzeptieren Alle ablehnen Anpassen | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb4-10 | 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://dev.to/stevenlu2004 | Tongyu Lu - 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 Tongyu Lu High school student at PRISMS. Interested in CS, ML, game-dev. USACO Platinum qualified, but still getting better at projects. Codes for fun. Location Earth Joined Joined on Jul 30, 2020 github website Education https://prismsus.org More info about @stevenlu2004 Badges Five Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least five years. Got it Close Four Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least four years. Got it Close Writing Debut Awarded for writing and sharing your first DEV post! Continue sharing your work to earn the 4 Week Writing Streak Badge. Got it Close Three Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least three years. Got it Close Two Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least two years. Got it Close One Year Club This badge celebrates the longevity of those who have been a registered member of the DEV Community for at least one year. Got it Close GitHub Repositories pygame-flappy-bird PyGame implementation of Flappy Bird Python • 1 star 2048 A simple C++ implementation of the classic game of 2048. C++ landmark Simple LAN file sharing using Node.js JavaScript • 1 star Skills/Languages I know some C++, Python, HTML/CSS/JS (Express, React), and a bit of Java Currently learning I plan to learn more about machine learning, get myself more familiar with PyQt5, and probably do some small projects. Post 2 posts published Comment 3 comments written Tag 22 tags followed High School Research #00 | Getting Started: idea + some literature review + glossary Tongyu Lu Tongyu Lu Tongyu Lu Follow Oct 8 '20 High School Research #00 | Getting Started: idea + some literature review + glossary 1 reaction Comments Add Comment 2 min read Want to connect with Tongyu Lu? Create an account to connect with Tongyu Lu. You can also sign in below to proceed if you already have an account. Create Account Already have an account? Sign in USACO 2014 December Gold 1 Tongyu Lu Tongyu Lu Tongyu Lu Follow Aug 16 '20 USACO 2014 December Gold 1 # usaco # computerscience 2 reactions Comments Add Comment 5 min read loading... 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — 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://lab174.com/blog/202601-yaml-norway/#cb6-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://grox.io/ | Groxio Learning: Career Fuel for Programmers Groxio Logo Home Courses Training Blog About Sign up/in Home Courses Training Blog About Contact Us Sign up/in Get unlimited access to $1,297 worth of Elixir courses for just $350/year Career Fuel for Programmers Build reliable Elixir systems—faster. Elevate your Elixir, OTP, Phoenix, and LiveView skills through structured courses, live training, and 1-on-1 mentorship. Learn disciplined AI workflows that improve real outcomes. Bruce Tate +10 books • 2 Jolt Awards • "Seven Languages in Seven Weeks" Get full access Learn more Choose the approach that fits your goals How do you want to learn? Self-Paced Courses Build strong foundations at your own pace. Deep video courses on Elixir, OTP, LiveView, and disciplined AI workflows. Browse Courses Live Training Recalibrate how you think about systems. Small-group workshops that focus on mental models that stick. Explore Training Mentorship Work through real production problems. 1-on-1 guidance for course members and trained teams making real decisions. See Options Core Topics What you'll learn From core foundations to production-ready systems Core Elixir & OTP Processes, supervision, boundaries, and failure as first-class concepts. Phoenix & LiveView Real-time systems, structure, and patterns that scale with complexity. AI Workflows Structured prompting, clear boundaries, repeatable outcomes. Production Systems Architecture, tradeoffs, deployments, and long-term maintenance. About Bruce Tate Mental models that stick Bruce is the author of widely read books on Elixir, OTP, Phoenix, and LiveView, and has helped thousands of developers understand why these systems behave the way they do. Author of: Programming Phoenix LiveView Designing Elixir Systems with OTP Programming Phoenix Seven Languages in Seven Weeks Adopting Elixir + 5 more books Why Groxio When learning Elixir, it's natural to focus on what functions do. We teach why systems work . We start with boundaries, failure, supervision, and tradeoffs. Then show how Elixir makes those ideas concrete. The same discipline applies to AI: structured workflows, clear boundaries, real outcomes. "I don't just want you to write Elixir. I want you to understand why it works the way it does. That understanding changes how you approach every problem." — Bruce Tate 10+ Technical Books 2× Jolt Awards 20+ Years Teaching Stay sharp on Elixir and AI Short notes on Elixir, OTP, Phoenix, and disciplined AI workflows, plus updates on courses and conferences. Subscribe We respect your privacy. Read our privacy policy . Real feedback from developers who've taken our courses and training What students say " I was really happy to learn about starting dynamic processes that I name on the fly. " Bill Groxio Training " I've been able to continue building my career in Elixir with confidence. " Liv Groxio Training " I always have fun. I'm a beginner and have to type in front of everyone. I just come as myself. " Paulo Groxio Training " It's about learning how to learn... allowing us to follow our own path. For me, it's life changing. " Christine Elixir em Foco " I learned important concepts to learn everything else in the Elixir Ecosystem. " Yuri Groxio Training " The biggest insight I had was the CRC pattern... That underlying pattern shapes programming. " Zaki Groxio Training Questions about team training or mentoring? Reach out to Maggie for help with live training, bulk course licenses, or custom team arrangements. Maggie Tate Business Development Send Message Education Online Courses Live Training Blog Who are we? About us Contact us Legal Privacy Policy Terms of Service Cookie Policy Do Not Sell or Share My Personal Information Groxio Logo LinkedIn Instagram X YouTube © 2018-2026 Groxio, LLC. All rights reserved. | 2026-01-13T08:48:04 |
https://forem.com/t/nintendoswitch/page/8 | Nintendoswitch Page 8 - 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 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: Viewfinder - Official Xbox Launch Trailer Gaming News Gaming News Gaming News Follow Aug 12 '25 IGN: Viewfinder - Official Xbox Launch Trailer # xbox # playstation # nintendoswitch # pcgaming Comments Add Comment 1 min read IGN: Story of Seasons: Grand Bazaar - Official Freya Trailer Gaming News Gaming News Gaming News Follow Aug 12 '25 IGN: Story of Seasons: Grand Bazaar - Official Freya Trailer # nintendo # nintendoswitch # pcgaming # steam Comments Add Comment 1 min read IGN: Henry Halfhead - Official Release Date Trailer Gaming News Gaming News Gaming News Follow Aug 11 '25 IGN: Henry Halfhead - Official Release Date Trailer # gamedev # indie # pcgaming # nintendoswitch Comments Add Comment 1 min read IGN: Super Robot Wars Y - Official Demo Trailer Gaming News Gaming News Gaming News Follow Aug 9 '25 IGN: Super Robot Wars Y - Official Demo Trailer # playstation # nintendoswitch # pcgaming # steam Comments Add Comment 1 min read IGN: Nintendo Hikes Prices in the United States - NVC Clips Gaming News Gaming News Gaming News Follow Aug 8 '25 IGN: Nintendo Hikes Prices in the United States - NVC Clips # nintendo # nintendoswitch # pcgaming Comments Add Comment 1 min read IGN hit by layoffs as parent company Ziff Davis cuts costs Gaming News Gaming News Gaming News Follow Aug 8 '25 IGN hit by layoffs as parent company Ziff Davis cuts costs # pcgaming # xbox # playstation # nintendoswitch Comments Add Comment 1 min read IGN: Did Nintendo Just Lose Its Chance to Beat the PS2? - Next-Gen Console Watch Gaming News Gaming News Gaming News Follow Aug 8 '25 IGN: Did Nintendo Just Lose Its Chance to Beat the PS2? - Next-Gen Console Watch # nintendo # nintendoswitch # playstation # retrogaming Comments Add Comment 1 min read IGN: Mina The Hollower Gameplay on Nintendo Switch 2 Gaming News Gaming News Gaming News Follow Aug 8 '25 IGN: Mina The Hollower Gameplay on Nintendo Switch 2 # nintendoswitch # retrogaming # indie # gaming Comments Add Comment 1 min read IGN: The House of The Dead 2: Remake - Official Launch Trailer Gaming News Gaming News Gaming News Follow Aug 8 '25 IGN: The House of The Dead 2: Remake - Official Launch Trailer # pcgaming # nintendoswitch # playstation # xbox Comments Add Comment 1 min read IGN: Pokemon Unite - Official Latias Overview Trailer Gaming News Gaming News Gaming News Follow Aug 7 '25 IGN: Pokemon Unite - Official Latias Overview Trailer # nintendoswitch # gaming Comments Add Comment 1 min read IGN: Go-Go Town! - Official Release Window Reveal Trailer | Nintendo Indie World 2025 Gaming News Gaming News Gaming News Follow Aug 7 '25 IGN: Go-Go Town! - Official Release Window Reveal Trailer | Nintendo Indie World 2025 # nintendo # nintendoswitch # indie # gamedev Comments Add Comment 1 min read IGN: Undusted: Letters from the Past - Nintendo Switch Reveal Trailer | Nintendo Indie World 2025 Gaming News Gaming News Gaming News Follow Aug 7 '25 IGN: Undusted: Letters from the Past - Nintendo Switch Reveal Trailer | Nintendo Indie World 2025 # nintendoswitch # indie # steam # gamedev Comments Add Comment 1 min read IGN: Glaciered - Official Nintendo Switch 2 Release Window Trailer | Nintendo Indie World 2025 Gaming News Gaming News Gaming News Follow Aug 7 '25 IGN: Glaciered - Official Nintendo Switch 2 Release Window Trailer | Nintendo Indie World 2025 # nintendo # nintendoswitch # indie # pcgaming Comments Add Comment 1 min read IGN: Content Warning - Official Nintendo Switch Announcement Trailer | Nintendo Indie World 2025 Gaming News Gaming News Gaming News Follow Aug 7 '25 IGN: Content Warning - Official Nintendo Switch Announcement Trailer | Nintendo Indie World 2025 # nintendo # nintendoswitch # indie # pcgaming Comments Add Comment 1 min read IGN: UFO 50 - Official Nintendo Switch Release Window Trailer | Nintendo Indie World 2025 Gaming News Gaming News Gaming News Follow Aug 7 '25 IGN: UFO 50 - Official Nintendo Switch Release Window Trailer | Nintendo Indie World 2025 # nintendoswitch # indie # steam # gamedev Comments Add Comment 1 min read IGN: Ultimate Sheep Raccoon - Official Nintendo Switch Announcement Trailer | Nintendo Indie World 2025 Gaming News Gaming News Gaming News Follow Aug 7 '25 IGN: Ultimate Sheep Raccoon - Official Nintendo Switch Announcement Trailer | Nintendo Indie World 2025 # nintendo # nintendoswitch # indie # gamedev Comments Add Comment 1 min read IGN: Is This Seat Taken? - Official Launch Trailer | Nintendo Indie World 2025 Gaming News Gaming News Gaming News Follow Aug 7 '25 IGN: Is This Seat Taken? - Official Launch Trailer | Nintendo Indie World 2025 # nintendo # indie # nintendoswitch # steam Comments Add Comment 1 min read IGN: Caves of Qud - Official Nintendo Switch Announcement Trailer | Nintendo Indie World 2025 Gaming News Gaming News Gaming News Follow Aug 7 '25 IGN: Caves of Qud - Official Nintendo Switch Announcement Trailer | Nintendo Indie World 2025 # nintendoswitch # indie # pcgaming # gamedev Comments Add Comment 1 min read IGN: Opus: Prism Peak - Official Nintendo Switch Announcement Trailer | Nintendo Indie World 2025 Gaming News Gaming News Gaming News Follow Aug 7 '25 IGN: Opus: Prism Peak - Official Nintendo Switch Announcement Trailer | Nintendo Indie World 2025 # nintendo # nintendoswitch # indie # gamedev Comments Add Comment 1 min read IGN: Tiny Bookshop - Official Nintendo Switch Launch Trailer | Nintendo Indie World 2025 Gaming News Gaming News Gaming News Follow Aug 7 '25 IGN: Tiny Bookshop - Official Nintendo Switch Launch Trailer | Nintendo Indie World 2025 # nintendo # nintendoswitch # indie # gamedev Comments Add Comment 1 min read IGN: Neverway - Official Release Window Reveal Trailer | Nintendo Indie World 2025 Gaming News Gaming News Gaming News Follow Aug 7 '25 IGN: Neverway - Official Release Window Reveal Trailer | Nintendo Indie World 2025 # nintendo # indie # nintendoswitch # gamedev Comments Add Comment 1 min read IGN: Strange Antiquities - Official Release Date Announcement Trailer | Nintendo Indie World 2025 Gaming News Gaming News Gaming News Follow Aug 7 '25 IGN: Strange Antiquities - Official Release Date Announcement Trailer | Nintendo Indie World 2025 # nintendo # nintendoswitch # steam # indie Comments Add Comment 1 min read IGN: Herdling - Official Release Date Trailer | Nintendo Indie World 2025 Gaming News Gaming News Gaming News Follow Aug 7 '25 IGN: Herdling - Official Release Date Trailer | Nintendo Indie World 2025 # nintendo # nintendoswitch # indie # pcgaming Comments Add Comment 1 min read IGN: Nicktoons & The Dice of Destiny - Official Danny Phantom Reveal Trailer Gaming News Gaming News Gaming News Follow Aug 5 '25 IGN: Nicktoons & The Dice of Destiny - Official Danny Phantom Reveal Trailer # pcgaming # xbox # playstation # nintendoswitch Comments Add Comment 1 min read IGN: Madden 26 - Official Gameplay First Look Gaming News Gaming News Gaming News Follow Aug 5 '25 IGN: Madden 26 - Official Gameplay First Look # pcgaming # xbox # playstation # 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/pricing | Pricing · Cursor Skip to content Cursor Features Enterprise Pricing Resources ↓ Changelog Blog Docs ↗ Community Learn ↗ Workshops Forum ↗ Careers Features Enterprise Pricing Resources → Sign in Download Pricing Monthly Yearly Individual Plans Hobby Free Includes: ✓ No credit card required ✓ Limited Agent requests ✓ Limited Tab completions Download Pro $20 / mo. Everything in Hobby, plus: ✓ Extended limits on Agent ✓ Unlimited Tab completions ✓ Background Agents ✓ Maximum context windows Get Pro Pro+ Recommended $60 / mo. Everything in Pro, plus: ✓ 3x usage on all OpenAI, Claude, Gemini models Get Pro+ Ultra $200 / mo. Everything in Pro, plus: ✓ 20x usage on all OpenAI, Claude, Gemini models ✓ Priority access to new features Get Ultra Business Plans Teams $40 / user / mo. Everything in Pro, plus: ✓ Shared chats, commands, and rules ✓ Centralized team billing ✓ Usage analytics and reporting ✓ Org-wide privacy mode controls ✓ Role-based access control ✓ SAML/OIDC SSO Get Teams Enterprise Custom Everything in Teams, plus: ✓ Pooled usage ✓ Invoice/PO billing ✓ SCIM seat management ✓ AI code tracking API and audit logs ✓ Granular admin and model controls ✓ Priority support and account management Contact Sales Bugbot Add-on Free $0 Includes: ✓ Limited code reviews each month ✓ Unlimited access to Cursor Ask ✓ Cursor connection to auto-fix bugs ✓ GitHub integration Try Bugbot Pro $40 / user / mo. Everything in Free, plus: ✓ 14 day individual trial ✓ Unlimited reviews on up to 200 PRs/month ✓ Access to Bugbot Rules Get Bugbot Pro Teams $40 / user / mo. Everything in Pro, plus: ✓ 14-day team trial ✓ Unlimited code reviews on all PRs ✓ Analytics and reporting dashboard ✓ Advanced rules and settings Get Bugbot Teams Enterprise Custom Everything in Teams, plus: ✓ 30-day org-wide trial ✓ Advanced analytics and reporting ✓ Priority support and account management Contact Sales Trusted every day by millions of professional developers. Questions & Answers What is the right plan for me? ↓ ↑ What are my payment options? ↓ ↑ How does usage-based pricing work? ↓ ↑ How can I see and manage Cursor's usage in my organization? ↓ ↑ How does Cursor use my data? ↓ ↑ Where can I ask more questions? ↓ ↑ Get started with Cursor. Download ⤓ Contact Sales 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 Pricing Monthly Yearly Individual Plans Hobby Free Includes: ✓ No credit card required ✓ Limited Agent requests ✓ Limited Tab completions Download Pro $20 / mo. Everything in Hobby, plus: ✓ Extended limits on Agent ✓ Unlimited Tab completions ✓ Background Agents ✓ Maximum context windows Get Pro Pro+ Recommended $60 / mo. Everything in Pro, plus: ✓ 3x usage on all OpenAI, Claude, Gemini models Get Pro+ Ultra $200 / mo. Everything in Pro, plus: ✓ 20x usage on all OpenAI, Claude, Gemini models ✓ Priority access to new features Get Ultra Business Plans Teams $40 / user / mo. Everything in Pro, plus: ✓ Shared chats, commands, and rules ✓ Centralized team billing ✓ Usage analytics and reporting ✓ Org-wide privacy mode controls ✓ Role-based access control ✓ SAML/OIDC SSO Get Teams Enterprise Custom Everything in Teams, plus: ✓ Pooled usage ✓ Invoice/PO billing ✓ SCIM seat management ✓ AI code tracking API and audit logs ✓ Granular admin and model controls ✓ Priority support and account management Contact Sales Bugbot Add-on Free $0 Includes: ✓ Limited code reviews each month ✓ Unlimited access to Cursor Ask ✓ Cursor connection to auto-fix bugs ✓ GitHub integration Try Bugbot Pro $40 / user / mo. Everything in Free, plus: ✓ 14 day individual trial ✓ Unlimited reviews on up to 200 PRs/month ✓ Access to Bugbot Rules Get Bugbot Pro Teams $40 / user / mo. Everything in Pro, plus: ✓ 14-day team trial ✓ Unlimited code reviews on all PRs ✓ Analytics and reporting dashboard ✓ Advanced rules and settings Get Bugbot Teams Enterprise Custom Everything in Teams, plus: ✓ 30-day org-wide trial ✓ Advanced analytics and reporting ✓ Priority support and account management Contact Sales Trusted every day by millions of professional developers. Questions & Answers What is the right plan for me? ↓ ↑ What are my payment options? ↓ ↑ How does usage-based pricing work? ↓ ↑ How can I see and manage Cursor's usage in my organization? ↓ ↑ How does Cursor use my data? ↓ ↑ Where can I ask more questions? ↓ ↑ Get started with Cursor. Download ⤓ Contact Sales 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://lab174.com/blog/202601-yaml-norway/#cb4-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/#cb1-4 | 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://dev.to/jwebsite-go/sinie-zielienoie-razviertyvaniie-na-eks-14e3 | Сине-зеленое развертывание на EKS - 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 Khadijah (Dana Ordalina) Posted on Jan 9 Сине-зеленое развертывание на EKS # eks # aws # bluegreen # programming EKS = Управляемый Kubernetes от Amazon Web Services EKS предоставляет вам: Управляющая плоскость ** Kubernetes** (API-сервер, планировщик). AWS управляет этим за вас. Вам всё ещё необходимо: Рабочие узлы (EC2) → для запуска подов kubectl **→ для связи с кластером **YAML → для указания Kubernetes, что нужно запустить. Очень важная ментальная модель _`Your laptop (kubectl) | v EKS API Server (managed by AWS) | v Worker Nodes (EC2) → Pods → Containers`_ Enter fullscreen mode Exit fullscreen mode Подключаться к узлам по SSH НИКОГДА нельзя. Шаг 1 — Создайте EKS вручную (через консоль AWS, без использования инструментов). 1. Откройте консоль AWS → EKS Выберите регион (например: us-east-1) Нажмите «Создать кластер» . 2. Конфигурация кластера Заполнять только: Имя * : bluegreen-demo * Версия Kubernetes : по умолчанию Роль кластерной службы * : Если AWS отображает её, выберите её. Если нет, нажмите * «Создать роль» (AWS создаст её автоматически). Нажмите Далее 3. Сетевое взаимодействие Использовать значения по умолчанию : VPC по умолчанию Как минимум 2 подсети Доступ к общедоступной конечной точке Нажмите « Создать ». ⏳ Дождитесь активации В этот момент: Kubernetes существует НО пока ничего не может бежать Шаг 2 — Создание рабочих узлов (ЭТО создаст EC2) Зачем нам это нужно Kubernetes размещает поды на узлах . Нет узлов = нет подов. Создать группу узлов Внутри вашего кластера: Перейдите в раздел «Вычисления» → «Добавить группу узлов». Наполнять: Имя: bg-nodes Роль IAM: создать/выбрать роль работника по умолчанию Настройки узла: Тип экземпляра:t3.medium Желательно: 2 Мин.: 2 Макс.: 3 Создать группу узлов → дождаться активации Теперь EC2 существует автоматически. Шаг 3 — Подключите kubectl (так работает DevOps) С вашего ноутбука: aws eks update-kubeconfig \ --region us-east-1 \ --name bluegreen-demo Enter fullscreen mode Exit fullscreen mode Проверять: kubectl get nodes Enter fullscreen mode Exit fullscreen mode Если вы видите узлы → значит, вы соединены. Впредь: Консоль AWS практически неактуальна. Всё делается с помощью kubectl Почему существуют стратегии развертывания (ОЧЕНЬ ВАЖНО) До Kubernetes (старый мир) Остановить приложение Развернуть новую версию Запустите приложение снова. Пользователи видят время простоя Откат происходит медленно. Проблемы, с которыми сталкивался DevOps Простои во время развертывания Пользователи получают ошибки Быстрый откат недоступен. Страх перед развертыванием войск Проблема с Kubernetes решена: - Капсулы - Услуги - Самоисцеление Однако стратегия развертывания определяет, как будет перемещаться трафик. Именно поэтому * существуют стратегии развертывания * . Что такое сине-зеленая стратегия (в простом виде)? Сине-зеленый = две версии, работающие одновременно. Синий → текущее производство Зеленый → новая версия, протестирована Транспортный поток резко меняет направление движения. Отсутствие частичного трафика. Отсутствие замедления развертывания. Почему сине-зеленый цвет используется в DevOps Преимущества Отсутствие простоев Мгновенный откат Безопасные релизы Легко понять Предсказуемое поведение Когда DevOps выбирает сине-зеленый подход Критические приложения API Финансовые системы Внутренние платформы Когда неудача обходится дорого Как работает принцип «сине-зеленого» взаимодействия в Kubernetes (простая истина) Kubernetes уже предоставляет нам такой инструмент: 👉 Сервис Решение принимает служба: «Какие модули посещают пользователи?» Сине-зеленый = * изменить селектор услуги * Вот и все. Внедрение сине-зеленого подхода (с нуля) 1️⃣ Развертывание Blue (версия 1 – в рабочем режиме) apiVersion: apps/v1 kind: Deployment metadata: name: app-blue spec: replicas: 2 selector: matchLabels: app: demo color: blue template: metadata: labels: app: demo color: blue spec: containers: - name: app image: hashicorp/http-echo:0.2.3 args: ["-text=BLUE v1"] ports: - containerPort: 5678 Enter fullscreen mode Exit fullscreen mode 2️⃣ Экологичное развертывание (версия 2 – не запущена) apiVersion: apps/v1 kind: Deployment metadata: name: app-green spec: replicas: 2 selector: matchLabels: app: demo color: green template: metadata: labels: app: demo color: green spec: containers: - name: app image: hashicorp/http-echo:0.2.3 args: ["-text=GREEN v2"] ports: - containerPort: 5678 Enter fullscreen mode Exit fullscreen mode 3️⃣ Сервис (производственный трафик) apiVersion: v1 kind: Service metadata: name: prod-svc spec: selector: app: demo color: blue # LIVE VERSION ports: - port: 80 targetPort: 5678 Это переключатель управления . Разверните всё kubectl apply -f blue.yaml kubectl apply -f green.yaml kubectl apply -f service.yaml Enter fullscreen mode Exit fullscreen mode Трафик → СИНИЙ Само развертывание (синий → зеленый) Измените одну строку: color: green Enter fullscreen mode Exit fullscreen mode Подайте заявку снова: kubectl apply -f service.yaml Enter fullscreen mode Exit fullscreen mode Транспортный поток мгновенно переключается. Перезагрузка Pod не требуется. Простой отсутствует. Откат (безопасность DevOps) Вернитесь назад: color: blue Enter fullscreen mode Exit fullscreen mode Применить → откат завершен. Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Khadijah (Dana Ordalina) Follow DevOps Engineer. AWS, Terraform, Docker and CI/CD. Building real projects and sharing my DevOps journey. Location United States Work DevOps Engineer Joined Dec 20, 2025 More from Khadijah (Dana Ordalina) Readiness probe # aws # kubernetes # beginners # devops Kubernetes #1 # kubernetes # nginx # docker # programming 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#fn2 | 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://dev.to/help/writing-editing-scheduling#Guidelines-for-Avoiding-Plagiarism-on-DEV | Writing, Editing and Scheduling - DEV Help - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close DEV Help The latest help documentation, tips and tricks from the DEV Community. Help > Writing, Editing and Scheduling Writing, Editing and Scheduling In this article The Editor Drafting and publishing a post: Scheduling a post: Creating a Series Cross-posting Content Helpful Resources DEV Editor guide Markdown Cheatsheet Best Practices for Writing on DEV Guidelines for Avoiding Plagiarism on DEV Guidelines for AI-assisted Articles on DEV Common Questions Q: How do I set a canonical URL on my post? Q: How do I set a cover image for my post? Q: Do I own the articles that I publish? Q: Can I cross-post something I've already written on my own blog or Medium? Q: Can I use profanity in my posts? Q: Why has my post been removed? Q: Will you put ads on my posts' pages? Explore the ins and outs of writing, editing, scheduling, and managing articles. The Editor The DEV editor is your primary tool for writing and sharing posts. With a Markdown -based syntax and flexible options for embedding content, the editor is one of the main ways DEV members express themselves. Drafting, scheduling, and publishing posts are all options; importing via RSS is also a feature that we provide. Learn how to use the DEV editor to create and format your articles effectively: Drafting and publishing a post: Click on " Write a Post " in the top right corner of the site. Follow the prompts to fill out the necessary inputs. Give your post a title, write the body content, add appropriate tags, and fill out any other optional fields. If you're not ready to share your article, just click "Save draft" in the bottom left. You can access your drafts from your user dashboard and return to editing your post whenever you wish. Once you're ready to share your post, click the "Publish" button in the bottom left. Note: if you are using the Basic Markdown editor you interface is more minimalistic, and you'll need to change published: false to published: true in the Front Matter of the post, then save to publish your post. Congratulations, your post should be published! You should see the article listed on your public profile. Note that you can access analytics for each post you've shared from your user dashboard by clicking on the ... beside the article title. Scheduling a post: To schedule a post, you may open a draft or start writing a new post. Once you've got your post set up, click on the hexagon icon in the bottom left-hand corner near the Publish button. See "Schedule Publication" and use the inputs to select a date and time for the post to go live. Note: this feature is set to your local time zone. Creating a Series DEV provides authors with the ability to link articles together in a series. A series has a title and an associated page to hold all the entries (e.g. Sloan's Inbox ). Most often this is done for articles that are thematically related or recurring weekly posts. We have a handy guide here that explains step-by-step how to create a series on DEV. Note: If you've written the first entry in a series and are wondering why the series title is not easily visible, it's because we don't actually display information about a post being part of a series until there is more than one entry in the series. Once you write your second entry in the series, the Table of Contents and title for the series should appear. Cross-posting Content DEV offers a variety of features for those who want to cross-post content from elsewhere on the web. We encourage folks to share articles from their personal and company blogs! Notably, we offer folks the ability to import content via RSS and set canonical links on any posts that are shared. Using the RSS Feed on DEV Community Configure RSS Feed: Navigate to extensions within the settings. Under "Publishing to DEV Community 👩💻👨💻 from RSS," enter your blog's RSS feed URL. You will see the option to "Mark the RSS source as canonical URL" or "Replace links with DEV Community links." Check the info below (Specifying a Canonical URL) to help you decide which option to select. Click "submit feed settings." Edit Post Drafts Before Publishing Go to your user dashboard. Click edit beside the post you want to post. Save each draft after making changes. Publish Post when ready. How to Specify a Canonical URL Members reposting content often worry about original posts becoming less discoverable in search engines and their website losing visibility as the newer publishing platform (e.g., DEV) might surpass the original blog. Fortunately, DEV allows authors to address these concerns. By inputting a canonical URL, contributors can ensure search engines understand the original source. This prevents any penalties for reposting, and search engine crawlers boost the ranking of the original article. Option 1 (RSS Import): Check the "Mark the RSS source as canonical URL by default" box upon import. Option 2 (Individual Posts): Identify your editor version in /settings/customization. Rich + Markdown Editor: Click the gear icon next to "Save draft" and enter the original post's URL in the "Canonical URL" field. Basic Markdown Editor: Add canonical_url: X to the post's front matter, specifying the original post's URL. Following these steps ensures proper attribution and maintains the visibility of your content. Helpful Resources Below you'll find various resources we recommend for better understanding DEV's writing policies and tools. DEV Editor guide A quick guide that provides you with technical tips for using the DEV Editor and our brand of Markdown. You can also find it by clicking the "?" page in the editor . Markdown Cheatsheet A handy cheatsheet for commonly-used Markdown formatting syntax. Best Practices for Writing on DEV A helpful series that offers both technical tips and general guidance for making the best-fit article for DEV. 🙌 Guidelines for Avoiding Plagiarism on DEV This resource offers guidance for how to avoid plagiarism. We take a strong stance against plagiarism on DEV; please don't hesitate to report any plagiarism to us. Guidelines for AI-assisted Articles on DEV These guidelines detail our requirements for properly labelling AI-assisted content on DEV. Please don't hesitate to report any content that is written with AI-assistance if it isn't following these guidelines. Common Questions Q: How do I set a canonical URL on my post? In the post editor, click the hexagon icon in the bottom left-hand corner beside "save draft" and you'll see an input box to designate a Canonical URL. Note: if you are using the Basic Markdown editor you must add a line for it inside the triple dashes (aka Front Matter), like so: --- title: published: false tags: canonical_url: <https://mycoolsite.com/my-post> --- Q: How do I set a cover image for my post? If using the Rich + Markdown editor, then click the "Add a cover image" button above the title of the post. If using the Basic Markdown editor, include cover_image: [url] in the front matter of your post. Note: you may change your editor type from your settings . Q: Do I own the articles that I publish? Yes, you own the rights to the content you create and post on dev.to and you have the full authority to post, edit, and remove your content as you see fit. Q: Can I cross-post something I've already written on my own blog or Medium? Absolutely, as long as you have the rights you need to do so! And if it's of high quality, we'll feature it. Q: Can I use profanity in my posts? We don't disallow profanity in general, but we do have an internal policy of not promoting posts that have profanity in the title, so you might want to keep that in mind. If your profanity is targeted at individuals or hateful, then it would cross the lines of what's acceptable via our Code of Conduct and we may take necessary action to remove you content. Q: Why has my post been removed? Your post is subject to removal at the discretion of the moderators if they believe it does not meet the requirements of our Code of Conduct . If you think we may have made a mistake, please email us at support@dev.to . Q: Will you put ads on my posts' pages? It's possible. We do allow organizations to purchase advertisements with DEV. However, if you would prefer that no ads be placed next to your posts, just navigate to Settings > Customization , scroll down to sponsors, and uncheck the box beside "Permit Nearby External Sponsors (When publishing)" Of course, we'd appreciate it if you keep those boxes checked as this is important to our business. But, we respect your decision and appreciate you sharing posts with us! 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV 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://dev.to/eachampagne/garbage-collection-43nk#tracing | Garbage Collection - 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 eachampagne Posted on Nov 17, 2025 • Edited on Dec 6, 2025 Garbage Collection # computerscience # performance # programming It’s easy to forget, while working in the abstract in terms of functions and algorithms, that the memory our programs depend on is real . The values we use in our programs actually exist on the hardware at specific addresses. If we don’t keep track of where we’ve stored data, we run the risk of overwriting something important and getting the wrong information when we go to look it up again. On the other hand, if we’re too guarded about protecting our data, even after we’re finished with it, we waste memory that the program could better use on other tasks. Most programming languages today implement garbage collection to automate periodically releasing memory we no longer need. The garbage collector cannot predict exactly which values will be used again by our program, but it can find some that cannot due to no longer having any way to use them, and safely free them. Garbage Collection Algorithms Reference Counting The simplest algorithm is just to keep a count of references to a piece of memory. If the number of references ever reaches zero, that memory can no longer be reached and can be safely disposed of. However, this strategy fails with circular references. If two objects, for example, reference each other, their reference counts with never reach zero, even if they are otherwise inaccessible from the main program. Tracing Tracing (usually mark-and-sweep), is a more sophisticated approach to memory management. Starting from some defined root(s), the garbage collector visits every piece of memory accessible from either the root or its descendants, marking that memory as still reachable. Any memory not traversed is unreachable and is garbage collected. This avoids the problem of circular references “trapping” memory, since the cycle will not be reached from the main memory graph. However, this approach has more overhead than the reference counting strategy. Many garbage collectors reduce the overhead of mark-and-search by having two (or more) “generations” of allocations. The generational hypothesis states that most allocations die young (think how many variables you use once in a for loop and never again), but those that survive are much more likely to survive a long time. Thus, the pool of young allocations (the “nursery”) is garbage collected frequently, while the old (“tenured”) pool is checked less often. It’s possible to combine both strategies in a hybrid collector. For example, Python uses reference counting as its primary algorithm, then uses a mark-and-sweep pass over the (now smaller) pool of allocated memory to find and eliminate circular references. The Downsides of Garbage Collection Of course, the garbage collector itself introduces some overhead. Depending on the implementation, it may bring the program to a halt while it scans and frees data or defragments the remaining memory. It is also impossible to create a perfectly efficient garbage collector due to the inherent uncertainty in which values will be used again. Other Approaches to Memory Management There are alternatives to garbage collection. A few languages, such as C and C++, require the programmer to manage memory manually (although you can add garbage collectors to both languages yourself if you wish), both while allocating memory to new variables and when deciding when to free memory. Manual memory management avoids the overhead of garbage collection, but adds to program complexity, since this now must be handled by the code itself rather than happening in the background. This also gives the programmer many opportunities to make mistakes , from creating floating pointers by freeing too soon to leaking memory by freeing too late or not at all, to say nothing of the difficulty of using pointers themselves. Rust takes a third option and introduces the concept of “ ownership ” – only one variable can own a piece of data at a time, and that data is released as soon as its owner goes out of scope. This eliminates the need for garbage collection at runtime, as well with its associated performance costs. However, the programmer has to keep track of ownership and borrowing of data, which limits how data can be read or changed at certain points of the program. This requires thinking in a different way from other languages, since some familiar patterns simply won’t compile, and increases Rust’s learning curve sharply. Garbage Collection in JavaScript JavaScript follows the majority of programming languages in using a garbage collector. However, the garbage collector itself is implemented and run by the JavaScript engine, not the script we write ourselves, so implementation varies slightly across engines. However, the general principles are the same. Modern JavaScript libraries all use a mark-and-sweep algorithm with the global object as the algorithm’s root. Since I regularly use Firefox and Node, I’ll look at their engines in a bit more detail. SpiderMonkey , the engine used by Firefox, applies the principle of generational collection, dividing allocations into young and old. It attempts to garbage collect incrementally to avoid long pauses, and runs parts of garbage collection in parallel with itself or concurrently with the main thread when possible. The V8 engine’s Orinoco garbage collector , has three generations: nursery, young, and old, and claims (as of 2019) to be a “mostly parallel and concurrent collector with incremental fallback.” V8 also brags about interweaving garbage collection into the idle time between drawing frames when possible, minimizing the time spent forcing JavaScript execution to pause. Based only on these descriptions, V8’s garbage collector seems a bit more advanced, perhaps because V8 used by Chromium-based browsers in addition to Node.js and thus has more support. However, they seem to have independently converged to similar architectures. The serious demands to provide a smooth user experience means that browser-based garbage collectors must be efficient and eliminate as much overhead as possible, because, as the Node guide to tracing garbage collection neatly summarizes, “ when GC is running, your code is not. ” I admit I’ve rather taken memory management for granted, since most of the languages I’ve studied have garbage collectors. I’ve been fascinated by Rust for years but haven’t managed to wrap my head around its ownership and borrowing rules. (Maybe this is the time it will finally click for me.) But if I struggle with memory management when the compiler itself is looking out for me, I’m not sure how I’d fare in a manual memory management scheme without guardrails. So for now, I’m very grateful to garbage collectors everywhere for making my life easier. The Memory Management Reference was invaluable while researching this blog post, in addition to many other engine- and language-specific references (linked throughout the text). Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse eachampagne Follow Joined Sep 5, 2025 More from eachampagne Parallelization # beginners # performance # programming # computerscience 💎 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://dev.to/help/fun-stuff#Caption-This | Fun Stuff - DEV Help - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close DEV Help The latest help documentation, tips and tricks from the DEV Community. Help > Fun Stuff Fun Stuff In this article Sloan: The DEV Mascot Caption This!, Meme Monday & More! Caption This! Meme Monday Music Monday Explore for extra enjoyment! Sloan: The DEV Mascot Why is Sloan the Sloth the official DEV Moderator, you ask? Sloths might not seem like your typical software development assistant, but Sloan defies expectations! Here's why: Moderates and Posts Content: Sloan actively moderates and posts content on DEV, ensuring a vibrant and welcoming community. Welcomes New Members: Sloan greets and welcomes new members to the DEV community in our Weekly Welcome thread, fostering a sense of belonging. Answers Your Questions: Have a question you'd like to ask anonymously? Sloan's got you covered! Submit your question to Sloan's Inbox, and they'll post it on your behalf. Visit Sloan's Inbox Follow Sloan! Caption This!, Meme Monday & More! Caption This! Every week, we host a "Caption This" challenge! We share a mysterious picture without context, and it's your chance to work your captioning magic and bring it to life. Unleash your creativity and craft the perfect caption for these quirky images! Meme Monday Meme Monday is our weekly thread where you can join in the laughter by sharing your favorite developer memes. Each week, we select the best one to kick off the next week as the post image, sparking another round of fun and creativity. Music Monday Share what music you're listening to each week on the Music Monday thread , - check back each week for different themes and discover weird and wonderful bands and artists shared by the community! 💎 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://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fhereisnaman%2Flogical-or-vs-nullish-coalescing-operator-in-javascript-3851&title=Logical%20OR%20%28%7C%7C%29%20vs%20%0ANullish%20Coalescing%20Operator%20%28%3F%3F%29%20in%20JavaScript&summary=With%20the%20latest%20release%20of%20version%2014%2C%20the%20Nullish%20Coalescing%20Operator%20%28%3F%3F%29%20is%20now%20supported%20in%20NodeJ...&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://lab174.com/blog/202601-yaml-norway/#fnref2 | 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://transistor.fm | Host Unlimited Shows • Best Podcast Hosting for Creators • Transistor Features Customer Service Supported by real humans Podcast Hosting Host unlimited shows on one account Private Podcasts Create a private podcast for your team Distribution Easily submit your podcast everywhere Collaborate Invite team members to your podcast AI Transcription Automatically transcribe your podcast Analytics Podcast analytics software Website Builder Podcast website builder Network Website Builder A website for your podcast network Embeddable Player Custom embeddable podcast player Dynamic Ads Automatically insert ads in episodes Integrations Integrations for your podcast workflow YouTube Auto-posting Auto-post your podcast to YouTube View all Features Pricing Company Blog Read our latest podcasting articles and guides About Us Transistor's story so far Our Customers Who is using Transistor for their podcast? Reviews What people are saying about Transistor Recent Posts How to start a podcast What is a podcast RSS feed? How to promote your podcast View all Posts Sign in Start free trial Sign in Free trial Dashboard Dashboard document.body.classList.toggle('max-md:overflow-hidden', isOpen)) } }" x-model="open" class="flex md:hidden justify-end"> Toggle menu Menu Pricing Try us free for 14 days. Blog Read our latest podcasting articles and guides About Us Transistor's story so far Our Customers Who is using Transistor for their podcast? Reviews What people are saying about Transistor Features View all Customer Service Supported by real humans Podcast Hosting Host unlimited shows on one account Private Podcasts Create a private podcast for your team Distribution Easily submit your podcast everywhere span]:block [&>span]:text-yellow [&>span]:drop-shadow-sm [&>span]:shadow-navy-950"> Publish your podcast everywhere YouTube Spotify Apple Podcasts Pocket Casts Start 14-day free trial Chat with us ★★★★★ “ The best podcast hosting tool I've used ” Rating via Product Hunt View Reviews *:first-child]:mt-0 [&>*]:mb-0 space-y-4"> Podcasts on Transistor Here are just a few of the thousands of incredible shows that are hosted by Transistor... Acquired Every company has a story. Learn the playbooks that built the world’s greatest companies — and how you can apply them as a founder, operator, or investor. Learn more Deep Dive with Ali Abdaal Dr Ali Abdaal is the world’s most followed productivity expert and author of Feel-Good Productivity, the brand new book that reveals why the secret to productivity isn’t discipline, it’s joy. In his podcast, Deep Dive, Ali sits down with inspiring creators, thinkers, entrepreneurs and high performers to help listeners build lives that they love. Ali’s cheerful style, positive approach, and well-researched content have made him a trusted voice when it comes to productivity. The internet means that we have access to more knowledge and information than ever before - but it can also be overwhelming. So, Ali and his expert guests focus on simple, scientifically proven, and actionable steps you can take to make real changes in your life. Ali’s a firm believer that happiness isn’t the result of success - in fact, happiness is the key to success in the first place. Ali made this discovery while working as a doctor in a chaotic hospital ward. In the past, hard work had been the answer to every obstacle in his life. But no amount of hard work was going to combat panic and burnout. So, Ali dedicated himself to figuring out a new approach to productivity - one that focuses on enjoying the journey and working towards truly meaningful goals. Deep Dive, with its authentic and engaging conversations, will give you all the insights you need to do just that. Learn more Diggnation (rebooted) Diggnation is back! After a 15-year break, the guys are returning with all new episodes. Diggnation covers the top stories from around the internet. Kevin Rose and Alex Albrecht give you their unique, sometimes awkward, and always hilarious take on the edges of the internet. Just a couple of geeks sitting on a couch. Learn more Distribution :first-child]:mt-0 [&>*]:mb-0 space-y-4 pt-0.5"> *]:!justify-start md:!items-start items-center text-center mx-auto"> *:first-child]:mt-0 [&>*]:mb-0 space-y-4"> Publish your podcast everywhere Get your podcast on Apple Podcasts, Spotify, YouTube, Overcast, Pocket Casts, and many more! Learn about podcast distribution Private Podcasts :first-child]:mt-0 [&>*]:mb-0 space-y-4 pt-0.5"> *]:!justify-start md:!items-start items-center text-center mx-auto"> *:first-child]:mt-0 [&>*]:mb-0 space-y-4"> Create your private podcast Host a members-only podcast for your company or online community. Learn about private podcasts Podcast Hosting :first-child]:mt-0 [&>*]:mb-0 space-y-4 pt-0.5"> *]:!justify-start md:!items-start items-center text-center mx-auto"> *:first-child]:mt-0 [&>*]:mb-0 space-y-4"> Host multiple podcasts on one account We don't charge you for creating additional podcasts. Unlimited podcast hosting Website Builder :first-child]:mt-0 [&>*]:mb-0 space-y-4 pt-0.5"> *]:!justify-start md:!items-start items-center text-center mx-auto"> *:first-child]:mt-0 [&>*]:mb-0 space-y-4"> Build a website for your podcast Choose a design and we'll automatically generate a website for your show. See our website builder Analytics :first-child]:mt-0 [&>*]:mb-0 space-y-4 pt-0.5"> *]:!justify-start md:!items-start items-center text-center mx-auto"> *:first-child]:mt-0 [&>*]:mb-0 space-y-4"> View detailed podcast analytics See your average downloads per episode, popular podcast apps, number of subscribers, trends. View our podcast analytics *:first-child]:mt-0 [&>*]:mb-0 space-y-4"> Testimonials Here's what podcasters are saying about Transistor: { const itemIndex = index + 1 if (itemIndex % 2 == 0) { cols[1].append(item) } if (itemIndex % 3 == 0) { cols[2].append(item) } }) } }" > Ali Abdaal YouTuber, Podcaster, Author We’ve been recommending Transistor to everyone we know who’s interested in starting a podcast. Nathan Barry ConvertKit When people ask me which podcast host I recommend, I say: 'Transistor is 100% the way to go.' Cameron Stack Stacked Audio After testing out 20+ podcast hosting platforms and working with numerous clients setting up their hosting, Transistor.FM is the one I always recommend because of its unique features, accessibility and user interface. Michele Hansen Geocodio Transistor is a fantastic podcasting platform — it just works out of the box and includes lots of other useful things, like a professional-looking podcast website. Andy Baldacci Pod Avenue After using Transistor for just a few minutes, I decided to leave Libsyn. I can say without a doubt, Transistor is the easiest to use podcast host on the market. On Libsyn you have to go through pages of confusing options to publish a single episode; Transistor is truly a breath of fresh air. Rob Hardy Ungated Creative Transistor is the bee's knees: it's indie owned and operated, they let you host multiple podcasts/private podcasts for one price, and they have a nice simple design. AJ Vens The Confused Breakfast Transistor is an amazing platform for hosting a podcast network. Great analytics, and most importantly, might be the best customer service you will find in the podcast hosting industry space. Michael Koper Nusii I've been using Transistor for a month, and I'm impressed. By far the best podcast hosting out there! Super easy to use and has excellent customer support. It made launching my first podcast a lot easier! Dan Schoonmaker CasterKit Transistor is incredibly easy to use, is very reliable, and has the best customer service! After starting my free trial, I immediately fell in love with how easy to use their interface was. I also like that they integrate with Zapier. Bret Fisher DevOps and Docker Talk We love Transistor.fm and they never let us down; the team is awesome! Gray MacKenzie ZenPilot I'm a big fan of recording with Riverside and then hosting on Transistor. Transistor has been amazing; you'll especially appreciate the UI, and it's very affordable. Lindsay Harris Friel The Podcast Host Transistor lets you have multiple RSS feeds, whether public or private, for one price. For the majority of independent podcasters, this could be your podcasts' forever home. Winner of Best Podcast Hosting *:first-child]:mt-0 [&>*]:mb-0 space-y-4"> Pricing Try us free for 14 days. Monthly Yearly 12 months for the price of 10 when you pay yearly. All prices in USD. div]:min-w-[33.333333%]"> Starter $19 mo Start free trial Unlimited podcasts Unlimited Team members/collaborators 50 Private podcast subscribers 20K Monthly downloads *]:inline [&>svg]:-mt-[3px]"> Live customer support *]:inline [&>svg]:-mt-[3px]"> Advanced analytics *]:inline [&>svg]:-mt-[3px]"> Built-in podcast website *]:inline [&>svg]:-mt-[3px]"> Podcast network website Buy Starter Professional $49 mo Start free trial Unlimited podcasts Unlimited Team members/collaborators 500 Private podcast subscribers 100K Monthly downloads *]:inline [&>svg]:-mt-[3px]"> Live customer support *]:inline [&>svg]:-mt-[3px]"> Advanced analytics *]:inline [&>svg]:-mt-[3px]"> Built-in podcast website *]:inline [&>svg]:-mt-[3px]"> Podcast network website *]:inline [&>svg]:-mt-[3px]"> Dynamic ads (pre-roll, mid-roll, post-roll) *]:inline [&>svg]:-mt-[3px]"> Dynamic show notes *]:inline [&>svg]:-mt-[3px]"> Auto-post to YouTube Buy Professional Business $99 mo Start free trial Unlimited podcasts Unlimited Team members/collaborators 3K Private podcast subscribers 250K Monthly downloads *]:inline [&>svg]:-mt-[3px]"> Live customer support *]:inline [&>svg]:-mt-[3px]"> Advanced analytics *]:inline [&>svg]:-mt-[3px]"> Built-in podcast website *]:inline [&>svg]:-mt-[3px]"> Podcast network website *]:inline [&>svg]:-mt-[3px]"> Dynamic ads (pre-roll, mid-roll, post-roll) *]:inline [&>svg]:-mt-[3px]"> Dynamic show notes *]:inline [&>svg]:-mt-[3px]"> Auto-post to YouTube *]:inline [&>svg]:-mt-[3px]"> Remove branding Buy Business Subscription Add-ons Transcription (5 hrs per month) $ mo Transcription (20 hrs per month) $ mo Enterprise $199+ $1990+ / mo If you need more than 250,000 downloads per month, or more than 3,000 private podcast subscribers, contact us about our Enterprise plans. Contact Us :first-child]:mt-0 [&>*]:mb-0 space-y-4 pt-0.5"> *:first-child]:mt-0 [&>*]:mb-0 space-y-4"> Are you new to podcasting? Learn which microphone is best for you, and how to publish an episode on Spotify, Apple Podcasts, and YouTube. How to start a podcast Try podcasting on Transistor for free Start 14-day free trial Transistor provides podcast hosting and analytics for thousands of organizations, brands, and creatives around the world. Learn how to start a podcast → Bluesky YouTube Facebook Instagram Mastodon Company Blog About Our customers New features Podcast Support Pricing System status Help guides API docs Affiliates Podcast Solutions Hosting Analytics Distribution Private podcasting Resources Libsyn Alternative Buzzsprout Alternative Captivate Alternative Castos Alternative Simplecast Alternative bCast Alternative Tools Episode Artwork Generator Podcast Score Tool Free Podcast Intro Music Free Podcast Website Builder Vendors Directory Apple Podcasts Preview Tool Podcast Website Gallery © 2026 Transistor Inc. All rights reserved. *+*]:before:content-['|'] [&>*+*]:before:px-2 [&>*+*]:before:opacity-30 "> Privacy Terms Government Terms | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb5-1 | 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://topenddevs.com/podcasts/adventures-in-machine-learning/episodes/how-to-create-team-utils-ml-122 | How to Create Team Utils - ML 122 - Adventures in Machine Learning - 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 Adventures in Machine Learning RSS Feed Spotify Apple Podcasts YouTube Amazon Music How to Create Team Utils - ML 122 Published: July 21, 2023 Download How to Create Team Utils - ML 122 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: Ben Wilson • Michael Berk Show Notes Have you ever written code and thought, "hmm, I wonder if my teammates would use this." Well in today's episode, we show you how to go from concept to production-level code. Spoiler alert: you're going to have to write tests! Sponsors Chuck's Resume Template Developer Book Club starting Become a Top 1% Dev with a Top End Devs Membership © 2026 2022 Intentional Excellence Productions, LLC. All rights reserved. | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb1-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://www.highlight.io/customers/superpowered | How Superpowered Uses Highlight to Understand Their Product Funnel Star us on GitHub Star Migrate your Highlight account to LaunchDarkly by February 28, 2026. Learn more on our blog. Product Integrations Pricing Resources Docs Sign in Sign up All customers Customer Case Study How Superpowered Uses Highlight to Understand Their Product Funnel Understanding user behavior The main use case for Highlight at Superpowered is to understand points of friction in the user journey. Highlight gives us a high-fidelity understanding of what users are experiencing as they onboard Superpowered and use the product. By looking at a collection of individual user sessions, we can piece together a story of what is causing users to fall off in particular parts of the user journey. We’re especially interested in learning about where in the onboarding workflow we’re losing users, and why we’re losing them. Rather than reaching out to users for interviews, Highlight serves us the same intel on a silver platter, making it easy for us to recognize patterns of behavior amongst users who successfully onboard our product or not. “ Rather than reaching out to users for interviews, Highlight serves us the same intel on a silver platter, making it easy for us to recognize patterns of behavior amongst users who successfully onboard our product or not. ” Jordan Dearsley , Superpowered Understanding user issues We do the same sort of analysis for user complaints. The only difference here is that the user gives us a lead to an issue they’re experiencing in the application. With Highlight, we can quickly see what the user was doing when they ran into the issue, and this makes it dead simple to figure out a fix. “ With Highlight, we can quickly see what the user was doing when they ran into the issue, and this makes it dead simple to figure out a fix. ” Jordan Dearsley , Superpowered Designed to impress One of the things that stands out about Highlight is the beautiful and intuitive UI. I liked the product immediately and trusted the design. It’s modern and easy to use. For me, I have a filter for what kinds of services might be good or bad, based on how much work they put into their UX. With Highlight, they pass that test with flying colors. “ Highlight lets us deeply understand our user funnel and how users are using Superpowered. This helps us make the necessary product improvements to achieve our business goals. ” Jordan Dearsley , Superpowered Next Customer About the company A calendar app that *actually* keeps you on time. Founded 2020 Using Highlight since Jan 2020 Try Highlight Today Get the visibility you need Get started for free Product Pricing Sign up Features Privacy & Security Customers Session Replay Error Monitoring Logging Competitors LogRocket Hotjar Fullstory Smartlook Inspectlet Datadog Sentry Site24x7 Sprig Mouseflow Pendo Heap LogicMonitor Last9 Axiom Better Stack HyperDX Dash0 Developers Changelog Documentation Ambassadors Frameworks React Next.js Angular Gatsby.js Svelte.js Vue.js Express Golang Next.js Node.js Rails Hono Contact & Legal Terms of Service Privacy Policy Careers sales@highlight.io security@highlight.io [object Object] | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb3-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://lab174.com/blog/202601-yaml-norway/#cb3-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://x.com/bufbuild | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T08:48:04 |
https://forem.com/t/nintendoswitch/page/9 | Nintendoswitch Page 9 - 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 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: Fortnite x Power Rangers - Official Live Action Trailer Gaming News Gaming News Gaming News Follow Aug 5 '25 IGN: Fortnite x Power Rangers - Official Live Action Trailer # pcgaming # playstation # nintendoswitch # xbox Comments Add Comment 1 min read IGN: Teenage Mutant Ninja Turtles: Tactical Takedown - Official Xbox and Nintendo Switch Reveal Trailer Gaming News Gaming News Gaming News Follow Aug 5 '25 IGN: Teenage Mutant Ninja Turtles: Tactical Takedown - Official Xbox and Nintendo Switch Reveal Trailer # nintendo # xbox # nintendoswitch # pcgaming Comments Add Comment 1 min read IGN: Fortnite - Official Bad Bugs vs Power Rangers Live Action Trailer Gaming News Gaming News Gaming News Follow Aug 5 '25 IGN: Fortnite - Official Bad Bugs vs Power Rangers Live Action Trailer # pcgaming # playstation # nintendoswitch # xbox Comments Add Comment 1 min read IGN hit by layoffs as parent company Ziff Davis cuts costs Gaming News Gaming News Gaming News Follow Aug 5 '25 IGN hit by layoffs as parent company Ziff Davis cuts costs # pcgaming # xbox # playstation # nintendoswitch Comments Add Comment 1 min read IGN: Borderlands 4 - Official Rafa Customization Trailer Gaming News Gaming News Gaming News Follow Aug 4 '25 IGN: Borderlands 4 - Official Rafa Customization Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: HUNTERxHUNTER NENxIMPACT - Official Season Pass Trailer Gaming News Gaming News Gaming News Follow Aug 4 '25 IGN: HUNTERxHUNTER NENxIMPACT - Official Season Pass Trailer # gamedev # playstation # nintendoswitch # steam Comments Add Comment 1 min read IGN: Overwatch 2 x NERF - Official Gameplay Trailer Gaming News Gaming News Gaming News Follow Aug 4 '25 IGN: Overwatch 2 x NERF - Official Gameplay Trailer # pcgaming # xbox # playstation # nintendoswitch Comments Add Comment 1 min read IGN: Street Fighter 6 - Official Outfit 4 Showcase Trailer Gaming News Gaming News Gaming News Follow Aug 4 '25 IGN: Street Fighter 6 - Official Outfit 4 Showcase Trailer # pcgaming # playstation # nintendoswitch # xbox Comments Add Comment 1 min read IGN: Guilty Gear Strive - Official Lucy Character Trailer Gaming News Gaming News Gaming News Follow Aug 4 '25 IGN: Guilty Gear Strive - Official Lucy Character Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: EA Sports Madden NFL 26 - Official Live-Action Launch Trailer Gaming News Gaming News Gaming News Follow Aug 1 '25 IGN: EA Sports Madden NFL 26 - Official Live-Action Launch Trailer # xbox # playstation # nintendoswitch # pcgaming 2 reactions Comments Add Comment 1 min read IGN: Ninja Gaiden: Ragebound | The First 20 Minutes of Gameplay | 4k 60FPS Gaming News Gaming News Gaming News Follow Aug 2 '25 IGN: Ninja Gaiden: Ragebound | The First 20 Minutes of Gameplay | 4k 60FPS # pcgaming # nintendoswitch # playstation # xbox Comments Add Comment 1 min read IGN: Nintendo Raises Switch 1 Prices For First Time Ever - IGN Daily Fix Gaming News Gaming News Gaming News Follow Aug 2 '25 IGN: Nintendo Raises Switch 1 Prices For First Time Ever - IGN Daily Fix # nintendoswitch # gaming # gamedev Comments Add Comment 1 min read IGN: Borderlands 4 - Official 'Designing Rafa' Trailer Gaming News Gaming News Gaming News Follow Aug 1 '25 IGN: Borderlands 4 - Official 'Designing Rafa' Trailer # pcgaming # xbox # playstation # nintendoswitch Comments Add Comment 1 min read IGN: Shinobi: Art of Vengeance - The First 26 Minutes of Gameplay Gaming News Gaming News Gaming News Follow Aug 1 '25 IGN: Shinobi: Art of Vengeance - The First 26 Minutes of Gameplay # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: SpongeBob Squarepants: Titans of the Tide - Official Announcement Trailer | THQ Nordic Digital Showc Gaming News Gaming News Gaming News Follow Aug 1 '25 IGN: SpongeBob Squarepants: Titans of the Tide - Official Announcement Trailer | THQ Nordic Digital Showc # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Yakuza 0 Director's Cut - Official Accolade Trailer Gaming News Gaming News Gaming News Follow Aug 1 '25 IGN: Yakuza 0 Director's Cut - Official Accolade Trailer # nintendoswitch # pcgaming Comments Add Comment 1 min read IGN: Madden NFL 26 Review Gaming News Gaming News Gaming News Follow Aug 15 '25 IGN: Madden NFL 26 Review # pcgaming # playstation # xbox # nintendoswitch Comments 1 comment 1 min read IGN: Mortal Kombat: Legacy Kollection - Official Physical Edition Announcement Trailer Gaming News Gaming News Gaming News Follow Aug 1 '25 IGN: Mortal Kombat: Legacy Kollection - Official Physical Edition Announcement Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Nintendo Direct Partner Showcase July 2025: Everything Announced Gaming News Gaming News Gaming News Follow Aug 1 '25 IGN: Nintendo Direct Partner Showcase July 2025: Everything Announced # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Apex Legends - Official Nintendo Switch 2 Trailer | Nintendo Direct Partner Showcase 2025 Gaming News Gaming News Gaming News Follow Aug 1 '25 IGN: Apex Legends - Official Nintendo Switch 2 Trailer | Nintendo Direct Partner Showcase 2025 # nintendoswitch # gaming Comments Add Comment 1 min read IGN: EA Sports Madden NFL 26 - Official Nintendo Switch Trailer | Nintendo Direct Partner Showcase 2025 Gaming News Gaming News Gaming News Follow Aug 1 '25 IGN: EA Sports Madden NFL 26 - Official Nintendo Switch Trailer | Nintendo Direct Partner Showcase 2025 # nintendoswitch # pcgaming # playstation # xbox Comments Add Comment 1 min read IGN: Nicktoons & The Dice of Destiny - Official Extended Gameplay Reveal Trailer Gaming News Gaming News Gaming News Follow Jul 31 '25 IGN: Nicktoons & The Dice of Destiny - Official Extended Gameplay Reveal Trailer # gaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Hela - Official Release Window Announcement Trailer | Nintendo Direct Partner Showcase 2025 Gaming News Gaming News Gaming News Follow Jul 31 '25 IGN: Hela - Official Release Window Announcement Trailer | Nintendo Direct Partner Showcase 2025 # nintendo # nintendoswitch # playstation # xbox Comments Add Comment 1 min read IGN: Just Dance 2026 Edition - Official Reveal Trailer | Nintendo Direct Partner Showcase 2025 Gaming News Gaming News Gaming News Follow Jul 31 '25 IGN: Just Dance 2026 Edition - Official Reveal Trailer | Nintendo Direct Partner Showcase 2025 # nintendoswitch # pcgaming # playstation # xbox Comments Add Comment 1 min read IGN: NBA Bounce - Official Gameplay Reveal Trailer | Nintendo Direct Partner Showcase 2025 Gaming News Gaming News Gaming News Follow Jul 31 '25 IGN: NBA Bounce - Official Gameplay Reveal Trailer | Nintendo Direct Partner Showcase 2025 # gamedev # nintendoswitch # playstation # xbox 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://cssence.com/elsewhere/ | Elsewhere - CSSence.com @CSSence elsewhere Internal November 6, 2024 These places are my home away from home. GitHub CodePen Mastodon Bluesky Twitter/X And there are even more places. cssence.github.io cv.cssence.com code.cssence.com (under construction) Last but not least, I’ve also joined some great webrings. About this page Written by Matthias Zöchling. Last revised on November 6, 2024 . Permalink: https://cssence.com/elsewhere/ 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://cursor.com/brand | Cursor brand guidelines · 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 brand guidelines Resources to represent Cursor consistently and accurately. Download brand assets ⤓ Brand assets Logos are available in 2D (default) and 2.5D (for larger applications), in horizontal lockup (preferred), vertical lockup, or separately as cube or wordmark. App icons are available in 2.5D (default), 2D, and 3D, light and dark. Avatars are available in 2D (default) and 2.5D, light and dark, for circular or square use. Cursor logos, app icons, and avatars. Name Refer to us as Cursor. Not Cursor AI or Cursor Code. 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 brand guidelines Resources to represent Cursor consistently and accurately. Download brand assets ⤓ Brand assets Logos are available in 2D (default) and 2.5D (for larger applications), in horizontal lockup (preferred), vertical lockup, or separately as cube or wordmark. App icons are available in 2.5D (default), 2D, and 3D, light and dark. Avatars are available in 2D (default) and 2.5D, light and dark, for circular or square use. Cursor logos, app icons, and avatars. Name Refer to us as Cursor. Not Cursor AI or Cursor Code. 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://cssence.com/popular/ | Popular posts - CSSence.com Most popular The popularity contest on CSSence.com Index January 10, 2025 Why not do rankings? Here are the most read and the most controversial posts from this site; and also some of my favorites. Featured posts The day the website stood still On the intersection of progressive degradation and graceful enhancement. Essay August 28, 2021 Six levels of dark mode From HTML-only to JS-infused, and all the CSS in between. Essay April 16, 2024 Pure CSS image comparison slider Can the CSS resize property be tricked into achieving something like this? Extra May 10, 2022 Most read posts Superior range syntax One more thing about the improved viewport size media queries. Extra April 29, 2024 The JavaScript wars In one corner, we have die-hard NoScripters. And then there are “The Others”. Essay November 1, 2016 CSS-only bottom-anchored scrolling area I’ve added an additional wrapper to Kitty Giraudel’s CodePen. Extra April 5, 2024 Most controversial posts Beyond progressive web apps My personal thoughts in response to “Regressive Web Apps” by Jeremy Keith. Essay May 27, 2016 No web font, no cry I’ve turned off font loading six months ago. This is what I learned. Essay May 18, 2018 Is CSS alive? Spoiler alert: More than ever! But let me go back in time a bit. Essay January 4, 2024 About this index page Curated by Matthias Zöchling. Last revised on January 10, 2025 . Permalink: https://cssence.com/popular/ 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://anchor.fm/ajtiti/episodes/AjTiTi-48---Jak-efektywnie-programowa-e1m2jbf | AjTiTi #48 - Jak efektywnie programować? by AjTiTi AjTiTi By Dawid Chróścielski, Grzegorz Kotlarz Luźny podcast o świecie IT. Prowadzący (Dawid Chróścielski i Grzegorz Kotlarz) rozmawiają o nowinkach technologicznych, dzielą się ciekawostkami z życia programisty oraz swoim spojrzeniem na IT. Jako dodatek dorzucają kilka (mniej lub bardziej, ale raczej bardziej) suchych żartów. Listen on Spotify Available on Report content on Spotify AjTiTi #48 - Jak efektywnie programować? AjTiTi Aug 19, 2022 Share 00:00 56:57 AjTiTi #58 - Co zrobić z twoim starym... komputerem! W tym odcinku eksplorujemy interesujący temat, jak sobie poradzić z naszym starym komputerem, gdy już staje się przestarzały i niepotrzebny. Czy powinniśmy go wyrzucić, sprzedać, czy może istnieje inny sposób na wykorzystanie jego potencjału? Zapraszamy do dzielenie się Twoimi pomysłami i realizacjami na naszym Discordzie! (00:00) Beatbox + Intro. (00:26) Co tam u Dawida? Kafka conference. (03:54) Co tam u Grzegorza? Tworzeniu ADR przy pomocy AI. (06:48) Przedstawienie tematu (07:24) Najprostszy i najważniejszy pomysł. (09:38) Centrum multimedialne. (10:48) Pomysły dla gamerów. (17:20) Pomysły dla domu. (30:27) Pomysły związane z IT. (36:07) Sztuka i dekoracja. (44:44) Outro May 26, 2023 46:51 AjTiTi #57 - Subdomeny w architekturze, a aspekt bezpieczeństwa - dlaczego warto? W tym odcinku omawiamy strategiczną stronę Domain Driven Design, skupiając się na pojęciach domeny, subdomeny i bounded contextów, a także relacji między nimi. Dowiesz się, jak wprowadzenie powyższych wpływa na nasze zarządzanie mikroserwisami pod kątem bezpieczeństwa. (00:00) Intro (00:22) Co tam u Dawida? .NET Templates (04:25) Co tam u Grzegorza? Krykiet (07:29) Przedstawienie tematu (08:00) Domain Driven Design (09:07) Czym jest domena? (11:20) Co to jest subdomena? (17:52) Bounded context (21:06) Bounded context, a subdomena (24:36) Wpływ na architekturę aplikacji (27:30) Wpływ subdomen na poziom bezpieczeństwa (33:36) Outro Apr 28, 2023 35:11 AjTiTi #56 - Onboarding programistów Hej, hej! Wracamy po przerwie! Czy zdarzyło Ci się trafić do firmy i... Tak właściwie nie wiedzieć co dalej? W dzisiejszym odcinku porozmawiamy o tym jak uniknąć takich sytuacji z perspektywy kogoś, kto wprowadza nowe osoby do zespołu. Miłego słuchania! 👌 (00:00) Intro (00:27) Co u Grzegorza? Automatyzacja Terraforma (03:09) Co u Dawida? Breakdance, SigmaOS I Setapp (08:38) Przedstawienie tematu (09:10) Od czego zacząć onboarding? (11:35) Sprzęt i oprogramowanie (13:18) Dostępy (15:29) Dokumentacja (31:10) Wideo tutorial (35:42) Pierwsze zadanie (38:48) Onboarding buddy (41:35) Pierwsze code review (42:10) Feedback loop (44:53) Jakie są Twoje porady (45:25) Outro Mar 31, 2023 45:37 AjTiTi #55 - O motywacji w świecie IT "Ale mi się nie chce" - pomyślał kiedyś każdy! To nic złego, każdemu się zdarza ;) Ale jak stworzyć środowisko, w którym nam się będzie chciało? O tym (bardzo subiektywnie) w dzisiejszym odcinku! Nov 25, 2022 54:17 AjTiTi #54 - O testowaniu aplikacji Testy jednostkowe, integracyjne, end-to-end, obciążeniowe, mutacyjne... Jeny ile tego! Na czym się skupić? Jak żyć? Na ostatnie pytanie nie odpowiemy, ale o całej reszcie zagadnień usłyszysz w tym odcinku! Enjoy! Nov 11, 2022 51:10 AjTiTi #53 - Wzorce w chmurze - design and implementation Odcinek kończący serię o wzorcach w chmurze. Jako wisienkę na torcie zostawiliśmy design & implementation - czyli wzorce, które pomagają podczas projektowania mikroserwisów. Jak nie stracić wszystkich pieniędzy od inwestora na chmurę? Jak ułatwić komunikację przy używaniu wielu języków programowania w obrębie mikroserwisów? Jak zaimplementować połączenie serwisów korzystających z różnych protokołów? Jak zaplanować kompletny refactor naszego serwisu? Czemu służy gateway i jak może odciążyć nasze serwisy? Po odpowiedzi na te, jak i wiele innych pytań, zapraszamy do odcinka! Odcinek #27 o App Configuration Store: https://tiny.pl/w92hf Odcinek #23 o API Management: https://tiny.pl/w92h1 Oct 28, 2022 50:25 AjTiTi #52 - Wzorce w chmurze - data management Kolejny odcinek dookoła wzorców projektowych używanych w chmurze publicznej. Tym razem poruszamy temat danych i zarządzania nimi. Jeśli interesuje Cie: Jak zaoszczędzić czas potrzebny na pobranie danych? Dlaczego warto oddzielić odczyty danych od zapisów? Po co i w jaki sposób dzielić dane? Na co mogą przydać się eventy? Czy użycie materialized view jest dobrym pomysłem w przypadku raportów? to zapraszamy do odsłuchu. Oct 14, 2022 01:04:40 AjTiTi #51 - Wzorce w chmurze - messaging W dzisiejszym odcinku rozpoczynamy temat wzorców projektowych używanych w chmurze publicznej. Na pierwszy ogień idzie messaging, czyli: W jaki sposób przekazywać wiadomości pomiędzy serwisami, by obsłużyć asynchroniczność? Czy można przekazać duże ilości danych bez przeciążania brokera wiadomości? Czy da się sterować procesem biznesowym poprzez wiadomości? Jak zapewnić, że nasz proces na pewno się wykona? O tych, i kilku innych rzeczach, dowiesz się z 51. odcinka podcastu AjTiTi. Sep 30, 2022 01:02:38 AjTiTi #50 - Code review Code review - z pozoru nic skomplikowanego: ktoś napisał kod, a ktoś inny go przegląda. Czy jednak na pewno? W dzisiejszym odcinku rozbieramy na części proces zarówno od strony piszącego kod, jak i przeglądającego. W jaki sposób przygotować swój kod, aby review przebiegło sprawnie? Jak robić review? Na co zwrócić uwagę? A może jest sytuacja, gdy code review możemy sobie odpuścić? Zapraszamy do odsłuchu! Sep 16, 2022 01:01:43 AjTiTi #49 - Wakacje programisty Rok szkolny się rozpoczął, więc podejmujemy sentymentalną podróż w stronę wakacji. W jaki sposób programista powinien przygotować się do wakacji? Co zrobić przed? Co robić w trakcie? Jak przeżyć powrót do pracy? Czy w ogóle warto robić sobie wakacyjne przerwy? (SPOILER: zdecydowanie warto!). Piosenka Janet Jackson niszczy komputery: https://devblogs.microsoft.com/oldnewthing/20220816-00/?p=106994 Sep 02, 2022 38:12 AjTiTi #48 - Jak efektywnie programować? Inni wyrabiają się szybciej w pracy? Spędzasz godziny nad każdą małą zmianą w kodzie? W tym odcinku poruszymy kilka kwestii, które być może będą w stanie Ci pomóc! Aug 19, 2022 56:57 AjTiTi #47 - Jak oceniać pracę programisty? Tym razem o tym, w jaki sposób oceniać oraz mierzyć progres w karierze programisty. Przyglądamy się głównie dwóm frameworkom: Dropbox Engineering Career Framework oraz Engineering Ladders, a także zastanawiamy się co czyni programistę "dobrym". Dropbox Career Framework: dropbox.github.io/dbx-career-framework/ Engineering Ladders: www.engineeringladders.com/ Aug 05, 2022 45:28 AjTiTi #46 - Stack Overflow Developer Survey 2021 Zastanawiasz się jak branża IT rozwija się pod kątem demografii oraz wiodących technologii? W jaki sposób programiści czerpią wiedzę? A może co robią, gdy napotkają problem? Jeśli tak, to jesteś w idealnym miejscu. W tym odcinku podcastu przyglądamy się danym zebranym w ankiecie portalu Stack Overflow: insights.stackoverflow.com/survey/2021 Jul 22, 2022 55:17 AjTiTi #45 - Czy na pewno potrzebujesz mikroserwisów? Czy mikroserwisy wyszły już z mody? A może stały się po prostu naszą codziennością? W dzisiejszym odcinku przyglądamy się temu tematowi z perspektywy kilku lat hype'u. Jul 08, 2022 57:49 AjTiTi #44 - Narzędzia pomagające w pracy zdalnej Kontynuujemy temat pracy zdalnej. Tym razem rozmawiamy o narzędziach, które nam pomagają i ułatwiają pracę w rozproszonym zespole. Czego użyć, by zadbać o efektywność pracy, komunikację, bazę wiedzy, ogarnięcie różnych stref czasowych, czy też ducha zespołu? Po odpowiedzi na te pytania, zapraszamy do odcinka. Jun 24, 2022 43:21 AjTiTi #43 - Komunikacja w zespole rozproszonym Praca w zespole rozproszonym geograficznie to dość świeży i nie do końca zbadany obszar. W dzisiejszym odcinku uchylamy nieco rąbka tajemnicy jak my komunikujemy się z innymi i co zauważyliśmy podczas pracy z ludźmi w taki sposób. Zapraszamy również na Discorda AjTiTi, gdzie Grzegorz pokazuje jak zrobić rękami znak lamy, która mówi, aby ktoś się przymknął ;) Jun 10, 2022 01:00:39 AjTiTi #42 - Greenfield vs Legacy Dzisiaj trochę o typach projektów IT. Wyjaśniamy czym są Greenfield oraz Legacy oraz dyskutujemy czym charakteryzują się oba te rodzaje. Jakie są zalety, a jakie wady pracy nad jednym i drugim? Przy czym my osobiście wolimy pracować? Zapraszamy do odsłuchu oraz podzielenia się swoją opinią na naszym Discordzie! May 27, 2022 58:25 AjTiTi #41 - Postpandemiczne przemyślenia o pracy zdalnej Czy praca zdalna działa? Czy jest dla każdego? Czy jako programiści zyskujemy, czy też tracimy na niej? Dzisiaj o naszych przemyśleniach na temat pracy zdalnej po ponad 2 letniej praktyce. May 13, 2022 01:12:53 AjTiTi #40 - Czy AI może być ZBYT ŁATWE? Wyliczanka z Microsoft Azure Cognitive Services. Sztuczna inteligencja na wyciągnięcie ręki? Niemalże! Możesz być magiem AI dzięki Cognitive Services, jeśli tylko potrafisz korzystać z REST API :) Wpis Dawida o wyłączaniu automatycznego tłumaczenia dokumentacji Microsoftu: https://www.chroscielski.pl/turn-off-microsoft-docs-auto-translate/ Odcinek w którym Dawid mówi o użyciu Face API: #12 Vendor Lock Apr 29, 2022 01:07:44 AjTiTi #39 - Projektowanie REST API Jak często spotykałeś się z API, które zawsze odpowiada statusem 200 OK, a dopiero po przeanalizowaniu całej odpowiedzi okazuje się, że wcale nie jest tak kolorowo? Bo my... wcale nie tak rzadko. Dlatego w dzisiejszym odcinku opowiadamy o sztuce projektowania REST API. Apr 15, 2022 01:01:13 AjTiTi #38 - O integracji systemów "You can't buy integration" - z tego zdania wypłynął temat odcinka: integracja systemów. Niemalże każde oprogramowanie wymaga jakiejś integracji. Dlatego ważne aby wiedzieć, jak podejść do tego tematu w sposób efektywny i w maksymalnie bezbolesny. Artykuł na blogu Martina Fowlera: https://martinfowler.com/articles/cant-buy-integration.html Apr 01, 2022 01:05:48 AjTiTi #37 - Logowanie i monitorowanie aplikacji na przykładzie Application Insights Chcę oglądać Twoje logi, logi, logi, logi... W tym odcinku rozmawiamy o tym po co i w jaki sposób logować komunikaty oraz jak monitorować nasze aplikacje. Wszystko to podlane sosem z Application Insights. Mar 18, 2022 01:01:60 AjTiTi #36 - O roli Team Leada (2/2) Ostatnio było trochę o tym kim jest Team Lead i jaka jest jego rola. Tym razem rozmawiamy sobie w jaki sposób Team Lead może zarządzać zespołem oraz wypełniać powierzone mu zadania w sposób efektywny. Mar 04, 2022 01:05:55 AjTiTi #35 - O roli Team Leada (1/2) Kim jest Team Lead? Jaka jest jego rola w zespole? Czy każdy może nim zostać? Czy każdy powinien? Na te i kilka innych pytań postaramy się odpowiedzieć w dzisiejszym odcinku! :) Feb 18, 2022 01:01:15 AjTiTi #34 - Jak przetrwać w grupie programistów - o "problematycznych" typach osób Czy chcemy, czy nie (a mamy nadzieję, że chcemy), to w IT pracujemy w zespołach. Niestety, czasami zdarza się, że nie każdy chce z zespołem współpracować, albo nie do końca jest do tego przygotowany. W 34. odcinku podcastu AjTiTi porozmawiamy o tym, jakie "problematyczne" typy osób spotkaliśmy w naszej karierze oraz jak można sobie z nimi poradzić. Bo, jak się okazuje, będąc "problematycznym" więcej tracimy, niż nam się może wydawać... Feb 04, 2022 01:19:51 AjTiTi #33 - Korpo vs Startup vs Software House W dzisiejszym odcinku rozmawiamy o tym, czym wyróżnia się praca programistów w zależności od tego dla jakiego rodzaju firm pracują. Jak to jest być w korpo, dobrze? Pewnie nie ma tak, że to dobrze, albo że nie dobrze... A jak to wygląda, gdy pracujesz w startupie? A może software house? Czym różnią się te typy organizacji, jakie są nasze doświadczenia oraz co polecamy początkującym programistom - o tym wszystkim posłuchasz właśnie tutaj. Jan 21, 2022 01:16:25 AjTiTi #32 - Dlaczego warto zostać programistą? Ostatnio było trochę narzekania na naszą pracę, ale poza zadami, jest też wiele walet w byciu programistą! Zapraszamy do kolejnej luźnej pogawędki w tym temacie. Jan 07, 2022 01:13:37 AjTiTi #31 - Dlaczego nie warto zostać programistą! Drzwiami i oknami ludzie pchają się do IT. Zastanówmy się jednak, dlaczego nie warto zostać programistą - luźne przemyślenia po kilku latach w branży :) Dec 24, 2021 01:08:50 AjTiTi #30 - SOLIDne oprogramowanie Są pewne zasady, które nie powinny być łamane. W najnowszym odcinku podcastu AjTiTi rozmawiamy o SOLIDzie i o wpływie, jaki może on mieć na nasze oprogramowanie. Dec 10, 2021 59:55 AjTiTi #29 - Dokumentowanie projektów IT O trudnej sztuce dokumentacji technicznej projektów IT :) Nov 26, 2021 01:05:31 AjTiTi #28 - Estymowanie zadań "Ile to zajmie?", "Na kiedy będzie?", "Dlaczego tak długo?" - jako programiści musimy się mierzyć z tymi pytaniami niemal codziennie. I sztuką jest odpowiedzieć na nie z odpowiednią dokładnością. W tym odcinku rozmawiamy o tym w jaki sposób dzielić i estymować zadania, by nasze szacowania były trafione i sensowne, a praca jak najbardziej przyjemna. Nov 12, 2021 01:16:10 AjTiTi #27 - Azure App Configuration - centralizacja konfiguracji w chmurze One to rule them all - o centralizacji konfiguracji w środowiskach mikroserwisowych i serverless z perspektywy chmury Microsoft Azure. PS. Zapraszamy na Discorda: https://www.ajttii.pl Oct 29, 2021 01:00:60 AjTiTi #26 - Błędy początkujących programistów #2 Z racji, że na początku kariery można popełnić wiele błędów, to ostatnio tak się rozgadaliśmy, że z naszej dyskusji powstały dwa odcinki ;) Zapraszamy do kontynuacji rozmowy o błędach, jakie, z naszej perspektywy, popełniają początkujący programiści. Oct 15, 2021 51:23 AjTiTi #25 - Błędy początkujących programistów #1 Każdy z nas kiedyś zaczynał... I większość prawdopodobnie popełniła na początku swojej przygody kilka mniejszych, bądź większych błędów. Dzisiaj o tym, jakie błędy, z naszej perspektywy, popełniają początkujący programiści. Oct 01, 2021 45:12 AjTiTi #24 - Korpomowa w IT ASAPy, f***upy i ogólnie takie takie - czyli nasze przemyślenia i przygody odnośnie korpomowy :) Sep 17, 2021 01:06:59 AjTiTi #23 - Azure API Management API, wszędzie API… Tyle z nim zachodu, by je zrobić i udostępnić klientom w użyteczny i bezpieczny sposób. Tylko, że nie - dzisiaj przedstawiamy usługę Azure API Management, która wspomaga programistów w procesach tworzenia, zabezpieczania, wydawania i dokumentowania API. Sep 03, 2021 58:40 AjTiTi #22 - Wzorce projektowe - behawioralne Kontynuujemy wątek wzorców projektowych (tym razem wzorce behawioralne) oraz podsumowujemy temat. Aug 20, 2021 01:09:08 AjTiTi #21 - Wzorce projektowe - kreacyjne i strukturalne Tym razem poruszamy temat bardzo popularny, ale także niezwykle ważny dla programisty - wzorce projektowe. W tym odcinku przybliżamy wzorce kreacyjne oraz strukturalne. Aug 06, 2021 01:01:02 AjTiTi #20 - Infrastructure as a Code - ARM Templates Jakie parametry do tego template’u Wariacie? Trzymaj infrę w repo to nie zginiesz. Pozdro i z fartem. Jul 16, 2021 57:41 AjTiTi #19 - Hackathony, GameJamy i ogólnie takie, takie… Dzisiejszy odcinek poświęciliśmy nostalgicznym wyprawom we wspomnienia z eventów programistycznych. Zapraszamy do odsłuchu :) Post Grzegorza o błędzie z datami: https://grzegorz.thehonest.dev/godates Jul 02, 2021 53:33 AjTiTi #18 - Azure DevOps Co to jest Azure DevOps? Jak może pomóc Ci w projekcie? Dlaczego warto skorzystać akurat z niego? Jak wejść na naszego Discorda? O wszystkim tym w dzisiejszym odcinku! :) Jun 18, 2021 01:02:13 AjTiTi #17 - Jak wytłumaczyć na czym polega praca programisty? Rodzice znów pytają co Ty tak właściwie robisz? Znajomi myślą, że grasz w gry i dostajesz za to pieniądze? Nie potrafisz wytłumaczyć innym na czym polega Twoja praca? W dzisiejszym odcinku omawiamy jak my radzimy sobie z takimi pytaniami :) Jun 04, 2021 56:36 AjTiTi #16 - Dług technologiczny Każdy dług powinien zostać zaciągnięty z głową. Dlatego ważnym jest, aby mieć świadomość tego czym jest dług technologiczny i w jaki sposób podejść do jego spłaty. Tego dowiesz się z 16ego odcinka podcastu AjTiTi. May 21, 2021 52:43 AjTiTi #15 - Code smells #2 A co to tak brzydko pachnie w naszym kodzie? Kontynuujemy temat code smells: Object-Orientation Abusers, Change Preventers, Dispensables oraz Couplers. May 07, 2021 01:02:22 AjTiTi #14 - Code smells #1 A co to tak brzydko pachnie w naszym kodzie? Dzisiaj porozmawiamy sobie czym są code smelle i omówimy ich dwie kategorie: obfuscators oraz bloaters. Apr 23, 2021 49:02 AjTiTi #13 - Microsoft Azure Durable Functions Słów kilka o tym jak nie wymyślać serverlessowego koła na nowo, czyli o rozszerzeniu Durable Functions :) Apr 09, 2021 01:05:32 AjTiTi #12 - Vendor lock - czy jest się czego bać? Tematem przewodnim najnowszego odcinka jest vendor lock. Co to takiego? Czy należy się go bać? W jakich okolicznościach może nam przeszkadzać? Jak sobie z nim poradzić? Po odpowiedzi na te pytania zapraszamy do odsłuchu ;) Jeśli masz jakieś pytania bądź wnioski w tym temacie (lub też innym z obszaru IT) - zapraszamy na naszego Discorda. Mar 26, 2021 01:02:17 AjTiTi #11 - Azure Functions Czym jest Azure Functions, App Service, App Service Plan, Application Insights, Azure Durable Functions - wszystkiego tego dowiesz się w tym odcinku! PS. Zapraszamy na naszego discorda! ;) Mar 12, 2021 01:08:04 AjTiTi #10 - Pierwsza praca w IT - co wiedzieć? Kolejny piątek, kolejny odcinek. A w nim - co trzeba umieć, aby dostać pierwszą pracę w IT? Jakie umiejętności są niezbędne dla Junior Developera? Zapoznajcie się z naszymi opiniami oraz historiami, no i nie zapomnijcie opisać swoich przemyśleń na naszym Discordzie :) Feb 26, 2021 01:05:40 AjTiTi #9 - Wprowadzenie do serverless Odcinek 9 jest odcinkiem wprowadzającym do świata serverless. Zapraszamy do odsłuchu :) Feb 12, 2021 45:25 Show more episodes © 2026 Spotify AB Careers Legal Help App Store Google Play | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb6-1 | 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://cssence.com/threads/ | Threads - CSSence.com Threads The opposite of Articles. Index January 2, 2026 Whenever I feel the need to constrain my thoughts to a certain number of characters, it ends up here: Random notes and bookmarks for my future self. Latest posts Safeguarded hyphenation Tweaking things with hyphenate-limit-chars is (almost) possible. Link January 2, 2026 Style Queries FTW! Warning: Limited availability across major browsers. Note January 1, 2026 MathML Manuel Sánchez created and contributed to an Advent Calendar. Link December 21, 2025 Favorite websites Sites I visit whenever I need inspiration. Note December 4, 2025 Baseline baseline Roma Komarov proposed a potential future for baseline alignment. Link November 9, 2025 What’s my screen resolution? Kilian Valkhof asks if a better test site would be welcome. Spoiler: Yes. Note October 22, 2025 What’s the size of the box? Should we circle back to the original box model? Link October 22, 2025 Save space for scrollbars Meet scrollbar gutter, as seen in CSS Overflow Module Level 3. Link October 12, 2025 Blogging hiatus My family came first this summer. Note October 8, 2025 Full-width backgrounds The ancient border-image property has a trick up its sleeve. Link July 30, 2025 On typing umlauts Apple brought the iOS way to MacOS, what about Linux and Windows? Link June 30, 2025 Whimsica11y and RSS Joy Great article by Sara Joy, and that pet project of hers is great too. Link June 17, 2025 The list above contains only the twelve most recent entries. In this section alone, there are 179 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 2, 2026 . Permalink: https://cssence.com/threads/ 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/about/matt/ | About Matthias Zöchling - CSSence.com About Matthias Zöchling CSS enthusiast (@CSSence) Internal March 21, 2024 Career I’m a front-end web craftsman. I started when Netscape was in its prime; my first website went online in 1998. When Microsoft added Xml Http Request to Internet Explorer, I began creating applications for browsers, at a time when “web apps” were nothing but a concept on paper, years before the term “ AJAX ” was coined. Since then I’ve been working on web-related projects spare-, part- or full-time. In addition to prototyping in the browser, I focus on creating responsive sites and making them accessible for all kinds of humans, devices and connection speeds. Thanks to fewer browser inconsistences, I enjoy it more than ever. This photo, taken in 2012, is part of my avatar image, where it is placed behind the CSSence logo. Private life I like creating all kinds of stuff. Online, that’s a given. Describing my offline hobby, I go by Interior Design Upcycler . I like to run. I used to travel, which lately clashes with my increased interest in degrowth. But the most interesting journey is fatherhood. And marriage. When I got married to my lovely wife I took her last name, so if you encounter (old) stuff about me online where my birth name Beitl has been used for attribution, that’s why. About this page Written by Matthias Zöchling. Last revised on March 21, 2024 . Permalink: https://cssence.com/about/matt/ 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://www.ycombinator.com/apply | Apply to Y Combinator | Y Combinator About What Happens at YC? Apply YC Interview Guide FAQ People YC Blog Companies Startup Directory Founder Directory Launch YC Startup Jobs All Jobs ◦ Engineering ◦ Operations ◦ Marketing ◦ Sales Internships Startup Job Guide YC Startup Jobs Blog Find a Co-Founder Library SAFE Resources Startup School Newsletter Requests for Startups For Investors Verify Founders Hacker News Bookface Open main menu Apply for X2026 batch. Apply Apply to Y Combinator Spring 2026 Batch Apply to Spring 2026 Not ready to apply this batch? Sign up for reminders to apply next batch. Y Combinator is accepting applications for the Spring 2026 Batch funding cycle. The batch will take place from April to June in San Francisco . You can also apply to future batches now via Early Decision. The deadline to apply on-time is February 9 at 8pm PT; if you apply before the deadline, you will get a decision by March 13 . If you apply after the deadline, we will still consider the application but can't promise exactly when we'll get back to you. About applying to YC If you want to apply, please submit your application online. People who applied before the regular deadline will hear back by March 13 . If you apply after the deadline, we'll still consider the application but can't promise exactly when we'll get back to you. We encourage you to submit your application as soon as you’re ready to apply. If your application is promising, we will invite you to interview with us. Most interviews will be held by video conference in February and March We typically make decisions the same day as your interview, and we give everyone who interviews detailed feedback on our decision. We invest in companies as soon as they are accepted; we do not wait for the batch to start. About the batch The batch will take place in-person at YC's campus in San Francisco. It starts with a 3-day, in-person kick-off and features regular meetups in San Francisco. For more information, please read our FAQs . During the batch, we invite eminent people from the startup world to speak. The founders of OpenAI, Airbnb, Stripe, and Doordash often come back to tell the inside story of what happened in the early days of their startups. Every company works with a dedicated YC General Partner , who gets to know them well and can help with a wide range of issues. Every YC general partner is a successful startup founder themselves, has advised hundreds of startups, and works closely with a small group of startups they personally hand-select every batch. YC companies are in a direct slack channel with their partner and meet weekly during the batch. Similar to how many universities have a house model, each YC batch is actually several small, autonomous groups of companies. You go through YC as part of this small group of companies, have dinner with them each week, and build both personal and professional relationships. Many founders build lifelong friendships with the founders in their group. During and after the batch, we introduce founders to people who can help with any challenge. Often, this means founders of other YC companies . Today, The YC alumni community is one of the most powerful communities in the world, and its members have a strong commitment to help one another. Towards the end of the batch, we help companies raise additional funds by introducing them to YC’s extensive network of investors. YC doesn't end after 3 months . We continue to help founders for the life of their company, and beyond — and so does the YC alumni community. Read more here . If you have other questions, reach out via email . Related About Y Combinator Founder Ethics Frequently Asked Questions Requests for Startups Apply to Spring 2026 Footer Y Combinator Programs YC Program Startup School Work at a Startup Co-Founder Matching Company YC Blog Contact Press People Careers Privacy Policy Notice at Collection Security Terms of Use Resources Startup Directory Startup Library Investors SAFE Hacker News Launch YC YC Deals Make something people want. Apply Twitter Twitter Facebook Facebook Instagram Instagram LinkedIn LinkedIn Youtube YouTube © 2026 Y Combinator | 2026-01-13T08:48:04 |
https://www.linkedin.com/in/acunniffe/ | Aidan Cunniffe - Atlassian | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now Sign in to view Aidan’s full profile Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Aidan Cunniffe Sign in to view Aidan’s full profile Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Brooklyn, New York, United States Contact Info Sign in to view Aidan’s full profile Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . 3K followers 500+ connections See your mutual connections View mutual connections with Aidan Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Join to view profile Message Sign in to view Aidan’s full profile Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Atlassian Syracuse University - Martin J. Whitman School of Management Blog Report this profile Activity Follow Sign in to view Aidan’s full profile Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Yesterday Sentry's co-founder David Cramer sent out this internal memo to the whole team about AI usage at the company 👀 Yesterday Sentry's co-founder David Cramer sent out this internal memo to the whole team about AI usage at the company 👀 Liked by Aidan Cunniffe Congratulations to Co-founders Danny Sheridan, Deep Singhvi, and the entire Fern team on being acquired by Postman! When Bessemer led Fern's $9M… Congratulations to Co-founders Danny Sheridan, Deep Singhvi, and the entire Fern team on being acquired by Postman! When Bessemer led Fern's $9M… Liked by Aidan Cunniffe I’m excited to share that Fern has joined Postman. Four years ago, Deep Singhvi, Zach Kirsch, and I left our roles at Palantir and Amazon to start a… I’m excited to share that Fern has joined Postman. Four years ago, Deep Singhvi, Zach Kirsch, and I left our roles at Palantir and Amazon to start a… Liked by Aidan Cunniffe Join now to see all activity Experience & Education *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> Atlassian *]:mb-0 not-first-middot leading-[1.75]"> ********* ** ******* *** *** ********* ***** *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> ***** *]:mb-0 not-first-middot leading-[1.75]"> ******* * *** *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> ********** *]:mb-0 not-first-middot leading-[1.75]"> ********** * ***** ** ********* *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> ******** ********** * ****** ** ******* ****** ** ********** *]:mb-0 not-first-middot leading-[1.75]"> ******** ** ******* ******* ********* ************ ******************************** ******* undefined *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> 2012 - 2014 *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> ***** ****** **** ****** *]:mb-0">- *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> 2009 - 2012 View Aidan’s full experience See their title, tenure and more. Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Volunteer Experience *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> Board of Directors, Director of Technology, Founding Member *]:mb-0 not-first-middot leading-[1.75]"> Friends of GV Track *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> Mar 2012 - Present 13 years 11 months Education I helped found a non-profit to support the running teams at my high school that I myself was a part of. Using some algorithms and crawlers I wrote to help build our database of contacts we met our ambitious fundraising goals. I help run campaigns, maintain the website and continue to grow our list of contacts using technology. Honors & Awards *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> 1st Place Raymond von Dran Idea Award for Information Technology *]:mb-0 not-first-middot leading-[1.75]"> Syracuse University Idea *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> Apr 2013 *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> State Finals Qualifier *]:mb-0 not-first-middot leading-[1.75]"> New York State Business Plan Competition *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> Apr 2013 Recommendations received Tony Kershaw “I had the pleasure of working with Aidan as he developed a few startup companies while at SU. I've seen him learn and grow as a business professional, startup founder, and young man. He is a gifted developer with a good head on his shoulders. He has never been afraid to ask for help either. His successes to date prove he's talented and he's always acknowledged the people who have helped him get to where he is. He's a dedicated young professional who is destined for great things. I look forward to continuing to support him in his future endeavors however I can.” 1 person has recommended Aidan Join now to view More activity by Aidan I've always believed that code holds 2 purposes... 1. Tell the computer what to do 2. Tell the next developer (sometimes yourself) what you were… I've always believed that code holds 2 purposes... 1. Tell the computer what to do 2. Tell the next developer (sometimes yourself) what you were… Liked by Aidan Cunniffe Coding Agents are making it easier to ship our backlogs and codebases are growing faster than ever. Often I find myself looking at some code I've… Coding Agents are making it easier to ship our backlogs and codebases are growing faster than ever. Often I find myself looking at some code I've… Shared by Aidan Cunniffe I'm Michael Carter-Williams, 2014 NBA Rookie of the Year. I played 9 seasons in the league and now I'm building here. Since basketball, I've been… I'm Michael Carter-Williams, 2014 NBA Rookie of the Year. I played 9 seasons in the league and now I'm building here. Since basketball, I've been… Liked by Aidan Cunniffe New Year - New Adventure! I’m joining the #DevRel team at Tessl! If we’ve bumped into each other at conferences over the last year, you’ve probably… New Year - New Adventure! I’m joining the #DevRel team at Tessl! If we’ve bumped into each other at conferences over the last year, you’ve probably… Liked by Aidan Cunniffe Thank you all! Going to be an epic 2026 as agentic workflows move beyond just coding to deliver more value in the enterprise...but lots to build 🏗️… Thank you all! Going to be an epic 2026 as agentic workflows move beyond just coding to deliver more value in the enterprise...but lots to build 🏗️… Liked by Aidan Cunniffe As our AI agents at Growthspace started touching more internal tools, we hit an uncomfortable question: How do you move fast without leaking… As our AI agents at Growthspace started touching more internal tools, we hit an uncomfortable question: How do you move fast without leaking… Liked by Aidan Cunniffe The inventor of Claude Code admits he didn’t write a single line of code in an IDE over the past month. Everything was written by Claude Code. We… The inventor of Claude Code admits he didn’t write a single line of code in an IDE over the past month. Everything was written by Claude Code. We… Liked by Aidan Cunniffe One of the greatest enterprise qualifying questions I've ever found: "what is the codename for this [project|initiative]?" When we were closing… One of the greatest enterprise qualifying questions I've ever found: "what is the codename for this [project|initiative]?" When we were closing… Posted by Aidan Cunniffe In 2025, we doubled down on what we do best: relationships and change. - entered the year grounding decisions in operating principles; knowing… In 2025, we doubled down on what we do best: relationships and change. - entered the year grounding decisions in operating principles; knowing… Liked by Aidan Cunniffe View Aidan’s full profile See who you know in common Get introduced Contact Aidan directly Join to view full profile Other similar profiles Bruce Bennett Bruce Bennett Tampa, FL Connect Dan Rodrigues Dan Rodrigues Newport Beach, CA Connect James Garvey James Garvey Austin, TX Connect Brant Wadsworth Brant Wadsworth Greater Phoenix Area Connect Jason Westland Jason Westland Sunshine Coast, QLD Connect Greg Segall Greg Segall Greater Boston Connect Micah Winkelspecht Micah Winkelspecht United States Connect Mae Karwowski Mae Karwowski New York, NY Connect Liran Kotzer Liran Kotzer Tel Aviv-Yafo Connect John Lima John Lima Pleasanton, CA Connect Explore top content on LinkedIn Find curated posts and insights for relevant topics all in one place. View top content Add new skills with these courses 1h 41m Azure DevOps: Continuous Delivery with YAML Pipelines 2h 41m AWS Automation and Optimization 1h 18m Learning GitHub Advanced Security for Azure DevOps See all courses LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (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)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Browse anonymously, connect when ready Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:04 |
https://music.forem.com#main-content | 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 Welcome to Music Forem — part of the Forem network! We're a place dedicated to discussing all things music - composing, producing, performing, and all the fun and not-fun things in-between. Create account Log in Home About Contact Other Code of Conduct Privacy Policy Terms of Use Twitter Facebook Github Instagram Twitch Mastodon Popular Tags #indie #indie #production #livestreaming #streaming #digital #hiphop #diy #distribution #theory #rnb #classical #ambientmusic #ambientmusic #alternative #soul #synthpop #trance #electronic #drumandbass #techno #blues #jazz #house #disco #dubstep #funk #ambient #pop #country Music Forem From composing and gigging to gear, hot music takes, and everything in between. 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. Posts Relevant Latest Top Music Monday (Happy New Year!!! 🥳) Mikey Dorje Mikey Dorje Mikey Dorje Follow for Music Forem Team Jan 5 Music Monday (Happy New Year!!! 🥳) # musicmonday # playlist # community # newmusic 17 reactions Comments 6 comments 1 min read Music Monday - Winter Music ❄️ Mikey Dorje Mikey Dorje Mikey Dorje Follow for Music Forem Team Jan 12 Music Monday - Winter Music ❄️ # musicmonday # community # playlist # newmusic 12 reactions Comments 3 comments 1 min read How do I discover new music that actually fits my taste? Luca Luca Luca Follow Jan 8 How do I discover new music that actually fits my taste? # newmusic2026 # risingartists # rnb # streaming 1 reaction Comments Add Comment 3 min read Why do some songs only make sense after you’ve lived more? Luca Luca Luca Follow Jan 12 Why do some songs only make sense after you’ve lived more? # musicdiscovery # alternativernb # emotionalmusic # newmusic 1 reaction Comments Add Comment 2 min read 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 COLORS: Silvana Estrada - Un Rayo De Luz | A COLORS SHOW Music YouTube Music YouTube Music YouTube Follow Dec 8 '25 COLORS: Silvana Estrada - Un Rayo De Luz | A COLORS SHOW # indie # livestreaming # streaming # digital Comments Add Comment 1 min read NPR Music: Annie DiRusso: Tiny Desk Concert Music YouTube Music YouTube Music YouTube Follow Dec 8 '25 NPR Music: Annie DiRusso: Tiny Desk Concert # indie # livestreaming # streaming 3 reactions Comments Add Comment 1 min read Music Monday (Community Playlist!) Mikey Dorje Mikey Dorje Mikey Dorje Follow for Music Forem Team Dec 29 '25 Music Monday (Community Playlist!) # musicmonday # playlist # community # newmusic 16 reactions Comments 3 comments 1 min read Music Monday (Seed the playlist) Mikey Dorje Mikey Dorje Mikey Dorje Follow for Music Forem Team Dec 22 '25 Music Monday (Seed the playlist) # discuss # musicmonday # playlist # newmusic 15 reactions Comments 9 comments 1 min read Andrew Huang: If you're not using envelope followers, you're missing out Music YouTube Music YouTube Music YouTube Follow Nov 30 '25 Andrew Huang: If you're not using envelope followers, you're missing out # production # digital # diy Comments Add Comment 1 min read COLORS: SSIO - Ich Bin Raus | A COLORS SHOW Music YouTube Music YouTube Music YouTube Follow Nov 29 '25 COLORS: SSIO - Ich Bin Raus | A COLORS SHOW # hiphop # livestreaming # streaming # digital Comments Add Comment 1 min read KEXP: Jembaa Groove - Dabia / Namo (Live on KEXP) Music YouTube Music YouTube Music YouTube Follow Nov 29 '25 KEXP: Jembaa Groove - Dabia / Namo (Live on KEXP) # indie # livestreaming # production # streaming Comments Add Comment 1 min read COLORS: Gabriel Jacoby - be careful | A COLORS SHOW Music YouTube Music YouTube Music YouTube Follow Nov 28 '25 COLORS: Gabriel Jacoby - be careful | A COLORS SHOW # indie # livestreaming # streaming # digital Comments Add Comment 1 min read NPR Music: SEVENTEEN: Tiny Desk Concert Music YouTube Music YouTube Music YouTube Follow Nov 28 '25 NPR Music: SEVENTEEN: Tiny Desk Concert # livestreaming # hiphop # production Comments Add Comment 1 min read Mix with the Masters: Mixing Night with Ken Lewis - 100TH SHOW - 12/3/25 Music YouTube Music YouTube Music YouTube Follow Nov 27 '25 Mix with the Masters: Mixing Night with Ken Lewis - 100TH SHOW - 12/3/25 # livestreaming # production Comments Add Comment 1 min read Andrew Huang: Don't sleep on envelope followers! 8 creative uses Music YouTube Music YouTube Music YouTube Follow Nov 28 '25 Andrew Huang: Don't sleep on envelope followers! 8 creative uses # production # diy # digital 4 reactions Comments 1 comment 1 min read KEXP: Jembaa Groove - Full Performance (Live on KEXP) Music YouTube Music YouTube Music YouTube Follow Nov 28 '25 KEXP: Jembaa Groove - Full Performance (Live on KEXP) # livestreaming # production Comments Add Comment 1 min read KEXP: Jembaa Groove - Dabia / Namo (Live on KEXP) Music YouTube Music YouTube Music YouTube Follow Nov 28 '25 KEXP: Jembaa Groove - Dabia / Namo (Live on KEXP) # livestreaming # production # indie 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 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://lab174.com/blog/202601-yaml-norway/#cb1-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://forem.com/t/nintendoswitch/page/3 | Nintendoswitch Page 3 - 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: Hollow Knight: Silksong Boss Fight - Last Judge (Blasted Steps) Gaming News Gaming News Gaming News Follow Sep 13 '25 IGN: Hollow Knight: Silksong Boss Fight - Last Judge (Blasted Steps) # pcgaming # indie # nintendo # nintendoswitch Comments Add Comment 1 min read GameSpot: Nintendo Isn’t Showing All Its Cards With The Switch 2 (For The Better) Gaming News Gaming News Gaming News Follow Sep 13 '25 GameSpot: Nintendo Isn’t Showing All Its Cards With The Switch 2 (For The Better) # nintendo # nintendoswitch # pcgaming Comments Add Comment 1 min read IGN: Metroid Prime 4, Hades 2 & More Release Dates From September 2025 Nintendo Direct - IGN Daily Fix Gaming News Gaming News Gaming News Follow Sep 13 '25 IGN: Metroid Prime 4, Hades 2 & More Release Dates From September 2025 Nintendo Direct - IGN Daily Fix # nintendo # nintendoswitch # retrogaming # gaming Comments Add Comment 1 min read IGN: Stardew Valley - Official Nintendo Switch 2 Edition Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Stardew Valley - Official Nintendo Switch 2 Edition Trailer | Nintendo Direct # nintendo # nintendoswitch # indie # gaming Comments Add Comment 1 min read GameSpot: Donkey Kong Bananza - DK Island and Emerald Rush Launch Trailer Gaming News Gaming News Gaming News Follow Sep 12 '25 GameSpot: Donkey Kong Bananza - DK Island and Emerald Rush Launch Trailer # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Hades 2 - Official Release Date Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Hades 2 - Official Release Date Trailer | Nintendo Direct # gaming # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Persona 3: Reload - Official Nintendo Switch 2 Demo Trailer Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Persona 3: Reload - Official Nintendo Switch 2 Demo Trailer # nintendo # nintendoswitch # retrogaming Comments Add Comment 1 min read IGN: Mortal Kombat: Legacy Kollection - Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Mortal Kombat: Legacy Kollection - Trailer | Nintendo Direct # nintendo # nintendoswitch # gaming Comments Add Comment 1 min read IGN: Maybe Nintendo Switch 2 Can Keep Up with PS5/Xbox After All - Next-Gen Console Watch Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Maybe Nintendo Switch 2 Can Keep Up with PS5/Xbox After All - Next-Gen Console Watch # nintendoswitch # gamedev # pcgaming # playstation Comments Add Comment 1 min read IGN: Pokemon Legends: Z-A - Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Pokemon Legends: Z-A - Trailer | Nintendo Direct # nintendo # nintendoswitch # gaming Comments Add Comment 1 min read IGN: Virtual Boy: Nintendo Classics - Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Virtual Boy: Nintendo Classics - Trailer | Nintendo Direct # nintendo # nintendoswitch # retrogaming Comments Add Comment 1 min read IGN: Super Mario Galaxy + Super Mario Galaxy - Nintendo Switch Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Super Mario Galaxy + Super Mario Galaxy - Nintendo Switch Trailer | Nintendo Direct # nintendo # nintendoswitch # retrogaming # gaming Comments Add Comment 1 min read IGN: Donkey Kong Bananza: DK Island The First 30 Minutes Gaming News Gaming News Gaming News Follow Sep 13 '25 IGN: Donkey Kong Bananza: DK Island The First 30 Minutes # nintendo # nintendoswitch # retrogaming Comments Add Comment 1 min read IGN: Borderlands 4 - Official 'Claptrap Needs Friends' Trailer Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Borderlands 4 - Official 'Claptrap Needs Friends' Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: One Piece: Pirate Warriors 4 - Official Next Gen Update Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: One Piece: Pirate Warriors 4 - Official Next Gen Update Trailer | Nintendo Direct # nintendo # nintendoswitch # playstation # xbox Comments Add Comment 1 min read IGN: Human Fall Flat - Official Nintendo Switch 2 Reveal Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Human Fall Flat - Official Nintendo Switch 2 Reveal Trailer | Nintendo Direct # nintendo # nintendoswitch # indie # gaming Comments Add Comment 1 min read IGN: Nintendo Switch 2 Enhanced Games Montage - EA FC 26, Persona 3 Reload, and More! | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Nintendo Switch 2 Enhanced Games Montage - EA FC 26, Persona 3 Reload, and More! | Nintendo Direct # nintendo # nintendoswitch # pcgaming Comments Add Comment 1 min read IGN: Everything Announced at the Nintendo Direct (September 2025) Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Everything Announced at the Nintendo Direct (September 2025) # nintendo # nintendoswitch # gaming Comments Add Comment 1 min read GameSpot: Every Announcement from the Nintendo Direct September 2025 Gaming News Gaming News Gaming News Follow Sep 12 '25 GameSpot: Every Announcement from the Nintendo Direct September 2025 # nintendo # nintendoswitch # retrogaming Comments Add Comment 1 min read GameSpot: Fire Emblem: Fortune’s Weave - Official Announcement Trailer Gaming News Gaming News Gaming News Follow Sep 12 '25 GameSpot: Fire Emblem: Fortune’s Weave - Official Announcement Trailer # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Hollow Knight: Silksong Boss Fight - Sister Splinter (Shellwood) Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Hollow Knight: Silksong Boss Fight - Sister Splinter (Shellwood) # pcgaming # indie # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Kirby Air Riders Amiibo - Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: Kirby Air Riders Amiibo - Trailer | Nintendo Direct # nintendo # nintendoswitch # pcgaming Comments Add Comment 1 min read GameSpot: Tomodachi Life Living The Dream - Official Release Window Reveal Gameplay Trailer Gaming News Gaming News Gaming News Follow Sep 12 '25 GameSpot: Tomodachi Life Living The Dream - Official Release Window Reveal Gameplay Trailer # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: PowerWash Simulator 2 - Official Nintendo Switch 2 Trailer | Nintendo Direct Gaming News Gaming News Gaming News Follow Sep 12 '25 IGN: PowerWash Simulator 2 - Official Nintendo Switch 2 Trailer | Nintendo Direct # nintendo # nintendoswitch # pcgaming Comments Add Comment 1 min read 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 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://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fdev.to%2Fneisha1618%2Fcallbacks-vs-promises-4mi1&title=Callbacks%20vs%20Promises&summary=The%20Goal%20%20The%20goal%20is%20to%20achieve%20asynchronous%20code.%20Async%20code%20allows%20multiple%20things%20to%20happen%20at%20th...&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://share.transistor.fm/s/0883be0d/transcript | APIs You Won't Hate | Note-taking tools for devs, with Drew White from Stashpad APIs You Won't Hate 40 ? 30 : 10)" @keyup.document.left="seekBySeconds(-10)" @keyup.document.m="toggleMute" @keyup.document.s="toggleSpeed" @play="play(false, true)" @loadedmetadata="handleLoadedMetadata" @pause="pause(true)" preload="none" @timejump.window="seekToSeconds($event.detail.timestamp); shareTimeFormatted = formatTime($event.detail.timestamp)" > Trailer Bonus 10 40 ? 30 : 10)" class="seek-seconds-button" > 40 ? 30 : 10"> Subscribe Share More Info Download More episodes Subscribe newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyFeedUrl()" class="form-input-group" > Copied to clipboard Apple Podcasts Spotify Pocket Casts Overcast Castro YouTube Goodpods Goodpods Metacast Amazon Music Pandora CastBox Anghami Anghami Fountain JioSaavn Gaana iHeartRadio TuneIn TuneIn Player FM SoundCloud SoundCloud Deezer Podcast Addict Share newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyShareUrl()" class="form-input-group" > Share Copied to clipboard newValue ? setTimeout(() => copied = false, 2500) : null)" @click="copied = copyEmbedHtml()" class="form-input-group" > Embed Copied to clipboard Start at Trailer Bonus Full Transcript View the website updateDescriptionLinks($el))" class="episode-description" > Chapters January 9, 2023 by APIs You Won't Hate View the website Listen On Apple Podcasts Listen On Spotify Listen On YouTube RSS Feed Subscribe RSS Feed RSS Feed URL Copied! Follow Episode Details / Transcript Mike talks with Drew White from Stashpad about personal notetaking apps for developers, and the potential of future API hooks for Stashpad. Show Notes Stashpad - https://stashpad.com/ Stashpad Discord - https://discord.gg/ScxPxcN9fK Drew White - @drucial Creators and Guests Host Mike Bifulco Cofounder and host of APIs You Won't Hate. Blogs at https://mikebifulco.com Into 🚴♀️, espresso ☕, looking after 🌍. ex @Stripe @Google @Microsoft What is APIs You Won't Hate? A no-nonsense (well, some-nonsense) podcast about API design & development, new features in the world of HTTP, service-orientated architecture, microservices, and probably bikes. Mike Bifulco: Hello, hello and welcome to APIs you Won't Hate. My name is Mike Fulco. Your effervescent and ever present host of the show. Today I am flying solo and having a chat with actually a friend of mine. Locally here in my hometown of Charlotte who I've known for a while now. And we're, we're gonna talk a bit about what he is working on, a bit about how he got there and you know, some of the backstory of that stuff. So I'm very excited to talk to today. Drew White. Drew, How's it going, man? Drew White: Hey Mike. How are you? Doing good today. Mike Bifulco: I'm good. I'm good. We have a lot of things to talk about. I'm really interested to hear your whole story and talk a little bit about stash pad where you, you have been laying down your lines of code of late among other things. Yeah, and I think we, we'll kind of get into all those things. In particular, like anything to do with building en engineering teams and all that is always interesting around here. Drew, tell me about yourself. How did we meet? Let's start there Drew White: this is actually, I feel like it was kismet if I can use that word. Yeah. So I'm a cyclist as you guys probably know, Mike is as well. And I was riding with a buddy on a local Greenway, and Mike was riding one of the most esoteric bikes that I feel like only a handful of local cyclists probably even know what they are. But I saw it was like, Hey. Is that a such and such? And he was like, Yeah, how did you, like, it was just like a, a sort of thing. And so we kind of met on the, the Greenway had a small little conversation and then later I had a. Set of wheels for sale. I, I believe, And you responded to the post. I don't think I realized it was you until you came to pick up the wheels and bought them and Yeah. So like that whole thing and then, yeah, just started riding like morning greenway grabbing coffee, that sort of thing. And that was a couple years ago now, Mike Bifulco: it was during the dark days of the pandemic for sure. You know, when, when we were not doing much indoor stuff, definitely a bit of kismet there. And I, I think if I remember like the space between bumping into each other for the first time and then me contacting you on Facebook marketplace to buy wheels when I needed them was like days to a week at most. Drew White: I think it was two days. I think it was two days. Mike Bifulco: a very strange back to back set of coincidences that I'm, you know, frankly pretty grateful for. Drew White: And I am too Mike Bifulco: Yeah, of course. We've talked about, you know, tons of writing stuff ever since, of course. And coffee seems to come up fairly often and you, you have similar tastes in design and all that other stuff too. So it's been super cool to kind of get to know you here. And what's been really cool to see over the past few years is like you've done a complete full on career. Like I, I, a pivot is not even fair. Like you've done an absolute like SUEx to your working world. Tell me a little bit about your working history. Like what, what have you done and what are you doing? Drew White: Yeah, so I've kind of taken a non-traditional path into the working world. I kind of started in finance for the first two years out of school. I did not go to college. Just really wasn't my, I attempted, but really wasn't my thing. So jumped into finance for a couple of years and then spent the. I don't know, decade or so in aerospace. Started kind of at the bottom of sort of midsize company and worked my way up to marketing director. And so from there, pivoted out of that into starting my own marketing agency which I did smack Deb in the middle of the pandemic right around the time that I met you. And what's interesting is I had been, You know, fascinated with the developer world for a couple years at that point. But really hadn't made it like a high priority on my, I tend to accumulate hobbies. So it kind of fell to the bottom of the stack. And then I met you and we were kind of talking about some of this stuff on the bike rides and, and such and such. And I had started building a lot of websites and things for. and yeah, just with one of your, your previous employers. Shown me the, the gymnasium actually which was like sort of like tutorial land, educational portal for largely like web dev stuff I feel like. But anyways, took every single course available on there and got a lot out of it. And just like that love of wanting to build stuff just ignited from that point forward. So fast forward. Let's say a year of really focusing on development education, particularly with JavaScript. I was kind of burn out managing this, this marketing business. Found a actual subcontractor that was interested in acquiring it and. Bailed and decided that I wanted to take a stab at, you know, working for a startup in the tech world. And so kind of applied to a couple of places and put my resume out there a little bit, However minimal it might have been at that point in time. And fielded quite a few inquiries and really landed on I had one conversation. Kara Bornstein is Stash pad ceo. And really believed in her vision and her as a leader of that company. So it was pretty sold and then in the second interview, got to meet with the cto the Meron and was even more sold. So I had kind of decided at that point that this is really where I wanted to be and. So took a role there as a developer experience designer, , Mike Bifulco: man, you've done so many things in such a short amount of time, like. Literally from, from finance to being a marketing director, to running an agency to figuring out how to find your way into the dev world is really fascinating. you know, Along the way, like you, you also had some interesting projects that you put out into the world, which, though your resume may have been short at the time you had some really cool stuff like your skew amorphism project . That, that was cool. Do you wanna talk a little bit about. Drew White: Yeah, sure. So I was just kind of in all of my free time, I was building a lot of UI stuff just. For learning purposes of my own, but also just cuz there were things that I wanted that I, I couldn't find or I didn't think existed or something like that. So I was using a lot of like, skew, morphism, glass, amorphism and amorphism in some of my designs. Primarily because I have a background in 3D design and so it was like sort of appealing to me to be able to create some of that stuff. Sort of like the in, in the web, which I thought was awesome. And so yeah, I created this tool. I got tired of like finagling, like, okay, 0.3 pixels, 0.4 pixels, like, like all of this stuff, like adjusting 'em to get like the shadows and the highlights and all of that stuff just right. And so I created a little tool that's basically a, a CSS generator with these really nice little sliders that, you know, you can quickly dial. The amount of s amorphism amorphism that you want with the right direction of light down to like, I think it's 1000th of a pixel or something like that. It's pretty crazy. But yeah, built that and it's actually gotten quite a bit of use from my, not only myself, but like other designers and developers have used it as well. And yeah, that was like the first real tool that I built and put out. Picked up any traction but it was super fun to build for sure. Mike Bifulco: Yeah. I appreciate most about you, how understated you are. It, this is an insanely cool thing and like to me, the, the perfect example of showing , that you're an interesting person who's taking a hands on approach to learning and actually building things out. I will drop the URL for this tool in, in the browser or sorry, in the, in the show notes here. And what's interesting for the audience of APIs you won't hate is like a lot of the folks we work with here. Really into building the data layer, the back end side of things, the connective tissue from the front end to the back end. But you can imagine in many ways that you could show off your chops as an API developer by building out a simple tool that just shows one facet of here's how I would, you know, build out these, these knobs and levers to adjust the experience of building an api. Better. New Amorphism is a very touchable like you know, tasty kind of thing to be able to go out and use and like as someone who's trying to break into the industry or as someone who was trying to break into the industry at the time, it's the perfect kind of prism put in front of yourself to say like, yeah, cool. I haven't worked in this yet, but I do this kind of work and I do a really good job of it. And it's gotten some great attention too, which is really cool. The, the thing I still need to yell at you about is you need to put your name on that webpage. In big, bold letters somewhere, minimalism be damned. People should know where it came from. You know what I mean? Drew White: That is sort of like a thing that we've talked about a bit. I'm a minimalist through and through like at every phase and yeah, it's, I get it. The branding. I need to be better about that for sure. And maybe someday I'll put it on there. Mike Bifulco: Fair enough. Yeah, I'll go chase down your code and open a poll request for you. Yeah. Cool. So why don't we talk a little bit about what you're doing now. So what is stpa? Drew White: So Stash Padd is a notes taking application. Kind of aims to flip that concept of notes taking on its head. The whole point of what we're doing is reducing the burden of capture. I mean from my perspective, notes is not a particularly enjoyable experience for most people. However, it is a particularly important. Part of daily dev life or daily, you know, really work life. Being able to get thoughts out of our head, take notes on conversations that we've had, meetings standups, code reviews, all that kind of stuff very easily, very quickly, and be able to put it somewhere and not really have to worry about where you're putting it necessarily and kind of give you that feeling and vibe. Similar to like if you were dm, DMing yourself in Slack. Where it's the, it's the lowest burden of entry for capture. And the, the, in my personal experience, I might be biased, but my personal experience, it's the, it's the least amount of friction for getting something out of my head and into somewhere that I can recall it later when I need to. So yeah, we've been working on the app for, oh, probably two years now, I guess is when. Things kind of started, but we just launched in August on product hunt. And reception has been phenomenal. It's been so, so good. So yeah. That's what Stash pad is. It's at the helm we have Kara Bernstein and Theo Meron as the two founders. And then it's a pretty small team. We're located in Raleigh or Durham, North Carolina. I keep saying Raleigh every Mike Bifulco: Middle of both. Drew White: Yeah. Yeah. Mike Bifulco: I mean, most people put 'em right next to each other anyway. Drew White: At the American Underground there which has been great. So, Yeah. Mike Bifulco: Yeah. Cool. Yeah. American Underground is kind of like the home of startups in, in that part of North Carolina. A super cool community created there. So note taking is a really interesting thing to me. I, I have kind of a, a interesting history with it and actually I remember, I wish I could tell you when it was, but I remember a specific conversation I had with one of my great friends actually. My former employer, Andrew Miller, who is the program director over at Gymnasium and his longtime friend of mine, one of the, the smartest people I know. At one point I remember having a conversation with him where he asked me about how I take notes for work. Like how do I keep track of what I'm doing? And literally at the time, my response was, why would I take notes? Like, I just remember it, you know? And like the, the brash, bold statement that I made that was just like I don't know. My brain's working at a thousand percent all the time. Why do I need to write anything down? I remember that moment and I remember like literally a month later being like, Oh man, I need to write everything down. Like I'm starting to forget things. They're all falling outta the back of my head. And that, that was the moment where I really started to focus on like, trying to organize myself, trying to organize my thoughts and have frankly, filtered through a lot of tools in the meantime. And I think. The note taking thing and writing down notes and taking notes is a virtuous thing. It's very good. You want to do it because it, it's less burden for your, your mind, but also it helps other people, right? So like, Drew, if you and I have a conversation, I'm teaching you something one on one, that's awesome. You might learn something from me. But if I also write it down and one other person reads it, I've doubled the efficacy of that conversation. And that's why note taking is good. It's also helpful. If I forget it in the future, I can come back to it. What, what I also really like about it too is that. Note taking is different for everyone and you kind of have to find what works for you. And I feel like people may feel like the market is kind of floated, flooded with note taking tools. But I think that's because people's style of thought and their style of organization is very, very different from one another and like, Some people are good with just a notepad, you know, txt file and, and the chaos that that may bring on. Some people might like the iOS, you know, note app for their own thing. But truly finding something that is like broadly applicable and easy to use and easy to understand is a challenging problem space. Drew White: Yeah, and I think actually your experience that you just described is fairly common. You know, I had the same. Greater than do attitude towards notes in the early days, like I have a pretty solid memory. I can remember a lot of things. But what I think a lot of people who do take notes now understand, and people who don't take notes will ultimately figure out is that the more you keep in your head, Yeah, you may be able to keep it in there, but you got limited space up there. So the more you take in, eventually some of that stuff's gonna start falling off. And then there's like the stress of, you know, some of that data may be important and then you may not have it. So I've definitely adapted a practice and you're absolutely right, there's a lot of options out there and. Varying degrees of Complexity, which is the interesting part to me. But I think what is so interesting is just the fact that there are so many, like different note taking applications speaks to a larger problem, right? No one has kind of sorted this stuff out. Usually, particularly in the dev the development world, engineering world dev tools tend to be winner take all, I mean, vs. Code by far and away owns the market and in ide, maybe with JetBrains or something coming in right behind them. You've got. Basically issue tracking tools and all these other things. There's usually like a winner take all sort of situation and in so sort of personal notes that sort of space that really isn't something that is landed on. People are kind of all over the board from, you know, untitled text files, just flooding their desktop to any combination of different apps, big ones, no notion Evernote obsidian, all of those things and. Where we like to think that we can fit in and, and, and why we're building this thing in the first place is to kind of have this defacto, we'll do whatever you want it to do. Lightweight and very speedy. I've used some of the other big name apps out there particularly. Like Apple notes and things like that. And there always seems to be a little bit of friction between, I just got told some information that I need to remember in four hours from now, or two days from now, or two months from now. Where do I put that? How do I organize that in my. Hierarchy or whatever and how am I gonna find that later? And that has always been my challenge. I've bounced around from, from app to app long before I even knew that stash pad was a thing. And so that's the problem we aim to resolve. And the reality is if we can bring a little bit of joy to something that is often like a mundane sort of experience yeah, I mean, all the better. That's. The goal Mike Bifulco: Sure. Yeah. It's a, it's a hard thing to describe the way, the value of having a good note taking system feels. But like, when you come out on the other side of it and you start writing things down, the task of recall suddenly doesn't become, I need to remember every detail about this thing. All you need to remember is that you wrote it down and you can find it. And that's something that, the scale that comes with that is pretty tremendous and also really helpful. Like in three years when I wanna look up what you and I talked about today I certainly won't remember. Right in my brain, but I will remember that we had this talk and I can jump back into my notes and chase it down. Drew White: Yep. Mike Bifulco: It's, it's super cool and I feel like there's a lot of psychology that goes into it, like both the people's hesitance to take on note taking, but then like the personal style, the workflow, the things that trigger peoples like, I need to take a note about this, or I need to keep my list of tasks in this versus you know, am I summarizing an article or, or writing down a note about, I dunno, some hack I wrote in my code, Whatever the case may. Yeah, I, I like all of that stuff. It's really interesting to think about and like you must be building a very kind of generic tool set to do that, right. Drew White: Yeah. I mean, like our whole concept is, is giving Users, people a default place to write to that they don't have to worry about. Like, it's, it's essentially a log, you know, it's. Date timestamped log. That includes everything that you've got. So if you even remember roughly what happened during the day, you should be able to find the note that, that you took down which is pretty awesome. And so sort of the next big thing for us is further removing we'll call 'em barriers to capture cuz we believe that that's the most important thing. And so as we continue to expand, Develop the product. One of our, our major items on our roadmap is like integrations and our api. So the whole idea of being able to. Send content from somewhere into stash pad or even have that content automatically be imported into Stash Padd as a note in the right place when you need it is really exciting for me. I don't know what it was like, you know, at any of your, your previous employers. But like one of the biggest things moving to the tech world that kind of knocked me off my socks is the tech stack. I was not prepared for that whatsoever. Like even coming from like my own business where I was using quite a few different tools for different purposes and managing those things. Like my bookmark folder for like just dash padd tools is, is, is pretty big. Like we, we've got at least 12 separate tools that we use for different purposes. And while that's great and all of them work really well, sometimes it's hard. Particularly in my position, it's difficult. Hey, remember where that comment that someone made that you need to reference came from? Or like, was it in Slack? Was it in, was it a conversation, Was it a thread in Slack, like going back and doing all of that stuff? Or was it a slab or any, any number of, of different locations it could have come from. And so the ability to have this sort of automated notes dashboard which is, you know, the ultimate goal here. Really, really appealing to me to be able to create some smart stacks that give you the information you need from the resources that you use, the tools that you use and combine that with capturing your own notes from one-on-ones meetings, code reviews, all of that stuff is really just feels like I would like to have that today. Mike Bifulco: Sure . Sure. Yeah. I what I'm really interested to hear about too is like, this is, this is one of those great cases where almost certainly you will be using Dash pad as you're building it. You know, probably both personally and as, as a company, as a team, whatever that looks like. Can you tell me a little bit about what, what your, like what your, I dunno. Your dog fooding process is like, and some of the things that your team does with Stash pad. Drew White: Yeah, so our dog fooding process is pretty strong. Everybody on our team is very opinionated and also very thorough and not afraid to speak up, which is hugely beneficial both from like a development standpoint, but honestly from a design standpoint, which I spend a lot of time in. And so we all use stash pad very differently. It's actually pretty fascinating. Often, like, we'll go into like a spec review or something like that and this person will say, You know, I use this this way, that makes perfect sense to me. And then like I'm looking at 'em like, I don't use it that way at all. Like I, my mindset, my brain map is, is different. My mental model is different. And so what's fascinating is we've, we've kind of engineered the flexibility to match different mental models into the app which has. I don't know, kind of just eye opening for me, but I use it all the time. Primarily with code reviews, design reviews, that sort of thing. Spec reviews. I have several, one-on-ones every week. I like to use it for them so I can both remember what we talked about, but also kind of measure my own progress and be able to go back and look at some of the things that we talked about. I also do it. Basically things that I want to bring up. I also use it as a drafting tool, believe it or not. Cuz it does support markdown and so I can do some longer form notes if I need to. So I do like it as a drafting tool. They render really, really nicely. And then I also use it as like a lockbox for data. I know I'm gonna need in perpetuity. I can keep a place for quick, quick info that I just need to access all the time. And I can know that everything in there is always gonna be there forever in the shape that it needs. So and that's how I use it. I also use it as a task manager. We've got a great sort of to-dos system and hierarchical todos, which is super awesome. So like you can create a stack of todos. Which is within another stack of, to-dos, that stack itself can be a to-do so on and so forth. So Yeah. it works really well for keeping me organized. Mike Bifulco: I can imagine as an engineer or someone working on a product team, whether you're an engineer or a designer or a product manager, whatever, whatever your role is there's a lot of value in keeping yourself organized and, and making this thing work for you. Can you tell me a little bit about the storage plan for for Dash pad? So right now, is it local only? Is it cloud synced? Is it something you use with like Dropbox or Google Drive or something like that? How does it work? Drew White: Yeah, right now it is local only. That was a decision we made based on some, you know, early feedback that we had from engineers and, you know, companies being very, we, we want people to be very have the option to be very private about their, their data and not be sinking to and from the cloud. But as. Right now we are I don't wanna put an actual date on it. We do have a date for release, but just in case things get pushed, you know plus a couple of days, minus a couple of days, whatever the case is, we are rolling out sync in the very near future which will give users an opportunity to not only have data on multiple computers, but also we'll be rolling out our mobile app about the same time. So yeah, we'll have access to. Again, the whole idea is further reducing that, that, that friction capture. So yeah, we'll, we'll have cloud sync available for a pretty small monthly fee. I don't know exactly what it is off the top of my head. But it's very reasonable. And I think there will be a, a certain number of. Um, like free sync sort of things. And then the community version, which is non sync will be free forever in perpetuity. Mike Bifulco: Yeah. Very cool. Is there, so is Stpa taking the perspective that notes are a sort of personal trove of information or is there collaborative features? Drew White: Yeah. So I mean, our whole thing through this has been, there are so many tools out there for teams, right? And. There's very little for managing your own daily work. And so we have taken this stance that Stash pad is for you, not for your team, not for your manager, not for even necessarily the enterprise, although I'm sure we will have enterprise level customers. The idea is it's for the engineer, it's for the user and. That being said, we actually do, we used to have a a web app version, which was like version negative 0.1 or whatever you wanna call it. That does have a collab feature that we still to this day use for retro. And it is easily the greatest platform for something like that that we have experimented with. We've tried basically everything else. We always end up coming back to the old web app. So, yeah, there may be plans for, for adopting some of that functionality in the future as well. Mike Bifulco: Sure. Yeah, I think it's, it is a good angle to take or an interesting angle to take, certainly. I think a lot of folks gut response might be that like having a team collaborative tool is maybe the, the table stakes for them. But in practice, all of the companies I've worked at that have reached any like. Reasonable team size of, call it five people or greater, tend to standardize on like, what is easiest. So and, and by that I mean like things that they've probably already paid for within the enterprise. So that may be Google Talks or Jira or GitHub or like the things that are sort of built into that process. But what I also like about this is that by keeping it local and for yourself, like it, it, it's a way for you to keep your information, to grow your own sort of stack of knowledge and, and to build upon your own set of notes in a way. That is you flavored. I think that's really interesting. And obviously you can still collaborate with your team right there. There are you know, ways to get information out of this thing. It's not a one way valve. Yeah, yeah, Drew White: And I think just based on our experience using the web app, I can't see that not making it in like the collaborative use case, not making it into the app. It's just, it's too good to like pass on. I just don't know where it lives on our roadmap today. Mike Bifulco: The perpetual startup challenge. Yeah. When, When is it the most important thing to build? Drew White: That's right. And I think a lot of people like, I mean, we're a team of seven, so like we're, we're pretty small. And so we've gotta kind of pick and choose our priorities, particularly this close to our launch, you know, And so we're trying to deliver one thing, but a perfect one thing, and then we'll Mike Bifulco: of course. Drew White: the next thing, you know? Mike Bifulco: Yeah. So I'm, I'm curious to probe in a little more about the sort of API layer that you teased, cuz I know that the, the team listening to this will definitely be interested in that. What does that look like? What are the sort of hooks you're thinking about? You know, opening up APIs for. Drew White: Yeah, I mean, primarily the initial sort of main function of the API is intended to expand capture essentially. So the ability to send information to stash pad from basically any tool or any product, any project that you're working on would be the primary function. You may have some other functionalities that come after that. But yeah, I mean our whole thing is that the easier you can make capture, the more likely people are gonna take notes and the better they're gonna retain information and then ultimately the better they're gonna be able to work. So yeah, the, that, that'll be the, the primary function there. We're still kind of working through the details on this. This is on our current roadmap. And I know it's coming probably way quicker. We're gonna be . It feels like we're doing a lot of things right now. But they're all very good things and we're executing at a pretty high level. And so we're trying to maintain that, that momentum. So I, I'd be surprised if this wasn't out early first quarter next year. Yeah. Mike Bifulco: Yeah. Cool. I, I know your team. So you said it's a seven person team. And I, I know you've done some of the engineering work. I'd imagine there's a few engineers that, that work on the product. Can you talk a little bit about what dpad is built with? Drew White: Yeah. Stash Padd is built with react type script in El. Has our primary shippable form, and then the mobile app will be React native actually. So yeah, it's been, it's actually been quite a joy to work with. I know. Our one of our engineers who kind of does a lot of the electron work definitely has some grapes about it. He just wrote a blog post that'll be up on our website probably at the end of today. But yeah, it's, it's, it's a great tool and there's a reason that it's so widely used. And so even with some of the, the push and pull I think it's still a good option, particularly for desktop. And it allows us to ship to Linux and Windows and Mac kind of all in one go. Mike Bifulco: Sure. Yeah, I feel like the electron's perpetual thing is that as it does more people want more. And you know, early on the conversation was mostly around performance. You know we can't ship a Chrome browser for everything. But to be honest, I think that's become less of a problem in recent years as computers have gotten better, as electronic self has gotten better, as Chrome has gotten more lightweight and all those things. Or chromium, I guess not quite chrome. Drew White: Right? Mike Bifulco: And it's interesting to pair that with React Native too, which historically has had similar things and has gotten tremendously further along in the past few years. Like building for React native now is so much easier than it was in 2016. It's, it's a much, much more capable thing. It's cool to see that coming around. Drew White: Yeah, I did some stuff with React native, just personal projects a couple years ago, and I haven't had an opportunity to work on any of the mobile stuff Now my role is, is pretty widely split between design, engineering, dev, re and then some higher level stuff, product stuff. So, but any chance I, I get an an opportunity to, to work in app I relish those opportunities cuz that's sort of what drove me to this place in the first place. But yeah, the we're, we're pretty excited. We've got some, some really good things coming out and I think they're happy with React native today. The engineers are don't, I haven't heard much in the way of complaints, so that's always a good sign. Mike Bifulco: Yeah, I'll say certainly. Cool. So Drew what other things haven't we touched on with Stash pad that, that folks might be interested in if they haven't tried it yet? Drew White: Yeah, I think for me it's the, it's really the speed of the thing that makes it so much better. Like I, I've been a long time, I, I kind of bounce, I mentioned it earlier, I bounced around from app to app for years notes app that is and ultimately landed on Apple Notes just because of its, Sort of nativity as it were. But it was always kind of like somewhat of a compromise for me. But I've actually just, I mean, within the last six months have like fully transitioned into stash pad as a whole, primarily because of the speed of the thing. It's just uncanny, like I think all of our. Basic actions are sub hundred milliseconds or something like that. Like even like loading a massive list of notes is just ridiculously fast. And the other real concept behind it, like particularly if, if you're like a developer and you know, the importance of keeping your hands on the keyboard, like the thing is, is well set up you can navigate everything create, delete, you know, whatever you want to do without ever leaving the keyboard. And like, Super familiar, sort of key bindings that make a lot of sense. And so that's like another huge thing for, for me in particular. We also have like a shortcut, like a global OS shortcut. So you can open it up while you're, so you're working in BS code or your ide and you gotta take a quick note. You can just open it up without ever touching the mouse and bounce over to it, dump your note, go back to work, and just basically eliminate that context switching sort of moment right there. Yeah, I think if anybody hasn't tried it that's listening. It's certainly worth it. It's free, so no harm, no foul. You can download it, our website wws-padd.com. And yeah, give it a try. Let us know. And we're super active on our Discord server. We love getting feedback from, from users even when they hate it. Like we got railed the other day by some guy. He just didn't like the interface like whatsoever. And. He was, he must have sent like 10 emails yesterday, I think. But that's good stuff for us. Like, it's, it's good feedback. Like we don't mind it at all. So yeah, I, I definitely think everybody, if you're using Evernote or Notion or Apple Notes or Ulysses or any of the other ones it's worth giving a try. It's a different experience for sure. You may like it, you may not, but we hope that you. Mike Bifulco: Yeah. Cool. I'll, I'll make sure to drop a link in the show notes here too. And if people wanna chase you down, Drew, where's the best place to find you? Drew White: Usually you can find me at the Whitewater Center in Charlotte, North Carolina or at Fonta Flora. Also Shta no. Yeah, you can find me on Twitter. Atul. I don't, I, I, I spend a lot of time there observing, but I'm not like a huge content creator. I like watching. Mike Bifulco: there's a lot to observe on Twitter these days too. Drew White: Yeah. Yeah, yeah. And then, yeah, that's probably the easiest way to get ahold of me, Mike Bifulco: Cool. Right on. Well, Drew, thanks so much for hanging out today. It's been really cool talking about STA pad. Yeah, come back anytime, especially once you're starting to talk about like opening up the API taps we'll have lots of people with very interesting opinions for you, and I'm sure you'll get a, a bit of an onslaught in your discord for people with feature requests and things like that in the near Drew White: Perfect. We'll create your own channel just for you guys. Mike Bifulco: Right on. Thanks so much, Drew. We'll talk soon. Drew White: thanks Mike. Mike Bifulco: See ya. All audio, artwork, episode descriptions and notes are property of APIs You Won't Hate, for APIs You Won't Hate, and published with permission by Transistor, Inc. Broadcast by | 2026-01-13T08:48:04 |
https://forem.com/t/nintendoswitch/page/2 | Nintendoswitch Page 2 - 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: Is Nintendo Switch 2 Off to a Good Start? - NVC Clips Gaming News Gaming News Gaming News Follow Sep 20 '25 IGN: Is Nintendo Switch 2 Off to a Good Start? - NVC Clips # nintendo # nintendoswitch # gamedev Comments Add Comment 1 min read IGN: Sonic Racing: CrossWorlds Review Gaming News Gaming News Gaming News Follow Sep 20 '25 IGN: Sonic Racing: CrossWorlds Review # pcgaming # playstation # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Final Fantasy 7 Remake Intergrade - Official 'World and Factions' Trailer Gaming News Gaming News Gaming News Follow Sep 19 '25 IGN: Final Fantasy 7 Remake Intergrade - Official 'World and Factions' Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: It’s Expensive Being a Nintendo Fan in 2025 - NVC Clips Gaming News Gaming News Gaming News Follow Sep 19 '25 IGN: It’s Expensive Being a Nintendo Fan in 2025 - NVC Clips # nintendo # nintendoswitch 1 reaction Comments Add Comment 1 min read IGN: Donkey Kong Bananza: DK Island and Emerald Rush Review Gaming News Gaming News Gaming News Follow Sep 19 '25 IGN: Donkey Kong Bananza: DK Island and Emerald Rush Review # nintendo # nintendoswitch # retrogaming Comments Add Comment 1 min read IGN: Hollow Knight Silksong - How to Get Needle Upgrade 2 - Pale Oil Location Guide Gaming News Gaming News Gaming News Follow Sep 19 '25 IGN: Hollow Knight Silksong - How to Get Needle Upgrade 2 - Pale Oil Location Guide # pcgaming # indie # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Ratatan - Official Early Access Cinematic Launch Trailer Gaming News Gaming News Gaming News Follow Sep 18 '25 IGN: Ratatan - Official Early Access Cinematic Launch Trailer # gamedev # pcgaming # steam # nintendoswitch Comments Add Comment 1 min read IGN: Absolum - Official Gameplay Trailer Gaming News Gaming News Gaming News Follow Sep 18 '25 IGN: Absolum - Official Gameplay Trailer # pcgaming # nintendoswitch # playstation # indie Comments Add Comment 1 min read IGN: Super Mario Galaxy + Super Mario Galaxy 2 - Official Overview Trailer Gaming News Gaming News Gaming News Follow Sep 18 '25 IGN: Super Mario Galaxy + Super Mario Galaxy 2 - Official Overview Trailer # nintendo # nintendoswitch # retrogaming Comments Add Comment 1 min read IGN: Nintendo Switch Online + Expansion Pack - Official Game Boy Advance September 2025 Update Trailer Gaming News Gaming News Gaming News Follow Sep 18 '25 IGN: Nintendo Switch Online + Expansion Pack - Official Game Boy Advance September 2025 Update Trailer # nintendo # nintendoswitch # retrogaming Comments Add Comment 1 min read GameSpot: S Rank Sonic Racing: CrossWorlds Super Sonic Speed Market Street Gameplay Gaming News Gaming News Gaming News Follow Sep 18 '25 GameSpot: S Rank Sonic Racing: CrossWorlds Super Sonic Speed Market Street Gameplay # pcgaming # nintendo # nintendoswitch Comments Add Comment 1 min read GameSpot: Sonic Racing: Crossworlds Review Gaming News Gaming News Gaming News Follow Sep 18 '25 GameSpot: Sonic Racing: Crossworlds Review # pcgaming # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Demon Slayer - Kimetsu no Yaiba - The Hinokami Chronicles 2 - Official Muzan Kibutsuji Trailer Gaming News Gaming News Gaming News Follow Sep 18 '25 IGN: Demon Slayer - Kimetsu no Yaiba - The Hinokami Chronicles 2 - Official Muzan Kibutsuji Trailer # pcgaming # playstation # nintendoswitch # xbox Comments Add Comment 1 min read IGN: EA Sports FC 26 - Official 'The Club is Yours' Launch Trailer Gaming News Gaming News Gaming News Follow Sep 18 '25 IGN: EA Sports FC 26 - Official 'The Club is Yours' Launch Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Hyrule Warriors: Age of Imprisonment - Official 'Fight the Epic Imprisoning War' Trailer Gaming News Gaming News Gaming News Follow Sep 17 '25 IGN: Hyrule Warriors: Age of Imprisonment - Official 'Fight the Epic Imprisoning War' Trailer # nintendo # nintendoswitch # pcgaming Comments Add Comment 1 min read IGN: Super Mario Galaxy 2 - Enhanced Switch 2 Gameplay 4K 60FPS Gaming News Gaming News Gaming News Follow Oct 3 '25 IGN: Super Mario Galaxy 2 - Enhanced Switch 2 Gameplay 4K 60FPS # nintendoswitch # nintendo # retrogaming 2 reactions Comments 1 comment 1 min read IGN: Hollow Knight: Silksong Review Gaming News Gaming News Gaming News Follow Sep 17 '25 IGN: Hollow Knight: Silksong Review # pcgaming # playstation # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: WWE 2K25 - Official Attitude Era Superstars DLC 4 Trailer Gaming News Gaming News Gaming News Follow Sep 17 '25 IGN: WWE 2K25 - Official Attitude Era Superstars DLC 4 Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Borderlands 4 - Official Accolades Trailer Gaming News Gaming News Gaming News Follow Sep 17 '25 IGN: Borderlands 4 - Official Accolades Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Marvel Cosmic Invasion - Official Cosmic Ghost Rider & Black Panther Character Reveal Trailer Gaming News Gaming News Gaming News Follow Sep 17 '25 IGN: Marvel Cosmic Invasion - Official Cosmic Ghost Rider & Black Panther Character Reveal Trailer # pcgaming # nintendoswitch # playstation # xbox Comments Add Comment 1 min read IGN: Street Fighter 6 - Official 'C. Viper Arrives!' Fighting Pass Trailer (Japanese VO) Gaming News Gaming News Gaming News Follow Sep 17 '25 IGN: Street Fighter 6 - Official 'C. Viper Arrives!' Fighting Pass Trailer (Japanese VO) # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Dragon Ball Xenoverse 2 - Official Future Saga Chapter 3 Trailer Gaming News Gaming News Gaming News Follow Sep 16 '25 IGN: Dragon Ball Xenoverse 2 - Official Future Saga Chapter 3 Trailer # pcgaming # playstation # nintendoswitch # xbox Comments Add Comment 1 min read IGN: Hollow Knight: Silksong Boss Fight - Skull Tyrant (The Marrow) Gaming News Gaming News Gaming News Follow Sep 16 '25 IGN: Hollow Knight: Silksong Boss Fight - Skull Tyrant (The Marrow) # pcgaming # indie # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Hollow Knight: Silksong Boss Fight - Double Conchflies (Blasted Steps) Gaming News Gaming News Gaming News Follow Sep 16 '25 IGN: Hollow Knight: Silksong Boss Fight - Double Conchflies (Blasted Steps) # pcgaming # indie # nintendo # nintendoswitch Comments Add Comment 1 min read GameSpot: Sonic Racing: CrossWorlds Everything To Know Gaming News Gaming News Gaming News Follow Sep 16 '25 GameSpot: Sonic Racing: CrossWorlds Everything To Know # pcgaming # nintendo # nintendoswitch # retrogaming 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://www.highlight.io/customers/cabal | How Cabal Uses Highlight to Ship Products Star us on GitHub Star Migrate your Highlight account to LaunchDarkly by February 28, 2026. Learn more on our blog. Product Integrations Pricing Resources Docs Sign in Sign up All customers Customer Case Study How Cabal Uses Highlight to Ship Products We have two main use cases for Highlight in the Cabal GTM team. The first is addressing support tickets. Our first reaction when we receive a ticket is to understand what the user did, and so we’ll check Highlight to see what interaction they had with the product and where things went wrong. Highlight allows us to address customer support requests with precision. The second way we use Highlight is to get self-serve feedback on new features from our users. Rather than having to set up a bunch of customer interviews, we’re able to go into Highlight and understand where people are clicking, where they’re getting held up, etc. We then make the necessary changes to the product and repeat the process. Understanding user issues “ One of the beautiful things about Highlight is it gives you an illustration of what events took place over the course of a user’s session. ” Sam Kernan-Schloss , Cabal At Cabal, we want to deeply understand the issues that our customers are facing. A lot of times, when customers reach out to us with an issue, we lack context on how the issue actualizes and what’s causing it. That’s where Highlight comes in. When a customer reaches out to us on Intercom, we’ll drop their email into Highlight and Highlight immediately returns a prioritized list of the sessions for that specific user. We’ll then watch the most relevant sessions to get an understanding of what’s wrong. One of the beautiful things about Highlight is it gives you an illustration of what events took place over the course of a user’s session. This makes it easy to quickly understand where something went wrong, within 10 seconds or so. New feature feedback “ With Highlight, we can understand how users actually feel about a particular feature by observing their behaviors. It makes it easy to understand things like where the friction points are, where users are getting frustrated, and whether users are using new features as we intended. ” Sam Kernan-Schloss , Cabal Shipping features quickly is important to our team at Cabal. One of the challenges of shipping quickly is making sure you’re staying in touch with customer feedback and getting an understanding for how your features are being received by end-users. You can set up a bunch of customer interviews, but there are two main issues with that: They require a lot of overhead to coordinate and manage at scale The customer feedback may not exactly align with their behaviors in-product With Highlight, we can understand how users actually feel about a particular feature by observing their behaviors. It makes it easy to understand things like where the friction points are, where users are getting frustrated, and whether users are using new features as we intended. Understanding user behavior through session replay is the best way to gauge the success of new features. Why Highlight “ One of the beautiful things about getting Highlight set up was that I didn’t need to worry about it interrupting our sprints. After we decided to use Hex, getting it set up for our team took less than an hour. ” Sam Kernan-Schloss , Cabal One of the things that stuck with me from the first time I demo’d Highlight was that, not only did it help the engineers with debugging, but it was easy enough for folks on the GTM team, like myself, to use and see how our users are using the product. One of the beautiful things about getting Highlight set up was that I didn’t need to worry about it interrupting our sprints. After we decided to use Hex, getting it set up for our team took less than an hour. When we were comparing Highlight to similar tools, we realized that we were able to get a bit more granular with what we were seeing in Highlight, as compared to other tools. It also made it easy to filter down to what we wanted to watch. Our engineering team also appreciated the engineer-first focus of the product and got really excited about the tool being suited for them. Previous Customer Next Customer About the company A private workspace for founders to send asks & updates, track contributions, and scale their advisor program. Founded 2020 Using Highlight since Jan 2020 Try Highlight Today Get the visibility you need Get started for free Product Pricing Sign up Features Privacy & Security Customers Session Replay Error Monitoring Logging Competitors LogRocket Hotjar Fullstory Smartlook Inspectlet Datadog Sentry Site24x7 Sprig Mouseflow Pendo Heap LogicMonitor Last9 Axiom Better Stack HyperDX Dash0 Developers Changelog Documentation Ambassadors Frameworks React Next.js Angular Gatsby.js Svelte.js Vue.js Express Golang Next.js Node.js Rails Hono Contact & Legal Terms of Service Privacy Policy Careers sales@highlight.io security@highlight.io [object Object] | 2026-01-13T08:48:04 |
https://github.com/skills/secure-code-game | GitHub - skills/secure-code-game: A GitHub Security Lab initiative, providing an in-repo learning experience, where learners secure intentionally vulnerable 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 / secure-code-game Public template Notifications You must be signed in to change notification settings Fork 319 Star 2.6k A GitHub Security Lab initiative, providing an in-repo learning experience, where learners secure intentionally vulnerable code. License MIT license 2.6k stars 319 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 0 Pull requests 1 Discussions Actions Security Uh oh! There was an error while loading. Please reload this page . Insights Additional navigation options Code Issues Pull requests Discussions Actions Security Insights skills/secure-code-game 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 100 Commits .devcontainer .devcontainer .github .github Season-1 Season-1 Season-2 Season-2 Season-3 Season-3 .gitignore .gitignore CONTRIBUTING.md CONTRIBUTING.md LICENSE LICENSE README.md README.md requirements.txt requirements.txt View all files Repository files navigation README Code of conduct Contributing MIT license Security 📣 SEASON 3 JUST DROPPED, AND IT'S ALL ABOUT ARTIFICIAL INTELLIGENCE 📣 Secure Code Game A GitHub Security Lab initiative, providing an in-repo learning experience, where learners secure intentionally vulnerable code. At the same time, this is an open source project that welcomes your contributions as a way to give back to the community. Welcome Who is this for : Developers, students. What you'll learn : How to spot and fix vulnerable patterns in real-world code, build security into your workflows, and understand security alerts generated against your code. What you'll build : You will develop fixes on functional but vulnerable code. Prerequisites : For the first season, you will need some knowledge of python3 for most levels and C for level 2. For the second season, you will need some knowledge of GitHub Actions for level 1, go for level 2, python3 for level 4, and javascript for levels 3 and 5. For the third season, no prior knowledge of Artificial Intelligence is needed. How long : Seasons 1 and 2 each feature five levels and typically take 3-6 hours to complete, depending on your skill level. Season 3 offers six levels and has an estimated completion time of 2-4 hours, also depending on your experience. 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. You can now proceed to the 🛠️ set up section. 🛠️ The set up 🖥️ Using codespaces All levels are configured to run instantly with GitHub Codespaces. If you chose to use codespaces, be aware that this course will count towards your 60 hours of monthly free allowance . For more information about GitHub Codespaces, see the " GitHub Codespaces overview ." If you prefer to work locally, please follow the local installation guide in the next section. To create a codespace, click the Code drop down button in the upper-right of your repository navigation bar. Click Create codespace on main . After creating a codespace, relax and wait for VS Code extensions and background installations to complete. This should take less than three minutes. At this point, you can get started with Season 1, 2, or 3, by navigating on the respective folders and reading the README.md file. Once you click on individual levels, a banner might appear on the bottom right asking you if you want to create a virtual environment. Dismiss this notification as you don't need to create a virtual environment. Optional: We recommend these free-of-charge additional extensions, but we haven't pre-installed them for you: github.copilot-chat to receive AI-generated code explanations. alexcvzz.vscode-sqlite to visualize the SQL database created in Season-1/Level-4 and the effects of our exploits on its content. If you need assistance, don't hesitate to ask for help in our GitHub Discussions or on our Slack , at the #secure-code-game channel. 💻 Local installation Please note: You don't need a local installation if you are using GitHub Codespaces. The following local installation guide is adapted to Debian/Ubuntu and CentOS/RHEL, and assumes your goal is to play through all the game's seasons. Open your terminal. Install OpenLDAP headers needed to compile python-ldap , depending on your Linux distribution. Check by running: uname -a For Debian/Ubuntu, run: sudo apt-get update sudo apt-get install libldap2-dev libsasl2-dev For CentOS/RHEL, run: sudo yum install python-devel openldap-devel For Archlinux, run: sudo pacman -Sy libldap libsasl Then, for all of the above Linux distributions install pyOpenSSL by running: pip3 install pyOpenSSL Once installation has completed, clone your repository to your local machine and install required dependencies. From your repository, click the Code drop down button in the upper-right of your repository navigation bar. Select the Local tab from the menu. Copy your preferred URL. In your terminal, change the working directory to the location where you want the cloned directory. Type git clone and paste the copied URL. $ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY Press Enter to create your local clone. Change the working directory to the cloned directory. Install dependencies by running: pip3 install -r requirements.txt Programming Languages To play Season 1, you will need to have python3 and c installed. To play Season 2, you will need to have yaml , go , python3 and node installed. To play Season 3, you will need to have node installed, just like for Season 2. Therefore, if you played Season 2 locally, you're all set. If you are using VS Code locally, you can install the above programming languages through the editor extensions with these identifiers: ms-python.python ms-python.vscode-pylance ms-vscode.cpptools-extension-pack redhat.vscode-yaml golang.go Please note that for the go programming language, you need to perform an extra step, which is to visit the official website and download the driver corresponding to your operating system. Now, it's necessary to install node to get the npm packages we have provided. To do so: Start by installing a package manager like homebrew by running: /bin/bash -c " $( curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh ) " Install node : brew install node Adapt the command to the package manager you have chosen if it's not homebrew. The npm packages needed are specified in package.json and package-lock.json . Navigate to the secure-code-game repository and install them by running: npm install --prefix Season-2/Level-4/ && npm install --global mocha Install vitest npm install vitest At this point, you can get started with Season 1, 2, or 3, by navigating on the respective folders and reading the README.md file. We recommend these free-of-charge additional extensions: github.copilot-chat to receive AI-generated code explanations. alexcvzz.vscode-sqlite to visualize the SQL database created and the effects of our exploits on its content. For more information about cloning repositories, see " Cloning a repository ." Get help: Email us at securitylab-social@github.com • Review the GitHub status page © 2025 GitHub • Code of Conduct • MIT License About A GitHub Security Lab initiative, providing an in-repo learning experience, where learners secure intentionally vulnerable code. Topics code-scanning code-security codeql 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 2.6k stars Watchers 25 watching Forks 319 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 25 Uh oh! There was an error while loading. Please reload this page . + 11 contributors Languages JavaScript 39.4% Python 32.3% Go 13.4% C 7.8% HTML 7.1% 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://livesuggest.ai/ko/ | 봇 없는 AI 회의 어시스턴트 | 실시간 제안 - LiveSuggest LiveSuggest 1시간 무료 요금제 로그인 회원가입 세션 시작 한국어 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 1시간 무료 요금제 로그인 회원가입 세션 시작 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개 언어 통화에 참여하지 않는 AI 회의 어시스턴트 마이크 또는 탭 공유를 통해 실시간 AI 제안을 받으세요. 봇이 회의에 참여하지 않고, 녹음도 저장되지 않습니다. 무료로 체험하기 ✓ 신용카드 불필요 ✓ 가입 불필요 ✓ 1시간 무료 👥 이미 컨설턴트, 프리랜서 및 프로젝트 관리자가 사용 중입니다 회의 중 AI 도움 예시 회의 후속 조치 결정 사항: Sarah가 금요일까지 프로토타입 완성. 새로운 아이디어 이번 스프린트 후에 회고를 진행해서 배운 점을 정리하면 어떨까요? 용어 설명 언급된 "스프린트"는 애자일 방법론에서 2주 개발 주기에 해당합니다. 용어 번역 "Stakeholder" (영어) — 이해관계자, 프로젝트에 관심이 있는 개인 또는 그룹. 데스크톱 모바일 집중력을 유지하고 효과적으로 기여하는 데 필요한 모든 것 실시간 제안 대화가 진행됨에 따라 맥락에 맞는 제안을 받으세요. 응답 아이디어, 핵심 포인트 리마인더, 설명이 가장 필요할 때 나타납니다. 설치 불필요 봇 없는 회의 어시스턴트인 LiveSuggest에 웹 브라우저에서 직접 접속하세요. 다운로드, 확장 프로그램, 복잡한 설정이 필요 없습니다. 몇 초 만에 시작하세요. 프라이버시 우선 설계 동의와 투명성을 핵심으로 구축되었습니다. 대화는 녹음 없이 실시간으로 처리되며 자동으로 삭제됩니다. 세션이 끝난 후에는 데이터가 보관되지 않습니다. 자주 묻는 질문 봇 없이 어떻게 작동하나요? LiveSuggest는 장치에서 직접 오디오를 캡처합니다 — 마이크 또는 브라우저 탭 오디오 공유를 통해. 봇이 통화에 참여하거나 참가자 목록에 표시되지 않습니다. 녹음 없이도 정확한가요? 예. 녹음 기반 도구와 동일한 고급 AI 모델을 사용합니다. 오디오는 실시간으로 처리되고 즉시 삭제됩니다 — 동일한 정확도, 더 강력한 개인정보 보호. 제안이 방해가 되지 않나요? 아니요. 제안은 필요할 때 확인하는 별도의 창에 나타납니다. 대화를 방해하지 않고 참여를 지원합니다. 작동 방식 1 세션 시작 브라우저에서 LiveSuggest를 열고 모든 참가자에게 알림이 전달되었는지 확인하세요. 청취 준비 완료 2 회의 참여 온라인 또는 대면으로 회의에 참여하세요. LiveSuggest가 실시간으로 듣고 전사합니다. 전사 중… 3 제안 받기 회의 내내 효과적으로 기여하기 위한 유용하고 맥락에 맞는 제안을 받으세요. 실시간 제안 4가지 맞춤형 제안 유형 회의 후속 조치 중요한 결정, 할 일, 담당자와 기한이 포함된 합의 사항을 기록하여 중요한 것을 놓치지 않습니다. 새로운 아이디어 토론을 풍부하게 하고 새로운 방향을 열어주는 관련 아이디어와 신선한 관점을 제안합니다. 용어 설명 대화에서 언급된 전문 용어, 약어, 복잡한 개념을 즉시 설명하여 놓치는 부분이 없도록 합니다. 용어 번역 외국어 표현을 즉석에서 번역하고 설명하여 언어에 관계없이 대화에 참여할 수 있습니다. 회의에 봇이 참가하지 않습니다 📹 Zoom 💼 Teams 🎥 Meet 👥 대면 모든 브라우저 기반 회의 플랫폼에서 작동 다른 AI 도구와 달리 LiveSuggest는 회의에 참가자를 추가하지 않습니다. Google Meet, Zoom, Microsoft Teams 또는 모든 브라우저 기반 플랫폼에서 원활하게 작동합니다. 탭 오디오를 공유하기만 하면 됩니다. 대면 회의에서는 마이크를 사용하세요. 요금제 선택 요구사항에 맞는 요금제를 선택하세요 🧾 비즈니스 청구서 발행 가능 Basic 가볍게 체험하기 좋은 $ 3 /월 부가세 별도 3 오디오 시간 ~6 회의 (30분 기준) 시작하기 ★ 추천 Plus 가장 인기 $ 8 /월 부가세 별도 10 오디오 시간 ~20 회의 (30분 기준) 8시간 가격으로 10시간 Plus 선택 Pro 파워 유저용 $ 20 /월 부가세 별도 30 오디오 시간 ~60 회의 (30분 기준) 20시간 가격으로 30시간 Pro로 전환 프라이버시 우선 설계 ✓ 동의와 투명성을 핵심으로 구축되었습니다. 대화는 녹음 없이 실시간으로 처리되며 자동으로 삭제됩니다. 세션이 끝난 후에는 데이터가 보관되지 않습니다. ✓ 오디오는 실시간으로 처리되며 저장되지 않습니다 ✓ 세션 데이터는 각 세션 종료 시 삭제됩니다 ✓ 개인정보 아무것도 놓치지 않고 회의에서 더 잘 기여할 준비가 되셨나요? LiveSuggest를 무료로 체험하세요 — 신용카드가 필요 없습니다. 봇이나 녹음 없이 실시간 AI 제안을 받으세요. 집중력을 유지하고 더 잘 기여하세요. 지금 무료로 시작하기 가격 보기 ✓ 신용카드 불필요 ✓ 가입 불필요 ✓ 1시간 무료 LiveSuggest 봇 없는 회의 어시스턴트로부터 말하면서 맥락에 맞는 제안을 받으세요 — 응답 아이디어, 핵심 포인트 알림, 명확화를 통해 외국어로 일할 때도 순간에 예리하게 대응할 수 있습니다. 제품 요금제 FAQ 블로그 법률 정보 개인정보 약관 법적 고지 동의 지원 연락처 버그 신고 © 2026 LiveSuggest. 모든 권리 보유. 이 사이트는 쿠키를 사용합니다 사이트의 올바른 작동을 보장하고 경험을 개선하기 위해 쿠키를 사용합니다. 모든 쿠키를 수락하거나 거부하거나 기본 설정을 사용자 지정할 수 있습니다. 모두 수락 모두 거부 사용자 지정 | 2026-01-13T08:48:04 |
https://www.ycombinator.com/interviews | YC Interview Guide | Y Combinator About What Happens at YC? Apply YC Interview Guide FAQ People YC Blog Companies Startup Directory Founder Directory Launch YC Startup Jobs All Jobs ◦ Engineering ◦ Operations ◦ Marketing ◦ Sales Internships Startup Job Guide YC Startup Jobs Blog Find a Co-Founder Library SAFE Resources Startup School Newsletter Requests for Startups For Investors Verify Founders Hacker News Bookface Open main menu Apply for X2026 batch. Apply YC Interview Guide If you've been invited to a YC interview, congratulations! We’ve designed YC interviews so that you don’t need to do much preparation. Here's what you need to know and what we recommend you do - and don’t do - to prepare. The Basics YC interviews are 10-minute conversations over Zoom. All founders should be present on the call. Expect 2-3 YC Partners to be on the call. Interviewers will have read your application and have it open during the call. Watch this Video We recommend watching this video by Dalton Caldwell, Group Partner at YC. He discusses what to expect in your interview and provides insights on what sets successful interviews apart. How to Prepare for Your YC Interview Because interviews are so short, there just isn’t time for small talk or formal presentations. We only do two things at interviews: we ask you questions, and we look at what you’ve built so far. Don’t rehearse Founders looking for an edge on how to get accepted into YC sometimes think that doing lots of interview preparation will help. However, beyond the basic preparation recommended here, it is not useful and is often counter-productive. You don’t need to do mock interview prep, and we prefer that you don’t prepare any kind of presentation. We sometimes notice that founders overprepare which does not increase the chances of their acceptance because it can make the interview more awkward. (For instance if founders start to answer a question that hasn’t even been fully asked yet.) There isn’t time for prepared speeches, slide presentations, or screencasts. We just want to have a conversation, and that works better when you are talking spontaneously. YC interviews can go in many different directions. So don’t worry if the interview doesn’t take the form you expected. Instead of rehearsing, make progress If you really want to improve your chances of getting into YC, the best way to get an edge is to work hard and have your startup improve between the time that you applied and the time that you interview. This may mean you launched, improved your product, increased revenue, etc. Demonstrating you can move fast and make quick progress is the most surefire way to impress your interviewers. Be ready to describe what your company does Typically the first question we ask is: What is your company working on? This is the most basic question an investor could ask, and yet you’d be surprised how many founders find it hard to answer clearly. Explain what you’re doing in a few simple, jargon-free sentences. We love learning new things. And a good startup idea usually teaches you something when you encounter it. Don’t worry if the new things about your idea are things only someone in your field would care about. We like that. We’d rather have interesting details than boring generalizations. Understand your users and metrics If you’re already launched, you should know everything you can about your users and your metrics. We’re impressed by startups who know a lot about their users, and can tell us what they learned. Here are some questions we often ask if you’ve launched: Where do new users come from? What is your growth like? How much are your users using the product, and do they stick around? What are your unit economics? What makes new users try you? Why do the reluctant ones hold back? What are the top things users want? What has surprised you about user behavior? If you already have users, it is helpful to have your key metrics written down someplace where you can quickly reference them during the interview. We don’t expect teams to have every little number memorized, and having them written down will free you from feeling like you have to. Please note that if you state numbers in the interview we may ask for verification of them afterwards. Don’t be afraid to be honest about challenges It will also be useful to think about obstacles in your path. We often ask about those and we tend to be more convinced by candid discussion of difficulties than glib dismissal of them. You’re going to face obstacles; every startup does. If you act as if there aren’t any, it will seem to us that you have overlooked them. We also don’t expect you to have all the answers. So if we ask a question you don’t know the answer to, don’t panic. A smart person trying sincerely to answer an unexpected question can lead to a great discussion. You should be intimately familiar with the existing products in your market, and what, specifically, is wrong with them. It’s not enough to say that you’re going to make something that’s more powerful, or easier to use. You should be able to explain how. Have a demo ready We sometimes will ask to see a demo of what you’re building. By demo, we mean a working version of whatever you’ve built or plan to build. If you have a working version of your product, be ready to show it. If it’s software, have it loaded up and ready to screenshare with us. If it’s hardware, have it physically with you and be prepared to show us on the call. If it can’t be in the room with you, have a demo video available. Make sure all founders are ready to participate For teams with multiple founders, we prefer if each founder answers at least one question, so we get to know all of you a bit. Be earnest The YC folks in your interview are likely the same people you'll work closely with should you be accepted. Interviews are a way for us to identify teams we are looking forward to going through a long journey with, and the more we feel confident that our conversation is sincere, straightforward and natural, the better. Post-Interview Feedback If your team is not selected after the interview, we’ll give you feedback over email. Our aim is to offer genuinely useful advice that will make you more likely to succeed. It’s very common for teams to take our feedback, re-apply the following batch and get accepted. Useful Links More advice on interviews from the YC community: Tips for YC Interviews by Jessica Livingston, YC Founding Partner 3 Tips to Nail the Y Combinator Interview by Garry Tan, YC President and CEO My 10 pieces of advice for preparing for a YC interview by Michael Seibel, YC Group Partner Footer Y Combinator Programs YC Program Startup School Work at a Startup Co-Founder Matching Company YC Blog Contact Press People Careers Privacy Policy Notice at Collection Security Terms of Use Resources Startup Directory Startup Library Investors SAFE Hacker News Launch YC YC Deals Make something people want. Apply Twitter Twitter Facebook Facebook Instagram Instagram LinkedIn LinkedIn Youtube YouTube © 2026 Y Combinator | 2026-01-13T08:48:04 |
https://github.com/skills/github-pages | GitHub - skills/github-pages: Create a site or blog from your GitHub repositories with GitHub Pages. 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 / github-pages Public template generated from skills/exercise-template Notifications You must be signed in to change notification settings Fork 9.1k Star 2.9k Create a site or blog from your GitHub repositories with GitHub Pages. License MIT license 2.9k stars 9.1k forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 20 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/github-pages 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 54 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 GitHub Pages Create a site or blog from your GitHub repositories with GitHub Pages. Welcome With GitHub Pages, you can host project blogs, documentation, resumes, portfolios, or any other static content you'd like. Your GitHub repository can easily become its own website. In this course, we'll show you how to set up your own site or blog using GitHub Pages. Who is this for : Beginners, students, project maintainers, small businesses. What you'll learn : How to build a GitHub Pages site. What you'll build : We'll build a simple GitHub Pages site with a blog. We'll use Jekyll , a static site generator. Prerequisites : If you need to learn about branches, commits, and pull requests, take Introduction to GitHub first. How long : This course takes less than one hour to complete. In this course, you will: Enable GitHub Pages Configure your site Customize your home page Create a blog post 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 a site or blog from your GitHub repositories with GitHub Pages. Topics pages github-pages 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 2.9k stars Watchers 405 watching Forks 9.1k forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 14 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.highlight.io/customers/bci | How Blue Cross of Idaho Uses Highlight.io for Auditing & Troubleshooting Star us on GitHub Star Migrate your Highlight account to LaunchDarkly by February 28, 2026. Learn more on our blog. Product Integrations Pricing Resources Docs Sign in Sign up All customers Customer Case Study How Blue Cross of Idaho Uses Highlight.io for Auditing & Troubleshooting We’re excited to showcase one of our early partners, Blue Cross of Idaho, an industry leading healthcare insurance provider, that uses Highlight for troubleshooting and auditing. Before integrating Highlight.io, Blue Cross of Idaho (BCI) faced a few operational challenges regarding their customer-facing insurance portals. They lacked real-time data on how users were using their web applications, leading to slow issue resolution. They also had legacy workflows for auditing that no longer fit the fast-paced digital transformation they undertook. The BCI team initially discovered Highlight through our open source presence. Integrating the product in days, the BCI team quickly saw value in being able to troubleshoot customer-facing issues and efficiently audit their applications. “ Highlight.io was incredibly easy to adopt, and their team moves extremely fast. We’re getting to the root causes of issues in a tenth of the time that is used to take us; the value here is insurmountable. ” Abraham Soto , Blue Cross Idaho Debugging and Troubleshooting Customer-facing Portals At Blue Cross of Idaho (BCI), ensuring seamless user experiences across their digital portals is paramount. Abraham Soto, Director of Innovation at BCI, emphasizes the critical role session replay plays in their debugging and troubleshooting efforts. “ With Highlight.io, pinpointing and resolving issues within our portals has never been more efficient. ” Abraham Soto , Blue Cross Idaho The platform's intuitive interface and comprehensive replay capabilities empower BCI's team to identify and address user experience bottlenecks swiftly. Whether it's a frontend glitch or a backend issue, Highlight.io equips BCI with the insights needed to maintain optimal portal performance. Sending User Audits to the Blue Cross Parent Association (BCBSA) Beyond internal operations, BCI leverages Highlight.io to uphold compliance standards and transparency obligations with their parent association, Blue Cross Blue Shield Association (BCBSA). “ Highlight.io enables us to conduct thorough user audits and seamlessly share them with the BCBSA. The ability to effortlessly generate and transmit user audits enhances our accountability and strengthens our partnership with BCBSA. ” Abraham Soto , Blue Cross Idaho By leveraging session replay technology, BCI can provide detailed user interaction records, ensuring alignment with BCBSA's guidelines and regulations. Closing Thoughts In conclusion, Highlight.io serves as an indispensable tool in BCI's digital strategy, facilitating both internal optimization and external compliance efforts. “ The implementation of Highlight.io has revolutionized our approach to auditing and troubleshooting. Its user-friendly interface and rapid insights delivery have exceeded our expectations. ” Abraham Soto , Blue Cross Idaho Moving forward, BCI remains committed to leveraging session replay technology to drive continuous improvement and deliver unparalleled user experiences within their ecosystem, and we are always finding ways to expand our partnership with their team. Our next project extends beyond frontend web monitoring to integrate server logs in session replays, giving full stack observability for even faster troubleshooting. Overall, it’s been incredible to work with Abraham and the team at BCI. We’re excited to continue the partnership. Previous Customer About the company An industry-leading healthcare insurance provider. Founded 1945 Using Highlight since Jan 2023 Try Highlight Today Get the visibility you need Get started for free Product Pricing Sign up Features Privacy & Security Customers Session Replay Error Monitoring Logging Competitors LogRocket Hotjar Fullstory Smartlook Inspectlet Datadog Sentry Site24x7 Sprig Mouseflow Pendo Heap LogicMonitor Last9 Axiom Better Stack HyperDX Dash0 Developers Changelog Documentation Ambassadors Frameworks React Next.js Angular Gatsby.js Svelte.js Vue.js Express Golang Next.js Node.js Rails Hono Contact & Legal Terms of Service Privacy Policy Careers sales@highlight.io security@highlight.io [object Object] | 2026-01-13T08:48:04 |
https://forem.com/t/nintendoswitch/page/6 | Nintendoswitch Page 6 - 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 3 4 5 6 7 8 9 10 11 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu IGN: Dragon Quest 1+2 HD 2D Remake: Game Length, Princess of Cannock, & Tombola | gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 23 '25 IGN: Dragon Quest 1+2 HD 2D Remake: Game Length, Princess of Cannock, & Tombola | gamescom 2025 # gamedev # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Dragon Quest 1+2 HD 2D Remake: Game Length, Princess of Cannock, & Tombola | gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 23 '25 IGN: Dragon Quest 1+2 HD 2D Remake: Game Length, Princess of Cannock, & Tombola | gamescom 2025 # playstation # xbox # nintendoswitch # pcgaming Comments Add Comment 1 min read IGN: Metroid Prime 4: Beyond Gameplay (Off-Screen) | gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 23 '25 IGN: Metroid Prime 4: Beyond Gameplay (Off-Screen) | gamescom 2025 # nintendo # nintendoswitch Comments Add Comment 1 min read IGN: Dragon Quest 1+2 HD 2D Remake: Game Length, Princess of Cannock, & Tombola | gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 23 '25 IGN: Dragon Quest 1+2 HD 2D Remake: Game Length, Princess of Cannock, & Tombola | gamescom 2025 # gamedev # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: NBA 2K26 - Official Live Action Trailer (Ft. Spike Lee) Gaming News Gaming News Gaming News Follow Aug 23 '25 IGN: NBA 2K26 - Official Live Action Trailer (Ft. Spike Lee) # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Borderlands 4 - Official Harlowe Gameplay Overview Trailer Gaming News Gaming News Gaming News Follow Aug 22 '25 IGN: Borderlands 4 - Official Harlowe Gameplay Overview Trailer # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read GameSpot: Kirby Air Riders Is Faster, Deeper, and Cleaner Than The Original Gaming News Gaming News Gaming News Follow Aug 22 '25 GameSpot: Kirby Air Riders Is Faster, Deeper, and Cleaner Than The Original # nintendo # nintendoswitch # retrogaming Comments Add Comment 1 min read IGN: Hollow Knight: Silksong Release Date Trailer Reaction Livestream | gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 21 '25 IGN: Hollow Knight: Silksong Release Date Trailer Reaction Livestream | gamescom 2025 # indie # nintendoswitch # pcgaming # xbox Comments Add Comment 1 min read IGN: Mortal Kombat: Legacy Kollection - Official Mythologies & Special Forces Trailer | gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 21 '25 IGN: Mortal Kombat: Legacy Kollection - Official Mythologies & Special Forces Trailer | gamescom 2025 # retrogaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read GameSpot: Kirby Air Riders City Trial Meta Knight Gameplay (Off Screen Filmed Footage) Gaming News Gaming News Gaming News Follow Aug 21 '25 GameSpot: Kirby Air Riders City Trial Meta Knight Gameplay (Off Screen Filmed Footage) # nintendo # nintendoswitch # pcgaming Comments Add Comment 1 min read IGN: Overwatch 2 - Official Season 18 Quick Play Trailer | Xbox @ gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 21 '25 IGN: Overwatch 2 - Official Season 18 Quick Play Trailer | Xbox @ gamescom 2025 # xbox # playstation # nintendoswitch # pcgaming Comments Add Comment 1 min read GameSpot: Lego Batman: Legacy Of The Dark Knight Hands-on Impressions Gaming News Gaming News Gaming News Follow Aug 21 '25 GameSpot: Lego Batman: Legacy Of The Dark Knight Hands-on Impressions # pcgaming # xbox # playstation # nintendoswitch Comments Add Comment 1 min read GameSpot: Hollow Knight: Silksong - Official Release Date Reveal Gameplay Trailer Gaming News Gaming News Gaming News Follow Aug 21 '25 GameSpot: Hollow Knight: Silksong - Official Release Date Reveal Gameplay Trailer # indie # pcgaming # nintendoswitch # playstation Comments Add Comment 1 min read IGN: Bye Sweet Carole - Official Release Date Trailer | gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 21 '25 IGN: Bye Sweet Carole - Official Release Date Trailer | gamescom 2025 # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Overwatch 2 - Official 'Elemental Kin' Wuyang Hero Trailer | Xbox @ gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 21 '25 IGN: Overwatch 2 - Official 'Elemental Kin' Wuyang Hero Trailer | Xbox @ gamescom 2025 # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Black Ops 7 Devs Respond to 'Lazy' Call of Duty Accusations - IGN Daily Fix Gaming News Gaming News Gaming News Follow Aug 20 '25 IGN: Black Ops 7 Devs Respond to 'Lazy' Call of Duty Accusations - IGN Daily Fix # pcgaming # xbox # nintendoswitch # gamedev Comments Add Comment 1 min read IGN: Little Nightmares 3 - Official 'The Carnevale' Commented Gameplay Trailer | gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 20 '25 IGN: Little Nightmares 3 - Official 'The Carnevale' Commented Gameplay Trailer | gamescom 2025 # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: Pokemon Legends: Z-A - Official 'The Case of the Sweet Scent Incident' Trailer Gaming News Gaming News Gaming News Follow Aug 21 '25 IGN: Pokemon Legends: Z-A - Official 'The Case of the Sweet Scent Incident' Trailer # nintendo # nintendoswitch # gaming Comments Add Comment 1 min read GameSpot: Hollow Knight: Silksong Gameplay (Over The Shoulder Filmed) | gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 20 '25 GameSpot: Hollow Knight: Silksong Gameplay (Over The Shoulder Filmed) | gamescom 2025 # pcgaming # indie # nintendoswitch Comments Add Comment 1 min read IGN: Lost Hellden - Official Gameplay Trailer | gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 20 '25 IGN: Lost Hellden - Official Gameplay Trailer | gamescom 2025 # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: LEGO Batman: Legacy of the Dark Knight Gameplay Gaming News Gaming News Gaming News Follow Aug 20 '25 IGN: LEGO Batman: Legacy of the Dark Knight Gameplay # pcgaming # playstation # xbox # nintendoswitch Comments Add Comment 1 min read IGN: The Darkest Files - Gamescom Trailer | gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 20 '25 IGN: The Darkest Files - Gamescom Trailer | gamescom 2025 # gamedev # pcgaming # steam # nintendoswitch Comments Add Comment 1 min read IGN: I Hate This Place - Official Release Date Trailer | gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 20 '25 IGN: I Hate This Place - Official Release Date Trailer | gamescom 2025 # gamedev # pcgaming # indie # nintendoswitch Comments Add Comment 1 min read IGN: Elden Ring on Switch 2 Is a Disaster in Handheld Mode | gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 20 '25 IGN: Elden Ring on Switch 2 Is a Disaster in Handheld Mode | gamescom 2025 # nintendo # nintendoswitch # pcgaming # gamedev Comments Add Comment 1 min read IGN: Borderlands 4 Has The Weirdest Weapons You'll Ever See | gamescom 2025 Gaming News Gaming News Gaming News Follow Aug 20 '25 IGN: Borderlands 4 Has The Weirdest Weapons You'll Ever See | gamescom 2025 # 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://lab174.com/blog/202601-yaml-norway/#cb4-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://music.forem.com/t/ambientmusic | Ambientmusic - 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 # ambientmusic Follow Hide ethereal soundscapes to chill 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 Marconi Union - Weightless. World’s Most Relaxing Song? Mikey Dorje Mikey Dorje Mikey Dorje Follow Apr 12 '25 Marconi Union - Weightless. World’s Most Relaxing Song? # discuss # ambientmusic # neuroscience 6 reactions Comments 2 comments 1 min read loading... trending guides/resources Why *Dhurandhar* Movie Songs Feel So Awesome 🎶 💎 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://cssence.com/latest/ | Latest posts - CSSence.com Most recent A “short” timeline of the latest blog posts. Index January 8, 2026 While you can always head to the archive and browse by year, this index page is a shortcut, as it shows the latest posts across years and blog post types. Basically what you get if you combined Articles and Threads and took the twelve most recent ones. Why isn’t the following list also shown on the home page? The home page displays the latest entry of every blog post type, so that each type appears exactly once, to prevent certain types from being overly represented. Over here on “Latest” the entries are chronological, you see the posts as they happen. Latest posts Text-based web browsers How do they fare with (not so) recent additions to HTML? Essay January 8, 2026 Safeguarded hyphenation Tweaking things with hyphenate-limit-chars is (almost) possible. Link January 2, 2026 Style Queries FTW! Warning: Limited availability across major browsers. Note January 1, 2026 MathML Manuel Sánchez created and contributed to an Advent Calendar. Link December 21, 2025 Accessibility is personal Is A11Y work rewarding? Demanding? Exhausting? All of the above? Essay December 19, 2025 Favorite websites Sites I visit whenever I need inspiration. Note December 4, 2025 @import ⚭ @supports How to load a stylesheet conditionally based on feature detection. Extra December 3, 2025 Baseline baseline Roma Komarov proposed a potential future for baseline alignment. Link November 9, 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 What’s my screen resolution? Kilian Valkhof asks if a better test site would be welcome. Spoiler: Yes. Note October 22, 2025 What’s the size of the box? Should we circle back to the original box model? Link October 22, 2025 The list above contains only the twelve most recent entries. 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/latest/ 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/2024/native-visually-hidden/ | Native visually hidden - CSSence.com Native visually hidden Essay April 10, 2024 Another CSS Naked Day is about to end. Once again it’s been a delight to find like-minded people by following the #CssNakedDay and #css_naked_day hashtags. Line length has been the only downside of the day, but even that could’ve been mitigated by looking at sites on mobile only. Some people admitted to cheating. Usually for a good cause, e.g. charts that would otherwise have been inaccessible. On one site however (I forgot which) it was about something as simple as keeping the styles for the .visually-hidden class in. This reminded me of last year’s debate whether we need a native visually hidden in HTML or CSS. So I did some searching online, and collected the results by compiling a list of links, because without doing that I’m fairly certain I’ll end up doing the same search next year. In a nutshell, good points have been made on both sides. Proponents usually argue this is such an established pattern, and universally needed, so the way to style it shouldn’t be a mess. But it is, and always has been, even back when we still called it .sr-only . Their point is, a CSS one-liner would certainly help. The biggest counterargument is that .visually-hidden is a code smell for not-so-great design: How about *not* hiding the content for *everyone* in the first place? All in favor I think it was Ben Myers who started the debate by making the initial case for it: »Native visually hidden« . Ben’s pal W. Evan Sheehan followed up with his thoughtful take: »Web Native “Visually Hidden”« . Even though not part of last year’s debate, this list wouldn’t be complete without mentioning »Inclusively hidden« by Scott O’Hara, which he wrote in 2017. All opposed I only brought up Scott to bring him in again on this side. He wrote so so many words , and those words ended up being the poster-child argument against a native way: »Visually hidden content is a hack that needs to be resolved, not enshrined« . Conclusion? None. I’m torn too. The debate will continue. Let me end this piece with some neutral information. In Bootstrap (at least in versions 3, 4 and 5), you’ll find a helper class to hide content visually. James Edwards wrote about »The anatomy of visually hidden« . His article contains a reference to a discovery by Manuel Matuzović: »Visually hidden links with 0 dimensions« . Comments Matthias Zöchling wrote on April 10, 2024 at 07:19 Another CSS Naked Day is about to end. Once again it’s been a delight to find like-minded people by following the #CssNakedDay and #css_naked_day hashtags. Line length has been the only downside of the day, but even that could’ve been mitigated by looking at sites on mobile only. Some people admitted to cheating. Usually for a good cause, e.g. charts that would otherwise have been inaccessible. On one site however (I forgot which) it was about something as simple as … — cssence.com/2024/native-visually-hidden Roma Komarov wrote on April 10, 2024 at 10:22 And another quick example, after reading today’s post by @CSSence. A visually-hidden CSS mixin: codepen.io/kizu/pen/PogeBNd Took the code from @ben@a11y.info, and wrapped it with my layered toggles. Now, just adding --visually: var(--hidden); to any element makes it visually hidden. Matthias Zöchling wrote on April 10, 2024 at 11:32 In reply to: @kizu@front-end.social . Oh my goodness, you keep churning out next-level stuff. I still have the tab open with your original post that I haven’t read yet. And another tab with that ellipsis thing from @hi_mayank@hachyderm.io, it all seems to be 🤯. Michael Gehrmann wrote on December 8, 2024 at 08:54 .visually-hidden , a code smell for not-so-great design? It feels conflicting. But it ties in with some discussions I have had recently. Essentially, visual and auditory perception of content can be quite different. For me, “visually hidden” works like the counterpart of decorative image patterns. Matthias Zöchling wrote on December 8, 2024 at 09:18 In reply to: @g12n.de . Essentially, visual and auditory perception of content can be quite different. Nicely put. I’ll admit that .visually-hidden has its uses. Michael Gehrmann wrote on December 8, 2024 at 10:47 In reply to: @cssence.com . We can be a bit kinder to ourselves sometimes. The web is the only medium that tries to be universally accessible. For any human and even robots. Get involved Have your say on Mastodon, or simply share this article. About this article Written by Matthias Zöchling. Published on April 10, 2024 . Permalink: https://cssence.com/2024/native-visually-hidden/ 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://www.finalroundai.com/blog/yoshua-bengio-ai-jobs-robotics | Godfather of AI Explains How AI Takes Your Job In 5 Years Promotion title Promotion description Button Text Interview Copilot AI Application AI Resume Builder Auto Apply AI Resume Builder Auto Apply AI Mock Interview Pricing Resources Resume Creation Tools Recruiters Hotline Resume Checker Cover Letter Generator Career Guidance Tools AI Career Coach LinkedIn Profile Optimizer LinkedIn Resume Builder Support Guides Blog Articles Resume Creation Tools Recruiters Hotline Resume Checker Cover Letter Generator Career Guidance Tools AI Career Coach LinkedIn Profile Optimizer LinkedIn Resume Builder Support Guides Blog Articles Question bank Sign In Sign Up Interview Copilot AI Application AI Resume Builder Auto Apply AI Mock Interview Pricing Resources Resume Creation Tools Recruiters Hotline Resume Checker Cover Letter Generator Career Guidance Tools AI Career Coach LinkedIn Profile Optimizer LinkedIn Resume Builder Support Guides Blog Articles 🔥 Question Bank Sign In Home > Blog > News Home > Blog > News Godfather of AI Explains How AI Takes Your Job In 5 Years AI Godfather Yoshua Bengio explains how rapid advances in AI could replace human jobs within five years. Written by Kaustubh Saini Edited by Jaya Muvania Reviewed by Kaivan Dave Updated on Dec 19, 2025 Read time 4 min read Comments https://www.finalroundai.com/blog/yoshua-bengio-ai-jobs-robotics Link copied! For the last couple of years, AI has been talked about in two very different ways. Either it’s going to boost productivity like crazy, or it’s going to make everyone jobless. “Godfather of AI” Yoshua Bengio weighs heavily on the latter side. Yoshua Bengio’s 5 Year Prediction on AI Taking Jobs Yoshua Bengio was recently the guest on The Diary of a CEO podcast, where he explained his growing concern about how fast AI is advancing and the serious risks that could come with it. Bengio is a one of the most influential figures in modern AI, for his research in deep learning and neural networks. He recently became the first living scientist to surpass one million citations on Google Scholar. His foundational work him the 2018 ACM A.M. Turing Award, alongside fellow AI pioneers Geoffrey Hinton and Yann LeCun, often called the three “Godfathers of AI". Geoffrey Hinton has also warned that AI could soon replace mid-level programmers and shared similar concerns on AI’s influence on the human society. Host Steven Bartlett asked him about his prediction on AI will be able to do most of the jobs int the next 5 years, which means before the end of this decade. Yoshua replied: “We are starting to see a shift that may be due to AI, even though on the average aggregate of the whole population, it doesn’t seem to have any effect yet. So I think it’s plausible we’re going to see in some places where AI can really take on more of the work. But in my opinion, it’s just a matter of time. If, unless we hit a wall scientifically, like some obstacle that prevents us from making progress to make AIs smarter and smarter, there’s going to be a time when they’ll be doing more and more, able to do more and more of the work that people do. And then, of course, it takes years for companies to really integrate that into their workflows, but they’re eager to do it. So it’s more a matter of time than, you know, is it happening or not?” AI is already starting to affect jobs , but it’s happening so quietly that it doesn’t show up clearly in big, national numbers yet.. He believes this trend will spread as AI gets better at doing real work. Cognitive Jobs first, Labor Jobs Next Yoshua Bengio believes that AI will be capable of performing most cognitive jobs in the near future, and eventually physical jobs as robotics advances. Industrial machines replaced physical labor. Computers sped up paperwork. The internet reshaped communication. In each case, human thinking remained essential. AI is different. Modern AI systems are now capable of doing tasks that once required years of education and experience. Writing, analysis, programming, customer service, design, and legal research. They are the backbone of modern white-collar work. Recently, Stuart Russell also shared similar concerns on how AI could massively disrupt jobs and society . Bengio argues that once AI becomes good enough to handle most keyboard-based tasks, the economic logic becomes unavoidable. Cognitive jobs will be hit first (it’s happening already) and then robotics will catch up. “Robotics is still lagging also, although we’re seeing progress. So if you do a physical job, as Geoff Hinton is often saying, you should be a plumber or something, it’s going to take more time, but I think it’s only a temporary thing. Why is it that robotics is lagging compared to doing physical things, compared to doing more intellectual things that you can do behind a computer? One possible reason is simply that we don’t have the very large data sets that exist with the Internet, where we see so much of our cultural outputs, intellectual output, but there’s no such thing for robots yet. But as companies are deploying more and more robots, they will be collecting more and more data. So eventually, I think it’s going to happen.” What Yoshua Bengio means is that AI is currently much better at intellectual tasks than physical ones. This is why AI has advanced so quickly in areas like writing, programming, and analysis. Robotics, on the other hand, deals with the physical world, which is far more harder to model. There is no massive dataset that captures how millions of people perform physical tasks. Because of this lack of data, robots struggle with things humans find simple. However, as more robots are deployed in real world, they will start collecting large amounts of real-world experience data. Over time, this will allow robots to learn and improve much faster, just as AI systems trained on internet data did. In Bengio’s view, once that data gap closes, robots will also begin catching up, and physical jobs may eventually face the same pressures as white-collar ones. Bengio’s concern goes beyond employment. If AI massively boosts productivity, the rewards will not be shared equally by default. They will flow to those who own and control the systems. “So you could imagine a corporation dominating economically the rest of the world because they have more advanced AI. You could imagine a country dominating the rest of the world politically, militarily, because they have more advanced AI.” But companies are incentivized to move fast, not cautiously. They are investing heavily right now in AI to increase their profit magins. “Right now, where are they all racing? They’re racing towards replacing jobs that people do because there’s quadrillions of dollars to be made by doing that.” These profits is the reasons AI companies are neglecting AI safety. Bengio notes that more advanced models are showing an increased tendency towards "bad behavior" that goes against human instructions. Bottom Line Bengio’s message is pretty clear but also, uncomfortable. AI is moving way faster than most people realize, and the risks aren’t just about job losses. We’re heading toward systems that can act on their own, influence people, and concentrate huge amounts of power in very few hands. Safety measures today are mostly patchwork and not keeping up with how capable these models are becoming. Bengio isn’t saying we should panic, but he is saying we need to slow down and rethink how AI is trained. Upgrade your resume! Create a hireable resume with just one click and stand out to recruiters. Upload Your Resume Now ← Back to all articles Table of Contents Example H2 Example H3 Ace Your Next Interview with Confidence Unlock personalized guidance and perfect your responses with Final Round AI, ensuring you stand out and succeed in every interview. Get Started Free Related articles Oracle laid off over 3,000 staff worldwide through WARN filings, no public statement News • Kaustubh Saini Oracle laid off over 3,000 staff worldwide through WARN filings, no public statement Oracle quietly eliminated over 3,000 jobs across US, India, Philippines and Canada through state WARN filings, with no official company announcement about the massive workforce reduction amid AI restructuring. 5 Industries That Are Most Affected by AI in 2025 News • Kaustubh Saini 5 Industries That Are Most Affected by AI in 2025 Here are 5 industries where job postings have decreased massively in 2025, and why AI is the main reason for these job losses. Amazon Layoffs: 40% of Recent Job Cuts Target Engineers News • Kaustubh Saini Amazon Layoffs: 40% of Recent Job Cuts Target Engineers Official notices on Amazon’s latest layoffs revealed that 40% of their recent job cuts in October hit engineering roles more. PepsiCo Plans Major Layoffs in US and Canada News • Kaustubh Saini PepsiCo Plans Major Layoffs in US and Canada PepsiCo is preparing major layoffs in the US and Canada as part of a broad restructuring that includes supply-chain changes and product cuts. 12 White-Collar Jobs Most at Risk from AI in 2025 News • Kaustubh Saini 12 White-Collar Jobs Most at Risk from AI in 2025 AI is replacing white-collar workers faster than anyone predicted. Companies are cutting entire departments. Check if your job is among the 12 at highest risk. Indeed, Glassdoor to cut 1,300 jobs as parent company invests in AI News • Kaustubh Saini Indeed, Glassdoor to cut 1,300 jobs as parent company invests in AI Indeed and Glassdoor to cut 1,300 jobs as parent company Recruit Holdings invests heavily in AI. Layoffs target R&D and operations teams amid platform consolidation strategy. Read All Articles Your trusted platform to ace any job interviews, craft the perfect resumes, and land your dream jobs. All services are online Products Interview Copilot AI Mock Interview AI Resume Builder Hirevue Phone Interview Speech Analysis College Admission Auto Apply QA Pairs Interview Notes Coding Copilot Resources Tutorials Blog Articles Special Discount Influencer Program Smarter Choice Support FAQ Contact Us Company How Final Round AI works About Careers News PR & Media Referral Program AI Tools AI Career Coach Recruiters Hotline Cover Letter Generator LinkedIn Profile Optimizer LinkedIn Resume Builder Resume Checker © 2025 Final Round AI, 643 Teresita Blvd, San Francisco, CA 94127 Privacy Policy Terms & Conditions Try Mock Interview Now | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb1-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://lab174.com/blog/202601-yaml-norway/#cb1-6 | 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://cssence.com/rss/ | RSS feeds - CSSence.com RSS feeds Subscribers welcome! Internal January 2, 2026 Tl;dr, just take me to the available feeds. Good to know What’s RSS? What’s a feed? Learn more at aboutfeeds.com. Introduction The list below contains all RSS feeds available on this site. You may subscribe to an individual feed, multiple feeds, or whatever makes sense for you. Feeds contain only the twelve newest blog posts, either across all sections, or limited to a particular section. If you’ve seen the navigation at the bottom of this page, or the Big Table on the archive page, said sections should be familiar. No rule without exceptions, let’s talk about the 🐘 in the room: The first entry in the list goes beyond newest posts, and instead contains all blog posts ever written. And then there is also one oddball in the list, because even the RSS feeds differentiate between Recent and Latest : While the latter simply contains the twelve newest entries across all sections, the former makes sure that two entries from all six sections are presented. If you are a first-time visitor I recommend you subscribe to the Recent feed. It will make a difference initially, but down the road you see the same updates as those who subscribe to Latest. Finally, I have a special offer if you don’t want to get too invested: Subscribe only until the end of the year . Your subscription will end automatically, no strings attached. You can always come back to this page and subscribe for another year. Previous years are there too, obviously those feeds are no longer updated, but maybe you feel nostalgic. 🙂 Available feeds All (large file, choose one below instead) Recent Latest Articles Editorials Essays Events Extras Threads Notes Links 2026 Previous years 2025 2024 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 2010 About this page Written by Matthias Zöchling. Last revised on January 2, 2026 . Permalink: https://cssence.com/rss/ 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://www.highlight.io/customers/life_at | How Highlight Enables LifeAt to Proactively Manage their Products Star us on GitHub Star Migrate your Highlight account to LaunchDarkly by February 28, 2026. Learn more on our blog. Product Integrations Pricing Resources Docs Sign in Sign up All customers Customer Case Study How Highlight Enables LifeAt to Proactively Manage their Products Enhancing Front-End Reliability LifeAt faced challenges in diagnosing and understanding front-end errors across their application and their existing tools were inadequate for delving into the complexities of a users’ interactions, particularly for a front-end heavy application. Highlight.io’s session recording and error logging capabilities provided LifeAt with the insights needed to address these challenges. The tool’s ability to correlate user behavior with front-end errors enabled LifeAt to quickly identify and address issues. “ Highlight.io was a game-changer for us, offering an in-depth view of user interactions and simplifying the process of replicating and resolving errors. ” Pouya Rad , LifeAt To learn more about Highlight's product philosophy and how we support you best, refer to our documentation on the subject. Seamless Implementation and Usage The implementation of Highlight.io was described as “super easy” by the CTO, with a straightforward setup process and clean documentation. The simplicity of integration, combined with the robustness of the tool, made it an ideal choice for LifeAt. “ Highlight.io’s two-liner implementation process was incredibly user-friendly, making it an obvious choice for us to enhance our front-end error tracking. ” Pouya Rad , LifeAt Ready to get started? Check out our implementation guides . Proactive and Efficient Error Management Since adopting Highlight.io, LifeAt has seen a significant reduction in the time spent identifying and resolving errors. The tool’s intuitive session filtering and playback functionality have made it easier for both technical and non-technical team members to proactively address user issues rather than waiting on users to write in their issues. “ With Highlight.io, we shifted from a reactive to a proactive approach in managing front-end issues, greatly enhancing our operational efficiency. ” Pouya Rad , LifeAt Get the most out of Highlight with alerts . Future Plans and Aspirations LifeAt aims to further integrate Highlight.io into their operations, expanding its use to connect full-stack error observability. This step is seen as crucial in continuing to enhance their product's reliability and user experience. “ We are excited to further leverage Highlight.io’s capabilities to create a more robust and error-resilient product for our users. ” Pouya Rad , LifeAt Previous Customer Next Customer About the company Prevents focus drift by making productivity management simple, so users can spend more time doing actual work Founded 2021 Using Highlight since Dec 2022 Try Highlight Today Get the visibility you need Get started for free Product Pricing Sign up Features Privacy & Security Customers Session Replay Error Monitoring Logging Competitors LogRocket Hotjar Fullstory Smartlook Inspectlet Datadog Sentry Site24x7 Sprig Mouseflow Pendo Heap LogicMonitor Last9 Axiom Better Stack HyperDX Dash0 Developers Changelog Documentation Ambassadors Frameworks React Next.js Angular Gatsby.js Svelte.js Vue.js Express Golang Next.js Node.js Rails Hono Contact & Legal Terms of Service Privacy Policy Careers sales@highlight.io security@highlight.io [object Object] | 2026-01-13T08:48:04 |
https://cssence.com/imprint/ | Imprint - CSSence.com Imprint Mandatory information. Internal December 20, 2022 On this page Privacy Policy License Legal Notice Accessibility Statement Privacy Policy This site values your privacy . Tracking No cookies 🍪 are used and no data is being collected while visiting this website, hence no reason to opt out of tracking. If you still believe that your rights with respect to your privacy have been violated, it would be recommended to get in touch first, but you can also file an official complaint at the Austrian data protection agency (“Datenschutzbehörde”) . License Unless stated otherwise, all content and code by Matthias Zöchling, available as open source on GitHub . Content under creative commons (CC BY 4.0) and code under MIT license (MIT) . Legal Notice Contact Published by: Matthias Zöchling Göttweiger Straße 19 3121 Karlstetten Austria You can contact the author Matt via e-mail, the address is legal (at) this domain . Accountability The content on this site has been created and published with utmost care. However, there is no guarantee about the contents’ completeness or accuracy. Links to external websites This site has no control over the contents of external links. Therefore the responsibility lies completely with the operators of those linked sites. While creating the content for this site and doing research on those external resources, no evident violations were found, but in case the author is informed of any violations afterwards, the respective link will be removed. Accessibility Statement This website attempts to be usable by the widest possible audience. To do so, this website has been tested on a variety of modern browsers, and occasionally on older browsers. Tests include viewing pages with a zoom level of 400%, and under High Contrast Mode. After major changes, pages are navigated with screen reader software such as VoiceOver and NVDA. If you still encounter issues, please send an e-mail to accessibility (at) this domain . About this page Written by Matthias Zöchling. Last revised on December 20, 2022 . Permalink: https://cssence.com/imprint/ 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://bizarro.dev.to/sofia_carter_d7be84dec7e4/comment/326ob | Świetny odcinek! Bardzo ciekawe podsumowanie nowości o Facebooku, Apple i AI ... - ALTERNATE UNIVERSE DEV 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 ALTERNATE UNIVERSE DEV Close Discussion on: ICD Weekend #25 – Facebook podsłuchuje Snapchata • nowe sposoby na oszukiwanie AI View post Collapse Expand Sofia Carter Sofia Carter Sofia Carter Follow Joined Nov 4, 2025 • Nov 4 '25 Dropdown menu Copy link Hide Świetny odcinek! Bardzo ciekawe podsumowanie nowości o Facebooku, Apple i AI — szczególnie spodobały mi się rekomendacje z F-Droida. Wasze rozmowy zawsze mają świetny balans między wiedzą a luzem, trochę jak strategiczne podejście w 3patti land , gdzie każda decyzja ma znaczenie. Czekam na kolejny sezon! Like comment: Like comment: 2 likes Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse 💎 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 ALTERNATE UNIVERSE DEV — A constructive and inclusive social network for software developers. With you every step of your journey. 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 . ALTERNATE UNIVERSE DEV © 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://addons.mozilla.org/es-CL/firefox/addon/rentgen/ | Rentgen – Consigue esta extensión para 🦊 Firefox (es-CL) Buscador de complementos para Firefox Extensiones Temas Más... para Firefox Diccionarios y paquetes de idiomas Otros sitios de navegadores Complementos para Android Conectarse Buscar Buscar Rentgen por “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 revisiones) 5 (12 revisiones) 216 usuarios 216 usuarios Descarga Firefox y obtiene la extensión Descargar archivo Metadata de la extensión Capturas de pantalla Sobre esta extensión 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 Comentarios del desarrollador 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 Calificado 5 por 12 revisores Inicia sesión para evaluar esta extensión Todavía no hay valoraciones Se guardó la valoración 5 12 4 0 3 0 2 0 1 0 Leer las 12 revisiones Permisos y datos Permisos requeridos: Leer y modificar los ajustes de privacidad Controlar configuración proxy del navegador Acceder a tus datos para todos los sitios web Recolección de datos: El desarrollador dice que esta extensión no requiere recolección de datos. Saber más Más información Enlaces del complemento Página de inicio Ayuda del sitio Correo de ayuda Versión 0.2.4 Tamaño 9,55 MB Última actualización hace 21 días (23 de dic. de 2025) Categorías relacionadas Desarrollo web Privacidad y seguridad Licencia Solo Licencia Pública General de GNU v3.0 Política de privacidad Leer la política de privacidad de este complemento Historial de versiones Ver todas las versiones Etiquetas anti malware anti tracker container privacy security Añadir a la colección Seleccionar una colección… Crear nueva colección Reportar este complemento Ayudar a este desarrollador El desarrollador de esta extensión te pide le ayudes a seguir con el desarrollo haciendo una pequeña contribución. Contribuir ahora Ir a la página de inicio de Mozilla Complementos Acerca de Blog de complementos de Firefox Taller de extensiones Central del desarrollador Normativas para desarrolladores Blog de la comunidad Foro Informar de un error Guía de revisión Navegadores Desktop Mobile Enterprise Productos Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Privacidad Cookies Legal A menos que se indique lo contrario, el contenido de este sitio está licenciado bajo la licencia Creative Commons Reconocimiento Compartir-Igual v3.0 o una versión posterior. Cambiar idioma Č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/tr/firefox/addon/rentgen/ | Rentgen - Bu 🦊 Firefox (tr) uzantısını yükle Firefox Browser Eklentileri Uzantılar Temalar Daha fazla… Firefox için Sözlükler ve dil paketleri Diğer tarayıcı siteleri Android eklentileri Giriş Ara Ara Rentgen geliştiren: “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 inceleme) 5 (12 inceleme) 216 kullanıcı 216 kullanıcı Firefox’u indir ve uzantıyı yükle Dosyayı indir Uzantı meta verileri Ekran görüntüleri Bu uzantı hakkında 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 Geliştirici yorumları 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 12 inceleyiciden 5 puan aldı Bu uzantıya puan vermek için giriş yapın Henüz hiç puan yok Puan kaydedildi 5 12 4 0 3 0 2 0 1 0 12 incelemenin hepsini oku İzinler ve veriler Gerekli izinler: Gizlilik ayarlarını okuma ve değiştirme Tarayıcının vekil sunucu ayarlarını yönetme Tüm web sitelerine ait verilerinize erişme Veri toplama: Geliştirici, bu uzantının veri toplamaya gerek duymadığını söylüyor. Daha fazla bilgi al Daha fazla bilgi Eklenti bağlantıları Ana sayfa Destek sitesi Destek e-postası Sürüm 0.2.4 Boyut 9,55 MB Son güncelleme 21 gün önce (23 Ara 2025) İlgili kategoriler Web Geliştirme Gizlilik ve Güvenlik Lisans Yalnızca GNU Genel Kamu Lisansı v3.0 Gizlilik ilkeleri Bu eklentinin gizlilik ilkelerini okuyun Sürüm geçmişi Tüm sürümleri göster Etiketler anti malware anti tracker container privacy security Koleksiyona ekle Bir koleksiyon seçin… Yeni koleksiyon oluştur Bu eklentiyi rapor et Bu geliştiriciyi destekleyin Bu uzantının geliştiricisi, küçük bir bağışta bulunarak gelişimin devamı için katkıda bulunmanızı rica ediyor. Bağış yap Mozilla'nın ana sayfasına gidin Eklentiler Hakkında Firefox Eklentileri Blogu Uzantı Atölyesi Geliştirici Merkezi Geliştirici Politikaları Topluluk Blogu Forum Hata bildir İnceleme rehberi Tarayıcılar Desktop Mobile Enterprise Ürünler Browsers VPN Relay Monitor Pocket Bluesky (@firefox.com) Instagram (Firefox) YouTube (firefoxchannel) Gizlilik Çerezler Hukuki Bilgiler Aksi belirtilmedikçe bu sitedeki içerikler Creative Commons Attribution Share-Alike Lisansı v3.0 veya daha yeni sürümüyle lisanslanmıştır. Dil değiştir Č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/#cb4-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://lab174.com/blog/202601-yaml-norway/#cb5-6 | 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://music.forem.com/t/diy | Diy - 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 # diy Follow Hide homemade music hustle Create Post Older #diy posts 1 2 3 4 5 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu Andrew Huang: If you're not using envelope followers, you're missing out Music YouTube Music YouTube Music YouTube Follow Nov 30 '25 Andrew Huang: If you're not using envelope followers, you're missing out # production # digital # diy Comments Add Comment 1 min read Andrew Huang: Don't sleep on envelope followers! 8 creative uses Music YouTube Music YouTube Music YouTube Follow Nov 28 '25 Andrew Huang: Don't sleep on envelope followers! 8 creative uses # production # diy # digital 4 reactions Comments 1 comment 1 min read Rick Beato: The Wolfgang Van Halen Interview Music YouTube Music YouTube Music YouTube Follow Nov 6 '25 Rick Beato: The Wolfgang Van Halen Interview # indie # production # diy Comments Add Comment 1 min read Rick Beato: Live Tour Update from Norway Music YouTube Music YouTube Music YouTube Follow Oct 31 '25 Rick Beato: Live Tour Update from Norway # livestreaming # production # indie # diy Comments Add Comment 1 min read Rick Beato: Is There Anything Bumblefoot Can't Play? ...No! Music YouTube Music YouTube Music YouTube Follow Oct 17 '25 Rick Beato: Is There Anything Bumblefoot Can't Play? ...No! # indie # production # diy Comments Add Comment 1 min read NPR Music: Macario Martinez: Tiny Desk Concert Music YouTube Music YouTube Music YouTube Follow Oct 10 '25 NPR Music: Macario Martinez: Tiny Desk Concert # indie # streaming # diy Comments Add Comment 1 min read Adam Neely: Sungazer - Whisky and Mes [Bass Playthrough] Music YouTube Music YouTube Music YouTube Follow Oct 8 '25 Adam Neely: Sungazer - Whisky and Mes [Bass Playthrough] # indie # production # diy Comments Add Comment 1 min read Andrew Huang: S4 2.0 is incredible! Music YouTube Music YouTube Music YouTube Follow Nov 10 '25 Andrew Huang: S4 2.0 is incredible! # production # indie # diy 3 reactions Comments 2 comments 1 min read Song (Original song ingredient) Jack Le Hamster Jack Le Hamster Jack Le Hamster Follow Sep 27 '25 Song (Original song ingredient) # composition # diy # songwriting Comments Add Comment 2 min read Nardwuar the Human Serviette: Nardwuar vs. Shai Gilgeous-Alexander Music YouTube Music YouTube Music YouTube Follow Sep 20 '25 Nardwuar the Human Serviette: Nardwuar vs. Shai Gilgeous-Alexander # indie # livestreaming # diy Comments Add Comment 1 min read Rick Beato: The Nick Raskulinecz Interview: Crafting The Sounds Of Deftones, Foo Fighters, AIC and Rush Music YouTube Music YouTube Music YouTube Follow Sep 17 '25 Rick Beato: The Nick Raskulinecz Interview: Crafting The Sounds Of Deftones, Foo Fighters, AIC and Rush # production # diy 1 reaction Comments Add Comment 1 min read Rick Beato: Major Announcement! Music YouTube Music YouTube Music YouTube Follow Sep 21 '25 Rick Beato: Major Announcement! # livestreaming # diy Comments Add Comment 1 min read La fin des reves (Original song ingredient) Jack Le Hamster Jack Le Hamster Jack Le Hamster Follow Sep 21 '25 La fin des reves (Original song ingredient) # diy # songwriting # dreampop # synthesizers 3 reactions Comments Add Comment 2 min read Rick Beato: Hiromi: The Most Electrifying Pianist Alive Music YouTube Music YouTube Music YouTube Follow Oct 9 '25 Rick Beato: Hiromi: The Most Electrifying Pianist Alive # indie # streaming # diy # production 2 reactions Comments Add Comment 1 min read NPR Music: Guster: Tiny Desk Concert Music YouTube Music YouTube Music YouTube Follow Aug 20 '25 NPR Music: Guster: Tiny Desk Concert # indie # streaming # diy Comments Add Comment 1 min read Soul Heist EP released in 2020 Vicente G. Reyes Vicente G. Reyes Vicente G. Reyes Follow Sep 6 '25 Soul Heist EP released in 2020 # indie # production # diy # ambient 3 reactions Comments 5 comments 1 min read Rick Beato: Our Record Label Told Us These Legendary Producers Sucked Music YouTube Music YouTube Music YouTube Follow Aug 6 '25 Rick Beato: Our Record Label Told Us These Legendary Producers Sucked # production # diy # distribution Comments Add Comment 1 min read Rick Beato: A Simple Twist Of Fate Music YouTube Music YouTube Music YouTube Follow Aug 9 '25 Rick Beato: A Simple Twist Of Fate # production # diy Comments Add Comment 1 min read Andrew Huang: 10 free online tools for musicians! Music YouTube Music YouTube Music YouTube Follow Jul 31 '25 Andrew Huang: 10 free online tools for musicians! # digital # production # diy 3 reactions Comments Add Comment 1 min read Bandlab songs 🔥 Zako Mako Zako Mako Zako Mako Follow Jun 22 '25 Bandlab songs 🔥 # streaming # hiphop # digital # diy 3 reactions Comments 1 comment 1 min read Workflow Discussion - pls halp RIchard M Blumenthal RIchard M Blumenthal RIchard M Blumenthal Follow Jul 22 '25 Workflow Discussion - pls halp # discuss # workflow # freelancer # diy 12 reactions Comments 5 comments 2 min read loading... trending guides/resources Rick Beato: Live Tour Update from Norway Rick Beato: The Wolfgang Van Halen Interview Andrew Huang: If you're not using envelope followers, you're missing out Andrew Huang: S4 2.0 is incredible! Andrew Huang: Don't sleep on envelope followers! 8 creative uses 💎 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://dev.to/dmuraco3/when-to-user-server-side-rendering-vs-static-generation-in-nextjs-8ab#comment-244im | When to Use Server-Side rendering vs Static Generation in Next.js - 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 Dylan Muraco Posted on Dec 30, 2021 When to Use Server-Side rendering vs Static Generation in Next.js Pre-rendering your pages has multiple benefits such as better performance and better SEO. But choosing whether to statically generate your pages or render them on the server side can be confusing. Let's first take a look at Server-Side rendering getServerSideProps The main difference between getServerSideProps and getStaticProps is when they are ran. getServerSideProps is ran when every new request is made to the page. export async function getServerSideProps ( context ) { const { userId } = context . params const user = await getUser ( userId ) return { props : { user } } } export default function User ({ user }) { return ( < div > < h1 > { user . name } < /h1 > < /div > ) } Enter fullscreen mode Exit fullscreen mode In this example we are getting the userId from a dynamic route , getting the information about the user, then using that data to build the user page. Note that we have access to the request through params now lets take a look at getStaticProps getStaticProps We saw that getServerSideProps gets ran every time a new request is made so what about getStaticProps. getStaticProps is ran at build time, meaning that whenever you run npm run build this is when your static pages are built. export async function getStaticProps () { const blogPosts = await getBlogPosts () return { props : { blogPosts } } } export default function Home ({ blogPosts }) { return ( < div > { blogPosts . map ( post => ( < h1 > { post . name } < /h1 > ))} < /div > ) } Enter fullscreen mode Exit fullscreen mode this function is getting a list of blog posts and rendering them on a page. Because we know what we want before hand we can statically render the page whereas in our server side rendering example we don't know before the request is made what the user wants. So when to user getServerSideProps? Good for when you don't know what the user wants before they make a request Still want good SEO When to use getStaticProps? When we know what the user wants at build time Really fast performance and SEO This was just a quick dive into static generation vs server-side generation. If you want to learn more please let me know. As always thanks for reading. Top comments (8) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Collapse Expand Martin Krause Martin Krause Martin Krause Follow “It’s only work if somebody makes you do it.” • craft code • creative ideas • cutting edge • author • senior front end architect • professional scuba diver • adventures above and below the sea level Location Germany Work Senior Front End Architect, Full Stack Engineer, Creative Technologist and Scuba Diving Professional Joined May 19, 2019 • Dec 30 '21 • Edited on Dec 30 • Edited Dropdown menu Copy link Hide Hey! Great explanation! Back in summer I took e deep dive into the different types of pre-rendering with next.js - take a look if you like! Cheers! Like comment: Like comment: 4 likes Like Comment button Reply Collapse Expand Aimee Aimee Aimee Follow I'm a passionate front end developer with experience in HTML5, CSS3, Javascript, React, Typescript, GraphQL, Styled Components, MUI. Location UK Work web developer Joined May 18, 2019 • Jan 12 '23 Dropdown menu Copy link Hide hey nice blog post, which one should I use then, getByStaticProps, I'm fetching some data from a CMS I set up which stores my projects in then I'm wanting to display this data in my portfolio, I was using getByServerSideProps but I'm thinking I should use the other as it's not rarely going to change unless I go into the CMS and add a new project. Thanks Like comment: Like comment: Like Comment button Reply Collapse Expand coder-pixel coder-pixel coder-pixel Follow Work Student Joined Jan 23, 2023 • May 3 '23 Dropdown menu Copy link Hide I think in that case you should go for 'getStaticProps' option, as your data is ll static in general most of the time. Like comment: Like comment: 2 likes Like Comment button Reply Collapse Expand Ryan-Mambou Ryan-Mambou Ryan-Mambou Follow Joined Mar 28, 2022 • Sep 20 '22 Dropdown menu Copy link Hide Excellent article man. Thanks a lot! Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Emeka Orji Emeka Orji Emeka Orji Follow Email emekapraiseo@gmail.com Location Lagos, Nigeria Pronouns He/Him Work Engineering Joined Jun 25, 2020 • Jul 25 '22 Dropdown menu Copy link Hide Amazing Explanation!!👍👍 Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Stelios Papoutsakis Stelios Papoutsakis Stelios Papoutsakis Follow I started as a full stack junior web developer in 2018, became a team leader and I am trying to level up my game. Joined Jun 15, 2024 • Jun 15 '24 Dropdown menu Copy link Hide good one. can we use both in a next.js project? Like comment: Like comment: 1 like Like Comment button Reply Collapse Expand Shuvo Koiri Shuvo Koiri Shuvo Koiri Follow Joined Jun 30, 2022 • Jun 30 '22 Dropdown menu Copy link Hide Ok,,,,Can you tell me wahich one should I use in index.js for my Blogging website>>>??? Like comment: Like comment: Like Comment button Reply Collapse Expand Md Ohidul Islam Md Ohidul Islam Md Ohidul Islam Follow Joined Jul 1, 2022 • Jul 1 '22 Dropdown menu Copy link Hide Hello Shuvo Koiri, I am assuming that your index.js page is responsible for showing a list of blog posts, which we can assume doesn't change so frequently (e.g: Multiple-times in an hour). Therefore you can use getStaticProps with the property revalidate: 10 . By doing that Next.js will re-generate only the index.js page at most once every 10 seconds. See the code snapshot below, this is from the official Next.js documentation. export async function getStaticProps () { const res = await fetch ( ' https://.../posts ' ) const posts = await res . json () return { props : { posts , }, // Next.js will attempt to re-generate the page: // - When a request comes in // - At most once every 10 seconds revalidate : 10 , // In seconds } } ``` Enter fullscreen mode Exit fullscreen mode Like comment: Like comment: 4 likes Like Comment button Reply Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Dylan Muraco Follow I like coding cool stuff Location Mars Joined Dec 21, 2021 More from Dylan Muraco Guide to Adding Info Text in Sanity Studio # sanity # webdev # react # typescript How to Create a Local RAG Agent with Ollama and LangChain # rag # tutorial # ai # python Authenticate in React with Firebase Auth # react # firebase # authentication 💎 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://gg.forem.com/gg_news/gen-z-is-cutting-back-on-video-game-purchases-like-really-cutting-back-13e2 | Gen Z Is Cutting Back On Video Game Purchases. Like, Really Cutting Back - Gamers Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Gamers Forem Close 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 Gaming News Posted on Aug 12, 2025 Gen Z Is Cutting Back On Video Game Purchases. Like, Really Cutting Back # gaminghardware # nintendoswitch # sportsgames # gamedeals Gen Z Is Cutting Back On Video Game Purchases. Like, Really Cutting Back Young zoomers just can't afford video games anymore. According to the Wall Street Journal, Gen Z is spending far less on gaming. vice.com Gen Z gamers are seriously dialing back their spend: according to Circana, 18- to 24-year-olds shelled out about 13 percent less on games between January and April versus last year, which translates to almost a 25 percent weekly spending drop—and that’s way steeper than any other age group’s single-digit decline. Tough job prospects, student-loan bills kicking back in and rising credit-card delinquency are to blame, say economists and analysts like Mat Piscatella. If zoomers can’t afford games now, both their future wealth-building and the gaming industry’s growth could take a real hit. Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Gaming News Follow Joined Apr 30, 2025 More from Gaming News IGN: Is Pokemon Legends: Z-A on Switch 2 That Much Better Than Switch 1? # nintendo # nintendoswitch # pcgaming GameSpot: Pokemon Legends: Z-A Review # nintendo # nintendoswitch # pcgaming GameSpot: Pokemon Legends: Z-A - 19 Things I Wish I Knew Before Starting # nintendo # nintendoswitch # pcgaming 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Gamers Forem — An inclusive community for gaming enthusiasts Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Gamers Forem © 2025 - 2026. We're a place where gamers unite, level up, and share epic adventures. Log in Create account | 2026-01-13T08:48:04 |
https://vibe.forem.com/t/opensource | Open Source - Vibe Coding 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 Vibe Coding Forem Close Open Source Follow Hide May The Source Be With You! Articles about Open Source and Free Software as a philosophy, and its application to software development and project management. Create Post submission guidelines UPDATED APRIL 8, 2020 To keep this tag clean and meaningful, please ensure your post fits into at least one of the following categories: Organizing, managing, running, or working in an Open Source project. Open Source philosophy, licensing, and/or practical and legal topics thereof. Advocacy and adoption of Open Source philosophy. DO NOT use this tag if you are simply using technologies which happen to be open source. You should NOT use this tag for any of the following: Promoting open source projects, such as feature lists or announcements. (Use #news or Listings .) Contributor requests. (Use #contributorswanted or Listings .) Tutorials/articles that happen to use an open source tool. (Use appropriate technology tags.) Showing off something you've built that happens to be open source. (Use the #showdev tag.) Sharing lists of open source projects. (Use #githunt or the appropriate technology tags.) Projects must comply with the Open Source Definition (see below) to legally use the term "open source". As all "Free Software" officially complies with the standards of Open Source anyway, this tag covers both (collectively, FOSS). about #opensource Open Source is so much more than "you can read the code". It is formally defined by the Open Source Initiative . "Open Source" should not be confused with the similar Free Software , which is defined by the Free Software Foundation . Generally, all Free Software is also Open Source, and the two camps often cooperate; however, the concepts are distinct! (The tags are merged here on DEV.to for simplicity, however.) Open Source Hardware is defined and overseen by the Open Source Hardware Assocation Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu I made a Meme Creator because I hate watermarks Brian Zavala Brian Zavala Brian Zavala Follow Jan 13 I made a Meme Creator because I hate watermarks # opensource # react # webdev # javascript Comments Add Comment 3 min read 20 Plus AI Coding Tools for Dev Workflows in 2026 Devin Rosario Devin Rosario Devin Rosario Follow Jan 7 20 Plus AI Coding Tools for Dev Workflows in 2026 # ai # devops # opensource # programming Comments Add Comment 6 min read The cal.com clone NIRMAL PY NIRMAL PY NIRMAL PY Follow Dec 19 '25 The cal.com clone # ai # opensource Comments Add Comment 1 min read Cooked this Paperfolio template with V0 | Here’s the template you can use for free Nikhil Shukla Nikhil Shukla Nikhil Shukla Follow Dec 1 '25 Cooked this Paperfolio template with V0 | Here’s the template you can use for free # ai # opensource # buildinpublic # cloud 4 reactions Comments Add Comment 1 min read Looking for feedback on a small side project I’ve been building Dinesh Dawonauth Dinesh Dawonauth Dinesh Dawonauth Follow Dec 22 '25 Looking for feedback on a small side project I’ve been building # python # opensource # cli Comments 2 comments 1 min read 🧞♂️ Introducing Code-Genie: A Small CLI Tool That Helps You Edit & Generate Code Using Natural Language Sherin Joseph Roy Sherin Joseph Roy Sherin Joseph Roy Follow Nov 13 '25 🧞♂️ Introducing Code-Genie: A Small CLI Tool That Helps You Edit & Generate Code Using Natural Language # opensource # ai # productivity # devto Comments 1 comment 2 min read I Made a Habit Tracker Because the Free Ones Were… Not Free 😅 Saami abbas Khan Saami abbas Khan Saami abbas Khan Follow Dec 16 '25 I Made a Habit Tracker Because the Free Ones Were… Not Free 😅 # opensource # gemini # ai # vscode 13 reactions Comments 7 comments 1 min read How I Vibe Coded a Custom Telegram Downloader (Because Browser Throttling is the Worst) Anay Pandya Anay Pandya Anay Pandya Follow Nov 22 '25 How I Vibe Coded a Custom Telegram Downloader (Because Browser Throttling is the Worst) # api # buildinpublic # opensource 1 reaction Comments Add Comment 3 min read Making your Java code null-safe without rewriting it JPlus JPlus JPlus Follow Nov 6 '25 Making your Java code null-safe without rewriting it # opensource # java # nullsafety # jplus Comments Add Comment 5 min read Making Java Code Null-Safe With JPlus JPlus JPlus JPlus Follow Nov 5 '25 Making Java Code Null-Safe With JPlus # linting # opensource # plugin Comments Add Comment 5 min read Krish Naik: Now Running MCP Server Is Easy With Docker MCP Toolkit Vibe YouTube Vibe YouTube Vibe YouTube Follow Oct 30 '25 Krish Naik: Now Running MCP Server Is Easy With Docker MCP Toolkit # docker # devops # opensource 3 reactions Comments Add Comment 1 min read Krish Naik: 5-Getting Started With Agentic RAG With Detailed Implementation Using LangGraph Vibe YouTube Vibe YouTube Vibe YouTube Follow Oct 22 '25 Krish Naik: 5-Getting Started With Agentic RAG With Detailed Implementation Using LangGraph # ai # opensource Comments Add Comment 1 min read Generate Complete HTML Pages Directly from the Frontend (No Backend Needed ⚡️) Alex Alex Alex Follow Oct 22 '25 Generate Complete HTML Pages Directly from the Frontend (No Backend Needed ⚡️) # ai # opensource # openai # gemini Comments Add Comment 1 min read Sharing My Little Experiment: Code Genie – A Simple Open-Source Tool to Help with Code Ideas Sherin Joseph Roy Sherin Joseph Roy Sherin Joseph Roy Follow Nov 13 '25 Sharing My Little Experiment: Code Genie – A Simple Open-Source Tool to Help with Code Ideas # opensource # ai # coding # aicoding 18 reactions Comments 9 comments 2 min read A Complete Guide to Exploratory Factor Analysis (EFA) in R Anshuman Anshuman Anshuman Follow Oct 13 '25 A Complete Guide to Exploratory Factor Analysis (EFA) in R # ai # opensource 5 reactions Comments Add Comment 6 min read Nicholas Renotte: I Spent 6 Weeks using Reinforcement Learning to Beat This GoDot Game Vibe YouTube Vibe YouTube Vibe YouTube Follow Oct 11 '25 Nicholas Renotte: I Spent 6 Weeks using Reinforcement Learning to Beat This GoDot Game # ai # opensource # git Comments Add Comment 1 min read I Built 25 AI Tools for Python Devs—Here's What I Learned yassine bout yassine bout yassine bout Follow Nov 13 '25 I Built 25 AI Tools for Python Devs—Here's What I Learned # ai # devops # opensource # api 7 reactions Comments 1 comment 2 min read How I Built a Free AI Learning Resource Hub from Scratch Boss Boss Boss Follow Oct 13 '25 How I Built a Free AI Learning Resource Hub from Scratch # ai # opensource Comments 1 comment 1 min read sentdex: Unitree G1 Security Disaster Vibe YouTube Vibe YouTube Vibe YouTube Follow Oct 2 '25 sentdex: Unitree G1 Security Disaster # ai # opensource 3 reactions Comments Add Comment 1 min read Krish Naik: Complete RAG Crash Course With Langchain In 2 Hours Vibe YouTube Vibe YouTube Vibe YouTube Follow Oct 14 '25 Krish Naik: Complete RAG Crash Course With Langchain In 2 Hours # ai # opensource 3 reactions Comments Add Comment 1 min read 🌟 Introducing JPlus – A Modern Java Superset Language JPlus JPlus JPlus Follow Oct 31 '25 🌟 Introducing JPlus – A Modern Java Superset Language # debugging # opensource Comments Add Comment 4 min read How to Vibe Code an App in 4 Easy Steps Karina Egle Karina Egle Karina Egle Follow Oct 30 '25 How to Vibe Code an App in 4 Easy Steps # ai # devops # opensource # openai 2 reactions Comments 2 comments 3 min read Next-Gen AI for Developers: Assistant Engine Assistant Engine Assistant Engine Assistant Engine Follow Oct 23 '25 Next-Gen AI for Developers: Assistant Engine # ai # devops # opensource # dotnet Comments Add Comment 2 min read I was tired of regression testing, so I weekend-vibe-coded something wyctor wyctor wyctor Follow Oct 12 '25 I was tired of regression testing, so I weekend-vibe-coded something # ai # opensource # cli # claude 10 reactions Comments Add Comment 1 min read The Creative Flow: Vibe Coding Tools and the Human Element on October 13, 2025 Om Shree Om Shree Om Shree Follow Oct 13 '25 The Creative Flow: Vibe Coding Tools and the Human Element on October 13, 2025 # ai # cloud # devops # opensource 16 reactions Comments 1 comment 3 min read loading... trending guides/resources Making Java Code Null-Safe With JPlus Making your Java code null-safe without rewriting it 20 Plus AI Coding Tools for Dev Workflows in 2026 How to Vibe Code an App in 4 Easy Steps The cal.com clone 🌟 Introducing JPlus – A Modern Java Superset Language How I Vibe Coded a Custom Telegram Downloader (Because Browser Throttling is the Worst) I Built 25 AI Tools for Python Devs—Here's What I Learned Cooked this Paperfolio template with V0 | Here’s the template you can use for free Krish Naik: Now Running MCP Server Is Easy With Docker MCP Toolkit 🧞♂️ Introducing Code-Genie: A Small CLI Tool That Helps You Edit & Generate Code Using Natural L... Looking for feedback on a small side project I’ve been building I Made a Habit Tracker Because the Free Ones Were… Not Free 😅 Sharing My Little Experiment: Code Genie – A Simple Open-Source Tool to Help with Code Ideas 💎 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 Vibe Coding Forem — Discussing AI software development, and showing off what we're building. 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 . Vibe Coding Forem © 2025 - 2026. Where anyone can code, with a bit of creativity and some AI help. Log in Create account | 2026-01-13T08:48:04 |
https://shop.forem.com/collections | Collections – Forem Shop Skip to content Home Collections Collections DEV CodeNewbie Forem DEV Challenges View All About FAQ Log in Country/region Albania (ALL L) Andorra (EUR €) Angola (USD $) Anguilla (XCD $) Antigua & Barbuda (XCD $) Argentina (USD $) Aruba (AWG ƒ) Australia (AUD $) Austria (EUR €) Bahamas (BSD $) Bahrain (USD $) Barbados (BBD $) Belgium (EUR €) Belize (BZD $) Benin (XOF Fr) Bermuda (USD $) Bhutan (USD $) Bosnia & Herzegovina (BAM КМ) Botswana (BWP P) Bouvet Island (USD $) Brazil (USD $) British Virgin Islands (USD $) Bulgaria (EUR €) Burkina Faso (XOF Fr) Cameroon (XAF CFA) Canada (CAD $) Cape Verde (CVE $) Caribbean Netherlands (USD $) Chile (USD $) China (CNY ¥) Colombia (USD $) Comoros (KMF Fr) Cook Islands (NZD $) Croatia (EUR €) Curaçao (ANG ƒ) Cyprus (EUR €) Czechia (CZK Kč) Denmark (DKK kr.) Djibouti (DJF Fdj) Dominica (XCD $) Dominican Republic (DOP $) Equatorial Guinea (XAF CFA) Estonia (EUR €) Eswatini (USD $) Ethiopia (ETB Br) Falkland Islands (FKP £) Faroe Islands (DKK kr.) Fiji (FJD $) Finland (EUR €) France (EUR €) French Guiana (EUR €) French Polynesia (XPF Fr) Gabon (XOF Fr) Gambia (GMD D) Germany (EUR €) Ghana (USD $) Gibraltar (GBP £) Greece (EUR €) Grenada (XCD $) Guadeloupe (EUR €) Guernsey (GBP £) Guinea (GNF Fr) Guinea-Bissau (XOF Fr) Guyana (GYD $) Haiti (USD $) Heard & McDonald Islands (AUD $) Hong Kong SAR (HKD $) Hungary (HUF Ft) Iceland (ISK kr) India (INR ₹) Indonesia (IDR Rp) Ireland (EUR €) Israel (ILS ₪) Italy (EUR €) Jamaica (JMD $) Japan (JPY ¥) Jersey (USD $) Jordan (USD $) Kenya (KES KSh) Kiribati (USD $) Kuwait (USD $) Latvia (EUR €) Liechtenstein (CHF CHF) Lithuania (EUR €) Luxembourg (EUR €) Macao SAR (MOP P) Malawi (MWK MK) Malaysia (MYR RM) Maldives (MVR MVR) Malta (EUR €) Martinique (EUR €) Mauritania (USD $) Mayotte (EUR €) Mexico (USD $) Monaco (EUR €) Montserrat (XCD $) Mozambique (USD $) Namibia (USD $) Nauru (AUD $) Nepal (NPR Rs.) Netherlands (EUR €) Netherlands Antilles (ANG ƒ) New Caledonia (XPF Fr) New Zealand (NZD $) Nigeria (NGN ₦) Niue (NZD $) Norway (USD $) Oman (USD $) Papua New Guinea (PGK K) Paraguay (PYG ₲) Peru (PEN S/) Philippines (PHP ₱) Poland (PLN zł) Portugal (EUR €) Qatar (QAR ر.ق) Réunion (EUR €) Romania (RON Lei) Rwanda (RWF FRw) São Tomé & Príncipe (STD Db) Saudi Arabia (SAR ر.س) Senegal (XOF Fr) Singapore (SGD $) Sint Maarten (ANG ƒ) Slovakia (EUR €) Slovenia (EUR €) South Africa (USD $) South Korea (KRW ₩) Spain (EUR €) Sri Lanka (LKR ₨) St. Barthélemy (EUR €) St. Helena (SHP £) St. Kitts & Nevis (XCD $) St. Lucia (XCD $) St. Martin (EUR €) St. Vincent & Grenadines (XCD $) Suriname (USD $) Sweden (SEK kr) Switzerland (CHF CHF) Taiwan (TWD $) Tanzania (TZS Sh) Thailand (THB ฿) Togo (XOF Fr) Tonga (TOP T$) Trinidad & Tobago (TTD $) Turks & Caicos Islands (USD $) Tuvalu (AUD $) U.S. Outlying Islands (USD $) Uganda (UGX USh) United Arab Emirates (AED د.إ) United Kingdom (GBP £) United States (USD $) Uruguay (UYU $U) Vanuatu (VUV Vt) Vatican City (EUR €) Vietnam (VND ₫) Zambia (USD $) Update country/region Country/region USD $ | United States ALL L | Albania EUR € | Andorra USD $ | Angola XCD $ | Anguilla XCD $ | Antigua & Barbuda USD $ | Argentina AWG ƒ | Aruba AUD $ | Australia EUR € | Austria BSD $ | Bahamas USD $ | Bahrain BBD $ | Barbados EUR € | Belgium BZD $ | Belize XOF Fr | Benin USD $ | Bermuda USD $ | Bhutan BAM КМ | Bosnia & Herzegovina BWP P | Botswana USD $ | Bouvet Island USD $ | Brazil USD $ | British Virgin Islands EUR € | Bulgaria XOF Fr | Burkina Faso XAF CFA | Cameroon CAD $ | Canada CVE $ | Cape Verde USD $ | Caribbean Netherlands USD $ | Chile CNY ¥ | China USD $ | Colombia KMF Fr | Comoros NZD $ | Cook Islands EUR € | Croatia ANG ƒ | Curaçao EUR € | Cyprus CZK Kč | Czechia DKK kr. | Denmark DJF Fdj | Djibouti XCD $ | Dominica DOP $ | Dominican Republic XAF CFA | Equatorial Guinea EUR € | Estonia USD $ | Eswatini ETB Br | Ethiopia FKP £ | Falkland Islands DKK kr. | Faroe Islands FJD $ | Fiji EUR € | Finland EUR € | France EUR € | French Guiana XPF Fr | French Polynesia XOF Fr | Gabon GMD D | Gambia EUR € | Germany USD $ | Ghana GBP £ | Gibraltar EUR € | Greece XCD $ | Grenada EUR € | Guadeloupe GBP £ | Guernsey GNF Fr | Guinea XOF Fr | Guinea-Bissau GYD $ | Guyana USD $ | Haiti AUD $ | Heard & McDonald Islands HKD $ | Hong Kong SAR HUF Ft | Hungary ISK kr | Iceland INR ₹ | India IDR Rp | Indonesia EUR € | Ireland ILS ₪ | Israel EUR € | Italy JMD $ | Jamaica JPY ¥ | Japan USD $ | Jersey USD $ | Jordan KES KSh | Kenya USD $ | Kiribati USD $ | Kuwait EUR € | Latvia CHF CHF | Liechtenstein EUR € | Lithuania EUR € | Luxembourg MOP P | Macao SAR MWK MK | Malawi MYR RM | Malaysia MVR MVR | Maldives EUR € | Malta EUR € | Martinique USD $ | Mauritania EUR € | Mayotte USD $ | Mexico EUR € | Monaco XCD $ | Montserrat USD $ | Mozambique USD $ | Namibia AUD $ | Nauru NPR Rs. | Nepal EUR € | Netherlands ANG ƒ | Netherlands Antilles XPF Fr | New Caledonia NZD $ | New Zealand NGN ₦ | Nigeria NZD $ | Niue USD $ | Norway USD $ | Oman PGK K | Papua New Guinea PYG ₲ | Paraguay PEN S/ | Peru PHP ₱ | Philippines PLN zł | Poland EUR € | Portugal QAR ر.ق | Qatar EUR € | Réunion RON Lei | Romania RWF FRw | Rwanda STD Db | São Tomé & Príncipe SAR ر.س | Saudi Arabia XOF Fr | Senegal SGD $ | Singapore ANG ƒ | Sint Maarten EUR € | Slovakia EUR € | Slovenia USD $ | South Africa KRW ₩ | South Korea EUR € | Spain LKR ₨ | Sri Lanka EUR € | St. Barthélemy SHP £ | St. Helena XCD $ | St. Kitts & Nevis XCD $ | St. Lucia EUR € | St. Martin XCD $ | St. Vincent & Grenadines USD $ | Suriname SEK kr | Sweden CHF CHF | Switzerland TWD $ | Taiwan TZS Sh | Tanzania THB ฿ | Thailand XOF Fr | Togo TOP T$ | Tonga TTD $ | Trinidad & Tobago USD $ | Turks & Caicos Islands AUD $ | Tuvalu USD $ | U.S. Outlying Islands UGX USh | Uganda AED د.إ | United Arab Emirates GBP £ | United Kingdom USD $ | United States UYU $U | Uruguay VUV Vt | Vanuatu EUR € | Vatican City VND ₫ | Vietnam USD $ | Zambia Twitter Facebook Instagram Home Collections DEV CodeNewbie Forem DEV Challenges View All About FAQ Search Log in Cart Collections DEV Challenges Show off your participation in DEV Challenges with these items! DEV Challenges All Products All Products Pride 2023 Collection Pride 2023 Collection CodeNewbie Collection CodeNewbie Collection Forem Collection Forem Collection DEV Collection DEV Collection Subscribe to our emails Email Facebook Instagram Twitter Country/region Albania (ALL L) Andorra (EUR €) Angola (USD $) Anguilla (XCD $) Antigua & Barbuda (XCD $) Argentina (USD $) Aruba (AWG ƒ) Australia (AUD $) Austria (EUR €) Bahamas (BSD $) Bahrain (USD $) Barbados (BBD $) Belgium (EUR €) Belize (BZD $) Benin (XOF Fr) Bermuda (USD $) Bhutan (USD $) Bosnia & Herzegovina (BAM КМ) Botswana (BWP P) Bouvet Island (USD $) Brazil (USD $) British Virgin Islands (USD $) Bulgaria (EUR €) Burkina Faso (XOF Fr) Cameroon (XAF CFA) Canada (CAD $) Cape Verde (CVE $) Caribbean Netherlands (USD $) Chile (USD $) China (CNY ¥) Colombia (USD $) Comoros (KMF Fr) Cook Islands (NZD $) Croatia (EUR €) Curaçao (ANG ƒ) Cyprus (EUR €) Czechia (CZK Kč) Denmark (DKK kr.) Djibouti (DJF Fdj) Dominica (XCD $) Dominican Republic (DOP $) Equatorial Guinea (XAF CFA) Estonia (EUR €) Eswatini (USD $) Ethiopia (ETB Br) Falkland Islands (FKP £) Faroe Islands (DKK kr.) Fiji (FJD $) Finland (EUR €) France (EUR €) French Guiana (EUR €) French Polynesia (XPF Fr) Gabon (XOF Fr) Gambia (GMD D) Germany (EUR €) Ghana (USD $) Gibraltar (GBP £) Greece (EUR €) Grenada (XCD $) Guadeloupe (EUR €) Guernsey (GBP £) Guinea (GNF Fr) Guinea-Bissau (XOF Fr) Guyana (GYD $) Haiti (USD $) Heard & McDonald Islands (AUD $) Hong Kong SAR (HKD $) Hungary (HUF Ft) Iceland (ISK kr) India (INR ₹) Indonesia (IDR Rp) Ireland (EUR €) Israel (ILS ₪) Italy (EUR €) Jamaica (JMD $) Japan (JPY ¥) Jersey (USD $) Jordan (USD $) Kenya (KES KSh) Kiribati (USD $) Kuwait (USD $) Latvia (EUR €) Liechtenstein (CHF CHF) Lithuania (EUR €) Luxembourg (EUR €) Macao SAR (MOP P) Malawi (MWK MK) Malaysia (MYR RM) Maldives (MVR MVR) Malta (EUR €) Martinique (EUR €) Mauritania (USD $) Mayotte (EUR €) Mexico (USD $) Monaco (EUR €) Montserrat (XCD $) Mozambique (USD $) Namibia (USD $) Nauru (AUD $) Nepal (NPR Rs.) Netherlands (EUR €) Netherlands Antilles (ANG ƒ) New Caledonia (XPF Fr) New Zealand (NZD $) Nigeria (NGN ₦) Niue (NZD $) Norway (USD $) Oman (USD $) Papua New Guinea (PGK K) Paraguay (PYG ₲) Peru (PEN S/) Philippines (PHP ₱) Poland (PLN zł) Portugal (EUR €) Qatar (QAR ر.ق) Réunion (EUR €) Romania (RON Lei) Rwanda (RWF FRw) São Tomé & Príncipe (STD Db) Saudi Arabia (SAR ر.س) Senegal (XOF Fr) Singapore (SGD $) Sint Maarten (ANG ƒ) Slovakia (EUR €) Slovenia (EUR €) South Africa (USD $) South Korea (KRW ₩) Spain (EUR €) Sri Lanka (LKR ₨) St. Barthélemy (EUR €) St. Helena (SHP £) St. Kitts & Nevis (XCD $) St. Lucia (XCD $) St. Martin (EUR €) St. Vincent & Grenadines (XCD $) Suriname (USD $) Sweden (SEK kr) Switzerland (CHF CHF) Taiwan (TWD $) Tanzania (TZS Sh) Thailand (THB ฿) Togo (XOF Fr) Tonga (TOP T$) Trinidad & Tobago (TTD $) Turks & Caicos Islands (USD $) Tuvalu (AUD $) U.S. Outlying Islands (USD $) Uganda (UGX USh) United Arab Emirates (AED د.إ) United Kingdom (GBP £) United States (USD $) Uruguay (UYU $U) Vanuatu (VUV Vt) Vatican City (EUR €) Vietnam (VND ₫) Zambia (USD $) Update country/region Country/region USD $ | United States ALL L | Albania EUR € | Andorra USD $ | Angola XCD $ | Anguilla XCD $ | Antigua & Barbuda USD $ | Argentina AWG ƒ | Aruba AUD $ | Australia EUR € | Austria BSD $ | Bahamas USD $ | Bahrain BBD $ | Barbados EUR € | Belgium BZD $ | Belize XOF Fr | Benin USD $ | Bermuda USD $ | Bhutan BAM КМ | Bosnia & Herzegovina BWP P | Botswana USD $ | Bouvet Island USD $ | Brazil USD $ | British Virgin Islands EUR € | Bulgaria XOF Fr | Burkina Faso XAF CFA | Cameroon CAD $ | Canada CVE $ | Cape Verde USD $ | Caribbean Netherlands USD $ | Chile CNY ¥ | China USD $ | Colombia KMF Fr | Comoros NZD $ | Cook Islands EUR € | Croatia ANG ƒ | Curaçao EUR € | Cyprus CZK Kč | Czechia DKK kr. | Denmark DJF Fdj | Djibouti XCD $ | Dominica DOP $ | Dominican Republic XAF CFA | Equatorial Guinea EUR € | Estonia USD $ | Eswatini ETB Br | Ethiopia FKP £ | Falkland Islands DKK kr. | Faroe Islands FJD $ | Fiji EUR € | Finland EUR € | France EUR € | French Guiana XPF Fr | French Polynesia XOF Fr | Gabon GMD D | Gambia EUR € | Germany USD $ | Ghana GBP £ | Gibraltar EUR € | Greece XCD $ | Grenada EUR € | Guadeloupe GBP £ | Guernsey GNF Fr | Guinea XOF Fr | Guinea-Bissau GYD $ | Guyana USD $ | Haiti AUD $ | Heard & McDonald Islands HKD $ | Hong Kong SAR HUF Ft | Hungary ISK kr | Iceland INR ₹ | India IDR Rp | Indonesia EUR € | Ireland ILS ₪ | Israel EUR € | Italy JMD $ | Jamaica JPY ¥ | Japan USD $ | Jersey USD $ | Jordan KES KSh | Kenya USD $ | Kiribati USD $ | Kuwait EUR € | Latvia CHF CHF | Liechtenstein EUR € | Lithuania EUR € | Luxembourg MOP P | Macao SAR MWK MK | Malawi MYR RM | Malaysia MVR MVR | Maldives EUR € | Malta EUR € | Martinique USD $ | Mauritania EUR € | Mayotte USD $ | Mexico EUR € | Monaco XCD $ | Montserrat USD $ | Mozambique USD $ | Namibia AUD $ | Nauru NPR Rs. | Nepal EUR € | Netherlands ANG ƒ | Netherlands Antilles XPF Fr | New Caledonia NZD $ | New Zealand NGN ₦ | Nigeria NZD $ | Niue USD $ | Norway USD $ | Oman PGK K | Papua New Guinea PYG ₲ | Paraguay PEN S/ | Peru PHP ₱ | Philippines PLN zł | Poland EUR € | Portugal QAR ر.ق | Qatar EUR € | Réunion RON Lei | Romania RWF FRw | Rwanda STD Db | São Tomé & Príncipe SAR ر.س | Saudi Arabia XOF Fr | Senegal SGD $ | Singapore ANG ƒ | Sint Maarten EUR € | Slovakia EUR € | Slovenia USD $ | South Africa KRW ₩ | South Korea EUR € | Spain LKR ₨ | Sri Lanka EUR € | St. Barthélemy SHP £ | St. Helena XCD $ | St. Kitts & Nevis XCD $ | St. Lucia EUR € | St. Martin XCD $ | St. Vincent & Grenadines USD $ | Suriname SEK kr | Sweden CHF CHF | Switzerland TWD $ | Taiwan TZS Sh | Tanzania THB ฿ | Thailand XOF Fr | Togo TOP T$ | Tonga TTD $ | Trinidad & Tobago USD $ | Turks & Caicos Islands AUD $ | Tuvalu USD $ | U.S. Outlying Islands UGX USh | Uganda AED د.إ | United Arab Emirates GBP £ | United Kingdom USD $ | United States UYU $U | Uruguay VUV Vt | Vanuatu EUR € | Vatican City VND ₫ | Vietnam USD $ | Zambia © 2026, Forem Shop Powered by Shopify Privacy policy Terms of service Choosing a selection results in a full page refresh. Opens in a new window. | 2026-01-13T08:48:04 |
https://neon.tech/terms-of-service | Neon Platform Services Product Specific Schedule - 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 Neon Platform Services Product Specific Schedule Last updated: 1 December 2025 This Neon Platform Services Product Specific Schedule (“ Product Specific Schedule ”) is entered into as of the Effective Date between Neon, LLC (“Neon” or “we”), an affiliate of Databricks, Inc. (“Databricks”), and Customer (as defined below) (“Customer”, “you,” or “your”) and governs Customer’s use of the Neon proprietary cloud computing platform services (the “ Neon Platform Services ”). By accessing the Neon Platform Services, Customer agrees to the terms of this Product Specific Schedule. If you are entering into this Product Specific Schedule on behalf of a company (such as your employer) or other legal entity, you represent and warrant that you are authorized to bind that entity to this Product Specific Schedule, in which case “Customer,” “you,” or “your” will refer to that entity (otherwise, such terms refer to you as an individual). This Product Specific Schedule is subject to the terms of the current Databricks Master Cloud Services Agreement located at https://www.databricks.com/legal/mcsa (the “ Agreement ”), as supplemented and amended by this Product Specific Schedule, solely with respect to a Customer’s use of the Neon Platform Services. Customer acknowledges that we may make changes to the Agreement, this Product Specific Schedule or pricing from time to time and Customer’s continued use of the Neon Platform Services will constitute consent to such changes. For clarity, this Product Specific Schedule does not affect the terms of the Agreement as they relate to any non-Neon Platform Services, including the Databricks data processing platform services. Capitalized terms not defined here will have the meanings specified in the Agreement. For purposes of this Product Specific Schedule, all references under the Agreement to the “Platform Services” and the “Databricks Services” will be deemed references to the “Neon Platform Services”, and all references to “Databricks” under the Agreement will be deemed references to “Databricks, together with its Affiliates”. In the event of any conflict or inconsistency between this Product Specific Schedule and the Agreement, solely with respect to Customer’s use of Neon Platform Services, this Product Specific Schedule will control. Self-Service Plans. The Neon Platform Services will be provided according to the usage-based pricing plan selected by Customer, as described in the Documentation at https://neon.com/docs/introduction/plans (such plans, together with any legacy plans, a “ Self Service Plan ”). Customer’s subscription to any Self Service Plan will automatically renew on a month-to-month basis (each, a “ Subscription Month ”), unless Customer cancels its subscription to such Self Service Plan within fourteen (14) business days prior to the expiration of the then-current Subscription Month. Fees. Except as otherwise specified in an Order Form, (a) Fees will be determined based on the Self Service Plan selected by Customer and calculated based on Customer’s usage of the Neon Platform Services during each Subscription Month, and (b) all Fees will be invoiced monthly in arrears with payment invoiced and due on or around the first day of the calendar month following each Subscription Month. Fees will be automatically charged to Customer’s payment card on record. Amendments to the Agreement: Documentation. All references in the Agreement to the “Documentation” shall be deemed references to the documentation related to the Neon Platform Services located at https://neon.com/docs . Subprocessor List. All references in the Agreement (including, for clarity, Section 4 of the DPA) to the “Subprocessor List” shall be deemed references to the subprocessor list specific to the Neon Platform Services located at https://neon.com/subprocessors. Security Addendum. All references in the Agreement to the “Security Addendum” or “Security Measures” shall be deemed references to the security addendum and security measures attached hereto as Exhibit A. Audit. Section 7 (Audits and Records) of the DPA is hereby deleted in its entirety and replaced with the following: “Databricks, together with its Affiliates, will make information reasonably necessary to demonstrate compliance with this DPA available to Customer and allow for and contribute to audits, including inspections conducted by Customer or Customer’s auditor in order to assess compliance with this DPA, where required by applicable law. Customer acknowledges and agrees that Customer will exercise Customer’s audit rights under this DPA by instructing us to comply with the audit measures described in this provision. Upon request, Databricks, together with its Affiliates, will supply (on a confidential basis) the SOC 2 report for the Neon Platform Services and summary copies of the penetration testing report(s) to Customer so that Customer can verify compliance with this DPA.” Service Specific Terms. All references in the Agreement to the Service Specific Terms are hereby deleted. Projects. All references in the Agreement to “Workspaces” shall be deemed to include any projects created by Customer within the Neon Platform Services. Cardholder Data. Customer acknowledges and agrees it shall not include in Customer Content any cardholder data as defined under PCI-DSS (“ Cardholder Data ”). All references to Cardholder Data in Section 4.5(b) shall be hereby deleted. SLA. Notwithstanding anything to the contrary, the Service Level Agreement located at https://neon.com/neon-business-sla shall be incorporated into this Product Specific Schedule by reference and apply exclusively to Customers who have subscribed to the Scale self-service plan. Exhibit A – Security Measures Neon, together with its Affiliate Databricks, shall implement reasonable administrative, physical, and technical safeguards to protect the security of the Neon Platform Services and the Customer Content as set forth in this Exhibit A (“ Security Measures ”). While Neon may update the Security Measures, it shall not materially diminish the effectiveness of the Security Measures during the Term of an Order. All capitalized terms not otherwise defined herein will have the meanings as set forth in the Agreement. Access Control . Preventing Unauthorized Product Access Outsourced processing . We host the Neon Platform Services on an outsourced cloud infrastructure provider, according to a shared responsibility model. Physical and environmental security . We host our product infrastructure with multi-tenant, outsourced infrastructure providers. We do not own or maintain hardware located at the outsourced infrastructure providers’ data centers. Production servers and client-facing applications are logically and physically secured from our internal corporate information systems. Authentication . We implement a uniform authentication policy for our customer products. Customers who interact with the products via the user interface must authenticate before accessing Customer Content. Authorization . Customer Content is stored in multi-tenant storage systems accessible to Customers via only application user interfaces and application programming interfaces. Customers are not allowed direct access to the underlying application infrastructure. The authorization model in each of our products is designed to ensure that only the appropriately assigned individuals can access relevant features, views, and customization options. Authorization to data sets is performed through validating the user’s permissions against the attributes associated with each data set. Application Programming Interface (API) access : Public product APIs can be accessed using an API key or through Oauth authorization. Preventing Unauthorized Use . We implement industry standard access controls and detection capabilities for the internal networks that support its products. Access controls . Network access control mechanisms are designed to prevent network traffic using unauthorized protocols from reaching the product infrastructure. The technical measures implemented differ between infrastructure providers and include Virtual Private Cloud (VPC) implementations, security group assignment, and traditional firewall rules. Intrusion detection and prevention . We implement a Web Application Firewall (WAF) solution to protect hosted customer websites and other internet-accessible applications. The WAF is designed to identify and prevent attacks against publicly available network services. Static code analysis . Code stored in our source code repositories is checked for best practices and identifiable software flaws using automated tooling. Penetration testing . We maintain relationships with industry-recognized penetration testing service providers for penetration testing of the Neon web application, API, and proximity and authentications flows at least annually. The intent of these penetration tests is to identify security vulnerabilities and mitigate the risk and business impact they pose to the in-scope systems. Limitations of Privilege & Authorization Requirements . Product access . A subset of our employees have access to the products and to customer data via controlled interfaces. The intent of providing access to a subset of employees is to provide effective customer support, product development and research, to troubleshoot potential problems, to detect and respond to security incidents and implement data security. Access is enabled through “just in time” (JITA) requests for access; all such requests are logged. Employees are granted access by role, and reviews of high risk privilege grants are initiated as needed. Administrative or high risk access permissions are reviewed at least annually. Reference checks . Where permitted by applicable law, Databricks and Neon employees undergo reference checks. All Databricks and Neon employees are required to conduct themselves in a manner consistent with company guidelines, non-disclosure requirements, and ethical standards. Transmission Control In-transit . We require HTTPS encryption (also referred to as SSL or TLS) on all login interfaces. Our HTTPS implementation uses industry standard algorithms and certificates. At-rest . We store user passwords following policies that follow industry standard practices for security. We have implemented technologies to ensure that stored data is encrypted at rest. I nput Control . Detection . We designed our infrastructure to log extensive information about the system behavior, traffic received, system authentication, and other application requests. Internal systems aggregate log data and alert appropriate employees of malicious, unintended, or anomalous activities. Our personnel, including security, operations, and support personnel, are responsive to known incidents. Response and tracking . We maintain a record of known security incidents that includes description, dates and times of relevant activities, and incident disposition. Suspected and confirmed security incidents are investigated by security, operations, or support personnel; and appropriate resolution steps are identified and documented. For any confirmed incidents, we will take appropriate steps to minimize product and Customer damage or unauthorized disclosure. Notification to you will be in accordance with the terms of the Agreement. Availability Control . Online replicas and backups . Where feasible, production databases are designed to replicate data between no less than 1 primary and 1 secondary database. All databases are backed up and maintained using at least industry standard methods. Disaster Recovery Plans . We maintain and regularly test disaster recovery plans to help ensure availability of information following interruption to, or failure of, critical business processes. Our products are designed to ensure redundancy and seamless failover. The server instances that support the products are also architected with a goal to prevent single points of failure. This design assists our operations in maintaining and updating the product applications and backend while limiting downtime. 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/adventuresinangular/angular-signals-vs-rxjs-aia-389#main-content | Angular Signals VS RxJS - AiA 389 - 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 Adventures in Angular Follow Angular Signals VS RxJS - AiA 389 Sep 7 '23 play Armen, Lucas, and Subrat join this week's panelist episode. They talk about the fascinating topic of using signals and observables in Angular. They also explore the differences between the two approaches, their use cases, and how you can enhance your development process. Moreover, they dive into the reactive graph systems to handling loading states, and many more! Sponsors Chuck's Resume Template Raygun - Application Monitoring For Web & Mobile Apps Developer Book Club starting Links Unvoid - Angular Experts - Design and web development services with enormous expertise in Angular for companies that truly care about quality https://unvoid.com/ Social Media Unvoid LinkedIn @unvoidweb https://www.linkedin.com/company/unvoidweb Instagram @unvoidweb https://www.instagram.com/unvoidweb Lucas Paganini YouTube @lucaspaganiniweb https://youtube.com/@lucaspaganiniweb LinkedIn @lucaspaganiniweb https://www.linkedin.com/in/lucaspaganiniweb Twitter @lucaspaganini https://twitter.com/LucasPaganini Instagram @lucaspaganini https://www.instagram.com/lucaspaganini Subrat Mishra YouTube @FunOfHeuristic https://www.youtube.com/@FunOfHeuristic Armen Vardanyan LinkedIn @ArmenVardanyan h ttps://www.linkedin.com/in/armen-vardanyan-am/ Advertising Inquiries: https://redcircle.com/brands Privacy & Opt-Out: https://redcircle.com/privacy Episode source Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Your browser does not support the audio element. 1x initializing... × 💎 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://secure.gravatar.com | Your Free Avatar, Profile, and Link In Bio | Gravatar Link in Bio Developers Support Log in Get Started Now Gravatar.com Developer API Support Create a new Gravatar profile and make it your go to place on the web. Claim your free profile Log in Menu Gravatar.com Developer API Support Create a new Gravatar profile and make it your go to place on the web. Claim your free profile Log in Your Free Profile For The Web Transform your email address into your digital passport – one avatar, one bio, social connections, and verified links. Get Started Now Gravatar is used by WordPress GitHub Slack OpenAI Atlassian Figma Mailchimp Stack Overflow Coinbase Update Once, Sync Everywhere When you update your avatar or profile, your changes appear instantly across thousands of platforms. Save time and maintain a consistent online presence effortlessly. Your Profile, Your Way Share your social media profiles, portfolio, website, and other relevant links easily. Your Gravatar profile works like a digital business card — simple, elegant, and uniquely you. Perfect for your link-in-bio. Claim Your Free Profile Manage Multiple Identities Gravatar links your identity to an email address, not your name. Seamlessly manage your work, personal, and anonymous profiles. Privacy First Design You're in control. Make your profile private or choose what you share and when. With Gravatar, your data is yours and yours alone. PROFILES-AS-A-SERVICE For Developers Customize user experiences and bootstrap your community with verified user profiles, including avatars, social links, and more. Integrating Gravatar is effortless with our REST API, SDKs, and easy-to-follow tutorials. Learn More About Our APIs example.js example.php 1 2 3 4 5 6 7 8 9 10 11 12 13 14 const sha256 = require( 'js-sha256' ); function getGravatarURL( email ) { // Trim leading and trailing whitespace from // an email address and force all characters // to lower case const address = String( email ).trim().toLowerCase(); // Create a SHA256 hash of the final string const hash = sha256( address ); // Grab the actual image URL return `https://gravatar.com/avatar/${ hash }`; } 1 2 3 4 5 6 7 8 9 10 11 12 function get_gravatar_url( $email ) { // Trim leading and trailing whitespace from // an email address and force all characters // to lower case $address = strtolower( trim( $email ) ); // Create an SHA256 hash of the final string $hash = hash( 'sha256', $address ); // Grab the actual image URL return 'https://gravatar.com/avatar/' . $hash; } You Asked, We Answered Is Gravatar really free? Yes, Gravatar profiles are completely free for individual users. We're committed to providing a valuable and open service for the web. Can I use a custom domain? Absolutely! You can personalize your Gravatar profile with your own domain. You can register a domain on our sister service, WordPress.com, and map it to your Gravatar profile. How does Gravatar compare with other link-in-bio services? Gravatar is an open alternative to profile page services like LinkTree. Integrated across millions of websites, Gravatar avatars and profiles ensure a consistent presence online. You have full control with no data lock-in and can use your own custom domain. Update your profile once, and it updates everywhere. Can I have multiple Gravatars? Yes! You can create different Gravatars and profiles for various aspects of your life — work, personal, hobbies, or anonymous profiles. Just create additional accounts using a different email address. Who owns Gravatar? Gravatar is a service by Automattic, the company behind WordPress.com, Tumblr, Pocket Casts, Day One, Beeper, WooCommerce, and other popular web services. We are passionate about open-source and making the web a more accessible place. Claim Your Free Gravatar Profile Today! Get Started Now Languages Features Link-in-bio Custom Domains WordPress Plugin Developers Developer Dashboard Developer Docs GitHub Support Docs Report Abuse Company About Press Terms of Service Privacy Policy Privacy Notice for CA Your Privacy Choices Powered by Create a Site An venture Work With Us | 2026-01-13T08:48:04 |
https://linkedin.com/company/suprsend | SuprSend | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now for free SuprSend Software Development San Francisco, CA 19,129 followers Communication Infrastructure for dev & product teams See jobs Follow View all 17 employees Report this company About us SuprSend is a central communication stack for easily creating, managing and delivering notifications to your end users on multiple channels. Our single notification API has all the features set, which enables you to send notifications in a reliable and scalable manner and take care of end user experience, thereby eliminating the need to develop any notification service in-house for transactional/engagement notifications. Website https://www.suprsend.com/ External link for SuprSend Industry Software Development Company size 11-50 employees Headquarters San Francisco, CA Type Privately Held Founded 2021 Specialties notifications, android push, ios push, email, sms, whatsapp, slack, Microsoft teams, Telegram, App Inbox, A/B Experiments, web push, RCS, preferences management, batching & digests, notification infrastructure, twilio, template builder, inapp inbox, and react sdk Products SuprSend SuprSend Push Notification Software SuprSend is a notification infrastructure as a service platform for easily creating, managing, and delivering notifications to your end users. SuprSend has all the features set which enable you to send notifications in a reliable and scalable manner, as well as take care of end-user experience, thereby eliminating the need to build any notification service in-house. Benefits of using SuprSend as your notification stack are that: * You do not have to do any vendor integrations for channels in your code. You can easily add/remove/prioritize vendors and channels from your SuprSend account, * You can design powerful templates for all channels together and manage them from a single place, * You can leverage powerful features to experiment fast with notifications and take care of end-user experience without writing a single line of code. Locations Primary San Francisco, CA 94104, US Get directions Bengaluru, KA 560102, IN Get directions Employees at SuprSend Deepak Deolalikar Samuel Sunderaraj Gaurav Verma Sathya Nellore Sampat See all employees Updates SuprSend reposted this SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share SuprSend 19,129 followers 4d Report this post 𝗧𝘆𝗽𝗲-𝘀𝗮𝗳𝗲 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗶𝗻 𝗦𝘂𝗽𝗿𝗦𝗲𝗻𝗱 🧩 Triggering workflows with loosely typed payloads often leads to bugs that only show up at runtime. To reduce that risk, SuprSend now supports schema-driven type generation for workflow triggers. You define the payload structure once as a JSON schema in SuprSend. From there, the CLI generates strongly-typed interfaces that you can use directly in your application code. What this improves: • Catch invalid payloads during development instead of production • Get IDE autocomplete and immediate feedback while coding • Keep workflow payloads consistent as schemas evolve • Avoid manually maintaining type definitions Type generation is available for 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, 𝗣𝘆𝘁𝗵𝗼𝗻, 𝗚𝗼, 𝗝𝗮𝘃𝗮, 𝗞𝗼𝘁𝗹𝗶𝗻, 𝗦𝘄𝗶𝗳𝘁, 𝗮𝗻𝗱 𝗗𝗮𝗿𝘁. Docs in the comments. 7 1 Comment Like Comment Share SuprSend 19,129 followers 2w Report this post [𝗟𝗜𝗩𝗘] 𝗛𝗼𝘀𝘁𝗲𝗱 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗣𝗮𝗴𝗲: 𝗥𝗲𝗮𝗱𝘆-𝘁𝗼-𝘂𝘀𝗲 𝘂𝘀𝗲𝗿 𝘀𝗲𝘁𝘁𝗶𝗻𝗴𝘀 🌍 SuprSend now gives you a ready-made Preference Page where users can manage how they receive notifications. Just link to it from your emails or SMS — no need to build or maintain your own preference system. It’s designed to help you stay compliant while giving users better control over their communication. We’ve now added full localization support so these pages work seamlessly for global audiences. What’s new: • Pages adapt automatically to the user’s locale • Category names, descriptions, and sections are rendered dynamically • Static page text is localized • Smart fallback when a regional language isn’t available If you’re sending notifications across regions, this makes preference management clearer for users and easier to scale for teams. Preview link in the comments. 5 Like Comment Share SuprSend 19,129 followers 3w Edited Report this post 𝗘𝘅𝗽𝗼𝗿𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 𝗗𝗮𝘁𝗮 𝘁𝗼 𝗔𝗺𝗮𝘇𝗼𝗻 𝗦𝟯 🚀 Now you can fully own and control your notifications data within your S3 bucket — create custom dashboards, debug delivery issues, or maintain audit trails for compliance. 𝗪𝗵𝗮𝘁'𝘀 𝗶𝗻𝗰𝗹𝘂𝗱𝗲𝗱: • Syncs every 5 minutes in encrypted Parquet files • Messages, Workflow Executions, and Requests • Automatic backfills and hourly partitions • Works natively with Athena, Snowflake, BigQuery, Redshift Confidently build dashboards, surface notification logs to customers, or track entire customer lifecycle end-to-end. Docs in comments 👇 9 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new UI / UX Designer in Bengaluru, Karnataka. Apply today or share this post with your network. UI / UX Designer SuprSend, Bengaluru, Karnataka, India 7 Like Comment Share SuprSend 19,129 followers 1mo Edited Report this post 𝗖𝗮𝘁𝗲𝗴𝗼𝗿𝘆 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗼𝗿 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗖𝗲𝗻𝘁𝗲𝗿𝘀 🌍 In pursuit of seamless translations: preference categories now display in your user's locale. 𝗪𝗵𝗮𝘁 𝘁𝗵𝗶𝘀 𝗺𝗲𝗮𝗻𝘀: • One preference center works globally (no separate versions for each region) • Users make informed choices when they see categories in their preferred language • Add translations through Dashboard, API, or CLI • Smart fallback logic ensures something always displays (es-mx → es → en) If you're shipping notifications to a multilingual audience, this removes friction for both your users and your team. Docs in comments below 👇 13 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Report this post 𝗛𝗼𝘄 𝗖𝗿𝗮𝘇𝘆𝗚𝗮𝗺𝗲𝘀 𝗖𝘂𝘁 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 𝗳𝗿𝗼𝗺 𝗪𝗲𝗲𝗸𝘀 𝘁𝗼 𝗛𝗼𝘂𝗿𝘀 CrazyGames serves 45M+ monthly players across 3,000+ browser games. But their in-house notification system held them back. 🎮 𝗧𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺: Building notifications required heavy engineering involvement. Even small template changes meant creating dev tickets and took 2 weeks to deploy. Product teams couldn't personalize or experiment fast without developer time. 𝗪𝗵𝗮𝘁 𝗰𝗵𝗮𝗻𝗴𝗲𝗱: CrazyGames adopted SuprSend to abstract notification development out of code. Templates, logic, and workflows shifted entirely to Product & Design. They also connected their database to SuprSend, allowing teams to create targeted cohorts by writing SQL — no data exports, no syncing delays, no engineering bottlenecks. 𝗧𝗵𝗲 𝗿𝗲𝘀𝘂𝗹𝘁: • Notification launches: weeks → hours • Self-serve campaigns with personalized game recommendations • A/B testing across email, push, and in-app — all unified • Product teams operate independently 🎥 Watch Jonas (VP of Product, CrazyGames) full story link in comments below. 33 4 Comments Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new Founders’ Office – Product Marketing in Bengaluru, Karnataka. Apply today or share this post with your network. Product Marketing Manager SuprSend, Bengaluru, Karnataka, India 9 1 Comment Like Comment Share SuprSend 19,129 followers 1mo Edited Report this post 𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗶𝗻𝗴 𝗧𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗶𝗻 𝗡𝗼𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 Maintaining separate notification templates for every language doesn't scale. Change one template and you update all language versions manually. Translations solve this. Write one template that works across all languages. SuprSend automatically serves the right language based on user locale, with intelligent fallbacks. What's included: • Upload existing JSON translation files & manage through CLI/API • Smart translation keys with automatic language selection • Dynamic variables and pluralization handling • Namespaced keys to organize by feature • Change history with rollback support Documentation in the comments 👇 13 4 Comments Like Comment Share SuprSend 19,129 followers 1mo Report this post We're #hiring a new Product Manager in Bengaluru, Karnataka. Apply today or share this post with your network. Product Manager SuprSend, Bengaluru, Karnataka, India 4 Like Comment Share Join now to see what you are missing Find people you know at SuprSend Browse recommended jobs for you View all updates, news, and articles Join now Similar pages SuperSend Software Development Las Vegas, Nevada Crew Technology, Information and Internet Keploy 🐰 Technology, Information and Internet San Franciso, California KubeSense Software Development Austin, Texas Gushwork Software Development Brooklyn, New York Robylon AI Software Development San Francisco, California Cube Technology, Information and Internet Palo Alto, California Klaar Software Development San Francisco, California Bik.ai Technology, Information and Internet Zime Data Infrastructure and Analytics San Jose, CA Show more similar pages Show fewer similar pages Browse jobs Engineer jobs 555,845 open jobs Product Marketer jobs 9,108 open jobs Marketing Manager jobs 106,879 open jobs Scientist jobs 48,969 open jobs Machine Learning Engineer jobs 148,937 open jobs Developer jobs 258,935 open jobs Marketer jobs 37,677 open jobs Intelligence Specialist jobs 7,156 open jobs Intern jobs 71,196 open jobs Python Developer jobs 46,642 open jobs Senior Product Marketing Manager jobs 11,129 open jobs Analyst jobs 694,057 open jobs Manager jobs 1,880,925 open jobs Associate Product Manager jobs 76,300 open jobs General Engineer jobs 54,597 open jobs Software Engineer jobs 300,699 open jobs Associate jobs 1,091,945 open jobs Account Manager jobs 121,519 open jobs Marketing Specialist jobs 49,178 open jobs Digital Marketing Manager jobs 17,135 open jobs Show more jobs like this Show fewer jobs like this Funding SuprSend 1 total round Last Round Seed Oct 14, 2022 External Crunchbase Link for last round of funding US$ 1.0M Investors BoldCap + 4 Other investors See more info on crunchbase More searches More searches Engineer jobs Developer jobs Marketing Manager jobs Machine Learning Engineer jobs Intelligence Specialist jobs Scientist jobs Associate Product Manager jobs Analyst jobs Software Engineer jobs Intern jobs Product Management Intern jobs Talent Specialist jobs Global Marketing Manager jobs Consultant jobs Marketing Lead jobs Marketing Specialist jobs Product Marketer jobs Writer jobs Frontend Developer jobs Program Management Intern jobs Product Manager jobs Associate Project Manager jobs Network Developer jobs Account Manager jobs Digital Marketing Manager jobs Manager jobs Product Engineer jobs Senior Developer jobs Application Engineer jobs Customer Service Technician jobs Advocate jobs Linux Developer jobs Security Administrator jobs Web Developer jobs Senior Software Engineer jobs Full Stack Engineer jobs Data Scientist jobs Curriculum Developer jobs Sales Trainer jobs Science Specialist jobs Web Development Specialist jobs Security Engineer jobs Software Engineer Intern jobs Staff Software Engineer jobs Technology Engineer jobs Lead Software Engineer jobs Research Software Engineer jobs Business Development Associate jobs Technician jobs Content Specialist jobs iOS Developer jobs Senior Product Manager jobs User Interface Designer jobs PHP Developer jobs Product Designer jobs Director jobs Bookkeeper jobs User Experience Designer jobs Operations Engineer jobs Founder jobs LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (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)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Sign in to see who you already know at SuprSend Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:04 |
https://www.linkedin.com/in/clydecutting/ | Clyde Cutting - Truist | LinkedIn Skip to main content LinkedIn Top Content People Learning Jobs Games Sign in Join now Sign in to view Clyde’s full profile Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Clyde Cutting Sign in to view Clyde’s full profile Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Minneapolis, Minnesota, United States Contact Info Sign in to view Clyde’s full profile Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . 1K followers 500+ connections See your mutual connections View mutual connections with Clyde Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Join to view profile Message Sign in to view Clyde’s full profile Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Truist University of St. Thomas, St. Paul, MN Report this profile About SOA, Microservices and Solutions Architect for financial industry enterprise and line of… see more Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now Activity Follow Sign in to view Clyde’s full profile Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . A 103-year-old doctor just exposed modern medicine: ⤵ We’ve heard this before. A nurse listening to the dying. Regrets spoken too late. Lessons… A 103-year-old doctor just exposed modern medicine: ⤵ We’ve heard this before. A nurse listening to the dying. Regrets spoken too late. Lessons… Liked by Clyde Cutting Experience & Education *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> Truist *]:mb-0 not-first-middot leading-[1.75]"> **** ******* *********** ********** **** ********* *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> ********* **** ******** *]:mb-0 not-first-middot leading-[1.75]"> ********* *** *** ********* ********** *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> **** ********* ******** *]:mb-0 not-first-middot leading-[1.75]"> *** ********* *********** *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> ********** ** *** ******* *** ***** ** *]:mb-0 not-first-middot leading-[1.75]"> ******* ******** undefined undefined *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> 1990 - 1994 *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> **** ******* *]:mb-0 not-first-middot leading-[1.75]"> ** undefined *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> 1981 - 1986 View Clyde’s full experience See their title, tenure and more. Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . Licenses & Certifications *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> ANSI Accredited CrossFit Level 1 Trainer Certificate *]:mb-0 not-first-middot leading-[1.75]"> CrossFit.com *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> Issued Apr 2011 Credential ID 30971504 *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> IBM VisualAge for Smalltalk, Certified Developer *]:mb-0 not-first-middot leading-[1.75]"> IBM *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> Issued Nov 1996 *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> Certified Passive House Tradesperson *]:mb-0 not-first-middot leading-[1.75]"> Passive House Institute *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> Issued Jan 2020 Expires Jan 2025 See credential *]:mb-0 text-[18px] text-color-text leading-regular group-hover:underline font-semibold"> Passed first 3-1/2 of 10 exams for Life Actuary *]:mb-0 not-first-middot leading-[1.75]"> Society of Actuaries *]:mb-0 [&>*]:text-md [&>*]:text-color-text-low-emphasis"> Recommendations received LinkedIn User “I worked on several technical projects with Clyde, he as principal architect. I worked as a change leader for an extensive technical middleware group. The projects required his input and guidance to insure the internal client needs were met within acceptable limits and capabilities. I found him to be a very thoughtful, competent person both technically and in his business conduct.” Pradeep W. “Clyde was instrumental as an Architect in one of my projects. He dealt with technical challenges with high professional conduct. Working with Clyde was a pleasant experience.” 2 people have recommended Clyde Join now to view View Clyde’s full profile See who you know in common Get introduced Contact Clyde directly Join to view full profile Other similar profiles Sridhar Pothkan Sridhar Pothkan Plano, TX Connect Ankit Kumar Ankit Kumar New York City Metropolitan Area Connect Rick Gansler Rick Gansler Worcester, MA Connect Victor Grazi Victor Grazi Toms River, NJ Connect Tim Cramer Tim Cramer Greater Boston Connect Ashay Thakur Ashay Thakur Chelmsford, MA Connect Arpit Patel Arpit Patel San Francisco, CA Connect Alex Freixas Alex Freixas Washington DC-Baltimore Area Connect Jayesh Govindarajan Jayesh Govindarajan Palo Alto, CA Connect Rick H. Rick H. Austin, Texas Metropolitan Area Connect Prayag Pathak Prayag Pathak United States Connect Erik Benner Erik Benner Atlanta Metropolitan Area Connect Mike W. Mike W. Vero Beach, FL Connect Ravi Jagannathan Ravi Jagannathan Boston, MA Connect Amin Vahdat Amin Vahdat Mountain View, CA Connect Amit Gupta Amit Gupta Dallas-Fort Worth Metroplex Connect Andrew Clay Shafer Andrew Clay Shafer Greater Tucson Area Connect Murali Batchu Murali Batchu Baltimore City County, MD Connect Venugopal Rao Gubbala Venugopal Rao Gubbala United States Connect Manuel Rocha Manuel Rocha Miami-Fort Lauderdale Area Connect Show more profiles Show fewer profiles Explore top content on LinkedIn Find curated posts and insights for relevant topics all in one place. View top content Add new skills with these courses 2h 44m Hands-On Advanced SQL Server: Strategies and Techniques 2h 19m Advanced Data Engineering with Snowflake 1h 15m Planning and Releasing Software with Jira See all courses LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines العربية (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)) Language Agree & Join LinkedIn By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . View Clyde’s full profile Sign in Welcome back Email or phone Password Show Forgot password? Sign in or By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . New to LinkedIn? Join now or New to LinkedIn? Join now By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . | 2026-01-13T08:48:04 |
https://datatracker.ietf.org/doc/html/rfc7807 | RFC 7807 - Problem Details for HTTP APIs Light Dark Auto RFC 7807 Proposed Standard Title Problem Details for HTTP APIs Document Document type RFC - Proposed Standard March 2016 View errata Report errata Obsoleted by RFC 9457 Was draft-ietf-appsawg-http-problem ( appsawg WG ) Select version 00 01 02 03 RFC 7807 Compare versions RFC 7807 draft-ietf-appsawg-http-problem-03 draft-ietf-appsawg-http-problem-02 draft-ietf-appsawg-http-problem-01 draft-ietf-appsawg-http-problem-00 RFC 7807 draft-ietf-appsawg-http-problem-03 draft-ietf-appsawg-http-problem-02 draft-ietf-appsawg-http-problem-01 draft-ietf-appsawg-http-problem-00 Side-by-side Inline Authors Mark Nottingham , Erik Wilde Email authors RFC stream Other formats txt html pdf w/errata bibtex Additional resources Mailing list discussion Report a bug Internet Engineering Task Force (IETF) M. Nottingham Request for Comments: 7807 Akamai Category: Standards Track E. Wilde ISSN: 2070-1721 March 2016 Problem Details for HTTP APIs Abstract This document defines a "problem detail" as a way to carry machine- readable details of errors in a HTTP response to avoid the need to define new error response formats for HTTP APIs. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741 . Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7807 . Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents ( http://trustee.ietf.org/license-info ) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Nottingham & Wilde Standards Track [Page 1] RFC 7807 Problem Details March 2016 Table of Contents 1 . Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2 . Requirements . . . . . . . . . . . . . . . . . . . . . . . . 3 3 . The Problem Details JSON Object . . . . . . . . . . . . . . . 3 3.1 . Members of a Problem Details Object . . . . . . . . . . . 5 3.2 . Extension Members . . . . . . . . . . . . . . . . . . . . 6 4 . Defining New Problem Types . . . . . . . . . . . . . . . . . 6 4.1 . Example . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.2 . Predefined Problem Types . . . . . . . . . . . . . . . . 8 5 . Security Considerations . . . . . . . . . . . . . . . . . . . 8 6 . IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6.1 . application/problem+json . . . . . . . . . . . . . . . . 9 6.2 . application/problem+xml . . . . . . . . . . . . . . . . . 10 7 . References . . . . . . . . . . . . . . . . . . . . . . . . . 11 7.1 . Normative References . . . . . . . . . . . . . . . . . . 11 7.2 . Informative References . . . . . . . . . . . . . . . . . 12 Appendix A . HTTP Problems and XML . . . . . . . . . . . . . . . 14 Appendix B . Using Problem Details with Other Formats . . . . . . 15 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 1 . Introduction HTTP [ RFC7230 ] status codes are sometimes not sufficient to convey enough information about an error to be helpful. While humans behind Web browsers can be informed about the nature of the problem with an HTML [ W3C.REC-html5-20141028 ] response body, non-human consumers of so-called "HTTP APIs" are usually not. This specification defines simple JSON [ RFC7159 ] and XML [ W3C.REC-xml-20081126 ] document formats to suit this purpose. They are designed to be reused by HTTP APIs, which can identify distinct "problem types" specific to their needs. Thus, API clients can be informed of both the high-level error class (using the status code) and the finer-grained details of the problem (using one of these formats). For example, consider a response that indicates that the client's account doesn't have enough credit. The 403 Forbidden status code might be deemed most appropriate to use, as it will inform HTTP- generic software (such as client libraries, caches, and proxies) of the general semantics of the response. However, that doesn't give the API client enough information about why the request was forbidden, the applicable account balance, or how to correct the problem. If these details are included in the Nottingham & Wilde Standards Track [Page 2] RFC 7807 Problem Details March 2016 response body in a machine-readable format, the client can treat it appropriately; for example, triggering a transfer of more credit into the account. This specification does this by identifying a specific type of problem (e.g., "out of credit") with a URI [ RFC3986 ]; HTTP APIs can do this by nominating new URIs under their control, or by reusing existing ones. Additionally, problem details can contain other information, such as a URI that identifies the specific occurrence of the problem (effectively giving an identifier to the concept "The time Joe didn't have enough credit last Thursday"), which can be useful for support or forensic purposes. The data model for problem details is a JSON [ RFC7159 ] object; when formatted as a JSON document, it uses the "application/problem+json" media type. Appendix A defines how to express them in an equivalent XML format, which uses the "application/problem+xml" media type. Note that problem details are (naturally) not the only way to convey the details of a problem in HTTP; if the response is still a representation of a resource, for example, it's often preferable to accommodate describing the relevant details in that application's format. Likewise, in many situations, there is an appropriate HTTP status code that does not require extra detail to be conveyed. Instead, the aim of this specification is to define common error formats for those applications that need one, so that they aren't required to define their own, or worse, tempted to redefine the semantics of existing HTTP status codes. Even if an application chooses not to use it to convey errors, reviewing its design can help guide the design decisions faced when conveying errors in an existing format. 2 . Requirements The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [ RFC2119 ]. 3 . The Problem Details JSON Object The canonical model for problem details is a JSON [ RFC7159 ] object. When serialized as a JSON document, that format is identified with the "application/problem+json" media type. Nottingham & Wilde Standards Track [Page 3] RFC 7807 Problem Details March 2016 For example, an HTTP response carrying JSON problem details: HTTP/1.1 403 Forbidden Content-Type: application/problem+json Content-Language: en { "type": "https://example.com/probs/out-of-credit", "title": "You do not have enough credit.", "detail": "Your current balance is 30, but that costs 50.", "instance": "/account/12345/msgs/abc", "balance": 30, "accounts": ["/account/12345", "/account/67890"] } Here, the out-of-credit problem (identified by its type URI) indicates the reason for the 403 in "title", gives a reference for the specific problem occurrence with "instance", gives occurrence- specific details in "detail", and adds two extensions; "balance" conveys the account's balance, and "accounts" gives links where the account can be topped up. The ability to convey problem-specific extensions allows more than one problem to be conveyed. For example: HTTP/1.1 400 Bad Request Content-Type: application/problem+json Content-Language: en { "type": "https://example.net/validation-error", "title": "Your request parameters didn't validate.", "invalid-params": [ { "name": "age", "reason": "must be a positive integer" }, { "name": "color", "reason": "must be 'green', 'red' or 'blue'"} ] } Note that this requires each of the subproblems to be similar enough to use the same HTTP status code. If they do not, the 207 (Multi- Status) [ RFC4918 ] code could be used to encapsulate multiple status messages. Nottingham & Wilde Standards Track [Page 4] RFC 7807 Problem Details March 2016 3.1 . Members of a Problem Details Object A problem details object can have the following members: o "type" (string) - A URI reference [ RFC3986 ] that identifies the problem type. This specification encourages that, when dereferenced, it provide human-readable documentation for the problem type (e.g., using HTML [ W3C.REC-html5-20141028 ]). When this member is not present, its value is assumed to be "about:blank". o "title" (string) - A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4 ). o "status" (number) - The HTTP status code ( [RFC7231], Section 6 ) generated by the origin server for this occurrence of the problem. o "detail" (string) - A human-readable explanation specific to this occurrence of the problem. o "instance" (string) - A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced. Consumers MUST use the "type" string as the primary identifier for the problem type; the "title" string is advisory and included only for users who are not aware of the semantics of the URI and do not have the ability to discover them (e.g., offline log analysis). Consumers SHOULD NOT automatically dereference the type URI. The "status" member, if present, is only advisory; it conveys the HTTP status code used for the convenience of the consumer. Generators MUST use the same status code in the actual HTTP response, to assure that generic HTTP software that does not understand this format still behaves correctly. See Section 5 for further caveats regarding its use. Consumers can use the status member to determine what the original status code used by the generator was, in cases where it has been changed (e.g., by an intermediary or cache), and when message bodies persist without HTTP information. Generic HTTP software will still use the HTTP status code. The "detail" member, if present, ought to focus on helping the client correct the problem, rather than giving debugging information. Nottingham & Wilde Standards Track [Page 5] RFC 7807 Problem Details March 2016 Consumers SHOULD NOT parse the "detail" member for information; extensions are more suitable and less error-prone ways to obtain such information. Note that both "type" and "instance" accept relative URIs; this means that they must be resolved relative to the document's base URI, as per [RFC3986], Section 5 . 3.2 . Extension Members Problem type definitions MAY extend the problem details object with additional members. For example, our "out of credit" problem above defines two such extensions -- "balance" and "accounts" to convey additional, problem- specific information. Clients consuming problem details MUST ignore any such extensions that they don't recognize; this allows problem types to evolve and include additional information in the future. Note that because extensions are effectively put into a namespace by the problem type, it is not possible to define new "standard" members without defining a new media type. 4 . Defining New Problem Types When an HTTP API needs to define a response that indicates an error condition, it might be appropriate to do so by defining a new problem type. Before doing so, it's important to understand what they are good for, and what's better left to other mechanisms. Problem details are not a debugging tool for the underlying implementation; rather, they are a way to expose greater detail about the HTTP interface itself. Designers of new problem types need to carefully consider the Security Considerations ( Section 5 ), in particular, the risk of exposing attack vectors by exposing implementation internals through error messages. Likewise, truly generic problems -- i.e., conditions that could potentially apply to any resource on the Web -- are usually better expressed as plain status codes. For example, a "write access disallowed" problem is probably unnecessary, since a 403 Forbidden status code in response to a PUT request is self-explanatory. Nottingham & Wilde Standards Track [Page 6] RFC 7807 Problem Details March 2016 Finally, an application might have a more appropriate way to carry an error in a format that it already defines. Problem details are intended to avoid the necessity of establishing new "fault" or "error" document formats, not to replace existing domain-specific formats. That said, it is possible to add support for problem details to existing HTTP APIs using HTTP content negotiation (e.g., using the Accept request header to indicate a preference for this format; see [RFC7231], Section 5.3.2 ). New problem type definitions MUST document: 1. a type URI (typically, with the "http" or "https" scheme), 2. a title that appropriately describes it (think short), and 3. the HTTP status code for it to be used with. Problem type definitions MAY specify the use of the Retry-After response header ( [RFC7231], Section 7.1.3 ) in appropriate circumstances. A problem's type URI SHOULD resolve to HTML [ W3C.REC-html5-20141028 ] documentation that explains how to resolve the problem. A problem type definition MAY specify additional members on the problem details object. For example, an extension might use typed links [ RFC5988 ] to another resource that can be used by machines to resolve the problem. If such additional members are defined, their names SHOULD start with a letter (ALPHA, as per [RFC5234], Appendix B.1 ) and SHOULD consist of characters from ALPHA, DIGIT ( [RFC5234], Appendix B.1 ), and "_" (so that it can be serialized in formats other than JSON), and they SHOULD be three characters or longer. 4.1 . Example For example, if you are publishing an HTTP API to your online shopping cart, you might need to indicate that the user is out of credit (our example from above), and therefore cannot make the purchase. Nottingham & Wilde Standards Track [Page 7] RFC 7807 Problem Details March 2016 If you already have an application-specific format that can accommodate this information, it's probably best to do that. However, if you don't, you might consider using one of the problem details formats -- JSON if your API is JSON-based, or XML if it uses that format. To do so, you might look for an already-defined type URI that suits your purposes. If one is available, you can reuse that URI. If one isn't available, you could mint and document a new type URI (which ought to be under your control and stable over time), an appropriate title and the HTTP status code that it will be used with, along with what it means and how it should be handled. In summary: an instance URI will always identify a specific occurrence of a problem. On the other hand, type URIs can be reused if an appropriate description of a problem type is already available someplace else, or they can be created for new problem types. 4.2 . Predefined Problem Types This specification reserves the use of one URI as a problem type: The "about:blank" URI [ RFC6694 ], when used as a problem type, indicates that the problem has no additional semantics beyond that of the HTTP status code. When "about:blank" is used, the title SHOULD be the same as the recommended HTTP status phrase for that code (e.g., "Not Found" for 404, and so on), although it MAY be localized to suit client preferences (expressed with the Accept-Language request header). Please note that according to how the "type" member is defined ( Section 3.1 ), the "about:blank" URI is the default value for that member. Consequently, any problem details object not carrying an explicit "type" member implicitly uses this URI. 5 . Security Considerations When defining a new problem type, the information included must be carefully vetted. Likewise, when actually generating a problem -- however it is serialized -- the details given must also be scrutinized. Risks include leaking information that can be exploited to compromise the system, access to the system, or the privacy of users of the system. Nottingham & Wilde Standards Track [Page 8] RFC 7807 Problem Details March 2016 Generators providing links to occurrence information are encouraged to avoid making implementation details such as a stack dump available through the HTTP interface, since this can expose sensitive details of the server implementation, its data, and so on. The "status" member duplicates the information available in the HTTP status code itself, thereby bringing the possibility of disagreement between the two. Their relative precedence is not clear, since a disagreement might indicate that (for example) an intermediary has modified the HTTP status code in transit (e.g., by a proxy or cache). As such, those defining problem types as well as generators and consumers of problems need to be aware that generic software (such as proxies, load balancers, firewalls, and virus scanners) are unlikely to know of or respect the status code conveyed in this member. 6 . IANA Considerations This specification defines two new Internet media types [ RFC6838 ]. 6.1 . application/problem+json Type name: application Subtype name: problem+json Required parameters: None Optional parameters: None; unrecognized parameters should be ignored Encoding considerations: Same as [ RFC7159 ] Security considerations: see Section 5 of this document Interoperability considerations: None Published specification: RFC 7807 (this document) Applications that use this media type: HTTP Fragment identifier considerations: Same as for application/json ([ RFC7159 ]) Nottingham & Wilde Standards Track [Page 9] RFC 7807 Problem Details March 2016 Additional information: Deprecated alias names for this type: n/a Magic number(s): n/a File extension(s): n/a Macintosh file type code(s): n/a Person and email address to contact for further information: Mark Nottingham <mnot@mnot.net> Intended usage: COMMON Restrictions on usage: None. Author: Mark Nottingham <mnot@mnot.net> Change controller: IESG 6.2 . application/problem+xml Type name: application Subtype name: problem+xml Required parameters: None Optional parameters: None; unrecognized parameters should be ignored Encoding considerations: Same as [ RFC7303 ] Security considerations: see Section 5 of this document Interoperability considerations: None Published specification: RFC 7807 (this document) Applications that use this media type: HTTP Fragment identifier considerations: Same as for application/xml (as specified by Section 5 of [RFC7303] ) Nottingham & Wilde Standards Track [Page 10] RFC 7807 Problem Details March 2016 Additional information: Deprecated alias names for this type: n/a Magic number(s): n/a File extension(s): n/a Macintosh file type code(s): n/a Person and email address to contact for further information: Mark Nottingham <mnot@mnot.net> Intended usage: COMMON Restrictions on usage: None. Author: Mark Nottingham <mnot@mnot.net> Change controller: IESG 7 . References 7.1 . Normative References [ RFC2119 ] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14 , RFC 2119 , DOI 10.17487/RFC2119, March 1997, < http://www.rfc-editor.org/info/rfc2119 >. [ RFC3986 ] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986 , DOI 10.17487/RFC3986, January 2005, < http://www.rfc-editor.org/info/rfc3986 >. [ RFC5234 ] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234 , DOI 10.17487/RFC5234, January 2008, < http://www.rfc-editor.org/info/rfc5234 >. [ RFC7159 ] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data Interchange Format", RFC 7159 , DOI 10.17487/RFC7159, March 2014, < http://www.rfc-editor.org/info/rfc7159 >. [ RFC7230 ] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing", RFC 7230 , DOI 10.17487/RFC7230, June 2014, < http://www.rfc-editor.org/info/rfc7230 >. Nottingham & Wilde Standards Track [Page 11] RFC 7807 Problem Details March 2016 [ RFC7231 ] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content", RFC 7231 , DOI 10.17487/RFC7231, June 2014, < http://www.rfc-editor.org/info/rfc7231 >. [ W3C.REC-xml-20081126 ] Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth Edition)", W3C Recommendation REC-xml-20081126, November 2008, < http://www.w3.org/TR/2008/REC-xml-20081126 >. 7.2 . Informative References [ ISO-19757-2 ] International Organization for Standardization, "Information Technology --- Document Schema Definition Languages (DSDL) --- Part 2: Grammar-based Validation --- RELAX NG", ISO/IEC 19757-2, 2003. [ RFC4918 ] Dusseault, L., Ed., "HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)", RFC 4918 , DOI 10.17487/RFC4918, June 2007, < http://www.rfc-editor.org/info/rfc4918 >. [ RFC5988 ] Nottingham, M., "Web Linking", RFC 5988 , DOI 10.17487/RFC5988, October 2010, < http://www.rfc-editor.org/info/rfc5988 >. [ RFC6694 ] Moonesamy, S., Ed., "The "about" URI Scheme", RFC 6694 , DOI 10.17487/RFC6694, August 2012, < http://www.rfc-editor.org/info/rfc6694 >. [ RFC6838 ] Freed, N., Klensin, J., and T. Hansen, "Media Type Specifications and Registration Procedures", BCP 13 , RFC 6838 , DOI 10.17487/RFC6838, January 2013, < http://www.rfc-editor.org/info/rfc6838 >. [ RFC7303 ] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303 , DOI 10.17487/RFC7303, July 2014, < http://www.rfc-editor.org/info/rfc7303 >. [ W3C.REC-html5-20141028 ] Hickson, I., Berjon, R., Faulkner, S., Leithead, T., Navara, E., O'Connor, E., and S. Pfeiffer, "HTML5", W3C Recommendation REC-html5-20141028, October 2014, < http://www.w3.org/TR/2014/REC-html5-20141028 >. Nottingham & Wilde Standards Track [Page 12] RFC 7807 Problem Details March 2016 [ W3C.REC-rdfa-core-20130822 ] Adida, B., Birbeck, M., McCarron, S., and I. Herman, "RDFa Core 1.1 - Second Edition", W3C Recommendation REC-rdfa-core-20130822, August 2013, < http://www.w3.org/TR/2013/REC-rdfa-core-20130822 >. [ W3C.REC-xml-stylesheet-20101028 ] Clark, J., Pieters, S., and H. Thompson, "Associating Style Sheets with XML documents 1.0 (Second Edition)", W3C Recommendation REC-xml-stylesheet-20101028, October 2010, < http://www.w3.org/TR/2010/REC-xml-stylesheet-20101028 >. Nottingham & Wilde Standards Track [Page 13] RFC 7807 Problem Details March 2016 Appendix A . HTTP Problems and XML Some HTTP-based APIs use XML [ W3C.REC-xml-20081126 ] as their primary format convention. Such APIs can express problem details using the format defined in this appendix. The RELAX NG schema [ ISO-19757-2 ] for the XML format is as follows. Keep in mind that this schema is only meant as documentation, and not as a normative schema that captures all constraints of the XML format. Also, it would be possible to use other XML schema languages to define a similar set of constraints (depending on the features of the chosen schema language). default namespace ns = "urn:ietf:rfc:7807" start = problem problem = element problem { ( element type { xsd:anyURI }? & element title { xsd:string }? & element detail { xsd:string }? & element status { xsd:positiveInteger }? & element instance { xsd:anyURI }? ), anyNsElement } anyNsElement = ( element ns:* { anyNsElement | text } | attribute * { text })* The media type for this format is "application/problem+xml". Extension arrays and objects are serialized into the XML format by considering an element containing a child or children to represent an object, except for elements that contain only child element(s) named 'i', which are considered arrays. For example, the example above appears in XML as follows: Nottingham & Wilde Standards Track [Page 14] RFC 7807 Problem Details March 2016 HTTP/1.1 403 Forbidden Content-Type: application/problem+xml Content-Language: en <?xml version="1.0" encoding="UTF-8"?> <problem xmlns="urn:ietf:rfc:7807"> <type>https://example.com/probs/out-of-credit</type> <title>You do not have enough credit.</title> <detail>Your current balance is 30, but that costs 50.</detail> <instance>https://example.net/account/12345/msgs/abc</instance> <balance>30</balance> <accounts> <i>https://example.net/account/12345</i> <i>https://example.net/account/67890</i> </accounts> </problem> Note that this format uses an XML namespace. This is primarily to allow embedding it into other XML-based formats; it does not imply that it can or should be extended with elements or attributes in other namespaces. The RELAX NG schema explicitly only allows elements from the one namespace used in the XML format. Any extension arrays and objects MUST be serialized into XML markup using only that namespace. When using the XML format, it is possible to embed an XML processing instruction in the XML that instructs clients to transform the XML, using the referenced XSLT code [ W3C.REC-xml-stylesheet-20101028 ]. If this code is transforming the XML into (X)HTML, then it is possible to serve the XML format, and yet have clients capable of performing the transformation display human-friendly (X)HTML that is rendered and displayed at the client. Note that when using this method, it is advisable to use XSLT 1.0 in order to maximize the number of clients capable of executing the XSLT code. Appendix B . Using Problem Details with Other Formats In some situations, it can be advantageous to embed problem details in formats other than those described here. For example, an API that uses HTML [ W3C.REC-html5-20141028 ] might want to also use HTML for expressing its problem details. Problem details can be embedded in other formats either by encapsulating one of the existing serializations (JSON or XML) into that format or by translating the model of a problem detail (as specified in Section 3 ) into the format's conventions. Nottingham & Wilde Standards Track [Page 15] RFC 7807 Problem Details March 2016 For example, in HTML, a problem could be embedded by encapsulating JSON in a script tag: <script type="application/problem+json"> { "type": "https://example.com/probs/out-of-credit", "title": "You do not have enough credit.", "detail": "Your current balance is 30, but that costs 50.", "instance": "/account/12345/msgs/abc", "balance": 30, "accounts": ["/account/12345", "/account/67890"] } </script> or by inventing a mapping into RDFa [ W3C.REC-rdfa-core-20130822 ]. This specification does not make specific recommendations regarding embedding problem details in other formats; the appropriate way to embed them depends both upon the format in use and application of that format. Acknowledgements The authors would like to thank Jan Algermissen, Subbu Allamaraju, Mike Amundsen, Roy Fielding, Eran Hammer, Sam Johnston, Mike McCall, Julian Reschke, and James Snell for review of this specification. Authors' Addresses Mark Nottingham Akamai Email: mnot@mnot.net URI: https://www.mnot.net/ Erik Wilde Email: erik.wilde@dret.net URI: http://dret.net/netdret/ Nottingham & Wilde Standards Track [Page 16] Datatracker RFC 7807 RFC - Proposed Standard Info Contents Prefs Document Document type RFC - Proposed Standard March 2016 View errata Report errata Obsoleted by RFC 9457 Was draft-ietf-appsawg-http-problem ( appsawg WG ) Select version 00 01 02 03 RFC 7807 Compare versions RFC 7807 draft-ietf-appsawg-http-problem-03 draft-ietf-appsawg-http-problem-02 draft-ietf-appsawg-http-problem-01 draft-ietf-appsawg-http-problem-00 RFC 7807 draft-ietf-appsawg-http-problem-03 draft-ietf-appsawg-http-problem-02 draft-ietf-appsawg-http-problem-01 draft-ietf-appsawg-http-problem-00 Side-by-side Inline Authors Mark Nottingham , Erik Wilde Email authors RFC stream Other formats txt html pdf w/errata bibtex Additional resources Mailing list discussion Report a datatracker bug Show sidebar by default Yes No Tab to show by default Info Contents HTMLization configuration HTMLize the plaintext Plaintextify the HTML Maximum font size Page dependencies Inline Reference Citation links Go to reference section Go to linked document | 2026-01-13T08:48:04 |
https://sessionize.com/s/shahadarsh/from_infrastructure_as_code_to_envi/42534 | Adarsh Shah's Speaker Profile @ Sessionize Jump to navigation Jump to content Menu Speakers Directory Favorites Login Join for Free Speaker Report profile Adarsh Shah Founder & CEO at CloudKnit New York City, New York, United States Actions Favorite Contact Adarsh Shah is the Founder & CEO of CloudKnit. He is an Engineering Leader, Coach, Public Speaker, Hands-on Architect & a Change Agent. He is also an organizer for Devopsdays NYC conference & devopsnyc meetup. Adarsh has a keen interest in building systems that add business value. These days, he is excited about working with Machine Learning and Cloud-Native technologies. You can reach him on twitter at @shahadarsh. Links @shahadarsh LinkedIn Blog Company Area of Expertise Information & Communications Technology Topics DevOps Cloud & DevOps Infrastructure as Code Platform Engineering Adarsh Shah Founder & CEO at CloudKnit New York City, New York, United States Links @shahadarsh LinkedIn Blog Company Actions Favorite Contact Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know . Jump to top Report this profile Select a reason Does not belong to a private person Does not represent a speaker Info and/or images include abusive or hateful content Spam profile Other reason (contact form will open) Report Thanks. We will evaluate your report and take appropriate actions. Contact Adarsh Contact type Invite to your Sessionize event Contact directly Invite to your event Please login to invite Adarsh to your event. Login Contact directly You can contact the speaker through their preferred channels. Tell speakers how you found them to kickstart the conversation. @shahadarsh LinkedIn Blog Company Copy message Hey Adarsh, I found your speaker profile at https://sessionize.com/shahadarsh and I wanted to... | 2026-01-13T08:48:04 |
https://livesuggest.ai/ja/ | ボットなしAI会議アシスタント | リアルタイム提案 - LiveSuggest LiveSuggest 1時間無料 料金 ログイン 登録 セッションを開始 日本語 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 1時間無料 料金 ログイン 登録 セッションを開始 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言語 通話に参加しないAI会議アシスタント マイクまたはタブ共有でリアルタイムAI提案を受け取れます。ボットは会議に参加せず、録音も保存されません。 無料で試す ✓ クレジットカード不要 ✓ 登録不要 ✓ 1時間無料 👥 すでにコンサルタント、フリーランサー、プロジェクトマネージャーに使用されています 会議中のAIサポート例 会議のフォローアップ 決定事項：サラが金曜日までにプロトタイプを完成。 新しいアイデア このスプリント後に振り返りを行い、学んだ教訓を整理してはいかがでしょうか？ 用語の説明 言及された「スプリント」は、アジャイル手法における2週間の開発サイクルに相当します。 用語の翻訳 「Stakeholder」（英語）— ステークホルダー、プロジェクトに利害関係を持つ人または団体。 デスクトップ モバイル 集中力を保ち、効果的に貢献するために必要なすべて リアルタイム提案 会話の進行に合わせて文脈に応じた提案を受け取ります。回答のアイデア、重要ポイントのリマインダー、説明が必要なときに表示されます。 インストール不要 ボットなしの会議アシスタント、LiveSuggestにWebブラウザから直接アクセスできます。ダウンロード、拡張機能、複雑な設定は不要です。数秒で開始できます。 プライバシー重視の設計 同意と透明性を核に構築されています。会話は録音なしでリアルタイムで処理され、自動的に削除されます。セッション終了後もデータは保持されません。 よくある質問 ボットなしでどのように機能しますか？ LiveSuggestはデバイスから直接音声をキャプチャします — マイクまたはブラウザタブの音声共有を通じて。ボットが通話に参加したり、参加者リストに表示されることはありません。 録音なしでも同じ精度ですか？ はい。録音ベースのツールと同じ高度なAIモデルを使用しています。音声はリアルタイムで処理され、すぐに破棄されます — 同じ精度、より強力なプライバシー保護。 提案は気が散りませんか？ いいえ。提案は別のウィンドウに表示され、必要に応じて確認できます。会話を中断せず、参加をサポートします。 使い方 1 セッションを開始 ブラウザでLiveSuggestを開き、すべての参加者に通知されていることを確認します。 待機中 2 会議に参加 オンラインまたは対面で会議に参加します。LiveSuggestがリアルタイムで聞き取り、文字起こしします。 文字起こし中… 3 提案を受け取る 会議中ずっと、効果的に貢献するための役立つ文脈に応じた提案を受け取ります。 リアルタイム提案 カスタマイズ可能な4種類の提案 会議のフォローアップ 重要な決定事項、タスク、担当者と期限を含む合意事項を記録し、大切なことを見逃しません。 新しいアイデア 議論を豊かにし、新たな方向性を開くための関連するアイデアや新鮮な視点を提案します。 用語の説明 会話で出てきた専門用語、略語、複雑な概念を即座に解説し、置いていかれることがありません。 用語の翻訳 外国語の表現をその場で翻訳・解説し、言語を問わず会話に参加し続けられます。 ボットは会議に参加しません 📹 Zoom 💼 Teams 🎥 Meet 👥 対面 あらゆるブラウザベースの会議プラットフォームで動作 他のAIツールとは異なり、LiveSuggestは会議に参加者を追加しません。Google Meet、Zoom、Microsoft Teamsなど、あらゆるブラウザベースのプラットフォームでシームレスに動作します。タブの音声を共有するだけです。対面ミーティングではマイクをご利用ください。 プランを選択 ニーズに合ったプランを選択してください 🧾 ビジネス請求書発行可能 Basic 体験向け $ 3 /月 税抜 3 時間の音声 ~6 30分の会議 始める ★ おすすめ Plus 人気No.1 $ 8 /月 税抜 10 時間の音声 ~20 30分の会議 8時間の価格で10時間 Plusを選ぶ Pro パワーユーザー向け $ 20 /月 税抜 30 時間の音声 ~60 30分の会議 20時間の価格で30時間 Proにする プライバシー重視の設計 ✓ 同意と透明性を核に構築されています。会話は録音なしでリアルタイムで処理され、自動的に削除されます。セッション終了後もデータは保持されません。 ✓ 音声はリアルタイムで処理され、保存されません ✓ セッションデータは各セッション終了時に削除されます ✓ プライバシー 何も忘れず、会議でより良く貢献する準備はできていますか？ LiveSuggestを無料でお試しください（クレジットカード不要）。ボットや録音なしでリアルタイムAI提案を受け取れます。集中力を維持し、より効果的に貢献できます。 今すぐ試す — 無料 料金を見る ✓ クレジットカード不要 ✓ 登録不要 ✓ 1時間無料 LiveSuggest ボットなしの会議アシスタントから、話しながらコンテキストに応じた提案を受け取れます — 回答のヒント、要点のリマインド、明確化で、外国語で仕事をしている場合でも、その場で的確に対応できます。 製品 料金 よくある質問 ブログ 法的 プライバシー 規約 法的通知 同意 サポート お問い合わせ バグを報告 © 2026 LiveSuggest. 無断転載を禁じます。 このサイトはCookieを使用しています サイトの適切な機能を確保し、体験を向上させるためにCookieを使用しています。すべてのCookieを承認、拒否、または設定をカスタマイズできます。 すべて承認 すべて拒否 カスタマイズ | 2026-01-13T08:48:04 |
https://livesuggest.ai/contact/ | Contact Us - LiveSuggest LiveSuggest Loading... Contact Us Have a question? A suggestion? Feel free to reach out. Website Name Email Message Send 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://www.postmarkapp.com/?via=036112 | Postmark: Fast, Reliable Email Delivery Service | SMTP | API 🐙 Check out Postmark's new MCP Server! Try it out x Postmark Log In Why Postmark? Product Features Email API SMTP Service Message Streams Transactional Email Email Delivery Email Templates Inbound Email Analytics & Retention Integrations Postmark For Agencies Enterprise Startups Bootstrapped Startups Side Projects Postmark vs. SendGrid Mailgun Amazon SES SparkPost Mandrill Pricing Resources Blog API Documentation Getting Started Email Guides Email Comic Webinars Videos Podcast Labs DMARC Digests Glossary Help Support Center Contact Support Talk to Sales Status Log in Start free trial Why Postmark? Product Features Email API SMTP Service Message Streams Transactional Email Email Delivery Email Templates Inbound Email Analytics & Retention Integrations Postmark For Agencies Enterprise Startups Bootstrapped Startups Side Projects Postmark vs. SendGrid Mailgun Amazon SES SparkPost Mandrill Pricing Resources Blog API Documentation Getting Started Email Guides Email Comic Webinars Videos Podcast Labs DMARC Digests Glossary Help Support Center Contact Support Talk to Sales Status Log in Start free trial Start free trial Already have an account? Log in → I’ve been so impressed with @postmarkapp since migrating almost all Smart Order Notifications transactional email to them last month. The peace of mind is amazing and the responsiveness of their support team is next level. – Kieran Masterton Sendgrid = Frustration Postmark = 💌 – Mike Verbruggen I have nothing but huge love for Postmark, one of my heroes in the bootstrapped world. – Anna Maste Ripped out Sendgrid and moved Growform's transactional emails over to @postmarkapp today. Their app is ridiculously easy to use, they have a clear focus on deliverability and great docs. Highly recommend so far. – Harvey Carpenter I just implemented @postmarkapp in like 5 minutes. Email received in Yahoo in seconds. I am sold. – Lola Spent the weekend shifting @SeshMysteries across from SendGrid to @postmarkapp and couldn't be happier with the experience so far ✨📩 – Dan Foster Been a postmark customer for a veeeerry long time. Stability and deliverability is so good I sometimes go months without thinking about it… just works(tm). – Ben Webster I’ve had great success with @postmarkapp and the API is solid as gold. – Tyson Lawrie Just tried out @postmarkapp and boy is it blazing fast. Transactional emails that previously took 5-10s to reach my inbox with Mailgun are now hitting my inbox in less than 1s. 11/10 would recommend. – Steven Tey I’ve been so impressed with @postmarkapp since migrating almost all Smart Order Notifications transactional email to them last month. The peace of mind is amazing and the responsiveness of their support team is next level. – Kieran Masterton Sendgrid = Frustration Postmark = 💌 – Mike Verbruggen I have nothing but huge love for Postmark, one of my heroes in the bootstrapped world. – Anna Maste Ripped out Sendgrid and moved Growform's transactional emails over to @postmarkapp today. Their app is ridiculously easy to use, they have a clear focus on deliverability and great docs. Highly recommend so far. – Harvey Carpenter I just implemented @postmarkapp in like 5 minutes. Email received in Yahoo in seconds. I am sold. – Lola Spent the weekend shifting @SeshMysteries across from SendGrid to @postmarkapp and couldn't be happier with the experience so far ✨📩 – Dan Foster Been a postmark customer for a veeeerry long time. Stability and deliverability is so good I sometimes go months without thinking about it… just works(tm). – Ben Webster I’ve had great success with @postmarkapp and the API is solid as gold. – Tyson Lawrie Just tried out @postmarkapp and boy is it blazing fast. Transactional emails that previously took 5-10s to reach my inbox with Mailgun are now hitting my inbox in less than 1s. 11/10 would recommend. – Steven Tey The email delivery service that people actually like Stop worrying if your emails made it to the inbox, and get back to focusing on what matters—building great products. Start free trial API documentation → Since 2010, we've delivered billions of emails for companies of all sizes Paddle Indie Hackers Faire.com IKEA litmus desk minecraft livestream UNICEF Asana Moz Code Climate LiveChat 1Password Wistia Betterment Webflow InVision Start sending in minutes With API libraries for pretty much every programming language you can think of, Postmark fits seamlessly into any stack. More # Send an email with curl # Copy and paste this into terminal curl "https://api.postmarkapp.com/email" \ -X POST \ -H "Accept: application/json" \ -H "Content-Type: application/json" \ -H "X-Postmark-Server-Token: server token" \ -d '{ "From": "sender@example.com", "To": "receiver@example.com", "Subject": "Postmark test", "TextBody": "Hello dear Postmark user.", "HtmlBody": "<html><body><strong>Hello</strong> dear Postmark user.</body></html>", "MessageStream": "outbound" }' # Send an email with the Postmark Rails Gem # Learn more -> https://postmarkapp.com/developer/integration/official-libraries#rails-gem # Add this to your gemfile gem 'postmark-rails' # Add this to your config/application.rb file: config.action_mailer.delivery_method = :postmark config.action_mailer.postmark_settings = { :api_token => "POSTMARK_API_TEST" } # Send the email class TestMailer < ActionMailer::Base def hello mail( :subject => 'Hello from Postmark', :to => 'receiver@example.com', :from => 'sender@example.com', :html_body => '<strong>Hello</strong> dear Postmark user.', :track_opens => 'true' ) end end # Send an email with the Postmark Ruby Gem # Learn more -> https://postmarkapp.com/developer/integration/official-libraries#ruby-gem # Add the Postmark Ruby Gem to your Gemfile gem 'postmark' # Require gem require 'postmark' # Create an instance of Postmark::ApiClient client = Postmark::ApiClient.new('POSTMARK_API_TEST') # Example request client.deliver( from: 'sender@example.com', to: 'receiver@example.com', subject: 'Hello from Postmark', html_body: '<strong>Hello</strong> dear Postmark user.', track_opens: true ) // Send an email with the Postmark .NET library // Learn more -> https://postmarkapp.com/developer/integration/official-libraries#dot-net // Install with NuGet PM> Install-Package Postmark // Import using PostmarkDotNet; // Example request PostmarkMessage message = new PostmarkMessage { From = "sender@example.com", To = "receiver@example.com", Subject = "Hello from Postmark", HtmlBody = "<strong>Hello</strong> dear Postmark user.", TextBody = "Hello dear postmark user.", ReplyTo = "reply@example.com", TrackOpens = true, Headers = new NameValueCollection {{ "CUSTOM-HEADER", "value" }} }; PostmarkClient client = new PostmarkClient("POSTMARK_API_TEST"); PostmarkResponse response = client.SendMessage(message); if(response.Status != PostmarkStatus.Success) { Console.WriteLine("Response was: " + response.Message); } // Send an email with the Postmark-PHP library // Learn more -> https://postmarkapp.com/developer/integration/official-libraries#php // Install with composer composer require wildbit/postmark-php // Import use Postmark\PostmarkClient; // Example request $client = new PostmarkClient("server token"); $sendResult = $client->sendEmail( "sender@example.com", "receiver@example.com", "Hello from Postmark!", "This is just a friendly 'hello' from your friends at Postmark." ); // Send an email with the Postmark.js library // Learn more -> https://postmarkapp.com/developer/integration/official-libraries#node-js // Install with npm npm install postmark --save // Require var postmark = require("postmark"); // Example request var client = new postmark.ServerClient("server token"); client.sendEmail({ "From": "sender@example.com", "To": "receiver@example.com", "Subject": "Test", "TextBody": "Hello from Postmark!" }); Switching to Postmark? Check out our handy migration guides I’m switching from I’m switching from… SendGrid Mailgun Amazon SES SparkPost Mailchimp Transactional Stellar deliverability (without paying for a dedicated IP) You might say that Postmark has serious street cred with inbox providers. That's because we vet every new sender carefully, help you follow deliverability best practices, and never, ever let spammers use Postmark. Learn more → Promotional and transactional emails never mix Our API and SMTP service help you send your emails with ease, whether that's password reset emails, notifications, newsletters, or anything in between. To protect the deliverability of your crucial transactional emails—and make sure they arrive lightning fast—we route promotional messages like newsletters through a parallel but separate sending infrastructure. Learn more about Message Streams → 86% Customer Happiness Rating 😃 Great (86%) 🙂 Okay (4%) 😔 Not Good (10%) Customer feedback gathered through Help Scout over the past 60 days. Great support as a standard It's not just our email delivery that's fast and reliable. Our knowledgeable customer success team is here for you should you need us (and we never make you pay extra for premium support.) Paddle Indie Hackers Faire.com IKEA litmus desk minecraft livestream UNICEF Asana Moz Code Climate LiveChat 1Password Wistia Betterment Webflow InVision Since 2010 we've delivered billions of emails for companies of all sizes → Explore our features Email API SMTP Service Message Streams Transactional Email Email Delivery Email Templates Inbound Email Analytics Webhooks Security Email Experts Rebound Ready to get started? Join thousands of businesses that already trust their email delivery to Postmark. Try Postmark free No Credit Card Required Product Pricing Customers Reviews Dedicated IPs Referral Partner Program Latest Updates Features Email API SMTP Service Message Streams Transactional Email Email Delivery Templates Inbound Email Analytics & Retention Integrations Webhooks Security Email Experts Rebound Postmark For Agencies Startups Enterprise Bootstrapped Startups Side Projects Developers Postmark vs. SendGrid SparkPost Mailgun Amazon SES Mandrill Resources Blog API Documentation Getting Started Email Guides Email Comic Videos Podcast DMARC Digests Webinars Labs Migration Guides Newsletter Glossary Help Support Center Contact Support Talk to Sales Service Status Visit ActiveCampaign for: Marketing Automation CRM & Sales Automation Landing Pages SMS Automation Made with ♥ at ActiveCampaign Privacy Policy ↗ Cookie Policy Terms of Service EU Data Protection © ActiveCampaign, LLC , 2026. | 2026-01-13T08:48:04 |
https://github.com/skills/communicate-using-markdown | GitHub - skills/communicate-using-markdown: Organize ideas and collaborate using Markdown, a lightweight language for text formatting. 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 / communicate-using-markdown Public template Notifications You must be signed in to change notification settings Fork 1.8k Star 1.2k Organize ideas and collaborate using Markdown, a lightweight language for text formatting. License MIT license 1.2k stars 1.8k forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 11 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/communicate-using-markdown 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 73 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 Communicate using Markdown Organize ideas and collaborate using Markdown, a lightweight language for text formatting. Welcome GitHub is about more than code. It’s a platform for software collaboration, and Markdown is one of the most important ways developers can make their communication clear and organized in issues and pull requests. This course will walk you through creating and using headings more effectively, organizing thoughts in bulleted lists, and showing how much work you’ve completed with checklists. You can even use Markdown to add some depth to your work with the help of emoji, images, and links. Who is this for : New developers, new GitHub users, and students. What you'll learn : Use Markdown to add lists, images, and links in a comment or text file. What you'll build : We'll update a plain text file and add Markdown formatting, and you can use this file to start your own GitHub Pages site. Prerequisites : In this course you will work with pull requests as well as edit files. If these things aren't familiar to you, we recommend you take the Introduction to GitHub course, first! How long : This course takes less than one hour to complete. In this course, you will: Add headers Add an image Add a code example Make a task list 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 Organize ideas and collaborate using Markdown, a lightweight language for text formatting. Topics github markdown 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 1.2k stars Watchers 59 watching Forks 1.8k forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 14 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://cursor.com/enterprise | Enterprise · Cursor Skip to content Cursor Features Enterprise Pricing Resources ↓ Changelog Blog Docs ↗ Community Learn ↗ Workshops Forum ↗ Careers Features Enterprise Pricing Resources → Sign in Download Enterprise Develop enduring software at scale. Contact sales → Trusted by the world's leading enterprises. Ship better software, faster Cursor helps your entire team deliver ambitious products. I've never, as a CTO, received so many texts or Slack messages from employees just saying "Thank you for getting this technology here." Melody Hildebrandt CTO , Fox 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 Enterprise Order Management System Implement a builder pattern for creating complex orders in our order management system. Make sure it handles validation and supports fluent API Agent GPT-5 Your engineering knowledge base Architected for complex codebases built by thousands of developers. Across roles and levels, we're seeing an increase of over 25% in PR volume and over 100% in the average PR size. Together, that means we're shipping about 50% more code. Anton Andreev Principal Software Engineer , Upwork 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 order-management-system src domain entities Order.h OrderItem.h builders OrderBuilder.h OrderBuilder.cpp infrastructure repositories OrderRepository.h application services OrderService.h tests OrderBuilderTest.cpp CMakeLists.txt OrderBuilder.cpp OrderBuilderTest.cpp OrderBuilder.h #include "OrderBuilder.h" #include <stdexcept> #include <sstream> #include <random> namespace OrderManagement { OrderBuilder& OrderBuilder::forCustomer(std::shared_ptr<Customer> customer) { this->customer = customer; return *this; } OrderBuilder& OrderBuilder::withShippingAddress(const std::string& address) { // TODO: Implement return *this; } OrderBuilder& OrderBuilder::addItem(const std::string& productId, const std::string& productName, int quantity, double unitPrice) { // TODO: Implement return *this; } std::unique_ptr<Order> OrderBuilder::build() { // TODO: Implement return nullptr; } } // namespace OrderManagement Loved by developers In head-to-head evaluations, 93% of engineers select Cursor as their preferred AI coding tool. What used to be a weeks-long ramp-up, navigating complex repos and scheduling handoffs across global teams, is now a structured process built around Cursor from day one. Roni Avidov Senior R&D Team Lead , Monday Interactive demo showing cursor.com/dashboard. cursor.com/dashboard Get Cursor Powerful, yet customizable Standardize your engineering team on the same tools and best practices. Contact sales → Total control Globally configure model access, MCP controls, and system-level agent rules. View enterprise controls ↗ Access the best models Choose between frontier models from OpenAI, Anthropic, Gemini, and xAI. View available models ↗ Auto Suggested Composer 1 GPT-5 High Fast ✓ Claude Sonnet 4.5 Claude Opus 4.5 Gemini 3 Pro Grok Code Ship with confidence Use Cursor to catch real bugs and security issues before they make it into production. Learn more about Bugbot ↗ 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 1 hour ago packages/agent/src/client/connect.ts 65 + const blobStore = new InMemoryBlobStore(); cursor bot 1 hour ago Bug: Global Blob Store Causes Data Leakage The blobStore is declared as a global module-level constant, making it shared across all AgentConnectClient instances. This causes data leakage, as in-memory blob data from one client session or conversation can be accessed by others. Fix in Cursor Fix in Web AI is changing how software is built. 64% Fortune 500 companies using Cursor. 50,000+ Enterprises choose to build with Cursor. 100M+ Lines of enterprise code written per day with Cursor. Trusted by companies worldwide Built with security and compliance at the core. Dedicated guidance Deploy AI at scale with professional expertise. Premium support Tailored support for teams with specialized needs. Zero data retention No training on your data by Cursor or LLM providers. Identity management SAML-based SSO integration for secure user access. SCIM user provisioning Easily create, update, and remove users and groups. Centralized security controls Configure model access, MCPs, and agent rules. Global compliance standards Compliant with the requirements of GDPR and CCPA. Third-party security certifications SOC 2 Type 2 certified and annual penetration testing. Robust data protection AES-256 encryption at rest and TLS 1.2+ in transit. Visit our Trust Center ↗ Read about our security → Modern engineering teams are powered by Cursor. Cursor quickly grew from hundreds to thousands of extremely enthusiastic Stripe employees. We spend more on R&D and software creation than any other undertaking, and there's significant economic outcomes when making that process more efficient and productive. Patrick Collison Co‑Founder & CEO , Stripe My favorite enterprise AI service is Cursor. Every one of our engineers, some 40,000, are now assisted by AI and our productivity has gone up incredibly. Jensen Huang President & CEO , NVIDIA By February 2025, every Coinbase engineer had utilized Cursor, which has become the preferred IDE for most of our developers. Single engineers are now refactoring, upgrading, or building new codebases in days instead of months. Brian Armstrong CEO , Coinbase Cursor has transformed the way our engineering teams write and ship code, with adoption growing from 150 to over 500 engineers (~60% of our org!) in just a few weeks. Albert Strasheim CTO , Rippling Watching a dozen agent branches merge every day has become normal, and that freed-up velocity shows up everywhere from release cadence to bug-backlog burn-down. Cursor isn't a convenience add-on; it's a scale-multiplier for the whole org. Cody De Arkland Senior Director , Sentry At Optiver, we've recently expanded our Cursor usage to firm-wide deployment. Our teams have consistently found Cursor to be robust, context-aware, and flexible enough to support the scale and complexity of a global trading firm. Scott McKenzie Head of Engineering , Optiver Bring Cursor to your team → Latest from Cursor Past, Present, and Future We raised our Series D of $2.3B and have passed $1B in annualized revenue. Nov 13, 2025 The productivity impact of coding agents A new study from the University of Chicago finds that companies merge 39% more PRs after Cursor's agent became the default. Nov 11, 2025 Introducing Cursor 2.0 and Composer A new interface and our first coding model, both purpose-built for working with agents. Oct 29, 2025 View more posts → Questions & Answers How do usage limits work for enterprises? ↓ ↑ How does Cursor handle large-scale codebases and monorepos? ↓ ↑ How does Cursor use my data? ↓ ↑ What security certifications does Cursor have? ↓ ↑ Does Cursor support SSO and SCIM? ↓ ↑ Does Cursor support on-premises or VPC deployment? ↓ ↑ What admin controls are available? ↓ ↑ How can I track AI adoption across my organization? ↓ ↑ Get started with Cursor Enterprise. Contact sales → 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 Enterprise Develop enduring software at scale. Contact sales → Trusted by the world's leading enterprises. Ship better software, faster Cursor helps your entire team deliver ambitious products. I've never, as a CTO, received so many texts or Slack messages from employees just saying "Thank you for getting this technology here." Melody Hildebrandt CTO , Fox 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 Enterprise Order Management System Implement a builder pattern for creating complex orders in our order management system. Make sure it handles validation and supports fluent API Agent GPT-5 Your engineering knowledge base Architected for complex codebases built by thousands of developers. Across roles and levels, we're seeing an increase of over 25% in PR volume and over 100% in the average PR size. Together, that means we're shipping about 50% more code. Anton Andreev Principal Software Engineer , Upwork 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 order-management-system src domain entities Order.h OrderItem.h builders OrderBuilder.h OrderBuilder.cpp infrastructure repositories OrderRepository.h application services OrderService.h tests OrderBuilderTest.cpp CMakeLists.txt OrderBuilder.cpp OrderBuilderTest.cpp OrderBuilder.h #include "OrderBuilder.h" #include <stdexcept> #include <sstream> #include <random> namespace OrderManagement { OrderBuilder& OrderBuilder::forCustomer(std::shared_ptr<Customer> customer) { this->customer = customer; return *this; } OrderBuilder& OrderBuilder::withShippingAddress(const std::string& address) { // TODO: Implement return *this; } OrderBuilder& OrderBuilder::addItem(const std::string& productId, const std::string& productName, int quantity, double unitPrice) { // TODO: Implement return *this; } std::unique_ptr<Order> OrderBuilder::build() { // TODO: Implement return nullptr; } } // namespace OrderManagement Loved by developers In head-to-head evaluations, 93% of engineers select Cursor as their preferred AI coding tool. What used to be a weeks-long ramp-up, navigating complex repos and scheduling handoffs across global teams, is now a structured process built around Cursor from day one. Roni Avidov Senior R&D Team Lead , Monday Interactive demo showing cursor.com/dashboard. cursor.com/dashboard Get Cursor Powerful, yet customizable Standardize your engineering team on the same tools and best practices. Contact sales → Total control Globally configure model access, MCP controls, and system-level agent rules. View enterprise controls ↗ Access the best models Choose between frontier models from OpenAI, Anthropic, Gemini, and xAI. View available models ↗ Auto Suggested Composer 1 GPT-5 High Fast ✓ Claude Sonnet 4.5 Claude Opus 4.5 Gemini 3 Pro Grok Code Ship with confidence Use Cursor to catch real bugs and security issues before they make it into production. Learn more about Bugbot ↗ 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 1 hour ago packages/agent/src/client/connect.ts 65 + const blobStore = new InMemoryBlobStore(); cursor bot 1 hour ago Bug: Global Blob Store Causes Data Leakage The blobStore is declared as a global module-level constant, making it shared across all AgentConnectClient instances. This causes data leakage, as in-memory blob data from one client session or conversation can be accessed by others. Fix in Cursor Fix in Web AI is changing how software is built. 64% Fortune 500 companies using Cursor. 50,000+ Enterprises choose to build with Cursor. 100M+ Lines of enterprise code written per day with Cursor. Trusted by companies worldwide Built with security and compliance at the core. Dedicated guidance Deploy AI at scale with professional expertise. Premium support Tailored support for teams with specialized needs. Zero data retention No training on your data by Cursor or LLM providers. Identity management SAML-based SSO integration for secure user access. SCIM user provisioning Easily create, update, and remove users and groups. Centralized security controls Configure model access, MCPs, and agent rules. Global compliance standards Compliant with the requirements of GDPR and CCPA. Third-party security certifications SOC 2 Type 2 certified and annual penetration testing. Robust data protection AES-256 encryption at rest and TLS 1.2+ in transit. Visit our Trust Center ↗ Read about our security → Modern engineering teams are powered by Cursor. Cursor quickly grew from hundreds to thousands of extremely enthusiastic Stripe employees. We spend more on R&D and software creation than any other undertaking, and there's significant economic outcomes when making that process more efficient and productive. Patrick Collison Co‑Founder & CEO , Stripe My favorite enterprise AI service is Cursor. Every one of our engineers, some 40,000, are now assisted by AI and our productivity has gone up incredibly. Jensen Huang President & CEO , NVIDIA By February 2025, every Coinbase engineer had utilized Cursor, which has become the preferred IDE for most of our developers. Single engineers are now refactoring, upgrading, or building new codebases in days instead of months. Brian Armstrong CEO , Coinbase Cursor has transformed the way our engineering teams write and ship code, with adoption growing from 150 to over 500 engineers (~60% of our org!) in just a few weeks. Albert Strasheim CTO , Rippling Watching a dozen agent branches merge every day has become normal, and that freed-up velocity shows up everywhere from release cadence to bug-backlog burn-down. Cursor isn't a convenience add-on; it's a scale-multiplier for the whole org. Cody De Arkland Senior Director , Sentry At Optiver, we've recently expanded our Cursor usage to firm-wide deployment. Our teams have consistently found Cursor to be robust, context-aware, and flexible enough to support the scale and complexity of a global trading firm. Scott McKenzie Head of Engineering , Optiver Bring Cursor to your team → Latest from Cursor Past, Present, and Future We raised our Series D of $2.3B and have passed $1B in annualized revenue. Nov 13, 2025 The productivity impact of coding agents A new study from the University of Chicago finds that companies merge 39% more PRs after Cursor's agent became the default. Nov 11, 2025 Introducing Cursor 2.0 and Composer A new interface and our first coding model, both purpose-built for working with agents. Oct 29, 2025 View more posts → Questions & Answers How do usage limits work for enterprises? ↓ ↑ How does Cursor handle large-scale codebases and monorepos? ↓ ↑ How does Cursor use my data? ↓ ↑ What security certifications does Cursor have? ↓ ↑ Does Cursor support SSO and SCIM? ↓ ↑ Does Cursor support on-premises or VPC deployment? ↓ ↑ What admin controls are available? ↓ ↑ How can I track AI adoption across my organization? ↓ ↑ Get started with Cursor Enterprise. Contact sales → 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/hello-github-actions | GitHub - skills/hello-github-actions: Create and run a GitHub Actions 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 / hello-github-actions Public template Notifications You must be signed in to change notification settings Fork 1.4k Star 1k Create and run a GitHub Actions workflow. License MIT license 1k stars 1.4k forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 0 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/hello-github-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 66 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 Hello GitHub Actions Create and run a GitHub Actions workflow. Welcome Automation is key for streamlining your work processes, and GitHub Actions is the best way to supercharge your workflow. Who is this for : Developers, DevOps engineers, students, managers, teams, GitHub users. What you'll learn : How to create workflow files, trigger workflows, and find workflow logs. What you'll build : An Actions workflow that will check emoji shortcode references in Markdown files. Prerequisites : In this course you will work with issues and pull requests, as well as edit files. We recommend you take the Introduction to GitHub course first. How long : This course can be finished in less than two hours. In this course, you will: Create a workflow Add a job Add a run step Merge your pull request See effect of 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 Create and run a GitHub Actions workflow. Topics actions workflows github-actions 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 1k stars Watchers 100 watching Forks 1.4k 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://maker.forem.com/t/esp32 | Esp32 - Maker Forem Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account Maker Forem Close # esp32 Follow Hide Create Post Older #esp32 posts 1 2 3 4 5 6 7 8 9 Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu The “No-Flicker” Addressable LED Strip Build (Power + Signal + Gamma) emmma emmma emmma Follow Dec 29 '25 The “No-Flicker” Addressable LED Strip Build (Power + Signal + Gamma) # arduino # esp32 Comments Add Comment 2 min read I plan to develop a wired Android Auto to wireless Android Auto device using the ESP32-S3. Leo Leo Leo Follow Dec 25 '25 I plan to develop a wired Android Auto to wireless Android Auto device using the ESP32-S3. # discuss # esp32 Comments Add Comment 1 min read What an ESP32 Teaches You About Resource Scarcity v. Splicer v. Splicer v. Splicer Follow Dec 23 '25 What an ESP32 Teaches You About Resource Scarcity # esp32 # iot # project # electronics Comments Add Comment 4 min read Made a $10 “Mood Lamp” with ESP32, WS2812B, and Ambient Light Sensor emmma emmma emmma Follow Dec 9 '25 Made a $10 “Mood Lamp” with ESP32, WS2812B, and Ambient Light Sensor # arduino # esp32 # leds # diy Comments 1 comment 1 min read loading... trending guides/resources I plan to develop a wired Android Auto to wireless Android Auto device using the ESP32-S3. What an ESP32 Teaches You About Resource Scarcity The “No-Flicker” Addressable LED Strip Build (Power + Signal + Gamma) Made a $10 “Mood Lamp” with ESP32, WS2812B, and Ambient Light Sensor 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV Maker Forem — A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. Home About Contact Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . Maker Forem © 2016 - 2026. We're a space where makers create, share, and bring ideas to life. Log in Create account | 2026-01-13T08:48:04 |
https://livesuggest.ai/pl/ | Asystent spotkań AI bez bota | LiveSuggest LiveSuggest 1h za darmo Cennik Zaloguj się Zarejestruj się Rozpocznij sesję Polski 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 za darmo Cennik Zaloguj się Zarejestruj się Rozpocznij sesję 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 języków Asystent AI, który nie dołącza do Twoich rozmów Otrzymuj sugestie AI w czasie rzeczywistym przez mikrofon lub udostępnianie karty. Żaden bot nie dołącza do Twojego spotkania, żadne nagranie nie jest zapisywane. Wypróbuj bezpłatnie ✓ Bez karty kredytowej ✓ Bez rejestracji ✓ 1h za darmo 👥 Już używane przez konsultantów, freelancerów i kierowników projektów Przykład pomocy AI podczas spotkań FOLLOW-UP SPOTKANIA Decyzja podjęta: Sara kończy prototyp do piątku. NOWY POMYSŁ A co jeśli zaplanujemy retrospektywę po tym sprincie, żeby zebrać wnioski? WYJAŚNIENIE TERMINU Wspomniany "sprint" odpowiada 2-tygodniowemu cyklowi rozwoju w metodologii Agile. TŁUMACZENIE TERMINU "Stakeholder" (angielski) — interesariusz, osoba lub grupa mająca interes w projekcie. Komputer Urządzenie mobilne Wszystko, czego potrzebujesz, aby pozostać zaangażowanym i skutecznie uczestniczyć Sugestie w czasie rzeczywistym Otrzymuj kontekstowe sugestie w miarę rozwoju rozmowy. Pomysły na odpowiedzi, przypomnienia o kluczowych punktach i wyjaśnienia pojawiają się, gdy najbardziej ich potrzebujesz. Bez instalacji Uzyskaj dostęp do LiveSuggest, asystenta spotkań bez bota, bezpośrednio z przeglądarki internetowej. Bez pobierania, bez rozszerzeń, bez skomplikowanej konfiguracji. Zacznij w kilka sekund. Prywatność przede wszystkim Zbudowane z myślą o zgodzie i przejrzystości. Twoje rozmowy są przetwarzane w czasie rzeczywistym bez nagrywania i automatycznie usuwane. Żadne dane nie są przechowywane po zakończeniu sesji. Często zadawane pytania Jak to działa bez bota? LiveSuggest przechwytuje dźwięk bezpośrednio z Twojego urządzenia — przez mikrofon lub udostępnianie karty przeglądarki. Żaden bot nie dołącza do Twojej rozmowy ani nie pojawia się na liście uczestników. Czy jest równie dokładne bez nagrywania? Tak. Używamy tych samych zaawansowanych modeli AI co narzędzia oparte na nagraniach. Twoje audio jest przetwarzane w czasie rzeczywistym i natychmiast usuwane — ta sama dokładność, silniejsza prywatność. Czy sugestie nie będą mnie rozpraszać? Nie. Sugestie pojawiają się w osobnym oknie, które przeglądasz w razie potrzeby. Wspierają Twój udział bez przerywania rozmowy. Jak to działa 1 Rozpocznij sesję Otwórz LiveSuggest w przeglądarce i potwierdź, że wszyscy uczestnicy są poinformowani. Gotowy do słuchania 2 Dołącz do spotkania Dołącz do spotkania online lub osobiście. LiveSuggest słucha i transkrybuje w czasie rzeczywistym. Transkrypcja w toku… 3 Otrzymuj sugestie Otrzymuj pomocne, kontekstowe sugestie podczas całego spotkania, aby efektywnie wnosić swój wkład. Sugestie w czasie rzeczywistym 4 konfigurowalnych typów sugestii Follow-up spotkania Rejestruje kluczowe decyzje, zadania do wykonania i ustalenia z odpowiedzialnymi i terminami, aby nic ważnego nie umknęło. Nowy pomysł Proponuje trafne pomysły i świeże perspektywy, by wzbogacić dyskusję i otworzyć nowe kierunki. Wyjaśnienie terminu Natychmiast wyjaśnia terminy techniczne, akronimy i złożone pojęcia pojawiające się w rozmowie, abyś nigdy nie czuł się zagubiony. Tłumaczenie terminu Tłumaczy i wyjaśnia obce wyrażenia na bieżąco, pomagając Ci pozostać zaangażowanym niezależnie od języka. Żaden bot nie dołącza do spotkania 📹 Zoom 💼 Teams 🎥 Meet 👥 Osobiście Działa z każdą platformą spotkań dostępną przez przeglądarkę W przeciwieństwie do innych narzędzi AI, LiveSuggest nigdy nie dodaje uczestnika do Twojego spotkania. Działa płynnie z Google Meet, Zoom, Microsoft Teams lub dowolną platformą dostępną przez przeglądarkę — wystarczy udostępnić dźwięk karty. Na spotkaniach osobistych użyj mikrofonu. Wybierz swój plan Wybierz plan, który odpowiada Twoim potrzebom 🧾 Fakturowanie biznesowe dostępne Basic Idealny na początek $ 3 /miesiąc netto 3 godzin audio ~6 spotkań po 30 min Zacznij ★ Polecany Plus Najpopularniejszy $ 8 /miesiąc netto 10 godzin audio ~20 spotkań po 30 min 10h w cenie 8h Wybierz Plus Pro Dla zaawansowanych użytkowników $ 20 /miesiąc netto 30 godzin audio ~60 spotkań po 30 min 30h w cenie 20h Przejdź na Pro Prywatność przede wszystkim ✓ Zbudowane z myślą o zgodzie i przejrzystości. Twoje rozmowy są przetwarzane w czasie rzeczywistym bez nagrywania i automatycznie usuwane. Żadne dane nie są przechowywane po zakończeniu sesji. ✓ Audio przetwarzane w czasie rzeczywistym, nie przechowywane ✓ Dane sesji usuwane na końcu każdej sesji ✓ Prywatność Gotowy, aby niczego nie zapomnieć i lepiej uczestniczyć w spotkaniach? Wypróbuj LiveSuggest za darmo — karta kredytowa nie jest wymagana. Otrzymuj sugestie AI w czasie rzeczywistym bez botów i nagrań. Pozostań skupiony, wnoś lepszy wkład. Wypróbuj teraz — Za darmo Zobacz ceny ✓ Bez karty kredytowej ✓ Bez rejestracji ✓ 1h za darmo LiveSuggest Otrzymuj kontekstowe sugestie od asystenta spotkań bez bota podczas mówienia — pomysły na odpowiedzi, przypomnienia o kluczowych punktach i wyjaśnienia, aby zachować koncentrację w danym momencie, nawet gdy pracujesz w obcym języku. Produkt Cennik FAQ Blog Prawne Prywatność Warunki Informacje prawne Zgoda Wsparcie Kontakt Zgłoś błąd © 2026 LiveSuggest. Wszelkie prawa zastrzeżone. Ta strona używa plików cookie Używamy plików cookie, aby zapewnić prawidłowe działanie strony i poprawić Twoje doświadczenie. Możesz zaakceptować wszystkie pliki cookie, odrzucić je lub dostosować swoje preferencje. Zaakceptuj wszystkie Odrzuć wszystkie Dostosuj | 2026-01-13T08:48:04 |
https://shahadarsh.com/2020/07/12/principles-patterns-and-practices-for-effective-infrastructure-as-code/ | Infrastructure as Code: Principles, Patterns, and Practices | Adarsh Shah Menu Adarsh Shah Home About Me Speaking Writing Book Contribution Hire Me Home Writing Infrastructure as Code: Principles, Patterns, and Practices July 12, 2020 Adarsh Shah Deliver Infrastructure and Software running on it Rapidly and Reliably at Scale Table of Contents Toggle Deliver Infrastructure and Software running on it Rapidly and Reliably at Scale What is Infrastructure as Code? Key Principles Idempotency Immutability Patterns and Practices Everything in Source Control Modularize and Version Documentation Testing Security and Compliance Automate Execution from a Shared Environment Infrastructure as Code Pipeline GitOps Challenges Scaling Infrastructure as Code Conclusion Notes: 1. There is a certain level of Organizational maturity needed to use these Principles, Patterns, and Practices. This article is not focused on the cultural side of things but it is very important for the successful adoption of these. 2. Examples used in this article are using Terraform and AWS but these Principles, Patterns, and Practices are generic and can mostly be applied to other IaC tools like Pulumi , CloudFormation , etc. and Cloud Providers like GCP and Azure or even On-Premise. What is Infrastructure as Code? Infrastructure as Code (IaC) is an approach that takes proven coding techniques used by software systems and extends it to infrastructure. It is one of the key DevOps practices that enable teams to deliver infrastructure, and the software running on it, rapidly and reliably, at scale. If you want to achieve Continuous Delivery for your applications, having a rapid and reliable, provisioning mechanism for your infrastructure is important. In this article, we will go through various Principles, Patterns, and Practices that have helped me, and the organizations I have worked with, over the years. Key Principles Before we start talking about Patterns and Practices lets look at key principles for effective IaC. Idempotency Idempotency means no matter how many times you run your IaC and, what your starting state is, you will end up with the same end state. This simplifies the provisioning of Infrastructure and reduces the chances of inconsistent results. Idempotency can be achieved by using a stateful tool with a declarative language, like Terraform, where you define the desired end state of infrastructure you want, and then it is Terraform’s job to get you to that end state. If it can’t get to the desired state it will fail. In diagram #1 below as you can see that for a Non-Idempotent IaC if you run it twice it will provision 6 VMs instead of desired 3. In the case of Idempotent IaC, it only provisions the 3 VMs even if you run it multiple times thereby making it more reliable and consistent. Diagram #1: Non-Idempotent vs Idempotent IaC Immutability Configuration drift is a huge problem with infrastructure. It occurs when over a period there are changes made to infrastructure that are not recorded, and your various environments drift from each other in ways that are not easily reproducible. This usually happens if you have a mutable infrastructure that lives for a long time. The system is more brittle in general for long-lived infrastructure since issues like a slow memory leak, disk out of space due to log accumulation, etc. might occur over a period. It also means that you won’t be provisioning the infrastructure as frequently as your applications or configuration and as a result won’t be confident in your ability to do so. These issues can be resolved by using immutable infrastructure. Immutable infrastructure means instead of changing an existing infrastructure you replace it with new. By provisioning new infrastructure every time, you are making sure it is reproducible and doesn’t allow for configuration drift over time. Immutable infrastructure also enables scalability when provisioning infrastructure on cloud environments. You can see in diagram #2 below that for mutable infrastructure v2 of application is deployed on the same servers as v1 but for immutable infrastructure, it provisions new VMs with v2 of application. Diagram #2: Mutable vs Immutable Infrastructure Patterns and Practices Everything in Source Control It goes without saying that everything should be in source control . Even a script that you run occasionally to fix an issue, as well as the pipeline used to provision your infrastructure and deploy your software ( pipeline as code ). I have been at places where no one knows where a script that runs in production lives, who created it, and history of changes. This is a situation you don’t want to be in. Make sure the code is accessible to everyone in the company, even for developers that don’t make changes to the IaC code base. An exception might be that you have a very strong reason for not doing it, like a legal reason. This gives visibility and a better understanding to those who run their applications on your infrastructure, so when your consumers want to troubleshoot an issue, and want to understand how the infrastructure was provisioned, they can easily do that by looking at the code. They should be able to look at the code, understand how the infrastructure is provisioned, and even contribute if they choose to do so. I have worked with teams where it is not only the case that IaC repositories are not accessible to the rest of the organization, but they are also stored on separate source control tools that keep them hidden. This is an anti-pattern. Modularize and Version Modularizing IaC like software code helps with maintenance, readability, as well as ownership. It also helps in keeping the changes small and independently deployable. Refactoring IaC is relatively difficult compared to software especially for critical pieces like DNS records, CDN, Network, Databases, etc. so being biased towards over-abstraction up-front works better even though that means dealing with slightly more complex IaC than needed. In many organizations where they have different teams like Networking, Security, and Platform Engineering ¹ it might make sense to separate various layers of your infrastructure and give ownership to appropriate teams to allow better control. I have also separated the layers in cases where it is a cross-functional team managing both software and infrastructure due to the other reasons mentioned above. In diagram #3 below I have shown an example for deployments to Amazon Elastic Kubernetes Service (EKS) with various modules within each infrastructure layer and its ownership. These modules/layers might be different for you based on the setup you have. Diagram #3: Infrastructure Layers Example Versioning for modules is pretty important to make sure you are not breaking things in production unless you are using monorepo in which case you are always using the latest version from the same repo. Documentation With IaC, you should not need extensive documentation since everything is codified, but some documentation is still essential. Better quality documentation not only helps the team that is maintaining IaC but the consumers of the infrastructure as well. Documentation is hard. Just like with code, making sure that you have just enough documentation to convey the message you want is important. More documentation doesn’t mean it’s better. Out of date documentation is even worse. Making the documentation easily available when needed is important. For example, if you display an error message, it’s a good idea to include a link to the documentation to troubleshoot issues like that. Also, having runbook for typical scenarios help troubleshooting during production issues. The documentation should live closer to the code. There are more chances you will keep it updated if it is with the code or closer to it. For example, adding a README in the same repository as IaC instead of some external place like confluence or wiki outside the repository is better. This way there are more chances you will remember to update the documentation in the same commit as the code changes and it can also be a reminder during the Pull Request process. If you can generate documentation from your code or use tests as documentation, that’s ideal. Testing Like in software development, you need to think about testing your IaC at various levels. If you are not aware of the Test Pyramid, here is an article on Martin Fowler’s website. Below is my attempt at a test pyramid for IaC. The idea here is that as you go up the test pyramid, the tests are more costly, more brittle, take longer to run, and require higher maintenance. So for these reasons and to get faster feedback, you should run tests at the bottom of the pyramid as often as possible, and the tests at the top, less frequently. Diagram #4: Test Pyramid for Infrastructure as Code Static Analysis: As this is the quickest way to get the feedback, you should run it as often as possible, even on your machine. There are integrations to do this automatically when you save a file in your text editor or IDE. You can do static analysis using tools like terraform validate or TFLint . Unit Testing: Since most of the tools (like terraform and ansible) are declarative, unit testing is usually not needed for IaC. In some cases, though, unit tests might be helpful like when you have conditionals or loops. If you are writing bash scripts you can do unit testing using bats , or if you are using Pulumi , which supports languages like TypeScript, Python, Go, or C# you can use the language test framework. Integration Testing: This is when you provision your resources in an environment and verify whether you have met certain requirements. Remember not to write tests for things that your tool is responsible for especially if you are writing declarative code. For example, you should be writing automated tests to make sure that none of your s3 buckets are public instead of verifying whether the policies specified in IaC were applied or not. Another example would be to test that only certain ports are open across all of your EC2 instances. You can also provision an Ephemeral ² environment (that you can tear down later) to run these tests. Depending on how long these tests take you might want to run these after every commit or as nightly builds. Tools like Chef InSpec and goss are helpful for these types of tests. Smoke Test with Dummy Application: Last but not the least way of testing is by provisioning an environment, deploying a dummy application, and running quick smoke tests to verify that the application was deployed correctly. Use a dummy application to test scenarios your real application would have but is not configured for production. For example, if your apps connect to a database that’s externally hosted, you should try connecting to it in your dummy application. This gives you confidence that infrastructure that you are provisioning allows you to run applications you intend to run on it. Since these are slow tests you can run these after a new environment is provisioned and then periodically. Security and Compliance Making sure your infrastructure, and the applications running on it, are secure and compliant is an important, but often overlooked aspect. Traditionally, a lot of organizations have manual checks and gates for this that are time-consuming and usually happen at a later stage in the deployment cycle, but with IaC you can automate those to provide better security/compliance and run them more frequently and sooner in the cycle. Here are some of the aspects to consider: Identity and Access Management: Make sure you have a robust Identity and Access Management for your IaC and the infrastructure it provisions. Using Role-Based Access Control (RBAC) for IaC that provisions the infrastructure helps in reducing the overall attack surface. With RBAC you grant just enough permission to your IaC to perform the operation it’s supposed to do. Secrets Management: IaC usually needs secrets to provision any infrastructure. For example, if you are provisioning resources in AWS you will need AWS credentials to connect to it. Make sure you use a reliable secrets management tool like Hashicorp Vault or AWS Secrets Manager . If you need to output or store any secrets in the state file (though you should try to avoid this) make sure they are encrypted so if someone gets hold of the state file they can’t extract the secret out of it. Security Scanning: Running security scans after provisioning or changing infrastructure in a Lower or Ephemeral environment helps in avoiding security issues in Production. Using tools like CIS Benchmark and Amazon Inspector helps with finding common vulnerabilities/exposures and also make sure that security best practices are followed. Compliance: Many companies have compliance requirements, but especially if you work in the Healthcare or Financial domain there are stricter requirements. I’m sure you are aware of some if not all of these: HIPAA, PCI, GDPR, and SOX. As mentioned above traditionally compliance teams used to do all the checks and paperwork manually. Using various tools like Chef Inspec or Hashicorp Sentinel to automate these compliance requirements helps in running it more frequently and finding the issues much faster. For example, you can run these compliance tests every time you change your IaC by provisioning an Ephemeral ² environment so you find out if there are any issues with the new code before going to production. Automate Execution from a Shared Environment All the steps mentioned above should be brought together and IaC executed with appropriate checks in a certain sequence to provision infrastructure with confidence in various environments. For this, I’m going to talk about 2 options below. Infrastructure as Code Pipeline See below an example that demonstrates a typical sequence of steps in an IaC pipeline. I have used CircleCI in the example below but you can use any pipeline tool to execute this. The pipeline provides visibility to everyone who is dependent on the infrastructure that gets provisioned and notifies appropriate teams when there is a failure. Diagram #5: Infrastructure as Code pipeline GitOps Another way of executing IaC is by using GitOps which extends IaC and adds a workflow (Pull Request Process) to apply a change to the Production or any environment for that matter. It could also have a control loop that verifies periodically that the actual state of the infrastructure is the same as the desired state. For example, it will make sure that if any changes were done directly to infrastructure it reverts to the desired state as per the source control. GitOps can be used instead of an IaC pipeline defined above. For more on GitOps, you can read the documentation on the Weaveworks website here . GitOps = IaC + (Workflow + Control Loop) Diagram #6: GitOps Workflow Challenges Scaling Infrastructure as Code Infrastructure as Code (IaC) has made managing infrastructure easier in a lot of ways, but there are many challenges that companies accept as the cost of adopting IaC, especially when scaling. Read the below articles to know about those challenges and how can you resolve them using Environment as Code. Challenges scaling Infrastructure as Code From Infrastructure as Code to Environment as Code Conclusion Thanks for reading the article and hope that you find it useful. If you know of other IaC Principles, Patterns, or Practices that could be added to this article or have any questions let me know in the comments below or reach out to me on twitter and I will look into it. You can also watch the talk I gave at FOSDEM 2021 on the topic below: Acknowledgments: Matt Kuritz, Michael Wytock and Arielle Sullivan read the draft version of this article and provided feedback to improve it. [1]: The Platform Engineering Team mentioned in diagram #3 is responsible for operating a platform that enables delivery teams to self-service deploy and operate systems with reduced lead time and complexity. For more on it, read on article on it here or watch the talk Priyanka Rao and I gave at DevOpsdays Edinburgh here or look at the deck here . [2]: Ephemeral environment means to provision an environment on demand when needed and then destroying it afterward. It is a useful technique to test your IaC and applications running on it without a need to keep it running all the time thereby saving costs. Also published on medium and part of the O’Reilly Media’s book “ 97 Things Every Cloud Engineer Should Know ” Since you are interested in Infrastructure as Code you might like the product my company has built that makes Environment Management Easy across all 3 major cloud providers as well as On-premises. Please watch the below video or go to https://zlifecycle.com/ to know more. Tags: Automation , Best Practices , Cloud Computing , DevOps , Infrastructure As Code , Terraform Vote Up Vote Down Adarsh Shah Adarsh Shah is an Engineering Leader, Coach, Public Speaker, Hands-on Architect & a Change Agent with over 15 years of industry experience. He is also an organizer for Devopsdays NYC conference & devopsnyc meetup. Adarsh has a keen interest in building systems that add business value and is passionate about helping clients with digital transformation by improving both technical as well as non-technical aspects. These days, he is excited about working with Machine Learning and Cloud-Native technologies. Challenges Deploying Machine Learning Models to Production Continuous Delivery for Machine Learning – nycdevops One Comment Swaminathan S June 9, 2021 Good Read about this concept 0 0 Leave a Reply Cancel Reply Save my name, email, and website in this browser for the next time I comment. Post Comment Δ Thanks for visiting my website. My name is Adarsh Shah. I’m a Fractional Engineering Leader, Founder, Advisor and a Polyglot Engineer with over 20 years of industry experience. If you need help, learn more about me . Follow me × Close Search Recent Posts Principles, Patterns, and Practices for Effective Infrastructure as Code – FOSDEM 2021 Platform Engineering: Challenges and Solutions Continuous Delivery for Machine Learning Systems – DevOpsDays Warsaw Platform Engineering: Using it to Gain Competitive Advantage Continuous Delivery for Machine Learning Systems Related Posts Platform Engineering: Challenges and Solutions Continuous Delivery for Machine Learning Systems Continuous Delivery for Machine Learning Systems – All Day DevOps Continuous Delivery for Machine Learning Systems – DevOpsDays Warsaw Continuous Delivery for Machine Learning – nycdevops Deploying Machine Learning Models to Production: Challenges & Solutions using MLOps Platform Engineering: Using it to Gain Competitive Advantage Challenges Deploying Machine Learning Models to Production Integrating Infrastructure as Code into a Continuous Delivery Pipeline – All Day DevOps Archives January 2021 November 2020 October 2020 September 2020 July 2020 June 2020 May 2020 April 2020 November 2019 October 2019 August 2019 June 2019 March 2019 November 2018 June 2018 May 2018 March 2018 November 2017 October 2017 August 2017 Categories Past Speaking Upcoming Writing Meta Log in Entries feed Comments feed WordPress.org Adarsh Shah × Close Search | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb10-9 | 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://livesuggest.ai/fr/ | Assistant IA de réunion sans bot | LiveSuggest LiveSuggest 1h gratuite Tarifs Connexion Inscription Démarrer la session Français 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 gratuite Tarifs Connexion Inscription Démarrer la 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 langues L'assistant IA de réunion qui ne rejoint pas vos appels Recevez des suggestions IA en temps réel via micro ou partage d'onglet. Aucun bot ne rejoint votre appel, aucun enregistrement stocké. Essayer gratuitement ✓ Pas de carte bancaire ✓ Pas d'inscription ✓ 1h gratuite 👥 Déjà utilisé par des consultants, freelances et chefs de projet Exemple d'aide IA pendant les réunions SUIVI DE RÉUNION Décision notée : Sarah finalise le prototype d'ici vendredi. NOUVELLE IDÉE Et si on planifiait une rétrospective après ce sprint pour capitaliser sur les apprentissages ? EXPLICATION DE TERME Le « sprint » mentionné correspond à un cycle de développement de 2 semaines en méthode Agile. TRADUCTION DE TERME « Stakeholder » (anglais) — partie prenante, personne ou groupe ayant un intérêt dans le projet. Ordinateur Mobile Tout ce qu'il vous faut pour rester engagé et contribuer efficacement Suggestions en temps réel Recevez des suggestions contextuelles au fil de la conversation. Idées de réponses, rappels de points clés et clarifications apparaissent au moment où vous en avez besoin. Aucune installation requise Accédez à LiveSuggest — l'assistant de réunion IA sans bot — directement depuis votre navigateur web. Pas de téléchargement, pas d'extension, pas de configuration. Démarrez en quelques secondes. Respect de la vie privée Le consentement et la transparence sont au cœur de notre conception. Vos conversations sont traitées en temps réel sans enregistrement et supprimées automatiquement. Aucune donnée n'est conservée après la fin de votre session. Questions fréquentes Comment ça marche sans bot ? LiveSuggest capture l'audio directement depuis votre appareil — via microphone ou partage d'onglet. Aucun bot ne rejoint votre appel ni n'apparaît dans la liste des participants. C'est aussi précis sans enregistrement ? Oui. Nous utilisons les mêmes modèles IA avancés que les outils basés sur l'enregistrement. Votre audio est traité en temps réel et immédiatement supprimé — même précision, confidentialité renforcée. Les suggestions ne vont pas me distraire ? Non. Les suggestions apparaissent dans une fenêtre séparée que vous consultez quand vous le souhaitez. Elles soutiennent votre participation sans interrompre la conversation. Comment ça marche 1 Démarrez une session Ouvrez LiveSuggest dans votre navigateur et confirmez que tous les participants sont informés. Prêt à écouter 2 Rejoignez votre réunion Rejoignez votre réunion en ligne ou en personne. LiveSuggest écoute et transcrit en temps réel. Transcription en cours… 3 Recevez des suggestions Obtenez des suggestions IA pendant vos réunions — des conseils contextuels pour contribuer efficacement. Suggestions en temps réel 4 types de suggestions personnalisables Suivi de réunion Capture les décisions clés, actions à mener et accords avec responsables et échéances, pour ne rien laisser passer. Nouvelle idée Propose des idées et perspectives nouvelles pour enrichir la discussion et ouvrir de nouvelles pistes. Explication de terme Clarifie instantanément les termes techniques, acronymes et concepts complexes mentionnés dans la conversation, pour ne jamais être perdu. Traduction de terme Traduit et explique les expressions en langue étrangère à la volée — votre assistant de réunion pour non-natifs. Aucun bot dans votre réunion 📹 Zoom 💼 Teams 🎥 Meet 👥 En personne Fonctionne avec toute plateforme de réunion via navigateur Contrairement à d'autres assistants de réunion IA, LiveSuggest ne rejoint pas votre appel comme un bot. Fonctionne avec Google Meet, Zoom, Microsoft Teams ou toute plateforme accessible via navigateur — partagez simplement l'audio de l'onglet. En présentiel, utilisez votre microphone. Choisissez votre plan Choisissez le plan qui correspond à vos besoins 🧾 Facturation professionnelle disponible Basic Pour découvrir $ 3 /mois hors taxes 3 heures d'audio ~6 réunions de 30 min Commencer ★ Recommandé Plus Le plus populaire $ 8 /mois hors taxes 10 heures d'audio ~20 réunions de 30 min 10h pour le prix de 8h Choisir Plus Pro Pour les utilisateurs intensifs $ 20 /mois hors taxes 30 heures d'audio ~60 réunions de 30 min 30h pour le prix de 20h Passer Pro Respect de la vie privée ✓ Le consentement et la transparence sont au cœur de notre conception. Vos conversations sont traitées en temps réel sans enregistrement et supprimées automatiquement. Aucune donnée n'est conservée après la fin de votre session. ✓ Audio traité en temps réel, non stocké ✓ Données de session supprimées à la fin de chaque session ✓ Confidentialité Prêt à ne plus rien oublier et à mieux contribuer en réunion ? Essayez LiveSuggest gratuitement — aucune carte bancaire requise. Recevez des suggestions IA en temps réel, sans bot ni enregistrement. Restez engagé, contribuez mieux. Essayer maintenant — Gratuit Voir les tarifs ✓ Pas de carte bancaire ✓ Pas d'inscription ✓ 1h gratuite LiveSuggest Assistant de réunion IA en temps réel avec suggestions contextuelles et rappels clés pour améliorer vos échanges, même lors de réunions dans une langue étrangère. Produit Tarifs FAQ Blog Légal Confidentialité CGU Mentions légales Consentement Aide Nous contacter Signaler un bug © 2026 LiveSuggest. Tous droits réservés. Ce site utilise des cookies Nous utilisons des cookies pour assurer le bon fonctionnement du site et améliorer votre expérience. Vous pouvez accepter tous les cookies, les refuser ou personnaliser vos préférences. Tout accepter Tout refuser Personnaliser | 2026-01-13T08:48:04 |
https://lab174.com/blog/202601-yaml-norway/#cb1-10 | 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/publish-packages | GitHub - skills/publish-packages: Use GitHub Actions to publish your project to a Docker image. 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 / publish-packages Public template generated from skills/exercise-template Notifications You must be signed in to change notification settings Fork 105 Star 207 Use GitHub Actions to publish your project to a Docker image. License MIT license 207 stars 105 forks Branches Tags Activity Star Notifications You must be signed in to change notification settings Code Issues 3 Pull requests 10 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/publish-packages 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 63 Commits .github .github .gitignore .gitignore LICENSE LICENSE README.md README.md index.html index.html View all files Repository files navigation README Code of conduct Contributing MIT license Security Publish to GitHub Packages Use GitHub Actions to publish your project to a Docker image. Welcome GitHub Actions makes it easier than ever to incorporate continuous delivery (CD) into your repositories. This course will teach you what is needed to test and deliver artifacts that are ready for deployment. Who is this for : Developers, DevOps engineers, full stack developers, cloud engineers. What you'll learn : Continuous delivery, how to save and access build artifacts, package management, how to publish to GitHub Packages. What you'll build : We will build a Docker image that runs a small game. Prerequisites : We recommend you first complete the following courses: Hello, GitHub Actions and Continuous Integration . How long : This course takes less than 30 minutes to complete. In this course, you will: Create a workflow Add a Dockerfile 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 Use GitHub Actions to publish your project to a Docker image. Topics docker deployment workflows github-actions github-packages 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 207 stars Watchers 20 watching Forks 105 forks Report repository Uh oh! There was an error while loading. Please reload this page . Contributors 14 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:04 |
https://lab174.com/blog/202601-yaml-norway/#cb4-9 | 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://www.finalroundai.com/blog/another-word-for-capable-on-resume | Another Word for Capable: Synonym Ideas for a Resume Promotion title Promotion description Button Text Interview Copilot AI Application AI Resume Builder Auto Apply AI Resume Builder Auto Apply AI Mock Interview Pricing Resources Resume Creation Tools Recruiters Hotline Resume Checker Cover Letter Generator Career Guidance Tools AI Career Coach LinkedIn Profile Optimizer LinkedIn Resume Builder Support Guides Blog Articles Resume Creation Tools Recruiters Hotline Resume Checker Cover Letter Generator Career Guidance Tools AI Career Coach LinkedIn Profile Optimizer LinkedIn Resume Builder Support Guides Blog Articles Question bank Sign In Sign Up Interview Copilot AI Application AI Resume Builder Auto Apply AI Mock Interview Pricing Resources Resume Creation Tools Recruiters Hotline Resume Checker Cover Letter Generator Career Guidance Tools AI Career Coach LinkedIn Profile Optimizer LinkedIn Resume Builder Support Guides Blog Articles 🔥 Question Bank Sign In Home > Blog > Job Position Home > Blog > Job Position Another Word for Capable: Synonym Ideas for a Resume Written by Kaivan Dave Edited by Michael Guan Reviewed by Jay Ma Updated on Jun 20, 2025 Read time Comments https://www.finalroundai.com/blog/another-word-for-capable-on-resume Link copied! Using "capable" repeatedly in your resume can weaken your message and make you sound less experienced or original. By varying your language, you can improve ATS results, make your resume clearer, and help you stand out. Should You Use Capable on a Resume? When Capable Works Well Using "capable" in your resume can be effective when it aligns with specific industry keywords or when you need to avoid unnecessary jargon. Its strategic and sparing use can create impact, especially in contexts where precision is key. For example, stating "capable of managing complex projects" can highlight your skills without overcomplicating your language. When Capable Might Weaken Your Impact Overusing "capable," however, might cost you a step on the career ladder. Relying too much on the common word makes your resume generic by failing to showcase the specific nature and depth of your experiences, causing it to blend in with countless others using the same vague descriptor. Synonyms can convey crucial nuances. Thoughtful word choice can reflect the specific actions you took, the depth of your involvement, and the distinct impact you made. Language shapes a clearer, more compelling narrative of your qualifications. Resume Examples Using Capable (Strong vs Weak) Strong Examples Successfully led a team of 10 engineers, demonstrating the ability to manage complex projects and deliver results on time. Proven track record of being capable of developing innovative marketing strategies that increased brand awareness by 30%. Capable of analyzing large datasets to identify trends and provide actionable insights, contributing to a 15% increase in sales. Weak Examples Capable of using Microsoft Office Suite. Responsible for various tasks and capable of completing them. Capable of working in a team environment. 15 Synonyms for Capable Competent Skilled Proficient Adept Qualified Efficient Talented Experienced Accomplished Expert Versatile Resourceful Effective Knowledgeable Masterful Why Replacing Capable Can Strengthen Your Resume Improves Specificity and Clarity: Replacing "capable" with "expert" makes your professional level more evident. For example, "Expert in data analysis" clearly shows your high skill level. Helps You Pass ATS Filters: Using "qualified" aligns better with job descriptions. For instance, "Qualified in project management" matches keywords that ATS systems look for. Shows Nuance and Intent: Choosing "specialist" better reflects your role or responsibility. For example, "Marketing specialist" indicates a focused expertise. Sets You Apart From Generic Resumes: An original synonym like "proficient" catches attention. For instance, "Proficient in software development" stands out more than a generic description. Examples of Replacing Capable with Better Synonyms Competent Original: Capable of leading a team to achieve project goals within deadlines. Improved: Competent in leading a team to achieve project goals within deadlines. Contextual Insight: "Competent" suggests a higher level of proficiency and reliability, making your leadership skills more convincing. Skilled Original: Capable of developing marketing strategies that increase brand awareness. Improved: Skilled in developing marketing strategies that increase brand awareness. Contextual Insight: "Skilled" emphasizes your expertise and hands-on experience, making your contribution to marketing efforts more credible. Proficient Original: Capable of using data analysis tools to drive business decisions. Improved: Proficient in using data analysis tools to drive business decisions. Contextual Insight: "Proficient" indicates a high level of skill and familiarity, enhancing the perception of your technical abilities. Adept Original: Capable of managing multiple projects simultaneously. Improved: Adept at managing multiple projects simultaneously. Contextual Insight: "Adept" conveys agility and ease in handling complex tasks, making your multitasking skills stand out. Qualified Original: Capable of overseeing financial operations to ensure compliance. Improved: Qualified to oversee financial operations to ensure compliance. Contextual Insight: "Qualified" highlights your credentials and suitability for the role, reinforcing your authority in financial management. Efficient Original: Capable of streamlining processes to improve productivity. Improved: Efficient in streamlining processes to improve productivity. Contextual Insight: "Efficient" underscores your ability to optimize and enhance operations, making your impact on productivity more apparent. Talented Original: Capable of designing user-friendly interfaces for web applications. Improved: Talented in designing user-friendly interfaces for web applications. Contextual Insight: "Talented" suggests a natural aptitude and creativity, making your design skills more impressive. Experienced Original: Capable of conducting market research to identify trends. Improved: Experienced in conducting market research to identify trends. Contextual Insight: "Experienced" emphasizes your background and history in the field, making your market research skills more trustworthy. Accomplished Original: Capable of negotiating contracts with vendors to secure favorable terms. Improved: Accomplished in negotiating contracts with vendors to secure favorable terms. Contextual Insight: "Accomplished" highlights your achievements and success, making your negotiation skills more compelling. Expert Original: Capable of implementing cybersecurity measures to protect data. Improved: Expert in implementing cybersecurity measures to protect data. Contextual Insight: "Expert" conveys a high level of mastery and specialization, making your cybersecurity skills more authoritative. Techniques for Replacing Capable Effectively Customize Your Capable Synonym Based on Resume Goals Tailor your choice of synonym to align with your resume's objectives. For instance, if you're highlighting leadership skills, "competent" or "proficient" might be more impactful. This approach ensures that your language is precise and relevant to the role you're targeting. Use Final Round AI to Automatically Include the Right Synonym Final Round AI ’s resume builder optimizes your resume by including the right terms and synonyms to help you better showcase your credentials. This targeted keyword optimization also makes your resume Applicant Tracking Systems (ATS) compliant, to help you get noticed by recruiters more easily and start landing interviews. Create a winning resume in minutes on Final Round AI. Analyze Job Descriptions to Match Industry Language Review job descriptions in your field to identify commonly used terms. Replacing "capable" with industry-specific language can make your resume more appealing to hiring managers. For example, if a job description frequently mentions "skilled," use that term to better align with employer expectations. Use Quantifiable Outcomes to Support Your Words Enhance your resume by pairing synonyms with quantifiable achievements. Instead of saying "capable of improving sales," you could say "proficient in driving a 20% increase in sales." This not only replaces "capable" but also provides concrete evidence of your skills and impact. Frequently Asked Questions Can I Use Capable At All? Using "capable" in your resume isn’t inherently bad and can be appropriate in certain contexts, especially when used sparingly and strategically. The occasional, well-placed use of "capable" can work when paired with results or clarity, emphasizing the importance of variety and impact in your language. How Many Times Is Too Many? Using "capable" more than twice per page can dilute its impact and make your resume seem repetitive. Instead, vary your language with specific alternatives to better highlight your skills and achievements. Will Synonyms Really Make My Resume Better? Yes, synonyms can really make your resume better. Thoughtful word choices improve clarity, make your achievements stand out, and increase your chances with both recruiters and ATS. How Do I Choose the Right Synonym for My Resume? Choose the right synonym by matching it with the job description to highlight relevant skills and ensure clarity and impact. Replacing "capable" with a more specific term can make your resume stand out and better align with what employers are looking for. Create a Hireable Resume Create an ATS-ready resume in minutes with Final Round AI—automatically include the right keywords and synonyms to clearly showcase your accomplishments. Create a job-winning resume Turn Interviews into Offers Answer tough interview questions on the spot—Final Round AI listens live and feeds you targeted talking points that showcase your value without guesswork. Try Interview Copilot Now Upgrade your resume! Create a hireable resume with just one click and stand out to recruiters. Upload Your Resume Now ← Back to all articles Table of Contents Example H2 Example H3 Ace Your Next Interview with Confidence Unlock personalized guidance and perfect your responses with Final Round AI, ensuring you stand out and succeed in every interview. Get Started Free Related articles Another Word for Obtained on Resume Job Position • Ruiying Li Another Word for Obtained on Resume Discover synonyms for "obtained" and learn how to replace it with stronger words in your resume with contextual examples. Another Word for Set Up on Resume Job Position • Ruiying Li Another Word for Set Up on Resume Discover synonyms for "set up" and learn how to replace it with stronger words in your resume with contextual examples. Another Word for Solidified on a Resume Job Position • Jaya Muvania Another Word for Solidified on a Resume Discover synonyms for "solidified" and learn how to replace it with stronger words in various contexts, including resume examples. Interview Questions for Office Clerks (With Answers) Job Position • Kaivan Dave Interview Questions for Office Clerks (With Answers) Prepare for your next tech interview with our guide to the 25 most common Office Clerks questions. Boost your confidence and ace that interview! Civil Engineer Skills for Resume (All Experience Levels) Job Position • Jaya Muvania Civil Engineer Skills for Resume (All Experience Levels) Enhance your resume with essential civil engineering skills for all experience levels. Discover key competencies to boost your career prospects. Interview Questions for Executive Assistant (With Answers) Job Position • Kaivan Dave Interview Questions for Executive Assistant (With Answers) Prepare for your next tech interview with our guide to the 25 most common Executive Assistant questions. Boost your confidence and ace that interview! Read All Articles Your trusted platform to ace any job interviews, craft the perfect resumes, and land your dream jobs. All services are online Products Interview Copilot AI Mock Interview AI Resume Builder Hirevue Phone Interview Speech Analysis College Admission Auto Apply QA Pairs Interview Notes Coding Copilot Resources Tutorials Blog Articles Special Discount Influencer Program Smarter Choice Support FAQ Contact Us Company How Final Round AI works About Careers News PR & Media Referral Program AI Tools AI Career Coach Recruiters Hotline Cover Letter Generator LinkedIn Profile Optimizer LinkedIn Resume Builder Resume Checker © 2025 Final Round AI, 643 Teresita Blvd, San Francisco, CA 94127 Privacy Policy Terms & Conditions Try Mock Interview Now | 2026-01-13T08:48:04 |
https://livesuggest.ai/it/ | Assistente IA per riunioni senza bot | LiveSuggest LiveSuggest 1h gratis Prezzi Accedi Registrati Avvia sessione Italiano 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 gratis Prezzi Accedi Registrati Avvia sessione 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 lingue Assistente IA per riunioni che non entra nelle tue chiamate Ricevi suggerimenti IA in tempo reale tramite microfono o condivisione scheda. Nessun bot entra nella tua riunione, nessuna registrazione salvata. Prova gratuitamente ✓ Nessuna carta di credito ✓ Nessuna iscrizione ✓ 1h gratis 👥 Già utilizzato da consulenti, freelancer e project manager Esempio di aiuto IA durante le riunioni FOLLOW-UP RIUNIONE Decisione presa: Sara finalizza il prototipo entro venerdì. NUOVA IDEA E se pianificassimo una retrospettiva dopo questo sprint per raccogliere le lezioni apprese? SPIEGAZIONE DEL TERMINE Lo "sprint" menzionato corrisponde a un ciclo di sviluppo di 2 settimane nella metodologia Agile. TRADUZIONE DI TERMINE "Stakeholder" (inglese) — parte interessata, persona o gruppo con interesse nel progetto. Computer Dispositivo mobile Tutto ciò di cui hai bisogno per rimanere coinvolto e contribuire efficacemente Suggerimenti in tempo reale Ricevi suggerimenti contestuali mentre la conversazione si svolge. Idee di risposta, promemoria dei punti chiave e chiarimenti appaiono quando ne hai più bisogno. Nessuna installazione richiesta Accedi a LiveSuggest, un assistente per riunioni senza bot, direttamente dal tuo browser web. Nessun download, nessuna estensione, nessuna configurazione complessa. Inizia in pochi secondi. Design orientato alla privacy Costruito con il consenso e la trasparenza al centro. Le tue conversazioni vengono elaborate in tempo reale senza registrazione ed eliminate automaticamente. Nessun dato viene conservato dopo la fine della sessione. Domande frequenti Come funziona senza bot? LiveSuggest cattura l'audio direttamente dal tuo dispositivo — tramite microfono o condivisione scheda del browser. Nessun bot si unisce alla tua chiamata o appare nella lista dei partecipanti. È altrettanto accurato senza registrazione? Sì. Utilizziamo gli stessi modelli IA avanzati degli strumenti basati su registrazione. L'audio viene elaborato in tempo reale e immediatamente scartato — stessa accuratezza, maggiore privacy. I suggerimenti non mi distrarranno? No. I suggerimenti appaiono in una finestra separata che consulti quando vuoi. Supportano la tua partecipazione senza interrompere la conversazione. Come funziona 1 Avvia una sessione Apri LiveSuggest nel tuo browser e conferma che tutti i partecipanti sono informati. Pronto ad ascoltare 2 Unisciti alla tua riunione Unisciti alla tua riunione online o di persona. LiveSuggest ascolta e trascrive in tempo reale. Trascrizione in corso… 3 Ricevi suggerimenti Ricevi suggerimenti utili e contestuali durante tutta la riunione per contribuire efficacemente. Suggerimenti in tempo reale 4 tipi di suggerimenti personalizzabili Follow-up riunione Cattura decisioni chiave, azioni da intraprendere e accordi con responsabili e scadenze, assicurando che nulla di importante sfugga. Nuova idea Suggerisce idee rilevanti e prospettive nuove per arricchire la discussione e aprire nuove direzioni. Spiegazione del termine Chiarisce istantaneamente termini tecnici, acronimi e concetti complessi menzionati nella conversazione, così non ti senti mai perso. Traduzione di termine Traduce e spiega espressioni in lingua straniera al volo, aiutandoti a restare coinvolto indipendentemente dalla lingua. Nessun bot nella tua riunione 📹 Zoom 💼 Teams 🎥 Meet 👥 Di persona Funziona con qualsiasi piattaforma di riunioni tramite browser A differenza di altri strumenti IA, LiveSuggest non aggiunge mai un partecipante alla tua riunione. Funziona perfettamente con Google Meet, Zoom, Microsoft Teams o qualsiasi piattaforma accessibile tramite browser — condividi semplicemente l'audio della scheda. Per riunioni di persona, usa il tuo microfono. Scegli il tuo piano Scegli il piano che si adatta alle tue esigenze 🧾 Fatturazione aziendale disponibile Basic Perfetto per provare $ 3 /mese IVA esclusa 3 ore di audio ~6 riunioni da 30 min Inizia ★ Consigliato Plus Il più popolare $ 8 /mese IVA esclusa 10 ore di audio ~20 riunioni da 30 min 10h al prezzo di 8h Scegli Plus Pro Per utenti avanzati $ 20 /mese IVA esclusa 30 ore di audio ~60 riunioni da 30 min 30h al prezzo di 20h Passa a Pro Design orientato alla privacy ✓ Costruito con il consenso e la trasparenza al centro. Le tue conversazioni vengono elaborate in tempo reale senza registrazione ed eliminate automaticamente. Nessun dato viene conservato dopo la fine della sessione. ✓ Audio elaborato in tempo reale, non memorizzato ✓ Dati della sessione eliminati al termine di ogni sessione ✓ Riservatezza Pronto a non dimenticare più nulla e contribuire meglio alle riunioni? Prova LiveSuggest gratuitamente — nessuna carta di credito richiesta. Ricevi suggerimenti IA in tempo reale senza bot o registrazioni. Rimani concentrato, contribuisci meglio. Prova ora — Gratis Vedi i prezzi ✓ Nessuna carta di credito ✓ Nessuna iscrizione ✓ 1h gratis LiveSuggest Ricevi suggerimenti contestuali da un assistente per riunioni senza bot mentre parli — idee per risposte, promemoria sui punti chiave e chiarimenti per restare reattivo sul momento, anche quando lavori in una lingua straniera. Prodotto Prezzi FAQ Blog Legale Riservatezza Termini Note legali Consenso Supporto Contatto Segnala un bug © 2026 LiveSuggest. Tutti i diritti riservati. Questo sito utilizza cookie Utilizziamo cookie per garantire il corretto funzionamento del sito e migliorare la tua esperienza. Puoi accettare tutti i cookie, rifiutarli o personalizzare le tue preferenze. Accetta tutto Rifiuta tutto Personalizza | 2026-01-13T08:48:04 |
https://dev.to/challenges/brightdata-n8n-2025-08-13#main-content | Real-Time AI Agents powered by n8n and Bright Data - DEV Challenge - 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 Challenges > Real-Time AI Agents powered by n8n and Bright Data CHALLENGE RESULTS 🏆 Winners Announced! 🎊 Congrats to the Winners of the Real-Time AI Agents Challenge powered by n8n and Bright Data! Read Announcement Challenge ends soon! Submit your entry now DAYS : HOURS : MINUTES : SECONDS See prompts Real-Time AI Agents powered by n8n and Bright Data View Entries Please sign in to follow this challenge Give your AI agents the power of real-time web data! Challenge Status: Ended Ended Join our next Challenge We're thrilled to partner with n8n and Bright Data to bring the community a brand new challenge! Running through August 31 , the Real-Time AI Agents Challenge powered by n8n and Bright Data invites you to build AI Agents using cutting-edge tools that are reshaping how AI agents access and process data. ✨ Join us on August 19 at 12pm ET for a special livestream right on the DEV homepage. Our co-founder @peter will be walking through the tools for this challenge with the n8n and Bright Data teams! For anyone that can't make it, we'll make sure to include the video in our resource section below. ✨ Building with n8n's automation platform combined with Bright Data's web data infrastructure truly puts you at the forefront of AI agent development. We have one prompt for this challenge with five chances to win, we hope you give it a try! Key Dates Contest start: August 13, 2025 Submissions due: August 31, 2025 Winners announced: September 11, 2025 Badge Rewards Real-Time AI Agents Challenge Completion Badge Real-Time AI Agents Challenge Winner Badge Find Out More Ask questions and share your ideas on the Real-Time AI Agents powered by n8n and Bright Data Launch Post. View Launch Post Sponsored by n8n n8n is the automation platform built for developers and technical teams. It lets users build useful, multi-step workflows using AI and 1000+ integrations—from Slack to Postgres to OpenAI. Whether self-hosted or in the cloud, n8n gives full control over data and logic while blending low-code ease with full-code power. With 120k+ GitHub stars and a vibrant global community, n8n is the trusted path for bringing AI agents and internal automations into production. Learn More → Sponsored by Bright Data Bright Data is the global leader in limitless web data infrastructure for AI & BI. Their platform enables users to discover, access, extract, and interact with any public website delivering structured, reliable, real-time or historical data at petabyte scale. Whether you're building a single agent or a full-scale AI pipeline, Bright Data ensures your models, workflows, and business intelligence systems are powered by the freshest, most flexible data available. Learn More → Challenge Prompt Unstoppable Workflow Build an unstoppable workflow with n8n that leverages Bright Data's n8n Verified Node to create something truly useful, complex, and creative. Your agent should demonstrate how adding real-time web data helps enhance what AI can accomplish. How to Submit In order to participate, you will need to publish a post using the submission template below. All projects must: Use n8n's AI Agent node with Bright Data's verified node Be publicly accessible via n8n's chat interface or another interaction layer, OR include a screen capture/demo video Include your n8n workflow JSON in a GitHub Gist or similar format (JSON file in the associated repo) Bright Data Credits Participants will receive $250 in credits upon signing up through our dedicated sign up link . If you're not seeing the credits in your account, try adding devto as a promo code. If additional credits are required, participants can email noah@brightdata.com with the subject line "DEV Challenge - Credit Required," including the email they used to sign up and details about their use case. Important Note: Use of Data Provided by Bright Data If you receive data from Bright Data as part of this challenge, it is solely for use in your project submission. This data is not intended for reuse, resale, or redistribution at any point. Data provided for the competition will be accessed through an account created by Bright Data and credited using a dev.to promotion code. The promotion code will provide the necessary credits to complete your project as part of the challenge. Misuse of the data or credits may result in disqualification from the competition and/or revocation of access. Submission Template Judging Criteria: Utilization of Underlying Technology Accessibility and User Experience Business Value and Use Case Creativity and Usability Writing Quality (Clarity and Originality) Helpful Links & Resources Get to know n8n and Bright Data by utilizing their docs and tutorials: Get n8n : Start fast with a 14-day trial on cloud or with the free self-hosted community edition n8n Quick Start Tutorial : Getting Started with n8n Bright Data Developer Docs Bright Data Blog Bright Data Use Cases Additional Videos: AI Agents Challenge with n8n and Bright Data Building with n8n and Bright Data (Live DEMO with DEV) Connect: Follow @n8n_io on X Frequently Asked Questions Participation Can I submit to a prompt more than once? Yes, you can submit multiple submissions per prompt but you'll need to publish a separate post for each submission. Can I work on a team? Yes, you can work on teams of up to four people. If you collaborate with anyone, you'll need to list their DEV handles in your submission post so we can award a badge to your entire team! Please only publish one submission per team. DEV does not handle prize-splitting, so in the event that your submission wins the shop gift, you will need to split that amongst yourselves. Thank you for understanding! How old do I have to be to participate? Participants need to be 18+ in order to participate. If I live in X, am I eligible to participate? For eligibility rules, see our official challenge rules . Submission Can I update my submission after the submission due date? No, please do not update your submission during the judging period. Can my submission include open source code? Riffing on open source code and borrowing and improving on previous work/ideas is encouraged but it's important your changes are significant enough to ensure your submission is valid. When does riffing become plagiarism? It will depend, but transparency is important, license compatibility is important. You can use someone else's code to give you a jumpstart to demonstrate your ideas on top of someone else's base, but not just re-package the base. It should be clear to the judges what you added to the project in terms of the code and conceptual inspiration. This means, you should clearly state what you were building on and what elements are original to this new submission. When building on existing code, we expect a significant change that adds something tangible to the output. i.e. a new animation, and new sprite, a new function, a new presentation. Not just changes to the source - i.e. changing colours, changing one sprite, changing one function. What happens if my submission is considered plagiarized or invalid? Anything deemed to be plagiarism will not be eligible for prizes. Incidental plagiarism may simply result in your disqualification from the challenge (regardless of the number of other valid submissions you have published). Egregious plagiarism will result in your suspension from DEV entirely. Any non-generic, non-trivial usage of prior work, including open source code must be credited in your submission. Do submissions have to be in English? Non-english submissions are eligible for a completion badge but not eligible for prizes due to the current limitations of our judges. We will not be judging on mastery of the English language, so please don't let this deter you from submitting if you are not a native English speaker! We hope to evolve this in the future to be more accommodating. Do I need a license for my code? You are not required to license your code but we strongly recommend that you do. Here are some you may consider: MIT , Apache , BSD-2 , BSD-3 , or Commons Clause . Can I use AI? Use of AI is allowed as long as all other rules are followed. We want to give you a chance to show off your skills in realistic scenarios. If you use AI tools to help you achieve your submission, all the power to you. How do I embed my project directly into my DEV post? Our editor supports many types of embeds, including: Stackbliz, Glitch, Github, etc. You can typically use the {% embed https://... %} syntax directly in the post. Click here for more information on our markdown support. For CodePen, you will need to use this syntax: {% codepen http://... %} For CodeSandbox, you will need to use this syntax: {% codesandbox http://... %} Judging and Prizing Can there be ties? In the event of a tie in scoring between judges, the judges will select the entry that received the highest number of positive reactions on their DEV post to determine the winner. How will I know if I won? Winners will be announced in a DEV post on the winner announcement date noted in our key dates section. When will I receive my DEV badge? Both participation and winner badges will be awarded, in most cases, the same day as the winner announcement. When will I receive my prizes? The DEV Team will contact you via the email associated with your DEV profile within, at most, 10 business days of the announcement date to share the details of claiming your prizes. What steps do I need to take to receive my cash prize? The winner (including each member of a team) may be required to sign and return an affidavit of eligibility and publicity/liability release, and provide any additional tax filing information (such as a W-9, social security number or Federal tax ID number) within seven (7) business days following the date of your first email notification. Real-Time AI Agents powered by n8n and Bright Data Rules NO PURCHASE NECESSARY. Open only to 18+. Contest entry period ends August 31, 2025 at 11:59 PM PDT. Contest is void where prohibited or restricted by law or regulation. All entires must be submitted during the content period. For Official Rules, see n8n and Bright Data Real-Time AI Agents Challenge Contest Rules and General Contest Official Rules . Dismiss 💎 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://popcorn.forem.com/t/marketing | Marketing - 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 # marketing Follow Hide Marketing campaigns and trailers Create Post Posts Left menu 👋 Sign in for the ability to sort posts by relevant , latest , or top . Right menu CinemaSins: Everything Wrong With Mission: Impossible - The Final Reckoning In 27 Minutes Or Less Movie News Movie News Movie News Follow Nov 28 '25 CinemaSins: Everything Wrong With Mission: Impossible - The Final Reckoning In 27 Minutes Or Less # movies # reviews # action # marketing Comments Add Comment 1 min read Ringer Movies: ‘Snake Eyes’ With Bill Simmons, Sean Fennessey, and Van Lathan | Ringer Movies Movie News Movie News Movie News Follow Nov 17 '25 Ringer Movies: ‘Snake Eyes’ With Bill Simmons, Sean Fennessey, and Van Lathan | Ringer Movies # movies # marketing # recommendations Comments Add Comment 1 min read CinemaSins: Everything Wrong With Thunderbolts* (The New Avengers) In 20 Minutes Or Less Movie News Movie News Movie News Follow Nov 14 '25 CinemaSins: Everything Wrong With Thunderbolts* (The New Avengers) In 20 Minutes Or Less # movies # reviews # marketing Comments Add Comment 1 min read IGN: Baahubali: The Epic - Official Trailer #2 (2025) Gaming News Gaming News Gaming News Follow Oct 18 '25 IGN: Baahubali: The Epic - Official Trailer #2 (2025) # adventure # action # marketing # movies Comments Add Comment 1 min read CinemaSins: Everything Wrong With Grown Ups In 18 Minutes Or Less Movie News Movie News Movie News Follow Oct 5 '25 CinemaSins: Everything Wrong With Grown Ups In 18 Minutes Or Less # movies # streaming # reviews # marketing Comments Add Comment 1 min read CinemaSins: Everything Wrong With Longlegs In 24 Minutes Or Less Movie News Movie News Movie News Follow Nov 5 '25 CinemaSins: Everything Wrong With Longlegs In 24 Minutes Or Less # movies # reviews # streaming # marketing Comments 1 comment 1 min read CinemaSins: Everything Wrong With The Strangers: Chapter 1 In 15 Minutes Or Less Movie News Movie News Movie News Follow Sep 23 '25 CinemaSins: Everything Wrong With The Strangers: Chapter 1 In 15 Minutes Or Less # movies # reviews # streaming # marketing Comments Add Comment 1 min read CinemaSins: Everything Wrong With Pee-wee's Big Adventure In 18 Minutes Or Less Movie News Movie News Movie News Follow Sep 16 '25 CinemaSins: Everything Wrong With Pee-wee's Big Adventure In 18 Minutes Or Less # movies # reviews # streaming # marketing Comments Add Comment 1 min read Mid-October 2025 Movie and TV Roundup: Releases, Trailers, and Buzz Om Shree Om Shree Om Shree Follow Oct 12 '25 Mid-October 2025 Movie and TV Roundup: Releases, Trailers, and Buzz # streaming # marketing # recommendations # movies 20 reactions Comments Add Comment 4 min read IGN: SHELL - Official Trailer (2025) Elisabeth Moss, Kate Hudson Gaming News Gaming News Gaming News Follow Oct 5 '25 IGN: SHELL - Official Trailer (2025) Elisabeth Moss, Kate Hudson # marketing # movies # thriller # horror Comments Add Comment 1 min read IGN: SHELL - Official Trailer (2025) Elisabeth Moss, Kate Hudson Gaming News Gaming News Gaming News Follow Oct 6 '25 IGN: SHELL - Official Trailer (2025) Elisabeth Moss, Kate Hudson # marketing # movies # thriller # horror Comments Add Comment 1 min read Ringer Movies: How To Save Movies With the CEO of AMC Theaters | The Town Movie News Movie News Movie News Follow Sep 1 '25 Ringer Movies: How To Save Movies With the CEO of AMC Theaters | The Town # movies # streaming # netflix # marketing Comments Add Comment 1 min read IGN: The Carpenter's Son - Official Trailer (2025) Nicolas Cage, FKA twigs Gaming News Gaming News Gaming News Follow Oct 2 '25 IGN: The Carpenter's Son - Official Trailer (2025) Nicolas Cage, FKA twigs # marketing # movies # thriller # horror Comments Add Comment 1 min read IGN: Psycho Killer - Official Trailer (2026) Georgina Campbell, Malcolm McDowell Gaming News Gaming News Gaming News Follow Oct 2 '25 IGN: Psycho Killer - Official Trailer (2026) Georgina Campbell, Malcolm McDowell # marketing # movies # thriller # horror Comments Add Comment 1 min read IGN: Good Fortune - Official ‘Gabe’s First Meal’ Clip (2025) Keanu Reeves, Aziz Ansari, Seth Rogen Gaming News Gaming News Gaming News Follow Oct 1 '25 IGN: Good Fortune - Official ‘Gabe’s First Meal’ Clip (2025) Keanu Reeves, Aziz Ansari, Seth Rogen # marketing # movies # fantasy # starpower Comments Add Comment 1 min read IGN: Good Fortune - Official 'Solved Problems' Clip (2025) Keanu Reeves, Aziz Ansari, Seth Rogen Gaming News Gaming News Gaming News Follow Oct 1 '25 IGN: Good Fortune - Official 'Solved Problems' Clip (2025) Keanu Reeves, Aziz Ansari, Seth Rogen # marketing # movies # starpower Comments Add Comment 1 min read CinemaSins: Everything Wrong With Dumb and Dumber In 18 Minutes Or Less Movie News Movie News Movie News Follow Sep 30 '25 CinemaSins: Everything Wrong With Dumb and Dumber In 18 Minutes Or Less # movies # reviews # marketing # streaming Comments Add Comment 1 min read Mr Sunday Movies: ANAKIN vs. OBI WAN Star Wars: Revenge of the Sith - 16 Bit Scenes Movie News Movie News Movie News Follow Aug 24 '25 Mr Sunday Movies: ANAKIN vs. OBI WAN Star Wars: Revenge of the Sith - 16 Bit Scenes # marketing # animation # action # movies Comments Add Comment 1 min read 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 CinemaSins: Everything Wrong With The Nutty Professor In 17 Minutes Or Less Movie News Movie News Movie News Follow Aug 14 '25 CinemaSins: Everything Wrong With The Nutty Professor In 17 Minutes Or Less # movies # reviews # streaming # marketing Comments Add Comment 1 min read CinemaSins: Everything Wrong With American Wedding Movie News Movie News Movie News Follow Aug 14 '25 CinemaSins: Everything Wrong With American Wedding # movies # reviews # streaming # marketing Comments Add Comment 1 min read Ramy Youssef Exits Will Ferrell's Netflix Golf Comedy Over Creative Differences; Molly Shannon Joins Cast TV News TV News TV News Follow Aug 12 '25 Ramy Youssef Exits Will Ferrell's Netflix Golf Comedy Over Creative Differences; Molly Shannon Joins Cast # marketing # offtopic # filmindustry # studios Comments Add Comment 1 min read Lionsgate Posts $10.6 Million Quarterly Loss After ‘Ballerina' Disappoints Movie News Movie News Movie News Follow Aug 8 '25 Lionsgate Posts $10.6 Million Quarterly Loss After ‘Ballerina' Disappoints # marketing # accessibilitymedia # agencies # offtopic Comments Add Comment 1 min read ‘Star Wars: A New Hope' Will Get 50th Anniversary Theatrical Re-Release on April 30, 2027 Movie News Movie News Movie News Follow Aug 8 '25 ‘Star Wars: A New Hope' Will Get 50th Anniversary Theatrical Re-Release on April 30, 2027 # marketing # analysis # distribution # filmindustry Comments Add Comment 1 min read Margot Robbie Eyed to Star in Tim Burton's ‘Attack of the Fifty Foot Woman' With LuckyChap in Talks to Produce Movie News Movie News Movie News Follow Aug 8 '25 Margot Robbie Eyed to Star in Tim Burton's ‘Attack of the Fifty Foot Woman' With LuckyChap in Talks to Produce # offtopic # marketing # analysis # filmindustry 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:04 |
https://livesuggest.ai/zh-CN/ | 无机器人AI会议助手 | 实时建议 - LiveSuggest LiveSuggest 1小时免费 定价 登录 注册 开始会话 中文 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 1小时免费 定价 登录 注册 开始会话 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种语言 不加入您通话的AI会议助手 通过麦克风或标签页共享获取实时AI建议。没有机器人加入您的会议，没有录音被存储。 免费试用 ✓ 无需信用卡 ✓ 无需注册 ✓ 1小时免费 👥 已被顾问、自由职业者和项目经理使用 会议中AI帮助示例 会议跟进 决定事项：Sarah 周五前完成原型。 新想法 这个冲刺结束后安排一次复盘会议，总结经验教训怎么样？ 术语解释 提到的「Sprint」（冲刺）对应敏捷方法论中的2周开发周期。 术语翻译 "Stakeholder"（英语）— 利益相关者，对项目有利益关系的个人或团体。 桌面 移动 保持专注并有效贡献所需的一切 实时建议 随着对话的进行获取上下文建议。回复思路、关键点提醒和澄清会在您最需要时出现。 无需安装 直接从网页浏览器访问 LiveSuggest，一个无机器人的会议助手。无需下载、无需扩展程序、无需复杂设置。几秒钟即可开始。 隐私优先设计 以同意和透明为核心构建。您的对话会实时处理，无录音，并自动删除。会话结束后不会保留任何数据。 常见问题 没有机器人如何工作？ LiveSuggest直接从您的设备捕获音频 — 通过麦克风或浏览器标签页音频共享。没有机器人会加入您的通话或出现在参与者列表中。 没有录音也一样准确吗？ 是的。我们使用与录音工具相同的高级AI模型。您的音频实时处理并立即丢弃 — 同样的准确度，更强的隐私保护。 建议不会分散我的注意力吗？ 不会。建议显示在您需要时查看的单独窗口中。它们支持您的参与而不会打断对话。 工作原理 1 开始会话 在浏览器中打开 LiveSuggest 并确认所有参与者已知情。 准备好收听 2 加入会议 在线或面对面加入会议。LiveSuggest 实时收听和转录。 正在转录… 3 获取建议 在整个会议期间获取有用的上下文建议，有效参与。 实时建议 4种可定制的建议类型 会议跟进 记录关键决策、待办事项以及包含负责人和截止日期的协议，确保重要内容不会遗漏。 新想法 提供相关的创意和新颖的视角，丰富讨论内容并开辟新方向。 术语解释 即时解释对话中出现的技术术语、缩写和复杂概念，让您始终跟上节奏。 术语翻译 即时翻译和解释外语表达，帮助您无论使用何种语言都能保持参与。 无机器人加入您的会议 📹 Zoom 💼 Teams 🎥 Meet 👥 面对面 适用于任何基于浏览器的会议平台 与其他 AI 工具不同，LiveSuggest 永远不会向您的会议添加参与者。与 Google Meet、Zoom、Microsoft Teams 或任何基于浏览器的平台无缝配合 — 只需共享标签页音频。面对面会议时，请使用麦克风。 选择您的方案 选择适合您需求的方案 🧾 可开具企业发票 Basic 适合体验 $ 3 /月 不含税 3 小时音频时长 ~6 场（每场30分钟）会议 开始使用 ★ 推荐 Plus 最受欢迎 $ 8 /月 不含税 10 小时音频时长 ~20 场（每场30分钟）会议 8小时的价格享10小时 选择 Plus Pro 适合高级用户 $ 20 /月 不含税 30 小时音频时长 ~60 场（每场30分钟）会议 20小时的价格享30小时 升级 Pro 隐私优先设计 ✓ 以同意和透明为核心构建。您的对话会实时处理，无录音，并自动删除。会话结束后不会保留任何数据。 ✓ 音频实时处理，不存储 ✓ 会话数据在每个会话结束时删除 ✓ 隐私 准备好不再遗漏任何内容并在会议中更好地贡献了吗？ 免费试用 LiveSuggest — 无需信用卡。无需机器人或录音，即可获得实时AI建议。保持专注，更好地贡献。 立即试用 — 免费 查看价格 ✓ 无需信用卡 ✓ 无需注册 ✓ 1小时免费 LiveSuggest 从无机器人会议助手获得上下文建议，在您说话时 — 回答思路、关键点提醒和澄清，帮助您在当下保持敏锐，即使是用外语工作。 产品 定价 常见问题 博客 法律 隐私 条款 法律声明 同意 支持 联系 报告错误 © 2026 LiveSuggest. 保留所有权利。 本网站使用 Cookie 我们使用 Cookie 来确保网站正常运行并改善您的体验。您可以接受所有 Cookie、拒绝它们或自定义您的偏好。 全部接受 全部拒绝 自定义 | 2026-01-13T08:48:04 |
https://www.finalroundai.com/blog/it-resume-objective-examples-to-pass-ats-checker | 30+ IT Resume Objective Examples to Pass ATS Checker Promotion title Promotion description Button Text Interview Copilot AI Application AI Resume Builder Auto Apply AI Resume Builder Auto Apply AI Mock Interview Pricing Resources Resume Creation Tools Recruiters Hotline Resume Checker Cover Letter Generator Career Guidance Tools AI Career Coach LinkedIn Profile Optimizer LinkedIn Resume Builder Support Guides Blog Articles Resume Creation Tools Recruiters Hotline Resume Checker Cover Letter Generator Career Guidance Tools AI Career Coach LinkedIn Profile Optimizer LinkedIn Resume Builder Support Guides Blog Articles Question bank Sign In Sign Up Interview Copilot AI Application AI Resume Builder Auto Apply AI Mock Interview Pricing Resources Resume Creation Tools Recruiters Hotline Resume Checker Cover Letter Generator Career Guidance Tools AI Career Coach LinkedIn Profile Optimizer LinkedIn Resume Builder Support Guides Blog Articles 🔥 Question Bank Sign In Home > Blog > Careers Home > Blog > Careers 30+ IT Resume Objective Examples to Pass ATS Checker Boost your chances of landing your dream IT job. Discover 30+ IT resume objective examples expertly crafted to pass Applicant Tracking Systems (ATS) and impress hiring managers. Written by Jaya Muvania Edited by Kaustubh Saini Reviewed by Kaivan Dave Updated on Sep 12, 2025 Read time 10 min read Comments https://www.finalroundai.com/blog/it-resume-objective-examples-to-pass-ats-checker Link copied! Let's address the elephant in the room: most recruiters will tell you resume objectives are outdated. They're not wrong, but they're not entirely right either. Here's the reality: if you're changing careers, just graduated, or targeting a specific role where you need to immediately clarify your intent, a well-crafted objective can still serve you well. The key is making it count in those precious 2-3 lines while ensuring it passes through ATS filters. When You Actually Need an IT Resume Objective Before diving into examples, understand that you should only include an objective if you're: Transitioning into IT from another field A recent graduate with limited experience Targeting a very specific role or company Changing your IT specialization significantly If you have 3+ years of relevant experience, skip the objective and go straight to a professional summary instead. When You Actually Need an IT Resume Objective The Formula That Works The best IT objectives follow this pattern: Your current level + key technical skill The specific role you want One quantifiable achievement or unique value How you'll contribute to their success Now let's look at objectives that actually work, organized by situation. For Recent Graduates Entry-Level IT Support Resume Objective Examples "Computer Science graduate with hands-on experience in Windows/Linux environments and ticketing systems seeking IT Support Specialist role. Completed 200+ hours of lab work troubleshooting hardware and network issues. Ready to leverage technical knowledge and customer service skills to maintain 95%+ ticket resolution rates." Why this works: Specific technical skills, quantifiable experience, realistic goal. Junior Developer Resume Objective Examples "Recent bootcamp graduate proficient in JavaScript, React, and Node.js seeking Junior Developer position. Built 5 full-stack applications including an e-commerce platform handling 1000+ concurrent users. Eager to contribute clean, tested code to your development team." Why this works: Mentions specific technologies ATS will catch, shows practical experience. Entry-Level Network Administrator Resume Objective Examples "Information Technology graduate with CCNA certification seeking Network Administrator role. Configured and maintained 15-node test network achieving 99.9% uptime during internship. Ready to apply routing, switching, and security knowledge to support enterprise infrastructure." Why this works: Certification mentioned upfront, specific metrics, relevant keywords. For Career Changers From Customer Service to IT "Customer service professional with CompTIA A+ certification transitioning to IT Support. Five years solving complex customer issues with 94% satisfaction rate. Combining technical skills with proven communication abilities to deliver exceptional IT support." Why this works: Acknowledges transition, highlights transferable skills, shows commitment through certification. From Teaching to IT Training "Former educator with 8 years classroom experience pursuing Technical Trainer role. Developed curriculum for 500+ students while earning AWS Solutions Architect certification. Ready to design and deliver technical training programs that improve team capabilities by 30%+." Why this works: Connects past experience to new role, shows relevant upskilling. From Military to Cybersecurity "Military communications specialist with Security+ certification seeking Cybersecurity Analyst position. Managed classified networks for 200+ users with zero security incidents over 4 years. Bringing disciplined approach to threat detection and incident response." Why this works: Translates military experience, emphasizes security mindset. For Experienced Professionals Changing Focus Developer to DevOps "Full-stack developer with 5 years experience transitioning to DevOps Engineer role. Implemented CI/CD pipelines reducing deployment time by 60%. Skilled in Docker, Kubernetes, and Jenkins, ready to bridge development and operations." Why this works: Clear transition, relevant achievements, key DevOps technologies. IT Support to Cloud Engineering "IT Support Specialist with Azure certifications pursuing Cloud Engineer position. Migrated 50+ on-premise applications to cloud during current role. Combining infrastructure knowledge with cloud expertise to optimize your Azure environment." Why this works: Shows progression, relevant project experience, specific platform focus. Database Admin to Data Engineering "Database Administrator with 7 years SQL experience seeking Data Engineer role. Built ETL pipelines processing 10TB+ daily while learning Python and Spark. Ready to architect scalable data solutions for analytics teams." Why this works: Leverages existing skills, shows learning initiative, quantifies scale. For Specific Situations and Specialized Roles Machine Learning Engineer Resume Objective Examples "Software Engineer with 3 years Python experience seeking Machine Learning Engineer role. Built recommendation system improving user engagement 35% using TensorFlow and scikit-learn. Ready to develop and deploy ML models at scale." Why this works: Specific ML tools, business impact, production focus. Data Scientist Resume Objective Examples "Statistician with PhD in Mathematics pursuing Data Scientist position. Published 5 papers on predictive modeling while developing Python and R expertise. Ready to apply advanced analytics to solve complex business problems." Why this works: Strong academic background, publications, business application. Blockchain Developer Resume Objective Examples "Full Stack Developer with 2 years Solidity experience seeking Blockchain Developer role. Deployed 10+ smart contracts handling $1M+ in transactions. Expert in Web3, Ethereum, and DeFi protocols." Why this works: Specific blockchain technologies, financial scale, relevant expertise. Site Reliability Engineer (SRE) Resume Objective Examples "DevOps Engineer with 4 years experience pursuing SRE role. Achieved 99.99% uptime for services handling 10M daily requests. Expert in monitoring, incident response, and chaos engineering." Why this works: Reliability metrics, scale, SRE-specific practices. Security Engineer Resume Objective Examples "Network Engineer with CISSP certification seeking Security Engineer position. Implemented zero-trust architecture reducing security incidents by 80%. Ready to design and maintain enterprise security infrastructure." Why this works: Advanced certification, security architecture, measurable improvement. Solutions Architect Resume Objective Examples "Senior Developer with 8 years experience seeking Solutions Architect role. Designed systems processing 1B+ events daily for Fortune 500 clients. Expert in cloud platforms, microservices, and enterprise integration." Why this works: Client-facing experience, massive scale, architectural expertise. Technical Project Manager Resume Objective Examples "Software Developer with PMP certification transitioning to Technical Project Manager. Led cross-functional team delivering $2M project on time and under budget. Combining technical depth with project management expertise." Why this works: Relevant certification, financial scope, dual expertise. Business Intelligence Developer Resume Objective Examples "Data Analyst with 3 years Tableau experience seeking BI Developer role. Created dashboards driving $5M+ in revenue decisions. Skilled in SQL, ETL processes, and data visualization best practices." Why this works: Tool expertise, business impact, full BI stack. Application Support Analyst Resume Objective Examples "IT Support Specialist with programming knowledge seeking Application Support Analyst position. Resolved 1000+ application issues with 4-hour average resolution time. Ready to bridge technical support and development teams." Why this works: Relevant transition, metrics, cross-functional value. Infrastructure Engineer Resume Objective Examples "Systems Administrator with 5 years experience seeking Infrastructure Engineer role. Automated 70% of routine tasks using Ansible and Python. Ready to design and implement scalable infrastructure solutions." Why this works: Automation focus, specific tools, strategic thinking. Returning After Career Break "IT professional returning after 2-year break, during which I completed AWS and Python certifications. Previously managed infrastructure for 500-user organization. Eager to apply updated cloud skills to modernize your IT environment." Why this works: Addresses gap directly, shows continued learning, focuses on value. Targeting Specific Company "Systems Administrator with expertise in healthcare IT seeking role at [Hospital Name]. Five years ensuring HIPAA compliance while maintaining 99.95% uptime. Ready to support your Epic implementation and digital transformation initiatives." Why this works: Industry-specific knowledge, relevant compliance experience, researched company needs. Remote Position Focus "Senior Developer with 4 years remote work experience seeking distributed team position. Led remote team of 6 developers delivering projects 20% under budget. Expert in async communication and self-directed productivity." Why this works: Addresses remote-specific concerns, proves remote success. IT Consultant Resume Objective Examples "Senior Engineer with 10 years experience across multiple industries seeking IT Consultant role. Saved clients average of $500K annually through optimization strategies. Ready to provide strategic technology guidance to diverse organizations." Why this works: Consulting mindset, client savings, broad experience. Technical Writer Resume Objective Examples "Software Developer with technical writing portfolio seeking Technical Writer position. Created documentation for APIs used by 1000+ developers. Skilled at translating complex technical concepts into clear, user-friendly content." Why this works: Portfolio mention, user impact, core skill emphasis. Scrum Master Resume Objective Examples "Project Coordinator with CSM certification seeking Scrum Master role. Facilitated agile transformation increasing team velocity by 40%. Ready to coach teams in agile practices and remove impediments." Why this works: Agile certification, transformation experience, coaching focus. Platform Engineer Resume Objective Examples "DevOps Engineer with Kubernetes expertise seeking Platform Engineer role. Built internal developer platform reducing deployment time 80%. Ready to create self-service infrastructure enabling developer productivity." Why this works: Modern platform skills, developer enablement, efficiency metrics. Mobile App Developer (iOS Specific) Resume Objective Examples "Software Developer with Swift expertise seeking iOS Developer position. Published 5 apps with combined 50K+ downloads and 4.5+ star ratings. Ready to create exceptional iOS experiences following Apple's design guidelines." Why this works: Platform specialization, app store success, design awareness. Android Developer Resume Objective Examples "Java Developer with 3 years Android experience seeking Android Developer role. Built apps supporting Android 5.0+ with 99.5% crash-free rate. Expert in Kotlin, Jetpack Compose, and Material Design." Why this works: Version coverage, stability metrics, modern Android stack. Game Developer Resume Objective Examples "Software Engineer with Unity experience seeking Game Developer position. Released 3 indie games with 10K+ total players. Skilled in C#, game physics, and performance optimization for mobile platforms." Why this works: Published games, player metrics, relevant technical skills. Embedded Systems Developer Resume Objective Examples "Electrical Engineer with C++ expertise seeking Embedded Systems Developer role. Programmed microcontrollers for IoT devices processing 1M+ sensor readings daily. Ready to develop efficient, real-time embedded solutions." Why this works: Hardware/software bridge, IoT relevance, scale of data. AI Engineer Resume Objective Examples "Machine Learning Engineer with 4 years experience seeking AI Engineer position. Deployed production models reducing customer churn 25%. Expert in deep learning, NLP, and MLOps practices." Why this works: Production focus, business metric, modern AI/ML practices. Check out 250+ resume objective examples for all industry role Common Mistakes to Avoid Too Generic Incorrect : "Seeking challenging IT position where I can grow and learn." Correct: "Python developer with machine learning experience seeking Data Science role to improve your recommendation algorithms." No Value Proposition Incorrect: "Recent graduate looking for entry-level IT job." Correct: "Computer Science graduate with 3 internships seeking Junior Developer role. Ready to contribute tested, documented code from day one." Overloaded with Buzzwords Incorrect: "Dynamic, synergistic IT professional seeking to leverage cutting-edge solutions." Correct: "Network Engineer with SDN experience seeking to reduce your infrastructure costs by 25% through automation." Too Long Incorrect: Four-sentence paragraph explaining your entire career history Correct: Two punchy sentences that state role, skills, and value ATS Optimization Tips Match the job title exactly - If they want "IT Specialist," don't write "Technology Specialist" Include specific technologies - List actual tools, languages, and platforms Use standard abbreviations - Both "IT" and "Information Technology" if space allows Quantify when possible - Numbers stand out to both ATS and humans Avoid graphics or special characters - Stick to plain text ATS Optimization Tips for IT Resume Objectives The Alternative: Professional Summary If you have solid experience, consider this summary format instead: "IT Infrastructure Manager with 8 years optimizing enterprise environments. Reduced system downtime 40% through proactive monitoring and automation. Expert in VMware, AWS, and disaster recovery planning. Currently managing 200+ server hybrid cloud environment." This format works better for experienced professionals because it: Leads with your title and experience Highlights achievements immediately Lists specific technical competencies Provides current scope of responsibility Final Thoughts The best resume objective is often no objective at all, especially if you're an experienced professional with a clear career trajectory. But when you need one, make it specific, quantifiable, and focused on what you'll bring to the role, not what you hope to gain from it. Remember: your objective should answer the question "Why should we interview this person?" in 2-3 lines. If it doesn't, either rewrite it or delete it entirely. Most importantly, don't let the objective become a crutch for a weak resume. Your experience, skills, and achievements sections still need to deliver the goods. The objective just sets the stage, your accomplishments close the deal. Let's Get You An IT Job Kickstart your career with our AI Job Hunter. Apply smarter, save time, and stand out from other candidates. Let our AI Job Hunter do the heavy lifting - find and apply to the best roles instantly. Apply Now Upgrade your resume! Create a hireable resume with just one click and stand out to recruiters. Upload Your Resume Now ← Back to all articles Table of Contents Example H2 Example H3 Ace Your Next Interview with Confidence Unlock personalized guidance and perfect your responses with Final Round AI, ensuring you stand out and succeed in every interview. Get Started Free Related articles Is Consumer Services a Good Career Path even in 2025? Careers • Kaustubh Saini Is Consumer Services a Good Career Path even in 2025? This guide will help you decide whether consumer services is a good career path or not. Also, how AI is shaping the future of the consumer services industry. Is Finance a Good Career Path in 2026? (Expert Insights) Careers • Kaustubh Saini Is Finance a Good Career Path in 2026? (Expert Insights) We asked 37 industry experts about finance as a career in 2026. Discover what they revealed about AI, job outlook, salaries, and how the industry is evolving. 9 Signs of a Toxic Work Environment Careers • Kaustubh Saini 9 Signs of a Toxic Work Environment Understand the warning signs of a toxic work environment and how it affects employees and the company's productivity. Goldman Sachs Interview Process Careers • Kaustubh Saini Goldman Sachs Interview Process Breaking down the complete Interview Process at Goldman Sachs from the HireVue Interview to SuperDay to Coderpad Technical Rounds. SpaceX Interview Process and Hiring Guide Careers • Kaustubh Saini SpaceX Interview Process and Hiring Guide Discover what to expect in the SpaceX interview process, from application to final round, with useful tips to boost your chances of success. Oracle Recruitment Process + Interview Tips Careers • Kaustubh Saini Oracle Recruitment Process + Interview Tips Discover the complete Oracle recruitment process, from resume shortlisting to technical interviews, with tips to help you prepare. Read All Articles Your trusted platform to ace any job interviews, craft the perfect resumes, and land your dream jobs. All services are online Products Interview Copilot AI Mock Interview AI Resume Builder Hirevue Phone Interview Speech Analysis College Admission Auto Apply QA Pairs Interview Notes Coding Copilot Resources Tutorials Blog Articles Special Discount Influencer Program Smarter Choice Support FAQ Contact Us Company How Final Round AI works About Careers News PR & Media Referral Program AI Tools AI Career Coach Recruiters Hotline Cover Letter Generator LinkedIn Profile Optimizer LinkedIn Resume Builder Resume Checker © 2025 Final Round AI, 643 Teresita Blvd, San Francisco, CA 94127 Privacy Policy Terms & Conditions Try Mock Interview Now | 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.