(I have not personally verified the behavior described in that tweet, but if it's true then a lot of the reporting and commentary around this story has left out important details and the actual change is positive for users. Intentionally configured PWAs still work; everything else opens in your default browser, without any potentially unwanted magic.)
Another vote for Postmark. It works and it's a paid but relatively affordable service - this is a good thing in this area, as it keeps the spammers out, and means you have real human support. I've not had a problem yet. Same can't be said for SendGrid which is used on some client projects but has sporadic deliverability issues at times.
This is now making me worry about what I do next. Will it be possible to revert this madness or is it really time to abandon Firefox?
I know that in the big picture it’s small, but a good part of why the Firefox is the UI. In compact mode, with dark theme, on Linux, Firefox is - for me - the ultimate browser UI that just gets out of my way.
This new “modern” look is oversized, distracting and wastes space. Nobody’s asked for it and the blog post wording really sounds like trying to justify change for the sake of it.
Sad times. What has happened to Mozilla?
Am I making too much of it? Maybe, but it’s certainly not making me “worry less”. It’s filling me with dread. And from the other responses here and on Reddit, it’s clear Mozilla is out-of-touch with it’s biggest users.
I don't see how anyone can give you useful information without knowing more about the pipeline and the projects, and as everyone's pipelines/projects are going to work differently (I do web dev work, so pipelines are relatively simple, I can imagine that a game dev team creating Windows/Mac/Linux builds might have multi-hour pipelines though).
Anyway as the question is "How Long Is Your CI Process", here we go!
I have two main types of pipelines, both running on a self-hosted GitLab instance which runs on an 8th-gen i3 Intel NUC. No project is particularly massive.
1. PHP Projects. Run PHPStan + unit tests on each branch. Most projects take 1-5 mins. On master, run PHPStan + unit tests, build a Docker image, and use Helm to deploy to managed Kubernetes on DigitalOcean. This takes 5-10 mins.
2. React Projects, again not massively huge, but sizable. Biggest time is to run ESLint on every branch. About 5 mins (due to very poor caching which I keep meaning to fix). On master, run ESLint, create a Docker image, and deploy to managed Kubernetes. 5-10 mins.
There are opportunities to improve this by fixing/optimising caching. Overall I'm reasonably happy with the pipeline performance. I'm also sure that upgrading the hardware would make a big difference, probably more so than fixing the caching; an i3 isn't really ideal but this machine does well overall for my small team.
I was subscribed to https://www.gitlab.com/atom.xml - at least, that's what Feedly's UI shows, but that URL doesn't seem to resolve at all. In my Feedly, the newest article was "building a better Heroku".
When you search for GitLab in Feedly, you also see that feed, without the 13.10 post. The "GitLab" source at top of search results shows "about.gitlab.com", 6k followers, but no 13.10 post.
I've directly added your atom.xml link so my situation is resolved for now. Thanks!
The feature releases don’t show up in GitLab’s RSS now... why not? Can’t find any way to subscribe to them.
13.9 didn’t appear and I had to go looking. 13.10 hasn’t either. Blog “news” posts, unfiltered and patch releases all show up in RSS... why aren’t the monthly releases being included anymore?
That's awful. This is one of the reasons I use Firefox, because its UI is customisable and not massive.
Mozilla seems to be intent on taking away the power user features. I didn't even know this redesign was coming, but those screenshots look horrendous. Why are the tabs "floating" as giant blobs? The current design looks much more cohesive and less distracting.
Sad to see Firefox succumb to the "must design everything every few years" mentality.
Almost all the comments in this thread can be summarised as:
GitLab: your product is great; your pricing is madness.
This removal of Starter doesn’t seem to have helped anyone except GitLab. You really need to look at how you’re pricing your service and seriously consider much stronger user role management.
GitLab pricing is unworkable for many smaller teams, so we stay on Free and give you nothing at all. The pricing actively discourages whole-org adoption - no way are we paying $19/mo for a non-dev user who would rarely use the system. So we pay nothing at all and keep everyone on free, because that user does still need some access, so you get nothing at all.
To be clear - I love GitLab and I want to pay for more features. I don’t want Premium for nothing but the way it’s billed is completely impractical and hard to get value from for small dev teams, as we have to think very carefully about who gets an account.
I would love it if you’d think about allowing different users on an instance to have a different plan - like with Microsoft 365, where some users have the full works and others just have an email inbox. I need 5 Premium users, 3 Starter users and 2 Free users, for example. You’d now be getting payment for 8 users instead of 0 in my scenario!
Not all my users need Premium; some do. Consequently, we all stay on Free, because I can only justify/afford the pricing for the handful of Premium licenses I actually need.
I really hope this makes sense - there is money waiting for you, and I know many other small dev shop owners feel the same way, but you’re not doing anything to claim it!
You need to look within yourself and work out how you can sell your product to smaller teams in a way that makes sense for everyone. It kinda feels like you just don’t care about your roots anymore and that you only want Ultimate users on your service; I hope you don’t make the mistake of turning your back on the users who started you off and who vocally endorse and support your product.
This is a genuine Amazon.co.uk cancellation email which I received today. I was going to discard it right after opening - I'd been expecting it and already knew the refund was approved.
Right before closing the message, my eye caught the line "will be displayed in your next bank account" (?). That got me looking at the rest. When you read it through, the whole thing is in horrific broken English and looks like a spam/scam.
I'm not really sure what to make of this. On the one hand, it doesn't seem too critical - it's not asking you to do anything, the meaning is obvious and a lot of people probably won't even read it. On the other hand, it's not exactly setting a good example or making it easy for customers to identify what is and isn't a scam. After spotting the issues, I actually had to verify whether it was real after all - it is, the link does indeed navigate to Amazon.co.uk and the shipment number/order number (redacted from screenshot) do indeed match the order I cancelled during shipping earlier in the week.
Key issues:
- "We are writing you in relation to the cancellation request" - Missing "to".
- "We have refunded the order and you will receive a confirmation e-mail." - Erm, isn't this the confirmation email? Not completely sure to be honest but I think it is.
- "You can see the refund within 5-7 working days, after the refund release, and will be displayed in your next bank account." - This line is awful. Weird mixing of tenses and I've no idea what "your next bank account" is meant to mean.
- "Click on 'Your Account' that you find high right corner on Amazon website" - !!!
- "Refunds and replacements are displayed on the bottom in this page." - !!!
- "We cannot read your answers reply." - Great.
I was really excited about this when I got the email a few weeks ago with a beta invite but after two minutes I realised I’d be unable to use it, and still can’t now it’s launched...
Why oh why is GitHub now considered the single place where code lives? Even as alternative providers gain in popularity.
It’s really sad to see DigitalOcean requiring this for some reason.
Please either allow use of arbitrary Git repositories (e.g. self-hosted GitLab in my use case) or provide a stand-alone CLI tool to enable deployment of anything, like Firebase does.
"Facebook has warned that it may pull out of Europe if the Irish data protection commissioner enforces a ban on sharing data with the US..." haha, "warned" who? You're not wanted!
(I have not personally verified the behavior described in that tweet, but if it's true then a lot of the reporting and commentary around this story has left out important details and the actual change is positive for users. Intentionally configured PWAs still work; everything else opens in your default browser, without any potentially unwanted magic.)