A closed container called the wood-slatted crate is in the Gazebo. "A bizarre crate sits
in the center of the gazebo." The crate contains a croquet mallet. The crate is openable.
Instead of taking the crate, say "The crate is too slimy to pick up." The description of
the crate is "A strange object, covered in muck and slime, but it looks like it can be
opened." The description of the mallet is "Just your usual croquet mallet."
(I wrote some of this on top of a demo program included in the documentation)
It's so cool and magical. I wish there were more programming languages like this.
These are simply facts, all verifiable from credible news sources and open source sources (and no, I'm not your librarian, I'm not going to do your work for you). If you don't like facts, unfollow and mute me and don't respond to my twts. We are long past the time of being gentle with people who refuse to look at reality.
I guess I'm old school because I still use
dc
╰─ dc -e '49 2o p'
110001
Anyway, that's my yarn for today.
I built the user interface in scalajs--first time I've used it--using the Laminar library to wire up all the reactive stuff. I made heavy use of the Scalably Typed ecosystem because I wanted to use Mapbox GL for maps and Pixijs for an animated, interactive map overlay. I used the Laminar bindings for the SAP UI5 web components for all the non-map user interface elements. There are some other choices, mainly libraries to help with time, geometry, and geospatial calculations, that I'm not listing.
This was my first large scala 3 project.
This:
> But my emails are just not delivered anymore
is just plain misleading. I hear this a lot about self-hosted email. But I have been self hosting my email for about ten years and as far as I know my email is always delivered. I've only had a problem one time and that was readily fixed.
I have MX and PTR records as well as SPF and DKIM records. I believe these are what make email deliverable reliably. It's a bit of a pain to sort out but once it's done it's done.
Who is Artemis? NASA's latest mission to the Moon is named after an ancient lunar goddess turned feminist icon
1. Cramming as many people as possible through "coding bootcamps" on the promise that anyone can learn to code and get a high-paying job in a few weeks
2. Companies largely using the frontend as branding and spyware, as opposed to useful applications
1. means that people learn to copy-paste from Stackoverflow or use libraries, because a bootcamp does not teach language fluency. 2. means there's corporate pressure to focus on visual design and surveillance at the expense of all else. People are given little time to design good application code, even if they had the skills to do that, which I posit the majority most likely don't.
I mean, there ought to be many ways for people to support themselves and their work/art/videos/what have you, not just sticking ads and promotions all over everything. There's no reason to consolidate around that particular model at the exclusion of all others.
defer call automagically be part of io.Copy or the open function built-in?
jupyter plugin that makes calls out to a local jupyter notebook and puts the results in your note, and it's great. However, this plugin had a peculiar set of supported languages, which made me suspicious. It turns out it makes network calls to some server to do the code compilation and running, and then grabs the results and puts them in your note. No way!!!
- Lots of opinions, many of which aren't cited and probably not super accurate (e.g., that Java is the reason for the rise of OO programming, when Xerox PARC, Sun Microsystems, Smalltalk, Alan Kay, etc etc led to Java and other things)
- His rant about OO programming is really about Java (and its variants). Smalltalk is quite a bit different. Objective C is too.
- The Actor model more or less fits his notion of what OO programming is, yet is hugely successful
- He imposes a bunch of arbitrary rules on OO programming based on a rigid understanding of what objects, states, and encapsulation mean. He then uses this to argue that messages can only be copies of state, not real state; that for one object to send a message to another object it must hold a reference to that object; that objects aren't allowed to have references to anything; etc.
- "The Most Important Programming Video You Will Ever Watch" <--- no, never say this about your own stuff it makes you sound like a crackpot