The working programmer might be interested in the series on ropes on the Xi Editor website[1] as a practical application, as it motivates the concept as it goes. (Alternatively, if you’ve taken an algorithms class you have probably encountered the idea of computing things over an interval of an array by storing them in for each node of a tree that flattens to that array, such as a search tree or interval tree.)
I was also dissatisfied with existing task tracking apps, and built my own:
t-do.com
There are still many rough edges, but it’s extremely useful. One of the best features that a text file has that very few apps support is unlimited sub-task nesting, and that’s a core feature of T-Do.
I disagree. There are many operators that you’ll never use but if you memorize
(^.), (.~), and (%~), you’re pretty much set for a lot of real-world software development.
Per Kmett’s original talk/video on the subject, I can confirm my brain shifted pretty quickly to look at them like OOP field accessors. And for the three above, the mnemonics are effective:
“^.” is like an upside down “v” for view.
“.~” looks like a backwards “s” for setters.
“~%” has an tilde so it’s a type of setter and “%” has a circle over a circle, so it’s over.
I’ll also add that my experience in recent versions of PureScript things get even nicer: visible type application lets you define record accessors on the fly like:
foo ^. ln@“bar” <<< ln@“baz”
“.” Is unfortunately a restricted character and is not the composition operator like Haskell, but I alias “<<<“ with “..”
The pretty obvious question with the above is: why don’t you just write “foo.bar.baz”. In my case I use a framework that uses passed lenses for IoC, but I think “%~” is always nicer and less repetitive than the built-in alternative.
There's actually a bit of a controversy over what the original film actually looked like. There are 35mm scans out there with no colour grading at all (e.g. https://youtube.com/watch?v=Ow1KDYc9XsE). Some people claim it never had the green and it was added later for the DVDs. The sequels definitely had it but turned up to 11. Trouble is nobody can really remember what they saw in the cinema in 1999 and there's a bit of Mandela effect going on thanks to retroactive grading and sequels.
I saw an original 35mm print at Cinespia somewhat recently and it's definitely not the green tint. That was added later.
The original look was a bleach bypass film process which was very colourful with blown highlights. There should be quite a bit of info on this online I would think.
Coolest part of this whole experience is that the Cinespia venue is at the Hollywood Forever in LA - it's a giant old cemetery with a huge lawn and massive screen. During the final scenes when Neo is about to fight Agent Smith in the rain it actually starts raining in real life (obviously rare for Los Angeles). People started leaving but I thought it was pretty damn amazing.
Yep, KV is broken too. Any worker that depends on KV is throwing exceptions. I was able to get into the dash, but it's very slow. Error rates started to go up significantly around 18:00 UTC.
It's not much of a reach to go from "discussion about impact on human-verification dialogs" to 'discussion about human-verification dialog policy". This isn't an incident-management channel, it's a discussion forum - tangents are fine!
I complained in the apnews.com thread, because the apnews.com verification, which is annoying by itself, did not work at all this time. That is hardly unrelated.
I really appreciate the integrated fingerprint reader in these cases. I usually run with my laptop screen closed (with external monitor) but open it specifically to authenticate in system dialogs.
Apple also sells a wireless keyboard with touchid integrated. Works great. Especially if you also set pam to use touchid for sudo. They’re not cheap though.
Eh MS wasn’t going to just let VSCode derivatives soak up all the AI gold rush money, these companies knew the risks. I wonder what it’s going to mean for projects like Zig, a migration of VSCode refugees could crank things up to 11 pretty quick.
I guess the point is that VSCode won because it collected critical mass (despite people practically chanting Microsoft’s “embrace, extend, extinguish” game plan). If a sort of exodus were to happen, perhaps that same critical mass would stoke the flames of mass plugin catch-up.
I have no skin in the game, I’m just a guy in the internet back alley throwing down a couple bucks on a dice game.
I've been shafted by Github under MS ownership in the past, after 7 years.
I'm using a gitea instance ever since.
The only thing Github is good for is visibility/discoverability.
Do not trust Microsoft ever.
They will fuck you.
* Perspective of what it’s like working in other engineering disciplines.
* A clear and shared definition of what “engineering” is.
* Experiences shared by people who do apply significant math and science to their software authorship.