panzi

Sure, I still find it fascinating.

That's more than 4 times the size of Super Mario World, I believe. Always fascinating how little is done with so much these days.

Black Mirror episode 2, IIRC.

For me:

> 503 Service Unavailable

I think the "avoid people" part does a lot of work. For a lack of a better word, AI generated people still look soulless.

Will this mean they yet again throw away their component library for Shopify apps and make everyone migrate AGAIN?

The article says LibreOffice is almost 20 years old. Well, before it was LibreOffice it was OpenOffice in 2000 and before it was OpenOffice it was StarOffice and StarWriter originates in 1985. So you could say it (or the Writer component) is 41 years old.

Even before I read this blog post only the way he behaved on The Standup made me suspicious, raised some red flags.

I'm so disappointed that The Standup was platforming him.

If I'd were 17 I'd choose a different career.

I'm not really against such special symbols, only if they are too much, like in Perl.

~ and @ weren't replaced by anything with ::, though, ~Foo is Box<Foo> and @Foo is Rc<Foo> (or is it Arc<Foo>?). :: to access a member of a module already existed when ~ and @ was in Rust.

Early Rust had ~ and @ references.

What's the public transport of software development? Where can I get good train service here?

Out of the things you mentioned I think the following make totally sense to be included in a language runtime like this:

JavaScript runtime (obviously), package manager, test runner for unit tests, bundler, JSX, SQLite bindings, formatter, linter, YAML and TOML parsers. Maaaaybe even a Markdown parser and HTML5 parser. Definitely JSON, CSV and XML parsers.

I.e. similar to Python. Though Python is a bit of an incoherent mess. If you have all these you need them to be coherent.

Just looked it up, that Apple license is indeed approved as open source/free software by the FSF and OSI!

I don't condemn the protocol. I specifically mention the buggy implementation. I say that I use X11 because KDE's Wayland implementation is so buggy.

I want to use KDE. KDE was perfect for me before Wayland. I don't criticize Wayland here, I criticize KDE Wayland. And I'm worried because very soon KDE will delete X11 support.

Yeah, but it works under KDE+X11. Wayland it the thing that changes. I think KDE has it's own Wayland implementation? kwin_wayland is what is broken, probably. Why they broke it when porting it from X11 I don't know. But the effect is the same: Can't use it as of now.

None of that matters if you don't have a HDR monitor, only have one monitor, and when absolute basics of window management are somehow broken under KDE Wayland. Why that even has anything to do with Wayland I don't know. I just know that it all works perfectly when I use KDE X11. Maybe other DEs/WMs have better Wayland implementations, I don't know.

Yeah, I still use KDE with X11 because they somehow messed up their window management with Wayland. My problems aren't even about rendering or any those features, but for some reason kwin_wayland's window management is very buggy. I'm still on 6.6 on the distribution that I use, so I don't know if it's fixed in 6.7, but I doubt it since it is here for a long time. Reported it here: https://bugs.kde.org/show_bug.cgi?id=524083

No other language that does what? Have out parameters? Many have that, even Pascal.

.env is another "simple" format that turns out to be actually a whole family of languages where each handles corner cases differently. And usually implementations quietly do nonsense on malformed input. Some even have command injection vulnerabilities. Or at least this was the case back when I looked at a few such implementations and wrote up this: https://github.com/panzi/punktum

The setup cost is basically zero anyway. Add apt repo, apt-get install the correct version. Easy to run different versions at the same time too. Upgrading is annoying.

It's something! I propose that the first 4 of those characters should in English be called Blinky, Pinky, Inky, and Clyde.

Interesting. I guess there are no well working normalization functions as there are for the different code points that can make umlauts (äöü)?

Is anyone using these characters now for anything? No youth language or online slang using it?

Andrew Wiley gently smiles, does his thing an voila!

Q.E.D. we agree and we all shout hurra

as he confirms what Fermat

jotted down on that margin

which could have used some enlarging

I see. Good to know!

What's wrong with using the title attribute for accessibility?

Also it's a different story intranationally for those of us who live in countries with much more restrictive/no fair use. Are you geolocking your software to the USA?

Yeah, or people/websites calling short looping MPEG4 videos (even with audio) GIFs.