1. 9

    Here’s the RSS feed: https://us18.campaign-archive.com/feed?u=ab0f46cf302c0ed836e0bf0ad&id=56b5f64c5f

    I still find this the best way for consuming periodical content. I can read it when I want, and not have it clutter my mailbox.

    1. 1

      While this will work, just keep in mind that there are plans for exclusive content that will not be available via RSS due to its limiting nature.

      1. 2

        Out of curiosity, what is more limiting about RSS than email? The only thing I’ve come up with so far is that I guess you could customize what is sent to each email address, but that doesn’t seem to apply to a newsletter anyway.

        1. 1

          Customization is precisely my issue. The RSS feed will only render the issue as an anonymous reader, which removes any personalized messages I include as well as any exclusive content paying readers (will) have access to. Another issue on my end is that RSS subscriber numbers are not precise.

          To be clear though, I am in no way against RSS. In fact, the whole newsletter is based on my ability to read tons and tons of feeds. Just that Morning Cup of Coding is not (and will not be) designed for RSS, and thus I will not be actively promoting its use.

          1. 3

            You could require that RSS readers append a “token” to the URL; which would identify the reader and thus give them said personalized content.

            1. 2

              That could definitely work. Not sure how I can integrate that with MailChimp. I’ll give it a look this weekend. Thanks.

              1. 3

                You could always roll your own so you have more control:

                you’d still need something like SendGrid for delivery, but that’s not too hard either.

                1. 3

                  Tbh, I don’t trust myself to build a software that sends emails to 3,5k readers :) But it’s definitely in the back of my mind because I still do a lot of things manually. I know about SendGrid and MailTrain, thanks for pointing out paperboy.

    1. 2

      For web stuff I use https://chrome.google.com/webstore/detail/bpasswd/dfehiejdcgoiofnfkdippnfadgdpnmlh?hl=en and find it works well (except for sites that in the infinite wisdom don’t allow me to paste in a password).

      But… I’ve been thinking about switching to https://www.passwordstore.org/ (or the Go port of same).

      For generating one off passwords I use https://github.com/ulif/diceware

      1. 21

        Is anyone else bothered by the use of the term ricing? As far as I know it is co-opting the automotive term which has racist origins.

        1. 21

          If somebody brings up ricing and linux, I have to think of this old site making fun of gentoo users w/o a clue:

          https://web.archive.org/web/20080830031318/http://funroll-loops.info/

          1. 15

            This thread got pretty ugly. It started out good talking about the history of the term and what it means to people but has sunk into personal attacks. If someone would like to cite academic sources on the history of the term in tech or racing, go ahead, but otherwise we’ve stopped adding new information and this thread is done. Please don’t post further comments.

            I’m also going to delete the comments with personal attacks. Please don’t do this. If you’re right, being mean doesn’t make you more right. Nobody has ever taken incoming vitriol and abuse are a sign that someone must really be worth listening to and seriously considering, and they’re not appropriate here.

            Tagging so everyone in the thread sees this: @fimad @fs111 @voronoipotato @djsumdog @mjtorn @nebkor @brendes @btaitelb @dz @vhodges @leolambda

            1. 5

              Sorry, I missed this because I was writing the post and went out to the food truck. honest mistake, wasn’t trying to be a butt. I got a little reactionary there, it won’t happen again.

              1. 3

                Nobody has ever taken incoming vitriol and abuse are a sign that someone must really be worth listening to and seriously considering, and they’re not appropriate here.

                Let’s etch that in bronze and hang that over every discussion area on the Internet, please.

                1. 2

                  Exactly.

              2. 13

                Hmm, I didn’t know about that at all. Would be nice to have a better term. Customization seems too general.

                1. 10

                  “Tweaking” seems to capture it pretty well.

                  1. 9

                    I considered that, but “tweaking” also means being high on stimulants, which is just common enough in the hacker community that I think it would be confusing.

                    Perhaps modding, but that’s already a massively overloaded term: game modding, hardware modding, etc.

                    I’m inclined to use “dotting”, as in “dotfile”, but also with the connotation of meticulousness (as in “dotting i’s and crossing t’s”. Its alternate definitions are pretty tame, as well.

                    1. 1

                      Dotting sounds what a dotard does, but I guess that’d be “doting”.

                      1. 1

                        Yeah, good point. I like “styling”.

                  2. 7

                    tuning, maybe?

                    1. 1

                      That looks more apropriate: https://en.wikipedia.org/wiki/Tuning

                      Fine tuning a computer environment” could be your job. “Like car tuning but for software” would be the hobby.

                    2. 5

                      from other communities: Hot Rodding (cars - more Chip Foose than useless spoilers on the back) and Modding (computer cases)

                      1. 3

                        Given that there’s a lot of style at work, maybe “peacocking”, spiffing up”, “turning out”, something riffing on fashion.

                        1. 2

                          It’s like styling, but like even more so. Stylizing?

                          1. 4

                            Styling is good, yeah. “Stylize” actually means “to depict or treat in a mannered and nonrealistic style”, so I don’t think it’s really applicable here.

                        2. 3

                          I had never seen it used in the Linux desktop. The term ricer may not have the same racist meanings as before but two things are common about ricers in my area:

                          1. mostly second hand Japanese cars because they are cheap but American pickup trucks are also part of it
                          2. many ricers seem to be of Hispanic ethnicity so it’s no longer a racist slang about Asians

                          My personal view is that, even when a word has no racist origins, if there is a specific ethnicity that it applies to, it will quickly become a racist word anyway. Luckily there are more and more white dudes who bought their first car and became a ricer 🍚

                          1. 5

                            I had never seen it used in the Linux desktop.

                            My perspective is exactly the opposite – I have never heard this term in connection to cars, just with *nix customization, especially in and around the Linux/Unix community. In over 4 years I’ve never heard anyone use it in any other context, nor was I in any sense aware that it had this other meaning. And I would suppose that most people, especially non-car enthusiasts like me would have probably never found out, nor use the term with this connotation.

                            All in all, it seems like a fantastic starting point for a horrible confusion…

                          2. 5

                            Yes, and yes. :( . It’s unfortunate when a racist term becomes so normalized that it’s just vernacular. Then the people who want to use it xenophobically basically get to do so and nobody speaks up because it’s just a word everyone uses. The term in guns is “Tacticool”. Perhaps there’s a good word for this that is less regressive and a little more general.

                            1. 5

                              It doesn’t have racist origins; or at least not in the context we used it in back when I was in various SCCA and use to race. A ricer is just someone who adds all kinds of shit to their car. Each sticker adds 2hp. The K&N air filter adds 10hp. Big cardboard wing adds 90hp. Fart can exhaust adds 30hp. That carbon fibre hood? 120hp right there.

                              Most ricers were white. They were just kids who didn’t know dick about cars and pretended they did. They’d fill the parking lot and hang out in their riced out Hondas while the rest of us raced. I mean if you stretch, some people might trace ricer back to the term wigger referring to white people enacting black culture.

                              Ricers had nothing to do with race and more to do with shitty car mods like these: https://www.reddit.com/r/Shitty_Car_Mods/

                              1. 12

                                Ricer aka rice burner kinda does though because it was about japanese cars. Yes this is where the term comes from and no I’m not shitting you.

                                Rice burner is a pejorative, used as early as the 1960s, originally describing Japanese motorcycles, then later applied to Japanese cars, and eventually to Asian-made motorcycles and automobiles in general. The term most often refers to vehicles manufactured in East Asia, where rice is a staple food.

                                I’ll be honest terms like wigger are also regressive. I’m not telling you how to speak or trying to say this is what you meant by it. Obviously you can use a word with racist or ethnocentric origins non-racistly. Just keep in mind that not everyone who uses it is using it the way you’re using it. Also keep in mind that someone who sees you using it might think you have it out for a specific ethnicity until they get to know you a bit better.

                                Frankly the title evokes a “Yikes” from me but in a “Yikes they don’t even know how bad that sounds” way. Like people who know you will probably go “Oh but that’s djsumdog, he doesn’t mean it in a racist way”, but wow it is just a really bad idea to lead with a racially loaded term in your article title to the general public.

                                1. [Comment removed by author]

                                  1. [Comment removed by moderator pushcx: https://lobste.rs/s/es3acm/how_i3_vim_ricing_enhance_my_developer#c_u525ta]

                                    1. [Comment removed by author]

                                      1. 0

                                        Someone can be unaware of how racist language affects thoughts and opinions without “being a racist”. Being said yea just because you heard the term from a person of the affected group does not mean it’s cool to say. Case in point if you dropped the n-word because you saw a black person doing it you’d probably get some frowns.

                                        1. [Comment removed by author]

                                          1. 11

                                            I think that’s a really good definition of a microaggression, a term that people don’t knowingly use offensively, but which has offensive origins and still conveys that offensiveness to some.

                                            Growing up, I’d use the term jip [sic] all the time as a synonym for screwing someone over in a deal. I actually thought it was less offensive to say than to say screw. Then I learned that the word has racist origins about stereotypes for Gypsies, so I went through the process that I think a lot of us go through. At first I was defensive because there was a discongruity in my reality between how I saw myself and how others might see me, so I rationalized that the word didn’t really mean that any more. And if someone happened to be offended by it, they were probably just being overly sensitive and should get a thicker skin.

                                            But over time, I realized I had the choice when using words, and that it’s not up to me to dictate how others should feel. So I slowly started correcting myself, because when given the choice, I’d rather not use words that offend a group of people, especially when I’m not part of that group.

                                            1. 3

                                              I didn’t think you meant that, sorry I was responding to the intense reaction to your post. Yeah I do think that’s the case. The root problem is like when you use a word that has racist origins, and a racist takes it as like “Ah they also hate the japs” validation for their racist attitudes. Which is bad. It also sucks because words that are that way primarily the racists, and the marginalized know what it means because they grew up in an environment where the intention behind the origin was more clear.

                                              I hope you understand I do not agree with painting you as a bad guy simply because you grew up in an area where a word was the norm and you didn’t see harm with it. Doesn’t mean there isn’t harm? It just means it was the norm and you were used to it and it would be exceptional for you to escape that norm, and not the default expectation. At least you’re not shutting down the discussion.

                                              Suffice to say, normal people have likely forgotten it, racists remember these things with a death grip and will use it to dehumanize people as much as physically possible.

                                      2. 3

                                        You quoted it yourself: it’s pejorative, not racist. The difference is significant, yet the whole point is moot, because so few people are neurotic about political correctness in slang etymology[citation needed]

                                        1. 5

                                          Things can be both pejorative and racist? Many racist things are pejorative. The term is racist because it uses East Asian products as a way to describe inferiority. To put in in a more personal way it would be like me saying “oh that’s snake code” as a pejorative for python programmers.It tries to illogically assert that since you’ve seen a python programmer make bad code, that a python programmer can never write good code. This is of course is horseshit, and is bigoted against python programmers. I’m merely trying to dislodge bullshit like that from the public consciousness.

                                          1. [Comment removed by moderator pushcx: https://lobste.rs/s/es3acm/how_i3_vim_ricing_enhance_my_developer#c_u525ta]

                                            1. [Comment removed by moderator pushcx: https://lobste.rs/s/es3acm/how_i3_vim_ricing_enhance_my_developer#c_u525ta]

                                              1. [Comment removed by moderator pushcx: https://lobste.rs/s/es3acm/how_i3_vim_ricing_enhance_my_developer#c_u525ta]

                                                1. [Comment removed by moderator pushcx: https://lobste.rs/s/es3acm/how_i3_vim_ricing_enhance_my_developer#c_u525ta]

                                                  1. [Comment removed by moderator pushcx: https://lobste.rs/s/es3acm/how_i3_vim_ricing_enhance_my_developer#c_u525ta]

                                                    1. 1

                                                      There’s nothing wrong with LeoLambda’s article, I liked it too. The title gave me a yikes, but that doesn’t mean that they’re a bad person it probably just means they either didn’t know about the origin of the word, or they knew about it but thought it wasn’t used that way anymore. I also like talking about culture, it doesn’t mean I’m virtue signaling. Though frankly I think you are virtue signalling to the pc-panic crew. You basically pooped your pants when you read the word racist like christ himself was being crucified. Exploring alternative words that are less racist isn’t virtue signalling it’s called not being actively hostile to an entire demographic for no reason.

                                                    2. -1

                                                      Potentially ironically, “hysterical” has sexist origins.

                                                      This whole conversation is a little frustrating to me. I hope @mjtorn and @brendes are just reading past what’s being said to them, due to defensiveness and confirmation bias. The responses to their comments aren’t being worded to tiptoe around their feelings, which is also pretty understandable—these conversations are an emotional investment, and there are lots of aggressive racists out there who will throw that investment back in your face. I don’t really have a solution, but I think the situation is regrettable. The path to realization that subtle racism is everywhere always seems to involve an epiphany after the fact, not careful reading and understanding of the arguments.

                                        2. 7

                                          From my experience it is probably racist. Case in point: In Edmonton they call riced cars ‘Nip’d up’ (racial slang for Japanese) since it would be mostly Asian drivers doing the mods.

                                      1. 1

                                        Depending on your comfort level with admin stuff (and laziness ;) you can always host it yourself (https://www.c0ffee.net/blog/mail-server-guide - seems to be a good guide). Multiple virtual domains and many mail boxes for about $5-$10 month on a VPS.

                                        Edit: But I tend to use sendgrid for transactional emails.

                                        1. 4

                                          The nice thing about make (vs some to other arguably better tool that needs to be installed) is that it comes installed just about everywhere.

                                          I’ve been using Makefiles for my Go projects. They are simple, just wrapping gb as well as some build dependencies (ie golang and gb). so I don’t need to worry too much about portability and since make comes installed my projects are eas(y:ier) to bootstrap.

                                          I’ll have to checkout some of the options mentioned here, especially ninja and cmake… But typing make is very hardwired into my muscle memory ;)

                                          1. 1

                                            installed just about everywhere

                                            Except for the OS used by almost 50% of developers.

                                            1. 1

                                              Sure, but it doesn’t have visual studio installed by default either. I would prefer something like cmake however that can create either a make file or visual studio project (And more)

                                          1. 7

                                            I ran BeOS as my primary os in the late 90’s for about 15 months (on a low end mac clone!), but had to drop it as a daily driver because of the lack of Java tooling (which is what I was doing at the time).

                                            That and I only had access to the built in C compiler that was limited to the size of executable it would produce left me little opportunity for software development. I do remember porting the plan9 rc shell using it as well as the galaxies X11 screenblanker.

                                            I played with the x86 release for a bitI checkout Haiku every one in while (along with Aros and ReactOS) but was back to running Linux as my primary by then.

                                            1. 2

                                              That’s neat you got to use it. I heard the compile times were slow possibly due to microkernel-style but maybe speculation. Another person said the filesystem was too clever. Did you have problems with these? And just how awesome (or not) was the responsiveness under load? They claimed it was great with gradual degradation as it got overloaded with it maybe going back to normal afterward. I still don’t have that on this backup laptop for Linux haha. Browsers especially can cause slowdowns at a distance.

                                              1. 2

                                                I didn’t notice slow compiles, but it was only a 140Mhz 603 ;) The file system was cool but I never really took advantage of it.

                                                The Internet was also much different from today (HTML 3.2 was still a thing) so the browser was not the resource pig it seems to have become (300-400 MB per TAB?!?!).

                                                And lastly I never manage to tax any of my systems all that much.

                                                1. 2

                                                  Appreciate the detailed reply. Esp frequency as I was curious what they ran. When secure hardware gets bootstrapped, it will be on the same nodes as original Pentium or maybe P2. So, I try to track what people could do with the older chips in case it becomes handy for a minimalist, secure workstation later. On top of it just being fun to learn about stuff.

                                            1. 4

                                              Is this just a mirror or are OpenBSD taking contributions via pull request?

                                              1. [Comment removed by author]

                                                1. 5

                                                  Are there specific reasons for this? ruby/ruby allows posting pull requests as long as there’s a tracking issue on the bug tracker for larger things and takes the time and effort to point people to it if necessary. It’s not much, that can be solved by having a block of standard text or even just putting it in the pull request template github provides.

                                                  1. 11

                                                    OpenBSD just doesn’t do github pull requests. That’s not how we work. The project mostly only relies on its own infrastructure; github is not part of that.

                                                    Another reason why pull request won’t be looked at is that you need a browser to use them. When doing reboots all the time during kernel development starting a browser, or even having a browser installed during a libc ABI bump is just a hassle.

                                                    1. 4

                                                      You can easily extract the patch by appending .patch: https://patch-diff.githubusercontent.com/raw/skade/lazers/pull/15.patch . You can respond to PR notifications through email, even send them to your mailing list if you are so inclined.

                                                      Assuming you have some way to do HTTP (which I assume if you have some way to read email), you can extract the patch there.

                                                      My point was more: why put a sign up that says “if you land here, we will ignore you, because you are not us”, when you could put up a sing “hey, hello, you are welcome, but for many reasons this is not the way we work, but we will happily teach you (and maybe accept small fixes with a grumble)”.

                                                      Ruby has also not switched over to Github for many good reasons (one of them being a lot of specialised tooling built around their infrastructure), but they appreciate that this is an angle of approach to the project and will help people coming from there.

                                                      Don’t get me wrong, I do understand and support the reasons for doing your own flow. But why actively working against fresh people that know another flow?

                                                      1. 4

                                                        It’s a little ironic that the solution to “github is unfamiliar” is “hack the URL to add a secret extension”.

                                                        1. 3

                                                          The URL is not obscure nor secret, it’s in the email notification you get for a pull request, right next to the link to the diff.

                                                          1. 1

                                                            Ok, that’s fair, but it’s not obvious how one would discover that without already switching to GitHub.

                                                      2. 2

                                                        It’s not quite true that you need the web to use them (though commenting on them probably does - which is a big part of reviewing):

                                                        https://gist.github.com/piscisaureus/3342247

                                                        But kudos on using your own infrastructure (I’m on a bit of an anti-SaaS kick right now)

                                                        1. 2

                                                          There is also the GitHub CLI for those that prefer doing most work outside a browser.

                                                          I’m on a bit of an anti-SaaS kick right now

                                                          Ditto. I do wish Gitlab was a bit easier to manage - I’d love to install it but the number of dependencies along with the frequent security updates make me a bit leery. Gogs looks good but I need to investigate further.

                                                      3. 5

                                                        Pull requests don’t encourage the same kind of code review as email-based workflows:

                                                        https://lobste.rs/s/rkux7i/why_kernel_development_still_uses_email/comments/vodxjs#c_vodxjs

                                                        1. 2

                                                          I’m not saying you should move discussions over, but you can still extract the patch and move the people over to your infrastructure. Would you prefer to leave potential commiters there?

                                                          1. 5

                                                            The quality of the patch itself is also affected by the medium. People just don’t write “patches” when they use PRs. They write a big pile of commits where whitespace changes are mixed with bugfixes are mixed with new features, all at once, with fuzzy boundaries across commits. There’s also the whole rewriting of the commit/patch stack that seldom happens with a PR, because that involves “scary” push-forces that partially lose the history of the code review, whereas with email it’s just a resend.

                                                            I don’t know about OpenBSD, but for the projects in which I have seen, yes, I much prefer the quality of the patches sent to email than what I’ve seen in PR. I am grouchy and would not miss leaving behind PR-based commits, because their quality tends to be lower.

                                                            1. 3

                                                              I don’t know about OpenBSD, but for the projects in which I have seen, yes, I much prefer the quality of the patches sent to email than what I’ve seen in PR. I am grouchy and would not miss leaving behind PR-based commits, because their quality tends to be lower.

                                                              Would you feel comfortable leaving behind the potential committer that could learn your way of writing patches?

                                                              1. 3

                                                                Some might argue that any potential committer should be keen enough to learn the way a project works. But I can see the value in your approach (and it’s one I’d favour personally - help people to swim rather than throwing them in the deep end, where only the strong survive). Wow, what a selection of mixed metaphors there!

                                                                1. 2

                                                                  Some might argue that any potential committer should be keen enough to learn the way a project works.

                                                                  Sure, I wouldn’t work with people that absolutely refuse the projects flow. But any approach should me met with the benefit of doubt and is an opportunity to start a conversation, ask people to clean up their patch etc.

                                                                  E.g. when I first submitted to freedesktop, I had to set up git send-mail. It’s horrible. It was hard to find out I even had to do this and then which the exact mailing list to send it to was, as the one I though was correct was slighly abandoned and full of spam. Took me around 5 hours for a tiny patch.

                                                                  The review experience with the freedesktop people was stellar, then. But the patch nearly got lost on the approach, and I have been doing things like that for nearly a decade.

                                                                  On the other hand, people complain about lack of committers.

                                                                  1. 10

                                                                    5h for a first patch submission is really not that much. Excepting to spend as little time as possible on submitting a patch makes it sound like the submitted contribution is a “fire and forget” one. Those can of course be nice, but no project can survive on them. Which is why contributors who avoid learning the tooling used by a project are really not that interesting.

                                                                    In OpenBSD’s case, consider that all developers are already volunteering a significant chunk of their time following the mailing lists and reviewing patches by fellow developers and new contributors. When your goal is security, every change can be dangerous. So code review applies to everyone, and the project relies on everyone to be involved in the canonical code review process to keep the code base stable and secure. .Email is where the real action is in this project. If a non-trivial change made it into the central repository but was not shown on a mailing list, or at least to other developers involved in the area, this would be regarded as a major problem..

                                                                    With a well established (since 1995) process like that, moving the attention span of even just a few developers to a different platform than email can be a huge distraction. Yes, it serves outsiders who don’t feel like learning the tooling. But suddenly everyone has to watch two spaces for upcoming changes to review, because it’s not all in the one usual place, and who knows what kind of breaking changes the other subgroup over on github is up to.

                                                                    Your best bet for contributing by pull requests it to ask an existing developer to accept pull requests from you and then channel them to the mailing list on your behalf. But why would any existing developer want to do that?

                                                                    1. 6

                                                                      I am inclined to agree when submitting a patch requires jumping through extra hoops. In this case, we’re asking people to do less work, not more. All one need do is send the output of git diff to the list. I’m pretty sure that’s actually less work than creating a pull request.

                                                                      1. 2

                                                                        Email? What is that? Some obsolete version of slack?

                                                                        I agree with everything that has been said here by OpenBSD developers. The proportion of quality patches received over email is light years ahead of the proportion of good GitHub pull requests. And this doesn’t even address the fact that GitHub pull requests force you to use a particular kind of workflow, while email allows actual developers (the people who do 99% of the work) to use what workflow they prefer. Sure, they don’t allow the casual contributor to chose arbitrary workflows, but that is a feature (not a bug) of the release engineering process.

                                                                        The process is stable and works very well.

                                                      4. 2

                                                        I believe it’s just a mirror and I doubt contributions are being taken via pull request (although @jcs can confirm).

                                                        BTW, the mirror has been there for quite a while if I’m not mistaken…

                                                        1. 4

                                                          It’s hitting news because of the official link on the openbsd.org website. See the commit.

                                                          1. 5

                                                            Or maybe this one ;)

                                                            1. 5

                                                              I prefer this one ;)

                                                              1. 1

                                                                Yes! That’s the good one! :D

                                                      1. 3

                                                        I like lab notebooks because they fold open flat. Unfortunately the one I use is 11.75" x 9.5". Lab notebooks are designed for researchers who need to staple pages into it, so it’s certainly too large for you, but maybe it’s a useful keyword for your searches.

                                                        1. 2

                                                          Thank you, if I can find a smaller version of this it may be what I need, since I am left-handed and notebooks that don’t fold flat can be annoying.

                                                          1. 2

                                                            http://www.bookfactory.com/ has smaller sizes

                                                            1. 2

                                                              Thanks! That’s exactly what I was looking for :)

                                                          1. 2

                                                            I am working on the documentation for my personal finance analytics and reporting toolkit (for banks and credit unions primarily) http://cashbooktoolkit.com/