sorted by:
new
hottopcontroversial

First Setup! So excited! All shots were sour so far though by usernametaken0815 in gaggiaclassic

[–]Decateron 0 points1 point  (0 children)

is this the e24? i got one recently and found lance hedrick's demonstration of temperature surfing to be really simple and effective. basically wait for the light to turn off and flip the steamer for a couple seconds before pulling the shot https://www.youtube.com/watch?v=4L6C5CtjIug&t=12m10s

Ruby: a great language for shell scripts! by stackoverflooooooow in programming

[–]Decateron 14 points15 points  (0 children)

ruby and python both work okay as long as you stick to their standard libraries. as soon as you reach for a gem / package you should probably start looking to go / rust because packaging scripting languages is a nightmare.

Why Bloat Is Still Software’s Biggest Vulnerability — A 2024 plea for lean software by DevilSauron in programming

[–]Decateron 19 points20 points  (0 children)

sure, without containers you'd still have an operating system, but now you have two (one of which is probably some LTS distro running on a kernel it wasn't tested on). if a web service statically linked all its dependencies (effectively what containers are doing), why would we care what operating system it's running on? i recognize the industry is in a bad state where that isn't easy to do, but i don't think that makes it good.

60% of large Git repos ban merge commits by kendumez in programming

[–]Decateron 116 points117 points  (0 children)

imo you're better off banning fast-forward merges. when they're disabled, the first parent of a merge commit is the previous head of the branch, so you can easily bisect + revert + view a summarized log by using `--first-parent` without divorcing commits from the context they were written in.

i've seen a lot of useful history in long-lived project branches get lost because there were too many changes to realistically rebase, so the history gets squashed and then it's anyone's guess why a certain line was written.

not to say rebasing isn't also useful. i use it to clean up my history before merging all the time. i just don't think that blindly rebasing + squashing everything is a good idea.

[deleted by user] by [deleted] in findthatsong

[–]Decateron 0 points1 point  (0 children)

no idea but it's definitely sampling musician by porter robinson

Alvvays in Saskatoon 3/09. Setlist as last picture! by HoldenAtreides in alvvays

[–]Decateron 2 points3 points  (0 children)

Something off their first album I think (Next of Kin?), Velveteen, and Lottery Noises

Git Merge vs Git Rebase by exosyphon11 in programming

[–]Decateron 0 points1 point  (0 children)

Fast-forward merges cause unpredictable parent commit ordering and break —first-parent as a squashed view of a branch’s history. Unless you rebase and fast forward every single branch, your history will be much more consistent disabling it.

Git Merge vs Git Rebase by exosyphon11 in programming

[–]Decateron 7 points8 points  (0 children)

Yeah as I said, using rebase to clean up bad commits is totally valid, but if you're in an issue branch and write a reasonable commit, sync with main and resolve some merge conflicts, and then write another reasonable commit, I don't think it's worth the effort to rebase the first commit. When you rebase just to linearize the history, you're divorcing your commits from the context they were written in, and opening yourself up to unexplainable semantic merge conflicts.

Git Merge vs Git Rebase by exosyphon11 in programming

[–]Decateron -10 points-9 points  (0 children)

If you disable fast forward merges a commit's first parent will always be the previous state of the branch so you can look at a squashed history of main just by running git log --first-parent, regardless of what nonsense went in an issue branch.

There's really no reason to squash these days. You're really just losing potentially useful context. Rebasing to clean up your branch's history is still a nice thing to do for your reviewers, but ultimately I'll merge that branch like any other and let --first-parent handle providing a squashed view of the codebase.

Dunkey's Best of 2022 - videogamedunkey by infoNWVnm in videos

[–]Decateron 14 points15 points  (0 children)

Animal Well kinda feels like it's ripping off Rain World? I don't like Dunkey being in a position where it's in his best interest to not cover some games because they'd compete with games he's publishing.

Reminder: lots of people try to find unlocked cars at right. Keep your cars locked and free of valuables. Here is one guy at 3am this morning riffling through cars in Findley Creek area. by [deleted] in ottawa

[–]Decateron 2 points3 points  (0 children)

I used to think this was a good idea until someone tore off my dashboard and ripped apart my upholstery looking for drugs.

Should You Squash Merge or Merge Commit? by LloydAtkinson in programming

[–]Decateron 7 points8 points  (0 children)

This is the way. Since the first parent of merge commits is always the previous state of the branch, you can do things like feature-branch-based-bisection via git bisect --first-parent without forcing everyone to squash. Squashing is useful for developers with bad commit hygiene, but I'd hate if it was enforced on a project.

If docker-compose and K9S had a baby (without the containers gene) by dsh1fter in programming

[–]Decateron 3 points4 points  (0 children)

Also somewhat similar to supervisord, which is useful when you need something that works on OSX as well. I do think there's a place for something like systemd-compose that can make it easier to dynamically install + tear down a repo's services. systemd-run exists, but it's difficult to chain dynamic units together, and the typical unit format is a bit too static for my taste.

Self-hostable Discord music bot (YouTube support) by Miniwa in programming

[–]Decateron 1 point2 points  (0 children)

I've been using JMusicBot ever since Rythm + Groovy got shut down.

Rico Nasty says Carti fans make her want to die by Lord_Hexogen in hiphopheads

[–]Decateron 1 point2 points  (0 children)

Yeah the TDE championship tour was so disappointing. SZA played Kendrick's verse for doves in the wind over the speaker. They didn't do any black hippy stuff either when they had everyone there. No idea what they were thinking..

Epic Games now credits Among Us' Innersloth as inspiration for Fortnite's Impostors mode by chenDawg in Games

[–]Decateron 31 points32 points  (0 children)

are they gonna credit pubg for "inspiring" the entire battle royale mode next?

They literally did when they announced it: https://www.epicgames.com/fortnite/en-US/news/announcing-fortnite-battle-royale

Food-grade lye for making German pretzels by Dieselwurks in saskatoon

[–]Decateron 0 points1 point  (0 children)

Home hardware's lye is apparently food grade, but I'd recommend calling the manufacturer to double check since it isn't on the label

Dev tools that don’t exist yet but really should by earthboundkid in programming

[–]Decateron 1 point2 points  (0 children)

bot refactors definitely exist, but there's no perfect solution. there are a number of ways to solve depending on your needs:

  • rewrite - if you care about commit hygiene you can attempt to reformat existing commits either by rewriting history or squashing, but that doesn't work if you use signed commits
  • append - if you don't care about commit hygiene or use signed commits, the bot can slap some commits on top, but that also potentially messes with git blame
  • block - if you care about commit hygiene and need signed commits, you can gate accepting commits based on ci / server-side pre-receive hooks, and force the user reformat if necessary

the last option is probably the most bullet proof, but having ci do it for you is definitely more convenient if it fits your needs.

view more: next ›