310 karma · joined December 4, 2017
- In-browser viewing of diffs and code - Issues management - Showing code to clients/other devs is simpler and prettier. - Can push to local and run tests on a fresh repo pulled in a VM
Honestly as with mostly everything, it can be achieved by other means. It's just what feels good to me. It's extremely lightweight but robust and fits well in my work environment. That is all code editing is done in Emacs with millions of opened tabs in Chrome. I make extensive use of workspaces in xfce and I just Ctrl-Alt-(Right/Left) my way around going back and forth Emacs/Chrome. I could just have a file manager opened and double click on every file, or open them in Emacs, but that isn't always necessarily faster (for me).
Tldr: Personal preference.
I use it for as my local git server on Debian 9. Binary is in the /home/me/gitea directory. Run the usual gitea setup, then copy this to /home/me/.config/systemd/user/gitea.service:
[Unit]
Description=Gitea (Git with a cup of tea)
After=syslog.target
After=network.target
[Service]
RestartSec=2s
Type=simple
WorkingDirectory=/home/me/gitea
ExecStart=/home/me/gitea/gitea web
Restart=always
[Install]
WantedBy=default.target
Then just systemctl --user daemon-reload && systemctl --user enable gitea. Then visit localhost:3000 and add it to your remotes (git remote add local ...) and you can push your changes to your own gitea instance."A tricky part of this would be how to balance letting the network have control over itself and letting the government have some special degree of input on ‘monetary policy’. It’s certainly ok for the government to have some, but I think the network needs to be mostly in charge (e.g., the government couldn’t be allowed to arbitrarily inflate the currency when it wanted to)."
This is how the current monetary system works. The "government" can't "arbitrarily inflate the currency". I'm surprised at the lack of depth of this article, is this a brainfart? Haha.
Overall very pleasant experience.
Edit: woops, forgot to say what I actually wanted to say! You don't need to write everything in one language. I actually abhorred that idea, and glad I found a stack that 1. doesn't need much maintenance 2. doesn't force me to spend countless hours learning about why XYZ is better than ABC and how QRT were wrong about this and that and learning 100 different new concepts and terms. I put together the stack myself, and it worked without me having to bend my programming knowledge to the particular task. There's value in this.
Scholarship resources being limited, you should maybe get less chances to win another scholarship after winning one. Then you'd get more people with scholarships, and maybe some of them would get the confidence boost they need to actually perform instead of work stupid jobs.
One particular case I always thought was especially unethical is for some people to win scholarships and then change branches entirely. I.e. to use the scholarship for an application to med school, or law school, or whatever other program they didn't get into.