Live data from Hacker News

Viewing profile — Princesseuh

Princesseuh

HN member
Joined
Sat, Oct 06, 2018, 3:14 AM UTC
HN karma
76
Public activity
20 items

About Princesseuh

No profile information was provided.

Recent public activity

  1. comment
    Comment #48885396

    Hello, I'm the maintainer of this. Let me know if you people have any questions / comments :)

  2. comment
    Comment #48826669

    We don't intend on removing support for the unified ecosystem, we on purpose made the Markdown processing pipeline pluggable so that it was possible for both to exists! The vast ma…

  3. comment
    Comment #48825428

    If you are using every single feature Astro has, your code somehow goes through every single branch (of every single dependency), etc then yes, but that'd be a pretty far-fetched s…

  4. comment
    Comment #48825353

    Love everything you do Steve, consider that I've done it for you

  5. comment
    Comment #48824201

    Yeah, the parts rewritten in Rust here as only parts of the bottleneck. A lot of it is still JavaScript (including the user's code!). If Astro was just .md -> HTML, it'd of course …

  6. comment
    Comment #48823218

    It was tough to create a plugin API that was both performant and intuitive. Especially since the library people were migrating from (remark/rehype) was very laissez-faire in regard…

  7. comment
    Comment #48822935

    This was actually part of the reason I made the Rust markdown processing, the unified ecosystem is a lot of deps! I still have some plans in this area that should reduce the overal…

  8. comment
    Comment #48822699

    It was partially that, but mostly the Vite version with the Rolldown bundling etc. We typically always need to do a major whenever Vite releases one because it tends to impact us a…

  9. comment
    Comment #48822440

    It depends in what regards you mean, I have some benchmarks here if you'd like to take a look at those: https://github.com/Princesseuh/web-markdown-benchmark The TL;DR is that `mar…

  10. comment
    Comment #48822330

    This does not affect remote content, only the content written in .astro files. If you have remote content you'd use something like `set:html`: https://docs.astro.build/en/reference…

  11. comment
    Comment #48822126

    I made the Rust compiler and the Rust Markdown pipeline ( https://satteri.bruits.org ) in this, let me know if you have any questions, glad to answer anything!

  12. comment
    Comment #48078874

    Zed has semantic highlighting: https://zed.dev/docs/semantic-tokens It was added a few months ago if I remember correctly.

  13. comment
    Comment #47847248

    Not intending this to be an ad, but a friend of mine has been working on a changesets-based tool that has native polyglot support: https://github.com/bruits/sampo Hopefully easier …

  14. story
    Show HN: Sätteri, high-performance Markdown pipeline for JavaScript

    Hello! I work at Astro ( https://astro.build ), where we do a lot of Markdown / MDX and performance in this area is often a bottleneck. Our users use a lot of plugins to process th…

  15. comment
    Comment #45568359

    Working on Maudit, a Rust library to make static websites. Emphasis on library instead of framework. I aim that you could integrate Maudit into existing Rust apps, building pages i…

  16. comment
    Comment #45533399

    Thank you! Let me know if you have any questions or encounter any problems, always happy to help.

  17. comment
    Comment #45526893

    Ah! Thank you for taking interest. At this time there's no built-in way to generate RSS feeds, you'd need to use a "Endpoint" route and return a .xml from it: https://maudit.org/do…

  18. story
    Show HN: Maudit, a Rust library to build static websites

    Hello! Maudit is a library (not a framework) to build static websites. What this means is that a Maudit website is a normal Rust project, pages are normal Rust structs and so on. T…

  19. comment
    Comment #39439879

    Prettier does not support Astro files natively, so it's the Astro plugin's fault in this case. (I maintain said plugin, so, well, it's my fault)

  20. comment
    Comment #18342826

    Wouldn't it be better to show the intended font at first page (using font-display: swap or fallback instead of optional) instead of a potentially uglier fallback font until second …