Absolutely beautiful story thank you so much for sharing.
I don't mind AI translation at all. The style comes off as a bit weird indeed, but I just took it off as a style I'm not used to because it comes from a different culture than mine. I wouldn't mind much the naysayers, I'd like to see them posting something in chinese and see how they'd like it ;)
I really enjoyed the writing style actually, all these different anectodes condensed in shorter sentences, without fluff or trying to connect them in a single narrative. Maybe this is not the correct way to put it, but I'm also not a native English speaker nor I have any classical training in writing.
Yours is the first substack I ever subscribed to and can't wait to read part two. It actually pushed me to start writing some of my childhood experiences.
I'm not sure if you are implying that you aren't using remix anymore after the rebranding, or that it's not a framework anymore?
Because React Router 7 definitely works as a framework [1] and it works like a charm.
Source: Backend developer with 15 years experience, lately switched to full stack, using RR7 after advice from a very good friend, still getting amazed every day.
This is amazing. I started playing it with my morning coffee and somehow it became 1pm...
Despite what other people commented, I really liked not really knowing what happens with some (most?) of the updated and having to try them to understand what they do and how to combine them. The last part is especially true: it was just SO SATISFYING when I realized that a perk I hated became my favourite once I was able to pair it properly and catch waterfall of coins :)
One thing I still don't get at all are the white and red ball "paths" that briefly appear from time to time. I don't get what they represent nor how are they triggered, especially as it doesn't look like the ball will actually do that exact path after it hits the puck (if I don't move it). It's a little annoying for the red one, that resets your coin counter, because I can't understand if I can avoid it somehow or do I have to take it as a "random debuff".
One of my hangups to start strength training at the ripe age of 41, is that I'm terrified of hurting myself.
Apparently to do "proper" strength training you need to focus on the free weights, or compound lifts, rather than gym machines that guide your movements. I.E. squats, deadlifts, bench presses, etc.
The problem is that these are EXACTLY the type of exercises that an untrained, anterior pelvic tilted computer long-time dweller will do wrongly as they don't have the right flexibility or skills or knowledge about how to do them right.
I remember how close I was to messing up my back permanently with deadlifts, and that was in my 20s. Thinking about going to the gym and starting doing them again unsupervised at my age is, to me, madness.
I really wish if someone could give me some advice in this matter...
My understanding was that's meant to be a way "ordinary people" () can contribute to the project by seeding one or more torrents with a part of their archive contents, to try and achieve a sort of "distributed backup", and it's not meant as a way for final users to get that one book they need.
() that is, people that can't run a IPFS node or other advanced options due to their limited space/network/skills/money.
BTW Your "Advanced ESP32 development with ESP-IDF" guide [1] is the best "getting started" guide I've seen so far. Up to now no guide has been so clear and complete, and I've spent one week being very frustrated by how confusing the official ones are.
So thank you again. You made me rekindle the spark of creativeness that got buried by age and daily grind.
> Today, I’d like to close this gap with a couple of crisp definitions that stay clear of flawed hydraulic analogies, but also don’t get bogged down by differential equations or complex number algebra.
Related: many, many years ago, when Facebook didn't exist yet, Google still passed as a "good" company, and hobbyist electronic geeks had almost only PICs to choose from, I found online a very long and complete electronic course that went from 0 to basic R/C concepts, to transistors, up to pretty advanced topics like magnets/transformers and IIRC radio too.
It was made of pretty raw HTML pages and images, and what was most peculiar about it was that it managed to explain a lot of concepts up to an applicable level (as in, actually designing analog circuits) without (any?) calculus at all.
Some of those may be false memories, but if I remember correctly:
* Its HTML style had a yellowy background
* It was taken from an old-ish (US?) navy electric engineer-focused applied electronics course for training naval engineers.
* It was more focused on analog circuits
I remember I downloaded it all but after all those years who knows where it could be. Maybe in some 1GB disk of my first Pentium PC, so it's basically lost.
Does anyone in HN knows what I'm talking about? I was never able to find it again.
I have this using Firefox on a 2019 Macbook Pro with 16GB RAM.
If the laptop has not been restarted for a while, Firefox tabs will eat up more and more memory over time until it makes the mac kind-of unresponsive (*) and will need to get hard power cycled.
The only signs that this is about to happen are two:
1. Any audio-emitting webapp will start to get very choppy, whether is youtube on FF, Google meet on chrome, or a slack call/huddle. Which is the problem I think you are referring to.
2. Switching workspaces animation will get very very choppy. Usually when this happens it's already almost too late.
(*) this means that while the pointer is still moving smoothily, even from a BT mouse, there is no reaction to any click or keyboard typing.
I didn't know this existed and as someone who is in the process of buying a new ride this is great! I can now have a pretty good idea how my position will be on any bike.
However, I have no idea of what I should strive for when looking at the angles? Are there some well-known ideal values I should look into?
It explains how we got there, the problems we are facing, the problems inherent to the proposed/possible solutions, etc.
(*) as in, they really try hard to stay neutral on the topic until the end, in the clearly marked conclusions and opinion section.