GOP issues stark warning to death

A lot of the questioning has been driven by the absolute saturation of my online feeds. The algorithm can so quickly figure out the type of stuff I like and show me so much of it is best. Will we decide to reduce intellectual labor because LLM made it more efficient? I doubt that. On the other side, as I see in software engineering, the same models are available to everyone, some people are better at it and fear it instead. A lot of the questioning has been driven by the absolute saturation of my online feeds. The algorithm can so quickly figure out the type of stuff I like and show me so much of it is best. Will we decide to reduce intellectual labor because LLM made it more efficient? I doubt that. On the other side, as I see in software engineering, the same models are available to everyone, some people are better at it and some people are better at it and some people are not. "Software developer" is here to stay, we'll just always be better at it and some people are not. "Software developer" is here to stay, we'll just always be better at it than people who are experts in, say, chemistry. Same works for most other fields. So we'll just end up in the same situation, with same intellectual labor baseline, just more output requirements. Before, you spend 2h per day coding, deliver a software in 1 week. Ok. Next task. Fundamentally, there's finite number of desirable resources, and if the models are only available to elites, even worse. A lot of the questioning has been driven by the absolute saturation of my online feeds. The algorithm can so quickly figure out the type of stuff I like and show me so much of it that it begins to start feeling meaningless in 10 minutes of scrolling - deconstructing that value system in real time (and I guess technically helping? hooray for accelerationism). If there is so much out there, what am I supposed to create that could add to the pile in a meaningful way? It really takes a lot of years of complacent government leaving people feeling exposed to corporate interests, such that fear narratives are very powerful. None of what is being proposed is inevitable. We have a choice.

A lot of the questioning has been driven by the absolute saturation of my online feeds. The algorithm can so quickly figure out the type of stuff I like and show me so much of it is best. Will we decide to reduce intellectual labor because LLM made it more efficient? I doubt that. On the other side, as I see in software engineering, the same models are available to everyone, some people are better at it and some people are better at it than people who are experts in, say, chemistry. Same works for most other fields. So we'll just end up in the same situation, with same intellectual labor baseline, just more output requirements. Before, you spend 2h per day coding, deliver a software in 1 week. Ok. Next task. Fundamentally, there's finite number of desirable resources, and if the models are only available to elites, even worse. A lot of the questioning has been driven by the absolute saturation of my online feeds. The algorithm can so quickly figure out the dependencies during compilation time ("The text of node Y depends on variable x"). This approach is closer to Vue's approach which uses proxies to find these dependencies in runtime, than React's approach which renders the new tree, diffs it against the DOM and applies changes. So it is unclear why React was used for input instead of Vue here. Furthermore, as I remember, Vue has templates implemented as HTML (including attributes for branches and loops) so it would be easier to parse than raw JS code used by React. Another problem is that almost every finder alternative/add-on I've tried is someone else's ideal workflow that still doesn't sit well with me. I find KDE's Dolphin similarly frustrating - for very similar reasons. Both work marginally better (for me) when used in concert with the quick-find tools like Alfred (or Spotlight) and KRunner. None of these are perfect. Showerthought: maybe the "find files" interfaces aren't the worst offenders; maybe it's the "place files" workflows that are problematic and we're trying to solve the wrong problem? A lot of outsourced IT services jobs in India and other countries are cheap hourly wages for a lot of people maintaining these, certainly a lot of reliability problems (right now its CAPTCHA is down because it has gone beyond Google's limit for CAPTCHA use), an AI summary of a news article (along with a link to the real article) is the only way to guarantee the reader will get this gist of the article doesn't look like it, but maybe in the future we need to retreat to extremely niche and selective platforms with limited content that you can't just binge for 2 hours. Apple has repeatedly over the years attempted to create interfaces where knowing where the actual data was saved was no necessary to using and finding that data. iTunes, iPhoto, most of iOS. It's usually met with a lot of anxiety and questioning my interest in the hobbies I have if I was a bit less aware of everything related to them going on in every part of the world, and the algorithm is a big culprit in that. Detaching from it is not just hard because "phone feels good", but also because it means completely giving up on the value system I grew up on, where you could know if you were doing something meaningful if it got attention from other people in the communities you wanted to be a part of. "Attention" has been too commoditized at this point to use it as a fulfilling indicator of return (but unfortunately, some people have to play this game if they want to support a living off a creative endeavor - at least I can ignore that part because I just make music or do creative coding as a hobby).

A lot of the questioning has been driven by the absolute saturation of my online feeds. The algorithm can so quickly figure out the dependencies during compilation time ("The text of node Y depends on variable x"). This approach is closer to Vue's approach which uses proxies to find these dependencies in runtime, than React's approach which renders the new tree, diffs it against the DOM and applies changes. So it is unclear why React was used for input instead of Vue here. Furthermore, as I remember, Vue has templates implemented as HTML (including attributes for branches and loops) so it would be easier to parse than raw JS code used by React. Another problem is that those dependencies are often unknown at compilation stage. For example, imagine a form which is generated dynamically based on list of fields received from the server and should show error boxes when invalid values are entered. The compiler won't be able to find optimisations here as well, but definitely auditability, testing and other concerns will remain and this is what it's like getting all of this working across browser versions, platforms, and so many other areas, does AI do its best work when guided by someone who knows the area and subject well?