Articles tagged with Web Development

A collection of articles tagged with Web Development on my blog!

If Google Forms and Sheets are not enough, Quasar's got your back

If Google Forms and Sheets are not enough, Quasar Framework is your best bet.

I’m consistently blown away by how ergonomic and beautiful Quasar’s pre-built components are. They’re also based off the Material Design specification, which makes them very similar to Google Forms and Google Sheets.

It is much faster to build a facsimile to Google Forms with Quasar than it is to build it with TailwindCSS. And at the end of the day, you have to ship.

For startups and especially side projects, there is nothing more jank but acceptable than a Google Sheet

For a lot of use cases, a Google Sheet is all you need.

You may think that you need:

  • A fancy custom user interface to gather and display user data
  • A powerful SQL database to store everything
  • A developer to create a custom solution for you

but often, you can use just a Google Form with a Google Sheet and it’s more than enough.

A Google Sheet includes (almost) everything you need. It includes robust methods to display your data. It comes with built-in filtering functions and sorting options. It even has Google Apps Script (shoutout to my script to copy a Supabase Table into a Google Sheet), which you could schedule like cron jobs, all without the headache of setting up cron jobs for yourselves. Many of these features are built-in, which saves you time and effort compared to creating your own table and styling it from scratch. These features truly are, for most people, good enough.

But perhaps most importantly of all, beyond features, Google Forms and Sheets are accessible. Everyone has used Google Forms and Sheets already. You do not need to worry about building your user interfaced from scratch using intuitive design principles, so that users can figure out how to use it when encountering it for the first time.

Think about all of the time wasted where people spend hours making dashboards and efficient ways to display their data. It’s already been solved before.

Do you really need to differentiate yourself through your user interface?

A quick rant on React I found on Reddit

I recently found a rant on React from this Reddit thread:

Vue should be more popular. I’m being forced to learn React because there are almost no Vue jobs on my country and I’m disliking it so far. I hate that to make it manageable I have to install more dependencies, form data management sucks, there’s no proper separation between logic, markup and style, css-in-js and CSS modules feel counter-intuitive and I don’t like them. React’s naming conventions isn’t good either. The only good thing I’ll give it would be passing props as function arguments and destructuring them.

Reminds me of A quick rant on Svelte succeeding React I found on Reddit, and how React sucks (kinda).

A quick rant on Svelte succeeding React I found on Reddit

From this Reddit comment:

Working with svelte, you do feel like it purposefully solved pain points in react:

-bloated syntax (svelte has succinct syntax and very little boilerplate in comparison)
-reactivity (svelte automatically has exhaustive dependencies and a simpler reactivity model in general)
-data fetching (svelte has an async/await paradigm instead of clunky useEffects + state)
-local state management (simple and intuitive syntax vs. useState)
-global state management (svelte stores are very lean compared to Redux)
-styling (svelte colocates markup and style)

It’s not a direct successor by any means, but in many ways it’s a spiritual successor, and generally very attractive to people who have worked deeply with React.

Reminds me of A quick rant on React I found on Reddit, and how React sucks (kinda).

)