[-] tatterdemalion@programming.dev 5 points 8 months ago

I think it would be reasonable to consider reparations for individual descendants of slaves. There are plenty of people alive today that can prove their descendance from a slave.

Reparations to entire countries in Africa seems a bit absurd to me.

Hard disagree about CCR.

Wouldn't it be de-ionize?

[-] tatterdemalion@programming.dev 5 points 2 years ago

What do you think a meme is?

[-] tatterdemalion@programming.dev 5 points 2 years ago

My biggest shortcoming at the moment is my NAS is also my gaming PC. It's pretty inefficient to have that on all the time. But I haven't had the time to build a dedicated NAS.

[-] tatterdemalion@programming.dev 5 points 2 years ago* (last edited 2 years ago)

Surely this will have a real impact instead of just making low-paid workers jobs much harder.

[-] tatterdemalion@programming.dev 5 points 2 years ago

Awwwww there goes that plan.

[-] tatterdemalion@programming.dev 5 points 2 years ago* (last edited 2 years ago)

Gleam is cool. I wrote some services with it to see if I wanted to use it for more projects. It seemed like a good option because it would be easy to teach.

Things I like:

  • fast build times (I only tested small apps though, under 2000 LOC)
  • strong static types
  • runs on the BEAM
  • easy to learn
  • pattern matching
  • immutable + structural sharing
  • currying (with parameter holes)

Things I don't like:

  • no re-exports
  • it's possible to have name collisions between packages; authors have a gentleman's agreement to always create a top-level module with the same name as the package
  • some standard library APIs seem missing or immature (it's still pre-1.0)
  • it can be hard to get good performance out of idiomatic code for specific tasks (see immutability)
  • no format strings; best you can do is "Hello, " <> name. It starts to get cumbersome
  • parsing/serialization is all quite manual boilerplate; there's nothing quite like serde
  • no field/argument punning
  • no method syntax; you just have to scan the docs to figure out what functions can be used with a given type
  • you can't define the same variant name twice in the same module; I believe this is a limitation in how the types are translated to Erlang records
  • you can't call functions in pattern matching if guards
  • you can't have dependency cycles between modules in the same package
  • hard to write FFI correctly; you lose all the comfort of types
[-] tatterdemalion@programming.dev 5 points 2 years ago* (last edited 2 years ago)

Probably climbing up the West Ridge of Quandary Peak in CO. I was with 3 college friends. I didn't expect the altitude to affect me as much as it did, but I got pretty winded. It was a little snowy and wet, so our holds were sketchy at times. Along the ridge it's class 3 climbing, and the crux is a crack in a steep rock with a dangerous fall behind you. That was probably the biggest adrenaline rush I've ever had.

Thankfully we were greeted by some friendly mountain goats on our descent.

Here's a good video of the climb. The harder stuff starts about 9 minutes in.

https://youtu.be/CN5P4aRxnu0?si=O0MSyjB_RJTZ4fmj

[-] tatterdemalion@programming.dev 5 points 2 years ago* (last edited 2 years ago)

The git push --force is definitely a controversial suggestion, im personally happy with doing that, but I have also personally accidentally force pushed dev/main and seen others do it. Squash on merge is probably a safer habit to have. Also, gitlab and bitbucket both get a bit confused if you forcepush to a branch that is part of a MR.

You can add branch protections that will prevent you from accidental force pushing to main or dev.

IMO when I see a PR with "WIP" commits, I just assume that minimal effort was put into keeping the commits organized, and I squash all commits to review the PR. If I see many meaningful commit messages, I will try reviewing one commit at a time.

When I make a PR, I force push to keep my commits organized. If there are changes I want to make as a result of feedback, and they would create significant churn to rebase all of the patches, then I will apply the feedback in a follow-up commit.

[-] tatterdemalion@programming.dev 5 points 3 years ago

Was anyone else bored of this meme as soon as it started?

[-] tatterdemalion@programming.dev 5 points 3 years ago* (last edited 3 years ago)

Loving it except for a handful of bugs that I expect to be fixed in the next release :)

It feels good to start fresh with a new set of community subscriptions. Some of them I've subscribed based on the topic before they've had significant traffic, but we'll see what happens!

view more: ‹ prev next ›

tatterdemalion

0 post score
0 comment score
joined 3 years ago