So I opened this article to find out at the very beginning, that author put's a lot of money to AI providers... So probably also used it to write this article. So, according to the rule "text which is not worth of spending time on writing is also no worth of reading" I closed it.
I found out that the author of a blog post paid a maid to clean their house, and sends their laundry out. Therefore, the blog post was written by the maid, or one of the laundromat employees. So I closed it.
That's a false equivalence. You might read a blog post about engineering from someone who paid a maid to clean their house, and sends their laundry out.
But would you read their blog post on laundry tips?
No - it's just as easy for you to send out your own laundry.
Err, no, the equivalent would be if the author had written an article about laundry, and how important it is to pay attention to all the details... then you realize the photo of his laundry still has a tag on it from the laundromat.
That's how it has to work. To increase capacity you have to make smaller cells where charge may easier diffuse from one cell to another. Also to make drive faster, stored charge has to be smaller, which also decrease endurance. With SLC and QLC comparison is even worse as QLC is basically clever hack to store 4 times more data in the same number physical cells - it's tradeoff.
Yes, but that tradeoff comes with a hidden cost: complexity!
I much rather have 64GB of SLC at 100K WpB than 4TB of MLC at less than 10K WpB.
The spread functions that move bits around to even the writes or caches will also fail.
The best compromise is of course to use both kinds for different purposes: SLC for small main OS (that will inevitably have logs and other writes) and MLC for slowly changing large data like a user database or files.
The problem is now you cannot choose because the factories/machines that make SLC are all gone.
I'm using Linux on some dell precision and camera just don't work. It's possible to install some custom kernel to make it work, but the pain of maintaining it by myself in comparison to IT department supported setup is a no go.
Sometimes it's rather matter of sanity than time management. I once created systemd service which goes to company web page and downloads some files which I sometimes need. This script was pretty hacky, and writing it took me a lot of time - probably more than clicking manually on this page in the long run. But clicking it so annoying, that I feel it was totally worth.
That's cool, except that NAND memories are horrible to hoard data. It has to be powered all the time as cells needs to be refreshed periodically and if you exceed threshold of like 80 percent of occupied storage you will get huge performance penalty due to internal memory organization.
An interesting parallel because there were undoubtedly some people who worried we would lose something important in the craft of instruction-level programming, and almost certainly we have in relative terms. But in absolute numbers I am confident we have more low-level programmers than we did before Fortran.
And if I were to jump into instruction-level programming today I would start by asking an LLM where to begin...
In most cases Yaml is bizarre kind of DSL with tricky way of API interaction. For instance - I don't understand why exactly the same Ansible API isn't just python library?
For the same reason any DSL exists: because the programming representation is a lot more verbose than the DSL, due to the computers not currently honoring the "you know what I meant" flag
#!/usr/bin/env python3
"""A made up example of the line noise"""
from ansible import *
def main():
hosts = ["localhost"]
for h in hosts:
run_one_host(h)
def run_one_host(inventory_hostname: str):
connection = ansible.builtin.ssh(inventory_hostname)
print("sniff out the machine's os")
host_vars = ansible.builtin.setup(gather_subset="os", connection)
if host_vars["distribution"] == "ubuntu":
dest = "/etc/apt"
else ...
dest = "/etc/something else"
print("do something awesome")
copy_ok = ansible.builtin.copy(src="./some_file", dest=dest, connection)
...
That said, I can't readily imagine why you couldn't do exactly what you said because the AnsibleModule[1] contract is JSON over stdin/stdout (and one can write Ansible modules in any programming language[2] - they just default to Python)
python (as much as I personally dislike the language itself) has clean syntax for sets, dicts and arrays. Which are the data structures you use in a playbook. Ansible as python instead of yaml can be made to look very similar to current playbooks. But saner. And easier to script.
reply