Front-end developer, team lead, dancer
Vilnius, Lithuania

During the day, working on projects which are interesting to me. Currently Qoorio. Balancing time between leading people and following others. Mentoring people who are making their first steps in IT.
MY TOPICS
Topic is a subject user would like to share its knowledge about.
Talk options
Choose how you’d like to meet Karolis and arrange your talk
CupCreated with Sketch.
30 min

Ask me anything over a cup of coffee
€10
MuseumCreated with Sketch.
1 h

Go for a walk around a city or a park
€15
Let's talk
Arrange a meeting with me or ask for insights on topics you are curious about
Get qoorio
Discover humans, learn & share your own knowledge
Karolis Grigas on Web developmentFront-end developer, team lead, dancerSome time ago
Current most popular way of developing web - React - is not sustainable. And that is a sentiment shared by React dev team (@dan_abramov at https://twitter.com/dan_abramov/status/1259614150386425858?s=20) and a great article at https://macwright.org/2020/05/10/spa-fatigue.html It's interesting that web development is going through a common phenomenon of circling back into old truths and a lost way of developing software. Client-side only applications are not sustainable, slow, and are only trying to emulate what a simple static html file with some styling and javascript sprinkled on top does. But it never will, purely because of the overhead of running the code, whose results should've come from backend in the first place. And that goal - static html with javascript small enough to fulfill interactivity on the open page - sounds eerly similar to how web used to be developed 10 years ago. Output some html, and manually write javascript for that page in particular. Very performant, but equally fragile and unscalable when it comes to complexity. Meanwhile, the modern tooling and developer experience for managing complexity is absolutely great. So joining these two things together sounds like a positive direction. Our web applications should serve the results of running it as the main response, with minimal post-processing needed. It should serve minimal javascript for that page, and that page only. Browsers know how to navigate, and they do it ridicilously well. At the same time, from developers experience application mental model remains what it is now - application is one, sound, and non-leaky model which can transition and resume it's state and any point, broken down into components with the same properties. It's just that these components don't return complete representations of themselves, but only minimal result in form of html, with minimal interactivity in form of javascript. The future sounds exciting.
Second-guessing the modern web - macwright.org
macwright.org
11

Appreciate
Comment
Ask
About qoorioHelp
We use cookies to personalise content, provide social media features, and analyse our traffic. We value your privacy and only use the most necessary and analytical cookies. You can opt out at any time.