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

I also think asking for some of those things is absurd and intrusive. I would feel a little (*not deathly) uncomfortable baring my soul like that to some anonymous Discord admins. I'd like to know what others feel/why this is a downvoteable comment.


This is one of the many problems Guix solves on a slightly lower level than most package managers, because binaries live inside Guix packages (/usr/bin is simply populated by absolute symlinks). Of course package managers also do this, but Guix kind of lets you symlink to a (unique) package, rather than `install`.


For stuff I compile from scratch I just use a symlink-based package manager I found online:

https://zolk3ri.name/cgit/zpkg/

It seems very minimal but supports my requirements. It makes sense to me, because everything gets installed (usually via make install) to ~/.local/pkg/foo-1.0/ and the like, and then symlinks are created to, say, ~/.local/{bin,etc,include,lib,man,share,var}. According to the source code, it is configurable via environment variables. It seems to share similarities with GNU's stow.


There's not much more to do than create a quicker remote wrapper. The Git flow here is 2+1 steps: add another remote, push to that remote (+1 is to create the remote). It would be cool to see it built into a Git plugin or wrapper!


The other day I tweeted with one of the localisers behind Half Minute Hero / 勇者30 , a silly RPG-esque game. They did this with one of the stages: it was a sepia level, harkening back to the NES (and slightly before) era. In Japanese, the bad guy spoke in spaced katakana, like the old Dragon Quest, Final Fantasy, Pokemon games. The reference was immediately understandable and cute.

You can easily do the same in English by using ALL CAPS, AND SILLY PHRASING WITH LOTS OF PUNCTUATION!!! In my opinion (native English, but not alive in the NES era), that would work great. But they didn't: they instead replaced all his dialog with various lines from the classic "all your base" meme/translation. It's a departure from the original - still works well, still funny, though in a different way.

Different translators think differently. I love seeing how that impacts things. (Also shoutouts to Square Enix's localisation team, they are usually INCREDIBLE. I have even more love for Crisis Core after playing it in Japanese.)


I love Jeremy, I've followed him for a while on Twitter. He comes across as self-confident and prideful of his work, which is great and perfect for a good translator (which he certainly is). Shame Kojima didn't agree at the time, I imagine he's a very proud person as well.


I left a comment the first time this was posted, but to reiterate, the MGS translations were excellent (and arguably better than later installments, though MGS3 was pretty high quality too).

Jeremy played a huge part in launching an incredibly successful series. I hope he doesn't feel too put out by Kojima's reaction.


I watched through most of the interesting MGS3 codec scenes in Japanese (after playing it in English years ago). It had an absurdly great script in both languages (perhaps better Japanese VAs). I'm a bit biased towards it though because it's one of the best games ever made IMO.

MGS was certainly memorable, moreso than MGS2 or MGS4 (lmao) for me.


I love audiobooks (and anything media that comes with audio too) for learning languages. Inflection and hearing what's written is hugely beneficial to understanding, and it's much more memorable for me.


Exactly, built-in delegation and impersation features solve this. AWS IAM and Kubernetes have great implementations. Hopefully we get some more standards like OAuth so people talk about this stuff more.


A nice setup is something I'm really, really looking forward to once my student life is over. So I can't upvote this, viewing it makes me too sad :'(


Many recent GitHub features have been ports from GitLab: WIP pull requests, suggested issues. I'd reverse the question and ask what GitHub is offering that GitLab isn't (except the community usage). (And yeah, I guess I'm a GitLab fanboy...)


Perfect, exactly what I needed. Trying to make the switch to Guix from Arch Linux but my hardware is hopelessly unsupported. There's a guix-nonfree repo out there but I couldn't get wrap my head around the config (new to Scheme). Guix looks really, really cool.


They could make it look slightly more friendly, with little things like reducing unnecessary punctuation characters. For example, this:

  (make-linux-libre
   %linux-libre-version
   %linux-libre-hash
   '("x86_64-linux" "i686-linux" "armhf-linux" "aarch64-linux")
   #:patches %linux-libre-5.1-patches
   #:configuration-file kernel-config)
Could be this:

  (make-linux-libre
   :version      linux-libre-version
   :hash         linux-libre-hash
   :list         (list "x86_64-linux"
                       "i686-linux"
                       "armhf-linux"
                       "aarch64-linux")
   :patches      linux-libre-5-1-patches
   :config-file  kernel-config)
Then it's easier to see that the semantics is actually familiar to you: it's just a call of function `make-linux-libre` with keyword arguments like `:version`.

Minus characters are parts of identifiers (like underscores in many other languages), parentheses delimit lists of things, and the first identifier in parentheses list is usually either a function name or a macro name.

If you want to invest half an hour into being able to read most Scheme code, you could skim the old R5RS paper, and skip the parts on first-class continuations, formal semantics, and `do`. https://schemers.org/Documents/Standards/R5RS/

On your first skim, also don't spend much time trying to understand R5RS `syntax-rules` -- it's neat, and worth learning someday, but there are now much more powerful and easier ways to extend syntax, especially in Racket.


Thanks. Your revised syntax looks so much cleaner. I'm interested in learning Guix because I was hoping the syntax would be cleaner than Nix's. From a dev ops perspective Nix/Guix is the way to go. To me, the syntax plays a great part in coming up to speed and trying new stuff without going back to the manual.

My understanding is that Guix is 7 years in the making (at least) so is there even a remote possibility that syntax revisions like the one above will be considered?


I don't know anything about Guix itself yet, but you could ask the developers.

Scheme is great as an imperative (or declarative) configuration language, because the language is super-powerful, yet small and elegant. So many configuration languages end up being ad-hoc.


You first have to specify the custom packages load path and then add the name of the package to your scheme system configuration.

For example:

You have a scheme file in /path/to/guix-custom which includes the declares linux-nonfree.

You run `export GUIX_PACKAGE_PATH=/path/to/guix-custom` and now guix will be able to find this package.

You use the module and include in the declaration

`(kernel linux-nonfree)`

PM and I will share my configuration :)


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

Search: