Apple has also seemingly stopped caring about the quality and efficiency of their software. You can see this especially in the latest iOS/iPadOS/macOS 26 versions of their operating systems. They need their software leadership to match their hardware leadership, otherwise good hardware with bad software still leads to bad product, which is what we are seeing now.
> Apple has also seemingly stopped caring about the quality and efficiency of their software.
Hardware has improved significantly, but it needs software to enable me to enjoy using it.
Apple is not the only major company that has completely abandoned the users.
The fastest CPUs and GPUs with the most RAM will not make me happier being targeted by commercial surveillance mechanisms, social-media applications, and hallucinating LLM systems.
I see this sentiment a lot, but I've found the OS26 releases to be considerably better than the last few years' OS releases, especially macOS which actually feels coherent now compared to the last few years of janky half baked UI.
It is frankly ridiculous how unintuitive it was to add an email account to Mail on iOS. This is possibly the most basic functionality I would expect an email client to have. One would expect that they go to their list of mailboxes and add a new account.
No. You exit the mail app -> Go to settings -> apps -> scroll through a massive list (that you usually just use for notification settings btw) to go to mail -> mail accounts -> add new account.
Just a simple six-step process after you’ve already hunted for it in the mail app.
I think the most most basic integration w.r.t. email I want from Apple is that I want to set up another email program besides “Mail” as the default email program, but without having to set up Mail first.
I prompted Bolt with a very simple task that I've spent years of my life developing (a specific scenario only possible via browser automation). Bolt invented a plausible, but fictitious, API on the third party to call.
I have enjoyed how quickly 1Password was adopting new technology and features while still staying stable. It just worked. Lately, that hasn't been the case. Recently, the browser extension, which is my main interface for 1Password, has been acting up.
I use browser extension in Edge on macOS. I am on a page signing up for a new website and want to save credentials. It doesn't. Keeps erroring out. Disabling and re-enabling extension, and then refreshing the tab finally fixes it. I reached out to customer support and they told me to sign out to force refresh the cache. I did it, but the problem wasn't fixed.
1Password needs to fix the bugs that their customers are already reporting, instead of alienating their users with telemetry. I don't think the learnings from telemetry will be worth the damage it will cause to their brand.
> Recently, the browser extension, which is my main interface for 1Password, has been acting up.
> I use browser extension in Edge on macOS. I am on a page signing up for a new website and want to save credentials. It doesn't. Keeps erroring out. Disabling and re-enabling extension, and then refreshing the tab finally fixes it. I reached out to customer support and they told me to sign out to force refresh the cache. I did it, but the problem wasn't fixed.
I've had the same issue, support told me the exact same thing:
1. Lock the 1Password app (which also locks the extension).
2. Unlock the 1Password app (which also unlocks the extension).
If the issue is still present, please go through the steps below to fully re-sync your account:
1. Right click the 1Password icon in your browser toolbar and choose Settings.
2. Under General, disable "Integrate with 1Password app".
3. Under Accounts & Vaults, sign out of your account.
4. Sign back into your account.
5. Go back to General, and re-enable "Integrate with 1Password app".
I told them it didn't help at all, they claim they've released a fix for "one of the possible causes of the bug", in the beta version of the extension, they asked me to make a new chrome profile and install the beta version but I just didn't bother at that point and just lived with it..
FYI, I spent some more time troubleshooting and might have found the root cause. I had switched to 1Password 8 Beta before it was released because I enjoyed the updated UI. Once version 8 was officially released, I switched to the Stable channel, but the desktop app was stuck on the old beta version. So, beta was old, but the extension kept getting updated likely causing the bad behavior.
I uninstalled the macOS beta app and reinstalled the stable version. It seems to be working fine for the last day or so.
Some may ask why we didn’t announce these role reductions with the ones we announced a couple months ago. The short answer is that not all of the teams were done with their analyses in the late fall;
I am torn on this. How does the decision to have at least two layoffs affect employee morale? Is that not worth waiting?
Yeah, not to mention it ignores the questions of "how many teams still haven't finished" and "is it the same management that made the excess growth that is looking to explain where they should be?"
That last is huge, btw. Leadership setup a disaster to require a few layoffs. I'm assuming leadership is having to take on some pain, as well?
My guess is they are probably looking for a buyer, who will likely roll everything into their offering. So, the more they can get back, the higher the sale price.
I don't know about CircleCI specifically, but generally, pre-IPO companies are pushed to reinvest profits in favor of aggressive/continued growth, instead of profit. Most companies intentionally overspend, but now that the investments are drying out, they are changing their posture. So, I would guess it's the former, i.e., letting people go to reduce the risk of running out of money.
At the same time, depending on how the business is doing, some investors might look for exits too instead of plateau or later raising another round. So, it could be both.
That's a not a very helpful feedback, especially for folks that might be looking into using them. Any chance you can share more on what you don't like?
Not the original commenter, but for me, several things made me despise it:
* No way of entering code blocks renders the product completely useless for technical teams. (JIRA also makes it particularly complicated with their "code block" element)
* The clunkiness of the heavy-weight JavaScript frontend is inducing a very negative feeling the moment I think about having to open Asana.
* The user interface breaks commonly established UX patterns: Middle click on a card doesn't open the task in a new window, as all other clickable things in a browser suggest. Cross-referencing two tickets is completely impossible (besides cloning the tab and opening two separate tasks in both)
Also imposible to link pull requests to tasks and back (because Asana tasks has long unreadable urls), constantly changing urls mean that you can't put Asana task URL in the vcs commit message to make it easier understanding evolution of code.
No markdown support, you have to remember clumsy set of unique hot keys for message formatting.
The feature I most wanted out of Asana, back when I had to use it, was a way to open links to individual issues as some kind of basic, plain HTML page so I'd rarely have to load Asana itself. I dreaded opening it every time, couldn't just leave it open because it ate too much memory and too many cycles for something I only needed to look at a few times a day.
We tried to move to Asana when Trello announced their restrictions a while back. At the time Asana had no production grade way to migrate from Trello. The tool they had was just an extension build by a third party and it did a poor job at migrating your boards over without losing detail.
For something so critical to Asana's business model - in capturing Trello evacuees - it sure felt a bit weird.
Has things improved since then?
In the end we went all the way to Azure DevOps to solve our problem. (But in doing so we created a million more!)
