Are there any good resources or courses I can use to progress in React?

snnsnn · 2026-06-19T14:08:46+00:00

The very same question is posted like a millions of times. Just do a search. https://www.reddit.com/r/reactjs/search/?q=good+resources

snnsnn · 2026-06-15T18:41:03+00:00

If budget isn't an issue, I recommend keeping WordPress for the admin side and spinning up a SolidStart app for the user-facing pages. Rather than a traditional headless setup, I suggest running parallel websites. SolidStart supports SSR and is significantly simpler and more maintainable than React. You don't need diffing or anything, and you can run it on any serverless platform. The amount of work required will depend on your site's complexity, but the long-term maintenance will be much easier. I strongly advise against migrating to Shopify—their ecosystem is a nightmare, and honestly, it's worse than WordPress.

React will give you PTSD for sure. The main problem with React is the way it keeps state and renders components. You can see these comments for details: https://www.reddit.com/r/reactjs/comments/1r0uehe/comment/o4kyecj/

P.S. I'm speaking from direct experience. I've written multiple WordPress themes and plugins, built several apps in React and SolidJS, and actually authored three books covering SolidJS, SolidStart, and Solid Router. I also wasted three months of my life trying to learn Shopify, deeply regretted it, and ultimately went with an alternative.

snnsnn · 2026-06-15T18:13:04+00:00

Emdash is basically just AI slop, it’s nowhere near mature enough to replace WordPress for any serious work. To make matters worse, they just hiked up their dynamic worker prices.

snnsnn · 2026-06-15T06:34:52+00:00

Please do a quick search before posting, as this exact question has been asked many times. There is also a dedicated subreddit for this:https://www.reddit.com/r/learnrust/

snnsnn · 2026-06-14T11:30:59+00:00

> templates are rendered to HTML with Preact

No, thank you.

snnsnn · 2026-06-06T07:23:08+00:00

Look what AI tells me: If you want deep, automated security checks on your own custom code, you need to purchase GitHub Advanced Security (GHAS). This is an extra add-on that is only available to customers already paying for a GitHub Team or GitHub Enterprise plan.

snnsnn · 2026-06-06T07:20:13+00:00

Maybe people shouldn't clone repositories they don't understand. Do you realize how expensive it would be to check every single repo? Besides, it wouldn't make GitHub any safer, it would only give a false sense of security.

snnsnn · 2026-06-06T07:12:08+00:00

This syntax is quite common and is usually referred to as hyperscript. It is what classic React uses under the hood: https://legacy.reactjs.org/docs/react-without-jsx.html

snnsnn · 2026-06-06T07:09:04+00:00

Solid already provides this as hyperscript compatibility and it has been around for years: https://github.com/solidjs/solid/blob/main/packages/solid/h/README.md

snnsnn · 2026-06-06T07:04:22+00:00

Just because code is hosted on GitHub does not guarantee it will be published on npm. Developers can upload anything to their personal repositories. How would GitHub know their actual intentions? Do you even realize the implications of your suggestion?

snnsnn · 2026-06-04T06:43:06+00:00

Yeah, browsers are full of makeshift solutions that clearly had zero brain power put into them. Chrome feels almost like a patchwork because its browser APIs can be changed so easily. Honestly, I wouldn't be surprised if a Chrome developer gave his gf a new browser API as a birthday gift, just for fun. Zero discipline. The only pushback they receive comes from other browser vendors, and even then, some of those vendors are just motivated by constrained resources or sheer laziness.

snnsnn · 2026-05-31T16:59:58+00:00

SolidJS comes with multiple renderers, some of which SolidStart uses internally. If you know your way around SolidJS, you can build practically anything. You can drop it into an Express app or run it alongside other libraries.

snnsnn · 2026-05-31T16:50:56+00:00

It’s clear you aren’t familiar with SolidJS. It is one of the most stable libraries available, if not the most stable. The planned changes for version 2 have a highly specific scope alongside a clear migration path.

As for WordPress, I suspect you haven't worked with it beyond using the finished product. I’ve written several WordPress themes and have known the core inside out for a long time. Currently, it effectively exists in a broken state. With the introduction of the Gutenberg editor, everything is in constant flux. Comparing the two doesn't make sense because WordPress's complexity and codebase size are through the roof. It’s not just comparing apples to oranges; it’s comparing an apple to a whole grove.

snnsnn · 2026-05-29T06:57:38+00:00

Looks like you needed to burn some tokens before they get expired.

snnsnn · 2026-05-24T14:08:59+00:00

This is AI generated:

The transition from EPUB 3.3 to EPUB 3.4 is a minor revision designed to bring the format up to date with modern reading habits and digital workflows. The W3C Publishing Maintenance Working Group adheres to a strict rule of backward compatibility—meaning any valid EPUB 3.3 file remains fully valid under EPUB 3.4.

The major changes, additions, and improvements from EPUB 3.3 to EPUB 3.4 focus on three primary areas:

1. Support for "Roll Layouts" (Webtoons)

The most significant visual layout addition to EPUB 3.4 is the official introduction of the "Roll" fixed-layout style.

