From what I understand, there's no standard implementation of the standard. So each implementation is unique in some ways. Therefore a "unified" experience is impossible.
This video provides a great lens for thinking about the cloud 'spectrum'. Using it as a lens, your product is living somewhere in the middle, and what you're proposing is at one end of the spectrum. Again siding with your CTO, your job is to deliver value, not infrastructure. Maybe you save a few dollars in app costs, but you'll more than eat through those savings in maintaining infrastructure.
I do! I'm sponsoring this effort to catch linux trackpad software up to mac standards. Not affiliated with them in any other way, was simply blown away by a friends magic pad, right about the same time this project started.
https://github.com/gitclear/libinput
edit: I also like to buy merch from OSS affiliated companies. e.g. mozilla hoodie, Neo4j shirt etc.
Is anyone else exhausted by the constant barrage of "personalized" experiences? Its always been about click rate for advertisers, but now they push their monetization model as a feature and it just feels draining.
Like a couple other people I'm very surprised by the negativity around this tool. I was introduced to it when I started my current position a few months ago and I've found it everything BUT hard to use.
The method chaining feels good as long as you check the return type of the function your calling. Most of the time it returns the element you just asserted against. And when you're trying to drill down into deeper sections of the DOM you can speed up tests by calling .within from a higher level element to keep the search to a specific part of the tree.
The individual steps with their state available for viewing in the sidebar is great as others have mentioned. The test doesn't run at light speed, so locally you can actually VIEW what is happening. Plus when it does fail there's typically a long timeout (~40 seconds) before the test actually fails. So it's very noticeable when your test hits a snag.
Also helper functions are not hard at all, and we have a few useful ones we use in almost every section. I have more I could say, but I'm not going to write a huge raving post. Just wanted to try to post some positive contrarian perspective.
100% depends on what kind of work you want to do. There's some principles like cleanliness and comments. But outside of that it starts to get domain specific pretty quickly.
I prefer to have the application ran on my machine in a fashion similar to how I'm going to deploy it. Using a "large" ecosystem IDE detracts from that as the application is now ran by an application rather than in a system. And almost all the features you listed are possible in VSCode. You just have to take an hour or two to set your system up to run it.
I feel like it's on the product to make those benefits apparent and easy to use. They're selling me (the user) not the other way around. The message comes off very privileged IMO.
What an absolutely tone deaf thing to say. "It can't be our product that's using out dated philosophies. It's the users that don't know how to use it properly"
From what I understand, there's no standard implementation of the standard. So each implementation is unique in some ways. Therefore a "unified" experience is impossible.