[flagged]
xAI's Grok 3 comes to Microsoft Azure
11–20 of 241 posts
Re: xAI's Grok 3 comes to Microsoft Azure
#12[flagged]
Re: xAI's Grok 3 comes to Microsoft Azure
#13[flagged]
It's honestly one of the better ones I've tried for general questions. I saw it used in a blind competition against ChatGPT, Claude, and Gemini, and amongst people who didn't use LLMs frequently, it was the most favored for 4/5 questions! It's very good at sounding much more natural and less robotic than the others, imo.
Re: xAI's Grok 3 comes to Microsoft Azure
#14[flagged]
It's honestly one of the better ones I've tried for general questions. I saw it used in a blind competition against ChatGPT, Claude, and Gemini, and amongst people who didn't use LLMs frequently, it was the most favored for 4/5 questions! It's very good at sounding much more natural and less robotic than the others, imo.
Re: xAI's Grok 3 comes to Microsoft Azure
#15[flagged]
As professionals, it is absolutely crucial that we discuss matters of ethics. One of which is the issue of an unethical founder.
Re: xAI's Grok 3 comes to Microsoft Azure
#16They claimed that they had a rogue actor who deployed their 'white genocide' prompt, but that either means they have zero technical controls in their release pipeline (unforgivable at their scale) or they are lying (unforgivable given their level of responsibility).
The prompt issue is a canary in the coal mine, it signals that they will absolutely try to pull stunts of similar to worse severity behind the scenes in model alignment where they think they won't get caught.
Re: xAI's Grok 3 comes to Microsoft Azure
#17No serious organization using AI services through Azure should consider using their technology right now, not when a single bad actor has the ability to radically change its behavior in brand-damaging ways.
Re: xAI's Grok 3 comes to Microsoft Azure
#18Re: xAI's Grok 3 comes to Microsoft Azure
#19I asked it about a paper I was looking at (SLOG [0]) and it basically lost the context of what "slog" referred to after 3 prompts.
1. I asked for an example transaction illustrating the key advantages of the SLOG approach. It responded with some general DB transaction stuff.
2. I then said "no use slog like we were talking about" and then it gave me a golang example using the log/slog package
Even without the weird political things around Grok, it just isn't that good.