Further cementing his hero status, I checked if there was a way to donate. The homepage says:
> The uBlock Origin project still specifically refuses donations at this time, and instead advises all of its clients, users and supporters to donate to block list maintainers.
Although not really import but just FYI, if you mean the website https://ublockorigin.com/ it's not the homepage, it's a fan-made page. uBO does not have any servers nor websites. The "homepage" is just the github page: https://github.com/gorhill/uBlock
Raymond Hill is like a 9/10 on the Jesus scale as far as programmers go. He even survived being martyred by that self-serving schemer who gained control of uBlock, before being successfully resurrected as uBlock Origin.
Real-time linux can be thought of taking vanilla linux - configuring the kernel in a certain way, booting your kernel with certain boot params and writing your real-time application in a certain way.
While there quite a few hiccups along the way - you will be able to bring down jitter or OS noise to around 1 us. Of course a microkernel based OS like QNX can take you down to around 1 ns - but then the point of using Linux is that you are able to utilize the ecosystem around it.
Look into isolation, real-time patch and high performance computing.
Simulink Real-Time team produces real-time applications from customer models made using modelling tools, ranging domains from aerospace, formula-1 to medical devices and then run them on dedicated target computers connected to real, physical systems. We support algorithms running on multi-core CPUs and FPGAs and we provide instrumentation and visualization capabilities as well.
Will sponsor VISA provided you are authorized to work in the US already.
At this point I consider being permission-less the limiting
factor: if broad "read/modify data" permission is to be used,
than there is not much point for an MV3 version over MV2, just
use the MV2 version if you want to benefit all the features
which can't be implemented without broad "read/modify data"
permission.
The problem is much more about reasonableness than about "waterfall" or "agile". Having everything "planned" beforehand and forcing it through is also terrible for embedded projects if there are holdups - and there are going to be holdups.
My favorite is always "but we defined 3 years ago that it'll do this-and-this fancy 3D thing on this screen, it's a requirement!" "well then maybe you should have selected hardware that can do fancy 3D. Let's talk about what we can change that still is good." "But its a requirement!".
Or on the hardware side, there is a "plan" that can't cope with the fact that suddenly there is a really good reason to do a hardware revision that nobody planned for. (e.g. because its 2021 and suddenly a bunch of parts just isnt available)
Of course totally freewheeling nothing-planned also causes equivalent problems, as does expectations that anything can change within 2 weeks. On the other hand on plenty projects I've worked on the "agile" requirements on the Yocto person are more among the lines of "we'd like this additional software added to the image please".
I would say the current state of RISC-V is complete but still lacks the final kick. Yes, you can now build an application core out of it, given that V, B, K extensions are now ratified under RVA22. However most high-performance u-archs are not built for client applications -- they are usually built for server/professional market and then derive down to the client side. (Edit: or if not in the Apple and ARM case, curated computing also needs something beyond regular client applications)
For server/professional market, RISC-V still lacks a selling point. Perhaps something like a pointer masking, memory tagging, or transactional memory in the J and T extensions which are still in very early stages.
It's really about who invests money. Say if you're a large country that wants an independent supply of CPUs that can't be sanctioned, ARM/x86 isn't going to be where you invest
I'm renting a couple of VPSes from Vultr that I run FreeBSD on. Very low cost, and decent for my current use which include self-hosting email, hosting a couple of websites that receive little traffic, as well as to host the mentioned VPN, and for testing of some backend services that I am developing.
I hope to afford racks of beefy bare-metal servers one day that can sit in colocation data centers and that I can host backend services for others on. But for the time being I do not have the funds for that so a couple of small VPSes for my own use it is :)
