• 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: March 28th, 2024

help-circle
  • My point is, clear up your mistakes in communication. It doesn’t help anyone to spread misinformation. I hate MS as the linux guy next door, but making false accusations, intentionally or not, will make people stay away from you. Because as I stated, I immediately understand the context just from you sending ToS of a plugin owned by MS. But your accusation is different entirely than your intention.


  • I never have a problem with your follow up, even if you still did not specify your intention explicitly. At least the ToS is for a plugin that is owned by MS so it provides a clue to what you’re referring to. I have a problem with your original statement.

    … A lot of the functionality is in the marketplace but non Microsoft products aren’t legally allowed to use it and you’re not allowed to distribute builds of the plugins.

    To put differently:

    A lot of the functionality is in the marketplace. Non MS products aren’t legally allowed to use it (1). You’re not allowed to distribute builds of the plugin(s) (2).

    See the problem? That statement with the follow up is accusing MS restricting your right to use MS marketplace from non MS product as a problem (1), and THEN accusing that you cannot distribute the build of the plugins from said marketplace (2) which is only true for MS owned plugins.


  • Yes, hence why I commented that MS never prohibits you from publishing your extension elsewhere. Nor does MS forbid you from using other marketplaces when using their product. It’s like saying valve is prohibiting game dev from publishing their game elsewhere or distributing their game outside of steam. It’s just not true. And MS has all the right to limit their marketplace to their own client too. After all, it is first and foremost, their service for their product specifically. It’s like you’re making an unofficial client for youtube.






  • Pick a hardware to tinker with. I’d suggest a development kit rather than some cheap mcu-psu-downloader-only board. Now listen, it may be more on the expensive side, but you don’t have to deal with hardware trouble first since many development board usually provide a lot of functionality to play with.

    Second, check the official documentation for said devkit and play with it. You’ll ended up immersing yourself on your selected manufacturer but that’s fine for learning.

    After you’ve more understanding of the workflow for embedded development, then I can safely advice you to start exploring. A simple one would be programming the same board but using a different workflow. You may ended up with the manufacturer IDE, and wondering how to get to your beloved editor for example. Then you start to learn the build workflow until download and debug step.