←back to thread

GGML – AI at the Edge

(ggml.ai)
899 points georgehill | 2 comments | 06 Jun 23 16:50 UTC | HN request time: 0.545s | source
Show context
_20p0 ◴[06 Jun 23 17:03 UTC] No.36215876[source]▶
This guy is damned good. I sponsored him on Github because his software is dope. I also like how when some controversy erupted on the project he just ejected the controversial people and moved on. Good stewardship. Great code.

I recall something like when he first ported it and it worked on my M1 Max he hadn't even yet tested it on Apple Silicon since he didn't have the hardware.

Honestly, with this and whisper, I am a huge fan. Good luck to him and the new company.

replies(4): >>36216131 #>>36216191 #>>36216199 #>>36216264 #
PrimeMcFly ◴[06 Jun 23 17:32 UTC] No.36216264[source]▶
> I also like how when some controversy erupted on the project he just ejected the controversial people and moved on. Good stewardship

Do you have more info on the controversy? I'm not sure ejecting developers just because of controversy is honestly good stewardship.

replies(2): >>36216584 #>>36218505 #
freedomben ◴[06 Jun 23 17:53 UTC] No.36216584[source]▶
Right. More details needed to know if this is good stewardship (ejecting two toxic individuals) or laziness (ejecting a villain and a hero to get rid of the "problem" easily). TikTok was using this method for a while by ejecting both bullies and victims, and it "solved" the problem but most people see the injustice there.

I'm not saying it was bad stewardship, I honestly don't know. I just agree that we shouldn't make a judgment without more information.

replies(3): >>36216964 #>>36218213 #>>36218398 #
csmpltn ◴[06 Jun 23 18:19 UTC] No.36216964[source]▶
> More details needed to know if this is good stewardship (ejecting two toxic individuals) or laziness (ejecting a villain and a hero to get rid of the "problem" easily).

Man, nobody has time for this shit. Leave the games and the drama for the social justice warriors and the furries. People building shit ain't got time for this - ejecting trouble makers is the right way to go regardless of which "side" they're on.

replies(3): >>36217227 #>>36218052 #>>36218144 #
wmf ◴[06 Jun 23 19:39 UTC] No.36218052[source]▶
And what do you do when every contributor to the project, including the founder, has been labeled a troublemaker?
replies(2): >>36218229 #>>36225614 #
csmpltn ◴[07 Jun 23 11:46 UTC] No.36225614[source]▶
I'm confused about the scenario you're describing here.

Look, my message is simple and clear: keep the politics and drama out of it. If you partake in politics and drama, you'll be ejected from the project. I don't have the time or the energy to police or play games with people. We're here to build things, not to partake in social activism or sling crap at each other over codes of conduct, pronouns, hair color or magic strings. If you're hurt - fork the project (as long as the license allows for it) and have fun playing somewhere else.

replies(1): >>36229180 #
1. wmf ◴[07 Jun 23 16:31 UTC] No.36229180[source]▶
The scenario is a mob of trolls attacking a contributor in bad faith. If you kick out the contributor, what's to stop the mob from picking off someone else?
replies(1): >>36238847 #
2. csmpltn ◴[08 Jun 23 08:29 UTC] No.36238847[source]▶
If a bunch of random strangers (external to the project) are "attacking" your project somewhere on the internet (for example, on Twitter) - just ignore them and move on with your day. They don't have any power over your project and their opinions don't matter. Go on with your life and continue building.

If a bunch of random strangers (external to the project) are messing with your tools and workflows (stirring things up in the issue tracker, creating drama and playing games with silly Pull Requests and comments) - lock down your tools such that they can only be used by trusted members of your team. Close down and remove all bullshit conversations without spending any further time or energy on any of it. Platforms like GitHub blur the lines between "a suite of productivity tools for software development" and "a social network" - so make sure to lock down and limit the "social networks" aspects whilst optimizing for the "software development productivity" aspect. Go on with your life and continue building.

If the "attacks" happens internally within the project (between two or more members of the team) - eject all parties involved because they're clearly not here to build stuff. Go on with your life and continue building.

Your goal should be to spend your energy on building and creating, and collaborating with like-minded people on building and creating. Not on policing, moderating, or playing games with people.