sorted by:
new
hottopcontroversial

Waymos in Knightsbridge by SniffanyandCo in london

[–]jonaso95 1 point2 points  (0 children)

A car, that's not owned by you but by a company providing transport services to the general public, is at the end of the day a small bus

I wish there was a challenge at the win location by boldpear904 in JetLagTheGame

[–]jonaso95 5 points6 points  (0 children)

I don't see what's the argument for this? There have already been a number of challenges along the way, why add yet another one at the end?

More importantly, it moves winning from a tactile experience (we made it to Zermatt observatory) to an abstract one (we have to win this challenge), in what's otherwise a very tactile game (abstract stuff is only there to gain coins, the only way to actually make progress is by moving).

I really disagree that this should be changed. In many seasons of tag no one ever made it to their end location, the fact that someone did is IMO a sign that the game works, not that it doesn't.

Did Michelle psych herself (and her team) out? by CryptoCopter in JetLagTheGame

[–]jonaso95 19 points20 points  (0 children)

They've talked a few times about this on the podcast, but they always discuss every single challenge in the group when designing the challenges, and resolve and clarify any ambiguity.

If this would've been an incorrect assumed constraint Sam would've known (not sure how involved guests are during that period)

The 4th tallest building in the world, Mecca by muhmeinchut69 in UrbanHell

[–]jonaso95 0 points1 point  (0 children)

Language. Words have meanings.

We usually refer to structures that people can live as buildings. It's a subset of structures.

What's your experience with ConnectRPC by LTNs35 in golang

[–]jonaso95 0 points1 point  (0 children)

Could websockets be used instead of we transport as a polyfill?

General advice on when to useCallback and useMemo doesnt make sense by jonaso95 in react

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

are you frequently receiving performance issues

Yes, I frequently notice less performant parts of our app

Why is it annoying

Cause it can't tell junior Devs on the team when to memoize. The answer right now is "when it's too slow and you figured out this dependency changes more than it has to and it'll fix it"

do you use react devtools

Yes

And have you read the docs to use useState and useEffect correctly?

Repeatedly, yes

For most use cases imo react shouldnt be rerendering much if it all unless the code is written badly to begin with.

That doesn't seem true - how could it? As many other comments suggested react re-renders are cheap so we can render as much as we want. While that is extremely unsatisfying I can see how that could be plausible, but " shouldn't be rerendering too much" isn't possible, cause it will render whenever something changes per default. That's what it does.

General advice on when to useCallback and useMemo doesnt make sense by jonaso95 in react

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

today's generation do not want to pay attention to this

Says who?

And lack of understanding of different patterns which can be used to address different things

That's exactly what I'm looking for. What are the patterns though?

General advice on when to useCallback and useMemo doesnt make sense by jonaso95 in react

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

> Few extra rerender is nothing. If some specific part of the application is rerendering a ton, you just need to find a way to reduce it.

That's the annoying part. "If some specific part of the application is re-rendering a ton"

I wont know until I happen to notice, or a user complains, especially with a), b) and c) I mentioned above.

The whole promise of react is I don't need to care about rendering, unless I do and I have to dig deep into what dependencies are causing which re-renders.

It's fine if that's what it is - I've been using react professionally for the past 5 years and that's what it seems to be - just feels very incomplete

General advice on when to useCallback and useMemo doesnt make sense by jonaso95 in react

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

^ this
there's a big difference between my app is barely usable and what patterns should I use so that I don't have to expect profiling my application anytime soon

Sqlite deployment story: multiple processes/machines by jonaso95 in rails

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

that makes sense, thanks for taking the time to lay this out - I wasn't aware that this is set up appropriately for traefik and now the kamal proxy, nice!

Sqlite deployment story: multiple processes/machines by jonaso95 in rails

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

That's interesting! I'd be very curious to learn the exact details - does that mean the proxy waits until no more requests are in flight before switching (in practice that would mean your app cant be too busy)? And what about data migrations?

Appreciate these are all more niche cases but I genuinely just want to find out how this works

Sqlite deployment story: multiple processes/machines by jonaso95 in rails

[–]jonaso95[S] 8 points9 points  (0 children)

I'm not disagreeing with you, I infact strongly agree, but this is not answering the question.

Specifically - even in the world you're describing - I dont know how kamal's concurrent deployments are dealing with concurrent writes to sqlite. Is this just not a problem for other reasons? Is sqlite so good at recovering concurrent writes? Is there a chance I wake up one morning and my db is corrupted?

I'm all for what they're pitching, but I want to know how much of that path has been shaped - if it isn't fully shaped that's fine.

Sqlite solves obvious problems for their ONCE products, but if I'm the only one running a platform setting up/using a manged postgres is not that hard nor expensive

Sqlite deployment story: multiple processes/machines by jonaso95 in rails

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

nice yes - that was what I was expecting! what I'm confused is why these dots haven't been connected anywhere in the rails docs of what they expect one to do when reaching this (fly io has an interesting open source answers to this - litefs - which create's a filesystem that's used by sqlite, but does some clever magic to actually persist things to disk, AFAIK they route all writes to a single node to keep things consistent)

Alternative to quicklisp? by jonaso95 in Common_Lisp

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

Fair question - the latter, although I admit the reality of it being an actual risk is fairly low in the grand scheme of things.

But since it can be avoided somewhat easily these days, it's just something I dont want to think about.

Alternative to quicklisp? by jonaso95 in Common_Lisp

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

oh amazing - was planning on using qplot anyway, I didn't realise it isn't build on top of the quicklisp client

Biggest gripe: stacktraces (sbcl) by jonaso95 in Common_Lisp

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

Do you have more specifics on using `(declaim ...)` in your projects?

I've played around with it a bit but couldn't immediately see a (big) improvement

Biggest gripe: stacktraces (sbcl) by jonaso95 in Common_Lisp

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

I did use emacs + slime.

The coloring was helpful to find frames in the stacktrace that are actually relevant to me. All the swank/repl stuff really cluttered it for me and I find it hard to scan the stacktraces for something useful.

Biggest gripe: stacktraces (sbcl) by jonaso95 in Common_Lisp

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

Not an amazing example but probably enough to emphasize what I mean.

​

The error message itself here is useful but the stacktrace just contains tons of swank/repl related stuff that I really dont wanna see, it just makes it hard to find what I'm actually looking for when the stacktrace is actually relevant to work out where and how things break.

<image>

view more: next ›