This open access study presents an application-specific instruction set processor (ASIP) design for the Kyber, Saber, and NewHope algorithms based on transport triggered architecture (TTA). While PQC algorithms are being standardized, one of the most critical issues is the development of efficient hardware architectures for them. Creating customized instruction set architectures (ISAs) is essential to ensure these algorithms can be used practically, especially in embedded systems.
The COVID-19 pandemic shows us how crucial patient empowerment can be in the healthcare ecosystem. Now, we know that scientific advancement, technology integration, and patient empowerment need to be orchestrated to realize future smart health technologies. In that effort, this paper unravels the Good (advantages), Bad (challenges/limitations), and Ugly (lacking patient empowerment) of the blockchain technology integration in the Electronic Health Record (EHR) paradigm in the existing healthcare landscape.
While I'm not totally on board with outlooks on a technological singularity a la Kurzweil and peers, what does it mean that there is no real representation of that idea here? For example, Kurzweil's "law of accelerating returns" where the speed of technological change increases exponentially has many flaws according to scientists I respect greatly, yet also has many hints at possible futures, ironically also according to scientists I respect greatly.
It is a controversial idea, and most people can only imagine a future for humanity where things look pretty much as they do now, but with slightly better technology (cf Star Trek, where meat bags are flying among the stars, mostly unchanged from present humanity).
I'm fairly certain we're looking at the end of human civilization one way or the other within the next 100 years max. The Global Pollution Epidemic, robot uprising, and nuclear war are the more likely bad scenarios for the end of civilization.
We might instead be able to develop technology which solves all present problems (like pollution and energy production) and then use it wisely to bring wealth and enlightenment to everyone.
I wouldn't care to estimate what outcome is more likely.
Even Kurzweil's updated ideas and projections in The Singularity is Near from around 2005 still make assumptions of humanity having a longer technology maturation period than 100 years. I actually have the same opinion as you when it comes to our time left if we can't make some global changes; it bums me out, having two girls who are not even in High School yet.
I agree with the core idea here, of developers reducing use of energy-pulling hardware and software resources. However, to both get interest moving and to ensure future participation, there should
1) be a solid plan on how to do it efficiently (HOWTOs),
2) a table of ideal targets (if your footprint is typically X then achieve Y or Z upon reduction, and
3) a public site where the actual results and data can be stored, studied and commented upon.
I feel to quantify this in a monetary way would bring support for the activity from non-developers as well, and perhaps lend to a shift in the way developers purchase hardware.
Two major factors that lead to hardware purchases are
1) software vendor minimum hardware requirements, and
2) hardware vendor advert strategies which often pull developers into buying more than they really need.
This global awareness week could end up making developers more aware of their actual hardware needs, and cause a shift in how companies actually purchase hardware. Done right, you could see a huge impact on the computer hardware market.
Keep in mind that Arc is the start of something with long-term goals; further, it's part of a lifecycle that didn't necessarily start with Arc but with the first Lisp. PG points to an early essay titled "The Hundred-Year Language" [1] as an indicator of where Arc is intended to go and some future outlooks that might inspire more evolution.
I don't know that any programming language can be everything it needs to be from the outset, but it certainly needs inherent featured supporting longevity, a framework that supports change and evolution, while still having a pleasing and useful function that can be taken advantage of immediately.
My one major concern not outlined above is that of responsibility to end users who may not have resources with which to adjust when large repos are retired. Case in point: We assume users of forges are like us - that is, back up their own code, proficient enough to move to their own local repository if needed, etc. However, what if some of the developers using an online repo were something else. Highly hypothetical but imagine they came from a country where they could only code from a remote server and had to check in to some online forge to store their code (whether it's source like Python or updates to documentation - not all project members are coders). Imagine this user was a political fugitive or similar.
Now, it's not your legal responsibility as the originator or current curator of the repo to help this person out, of course, but in terms of the industry and our behavior as software engineers it seems we do owe some sense of permanence to things that feel more like infrastructure than simple personal websites. I’ve been very guilty myself of stepping “briefly” away from things knowing in the back of my mind I may never return. I continue to try to reform my attitudes online. Remember BerliOS, Google Code, and CodePlex? Gna! is merely one of several, not even the most used.
Realizing this might appear an attack against the Gna! project owners, I had to reach out and talk about this with them and identify this as merely a conversation starter. The loss of Gna! definitely has made me think more about the ecosystem we work within and whether we are doing everything the way we should be doing. How many users of GitHub might be working under frightening conditions to get code out to the world they could be arrested for writing? We don't know. I merely propose we might have a gap here in the process that does not acknowledge users who may rely greatly on some of our tools we offer for "free" and that when we retire them, something important could be lost in the process.
Note: Sylvain Beucler, formerly of the Gna! project and notably of many great projects like Savane and FusionForge, reminded me ArchiveTeam volunteers are often working behind the scenes to keep snapshots of retires sites such as Gna! when able. That project is currently headed by one of my favorite ASCII-oriented minds, Jason Scott of textfiles.com. They are linked to below.
If you take a look at the code for HN written in Arc, you can compare it against other Lisp dialects. I point to this as it is possibly the most widely-used and familiar application to most here written in Arc.
This is a great place to start with understanding Arc, as the jump to Anarki (an Arc fork) will make more sense as it comes bundled with News - a Hacker News style app - which is fun to play with if you have experience with HN and want to try a variation of this site.
Working at UCLA I have an affinity for Ted Nelson and the early life of the Internet. I am also deeply interested in his ideas related to the interrelations in human knowledge. Perhaps I am a lover of things not celebrated (I sometimes work off an early version of the GNU Hurd and an OpenVMS system) but I feel he has ideas that actually should be. O'Reilly had a great article recently that invoked Ted Nelson I enjoyed:
The Intertwingularity is near: When humans transcend print media
