Thanks, this is exactly the content I come here for. Apt handle :P
I am very not comfortable with the situation, as a seller. I mailed out the stuff that was paid for before the outage...but I don't think I'm mailing anything else until I can disburse.
Yeah this sucks, I have a bunch of hobbyist orders stuck in limbo since last week -- customers have paid, but I can't pull the orders down even through the API.
I really like Tindie as a platform and have been using it since nearly the beginning...but I'd have lost the contract if I pulled this level of nonsense on a customer's production application.
Nothing wrong with Rails in 2026. We still use it for both internal and customer projects. I haven't yet encountered anything that made me feel like switching. I'm also not interested in changing frameworks just to have the New Hotness die in 2-5 years (our oldest currently maintained Rails project is over 10 years old, and some stuff I started working on when Rails 2 was new is still being maintained, just not by us)
I don't always play UT2K4, but when I do, it's usually with Ballistic Weapons mod + Sergeant Kelly's weapon packs. I agree that the UT2K4 weapons just don't quite do it like UT99.
Plus, learning PDP-11 ASM explains some of the idioms from C as they map directly onto the architecture! "Pointer to a pointer" is just a native addressing mode, for instance.
Remember, though, that in many places ignoring something can put you at risk for a default judgement at a later date. It'd be nice if we could just ignore troll trash :/
Huh, interesting. Never noticed. Might have something to do with pretty regularly using actual serial terminals. I don't know how the testing under Mac OS X affects it -- I only run it under Linux and OpenBSD, on OS X I just use the OS X terminal. Anyway, `st` does its job for me!
"Worst" for me is stuff that grabs keys it shouldn't, scrolling that doesn't work right with `screen` and/or `tmux`, etc.
Occasionally I end up with a truckload of gear from things like that. The circumstances that saved it from shredding are usually something like Founding Engineer X couldn't stand to see all that nice workstation stuff go in the trash so he kept it in his garage for 25 years and now his kids are selling it.
Same, I was around 1500 tabs across three windows when I finally moved from the HP Z420 workstation I'd been using as my primary sometime around JAN 2023. Machine was fine with it.
Yeah, totally possible to get excellent results with older hardware, and really stellar results with very new hardware, if you're running stuff that's not essentially made to be slow.
I basically only upgrade workstations due to web browsers needs, and occasionally because a really big KiCAD project brings a system to a crawl. At this point even automated test suite runtimes are more improved by fixing things that stop test parallelization from working efficiently vs. bigger hardware.
That was our main reason for scrutinizing AGPL libraries at $previous_job. IIRC our biggest concern was over iText (Java PDF library) and other libraries that depended on iText. In our case, we ended up not having to modify anything and were fine, but if we did have to modify, it'd have been to include trade secret features, which are a non-starter for distribution!
It's a nasty, complicated situation with bad actors on both sides.
Been saying this privately for a long time. Agree on "GPL is the best choice," as well. My personal experience with devs who don't want to GPL their code or contribute to GPL projects is that they're under the impression that having a permissive license on their own project will get $corp to use it and, somehow, they'll profit from $corp using it. Haven't personally seen it yet, but I have seen a bunch of permissive licensed stuff get pulled into bigger projects and changes never contributed back.
I am very not comfortable with the situation, as a seller. I mailed out the stuff that was paid for before the outage...but I don't think I'm mailing anything else until I can disburse.