lexx

I read on my mobile. If I fall in love with a book then i buy a physical copy for my library.

Same with music and record collection.

I want my kids to be able to browse my stuff and discover the previous decades as I did with my parent's collection

So, the author suggests to look out for a specific trait in programmers. To care about the essence of what they actually work on. I agree but why the need for the terminology

Svelte is brilliant. The new things you have to learn are minimum. New devs can be productive since day one. I don't know why I would ever want to use vue or react.

That's the best recipe to favorite tribalism. No thank you. New age patronizing is as old as humans. It's just that the current humans think it's new

I love my Linux desktop. More than 10 years I exclusively work on i3. Wouldn't change it for anything.

Now also USB audio just works

This is a really nice idea and I love the execution as well.

Congrats and thanks for sharing.

For those that want to make their canon work in linux, check this guide

https://maximevaillancourt.com/blog/canon-dslr-webcam-debian...

I've done exactly the same with a canon dslr. Everybody asks me if I am a streamer

Many are jealous, i think. It's hard to understand through their poor webcams haha

i really love your website

If they don't say they value privacy and freedom, what are they?

The interface and overall feeling reminded me of the internet 15 years ago. I like the vision, not the execution. What I didn't enjoy is that it's really slow.

How is this concept different from reddit though?

I love both products. Not currently using them, but thanks guys for warming my heart

I am in the exact same situation for the past 2 years. My mood is vastly improved. The social media isolation aspect is as important as the social media socialization aspect to me. Not important.

The people I want to talk to are on discord or signal, and we do actual activities together

I don't think such a monolith can exist. That's my point

Yeah, I get that and it happened to me too. That can happen in any design though. Even with a microservices approach.

As I said in the previous comment, you have to design your way out of the thing you are building. Not easy at all, and sometimes, not possible to predict.

I mean successful companies do grow, but a lot of times they pivot, etc.

True, that is also very funny in my opinion. It's our need to play with new toys that makes us over-engineer stuff.

As I get more experienced, I try to find the easiest, most profound solution to a problem. At the same time I "design" escape scenarios. If that business will scale in that x way then I will be able to do y. Most times the need for scale never comes.

You can't reason about solutions when the problem is not defined.

Of course a monolith is a great choice for a team of 4 devs for example. It could be great even for a team of 20 devs. But when you have 30 teams of N devs, then the monolith maybe is not the best idea.

Businesses scale in different ways, and different stacks exist for this reason.

I think this is a great comment. I totally agree

you reminded me of this one https://news.ycombinator.com/item?id=30191729

btw restql seems dead

You could give a POST /custom/query with only read capabilities. Also you can give some custom "helper" operations along. And certainly you could give them some option to prettify the response. Because one thing is to query the correct things, another whole thing is how to structure the response according to your needs.

I didn't know Restql. thanks for the link

One solution is "Persistent Queries". Other solution is to throw a Varnish Cache and cache the hell out of POST requests :P

Is it elegant? No.

Do you have another service to manage? Yes

Will you pay someone else to do it for you? Possibly

I think there are already products trying to do that. But how many layers of abstractions and dependencies are you willing to have in your everyday processes?

You are right. Some things are just hard. I went deep into Graphql because I wanted to explore the possibility of it being an more comprehensible interface for the end user in comparison to a REST interface. In such cases, it is not.

Graphql gives a better way to request nested schemas and handle relationships and recursion. But when you cross that line, the client now would get ideas and starts asking "Why not be able to do that operation on the 5 level deep object?". Now you have to either not allow the client to do that, or you have to "rewrite the database" to make recursion optimal.

This is not a problem of Graphql. This is an HTTP problem. When you need to promote the database querying layer over HTTP, then you have a problem regardless.

I am also considering woriking with Neo4j for a project.

I am wondering why not build on top of their Http Api? You can send multiple Cypher statements over Http and correct me if I am totally wrong, but "stealing" the concept of graphql's persistent queries, you could make use of http caching also.

I would love read your thought's on that

I agree with you. I am currently working on a project that need to give very sophisticated querying capabilities, so I'm kind of seeing everything from that prism.

I've found that this is a simple and effective way to handle relational data either in REST or Graphql. But imagine having to traverse trees, filter on data of different types and levels. Sort and filter on edges. I mean it can get pretty complex and I am not saying that REST would be easier on those complex cases.

In my opinion graphql and rest can both be super cute in simple everyday queries. But I am thinking that people are creating databases like postgres, mongodb, neo4j, etc, are doing exactly that. Trying to give us the power to query our data efficiently. Why not be able to expose directly the database and just add a layer for security, control, decorating and other stuff that would add value. Why rewrite databases?

GraphQL is a great experience when you consume it and the service fulfills your query needs. Because you just ask stuff and you get them. It's really cool.

On the other hand, when you are the one to implement the Graphql server, it feels like writing your own database. You have to create a query plan, handle optimizations, corner cases, etc.

Also if you really want to provide a graph experience, with inverse connections, filter on relationships and other advanced stuff... get ready to burn your mind and your soul.

haha, me too

I just add to the conversation. There are great points discussed. No reason to repeat them. I just add

On the plus side. 54k know and use this project not because they have it starred. So it will regain the stars rapidly, and it will again hit all the trending metrics, so new people will discover it also. No biggie