Way back in the day I used a Windows-based backup system called FileHamster. It would watch our development server (we didn't have local copies of the code, just accessed a folder over the network). It would make snapshots whenever anything changed (every 5 minutes if something changed), as a diff. And you could roll back / forward to any snapshot pretty easily.
We also used the Dreamweaver "check in, check out" system, which would upload a .LCK file to the server with the name of the person who had a file "checked out", and warn you if you tried to edit a file that was checked out already. "<name> has this file checked out." You could override, if you had to (usually when someone forgot to check a file in before leaving for the day).
This whole system actually worked really well! When we were only working on simple PHP websites and web apps, and rarely had 2 people working on the same thing, this was actually so seamless for us ... kind of just forgot about it, did your thing, and in the rare case you needed to roll back, you just went to FileHamster, found the file(s), and clicked a button and it was back to its original state.
Of course, once we started collaborating more and working on more complex apps that actually required some code review, then we switched to ... SVN for like a month, and then git not long after.
In some ways I still miss the ability to just cowboy code this stuff, smaller stuff that if it broke, you just fixed it and moved on. Simpler days.
How would you build useOnlineStatus()?
If you said useState/useEffect, you really need to read this: https://t.co/u3psIzKGZq
If you've ever struggled with useSyncExternalStore, check that out because we go through common mistakes and questions!
@vedovelli74 Inicialmente, acho muito arriscado a decisão de um framework sem bundler e sem React. Mas, esses caras são MUITO BONS e já provaram a capacidade de criar coisas incríveis.
Que venha mais um grande projeto por aí!
@vedovelli74 Eu entendo o desânimo com as decisões do passado, mas essa decisão era necessária para finalmente separar o Remix do RR. Depois que juntaram as funcionalidades do Remix v2 no RR7, o caminho que restou foi desassociar bastante para justificar ser algo separado.
Wake up, Remix!
React Router is so good, Remix can be something totally new
I think it's going to be the best work I've ever been a part of
I can't stop working on it and my family is getting irritated with me already
https://t.co/E9YH0JcRkV
Mom iam on HLTV 😆😆😆
never did as player(one of my dreams) did as one that made a significant impact on the game that i love.
Leaving my mark in the game was allways one of my dreams aswell, i guess i achieved this, after 10 years of playing, iam so f happy xd
@HLTVorg@CounterStrike
Every time I post this, I get so many WTF's in the comments.
It's the 'string & {}' trick.
Still absolutely essential for getting 'loose autocomplete' in library code.
Yes, I understand that normies don’t understand what a URL is.
Most developers don’t understand what a URL is.
But if you take the URL out of the browser location bar we are going to burn this thing to the ground.
>be me
>"this React component kinda messy, lemme clean it up real quick"
>start refactoring
>need to refactor the thing that uses it
>then the thing that uses *that*
>accidentally rewriting the whole app
>it's day 4
>send help
Foi uma experiência e tanto. Utilizar o React Router 7 (meu framework favorito) juntamente das diversas formas de IA apresentadas no curso foi legal demais ❤️
I don't know if SQL is bad or not but losing user data in the middle of a workflow certainly is!
Did you know you can block React Router navigations in to prevent losing user data?
let blocker = useBlocker(shouldBlock)
blocker.state
blocker.proceed()
blocker.reset()
Estou acompanhando as gravações do Vedovelli e é muito legal o carinho que ele tem com o conteúdo apresentado, vai vir muita coisa inédita na Rocketseat. Certeza que esse conteúdo vai impactar muito positivamente quem assistir 💜