F

Frontside Blog

frontside.com · Company blog · on HN since 2021

Blog of Frontside, a consultancy behind Effection, writing about structured concurrency, generators and async/await in JavaScript.

What HN saysHN commenters link it to argue that generators beat async/await, and point to Effection and the team's Backstage consulting work.
19HN people shared it
5linked it in comments
19stories submitted
50story points
9 months agolast shared
2021people per year2026

Most-shared posts

  1. 1
    The await event horizon in JavaScript (2023)
    10 people · 27 points · first shared 2023 · 1 comments on HN
  2. 2
    Effection – Structured Concurrency for JavaScript
    5 people · 1 points · first shared 2022 · discussion on HN
  3. 3
  4. 4
    Deno Is “Fast” for Humans
    2 people · 3 points · first shared 2022 · discussion on HN
  5. 5
  6. 6
    The Heart Breaking Inadequacy of AbortController
    1 people · 4 points · first shared 2025 · discussion on HN
  7. 7
    Effection: For When Async/Await Is Not Enough
    1 people · 3 points · first shared 2021 · 2 comments on HN
  8. 8
    The Conjoined Triangles of Senior-Level Development
    1 people · 2 points · first shared 2021 · discussion on HN
  9. 9
    Why JavaScript Needs Structured Concurrency
    1 people · 2 points · first shared 2026 · 1 comments on HN
  10. 10
    Homepage
    1 people · first shared 2022

What HN people wrote when they linked it

cowboyd · 2024-05-05
JavaScript generators are unmined gold! We've done a lot of usage of JavaScript generators as delimited continuations; using them to implement the classic shift/reset operations in JavaScript. https://github.com/thefrontside/continuation Built on those delimited continuations is structured concurrency for JavaScript (https://frontside.com/effection)
qudat · 2024-03-01
Hi! Charles has a great article about why it's better to use generators over async/await: https://frontside.com/blog/2023-12-11-await-event-horizon/ There are real benefits to using generators over async/await so I would encourage everyone to learn more about them and their benefits.
combustilin · 2022-09-23
Indeed, Backstage is a framework for creating a developer portal, not a ready-made product. I used to work on a consultancy (https://frontside.com) who's specializing in adopting Backstage at Fortune 500s like HP. When you adopt Backstage at scale, you rely on processors that scan your LDAP, GitHub, etc to discover, stitch, and feed cohesive data to the software catalog. HP is giving a talk next month on how they manage 100,000+ entities in Backstage. Backstage does a lot of heavy lifting that I'd rather use than have to build from scratch.
kabes · 2024-05-03
Have a look at effection,which seems to share some ideas: https://frontside.com/effection
rixtox · 2024-06-28
I think React would get better developer experience and performance if they adopt language coroutine feature to implement direct style algebraic effect. In fact the React Fiber system is already an implementation of algebraic effect.[1] However, it’s “suspending” a routine by raising an exception. Thus unwinding all the call stack, therefore, it needs to re-run that same routine on resume. This is the core reason why they have a performance issue and why they created the compiler to cache values on reruns. JavaScript has language level coroutine features like async/await or yield/yield* and we have seen libraries using these features to implement direct style algebraic effect. For example Effect[2] and Effection[3]. You don’t need to memoize things if the language runtime can suspend and resume your functions instead of throwing exceptions and rerun them. [1]: https://youtu.be/7GcrT0SBSnI [2]: https://effect.website/ [3]: https://frontside.com/effection/

Keyboard shortcuts

/Search
j kNext / previous blog
EnterOpen selected blog
vVisit the blog site
fFollow / unfollow
lSwitch grid / list view
dSwitch dark mode
g hHome
g pTop posts
g tTopics
g fFollowing
g lLiked
g yHistory
g qFAQ
EscBack / close