Hacker Newsnew | past | comments | ask | show | jobs | submit | cyunem's commentslogin

It's technically true (the best kind). The more affordable apartments are usually rented out by a 'boligforening' and it's relatively common to give a membership/waiting list spot as a birthday present to newborns when the family lives in or near Copenhagen. This helps getting an affordable apartment when people leave home later to study. But there are plenty of apartments that do not require 18 years of waiting, it's just that the rent is higher.

As for my own experience, I'm moving to Copenhagen in a month for a job and I managed to find an apartment after searching for about a month. I'm moving from Aarhus (the second largest city in Denmark) and my new apartment costs 2.5 times as much each month, for which I'll get a slightly bigger apartment but much further from the center of town. My guess at the reasons for the price increase is ~50% higher rent in Copenhagen, ~30% moving from a 'boligforening' to a non-'boligforening' and ~20% the extra square meters in the new apartment.


To avoid the hassle of categorising games manually, I've been using https://github.com/Depressurizer/Depressurizer It took me a couple of tries to get a functioning setup with an older version, but it's working now and they seem to have improved the UI a bit. It allows automatically making categories in your library based on genres and user-defined tags from steam as well as some other things like ratings and time to beat


With regards to your desktop, I had/have the same issue with the volume being insanely loud and my options being either on at 2% or off since everything else was uncomfortable. I found https://equalizerapo.com/ (for Windows, similar things seem to exist for other systems based on a quick google search) fixed the problem and allowed a lot greater fine control.

To get lower volume overall with Equalizer APO: install, reboot and change the Preamp line in EqualizerAPO/config/config.txt to -20 dB or whatever suits you. It should work as soon as you save.


Out of curiosity, what features were you missing in fish? I've been using it for a while and haven't noticed anything, but I am probably not in need of heavy on shell scripting. I've heard of plenty of people choosing zsh instead of fish, but I started on fish and never felt the need to switch, so I'm kind of wondering what I might be missing out on.


This could get very long, but to keep it short:

Substitution via `=()`, `<()`, and `>()`. `=()` save's a process output in a temporary file that I don't have to mess with explicitly and substitutes itself with the path. An example of use is `viewnior =(maim -s)` which shows in an image viewer a window that I select; `diff -u <(...) <(...)` or `cmp`, or `comm` instead of `diff` compares the output of multiple processes without having to save them to files; `tee >(...) >(...) | ...` feeds the output of one command to multiple commands without needing to save files

Subshells. I've used them interactively, and I prefer to not have troubles with quoting doing `fish -c '...'` in my commands.

Extended globbing. It's far more concise and less error prone than using a combination of `find` and text processing tools.

Dynamic directories. ~some_project/ for me expands to ~/work-for/client/some_client/some_project/ and works great with completion.

What attracted me the most to fish was the ability to work with multi-line commands as a single command in the history. However, I've seen that zsh has better support for this.

What killed fish for me back then was that their pipes were fake back then. This is something that they've since fixed, but back then, instead of running all commands at the same time with their inputs and outputs linked, I think fish would run the first command, save it to a file and then ran the second command with that file as input. I mean, the behaviour that I saw was that I wouldn't see any output until the first command finished, and some of the commands that I wanted to run took very long to finish or never were supposed to finish without me seeing some of the output first. I'm talking about watching file changes under a directory and manipulating the presentation of the output of the file watching command (e.g. `inotifywait -m ... | awk ...`) or looking for specific events in the system log as they happened (e.g. `journalctl -f | grep ...`) or looking for specific system calls of a never-ending running process (e.g. `strace -fe trace=file -p $pid | grep ...`). That made fish pipelines useless for me.

Anyway I wrote a more lengthy post once describing the differences between bash and zsh that I liked:

https://news.ycombinator.com/item?id=16963856

However, there must be more differences between fish and zsh. I can think of history syntax, right now. I can get an argument from any command I've ever typed based on a substring by doing !?substring?%. If I find myself calling two commands in succession multiple times, I can combine them in a single command without retyping them by doing `!-2; !!`. Then I only have 1 command to re-run next time instead of 2. If I typed a command and realize I want to include the last argument of the previous command, I can type `!$` to include it.


And maybe a law that says things have to load in slowly so it's possible to scroll past them before they appear?


It's all about the experience, the exploration, the perdition of purpose as a tool of the establishment that conditions the individual to always be learning, for only then it can fruit him in his greedy machine of post-modern industry.

Also, frankly, this is nearly a dadaist instance of a web page.


These were recently included in the coverage given by the danish government (at least in my area) and this is probably the biggest quality of life improvement I have received in at least 10 years of diabetes. Even though it's not as clever as some of the other systems, being able to get an idea of the level without having to find a secluded spot and prick my finger is a really great feeling. It also means I can actually check my levels while at a party for example, where previously I would put it off for a bit because it was inconvenient.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: