stsquad

Ecosystem is the key thing here. It's a hard thing to go from cute embedded nonsense hacks to standard firmware booting distro cdroms/usb sticks and "boring" installs with strong upstream support. I've watched this first hand from the Arm ecosystem point of view and I don't know who or where this work is being driven from for RiscV. Defining the ISA is really just the first step.

I use foot which is Wayland aware and renders Unicode fonts. Honestly I don't need much from the terminal itself as I'm usually in tmux to deal with all the "tabs" and scrollback.

I wonder how much of the core has been changed to prevent rebasing onto a more recent QEMU? We've done a bunch of cleanups and additions too the x86 emulation since 7.2.

Does this use the same attention architecture as traditional tokenisation? As far as I understood it each token has a bunch of meaning associated with it encoded in a vector.

To be honest you wouldn't need to blow much up. ASML have staff on site at part of their support contracts for the lithography kit. I doubt they will hang around if China occupied Taiwan and I suspect license keys would quickly expire. The jobs at TSMC are highly skilled so you won't just be dropping in mainland staff to replace anyone who fled or got killed during the invasion. Even if they get the plant limping along the yields are likely to drop and there would likely be no Western customers for an appropriated fab plant.

In short there are lots reasons invading a country to seize the means silicon wafer production is not likely going to work. I also doubt China see manufacturing as worthwhile spoils of war, a decision to invade is more likely going to be driven by ideological motives.

While I've been updating open street map I've also taken the time to report right off way violations via my councils web portal. The problem is most of the paths around here are permissive national park paths and there is no canonical catalog available digitally to cross check against. I don't know if they should also be registered as a right of way?

I guess these batteries are going into buffers rather than cars. How do they compare work energy density and cost to the liquid sodium batteries?

Quite. Servers aren't free and someone needs to pay the bills and increasingly distribute the moderation load. I'm happy with my Mastodon and following a few federated accounts on threads and bsky. But I'm not going to someone they are a bad person for choosing something that is familiar yet a little different while escaping x/itter.

But little by little, they started asking Jay and the team for moderation tools, and to kick people off. And unfortunately they followed through with it.

This bit I don't get. Even on Lemmy and Mastodon we need moderation tools and arguably the current provisions aren't fit for purpose. It's not something that can just be pushed to the individual users and most hobbyists who want to spin up public servers don't want to be spending their time wading through reports and CSAM. How to provide a safe environment for users is still an unsolved problem in the fediverse so it's no wonder people drift to corporate controlled servers which say least nominally have the resources to do something about it.

Yes and no. A lot of the projects I work on the majority of the engineers are funded by companies which have very real commercial drivers to do so. However the fact the code itself is free (as in freedom) means that everyone benefits from the commons and as a result interesting contributions come up which aren't on the commercial roadmap. Look at git, a source control system Linus built because he needed something to maintain Linux in and he didn't like any of the alternatives. It solved his itch but is now the basis for a large industry of code forges with git at their heart.

While we have roadmaps for features we want they still don't get merged until they are ready and acceptable to the upstream which makes for much more sustainable projects in the long run.

Interestingly while we have had academic contributions there are a lot more research projects that use the public code as a base but the work is never upstreamed because the focus is on getting the paper/thesis done. Code can work and prove the thing they investigating but still need significant effort to get it merged.

Yes

It's one of the reasons I enjoy working on open source. Sure the companies that pay the bills for that maintenance might not be the ones you would work for directly but I satisfy myself that we are improving a commons that everyone can take advantage of.