383 karma · joined January 4, 2012
I have a old WD small one that's kinda faulty (plugged it in then put it down heavily, it's not been right since), I should pop it open just to see what's inside, but it's older than the USBC models so could easily have changed. In any case, I don't think AI is eating the stock of slow laptop HDDs, so I'm not sure there's any need to buy these just for shucking.
As for Slides, it's pure junk compared to the Keynote, but iCloud has it's own problems so I use this offline-only.
With the web version of Word 365 or whatever it's called, we've had so many problems syncing with OneDrive and sharing and whether it's showing the right version of the document that I'd be happy to never see it again, but their foothold in education means I'm forced to deal with it and provide technical support.
I use Google Chat, only because my clients use it. Network effects matter. Personally I think it's terrible, but I wasn't a fan of Slack either but I'm not entirely sure why as it's pretty much just sending text. Maybe the opportunity to innovate in this space is UI/UX, and performance/reliability (Signal has been slow/flaky recently for us).
It also looks like the PDF in the repo is just the first 20 pages, it would be worthwhile scanning the whole thing cleanly and uploading to preserve this important work.
Trust it not to leak credentials? No, that's something that is never taken for granted.
Trust it to hold a full history of uploaded binaries? That depends on the value of the releases. For incubator work, or web projects, or even Appstore apps where it's released to those stores to manage, maybe there should be enough trust. I just wouldn't use it for code where I want access to many stable versions, and I wouldn't put it publicly on the web either - not that I would do so with Sonatype Nexus without vendor support and many safeguards. I think it'll earn trust over time, once folk are convinced to use it for real workloads.
There's a lot of forms of trust.
It doesn't use the 'unsafe' keyword anywhere, but that's not necessarily an indicator. Uses unsafe-libyaml which is like what it sounds (a hacky port of libyaml) but is no longer maintained (archived on GH in March 2024), and may have better choices. An SBOM would highlight these dependencies better than me doing random searches through the code.
I'm not sure I'd have put a default in the OIDC callback to localhost, that's about the only thing I've seen in a quick 5-minute skim through. I do like the comments and the lack of emojis :-)
I too would like to know the process, if OP is willing to share.
On the other hand, it also shows that it took three weeks, so why should I use this instead of building a custom toolchain myself that is optimised for what I need and actually use? Trimming away the 45+ formats to the 5 or so that matter to my project. It raises the question - is 'enterprise' software doomed in favour of a proliferation of custom built services where everybody has something unique, or is the real value in the 'support' packages and SLAs? Will devs adopt this and put 'Artifact Keeper' on their CV, or will they put 'built an artifact toolchain with Claude'?
But then again, kudos to you for building something that can (and probably should) eat the lunch of the enterprise-grade tools that are simply unaffordable to small business, individual contractors, and underfunded teams. Truth be told, I'm not going to build my own, so this is certainly something I want to put in a sandbox and try out, and also this is inspirational and may finally convince me that I should give Claude a fair go if it's capable of being guided to create high quality output.
Joplin has a paid subscription sync service and is free and open source software.
It's a different business model, but it's possible.
As for Linux from Scratch - This is something that's been on my radar, but without the part I'm truly interested in (learning more about SysV) then I'm less inclined to bother. I don't buy the reason of Gnome/KDE - isn't LfS all about the basics of the distro than building a fully fledged system? If it's the foundation for the other courses, but it still feels weak that it's so guided by a future GUI requirement for systemd when it's talking about building web servers and the like in a 500Mb or less as the motivation.
For more control and to close that loophole, it could be possible to put annotations/comments in the code to `/* ignore this line */` in the same way that eslint does? Or have a config that lists how many uses in each file, instead of one-per-project?? There's always refinements, but I'm sure that for many projects the simplicity of one counter is more than enough, unless you have devious developers.
Alternatively they may be using AI in HR as part of the decision making, and it's made the determination that these folk can go "because of AI" based on past firings and performance since then.
The only thing that's caused any issue is power management, I'm fairly sure it's not optimal, but it's still better than Win11. That's purely down to lack of effort on my part, and basically setting it for max performance because it's not important to me for a desktop machine. Everything (and I mean everything - sound, video, wifi, bluetooth) else is 100% out of the box working on mid-range commodity hardware, albeit with excessive RAM for my needs. Some of it is a bit clumsy looking in places, but it did look weird on Windows too with some of the apps.
When I did have trouble, it was not like I could get support from Microsoft as the community forum is a joke, but with Linux at least I stand a fighting chance of working around any potential problems.
Is there anything on Windows I miss? No.
Is there anything on Mac that I miss? Yes, there's a few things that I like about MacOS (pre-glass) but I have a MacBook Air for those which is good for occasional use but not as a daily driver.