Is this something you're seeing personally? If so, how do you know it's because of the Online Safety Act? This is a personal blog and it doesn't seem to have any adult content that I can find. The homepage of the site isn't blocked when I check it here: https://www.blocked.org.uk/check
This is a great list! A while back I also enjoyed reading “Mazes for Programers” and playing around with different maze generation algorithms from that book over a holiday break. The book isn’t super deep, but it has a fun set of projects and further ideas/reading as well. https://pragprog.com/titles/jbmaze/mazes-for-programmers/
The book starts with generating fairly standard mazes, but transitions to making more interesting ones in later chapters. There are 12 algorithms explained in the book (listed in the link above), and the author does care about making pleasant mazes.
> AI is getting better/faster/cheaper at incredible rates, but regardless of when, unless you believe in magic, it's only a matter of time until we reach the point at which machine intelligence is indistinguishable from human intelligence. We call that point AGI.
I still don’t think this is certain. It’s telling that code generation is one of the few things these systems do extremely well. Translating between English and French isn’t that much different than translating between English and Python. These are both tasks where the most likely next token has a good shot of being correct. I’m still not sold that we should assume that LLM-based tech will be well-generalized beyond that. Maybe some new tech will come along to augment or replace LLMs and that will get us there, who knows. Just because the line is going up quickly at the moment doesn’t mean it always will.
What is Office EU?
Office EU is a European productivity suite for files, email, calendars, documents and calls, built on Nextcloud Hub. It brings Files, Talk, Groupware and Office together in one platform.
Looking through the Office EU screenshots, they do look like Nextcloud Groupware/Files/Office with the logo changed.
Mostly adding this because I wasn't sure if it was a new product or not based on a first glance over the Office EU site. Nextcloud offers recommendations for providers on their site, most of which are in the EU [0]. The Office EU website seems to be new since around January of this year [1]. More managed hosts for Nextcloud is a good thing in my book, but I'd be a bit wary to host my stuff with a brand new provider.
You say "tax money", but this project isn't a government project or using public money at all. As for contributing back to Nextcloud: there is a long list of Nextcloud partners [1] that contractually obligated themselves to contribute back to Nextcloud for every user they onboard. The company in this article has not.
This is a fully local version of WordPress running in the browser. It's based on the WordPress Playground project (https://wordpress.org/playground/), and allows for editing the WordPress files, administrating the SQLite database, and doing things like installing plugins. A really handy way to play around with the platform.
I loved Christmas Lemmings so much back in the day! The snowfall visualization and the little Santa lemming clearing it. I made a much less impressive snowfall demo a while back based on that (minus the clearing lemming, because I always wanted to watch the snow pile up). https://anderegg.ca/projects/flake/
In the early 2000s I was 100% sold on the idea of strict XHTML documents and the semantic web. I loved the idea that all web pages could be XML documents which easily provided their data for other sources. If you marked your document with, an XHTML 1.0 Strict or XHTML 1.1 doctype, a web browser was supposed to show an error if the page contained an XML error. Problem was, it was a bit of a pain to get this right, so effectively no one cared about making compliant XHTML. It was a nice idea, but it didn't interact well with the real world.
Decades later, I'm still mildly annoyed when I see self-closing tags in HTML. When you're not trying to build a strict XML document, they're no longer required. Now I read them as a vestigial reminder of the strict XHTML dream.
As someone who has gotten into the idea of semantic Web long after XHTML was all the rage[0], I somewhat resent that semantic Web and XML are so often lumped together[1]. After all, XML is just one serialisation mechanism for linked data.
[0] I don’t dislike XHTML. The snob in me loves the idea. Sure, had XHTML been The Standard it would have been so much more difficult to publish my first website at the age of 14 that I’m not sure I would have gotten into building for Web at all, but is it necessarily a good thing if our field is based on technology so forgiving to malformed input that a middle school pupil can pass for an engineer? and while I do omit closing tags when allowed by the spec, are the savings worth remembering these complicated rules for when they can be omitted, and is it worth maintaining all this branching that allows parsers to handle invalid markup, when barely any HTML is hand-written these days?
[1] Usually it is to the detriment of the former: the latter tends to be ill-regarded by today’s average Web developer used to JSON (even as they hail various schema-related additions on top of JSON that essentially try to make it do things XML can, but worse).
That is a good point, if you consider XSD then that is an XML connection, it starts to become a bit complicated and I see why people start to dislike it. I forget about that because to me it’s just about the idea of a graph, which is otherwise quite elegant. Why not have a graph type-free with just string literals; much richer information about what kind of values go where can be provided through constraints, vocabularies, etc.
My favourite serialisation has got to be dumb triples (maybe quads). I don’t think writing graphs by hand is the future. However, when it comes to that, Turtle’s great.
Because the semantics of numbers and dates matters.
It's absurd that JSON defines numbers as strings and has no specification for dates and times.
I believe we lose a lot of small-p programming talent (people who have other skills who could put them on wheels by "learning to code") the moment people have the 0.1 + 0.2 != 0.3 experience. Decimal numbers should just be on people's fingertips, they should be the default thing that non-professional programmers get, IEEE doubles and floats should be as exotic as FP16.
As for dates, everyday applications written by everyday people that use JSON frequently have 5 or more different date formats used in different parts of the application and it is an everyday occurrence that people are scratching their heads over why the system says that some event that happened on Jan 24, 2026 happened on Jan 23, 2026 or Jan 25, 2026.
Give people choices like that and they will make the wrong choices and face the consequences. Build answers for a few simple things that people screw up over and over and... they won't screw up!
> Because the semantics of numbers and dates matters.
Type semantics is only a small part of what is needed for systems and humans to know how to adequately work with and display the data. All of that information, including the type but so much more, can be supplied in established ways (more graphs!) without having to sprinkle XSD types on your values.
For example, say you have a triple where the object is a number that for whatever good reason must lie between 1 and <value from elsewhere in the graph> in 0.1 increments. Knowing that it is a number and being able to do math on it is not that useful when 99% of math operations would yield an invalid value; you need more metadata, and if you have that you also have the type.
Besides, verbatim literal, as obtained, is the least lossy format. The user typed "2.2"—today you round it to an integer but tomorrow you support decimal places, if you keep the original the system can magically get more precise and no one needs to repeat themselves. (You can obviously reject input at the entry stage if it’s outlandish, but when it comes to storage plain string is king.)
You're annoyed when people are trying to keep the dream alive?
Since HTML5 specifies how to handle all parse errors, and the handling of an XML self-closing tag is to ignore it unless it's part of an unquoted attribute value, it's valid HTML5.
I'm not annoyed by it when people are trying to make XML compatible documents, but effectively no one is. Platforms like WordPress use self-closing image tags everywhere, but almost no one using WordPress cares about document validation. This ends up meaning that the `<img ... />` is just an empty gesture.
All of vintage computer emulators on the Internet Archive owe a tip of the hat to the Canon Cat emulation, because that was the computer that started me on automating the original cross-compilation infrastructure.
Author here. I was also surprised to see this getting a bunch of HN traffic suddenly. I guess the Liquid Glass hate is pretty strong when a dashed-off blog post about a real blog post can randomly do numbers! Heartened to see that others are annoyed by this design as well, though. Hopefully Apple will do something about it, but I'm not holding my breath.
I don’t know if you remember iOS 7, it was a catastrophe. Designs evolve on Apple platforms, usually in the correct direction.
Anecdotally, I have used Liquid Glass since the first beta and I honestly think there are a lot of good things there. Took me a few months but I actually like it now (and I have some colleagues in there same boat as me).
reply