Only talking about relatively new technologies, what is most appealing to you? Why do you want to learn it?
This post is part of the Mayfield + DEV Discussion series. Please feel free to go back and answer previous questions as well.
For further actions, you may consider blocking this person and/or reporting abuse
Oldest comments (54)
Supabase stands out. New open source alternative to something proprietary in Firebase, but also built on top of something I'm quite comfortable with in Postgres.
Haven't had the chance to play around yet, but it hits a sweet spot for me.
Putting this one on my list to test out for sure.
Make a post about it if you do!
Putting it into Notion now so I don't forget 😁
On the first look it seems like Supabase has no vendor lock in because it is open source but it actually is lock in because very important features are Supabase Cloud exclusive and not part of Supabase. Very sad.
I really recommend learning it. Currently using it for a real project and it has been awesome.
Also check out Thin Backend, it's similar to supabase but provides optimistic updates :)
I'll stick to the old stuff :P
Proved and tested is also a great way to go!
I´ve been dreamin with three.js everyday....
Machine learning, cause of its capability to solve many problems (if implemented fairly) for people.
I don't have anything new* in mind at the moment, I'm focusing on improving my current skills at the moment. I jumped between to many technologies, frameworks, libraries etc... a couple years back. It's was interesting and learned quite a bit, but it was a bit of a mess for my mind xD
For me it's Remix.run this year. My last three freelancing gigs I've done in Next.js and I think it's time to remix things a bit ;)
Seeing a lot of that
Wow this landing page (on mobile at least)!
For me is PWA! I love the concept, when I have some free time is the next thing I will learn!
Channel
Why Progressive Web Applications Are Not Single Page Applications (2019)
Beyond SPAs - alternative architectures for your PWA (2018)
Service worker rendering, in the cloud and in the browser (2021)
Service Worker Side Rendering (SWSR)
Pascal Schilp ・ May 6 ・ 8 min read
PRPL Pattern
Thanks!
Prisma ORM
thin.dev/
I was tinkering with the idea of abstracting backend for simple apps and seeing this in action kinda validated that idea 😅
I want to try out frameworks that take a different approach in delivering content - I mean, if you use the popular meta frameworks for building web*sites* (with only little interactivity compared to apps), they all nicely SSR your HTML, but hydrate once again on the client, which is pure overhead, if your site doesn't need full blown SPA interactivity. The hydration step requires much data to be serialized into json. So duplicated content will be sent over HTML and JS. Plus, we need to take into account that it both takes time to download JS and parse JS and execute JS, which is blocking the main thread..
For building websites I want to check out Qwik, which is super new, and Marko.js, which is not new at all :)
Plus, I wanna check out Go!