I am sorry to say Graphene has fallen to the slop.
-
@davidgerard @dysfun @FediThing @contrasocial Why should GrapheneOS even care that they're being "left behind"? "Left behind" by whom? Is the point of the project merely to one-up similar projects on features at any cost, including at the expense of quality and security? That's not a great proposition for its users, who should perhaps instead start looking at the competition to see what GrapheneOS is so desperate to catch up with.
@pndc @davidgerard @dysfun @FediThing @contrasocial They want some of that sweet VC money (that has already been thrown away elsewhere)?
-
@davidgerard If ycombinator is the source on grapheneos issues, then it's not true. Some of you sound like religious nutjobs when talking about ai with words like 'tainted', a horseshoe version of twitter users who are psychotically pro ai.
Edit: you blocked me, but this was my first fedi account, so yes it's masto.social. Is that the best you've got, mister terminally online who replies in 30 seconds?
@frutiger@mastodon.social mastodon.social, 14 followers, thanks slopbot
the source is reading their fucking AGENTS.md you dipshit
-
@pndc @davidgerard @dysfun @FediThing @contrasocial They want some of that sweet VC money (that has already been thrown away elsewhere)?
@RogerBW @pndc @dysfun @FediThing @contrasocial yeah @zzt points out the fucking weird Motorola deal as the obvious proximate cause
-
I am sorry to say Graphene has fallen to the slop. thread: https://grapheneos.social/@GrapheneOS/117226938743085364
they are making out that their vibe coding isn't *vibe* coding how dare you, which may be worse https://news.ycombinator.com/item?id=49591796
@davidgerard “The output is filled with hallucinations and incorrect details but an experienced developer can sift through it, identify the real issues it uncovered and get those fixed.”
Because every developers favorite part of using code analysis tools has always been sifting through all the false positives.
-
@davidgerard “The output is filled with hallucinations and incorrect details but an experienced developer can sift through it, identify the real issues it uncovered and get those fixed.”
Because every developers favorite part of using code analysis tools has always been sifting through all the false positives.
@iain yeah that bit was very obviously someone pasting in a marketing excuse
-
I am sorry to say Graphene has fallen to the slop. thread: https://grapheneos.social/@GrapheneOS/117226938743085364
they are making out that their vibe coding isn't *vibe* coding how dare you, which may be worse https://news.ycombinator.com/item?id=49591796
@davidgerard So how fucked up is /e/os with respect to LLM use? GrapheneOS is out of consideration, and I considered them to be the best de-Googled Android option, unfortunately.
-
@davidgerard “The output is filled with hallucinations and incorrect details but an experienced developer can sift through it, identify the real issues it uncovered and get those fixed.”
Because every developers favorite part of using code analysis tools has always been sifting through all the false positives.
@iain @davidgerard Reminds me of the C standard, which requires a conforming implementation to output at least one diagnostic for invalid code, but says nothing about valid code. So if your compiler simply prints "your code is bad" in all cases, even if the code is fine, it is conforming.
-
@davidgerard “The output is filled with hallucinations and incorrect details but an experienced developer can sift through it, identify the real issues it uncovered and get those fixed.”
Because every developers favorite part of using code analysis tools has always been sifting through all the false positives.
@iain @davidgerard@circumstances.run This may be me personally but this approach feels beneath me.
I did not spend more than fifteen years honing my craft to be degraded to a babysitter for someone's poor quality tool.
-
@davidgerard “The output is filled with hallucinations and incorrect details but an experienced developer can sift through it, identify the real issues it uncovered and get those fixed.”
Because every developers favorite part of using code analysis tools has always been sifting through all the false positives.
@iain @davidgerard I’m no coder but doesn’t that suggest the developers should just craft the output themselves if the vibe output is shite?
-
I am sorry to say Graphene has fallen to the slop. thread: https://grapheneos.social/@GrapheneOS/117226938743085364
they are making out that their vibe coding isn't *vibe* coding how dare you, which may be worse https://news.ycombinator.com/item?id=49591796
@davidgerard god fucking dammit! The whole appeal of this project was that commited experts would patch everything. What's even the point?
-
@frutiger@mastodon.social mastodon.social, 14 followers, thanks slopbot
the source is reading their fucking AGENTS.md you dipshit
@davidgerard
“I read your AGENTS.md” diss -
J jwcph@helvede.net shared this topic
