The HMD phones I bought before 2020 were really great (e.g. 7+) - I kept needing to replace because got stolen or I broke screen. After Covid I bought an underpowered HMD which was really terrible - maybe they had trouble sourcing good CPUs?
With Android I find my choices are either buy a cheap shitty phone, or pay too much. It's hard to find a good value Android. At least the battery can last 2 days on some Androids (my favourite feature).
HMD was founded by a bunch of ex-Nokia people. They're based in Finland, like Nokia. I assume plenty ex-Nokia people work there now, would love to know how true this is if anyone knows.
There's a smattering of old Nokia hands at HMD, but in my experience you're likely to find at least a few ex-Nokia people in almost any tech company of note out here. For all its faults as a company it birthed a generation of truly exceptional electrical and embedded engineers, and they in turn have birthed a metric ton of startups in the last decade all over the place.
It looks like HMD Global's headquarters are in Espoo, which is kind of like the Long Island of Helsinki if that makes sense. So they definitely have access to a lot of that human capital if and when they need it.
Fair, still calling it a successor just because it was founded by some employees is reaching. Nokia still exists and has just lent its brand and some patents to HMD. All the manufacturing style, innovation, basically the hallmarks of Nokia are gone. Nokia was one of the biggest companies in Finland so it is no surprise to find people working at HMD or any other tech company.
Can I ask what specific pain points you have with Gitlab CI? I've been using it extensively the last couple of years and all in all it's been a pretty smooth experience!
* Doesn't scale. In many places. In particular, GitLab CI is required to use GitLab's Gitaly for Git replication. Gitaly has architectural limitations on throughput, which are surprisingly easy to hit with even a medium sized team. Certain otherwise reasonable patterns, particularly child pipelines, cause severe load amplification with Gitaly.
* Bad error handling. Ruby errors leak through. Although the underlying error is my user error, returning it to me as an underlying Ruby exception is really unhelpful. It basically shows that they didn't validate inputs at all. The input is trusted, so it's probably not a security issue, but it's a huge usability and developer experience issue.
* Config format is weird and deficient. Surprisingly difficult to programmatically generate. Can't generate new jobs into the current pipeline. Must generate child pipelines. See above for the load amplification issue therein.
The fact that it would even go down and it requires online connection to vacuum up my data is such a bananas level oversight from MS. That company, man, that company.
It doesn’t. These guys are probably still upset about the ribbon.
Microsoft is not my favorite company. But the only reason O365 has been down for days is when customer integrations (identity, security stuff, VPN rules, etc) break. That was even true in the early days before 365 branding. Source: I’ve been accountable for 250k+ user O365 environments as a customer director or VP for over a decade.
Really? Or did that not make its way up the chain of command? None of your 250k+ accounts had issues because they didn't connect to the internet? What about license renewals - did anyone get shut out of their account immediately because they missed a license renewal date and happy to be off the internet?
