Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
tuldia
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
61.
▲
by
tuldia
7y ago
Duplication is far cheaper than the wrong abstraction. I do prefer to have lots of dumb files than having to deal with the cognitive load of a tool that in the end will generate lots of files anyways.
62.
▲
by
tuldia
7y ago
Sometimes there is no problem to be solved, all these tools just complicate everything. Do this instead: 1. Use flat yaml files. No loops nor conditionals, no complexity. 2. One (single) yaml file templated by ansible just for secret/s
63.
▲
by
tuldia
7y ago
PostgreSQL never ceases to amaze me. The great thing is that it is a mature tool and you don't need to bring another beast to the zoo.
64.
▲
by
tuldia
7y ago
I know. This was a social experiment. Thanks for your comment, I appreciate that! Both tools you mentioned are great and kinda relate to this experiment too. The existence of docker and how it was developed and absorved by people brought n
65.
▲
by
tuldia
7y ago
This is an example of "unpopular" post. As expected, it received no counter arguments.
66.
▲
by
tuldia
7y ago
> Without Docker everything new becomes a project on its own where you need to call in "ops" for the smallest of things. I hope that one day we will stop echoing that or framing it as a bad thing. It's always good to invol
67.
▲
by
tuldia
7y ago
> You don't infect the host with the toolchain's packages; you install the toolchain's packages in the toolchain chroot. Infect is a too strong word, because normally the cross compiler will coexist well with your system.
68.
▲
by
tuldia
7y ago
First you should not mix CentOS 5 packages into a CentOS 4 system. That is how you create a problem in the first place. Building software on top of frankenstein build environments is how you end with broken software, and should not be encou
69.
▲
by
tuldia
7y ago
> Most likely, custom installed libraries and tools (./configure; make; make install), that were never packaged. And a package manager, that can't even tell you if any of the installed files were changed, after they were instal
70.
▲
by
tuldia
7y ago
Excuse me but this is "crazy shit": ".. in 2009: nobody could remake our centos4 build machine for our C++ code ... so absolutely fucking cursed" What lead a computer running a supported operating system[1] in a sta
71.
▲
by
tuldia
7y ago
No, it just made something that existed 18 years ago become more popular. It's just a rootfs compressed tarball. Running on top of Linux technology. Docker was always a brittle tool with lots of limitations and huge compromisses. Want
72.
▲
by
tuldia
7y ago
https://en.wikipedia.org/wiki/Ubuntu#History
73.
▲
by
tuldia
7y ago
> It can (and does) take days for critical security updates to migrate from unstable to testing after stable has access to patched version. Now you are making way to many assumptions with this phrase. Do you really think that make sense
74.
▲
by
tuldia
7y ago
I guess you are exagerating quite a bit. Creating a Debian package is actually pretty straight forward: 1. download upstream tarball. 2. execute dh_make -f <path-to-tarball> 3. debuild -us -uc -b That is it! There is no secret. dh_mak
75.
▲
by
tuldia
7y ago
One can think of Debian testing as the "next-stable". How does it works? 1. Upstream release a new version, it goes to unstable. 2. Package is tested for some days in unstable and get promoted to testing. So telling that testing
76.
▲
by
tuldia
7y ago
Ubuntu is nothing more than the Debian "unstable" branch with Canonical branding plus non-free packages. Compare https://distrowatch.com/table.php?distribution=debian and https://distrowatch.com/ta
77.
▲
by
tuldia
7y ago
That is great! You are doing system administration now, enjoy! I believe people should be doing that more often, you know, just moving stuff around.