▲ 173 ▼ I ditched Linux for Windows 11 for one week - and found 9 big problems (www.zdnet.com) submitted 1 year ago by tomenzgg@midwest.social to c/linux@programming.dev 128 comments fedilink hide all child comments
[–] possiblylinux127@lemmy.zip 4 points 1 year ago* (10 children) Why are we shouting? Anyway, don't waste your time with "antivirus" software. That is not how you secure a system. permalink fedilink source parent hideshow 10 child comments replies: [–] princessnorah@lemmy.blahaj.zone 5 points 1 year ago (1 child) That is not how you secure a system. Yes, but projects like Wayland which are trying to do this get shouted down. permalink fedilink source parent hideshow 1 child comment replies: [–] sem@lemmy.blahaj.zone 1 point 1 year ago I was almost sure Wayland had succeeded... Well except for people still stuck on Xorg because of accessibility features... permalink fedilink source parent [–] Lojcs@piefed.social 6 points 1 year ago (7 children) Your viewer must be parsing #8 as # 8. You're free to not 'waste time' with anti-virus but I prefer the peace of mind. permalink fedilink source parent hideshow 7 child comments replies: [–] possiblylinux127@lemmy.zip 4 points 1 year ago (6 children) You need to put a backslash before the hash tag. In Markdown a # is a headet permalink fedilink source parent hideshow 6 child comments replies: [–] Lojcs@piefed.social 4 points 1 year ago (1 child) No? There needs to be a space between on piefed and that's how it works on github too. https://piefed.social/comment/8602660 permalink fedilink source parent hideshow 1 child comment replies: [–] Nalivai@lemmy.world 5 points 1 year ago https://www.markdownguide.org/basic-syntax/ Putting a space is a good practice for compatibility because different software behaves differently. But the standard doesn't specify it per se. permalink fedilink source parent [–] ulterno@programming.dev 1 point 1 year ago (3 children) As Lojcs said... The Markdown format expects a space after whatever number of #s you put at the start, for it to be a corresponding level header. Due to different parsers having different types of leeways, it becomes a bit difficult to make sure stuff always matches. e.g. I was once mistaken about the way tabs work for multi-level bullets and numbering because GitLab had more leeway. Using discount, I realised where I was being wrong. permalink fedilink source parent hideshow 3 child comments replies: [–] Nalivai@lemmy.world 1 point 1 year ago (2 children) The whole problem is because format doesn't actually expects the space there, and it's left to the interpretation of the parser permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@programming.dev 1 point 1 year ago (1 child) I thought the whole problem was that there was no de-facto standard and people kept on making their deviations while still calling it Markdown. I personally like how Doxygen implements it. permalink fedilink source parent hideshow 1 child comment replies: [–] Nalivai@lemmy.world 2 points 1 year ago Yeah. The power of MD is that it's lightweight, versatile, and not very restrictive. You don't need to remember a lot, and the parser is dirt easy to implement. The negatives are that it's not very restrictive, nobody remembers what's what, and the parser so easy to implement, everyone and their dog has one, and they're all slightly different permalink fedilink source parent
[–] princessnorah@lemmy.blahaj.zone 5 points 1 year ago (1 child) That is not how you secure a system. Yes, but projects like Wayland which are trying to do this get shouted down. permalink fedilink source parent hideshow 1 child comment replies: [–] sem@lemmy.blahaj.zone 1 point 1 year ago I was almost sure Wayland had succeeded... Well except for people still stuck on Xorg because of accessibility features... permalink fedilink source parent
[–] sem@lemmy.blahaj.zone 1 point 1 year ago I was almost sure Wayland had succeeded... Well except for people still stuck on Xorg because of accessibility features... permalink fedilink source parent
[–] Lojcs@piefed.social 6 points 1 year ago (7 children) Your viewer must be parsing #8 as # 8. You're free to not 'waste time' with anti-virus but I prefer the peace of mind. permalink fedilink source parent hideshow 7 child comments replies: [–] possiblylinux127@lemmy.zip 4 points 1 year ago (6 children) You need to put a backslash before the hash tag. In Markdown a # is a headet permalink fedilink source parent hideshow 6 child comments replies: [–] Lojcs@piefed.social 4 points 1 year ago (1 child) No? There needs to be a space between on piefed and that's how it works on github too. https://piefed.social/comment/8602660 permalink fedilink source parent hideshow 1 child comment replies: [–] Nalivai@lemmy.world 5 points 1 year ago https://www.markdownguide.org/basic-syntax/ Putting a space is a good practice for compatibility because different software behaves differently. But the standard doesn't specify it per se. permalink fedilink source parent [–] ulterno@programming.dev 1 point 1 year ago (3 children) As Lojcs said... The Markdown format expects a space after whatever number of #s you put at the start, for it to be a corresponding level header. Due to different parsers having different types of leeways, it becomes a bit difficult to make sure stuff always matches. e.g. I was once mistaken about the way tabs work for multi-level bullets and numbering because GitLab had more leeway. Using discount, I realised where I was being wrong. permalink fedilink source parent hideshow 3 child comments replies: [–] Nalivai@lemmy.world 1 point 1 year ago (2 children) The whole problem is because format doesn't actually expects the space there, and it's left to the interpretation of the parser permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@programming.dev 1 point 1 year ago (1 child) I thought the whole problem was that there was no de-facto standard and people kept on making their deviations while still calling it Markdown. I personally like how Doxygen implements it. permalink fedilink source parent hideshow 1 child comment replies: [–] Nalivai@lemmy.world 2 points 1 year ago Yeah. The power of MD is that it's lightweight, versatile, and not very restrictive. You don't need to remember a lot, and the parser is dirt easy to implement. The negatives are that it's not very restrictive, nobody remembers what's what, and the parser so easy to implement, everyone and their dog has one, and they're all slightly different permalink fedilink source parent
[–] possiblylinux127@lemmy.zip 4 points 1 year ago (6 children) You need to put a backslash before the hash tag. In Markdown a # is a headet permalink fedilink source parent hideshow 6 child comments replies: [–] Lojcs@piefed.social 4 points 1 year ago (1 child) No? There needs to be a space between on piefed and that's how it works on github too. https://piefed.social/comment/8602660 permalink fedilink source parent hideshow 1 child comment replies: [–] Nalivai@lemmy.world 5 points 1 year ago https://www.markdownguide.org/basic-syntax/ Putting a space is a good practice for compatibility because different software behaves differently. But the standard doesn't specify it per se. permalink fedilink source parent [–] ulterno@programming.dev 1 point 1 year ago (3 children) As Lojcs said... The Markdown format expects a space after whatever number of #s you put at the start, for it to be a corresponding level header. Due to different parsers having different types of leeways, it becomes a bit difficult to make sure stuff always matches. e.g. I was once mistaken about the way tabs work for multi-level bullets and numbering because GitLab had more leeway. Using discount, I realised where I was being wrong. permalink fedilink source parent hideshow 3 child comments replies: [–] Nalivai@lemmy.world 1 point 1 year ago (2 children) The whole problem is because format doesn't actually expects the space there, and it's left to the interpretation of the parser permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@programming.dev 1 point 1 year ago (1 child) I thought the whole problem was that there was no de-facto standard and people kept on making their deviations while still calling it Markdown. I personally like how Doxygen implements it. permalink fedilink source parent hideshow 1 child comment replies: [–] Nalivai@lemmy.world 2 points 1 year ago Yeah. The power of MD is that it's lightweight, versatile, and not very restrictive. You don't need to remember a lot, and the parser is dirt easy to implement. The negatives are that it's not very restrictive, nobody remembers what's what, and the parser so easy to implement, everyone and their dog has one, and they're all slightly different permalink fedilink source parent
[–] Lojcs@piefed.social 4 points 1 year ago (1 child) No? There needs to be a space between on piefed and that's how it works on github too. https://piefed.social/comment/8602660 permalink fedilink source parent hideshow 1 child comment replies: [–] Nalivai@lemmy.world 5 points 1 year ago https://www.markdownguide.org/basic-syntax/ Putting a space is a good practice for compatibility because different software behaves differently. But the standard doesn't specify it per se. permalink fedilink source parent
[–] Nalivai@lemmy.world 5 points 1 year ago https://www.markdownguide.org/basic-syntax/ Putting a space is a good practice for compatibility because different software behaves differently. But the standard doesn't specify it per se. permalink fedilink source parent
[–] ulterno@programming.dev 1 point 1 year ago (3 children) As Lojcs said... The Markdown format expects a space after whatever number of #s you put at the start, for it to be a corresponding level header. Due to different parsers having different types of leeways, it becomes a bit difficult to make sure stuff always matches. e.g. I was once mistaken about the way tabs work for multi-level bullets and numbering because GitLab had more leeway. Using discount, I realised where I was being wrong. permalink fedilink source parent hideshow 3 child comments replies: [–] Nalivai@lemmy.world 1 point 1 year ago (2 children) The whole problem is because format doesn't actually expects the space there, and it's left to the interpretation of the parser permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@programming.dev 1 point 1 year ago (1 child) I thought the whole problem was that there was no de-facto standard and people kept on making their deviations while still calling it Markdown. I personally like how Doxygen implements it. permalink fedilink source parent hideshow 1 child comment replies: [–] Nalivai@lemmy.world 2 points 1 year ago Yeah. The power of MD is that it's lightweight, versatile, and not very restrictive. You don't need to remember a lot, and the parser is dirt easy to implement. The negatives are that it's not very restrictive, nobody remembers what's what, and the parser so easy to implement, everyone and their dog has one, and they're all slightly different permalink fedilink source parent
[–] Nalivai@lemmy.world 1 point 1 year ago (2 children) The whole problem is because format doesn't actually expects the space there, and it's left to the interpretation of the parser permalink fedilink source parent hideshow 2 child comments replies: [–] ulterno@programming.dev 1 point 1 year ago (1 child) I thought the whole problem was that there was no de-facto standard and people kept on making their deviations while still calling it Markdown. I personally like how Doxygen implements it. permalink fedilink source parent hideshow 1 child comment replies: [–] Nalivai@lemmy.world 2 points 1 year ago Yeah. The power of MD is that it's lightweight, versatile, and not very restrictive. You don't need to remember a lot, and the parser is dirt easy to implement. The negatives are that it's not very restrictive, nobody remembers what's what, and the parser so easy to implement, everyone and their dog has one, and they're all slightly different permalink fedilink source parent
[–] ulterno@programming.dev 1 point 1 year ago (1 child) I thought the whole problem was that there was no de-facto standard and people kept on making their deviations while still calling it Markdown. I personally like how Doxygen implements it. permalink fedilink source parent hideshow 1 child comment replies: [–] Nalivai@lemmy.world 2 points 1 year ago Yeah. The power of MD is that it's lightweight, versatile, and not very restrictive. You don't need to remember a lot, and the parser is dirt easy to implement. The negatives are that it's not very restrictive, nobody remembers what's what, and the parser so easy to implement, everyone and their dog has one, and they're all slightly different permalink fedilink source parent
[–] Nalivai@lemmy.world 2 points 1 year ago Yeah. The power of MD is that it's lightweight, versatile, and not very restrictive. You don't need to remember a lot, and the parser is dirt easy to implement. The negatives are that it's not very restrictive, nobody remembers what's what, and the parser so easy to implement, everyone and their dog has one, and they're all slightly different permalink fedilink source parent