We seem to have arrived at a set of assumptions that states that if a large number of people like something that we don’t, or don’t subscribe to some cultural norms that we doggedly adhere to, then there has to be something sinister afoot.
The out of box experience with Omarchy is highly functional, aesthetically pleasing and challenges users to lean more on keyboard shortcuts than they’d typically be used to. That’s clever because once you’re whizzing around with these shortcuts you feel accomplished, productive, and that generates loyalty towards the distro.
None of this is a bad thing, anything that makes Linux more accessible and interesting is good. Bucking trends that were making Linux harder to adopt or less culturally relevant is good too.
To be fair, losing your job in America is a lot scarier than in most countries; especially when your whole industry is affected and your skill set has become obsolete. There’s not much of a social safety net to catch you.
AI companies are hugely motivated to show beyond-human levels of intelligence in their models, even if it means flubbing the numbers. If they manage to capture the news cycle for a bit, it's a boost to confidence in their products and maybe their share price if they're public. The articles showing that these advances are largely junk aren't backed by corporate marketing budgets or the desires of the investor class like the original announcements were.
You don't need a driver to read that kind of data anyway, so your concerns are moot. Once you install any application on your PC, there's not a lot that it can't access.
I’d recommend using something like Tailscale for these use cases and general access, there’s no need to expose services to the internet much of the time.
That's an incredibly naive perspective. KLA represents a real risk to companies, as something going wrong can crash player computers instead of just game processes; this is a PR nightmare if/when it happens on a large scale. Not to mention the cost of hiring engineers capable of building kernel components in the first place, it's a niche skillset that's not cheap to hire for.
Games companies don't turn to KLA out of laziness, it's out of absolute necessity, especially for games like FPS' where it's impossible to fully secure the game using pure server-side methods. Machine learning has been tried, it's too prone to false positives and misses more subtle cheats that still negativel impact the the player experience. Anti-Cheat used to exist purely in user mode and then, guess what?, cheats moved into the kernel where they couldn't be detected or stopped. Anti-cheat had to follow in order to remain effective.
The alternative was conceding the space to cheaters and watching games that players love, and that required massive resources to develop and maintain, degenerate into a hellscape of cheating that real players refuse to play.
In this case I think it's a little different. People are saying that they don't want to have their own productive or creative output used to undermine their own standard of living. That's not the same as simply not wanting to have your job automated away by someone else's business innovation.
I'd consider myself to be one of these developers. I don't blog, I don't Tweet, and my public GH contributions are sparse at best. I'm a fairly senior engineer in a large company. What bothers me about this post is the idea that I must be lagging behind on using the newest technologies just because I don't Tweet about it?
Conferences, in my experience, are mostly a waste of time. I can usually watch the keynotes online after the fact if I care to. I'm not interested in joining discussion groups and posting; like the vast majority of people, I'm content to lurk, but I'm not blind!
So yeah, I'd be very comfortable challenging a light-visible developer on pushing/using new technology and generally being aware of the landscape. I just don't care to talk about it constantly.
VAC probably sets up a hardware breakpoint conditioned to trigger when the start of that memory region is read. When triggered, a function registered via AddVectoredExceptionHandler will be called. It probably just sets some flag somewhere indicating that the memory region was accessed before resuming flow. You can guard entire pages of memory using a similar approach (https://dzone.com/articles/memory-access-breakpoint-large).
Your conflating harming people with causing them anger is very much part of the problem. 'Harm' used to mean something much more severe; now it basically means anything at or above pissing someone off.
The same concept creep has occurred when it comes to the word 'violence' too. As a society, we long ago drew red lines at behaviours that are violent or harm people, but thanks to these deliberate redefinitions, extreme responses are somehow justified to utterly non-consequential speech, because people accept that speech can cause 'harm' or is 'violent'.
It's such a cheap rhetorical trick that does nothing but chill public discourse while doing nothing to positively impact the lives of the people it's ostensibly supposed to protect.
I like this idea, however I think the event ID being encoded in the response body places constraints on what each element looks like. Perhaps it would make more sense to encode the last ID/feed position in a response header and have the client submit that in a subsequent request header? That would decouple the feed position from any one element or the response structure itself.
The out of box experience with Omarchy is highly functional, aesthetically pleasing and challenges users to lean more on keyboard shortcuts than they’d typically be used to. That’s clever because once you’re whizzing around with these shortcuts you feel accomplished, productive, and that generates loyalty towards the distro.
None of this is a bad thing, anything that makes Linux more accessible and interesting is good. Bucking trends that were making Linux harder to adopt or less culturally relevant is good too.