tazjin

69 ms·

751.
by tazjin 7y ago
Nixery ;-)
752.
by tazjin 7y ago
Next up: Beanbag chairs become problematic and Silicon Valley implodes.
753.
by tazjin 7y ago
This seems unsurprising to me. Presumably the language he designed fits his way of thinking, and he uses it to express his thoughts. As long as you still understand it he succeeded in using it to communicate, and with some people that'
754.
by tazjin 7y ago
Yes, you can do that using for example `buildLayeredImage`: { pkgs ? import <nixpkgs> {} }: with pkgs; dockerTools.buildLayeredImage { name = "curl-bash"; contents = [ curl bashInteractive coreutils ]; }
755.
by tazjin 7y ago
That's actually something I've been discussing with a colleague - Nix is capable of building various other image types (netboot, qemu, etc.) and we could theoretically extend Nixery to provide such images in addition.
756.
by tazjin 7y ago
This is now fixed - the issue was basically that image manifests and config layers contain the image name, so if the name changes those layers will be replaced. The solution is to sort the packages in the name and return identical manifests
757.
by tazjin 7y ago
Quick note on the layers: The current layering strategy of the public instance is not the one linked to in the README (edit: fixed), it is the one described in this document: https://storage.googleapis.com/nixdoc/nixery
758.
by tazjin 7y ago
Currently when running a private Nixery instance you can actually specify a full git commit hash for the Nix repository that you're using. If this repository is the upstream nixpkgs[1], or if your private repository follows the same ru
759.
by tazjin 7y ago
(Author here) The actual content layers (i.e. those containing Nix store paths) are going to be the same, but metadata layers (those containing the image name and the references to all layers) are currently going to be cache-busted. I'
760.
by tazjin 7y ago
There's another clear distinction: Telegram has proper native clients and an open protocol.
761.
by tazjin 7y ago
> Although Kubernetes requires 3 to start It doesn't actually, and if you're running on GKE then the master is a managed service - you can have a single-node cluster (I do this occasionally for testing). Said startup might want
762.
by tazjin 7y ago
My experience with shipping companies (no matter which one, and in 4 different countries) is that they generally don't manage to deliver a large fraction of packages. The failure rate must be above 20%, which would be unacceptable for
763.
by tazjin 7y ago
It was also recently reversed by Google for the Pixel 3a. I'm hoping other manufacturers follow suit. It's fine to admit a mistake and many have been made in phone design recently.
764.
by tazjin 7y ago
If "the market has spoken", it seems like its words were dictated by the manufacturers. As a consumer I don't remember even being given the option of buying any small phones (besides the now discontinued iPhone SE) for the
765.
by tazjin 7y ago
> Apparently the smaller-handed have given up on single-handed use several phone generations ago, so they have nothing to lose from even bigger phones. Yes, we do - RSI issues on the medical front and at some point you also simply excee
766.
by tazjin 7y ago
It's interesting to see it go down. There's some chaos involved, but from my perspective it's the constructive[0] kind. If you're interested in how these sorts of incidents are managed, check out the SRE Book[1] - it has
767.
by tazjin 8y ago
The blog post says "We are evaluating products, not protocols". There are no XMPP frontends that can compete with the "shininess" of the modern, proprietary systems like Slack so that's out already. As for Matrix&#x
768.
by tazjin 8y ago
> What's the rationale for not including capitals? London's infrastructure is not really comparable to other cities in the UK, so it skews the image for the point that the authors are trying to make.
769.
by tazjin 8y ago
There are no other phones that can compete with the SE on size and specs, unfortunately. Companies stopped making reasonably sized phones long ago.
770.
by tazjin 8y ago
My experience with Tumblr was generally that a large part of the content, especially larger media content like videos, failed to load most of the time. Makes me wonder if that's related ...
771.
by tazjin 8y ago
As someone who's used EXWM exclusively for over a year: Getting it up and running is very quick, finding the workflow you want can take a while - it depends on how familiar you already are with Emacs. For example you might initially ke
772.
by tazjin 8y ago
Makes me wonder if "smart" speakers generally are legally dubious in two-party-consent areas ...
773.
by tazjin 8y ago
Phone Arena has a good page for phone size comparisons: https://www.phonearena.com/phones/size#/phones/size/Apple-iP...
774.
by tazjin 8y ago
For me, it's the size and headphone jack. Android vs. iOS doesn't matter much, but Apple was the only company still offering a phone that fits my two criteria. Now I have 3 SEs (one with a broken screen that I'll get fixed, o
775.
by tazjin 8y ago
The thing is that for the more niche kink communities on Tumblr the fact that everyone was using it was what made them work. You will never get that kind of activity on a Tor service. If you look at the more obscure, older fetish-related ne
776.
by tazjin 8y ago
By the time they're old enough to purchase things online they probably won't be using Tumblr anymore ...
777.
by tazjin 8y ago
The old website is still online: https://www.rust-lang.org/ The new one is just hosted on a preview subdomain to gather feedback, from what I understand.
778.
by tazjin 8y ago
As a Haskell & Erlang person who currently uses Rust as my primary language at work: > do you do functional programming, and is Rust a better (with all the subjectivity that word implies) language than Go? Yes, yes. Obviously the Rus
779.
by tazjin 8y ago
Who knows what kinds of things are flying through "their" systems? Maybe this thing is the most not suspicious object they could imagine ;-)
780.
by tazjin 8y ago
Great post on the issues of Docker's linear layering method (which a tweet[1] by the author of the post also explains well independently of computers) and how to improve on it with Nix. The "old" way of building Docker images

More ›