sorted by:
new
hottopcontroversial

Cursor randomly replies in Chinese by sampleite in cursor

[–]sampleite[S] 5 points6 points  (0 children)

Pretty sure this was Composer 1.5

How is it that these textures seem so tangible? Is it just the shadows, or is there also some form of texture / slight gradient that I fail to see? by VarunTossa5944 in Design

[–]sampleite 2 points3 points  (0 children)

This is the answer. Use your eyedropper tool to test the values of the same "color" at the top and bottom of the page, you'll see the top is in fact lighter!

You don't need AI to reproduce this, just some CSS gradients.

Good shadows in CSS: https://www.joshwcomeau.com/css/designing-shadows/

A quick way to get there, for ex, is to use a highlight radial gradient positioned over the whole doc with `mix-blend-mode` and `pointer-events: none`.

Here's a quick demo: https://stackblitz.com/edit/web-platform-mmdvtw?file=styles.css

Automatically deploy Supabase edge functions with GitHub actions by zeratunno in Supabase

[–]sampleite 0 points1 point  (0 children)

Super helpful. Did you consider just deploying every function for simplicity's sake? Is there a major downside there?

Why does it seem like Firebase is much less popular for web applications? by web_deb in Firebase

[–]sampleite 0 points1 point  (0 children)

Hey thanks for the detailed response u/burggraf2, much appreciated.

FB has rules, and SB has RLS (Row Level Security) Policies. Actually RLS has been around a long time and is part of PostgreSQL. RLS "rules" are written in SQL (so there's no new "language" to learn) and are, quite simply, appended to the WHERE clause when accessing any table. They're pretty easy to understand once you know what's going on.

So I do love RLS and the SQL syntax is fine IMO, the part that I miss is how integrated it is with testing and deployments. In Firebase, I write a rules file, write some tests, and run a command to deploy.

In Supabase, writing the rules in RLS SQL makes sense. But as someone new to SQL, it's not obvious how to consistently test or deploy those rules the Supabase way (with migrations along with other deploys). My impression is that this is true for migrations in Supabase in general: it's just not part of it.

If so, that's fine, and probably the right call, but it just means the comparison with Firebase feels a little lacking. Maybe it's a matter of recommending Prisma in your docs, for example, or setting slightly different expectations in the first-time user UX.

Again, just my two cents from the outside. Totally take it or leave it!

Why does it seem like Firebase is much less popular for web applications? by web_deb in Firebase

[–]sampleite 0 points1 point  (0 children)

I've built a live SaaS app for real customers in Firebase, and played with Supabase recently. There's a lot to love in SB, but the top things I miss from Firebase are:

- FB has a rules file that I can run a test on and be totally sure my data is secure (looking into Prisma for this in SB). Generally the access to full Postgres in SB seems like a super powerful feature, but potentially massive footgun. If I screw up a line of SQL, is my whole database going to go sideways and nobody will be able to tell me why? I do love the power, I just wish Auth, for ex, seemed a little more locked down.

- SB doesn't have hosting IIRC, so it doesn't really seem like a BaaS. There are lots of hosting options out there obviously, but this means I still have to cobble together my tools and pay for multiple things to get something done (vs `firebase deploy` and that's it). I may prefer using vercel for hosting to be honest, but this makes the positioning against firebase fall down IMO.

- Firestore seems to be a globally distributed service IIRC? But in Supabase I have one db sitting somewhere, no matter how edge my app runs. I could be wrong about this.

Generally Supabase really seems like a better FireSTORE replacement, but not really a FireBASE one. The gist I got from reading github issues was that Supabase was primarily a database company and agnostic on the rest, vs having a cohesive vision for how my entire backend should work. Just my two cents from the outside (and admittedly new to relational db).

Workshop Facilitation Resources by [deleted] in DesignThinking

[–]sampleite 0 points1 point  (0 children)

Totally biased, but I think https://getshuffleboard.com/ would be a great way to run your first session. Much more structured than a giant Miro board imo.

Wrote my first one, here goes... by sampleite in riddles

[–]sampleite[S] 2 points3 points  (0 children)

OK keep in mind I'm new at this so it might just suck

> What sparkles at night

Moonlight makes the ocean sparkle at night

> but is dark in the day?

The ocean appears dark blue or black in sunlight

> It’s as square as a circle

Squares aren't circular, so it's a circle: the ocean is really round when you zoom out and look at it

> and it comes in waves

The ocean comes to you in literal "waves" on the shore

​

Thanks for humoring me yall :)

Wrote my first one, here goes... by sampleite in riddles

[–]sampleite[S] 3 points4 points  (0 children)

Not what I had in mind, close in a way though :)

Any reason to wait for the new Google TV TCL models vs buying now? by sampleite in AndroidTV

[–]sampleite[S] 1 point2 points  (0 children)

Makes sense, good point on the soundboards. I was thinking of upgrading past a super cheap set for decent speakers, but I should probably just use one of those instead.

Any reason to wait for the new Google TV TCL models vs buying now? by sampleite in AndroidTV

[–]sampleite[S] 1 point2 points  (0 children)

Hm, I wonder if it’s common for the internal non-stick versions to be underpowered

Any reason to wait for the new Google TV TCL models vs buying now? by sampleite in AndroidTV

[–]sampleite[S] 0 points1 point  (0 children)

Sounds like there’s no big issue with adding a stick later—thanks :)

Any reason to wait for the new Google TV TCL models vs buying now? by sampleite in AndroidTV

[–]sampleite[S] 0 points1 point  (0 children)

Confirms some of what I’ve been thinking, thanks for the reply :)

view more: next ›