ris

17 ms·

91.
by ris 3y ago
There is no "just" about it. The absolute key takeaway is in "what we learned": > We chose to use DMS because it was well supported by the GOV.UK PaaS and we could also get support from AWS. If we were doing a Postgre
92.
by ris 3y ago
GOV.UK PaaS also runs on AWS (for as long as it remains to exist)
93.
by ris 3y ago
> This has already been done, but never upstreamed Assume you're referring to hqemu http://csl.iis.sinica.edu.tw/hqemu/ > Adding an on-disk cache would also be quite useful. +100
94.
by ris 3y ago
Packages that make it into nixpkgs (and are not ignored by Hydra because e.g. they're non-free) get copies of their fetched sources included in the nixpkgs binary cache. So they're there for "posterity" (there's no
95.
by ris 3y ago
If you're getting into the territory of Global Optimization algorithms like SA it can be helpful to implement your problem generically enough that it can be plugged into a general purpose optimization package like pagmo2, where you can
96.
by ris 3y ago
> Don’t want to use your phone? Use a hardware key instead. Don’t want to use a hardware key? Use an open source solution like Bitwarden (and it’s not the only one). You're ignoring the fact that WebAuthn can require attestation, wh
97.
by ris 3y ago
Dear map widgets in 2023, Stop asking me for WebGL, I will not give it to you.
98.
by ris 3y ago
Indeed, I'd be much happier donating through e.g. opencollective.
99.
by ris 3y ago
> You can run Haiku today, so it's hardly unfalsifiable Excellent, so let's falsify it: how come 20 years later the best thing people really have to say about BeOS/Haiku is that is has smooth window dragging? > multi-us
100.
by ris 3y ago
> After 25 years, GTK joins the party … I mean.. shall we start a list of ways in which BeOS/Haiku have yet to "join the party" that the linux desktop has managed? Juggling the various needs of one hell of a lot more users
101.
by ris 3y ago
There must be a name for the logical fallacy I see whenever someone pines over a past "clearly superior" technology that wasn't adopted or had its project cancelled, but I can never grasp it. I guess the closest thing to it i
102.
by ris 3y ago
Thinking, or even knowing you're right isn't sufficient grounds for concocting fraudulent ways of proving it. This approach runs the risk of blowing up in your face if discovered.
103.
by ris 3y ago
> The speed of deployment cant be beat. The sound of someone who hasn't used Nix.
104.
by ris 3y ago
That's what I was thinking - most bookmarklets I ever wrote one by one stopped working and I got tired of fixing them.
105.
by ris 3y ago
One of the main reasons I'm uneasy about cloud databases is the sheer absurdity of trying to meaningfully compare offerings and their value for money.
106.
by ris 3y ago
> Have Terraform plug into your Git history, take the Terraform code from the previous commit, and use that to calculate the old tree This is much much more difficult than it sounds if you want to be able to handle any amount of refactor
107.
by ris 3y ago
I don't understand the author's argument (if there is one) - pytorch has existed for ages. AMD's Instinct MI* range has existed for years now. If these are the key ingredients why has it not already happened?
108.
by ris 3y ago
This does look awesome, though I think I'd need a lot of trust in it before I went down this route. It seems to take a pretty drastic approach and it's unclear how complex a schema it would be able to handle. e.g. how well would
109.
by ris 3y ago
> For example the old app can keep writing data with the old schema, whereas the new version makes assumptions based on the new schema To do safe migrations it's a good idea to avoid rolling out versions that start making assumption
110.
by ris 3y ago
> It is worth the cost of slower introduction of new materials to take the time to ensure that those materials are safe. Perspective time. Global life expectancy is higher than it has ever been at any point in history and many of these m
111.
by ris 3y ago
> If I have a distributed microservice architecture and I want to keep multiple datastores in synchronization or "consistent" what's the industry best practice? Not to use a distributed microservice architecture.
112.
by ris 3y ago
Transaction-scoped advisory locks are very much a thing too.
113.
by ris 3y ago
https://github.com/pipelinedb/pipelinedb
114.
by ris 3y ago
The single thing that I most detest about GitHub Actions is how they, by design, completely miss the point of containers. Having "actions" that are just "install language foo" is barely better than just publishing shell
115.
by ris 3y ago
That's extremely vague. The CVE database is a spectacularly terrible thing to use to try and assess comparative "security" because there are so so many things social, organizational and cultural that affect whether and how an
116.
by ris 3y ago
Ditto aiven.
117.
by ris 3y ago
AI hysteria is is going to get worse before it gets better.
118.
by ris 3y ago
I think the fundamental mistake of nginx's configuration syntax was always making it look much more flexible and general than it actually is . Particularly with statements like `if` almost giving it the flavour of a general purpose pr
119.
by ris 3y ago
> Likewise practicing YAGNI This is why I have come to hate YAGNI. Nowadays when it's said what I hear is "I don't understand why I need it (yet)".
120.
by ris 3y ago
I've been both ways on this, and ultimately I come down heavily in the camp of using ORMs for as far as it makes sense. Why? Sure, the "just use SQL because it's so simple" crowd use seductively simple examples, and inde

More ›