What about using enums? In this case you will have to specify them for all records, but this ensures that the field will always be present.
enum license_owner {
regular_citizen = 0,
embassy,
government,
...
}
What about using enums? In this case you will have to specify them for all records, but this ensures that the field will always be present.
enum license_owner {
regular_citizen = 0,
embassy,
government,
...
}
In Elixir, we mark statuses by using a question mark at the end of the variable name. Something like this:
authorized? = user |> get_something() |> ensure_authorized?()
I like this better than the is_
prefix
console.log() is really easy to learn, but what happens after that is a complete “wtf”
The language idea is good, but: THREE.WebGLRenderer: A WebGL context could not be created. Reason: WebGL is currently disabled
.
Seriously? Why do I need WebGL to read TEXT in docs? :/
I used DuckDuckGo a couple of years ago, but they added their own blacklist of sites (pretty stupid), and for my language it started returning crappy generated spam sites instead of relevant results. They shouted at the top of their lungs that for my language they simply index the results from Yandex, but this is a lie, they are different.
StartPage gave the best results, but they introduced a captcha that I got every damn request.
I’m currently using SearXNG, which collects results from Google. And these are damn normal results, unlike other search engines that consider themselves the smartest and edit the results.
Try not to work in pitch darkness :)
Used dark (not black) themes everywhere for 8 years. My eyesight is still good according to my annual physical, but recently I’ve noticed that I have a hard time reading text written on a dark background. It is slightly blurred, especially when there is no light in the room.
Somewhere I still use dark themes, but I always try to switch to light mode if things look okay with code highlighting or smth.
Have you tried Debian?