kabes

Article resonates with me. I'm Belgian and moved to work in SF in 2016.

I really hated it and it took me a long time to admit this, because it felt like failure.

I moved back 2 years later and the upside is that I now appreciate Belgium, my friends and family here way more. Before I was just focused on moving away to what I thought was a better place.

tl;dr author discovered blue/red problem, then went on to discover coroutines and likes coroutines better. Same old discussion, nothing new.

But Yup also allows to infer types from schemas...

Are we still overwhelmed by js? I almost only see TS code these days.

Then just an ever increasing number like most browser do these days would make more sense.

I was way more likely to succeed the faang tech interviews coming straight out of university than I do now after working for 10 years.

But I do think I'm a way better software engineer now than back then. So something is broken with that interview process.

No, because

1. It's a fight you can't win

2. It might allow me to finally build the ideas I have. I have better things to do than striking a keyboard all day.

I can't wait for AI to replace me.

From skimming through the site, it's not clear to me how the BE looks like. Obviously, the BE part is the hard/interesting part. Is that open-source and/or self deployable? Or is this fixed to a backend-as-a-service you guys provide?

So from your explanation I get that they use webrtc for videos. But then what do they use http over webrtc for? Do they serve the UI as well over webrtc?

Tech is more than social networks though

It says one of the big differentiators with 'traditional workflow orchestrators' is that is supports cyclic graphs. But BPMN (and the orchestrators using it) also supports loops.

It's hard to believe one of the highest valued companies in the world cares about being shamed for not having open source drivers.

Yeah. I think mobx is often disregarded as mutable state goes against the react philosophy. Instead they somehow rather make monstrosities of codebases (redux anyone?) just to avoid it.

And mobx is really just signals everyone now loves automated via proxy objects.

I've been in mi-26s a couple of times (friend of mine used to have 3 of them in storage) and up close it's almost unbelievable the thing can fly.

It's mostly a change from js to go and rust. For older tools it's harder to migrate towards rust/go because of their ecosystem (plugins etc) being build around js.

However, vite currently consists out of a different build tool for prod and dev (rollup and esbuild). And they're working on replacing both with the new rust based 'rolldown'

I found it very frustrating that in the recent Belgian elections, because the EU and local elections were combined, there was very little debate on this subject and EU programs in general. Luckily it was finally brought up in the media (although way overdue IMO)

It also increases blood flow to the scalp, which helps against hair loss.

Except, the alternatives he presents aren't alternatives.

And for each issue he mentions that rest doesn't have said issue is basically because rest doesn't have the feature at all.

You could use graphql the same way as rest (by exposing queries without allowing to specify fields) and you still have a better rest, since at least the response has a schema out of the box.

True, but rest calls over multiple micro services is even worse

Have a look at effection,which seems to share some ideas: https://frontside.com/effection

How much value has flutter created for Google?

I don't get the argument that you don't know when react will rerender, as that hasn't fundamentally changed since react v1

I know a miter joint, a box joint and dowel joint. But what is a mitered box joint with dowels?

I remember back when I lived in the US, I got daily spam calls. I never get spam calls in Europe. I wonder why that is and if that's still the case (lived there between 2014 and 2018)

What's the point of acquiring them instead of just sponsering the project? I'm trying to understand supabase's angle here and if this is good or bad news for non-supabase postgres users.

I think lexical is the future

Lexical is more of a framework comparable to prosemirror. Learning curve is therefore higher, but IMO way more flexible and better designed than quill.

Do you have more info on the GIS improvements in PG15?

You can say this about most things in the standard library. But as stated in the motivation, there's an ongoing trend to extend the rather small standard library js offers, so you don't need to have a package for each and every common task.

You can argue about the need for this, but if we're going to extend the standard lib, then looking at what is popular is a good approach IMO.

> Before these libraries used signals, they or their predecessors used virtual DOM

Signals are not a replacement for virtual DOM.

Signals are also just pub/sub, but with a more ergonomic api. More ergonomic because listeners are added and released automatically.

It can also be more performant, eg, say you have a computation that depends on 2 values:

`result = a ? b : 0`

Then if a is falsy, we don't need to recompute if b changes. This is achieved automatically with signals, but would require quite some code with classic pub/sub.