I use ZFS on my laptops and desktop but kind of considered Btrfs for this new NAS. What made me decide to use ZFS instead is that Btrfs does not have [yet] transparent encryption, I'd need to use dm-crypt/LUKS. ZFS has that natively, so :shrug: When transparent encryption lands on Btrfs, I may consider it for new machines (or Bcachefs if it gets back in the Linux Kernel).
> Also, has anyone though of how mind-numbingly wasteful solar fusion is? All that energy, and only a tiny fraction makes it to Earth with the rest getting dumped wastefully into space. Seems like an area that's ripe for disruption by a startup.
That energy can be captured by a Dyson sphere:
> A Dyson sphere is a hypothetical megastructure that encompasses a star and captures a large percentage of its solar power output
Is this a bad thing? Investing a lot into safety measures to avoid catastrophes seems better than investing significantly less because we assume is safe.
Could you elaborate on why this investment is an argument against nuclear?
I once talked to people that worked at Angra Nuclear Power Plant in Brazil and they said the real danger is actually the spent nuclear fuel. The power plant itself is safe due to many redundant safety measures, continuous tests and monitoring. I don't have a source for this, and don't take my words for absolute truth, I'm not an expert in the subject.
> kept from harming us by a large crew of skilled people
I'm glad to hear people working with nuclear are skilled ;) I assume people working in solar/wind/hydro are also skilled at their craft. And I'm sure you didn't imply that, maybe the phrasing wasn't the best?
Brazil abolished daytime change a couple of years ago. Our time is the same all year, no more +1 and then -1 hour.
It was mess on the day there should a change, many people arrived on their appointments one hour before or later. Many automatic systems changed their time, different clocks at home reported different hours.
This chaos lasted one morning. After some time, nobody now complains about not having it. Many people don't remember about the change anymore. The only people that complains about daylight change are the ones that work with people from countries that have that.
Abolishing daytime change is not the same as adopting an "universal" (country-like?) timezone, but shows that it is _possible_ to do on a "big country spanning a lot of latitude as well as longitude and tens of millions on wildly different work and sleep schedules".
Maybe the main issue is that many people fear change? (Which is quite "funny", as winter/summer time is a change in time...)
One of those left out features is `sudoedit` or `sudo -e`. I use this a lot when editing files in /etc or any file that my user does not have permissions. The flag first copies the file to a temporary location with permissions for my user to edit, then opens my text editor (defined via $SUDO_EDITOR env var) as _my user_, without any sudo permissions. After I close the editor, the file is copied back with the original permissions only if there were any changes.
The cool thing is running the editor via my user, which loads my user's configuration/plugins, instead of the root user's.
I really liked the calculus book by Swokowski. The books starts with a revision of the requirements to start learning derivatives, has sections dedicated to applications of that and then goes on to integrals, analytical geometry and differential equations. It will keep you entertained for months.
> CERN’s data store has now crossed the remarkable capacity threshold of one exabyte, meaning that CERN has one million terabytes of disk space ready for data!
1MTB -> 1EB ready for data. It is _effective space_, not raw space. And it keeps growing.
I think Servicer can be a good starting point for people to learn how to use Systemd services and systemd-run. Systemd is huge and can be scary to learn, so providing a set of steps to get a service running is very instructive.
But then, Servicer requires super user priviliges to modify the system, instead of running everything as the non-privileged user, via `--user` flag for systemctl or via systemd-run...
There are few commands to learn the basics when setting up a new system wide service: systemctl and journalctl. Some examples:
- systemctl daemon-reload: reload all unit files
- systemctl start/stop/status/restart <service>: quite intuitive, don't you think?
- journalctl -u <service>: to see all logs from that service. I like to also use `-f` flag to follow new log entries.
- man systemctl: the manual for systemctl
- man journalctl: the manual for journalctl
Writing new service units is the "hard" part, but there are plenty of "templates" on the net, or you can browse `/usr/lib/systemd/system/` for examples.
But don't let the critics here demotivate you. You made a tool, you published it, congrats!
Some benchmarks evaluate "execution time", so the lower the better.
Some benchmarks have a "score" instead, that the lower the higher in the chart. I'm not familiar with these benchmarks and don't know how to interpret it. Is higher score worse or better?
> A flywheel can provide frequency stabilisation, or it can provide energy storage, but it can't do both at the same time.
Ah, that's a good point to know. I thought flywheels could to both at the same time. Do they also help with keeping the load resistive? I guess their high inertial mass would add some inductance, which is how they stabilize the frequency?
Do you have some resources about this topic to share to a layman like me?
I always wondered if flywheels[0] would be a good alternative to batteries to store energy. Flywheels can absorb peak current, help stabilize grid frequency[1] and can
have high efficiency.
But I haven't seen much on the topic, and a lot in chemical batteries.
What are the prices and downsides of flywheels? Does anyone have an up date comparison of commercial solutions with TeslaWall and similar?
Location: UTC-3, flexible
Remote: Yes
Willing to relocate: No
Technologies: Linux, Python, Bash/shell, git, Docker/Podman, CI/CD, backend, microservices, infrastructure
CV: https://heitorpb.github.io/Heitor-resume.pdf
Email: heitorpbittencourt at gmail.com
Interests: Python, Rust, Nix, infrastructure, systems engineering, distributed systems, high performance computing, open-source
LinkedIn: https://www.linkedin.com/in/heitorpb/
GitHub: https://www.github.com/heitorPB
Website: https://heitorpb.github.io/
7+ years of experience in Software Engineering.
I'm a self-starter that get things done. I have experience in software engineering for highly scalable and distributed systems (I've built a few large scale clusters on a data center), backend development (containers with REST APIs), software and systems development (I love building CLIs), bare-metal and cloud systems; I like documenting projects, processes, and code; I've worked in small startups and also in large teams; I enjoy sharing my knowledge, mentoring new teammates and contributing to open-source communities. I am able to operate autonomously and at the same time be a strong team player.
I like to build simple solutions to address user's needs, without sacrificing security or compatibility. I work hard to build systems that are pleasant to use, well documented, and robust (scalable, resource efficient and secure).