@pony - makes my computer slow if I open 20 tabs of it - has some stupid limit on temporal resolution - some other edge cases I forgot about - in principle, I don't like when there is only one piece of software doing a $thing
@izaya tbh I don't know which is worse: - Mozilla being arrogant and thinking it knows what's best better than the user - Mozilla forgetting they have a customization framework and adding a hardcoded $thing, where every other $thing that already existed in the browser was user-configurable
@pj@kline@lanodan@nytpu tbh I think an sh replacement doesn't need to be a good interactive shell - we have plenty of those.
And in that area, there's execline[1] and while it has some good primitives for manipulating process state, I don't think it'd be a good fit for more high-level uses of shell.
@lanodan@pj@kline@nytpu also, tools to sync mirrors probably aren't as widely used as the distro itself, so I'd say it's fine if they have more dependencies (that are also packaged by the distro)
@pj@kline@lanodan@nytpu default shell soesn't matter, all that matters is that it's installed everywhere and has a consistent path. If you have a one #!/usr/bin/perl script in a #!/bin/sh world thay would work fine.
Question is, do your scripts that mostly invoke other programs become more maintainable and less error-prone after you rewrite them in Perl
@mikoto - irc - phpBB - Thinkpad Power Bridge - T9 keyboards - small phones - dual GPU rendering - 5.25" bays - data-dense UI - netbooks - laptop docks that connect from the bottom, with a very large and springy release button
@ignaloidas hmm what do you mean devops side / what is your current role?
IME, anything from "make Jenkins notify people that their docker image is built" to "develop a way to shrink persistent volumes on k8s" to "automate removing permissions in 15 different systems when offboarding an employee" can be done with python and shell (and a bit of groovy in case of Jenkins).
And while many of the tools I use are written in golang, I rarely have to write any golang code.
I was wondering why the colder a CPU is, the further you can overclock it...
And by colder I don't mean more watts of heat taken away from it at the same die temperature, I mean lower temperature at the same heat flow.
Well, one of the limiting factors of overclocking is square signal becoming insufficiently square. That's because of stray capacitance. But a capacitor alone can't round the edges of a square signal - it needs some resistance on where the signal is coming from.
Idk how stray capacitance reacts to temperature. But if it's anything like ceramic capacitors, it should have more capacitance when it's cold, right? So that can't be it.
And what about resistance?
Well, semiconductors have higher resistance when they're cold, and lower when they're hot, right? So that shouldn't help either.
But! the silicon is only a small part of the chip. The rest is wires. Layers upon layers of tiny metal wires. And in metals, resistance increases with temperature.
So my guess is that the reason overclocking benefits from sub-ambient temperatures is that the metal wires in the CPU have less resistance when they're cold.
> When you're throwing a workload at it, you can go to, say, -160C, but when you reboot, there's no more workload, all of a sudden you can't boot anymore. Then you have to increase to -140C to boot."