Oh my god, yes. I used to like it, but once you dive just a bit deeper into literally any feature, you will always always find quirks that make absolutely no se

Oh my god, yes. I used to like it, but once you dive just a bit deeper into literally any feature, you will always always find quirks that make absolutely no sense. There is always some sort of limitation that is obviously caused by shipping anything they can as fast as possible. Absolutely 0 polish. A small but frustrating example I experienced just today: In Azure ML, you can create data assets (basically a sort of centeal syslink to your actual data in a storage container) so that you can version your data and access it easily in your pipelines. Sounds great! But they recently pushed a new version that makes it impossible to create a data asset with multiple folders (!). You used to be able to do it, but now your data asset can either be a single file, a single folder (with no subfolders!), or a tabular asset. It's completely insane to me because you now need to create a data asset for every folder you have. on a product made for data-heavy ML workloads. If you have data across a few dozens/hundreds of folders, you can't aggregate them even if they are to be used on the same pipeline, unless you do it manually. Also, now that you have dozens of unnecessary data assets, you can't even set your pipeline to take an arbitrary amount of them as input. You have 20 data assets/folders? Have fun adding 20 inputs in your component's YAML. I can get around it, and maybe I'm dumb and all of our data should have been in a single folder anyway. But it used to work, with no downsides! This stuff happens every day and can be especially aggravating in "heavier" services like AKS.