81–90 of 204 posts
As a web developer who knows enough Linux to do minimum dev-ops, could anyone recommend some things worth playing around with in FreeBSD? Like "do this and see how easy it is vs Ubuntu!". Or are the gains more long term like better stability?
And yet, still no universal support for IPv6, and the droplets that do get it only get 16 addresses. Yes, I am going to complain every time DO comes up in the news until this is fixed.
Should have gone with OpenBSD instead to be honest. Half the requests on your UserVoice are for OpenBSD. All the coolest stuff in FreeBSD comes from OpenBSD. OpenBSD -- the world's simplest and most secure Unix-like OS. Creator of the world's most used SSH implementation OpenSSH, the world's most elegant firewall PF, the world's most elegant mail server OpenSMTPD, the OpenSSL rewrite LibreSSL, and the NTP rewrite Ope…
There does seem to be one part of their announcement that's a bit off: While similar to other open source unix-like operating systems, it’s unique in that the development of both its kernel and user space utilities are managed by the same core team, ensuring consistent development standards across the project. Wouldn't it be Linux that would be unique in that they don't do this? Solaris, AIX, HP-UX, all the BSDs, Mac…
AFAIK, AIX, HP-UX, and Mac OS X are not open source (I'm only positive about OS X)
As a web developer who knows enough Linux to do minimum dev-ops, could anyone recommend some things worth playing around with in FreeBSD? Like "do this and see how easy it is vs Ubuntu!". Or are the gains more long term like better stability?
My reasons for using FreeBSD are a little more philosophical: - I want to have a stable base O/S to which I can always easily return. - I want to be able to customize installed packages in an easily scalable way. - I want a server O/S to be simple to maintain, relative to Windows or Solaris. - I want the goddamned documentation installed. During development it's difficult to get RHEL or Ubuntu back to a known-good se…
That's the real reason. Everything else is rationalization added later.
(Don't get me wrong, I've also started on Slackware. But sometimes you need to break old habits to learn something new.)
Earlier quoted context omitted.
Dtrace alone will turn you from a developer to a Developer + Systems admin + practical OS engineer, you will understand how your stack is performing within various lower levels of the operating system and be able to tune the hell out of your stack from bottom up.
Come on, 0.1% of the people need Dtrace...
And DTrace in particular is really, really easy to use (the Linux alternatives, not so much).
As a web developer who knows enough Linux to do minimum dev-ops, could anyone recommend some things worth playing around with in FreeBSD? Like "do this and see how easy it is vs Ubuntu!". Or are the gains more long term like better stability?
I switched from CentOS to FreeBSD as my daily driver a little over a year ago, for the ports tree. I needed a bleeding edge version of valgrind, but my ~/bin and ~/lib were already pretty unwieldy - so that is what caused the switch. That and ZFS. But I've found a couple of other things that I really like: the documentation is awesome, and config files are where you'd expect them to be. Being able to tune system inte…
Earlier quoted context omitted.
Yep. I was running Arch Linux on a personal droplet, and they decided to deprecate support for it. I don't even think there was an official announcement about it. There's even quite a bit of backing to bring it back [1], and oddly, they use an old video on their front page with when Arch was still listed [2]. "Built for developers" => can't use developer's favorite OS. :( [1]: https://digitalocean.uservoice.com/forum…
Because Arch is what % of the userbase and how much does it cost to support that userbase? It gets kind of old hearing people whine about this. If you really want Arch there are providers that support it.
Earlier quoted context omitted.
Everyone needs to know all of the things. Just because it's a pain to get now doesn't mean people wouldn't use it if it were there. Remember when monitor mode meant patching drivers and running a weirdo kernel? It's like that.
Two things here: - If you use Dtrace to troubleshoot a problem it's way beyond your scope of knowledge as a web developer. Dtrace is too deep and very specific to certain problems that you will never see because your regular nginx + php works fine in all cases. - Not everyone wants and should be good at everything. Just be good at what your doing well, I'm not saying that one shouldn't be curious but Dtrace isn't "an…
DTrace is not hard, it's essential; and it's significantly easier, than say, awk, which is another crucial tool.
As a web developer who knows enough Linux to do minimum dev-ops, could anyone recommend some things worth playing around with in FreeBSD? Like "do this and see how easy it is vs Ubuntu!". Or are the gains more long term like better stability?