- skrtskrt parentIf that's all the issues there are with the dataset, it is probably far and away the best dataset any researcher has ever used.
- Does RAMP or CURE offer any possibility of conditional writes with CRDTs? I have had these papers on my list to read for months, specifically wondering if it could be applied to Garage
https://dd.thekkedam.org/assets/documents/publications/Repor... http://www.bailis.org/papers/ramp-sigmod2014.pdf
- When I was there, DigitalOcean was writing a complete replacement for the Ceph S3 gateway because its performance under high concurrency was awful.
They just completely swapped out the whole service from the stack and wrote one in Go because of how much better the concurrency management was, and Ceph's team and codebase C++ was too resistant to change.
- I would say if you're going to charge a pretty penny for the box, you have to make it ridiculously seamless to run every app the way a user wants, without issue.
TrueNAS sort of half-accomplishes this but as soon as you have to start configuring Redis and Postgres parameters to install Immich or understanding how to set permission on every layer of the filesystem so you can SMB share, the idea of a normal person being able to do this goes completely out the window.
My advice is to go ahead and just open-source everything. You won't on being closed-source anyway. You'll win on the experience for nontechnical users (or tehcnical users that don't want to spend time fiddling). You'll stomp out these complaints on Reddit and HackerNews so people don't get a bunch of negative comments when they google your company.
- Kagi's Orion browser is 1.0 on Mac and working on the first full Linux release - it's built on WebKit. That WebKit is a "third party" dependency but it's still a break from the browser monoculture and it doesn't seem like Mozilla has as much interest in pushing the browser engine space forward after pulling back from Servo.
- > The latter is what my Copilot suggested when I addressed complaints about higher gas prices
I would suspect this is because it is most mainstream recommendation from economists on how to disincentivize fossil usage without destroying your society & economic stability in the interim. Not because it's "lefty".
The yellow vest protests in France were basically what happens when you try to do A without also doing B.
- Well it only needs to be Kafka-compatible, so personally I hope that things like RedPanda will turn out to be easier to run for this use case than actual Kafka.
Having an S3-compatible store was already a fairly heavy dependency in terms of something to run correctly in production, it's just that most people don't even consider running their own object store at any real scale, they just go to cloud. Whereas running your own Kafka is something more platform teams are already attempting.
- The world of Auth has been made miserable with everything having to support OAuth2/LDAP/SSO/SAML etc., plus a million versions of access control, session configs, yadda yadda. Each of these has their own (usually legitimate) purpose, but also each one has to integrate with other providers that each don't follow and/or extend the spec in their own special way. And the pain goes on and on.
Obviously you can make a product that only does really good username/password auth for example, but there's always more pressure to implement more things for another use case.
- I think this blunkiness is in part because these things are often created and designed exclusively by frontend and full stack developers. IMO systems like these need strong backend developer influence, with highly scalable data models and and as much work as possible pushed server-side.
In short, the system should be designed by people that despise the general state frontend development. It should still look good, I love a modern clean frontend (like Docmost for example), but not at the expense of snappiness and scalability.
- Here come the HN comments from people that work at closed source companies or companies that profit off the free labor of open source devs, wailing and gnashing their teeth that it's not the purest form of open source blessed by Stallman himself and therefore is radioactive and doomed to fail.
- It's also a political tool.
About a year ago when the NYTimes wrote an article called liked "Who really gets to declare if there is famine in Gaza?", the conclusions of the article were that "well boy it sure is complicated but Gaza is not officially in famine". I found the conclusion and wording suspect.
I went looking to see if they would like to the actual UN and World Food Program reports. The official conclusions were that significant portions of Gaza were already officially in famine, but that not all of Gaza was. The rest of Gaza was just one or two levels below famine, but those levels are called like "Food Emergency" or whatever.
Essentially those lower levels were what any lay person would probably call a famine, but the Times did not mention the other levels or that parts were in the famine level - just that "Gaza is not in famine".
To get to the actual report took 5 or 6 hard-to-find backlinks through other NYTimes articles. Each article loaded with further NYTimes links making it unlikely you'd ever find the real one.
- AI is solid for kicking off learning a language or framework you've never touched before.
But in my day to day I'm just writing pure Go, highly concurrent and performance-sensitive distributed systems, and AI is just so wrong on everything that actually matters that I have stopped using it.
- Interestingly I noticed in a bunch of places in Europe, TripAdvisor was much better just due to higher usage / more data than Google. TripAdvisor's UI is pretty clunky but the network effect of just having enough people using it in a given place seems to be by far the most important.