> Although not perfect, [Sound Canvas VA] is the closest recreation of the original SC-55 in software form as of 2023.
Ah, this submission should have a “(2023)” added to the title. In 2024, Nuked-SC55 (https://github.com/nukeykt/Nuked-SC55) was released, which is a fully accurate software emulation of the SC-55/SC-55mkII (it relies on having the original ROM files).
You could be presenting the most carefully-researched information in the world, but with such an obviously vibecoded site I'm not going to attempt to read it.
FrontPage didn't generate your content for you! So there was no reason to assume a FrontPage page might be meaningless just from how it looked. For AI-generated sites, though, if the page looks like slop, is it worth bothering to figure out if it actually is slop? It's not like they're uncorrelated variables. Sure, occasionally it won't be. But I'm drowning here. I must simply assume that if someone is serious about conveying a message, they won't package it in this form.
I don't think it's even gatekeeping. You could copy-paste two tables and write two sentences into a Word document and export to HTML, one of the laziest possible ways to produce a website, and it'd still be less off-putting because it doesn't have the association with slop content.
You could be presenting the most carefully-researched text in the world, but with such obviously machine made paper I'm not going to attempt to read it.
Even if the information is accurate, I'm calling it low effort slop... Smart LLMs have basically automated producing a plausible looking "content farm".
The "Windows Classic" look on XP is exceptionally ugly, because those 3D-rendered icons just do not belong on a Windows 2000-style grey background for menus or buttons. (I have recently had to test both these OSes in VMs…)
That is true, it looked completely off, as if no one really bothered to tests it and make it look nice. It got rid of the horrible window decoration of the default theme, but the start menu looked terrible.
There's such an avalanche of blogposts on HN constantly saying relatively similar things about AI, that it would be really nice if they were all just filtered down into lists like this occasionally.
It needs a more coherent cogent discussion, leading to dare I say it sane _policy_ ... which the frontier model companies and hyper-scalars are not incentivized to finance, and governments too slow and weakly funded to finance.
Other topics we seem to have been unable to have deep and informed discussion on, leading to sane policy :
- inequality / taxation
- demographics / aging population
- climate change mitigations
- affect of social media esp on young people
- safety of self-driving cars
- economic impacts of LLMs
- educational "" ""
- security "" ""
- surveillance of in-home devices
- data collection and sharing
- right to repair
Failing to react rationally to a rapidly emerging global pandemic a few years ago should have been a wake up call but wasnt.
If the technorati are woefully unprepared for the age of AI, which is being rapidly thrust upon us by the big money, then the wider public dont stand a chance of being informed / prepared.
I'm not sure if this quite answers your question, but the difference in philosophy here is that C++ objects with pointers always have identity, whereas a Rust object only has identity if it has a non-zero size. It's an application of the zero-overhead principle, "you only pay for what you use".
> whereas a Rust object only has identity if it has a non-zero size.
Rust also has the complication that function pointers are not guaranteed to have an unique identity; If multiple functions compile to the same code, the compiler is allowed de-duplicate them.
The documentation [0] also warns it's also possible for the compiler to create multiple versions of the same function. And while I've absolutely seen the compiler to create multiple optimised versions of functions in disassembled code (partial inlining based on the caller), I'm not sure it's possible to get pointers to more than one version.
This is why C++ doesn't have ZSTs, it wants all objects to have identities, the obvious way to distinguish them is by where they are in memory, but ZSTs don't have distinct addresses in memory.
I'm not a C++ expert. Why does C++ want all objects to have identities? Presumably it has some feature or something Rust doesn't have that requires this?
It's pretty deeply tied into C++'s object lifetime mechanics, which rely on storage being available and reserved for the use of that object's lifetime. If multiple objects with valid lifetimes had a situation where one lifetime needs to end, what should happen to the other objects' lifetimes?
C++ actually did end up evolving the ability to define a zero-sized class without a unique memory address, but mostly to allow optimizations like the empty base optimization to apply in other situations where it could make sense, especially with templated or constexpr code.
> C++ actually did end up evolving the ability to define a zero-sized class without a unique memory address
Did it? Are you talking about the no_unique_address attribute (I had to go look that up because WG21 apparently doesn't care about consistently using or not using separators in attribute names) ? That attribute lets you do the same trick as empty base class but without the ceremony, however it doesn't let you make ZSTs.
Yes, that's what I'm talking about. It does expand on the empty base object optimization, though it is still not fully generic.
But you can now have multiple zero-sized types as siblings in a struct or class that can be zero-sized, the restriction is that they do have to be different types.
But that's just not ZSTs. All C++ is doing is, as with EBC you can overlap a thing which doesn't need any representation with any number of other such things and with the no_unique_address attribute C++ will say their total size is 1.
C++ is bad at type arithmetic, that's nothing new. Rust has unit types like () which have size zero, and it has empty types like ! [aka never] which do not have a size because no values of these types exist. C++ struggles with this, if you attempt a unit type you get a type with a single byte that's all padding, thus size 1, and you can't write an empty type at all.
…but make sure you keep on top of your domain renewals, make sure they can renew automatically, and make sure there is a backup email address that isn't on your domain that can be used to get into your domain registrar account.
(You probably don't need to ask how I know. I am very lucky that there was a grace period after my domain expired, where I spent a few days not realising why I wasn't receiving any email any more.)
> Per Secretarial Order 3453, Lake Ontario has been renamed to Lake America. The basemaps for GNIS are in the process of being updated to reflect this name change.
This is fun to read, but there are some odd quirks to the text that I would hope wouldn't slip past an editor, and the way some of the Christian aspects are talked about feels bizarrely partisan for an academic text (it gives the impression the author might be Catholic). I wonder if it is just clumsiness.
“The Great Chain of Being” that the author mentions is an idea that dates back to Aristotle and Plato, but it developed into the concept described in the article under medieval Christianity, before the Catholic/Protestant split.
I agree the article presents it a bit weirdly, like a fact of existence. But I can see how it makes sense in a discussion of taboo, since as the article points out, taboos applied differently at different “levels” of that chain.
If the author had included a sentence or two to contextualize it, it might have helped - but he probably expects that the audience already knows about it, and (one hopes) wouldn’t take it literally. But it’s difficult to tell for sure.
The EU is responsible for a lot more than that once you factor in emissions in other countries producing goods bought by people and businesses in EU countries.
Ah, this submission should have a “(2023)” added to the title. In 2024, Nuked-SC55 (https://github.com/nukeykt/Nuked-SC55) was released, which is a fully accurate software emulation of the SC-55/SC-55mkII (it relies on having the original ROM files).
reply