Readit NewsYou can do them both with one hand.
Really powerful seeing different options, especially based on your codebase.
> I wouldn't give them a big feature again. I'll do very small things like refactoring or a very small-scoped feature.
That really resonates with me. Anything larger often ends badly and I can feel the „tech debt“ building in my head with each minute Copilot is running. I do like the feeling though when you understood a problem already, write a detailed prompt to nudge the AI into the right direction, and it executes just like you wanted. After all, problem solving is why I’m here and writing code is just the vehicle for it.
The hamburger is basically all of that rolled into one button. It's pretty abstract, you never know what's behind it and when they get fancy with animations and swipe gestures, it's almost always a failure.
I know it's a convenient way to clean up a screen, but the content in that menu needs to be absolutely optional for it to work.
* their revenue comes mostly from Google, they need to diversify
* but nobody will pay for a browser, so they need to offer other services
* then everyone criticises that they shill their other services and should instead focus on the browser
Realistically, what should they do to stop relying on money from their competitor and be continue their mission?
Kind of sounds like Arc. But nowadays we rarely get new features and when they do come out, they’re often unpolished, so I wonder if the browser has much of a future. They’d have to step up their investment in FF to be competitive for sure.
All I can say is that spite plays a big part in why I’m using FF, not good if you want to gain users and make money.
Might as well talk to a support chatbot to socialize.
The thing is, if you're not used to working with distributed state there's definitely a learning curve. Even simple things like incrementing a counter — the "hello world" of JavaScript framework demos — get tricky when dealing with multiple clients. Worse, a lot of tutorials are just like "install this library and text editor integration and boom you have an app", which doesn't give you a good mental model for what's actually happening.
So we made Learn Yjs! It's an interactive Yjs tutorial. I wanted it to be really intuitive for people just getting their feet wet with local-first development, so there are lots of explorable demos and coding exercises. The idea is to use interactive examples to build an understanding from the ground up.
Hope you like it :)
I was interested in working with CRDTs and collaboration in general for a while now and this has been the biggest issue whenever I tried to get into it. Websockets also seem a bit harder to find (free) hosting for.
Btw, your other tutorials on CRDTs were also a great help.
Personally, two years ago the topics here were much more interesting compared to today.