After the grok cli fisaco (uploading the full repo) I moved my different projects to seperate users, seperate sandbox around each harness (nono). Vm is of course even better but resources and easy of use start to be an issue
Definitely an approach worth exploring! I actually started to look into semi formal spec language like Quint because I wanted something more structured then prose, so I feel like this goes into the right direction.
I played with this extensively on hobby projects (music visualizer Wayland widget for example) and I like the idea. I like coming up with cool stuff and solutions.
The problem is I'm just not disciplined enough, it makes me lazy. The longer I uses it, the less code I read myself and just fire quick /implement loops and go do something else, thinking it should be straight forward.
As other have pointed out, AI still needs a lot of hand holding and there are a lot of necessary decisions to make that one usually only realizes while actually building it.
That looks awesome! Do you have any metrics on storage space and query/insert performance for large amounts of data? Building something that has couple of million rows.
We used to do that with device that where in difficult to reach places with harsh uptime requirement! Think industrial routers and protocol converters. I think it pays for itself very quickly. Sending someone for such a device can get expensive.
Only half a data point: I played around with it for a private project. It works but the documentation is far from good enough for production. I was even considering getting the book, but it's not out yet. In my humble opinion, normal documentation should be enough to understand a framework, otherwise you can't expect anyone beyond hobbyist and enthusiast to pick it up.
"Break out" is definitively part of the design goals, so I always felt like they put a hatch.
There seems to be the notion in a lot of comments that Stoicism is about acting against one's nature or surpressing ones emotions.
For me, on the other hand, it was very freeing to encounter Stoicism, because I felt like it was okay that I didn't feel or react as strongly as people around me expected me to.
An interesting side effect of that is one can use the grid frequency to coordinate emergency power response - individual nodes (batteries, peaker plants, etc.) can react directly to the frequency measurement with generation or load, thus stabilizing the grid. Too much energy is equally an issue. Usually it's called fast frequency response these days.
Interessting point with the tax right off. I asked my boss to donate to a open source software we used a lot in our dev department and he labeled it as license costs because donations aren't something he could argue for (big company tho).
The author says the learning curve is steep but it pays off at the end. Somehow I don't really see that claim well supported.
Don't get me wrong, I absolutely love the idea of managing my system declarative (aconfmgr gets me somewhat there). I replicate my system on an external SSD for on the go for example.
I hate a messy home but resigned myself to it. I come from a functional background, so the learning curve should be less steep for me.
But overall it always seems the amount of work and time for the result is not a reasonable tradeoff. Tried Nix as a package manager a few times, always stopped when simple things took immense amount of time (Emacs with broken fonts?). Have colleagues running NixOS, never heard an argument for it that wasn't half a straw man. Yeah other systems break and it sucks but fixing that takes less time than figuring out how to write your own packages in Nix.
Adding to that that I run around and install every second neat thing I see on HN, I struggle to see Nix as more than a Rubik's cube.
As I understand it, GrayJay is not free (as in they want to be paid, which is I think is reasonable). How does this work with something like AGPL?
I'm curious to hear more, because I'm in the process of evaluating licenses for a software I'm planning to build and sell. For me it's important that users can feel safe with running my code and build it themselves - and keep using the software if I'm no longer around to maintain it.
Looking forward to hearing your thoughts.
I used to work for a company that wanted zero downtime through Erlang's hot code reload feature. While it absolutely works, it requires immense effort and extra code to handle state upgrades and downgrades.
I'm surprised that universities have to consider dyslexic students. When I went to university, I was basically told to figure it out. "It's your problem after elementary school. nobody cares."
Side note: donations are kind of difficult in a cooperate environment. Once I request that the department donates a modest amount to an OS project. We had to call it a 'license fee' internally. Paying it fine - donating is not :)
Every few months there is a new breakthrough in energy storage. To this day none really materialized in the way these articles claim.
I work in that sector but am not an expert in the technology so make of that what you will.
Looks like a polished VC funded version of git annex. Not a bad thing, since annex is a bit clunky and unusable for people not using git.
I using git annex for a while for all my files (tracking and duplicating files to 2 laptops, external disk, cloud, server). Any one spots a major feature that spacedrive has more than git annex?
Could this be a replacement for git-annex?
I'm using git-annex for a while, but its slow and has some quirks.
I would love to use version control on my whole home dir and sync different computers with it.