Over the past year, Scholarly has made significant progress, including securing funding, achieving SOC 2 Type II compliance, expanding their team, and maintaining a simple technology stack with Ruby on Rails, Stimulus, and MySQL. The decision to move from React to a server-rendered approach has resulted in better testability, faster performance, and reduced complexity. Their focus on minimizing JavaScript use has led to more reliable and maintainable code. Scholarly remains committed to their current tech stack and confident in their approach moving forward.
Table of contents
Where are we today?It’s a server-rendered worldIt’s really fastWe view JavaScript as a liability more than most codeWhere are we going from here?19 Comments
Sort: