I've a Xiaomi Mi 6 phone (2017 model) that I still use as a fridge-mounted shopping list and it's using the latest version of Chrome. I think it would be quite the stretch to find a user using a 10 year old browser.
I think it's also meant to protect from potential mistakes in handling of hard disk decommissioning which presumably is a common thing with data centers.
Copilot cannot be behind any models because it's a harness, not a model. You can use any of the popular models through it, including Claude models. Though people have been saying that Claude CLI is a better experience.
Same experience with UI performance, especially on Linux (Fedora). I went back to Zen Browser because of this, but frankly most browsers are performing worse for me on Linux than on Windows.
According to the email I initially received for this alert, zed.exe was attempting to access its own folder within the AppData directory. Nothing more normal than that, no?
No idea how that related to what I was told by the sec people shortly afterwards.
I installed Zed on a work machine at a well-known software company and a week later they forced me to reimage my machine because they got some alert that the app was attempting to access browser credentials :(
No shade on Zed, sometimes in-house security tools just don't like new software.
As with regex, querying is about not getting what you don't want as much as it is about getting what you want. And the former of the two is much more difficult to verify.
I don't want to paint your comment as pro-AI brigading, but in the solution to any problem, considering the collaterals is a pillar principle of engineering. You don't get praise for solving a bug infestation problem by nuking the city.
I feel some of the recent HackerNews stories start leaning a bit too much toward using AI regardless of whether it makes sense. A solution to any problem, however interesting or clever should be critiqued holistically, alternatives included.
I don't think performance advice should be part of a general architectural principles list, so I don't think that's what they meant. Otherwise might as well add "avoid nested loops", etc, and then it devolves into a general programming advice list.
Performance is and always was something dependent on the domain rules. You don't start architecting for performance before understanding requirements so why make it a pillar of all architecture.
Bottom line is the people described as hypocritical in the comment have no principles, but rather feign passion in anything they think other people consider valuable. When devs thought coding skill was valuable, that's what they claimed to be passionate about, when the game changed and communication became key, they suddenly changed their passion. Either the timing is a coincidence, or they are hypocrites.
I don't think switching one's passion on a dime is a valid escape hatch from hypocrisy.
They said 2 years after purchase. So that's where the debate is. How long should we hold manufacturers accountable for in regards to waterproofing? 1 year, 2 years, forever?
The only thing that bothers me about Zed is the theme. It's so bland it actually gives me reading difficulties. I'd be surprised if some of the color combinations don't pose an accessibility issue. Grey text on grey background is quite the choice.
MS incentivizes feature quantity, and the leadership are employees like any other. Product improvements are not on the table unless the company starts promoting people based on it. Doesn't look this will start happening any time soon.
Hetzner was raved about before AI was cool. I know since based on those good reviews I moved half of my apps from DigitalOcean to Hetzner. My DigitalOcean droplet was lacking in RAM and it was more expensive for me to grow it than move some stuff to another small VPS on Hetzner.