896 karma · joined December 4, 2015
If you do a vanilla FreeBSD+samba+NFS+ZFS setup, you'll need to edit several files around the file system, which are easy to forget months down the line in case of adjustment or disaster recovery.
Additionally, Google and the PSL have inadvertently broken .home.arpa on Chrome by misclassifying it as a public suffix, while leaving .internal alone. A wildcard cert for *.home.arpa will not work on Chrome, but *.internal will, despite these two domains being essentially equivalent in purpose.
Using the eqn and troff suite in 2025 ... I'll just say there's a better way. LaTeX is arcane enough, but at least it is a universal standard in mathematical publication that it pays off to learn a little.
The maintenance window will morph into a do-big-risky-changes window, which means everybody in engineering will have to be on-call. Many years ago, when I newly joined a FAANG, I asked, "shouldn't I run this migration after hours when load is low?" and the response was firm, "No, you'll run it when people are around to fix things". It may not always be the answer, but in general, I want to do maintenance when people are present and willing to respond, not nights and weekends when they're somewhere else and can't be found.
A lot of applications are usually tolerant of suboptimal compensator design. I've participated in a few designs where these circuits were plucked from the datasheet reference design and never touched. There's a tradeoff between having a little bit of ringing vs. having an engineer model, tune, and test, and also adding to the BOM complexity with a bunch of different passive part values.
True, but the USG has a long memory and holds grudges. Even if they never travel, they have to be confident every future government of the country will have their back. What's the odds the North Korean or Russian regime substantially changes in their lifetimes? Probably higher than the chance a future US administration will stop caring about an outstanding warrant.
Your timeline is off by at least half a decade, and things were changing very rapidly in that time. By the mid-'90s, NSFNET was formally dead, after years of accepting commercial traffic. Local ISPs for home users started popping up and AOL opened its access to USENET in 1993.
The push for residential broadband also started almost immediately; @Home was offering residential cable internet in 1996, it was the future at the time, just not very evenly distributed. This was well before PCs had the processing power to do standard-definition video.
It's a problem if you're building systems as a dilettante. There are enough individuals on the planet that people can specialize so we need not be at the mercy of systems built by people of average discernment.
> If their art dies out, maybe nobody will know how bad all the pianos are. And then we'll all have slightly worse pianos than we would otherwise have. And I mean if that's the way things are going to go, then let's just steer the Earth into the Sun, because what's the point of any of this.
One counterexample to this viewpoint is Damascus steel. The exact art of making it has been lost (although now effectively reproduced), but modern steels surpass the qualities that made Damascus steel prized. It turns out those ancient masters didn't know bad their steel was. Maybe modern piano tuners don't know how bad their technique is, once the process of "finessing how the overtones interact with each other" has been thoroughly characterized by present or future technology.
Not a true top-line overall number, but the trend is obvious notwithstanding.
The first time I saw a PCB business card, I thought it was pretty cool. Then I saw a PCBA business card (with components!) and was amazed. But now I just see them as unnecessary e-waste for vanity. Business cards get read, scanned, and tossed. At least the impact of a piece of paper and ink is small compared to fiberglass resin, copper foil, ENIG, and solder mask. This example isn't even that great as a business card: the typography and contrast make the contact information poorly legible compared to the component silkscreen. Amazing PCB art (https://grandideastudio.com/portfolio/projects/the-worlds-th... is the best I've seen) makes creative use of the different contrast, translucency, and textures between exposed and masked copper, masked and unmasked bare FR4, and silkscreen layers. It's a very constrained graphic design problem that takes a good eye.
[1] https://www.penpapernomographic.com/pdf/smith-chart.pdf
[2] https://github.com/pgf-tikz/pgf/issues/817
[3] https://camo.githubusercontent.com/0cc44db2e367356629d897c10...
10x that amount and maybe you can start thinking about tape.
It's like saying Google and Facebook are at a business (dis)advantage over the merits of Tensorflow and PyTorch, when their actual business is something completely different.
LTspice (sponsored by Analog Devices) is closed-source. The recently-released QSpice (sponsored by Qorvo) also closed-source. QucsStudio was taken closed-source by Qucs' original author, and he's not commented on his intentions in this decision.
Big companies typically open-source software when it's not part of their strategic business value, and offers community engagement benefits and good press. LTspice is kind of an advertisement for AD's chips. AD and Qorvo aren't remotely in the software and EDA business, so their decision to keep them closed is even more puzzling, but I guess the instinct of hardware companies is guard everything.
The event where some kid of humble origin connects with a kid of the Social Register crowd and forms a lifelong bond comes from mostly odd chance, and it tends to recedes after the initial mix of roommates and floormates are assigned. Social circles gel and people start sorting themselves almost right away.