Husband, father, kabab lover, history buff, chess fan and software engineer. Believes creating software must resemble art: intuitive creation and joyful discovery.
Views are my own.
I didn’t like the capitalised names so configured xdg to use all lowercase letters. That’s why ~/opt
fits in pretty nicely.
You’ve got a point re ~/.local/opt
but I personally like the idea of having the important bits right in my home dir. Here’s my layout (which I’m quite used to now after all these years):
$ ls ~
bin
desktop
doc
downloads
mnt
music
opt
pictures
public
src
templates
tmp
videos
workspace
where
bin
is just a bunch of symlinks to frequently used apps from opt
src
is where i keep clones of repos (but I don’t do work in src
)workspace
is a where I do my work on git worktrees (based off src
)Thanks! So much for my reading skills/attention span 😂
Which Debian version is it based on?
Something that I’ll definitely keep an eye on. Thanks for sharing!
RE Go: Others have already mentioned the right way, thought I’d personally prefer ~/opt/go
over what was suggested.
RE Perl: To instruct Perl to install to another directory, for example to ~/opt/perl5
, put the following lines somewhere in your bash init files.
export PERL5LIB="$HOME/opt/perl5/lib/perl5${PERL5LIB:+:${PERL5LIB}}"
export PERL_LOCAL_LIB_ROOT="$HOME/opt/perl5${PERL_LOCAL_LIB_ROOT:+:${PERL_LOCAL_LIB_ROOT}}"
export PERL_MB_OPT="--install_base \"$HOME/opt/perl5\""
export PERL_MM_OPT="INSTALL_BASE=$HOME/opt/perl5"
export PATH="$HOME/opt/perl5/bin${PATH:+:${PATH}}"
Though you need to re-install the Perl packages you had previously installed.
This is fantastic! 👏
I use Perl one-liners for record and text processing a lot and this will be definitely something I will keep coming back to - I’ve already learned a trick from “Context Matching” (9) 🙂
That was my case until I discovered that GNU tar has got a pretty decent online manual - it’s way better written than the manpage. I rarely forget the options nowadays even though I dont’ use tar
that frequently.
This is quite intriguing. But DHH has left so many details out (at least in that post) as pointed out by @breadsmasher@lemmy.world - it makes it difficult to relate to.
On the other hand, like DHH said, one’s mileage may vary: it’s, in many ways, a case-by-case analysis that companies should do.
I know many businesses shrink the OPs team and hire less experienced OPs people to save $$$. But just to forward those saved $$$ to cloud providers. I can only assume DDH’s team is comprised of a bunch of experienced well-payed OPs people who can pull such feats off.
Nonetheless, looking forward to, hopefully, a follow up post that lays out some more details. Pray share if you come across it 🙏
TBH I use whatever build tool is the better fit for the job, be it Gradle, SBT or Rebar.
But for some (presumably subjective) reason, I like GNU Make quite a lot. And whenever I get the chance I use it - esp since it’s somehow ubiquitous nowadays w/ all the Linux containers/VMs everywhere and Homebrew on Mac machines.
I’m nitpicking but can you properly quote your code?
I just love the “Block User” feature. Immediate results w/ zero intervention by the mods 😆
Nice! Good to see this idea becoming more common 👍
I personally use Firefox Relay which gives me better control for my workflow - I usually need my temporary e-mails to last a bit longer, eg a week or a month.
On another note, the post clickable URL opens the Lemmy instace landing page and not that of the disposable email service.
That single line of Lisp is probably (defmacro generate-compiler (...) ...)
which GCC folks call every time they decide to implement a new compiler 😆
Would be lovely to have a download per release diagram along w/ the release date (b/c Summer matters in the FOSS world 😆)
That’s a fair point 👍 I just wanted to point out that I’m not the author.
As I said, I very much like the idea. It helps raise awareness around the current trend of switching licenses to curb competition/make $$$.
a list or database of projects that were open but then closed down
That’s a great idea! Esp if the list is actively maintained & updated.
Since I am NOT the author of this extension, do you think you could write down your thoughts on the project’s issue tracker?
Created an issue on the repo: https://github.com/galdor/github-license-observer/issues/5
It is: https://opensource.org/license/mit/
It’s most probably a bug in the addon. Best to report it on the repo’s issue tracker: https://github.com/galdor/github-license-observer/issues
Good question!
IMO a good way to help a FOSS maintainer is to actually use the software (esp pre-release) and report bugs instead of working around them. Besides helping the project quality, I’d find it very heart-warming to receive feedback from users; it means people out there are actually not only using the software but care enough for it to take their time, report bugs and test patches.