you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 11 months ago (1 child)

I don't want to make this a "gotcha", but you say no xaml knowledge needed but then talk about it and have the reader touch them (mostly delete). You say you usually delete this xaml file but I don't need to do that. Why? What do I gain or lose? I thought I didn't need to know xaml?

I read your entire tutorial. I've been in the industry for a while. I found it hard to read but mostly due to the sentence structure. I suppose if english isn't your first language (it isn't mine), that might explain it. I can give you more comprehensive feedback, if you'd like.

I know hearing constructive criticism is hard, but it is part of the learning process.

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] -1 points 11 months ago

    I don’t want to make this a “gotcha”, but you say no xaml knowledge needed but then talk about it and have the reader touch them (mostly delete).

    I only have them delete the XAML files. You don't need to know anything about what's inside a file to delete it 😂 Also, I only talk about the benefits of getting rid of them, which also doesn't require any knowledge of XAML.

    You say you usually delete this xaml file but I don’t need to do that. Why?

    No I don't! I say disabling implicit usings is optional, and do explain why I do it, then delete the XAML files. You seem to have conflated 2 successive paragraphs.

    I thought I didn’t need to know xaml?

    You don't. They're never used anywhere in the whole thing. We only delete the XAML files, then replace them with C#.

    I read your entire tutorial.

    Not very carefully apparently.

  • source
  • parent