@luciano@simon I have a suspicion that the fear of losing particular automations and configurations is waaaay bigger than it needs to be for a lot of programmers.
“Aaah, my keybindings!” or “Aaah, my workflow!”
Friend, the smartest and most adaptable part of this system is YOU. You'll hit the wrong thing for a bit and then you'll adapt. You can leave that browser/editor/shell/note-taking tool of you want to. It's going to be okay.
Okay, it's time. Time to change servers. Time to have local & federated timelines that don't make my eyes bleed. Time to support an indie effort.
Does anyone want to share about their server? My main interests are #Music - I play #Eurorack#Synth, #Guitar, #ChapmanStick, and software, with varying degrees of skill - and #Mathematics - I'm attempting to get into grad school for #Math to facilitate a career change. I'm also liberal af, if that matters one way or the other on your server.
I want to see absolutely no sensible and practical advice here. What programming language should I start vaguely and in a chill way teaching myself if I just want to experience something fun or elegant or interesting in and of itself, assuming I have no goal for using it to do anything really (outside of learning)
@michaelaye I haven’t tried, but I think that’s right. My use case is mostly editing code in a terminal. I’m content with VS Code, just hedging my bets so I’m not too dependent on one tool.
@pamelafox I've been learning Typst and their docs are really good for this. There's a tutorial and a reference section, and nearly every argument to every function has explanation and an example. Everything is hyperlinked. It's just glorious.
why the fuck does the first copy of a #vuejs component intercept the v-model updates from the second copy
the vuejs docs specifically state that events don’t bubble beyond the immediate parent, and the two component instances in question aren’t on the same parent
and attempting to manually reimplement the stuff v-model is a shortcut for didn’t fix it
and googling has not turned up anyone else with this problem (then again google sucks these days)
@aldeka Of course. Because when you adopt a framework to help mitigate the ~30 years of weirdness the web platform has accumulated OBVIOUSLY what you want is for it to actually not do that at all.
I love when the things I need to get done today are are the things I want to do least (video recording, newsletter writing, dept-wide email) while I have nice, fun nerd snipes hanging in my peripheral (WASI).
The other day, I got on my soapbox bit about productivity, how humans work and how we don't need to choose between having this nice happy world where people are allowed to help each other and "actually being productive"
I also described humans as a social and equitable animal that wants to help others. But... I don't have any scientific citations on hand for that; I've seen research around it over the years, I just don't have references on hand.
@hazelweakly Fundamentally, computers can do math, remember stuff, and decide what to do next based on math and stuff they remember. The rest is just plugging in buttons/screens/radios/motors/etc.
i've been hearing a lot from folks on here who are frustrated with git (for many good reasons!)
but I'm curious about the opposite perspective: if you've worked with more than one version control system over the years and you prefer git, I'd love to know:
a) what other systems have you worked with? (hg? svn? p4?)
b) why do you prefer git?
notes:
please no replies about why you think git is worse
interested in answers other than "because I have no choice"
some proprietary language integrated thing (Progress ABL's version manager)
MS Team Foundation
I've found the combination of git commands that work for me and have written down the incantations that I don't know well enough to remember. I've got a good enough mental model that I can usually figure out how to get where I want to be.
@b0rk I prefer git because while other systems may be simpler when things are going well (a linear sequence of commits gets applied by people who aren't working on the same files) they fall apart when you get off the happy path (basically any time you'd rebase a branch in git you're hosed).
You end up with different branches in different directories, or having to lock files before you can edit them. It's conceptually simpler but makes it difficult or downright impossible to get work done.
@b0rk
Having tried the "simpler" models, my hunch is that there's some irreducible complexity to this problem and you need a model that can handle the edge cases.
I'd compare it to the difference between Python or JavaScript where APIs are simpler but might throw exceptions to and Rust or Elm where the APIs feel fussy but force you to think about edge cases.
If you would like to do something for me for my birthday, will you please send me a picture (or recording) of something broken (or not working correctly)?
You can reply, or post it with #glitch4andi and I will see it.
What are folks using for simple build scripting these days? I know tons of folks love Just, but I've just (lol) never been able to make it fit my brain and after a very frustrating morning not being able to get what feels like a simple thing to work I'm ready to move on. What should I look at next?
I don't want to go back to Make, I find that even harder. And we use Babashka at work, which I find mostly fine, but I'd prefer something without the JVM dependancy.