I'm not well read, and don't think I'd be able to finish any of the classics. As such I have no clue what "slipping from prose into a soft Iambic pentameter" means. I came here for the robots.
You know how in Disney movies they shift smoothly from talking to singing? It’s just like that, only instead of the bass beat to the character’s song starting to play, her ‘prose’ (think ‘non-poetry words’, aka what most people consider books to be full of) shifts smoothly into Shakespeare-like syllable emphasis patterns. Listen for the percussion notes starting about ten seconds into https://youtu.be/79DijItQXMM and imagine that instead of him bursting into musical song, he burst into chanting a limerick:
There once was a demi-god, Maui / Amazing and awesome: I’m Maui // Who stole you your fire / and made your days lighter // Yes, thank you, you’re welcome! Love: Maui
It’s a bit odd of an analogy, but limericks and “Iambic pentameter” are specific instances of an underlying language architectural thing, so it should be just enough to convey the basics of that “prose to Iambic” sentence. And: if you’ve ever watched “Much Ado About Nothing” from the mid-90s, that’s 100% Iambic.
(If you’re an English major, yes, I know, this is all wrong; it’s just a one-off popsicle-sticks context-unique mindset-conveyance analogy-bridge, not step-by-step directions to lit/ling coordinates in your field.)
This is a great example, and not odd as an analogy at all. It surfaces something subtle.
Language architecture is really interesting, I think, for programmers who have bought into the LLM hype in any meaningful way. It's an important field to have a sense of.
Tokenizers, for example, generally have multi-syllabic tokens as their base-level, indivisible unit.
You rarely see this mentioned when LLM capability against non-coding tasks is discussed, despite it being deeply important for prose construction.
Not to mention, putting language models aside, that the vast majority of code is written in language with a logical grammar. The disciplines are highly linked.
I wonder as a resident being forced to pay for this, and therefore part owner, whether I'd be within my rights to first tape over the cameras, and then "accidentally" break it...
/s
Actually I'd likely seriously consider this exactly. Who's making the money here. The residents are paying for it. The building management must be getting paid by both the residents and that parasite company that produces this shit.
I think visual signs are an amazing way to impart immediate information at a glance. Take road signs for example, at speed I can know what to expect around the corner.
However it is another language to learn and as such needs standardisation to be useful. If I go to another country and start driving the road symbols mean something else.
Its the same in the GUI. The symbols should allow me to move quicker around the interface, even if I've not used the software before.
The issues I see are each OS/App can, and does, use their own symbols for the same functionality (sure there are some universals like cut/copy/paste). And like the article these symbols now appear to be getting used as bullet points, so each item needs it's bullet points.
In my opinion, and like the greyed out keyboard shortcuts over to the right of some menu items, these symbols should only be there when they denote actions that can be done by clicking a button. They should be imparting the mouse equivalent or those keyboard shortcuts, a way to navigate and do actions; not as some decoration. Imparting the language of the GUI.
So yeah I agree with the article. Function over design aesthetic every time.
> However it is another language to learn and as such needs standardisation to be useful. If I go to another country and start driving the road symbols mean something else.
A lot of countries seem to standardise on similar signs. I have not had a difficulty driving in different countries and visiting more.
Cars are even more standardised. The controls vary very little.
There is a definitely problem with GUIs and the problem seems to be aesthetics and branding trump function.
No. Which is why "the only exception is macOS" is also false. At some point Apple drops support for that model and then that hardware not only gets no more driver updates, because the whole system is tied to the rest of it, it gets no more updates at all.
So the only exception is systems with open source drivers. Those are basically supported as long as the hardware architecture is and enthusiasts even have the option of adding support themselves. You can install the latest version of many Linux distributions on the first generation of x86-64 hardware from 2003 and some on 32-bit PC hardware going back to the 1980s.
It should literally be a crime that you can't do the same thing on a five year old phone.
My point is that with macOS, Apple writes the drivers which means at least as long as the hardware is supported you can be pretty sure that there will be prompt fixes for any issue. With Android, Windows or closed-source Linux drivers (cough NVIDIA) you're left entirely at the mercy of whoever made the tiny little component controlled by the driver to provide a fix, which then has to bubble up through the ODM/OEM until it finally appears in an update you can install.
If you want fast responses to driver bugs, you only have Apple or a fully open-source Linux systems as an option.
I can't see how the situation with apple is any better considering what you've said, you're still beholden to apple to provide a fix. Even if that fix might be quicker coming IF apple is currently supporting the device; not at all otherwise.
> I can't see how the situation with apple is any better
Because in the Windows world, there often are no updates after maybe 1, 2 years. Chances are high, if you look in Device Manager of any reasonably new system, you'll find a lot of drivers dating back to before Covid and that's 5 years ago. Chances are even higher that if you look close enough, you'll find something being exploitable.
With Apple? Their track record for support is around 7 years.
If you have macOS, it's supported until the OEM (Apple) stops supporting it. If you have Linux with some proprietary driver, it's supported until the OEM (e.g. Nvidia) stops supporting it. If you have Linux with open source drivers, it keeps working pretty much indefinitely.
Meanwhile 10+ year old hardware is serviceable for many uses. A 15 year old machine from the scrap heap could have 64GB of RAM, a different one could have a low idle power draw for a use where that's the only thing that matters. Put a cheap SSD in a machine of that vintage and someone who is just using web and email could keep using it for the rest of their life.
The question was asked in good faith, not as a set up for an argument. I'm sorry you feel put upon or need to become defensive about a honest question...
This looks good. I'm currently enjoying nushell. I like the built in http server and appreciate the built in mysql functionality. For me though sqlite would be a better fit for a language like this, small and portable that it is.
Sometimes simplicity passes complexity into the user. One of the reasons I'm likely nushell is the built in functionality, for example, the ability to natively open CSV,JSON,XML,etc files.
Can I confirm that you need to write your content as valid JSON? Because if that's the case I can't think of anything worse.
I can't really get a feel for what this actually is/does from the landing page. Terms like "Growth Engineers" and "Automate lead magnet generation." Don't help. I've no idea what a growth engineer is or what those 4 random words combined into a sentence means, or how it relates to growth engineer.
I don't see anything here that would make me move away from pandoc/quarto...
reply