Thinking it’d be good to be able to refer back to specific chunks of text on a website: https://scratchfile.sjm.codes/2020/12/09/capturing-webpage-locations/
(Excuse the missing logo, still under construction I guess)
noticed an interesting "physical computing ritual" that I've been doing today. I use i3, and have a laptop that I hook up to a big monitor every morning. When I first hook it up, all of my workspaces are on my laptop, and you have to do a bunch of ctrl-shift-ing to get everything over to a different monitor usually. Instead, I close the laptop lid for long enough for all of the workspaces to shift over to the monitor, then open the laptop up again.
works a treat.
I was having a read of Programming as Theory Building (https://gist.github.com/onlurking/fc5c81d18cfce9ff81bc968a7f342fb1) and now I'm thinking about if it's possible to design software in a way that makes it's theory easy to impart. Not necessarily a programming language, but at the design level.
Or possibly out of chunks of well-known theory. Dare I say "pattern language"?
Mozilla Google budget screaming
Something is just wrong here... Mozilla just extended its deal with Google (making it the numero uno search engine) for something like 400 million dollars PER YEAR. For the next three years.
That is 1.2 BILLION dollars from 2020 to 2023.
If you cannot run a freaking NON-PROFIT on 400 MILLION dollars PER YEAR that means:
a) You are paying your executives too much.
b) You don't know how to manage a non-profit.
c) All of the above.
the more I read about solarpunk, the more I think that Christopher Alexander's 'A Pattern Language' is pretty close to being solarpunk
@unwesen yeah, definitely a set of trade-offs there. It's always possible that a language/environment could layer these enhancements on top of a generic vcs to avoid the issue and keep the positives. Not necessarily an easy problem, though
Any semantic storage and editing should probably come with easy transformations to/from plain text too...I think editing, viewing, running (and distributed computing, according to unison) could all be improved
again, dunno what to do with this. Just cool 🤔
@unwesen I guess I'm thinking there's a whole bunch of possibilities that are slowly being explored, and I'm excited by it. Having a VCS that was aware of the semantics of my code and could perform a merge or show diffs based on this. True, this doesn't mean we need to move away from a plain-text/parser architecture and processing power is cheap, but it might be made simpler and easier if plain text isn't the only choice
@unwesen sure, it's not the biggest problem in the world! (if we stick to plain text being the primary way we write code which realistically is going to be tricky to get away from)
Languages like idris allow such a great editing experience even with it being text-based but you could push it further
This blog post shows one alternative flow for editing code: https://petevilter.me/post/datalog-typechecking/
There's also unison, which uses plain text for presentation and editing, but not storage: https://www.unisonweb.org/
I'm currently fascinated about storing and editing code in a way that is consistent with its semantics, rather than using plain text for everything and requiring that each tool parses and understands the code separately. I know that lsp has done a bunch here, but it's not quite as far as it could go.
but having said that, no idea what to do with this fascination.
I’m planning on trying this with some folk from work and the little schemer. We’ll see how it goes 😎
Why Mastodon and the fediverse are “doomed to fail”:
I wonder if pair/mob reading of difficult programming books would be useful. I’m especially thinking of books like the reasoned schemer or the little typer, where there’s a certain pace that lends itself to discussion and diving deep.
It would set up some accountability and maybe some momentum. Or it might be terrible, idk
in capitalist tech: massive user growth ---> lots of money (funding) available --> pay fancy people to do fancy scaling things
in community project: massive user growth ---> aaaah everything is really chaotic now, there are loads of tasks that nobody wants to (or can) do... it's like actual work!! I thought this was meant to be fun...
the solution to me is to scale out, not up, federate don't grow. but still, people seem more focused on big ideas that need to scale up to be successful.