There's a guy complaining that the creator is poisoning the collective code used to train LLMs. If that's all it takes we have a moral responsibility to flood GitHub with garbage.
I run a SVN server for my personal projects, home lab and home automation stuff.
I noticed that the SVN CLI workflow is a bit dated and I think there's room to create a graphite like experience for svn, especially focusing on stacking.
I am set out to:
- create a modern CLI to interact with SVN
- create a subsystem to run alongside the svn repo (similar to gitaly)
- create a good looking web UI to browser the repo, review code reviews, etc
I am creating a webapp to let screenwriters collaborate when writing their scripts.
I have several friends in this industry and their tooling is either expensive, not localized for their market or straight away bad (I've seen terrible dataloss).
I got some inspiration from linear and am building it on top of ruby on rails with CRDTs.
Scriptwriting require specific formatting (set by Hollywood ages ago). Doing this in google docs is really painful. Besides that, people who work in this industry are already used to the format, so if you wanna pitch something to studios, they expect to be in industry format.
if coding a webapp, I use full stack ruby on rails (hotwire/turbo/javascript with importmaps).
System stuff go/pyhon. I haven't had time to learn either Rust or Zig, but I think Golang is good enough for now.
I have a lot of java experience, but to be honest the opensource toolchain outside big tech is too much of a pain to use (say gradle or mvn). I believe SBT is quite good but learning scalla goes into the bucket alongside rust and zig.
2400 requests is somewhat decent. Having seen companies like amazon, where their website backend can only handle a few hundred RPS per box, 2400 ain't that bad.
Is your post related to a political stance against Elon musk, a distrust call against putting AI on a privacy first app or you don't like AI chat bots?
It's very hard to understand what's it you want people to get out of the blog post since it's just "don't use x, use y" and usually people rather get some reasoning rather than being herded to do what you want
Not my blog post, not my report, but my reading of it, and the reason I posted a link here to it, is that it raises a concern about integrating a privacy invading technology with a messaging system.
Everyday we stray further from the simplicity god.
reply