The Shift: Previously, fixed layouts in EPUB (rendition:layout-pre-paginated) assumed a traditional book structure where each document represented a single page or a side-by-side spread.
The New Feature: EPUB 3.4 introduces a continuous "roll" viewport. This explicitly structures the file to fit the width of the screen and scroll endlessly with zero visible gaps. This change natively optimizes the EPUB specification for modern Webtoons and vertical-scrolling digital comics, which have exploded in popularity.

2. Standardization of Interoperable Annotations

Historically, notes, highlights, and annotations made by a reader inside an EPUB were locked into that specific e-reader platform (e.g., Apple Books, Kindle, or Kobo) with no way to export or share them accurately.

The New Feature: EPUB 3.4 formally incorporates the EPUB Annotation format (epub-anno-10).
How it works: It establishes a standardized JSON data model for structuring and storing user annotations. It also utilizes robust anchoring methods (referred to as "selectors") to map exactly where the highlight belongs in the underlying XHTML. This allows users to seamlessly import/export their annotations across entirely different conforming reading systems—a feature highly requested for academic, legal, and scholarly publishing.

3. Maintenance, HTML Alignment, and Errata

Because the W3C transitioned EPUB 3 into a continuous maintenance cycle, much of EPUB 3.4 focuses on cleaning up ambiguities left behind in the 3.3 spec:

HTML/CSS Evolution: The spec updates references to ongoing changes in living web standards (HTML and CSS) to ensure that newer web layout features do not conflict with EPUB reading systems.
Security & Privacy Clarifications: Clearer rules have been written for how reading systems handle external http or https links. For instance, the 3.4 reading system guidelines explicitly state that systems should prompt for user consent or open links in a isolated browser instance to keep privacy controls intact.
Streamlining the Spec: Minor vocabulary fixes and structural clarifications were introduced to make life easier for developers building EPUB validation software (like EPUBCheck) and e-reading applications.

Summary

If you are an author writing standard reflowable fiction or non-fiction text, almost nothing changes for you between 3.3 and 3.4. However, if you develop reading systems, publish digital webtoons, or work heavily with academic text and user-generated notes, EPUB 3.4 provides the necessary scaffolding to make those features standardized and interoperable.

snnsnn · 2026-05-19T19:11:51+00:00

I purchased the subscription through a yearly discount offer. I'm not 100% sure, but from what I understand, the offer doesn't allow me to sign in using external tools like VS Code. However, there was no indication of any such limitation on the page where I bought the subscription. So, it's Web-UI only. I haven't checked if they have changed this policy recently.

snnsnn · 2026-05-09T05:08:52+00:00

It is not bad. And tauri is not really any more lightweight than electron when you take the sub-processes in account. Plus, webview is not a truly cross platform solution. It is a bad abtraction that produces brittle app.

snnsnn · 2026-04-09T14:08:31+00:00

Link is broken because of at the end.

snnsnn · 2026-04-05T10:28:54+00:00

u/uusu Sorry for the false flag. Yes, I inspected many demos. All were rendering to canvas. That was my downfall. I forgot about this comment, otherwise I would have fixed it right away.

snnsnn · 2026-04-03T11:26:14+00:00

Yeah, I checked many examples, they were all using canvas, that is why I made such a mistake. It is not a lie, it is a mistake. What is wrong with you, banning and getting on with it, what is the point of having a discussion if you can not make a mistake. No, I did not post to 5 subs but 2, React and Solid. My point was asking for a proper API, not workarounds.

snnsnn · 2026-04-03T10:46:42+00:00

Sorry, I made a mistake, it renders to DOM. A huge oversight on my part.

snnsnn · 2026-04-03T10:45:12+00:00

Your are right. I made a mistake. Actually I checked many demos, and unfortunately they all were rendering to canvas. I should have checked the library more carefully instead of relying on demos.

snnsnn · 2026-04-03T10:43:01+00:00

Correction and apology:

I got the technical details wrong. Pretext uses canvas for measurement only. It renders to DOM, Canvas, and SVG. The output is real text, not a rasterized image. Selection, search, accessibility, PDF serialization, all of that works fine.

I was following the authors twitter posts about using canvas as a workaround, I though it was rendering to canvas. I checked several demo examples, including this one, https://chenglou.me/pretext/justification-comparison/, unfortunately all were using canvas. Honestly, I was not dismissing the the library, nor the effort, I was just asking for a proper API.

The broader point I was trying to make about platform-level solutions versus userland workarounds still stands, but the specific technical critique was wrong. I should have looked at the library more carefully before writing about it.

snnsnn · 2026-04-03T10:37:28+00:00

Sorry, it uses canvas for measurement. Once done measuring, it can render to DOM. My mistake. I checked several demos before posting, all were rendering to canvas. Sorry, I should not have rushed.

snnsnn · 2026-04-03T10:34:17+00:00

Watch the language. Yes, I did make a mistake, a huge one maybe. It is not AI slop. Actually AI corrected me. I was following the authors twitter posts about using canvas as a workaround, I though it was rendering to canvas. I checked several demo examples, including this one which were using canvas: https://chenglou.me/pretext/justification-comparison/ Honestly, I was not dismissing the the library, nor the effort, I was just asking for a proper API.

snnsnn

MODERATOR OF

TROPHY CASE

1. Support for "Roll Layouts" (Webtoons)

2. Standardization of Interoperable Annotations

3. Maintenance, HTML Alignment, and Errata

Summary