61–70 of 113 posts
Partnering with the incomprehensibly byzantine andcomplacent architect of the SEOpocalypse AND "late-to-the-ai-party" Google does not give faith that the solution will be more performant or private than Github's copilot.
This is just another in a series of terrible blunders in the last year that has wiped out any goodwill I had towards gitlab. WTF happened, did they get a new CEO or something?
Maybe GCP, Azure and AWS could pull together the text to train a language model to tell us how to deal with their fucking stupid UIs and arcane terminology. I dread having to use their cloud portals. How do you find a VM by IP address in Azure? that kind of thing.
First, their UI and UX are very different. Azure is by far the worst (as in pretty much all categories) - even their docs suck, with random broken links (even the links to switch the language of the exemple code) and very weird naming schemes, let alone the actual cloud UI. GCP and AWS are quite decent (for AWS you need to know a bit about how they organise things or use the search, but still). > How do you find a VM…
AWS's UI varies dramatically by product, which is both part of the problem with it (lack of a coherent design language leads to confusion) and makes it hard to talk about AWS's UI. Everyone has a different opinion based on which subset of tools they use.
AI sound cool but at this point I'm just expecting another half baked feature that checks boxes for executives to justify purchasing it.
> GitLab plans to improve its customers' DevSecOps workflow efficiency by 10x, by applying AI-assisted workflows I'm also planning to improve my fitness by 10x from tomorrow. Using AI obviously! But today let me eat this pizza
Earlier quoted context omitted.
I think it's due to cookies. That's why there's e.g. googleusercontent.com, ggpht.com etc. That way if users find a way to upload malicious content (or e.g. blog is compromised) you can't get users' Google cookies
If only there was some sort of system of domain names that could be used to indicate the demarcation points...
There's no way to exclude certain subdomains, so once you've decided to share a cookie between subdomains you have to use a new domain if you want to exclude a site from sharing.
I think my productivity would 2x or 3x if gitlab would work on fixing issues with core features such as task planning. There's a lot of minimum viable features that never got improved, especially for those of us on the premium tier. AI sound cool but at this point I'm just expecting another half baked feature that checks boxes for executives to justify purchasing it.
Earlier quoted context omitted.
I think it's due to cookies. That's why there's e.g. googleusercontent.com, ggpht.com etc. That way if users find a way to upload malicious content (or e.g. blog is compromised) you can't get users' Google cookies
They have their own tld, .goog, they could surely have put the website under their instead to at least gain some trust, instead of the current abomination of a domain. Or, you know, just use subdomains which has existed since forever...
All of the links go to some fishy domain c212.net which is blocked by µblock lists.
Bizarre choice for a domain huh, googlecloudpresscorner.com… With all the domains in the world, they pick one that almost looks fake. Why not presscorner.google.com? (Or why not their TLD…) Anyways, I look forward to some new improvements in Gitlab. Seems a little vague on the details, but I think some different flavors of LLMs should prove interesting. Seems likely it’d spit out different results than what OpenAI mi…
However strange that they didn't use withgoogle.com which IIRC is a commonly used separate domain for this type of thing.
Gitlab should stick to its lane and finish its already huge surface area of its products instead of chasing the AI hype. Sid…
Earlier quoted context omitted.
If only there was some sort of system of domain names that could be used to indicate the demarcation points...
Google's cookie situation is complicated, because they have one login that people expect to work across mail.google.com, docs.google.com, drive.google.com, etc. Without going to a ton of server-side gymnastics, the most seamless way to connect all those properties is to set the session ID cookie on .google.com, allowing access to all subdomains recursively. There's no way to exclude certain subdomains, so once you've…
I think Google should fix this. The alternative is endless domain sprawl, for all time.