tempaccsoz5

The actual Mermaid ASCII renderer is from another project [0]. This project transliterated it to typescript and added their own theming.

[0]: https://github.com/AlexanderGrooff/mermaid-ascii

Engines other than v8 exist. React Native uses Hermes or JavaScriptCore (Apple/Safari). [0]

Other engines include SpiderMonkey (Mozilla/Firefox) [1] and QuickJS [2]

[0]: https://reactnative.dev/docs/javascript-environment

[1]: https://spidermonkey.dev/

[2]: https://bellard.org/quickjs/

Have a look at the Steam Hardware [and software] Survey [0] results. Linux has been trending upwards whist Windows has been trending down for a wee while. And the population this looks at is primarily interested in gaming, which means that this is despite a compatibility layer being needed for a large amount of the software used. I imagine in other communities (software, old people) it's trending much faster.

E.g. I recently installed Linux Mint for my grandma so she could use email and an up-to-date web browser on her old laptop that can't run (secure) Windows anymore. The UI differences are marginal for her, and she can do everything she needs to much better than she could before (which was not at all).

[0]: https://store.steampowered.com/hwsurvey/

They're real bugs all right - have you ever tried to search a gmail account via apple mail?

So the protection is that debit cards take longer to pay out to merchants? An increased window to dispute charges doesn't strike me as innovative but more like an arbitrary variable from the CC company.

This varies a lot between countries and cultures.

For example in New Zealand, EFTPOS cards are very popular (similar to debit cards, but issued directly by our banks so no user fees ever - the merchant pays for the machine and that's it). People usually have all 3 - an EFTPOS card for most in-person purchase (although online EFTPOS is gaining adoption), a debit card for online or paywave-only places, and a credit card for large purchases/ emergencies. Credit cards here are highly unpopular among the under-25 age bracket; most young people just have EFTPOS and debit.

I think this might be a result of our stricter banking regulations compared to economies like the U.S.; it's difficult for banks to offer tempting enough rewards schemes to entice people to credit cards. Additionally, there is much less of a borrowing culture - most people will only ever properly borrow money once - buying a house. Paying cash for cars is the norm, and purchasing anything else on finance is seen as stupid compared to just saving the money (and earning the interest yourself).

TimeLine maintainer here. Their demo for live-streamed data [0] in a line plot is surprisingly bad given how slick the rest of it seems. For comparison, this [1] is a comparatively smooth demo of the same goal, but running entirely on the main thread and using the classic "2d" canvas rendering mode.

[0]: https://chartgpu.github.io/ChartGPU/examples/live-streaming/...

[1]: https://crisislab-timeline.pages.dev/examples/live-with-plug...

The same website says that as of 2024, it is slowly being reconstructed: https://www.oskarjwhansen.org/news/2024-hoover-dam-star-map-...

Source for this stat?

Now, with our ALL NEW Agent Desktop High Tech System™, you too can experience prompt injection! Plus, at no extra cost, we'll include the fabled RCE feature - brought to you by prompt injection and desktop access. Available NOW in all good frontier models and agentic frameworks!

This still wouldn't be perfect of course - AIML101 tells me that if you get an ML model to perfectly respect a single signal you overfit and lose your generalisation. But it would still be a hell of a lot better than the current YOLO attitude the big labs have (where "you" is replaced with "your users")

So a trivial supply-chain attack in an npm package (which of course would never happen...) -> prompt injection -> RCE since anyone can trivially publish to at least some of those registries (+ even if you manage to disable all build scripts, npx-type commands, etc, prompt injection can still publish your codebase as a package)

The example in this article is prompt injection in a "skill" file. It doesn't seem unreasonable that someone looking to "embrace AI" would look up ways to make it perform better at a certain task, and assume that since it's a plain text file it must be safe to upload to a chatbot

Even if you don't fully retrain, you could get what's likely a pretty good safety improvement. Honestly, I'm a bit surprised the main AI labs aren't doing this

You could just include an extra single bit with each token that represents trusted or untrusted. Add an extra RL pass to enforce it.

Also cool that when you open it in a new tab, the svg [0] is interactive! You can zoom in by clicking on sections, and there's a button to reset the zoom level.

[0]: https://questdb.com/images/blog/2026-01-13/before.svg

This is missing the best part of windows 8/metro - the glow around the cursor. I found it really fun playing with how the glow highlighted smooth sections of tile borders as well as illuminating the whole tile. IIRC it also affected window borders, etc. Very fun to play with.

Seems that OpenCode is YC-backed as well [0] [1]. I would've thought YC would encourage better cyber security practice than OpenCode have demonstrated here.

[0]: https://www.ycombinator.com/companies/sst

[1]: https://anoma.ly/

Hilariously, a link given as an example is now effectively broken.

https://github.com/styleguide/templates/2.0, cited in a comment cited in the article now just redirects to a style guide landing page with no context.

I guess it depends highly on what you value. I dislike site that eagerly load all their images below the fold, since on my mobile phone I have a metered data plan. Unlimited data is still uncommon or very expensive in many countries. For example I pay $13/mo for 650Mb of data, which is one of the best value plans (under $40/mo) from any provider.

Their structure in the markup can be a bit confusing imo - something more like a <figcaption> inside a <figure> or a <legend> inside a <fieldset> would be much nicer imo.

The spec even mentions [0] that you're allowed to use <div>s to group dt/dd pairs for styling purposes.

[0]: https://html.spec.whatwg.org/multipage/grouping-content.html...

I once tried to try Raku years ago, but I was left really confused by the website and docs.

Clicking through the code examples on your new website, I kept being amazed at some of the great things Raku does. It's night and day in understanding the uses and purpose of the language! Thank you.

Unfortunately, as soon as I click into the "introduction" section of the docs I'm abandoned to a wall of links and am once again lost. I'll try persevere this time, but I think you could do adoption of Raku a great favour by working on organising your docs site a bit more clearly. Astro's docs are an amazing case-study on best-in-class docs layout and writing: https://docs.astro.build/en/getting-started/