Agreed. I tried to dig around a bit in the pdf (though I am admittedly distracted at the moment) and it looked like a tree walk interpreter being built. At least at first. There were some sections involving x86 assembly, so it may eventually compile down to that architecture in later segments?
If anyone knows more about the style of copmiler(s) that this covers I would be interested in knowing. If I find the time to dig through the book a bit more and find out I'll update here.
The link styling system used on the wiki complies with all web accessibility standards: it clearly and consistently shows a link without using color as the sole determining factor. An underling is not required (whether you think it should be or not, though feel free to get involved, join a working group, and lobby for the change to your hearts content... though I think it will be an uphill battle for you). Accessibility standards are about helping those with disabilities. What you are experiencing is a difference of opinion about _usability_. I personally do not experience the same usability issues, but to each their own on that one. Accessibility and usability are two very different things and should not be conflated.
> Accessibility and usability are two very different things and should not be conflated.
Nope. They are the same. It's a taxonomy of convenience.
I do not care what W3C says about this.
Example: If you have something with say clean typefaces it may be considered more usable unless the person has low vision or dyslexia then it's accessibility. The labels are easily swappable and there's tons of learning and attention disabilities people have (most people are probably not cognitively perfect).
What if you add an elevator to a building with a bunch of stairs. That's accessibility for the handicapped but also usability for others and thus we've swapped in the opposite direction.
You can take everything labeled usability and relabel it accessibility with a slightly different narrative and the reverse is true also.
The distinction therefore, in this context, is illusory. It's not an actual material difference here, just a fiction.
In scholarly research sure it's not the same. But in the material world without the clinical precision of scholarship, they are in practice always intertwined.
And this is fine, I don't care. A taxonomy of convenience is still a convenient taxonomy. Let's not kid ourselves however...
If you dont care about the standards, which governments use to define how accessibility works and who it applies to for legal purposes, then you essentially want to make up your own rules, policies, and ideas. Which is fine, mostly. However, it doesn't really give you solid ground to stand on when making an argument about other people's work. The fact is that according to the recognized "experts" on the subject (I'm using recognized here because again, governments use these standards and they have legal merit) there is nothing wrong with these links. There is, however, something wrong with conflating accessibility and usability. They are different. One applies to protected classes. The other has to do with everyone, but is in no way protected. There are legal ramifications to one. With the other, you are maybe a jerk for doing things against usability, but if it is equally bad for everyone, it often is not an accessibility issue. Accessibility is about leveling a palying field, usability is an opinion based thing regarding how a random person might interact with a website and usually relates to design decisions, not programatic experiences.
> Example: If you have something with say clean typefaces it may be considered more usable unless the person has low vision or dyslexia then it's accessibility. The labels are easily swappable and there's tons of learning and attention disabilities people have (most people are probably not cognitively perfect).
If it's equally a problem for everyone then it's not an accessibility problem.
(And don't think for a second that any design avoids causing problems.)
The link styling is inconsistent with basically every other web page; underlines haven't been "everywhere" since the late 1990s (for better or worse), but distinguishing links has usually been done via the use of color, maybe some other border effect.
The style chosen by this particular web page comes across not as hyperlinks, but as a weird choice to randomly remove words and phrases from the main sentence matter, rendering them more difficult to read and comprehend, and worse, leaving the reader unaware this this choice actually denoted a link.
Using color alone to distinguish links is explicitly an accessibility violation. Underlines are not a requirement. I certainly agree that the link system here is atypical. It just isnt an accessibility violation.
I have not been on an official tilde server (I wouldnt join because they have a code of conduct which I think infantilises adult humans)... but I am on a few pubnixes (circumlunar.space, rawtext.club, colorfield.space) and know a large number of folks that do not align with social and economic left values on these servers. Honestly, most of us stay out of political discussion on the servers and mostly talk about tech or sometimes philosophy (which can have political elements to it). Anecdotal, of course, so ymmv... but so long as you arent being a jerk to other people I've not seen any issues with people having diverging views of those sorts on these servers (at least the ones I have been on).
That seems reasonable to me. Small groups can be easily torn apart bad bad actors. Even well meaning folks that just don't vibe well can really hae a large effect on small intentional communities. It isnt about being good enough, by my reading, it is about a good fit.
Different standard library, different focus, similar-ish core interpreter. However, it doesnt need to be different. This was not built for folks other than me and a few friends to use (I didnt post it here on hacker news, and am not looking to "grow a userbase").
macros werent necessary for me and the language is for me. I can always add them later (as the other comments mention). Not having them makes things simpler and easier for those with less programming experience that don't need power features. Those that end up needing them can always move on to scheme, clojure, common lisp, etc.
I would agree. Simple and old school, but with a dash of modern features was what I was going for. I used Logo a good bit when I was young, so I can appreciate the comparison.
Because at one point filter was implemented as a special form in the interpreter rather than in the library. As such it was colored with special forms. That has changed and it is now in the library, but I have not gone into the highlight plugin to switch the colors as it is not a high priority.
If anyone knows more about the style of copmiler(s) that this covers I would be interested in knowing. If I find the time to dig through the book a bit more and find out I'll update here.