That's why for this one, I will have to think for myself, if the fake sugar can fool my tongue, it surely may also fool my digestives organs and that should not be good.
I love it, just purchased a pack.
I've also found that it is a very great tool to test LLM, like take a screenshot of a half resolved game and feed it to ChatGPT with the rules and ask him to select the next target
I play chess on a e-ink smartphone and it is a nice break for my eyes in the evening.
I can not wait for the moment when I would be able to code on a nice colored e-ink desktop screen
OP did miss the vscode extension for claude code, it is still terminal based but:
- it show you the diff of the incoming changes in vscode ( like git )
- it know the line you selected in the editor for context
Ok so I tested it by CD into a directory, and open a file from another directory, create an empty function and selecting the function in the editor, and asking claude to just "fill the function" it knew which text was selected in which file and filled the function, this will gain me some time
The extension say "Tab awareness: Claude can see which files you have open in the editor" I don't know how to activate this, it would help me to not have to CD in the terminal each time
I use Bunny for my real estate model viewer where each visitor must download hundred of pictures
example https://icade-leblancmesnil.hive-maquette3d.fr/maquette/f5
Bunny was the best solution to serve those images fast at scale and for really cheap.
One day I was asked to take on a web development assignment.
The aim was to make the website delivered by a guy look more like the figma model.
The guy had used tailwind.
That's when I realized that tailwind is great for rapid prototyping, but if you really want something precise, nothing beats raw css.
Needless to say, the mission was hell.
By Updated I mean that more than comparing virtual DOM to real DOM.
- If you have a useEffect without dependendy, it trigger it.
- If you have some map, filter, sort, any lambda in your template, it will be executed again.
And that is true for your component and every children recursively.
"If you pass a prop to a child component, it will update whenever you change state"
Well if you update a state, every children of your component is updated as well regardless of if they have a prop passed.
I know there are way to make react trully reactive like Valtio using proxy or maybe Zustand, but my point is that useState or useContext is not "reactive" at all, you must call a function to rerender the components.
This piece of code only rerender the component as if you do a setState, in fact it does a setState under the hood, maybe the word "render" is missleading.