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.
bitfucker
joined 1 year ago
Then specify MS plugins. If you only said plugins on MS marketplace, you are blaming MS for things they didn't do
You are allowed wtf. If the plugin author didn't distribute it elsewhere, it's on them. MS doesn't forbid them from uploading the extension build elsewhere, they just wanted their marketplace not getting requests from not-their-client which is a fair point for a for profit company.
Did you not disable the unneeded plugins on a project? I wouldn't turn on the rust plugins for a js project if the codebase doesn't have it
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.
No. Normally the kernel doesn't get updated in the network during training. They are called hyper-parameters. They do affect training, but they are not updated by the training algorithm
In the context of machine learning, usually a list of numbers that is arranged in a certain way, and is used for mathematical operation. You can think of it as a transfer/transform "function" that takes data as input, and spits out the representation of said data in some other way (that we usually don't know until the training is finished and we analyze the result)
Yeah, the difference is that this time an expert uses the tools as it should be. Not regular Joe feeding all the code with a prompt to "find a vulnerability". Even then, this is a coincidence. But this discovery means there exists (maybe) a strategy that can be tried to detect similar exploits.
For the kind of supported data, one looks at the README and it supports a lot of different kinds of metadata, hence the generic description. A jpeg (or other image) metadata editor cannot edit metadata for geospatial surveys for example. But this application can. And manage it like any other CRUD application works. By providing users a way to enter a new entry, edit it, remove it, query it, all kinds of things really.
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.
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.