43224gg252
Seems like they've been doing this since the beginning.
Welcome to *BSD
I have an OS I coded my self that no one has ever found a vulnerability on.
If it needs a web UI, Vue.js.
Plan on using Redis too.
Source? Is there any empirical evidence that this is happening or is this just what you're telling your self? IMHO, it's quite the opposite -- anytime cannabinoids are shown to have medical value people claim "correlation does not imply causation" and "we need more studies" and "this only works in a lab!!1".
Most of the companies here I've never even heard of and the ones I have heard of aren't companies I would take into account when choosing a file system.
http://open-zfs.org/wiki/Companies
In all my years I've never encountered or needed this file system, and every time it's mentioned it sounds like it's more trouble to run it than its worth.
Not to mention Linux has a much better license for end-users in that it makes some effort to guarantee the code stays free, and that corporations can't close and modify the code and redistribute it for profit.
I feel like "advocating for FreeBSD" really does more harm to the open source ecosystem than good.
I used mpd and cmus for years but the main problem I had with them is that when I changed the directory structure of my music files it would corrupt my playlists. There are a lot of different work arounds but eventually I decided that to build a playlist I wanted to copy the file into a playlist directory instead of just reference the file location in a text file.
Right now I use Ranger (a CLI file manager) as the "front end" to mpv. I run mpv on a unix socket so it can be controlled remotely and I can request things like artist, title, etc.. and use that info in desktop notifications and widgets (if I want). Most of the time I never even look at my music player so this works out really well, and I already have mpv installed for video so I'm finding another way to utilize a program I already have installed instead of using another one.
I disagree. If you're a programmer who cares about privacy use Linux.
Why would a so called "hacker" choose to use an OS that's slow, has horrible update policies, horrible privacy standards, injects ads into the main programs and start menu, requires anti-virus, etc?
Also, the idea that Windows has good drivers and Linux doesn't is asinine. My current dell came pre-loaded with windows 10 and failed to wake from sleep without me opening and closing the lid, then when it woke up, wifi would not come on and the only thing that fixed it was a reboot. Then when I used the touch screen things were going fine until I tried to select text and got an instant BSOD. Also I learned not to accidentally touch the screen and then try to type immediately afterward, or it would lock up the whole OS.
Linux just worked. Literally. Even the touch screen. I get 15 minutes less battery life but it's worth it.
My opinion is the opposite. Almost every go code base I've seen is extremely consistent compared to other languages. Going from one code base to another is almost always seamless because learning Go involves learning the Go tools which forces you to follow Go coding standards. I'd choose to work on a Go code base over Java or C++ any day of the week.
I don't have much experience with elixir, but that's because I like to stay employed.
>the entire error thing is absurd. Anders Hejlsberg got this right many years ago: 9 out of 10 errors are "handled" by a central error handler
This is almost always unacceptable in production, especially when it comes to mission critical hard/software. You need to be able to handle errors in production that you may not even be able to catch in testing and that means you need to catch all the errors and think critically about what should be done when that error is encountered. "Central error checkers" are almost never robust enough for mission critical systems.
Go basically forces people to write high-quality, resilient code bases, and I like it for that.
If you just want a very temporary ordered list you could probably use a channel.