Some of the most interesting projects here have the worst installation stories.It's sort of tilting at windmills to not acknowledge that people are going to mostly install through package managers for their platform by advertising it as such. I'm not suggesting there's anything wrong with building from source. On the contrary, I think it's fantastic as many targets are supported here as there are! I think it's a shame more people aren't discovering them is all.
Rust, following Go's footsteps, has made it very easy to distribute-and-compile from source. They've taken all the pain out of the compiling-from-source pipeline, through "go build" or "cargo build"
Meanwhile, distributions sometimes maintain their plodding rate at package updates (usually handled by distribution volunteers, not the original program's developers), which was developed in an era when building from source was a tedious process where the distribution volunteers provided value.
In effect, build-from-source has taken over "just use the distribution package".
The reason I was put off by Rust was compiling from source. I experimented with a ports collection package management system similar to those used in BSD a while ago, and every time a Rust program needed to be compiled, I could go to sleep; no, basically rendering the system unusable. It was like the dependency abyss of NPM combined with the worst possible compile times, even worse than C++.
Even worse than C++? That has never been my experience. I maintain C++ projects that take hours to build from scratch. Most Rust projects I install, even the very big ones, are ~3-5min max.
Are you building in release or debug? Do you have lto enabled? Rust compile time is absolutely worse than c++, and I'm not sure many in the community would disagree. You need to aggressively split large crates up to make it sane. A lot of this comes down to the fact the crate is the compilation unit rather than individual files.
Okay, but where do you put it? I mean, yes, I know there's /usr/local/bin and /opt/bin, but why do I have to compile then mv it myself? It's a small paper cut. Does cargo or go have a global build command? That would be a nice all-in-one. And why should I have to download the source code if, honestly, I don't care as long as it works? Nah, I don't think build from source has taken over at all. It's 2025 and I use a package manager (or three) on every major operating system across multiple languages. It's because, as a vendor experience, I can one-line and use just about anything.
The reason for the rate of updates is isially for one reason: Trust and Stability. Instead of trusting a myriad people all over the world to do their job well, I trust one team to ensure that all the tools I need do run well.
And in the Unix world, build from source can be pretty easy. When it’s hard, it’s usually the project’s fault (Firefox, Electron,..).
gTLDs have no registration/renewal price cap. This probably doesn't mean much to you now, and statistically, it probably never will, but if it ever does... Yikes!
The best part of this is I watched Sam Altman say he really thinks fusion is a short period of time away in response to a question about energy consumption a couple years ago. That was the moment I knew he's a quack.
Not to be anti YC on their forum, but the VC business model is all about splashing cash on a wide variety of junk that will mostly be worthless, hyping it to the max, and hoping one or two is like amazon or facebook. He's not an engineer, he's like Steve Jobs without the good parts.
Altman recently said, in response to a question about the prospect of half of entry-level white-collar jobs being replaced by "AI" and college graduates being put out of work by it:
> “I mean in 2035, that, like, graduating college student, if they still go to college at all, could very well be, like, leaving on a mission to explore the solar system on a spaceship in some completely new, exciting, super well-paid, super interesting job, and feeling so bad for you and I that, like, we had to do this kind of, like,
really boring old kind of work and everything is just better."
Which should be reassuring to anyone having trouble finding an entry-level job as an illustrator or copywriter or programmer or whatever.
Fusion is 8 light-minutes away. The connection gets blocked often, so methods to buffer power for those periods are critical, but they're getting better so it's gotten a lot more practical to use remote fusion power at large scales. It seems likely that the power buffering problem is easier to solve than the local fusion problem, so more development goes to improving remote fusion power than local.
Sam is an investor in a fusion startup. In any case, how long it takes us to get to working fusion is proportional to the amount of funding it recieves. I'm hopeful that increased energy needs will spur more investment into it.
It is really weird how some sessions with claude are better than others despite similar tasks. I'm certain it's not sleep deprivation or something else. Sometimes it gets on a hot streak by accidentally discovering the right tools to use. It's like an unstable solder joint or something. It's very difficult to guide it. When you do it overfits hard.
The model only works because of the subject matter filtering 99% of potential users. One good moderator can’t possibly scale to a network the size of Reddit.
Isn't dang a paid employee? If so, incentives are different. Its a day job that he could get fired from if he deviates from his main duties. (dang you are pretty decent don't get fired please).
Heh, according to the other guy he could get fired and replaced with AI because of his ego. For the less than subtle, I wasn't implying that it was good or bad. I was just pointing out the irony of criticizing centralized moderation on a site with centralized moderation.
As for whether or not pay makes a difference, I think you probably have a point, but I'm sure there's still wiggle room there.
Agreed, but just so no one latches onto what I think you meant as a joke, the overwhelming majority of homeless people in California are native Californians.
I didn't bother to cite my sources at the time, and it seems that was a mistake. I used careless language. The overwhelming majority are Californians, at least as much as I have any right to claim to be. They lived in California for a significant enough period of time that they didn't necessarily intend to just become homeless. However, you're correct that a simple majority, not the vast majority, are native Californians.
> People experiencing homelessness in California are Californians. Nine out of ten participants lost their last housing in California; 75% of participants lived in the same county as their last housing (Benioff Homelessness and Housing Initiative - UCSF, page 5, June 2023)[0].
> Two-thirds (66%) were born in California[0].
> Where were you living at the time you became most recently became homeless?[1]
85.39% answered Santa Clara county in a survey conducted on homelessness in Santa Clara county conducted by the county government around the same time. 54.12% of those answered that they'd lived in Santa Clara county for more than ten years, with the next largest percentage, 21.26%, having lived there for 1-4 years.
Moreover some images SHOULD NOT have alt text or at least shouldn't have their associated alt text displayed in all contexts. I put this in all caps because this is a pervasive and common myth. Granted, all images on Bluesky probably should have alt text because ostensibly an image as part of a post is probably content. However, in cases where an image is purely decorative and not meaningfully relevant to the page, a blind or low-vision person doesn't need to, nor do they want to, hear your weird interpretation of some abstract art. If you disagree, take it up with W3C. This isn't just my opinion.
