Huh, this is interesting. Great idea for a project. Is there much out there with similar aims? I absolutely don't know the field well enough to say.
I think this could really benefit from documentation, and maybe a sort of tutorial that walks you through the steps of building something with these. Even just commenting the various parts of the examples, "here we need to foo so we can flerb the qux", "to do xyz, we need to …" and so on.
"Investing" in code readability & comments might also be worthwhile. If I wanted to use nux to build something, I really wouldn't know where to start even with the examples, as the comments on the header files are pretty terse and reading the code itself is pretty daunting as there's quite a lot of it and with fairly few comments, and there's a lot of acronyms and short identifiers. This'd also make it easier for others to contribute too.
But having a toolkit for testing out ideas and prototypes without having to worry about all the more boilerplate-y parts of kernels seems very useful.
"Big words, phrases and memes"? You got this distressed about an article using industry standard terminology for its target audience and assuming that you'd read (or would read) the post it linked to on Conway's law?
Real names were absolutely used on Usenet especially in the early days, ditto for mailing lists (and still are for that matter), even though technically they are pseudonymous. In any case pseudonymity doesn't seem like it's relevant for whether something is a social medium or not – many social media are pseudonymous (or even anonymous, like the chans). HN is pseudonymous. Reddit. Tumblr. The various Fediverse services.
Right, and which particular "fact" was it? Somehow I doubt it's an actual biological "fact" but rather a conservative "alternative fact", which ignores actual biology
You generally need line-of-sight for microwave links and the longest known link is something like 350km, and even using tropospheric scatter you can't go over ~500km, so you'd need multiple relay stations with microwaves.
Using a lower band and bouncing off the ionosphere gets you much further but only works if ionosphere weather is OK, and it'll have lower bandwidth (not necessarily a problem though), and encryption is a no-no for amateur radio in most countries
> If one would like to interconnect various meshes, I can't think of a way to avoid using the Internet to trunk traffic across the Atlantic let's say.
Radio links with a regular 'ol dipole antenna? Although I think most countries prohibit encrypted traffic for amateur radio purposes, plus the link would be kinda spotty and depend on ionospheric weather
Google used to have superior translation but that hasn't been the case for years now. Based on my experience DeepL (https://www.deepl.com/) is vastly superior, especially for even slightly more niche languages. I'm a native Finnish speaker and I regularly use DeepL to translate Finnish into English in cases where I don't want to do it by hand, and the quality is just way beyond anything Google can do. I've had similar experiences with languages I'm less proficient with but still do understand to an extent, such as French or German
How are GA144's nodes / "computers" not real cores? They're fully independent, each has its own memory (RAM and ROM), stacks, and registers, its own I/O ports and GPIO pins (some of them), and so on.
I think they were more meant to minimize power use than be very performant. Honestly no clue how widely the GA144 is used in real-world applications, but I guess that since the company still exists they have to be getting money from somewhere
> Apple’s current implementation of lightweight virtualisation still has no support for Apple ID, iCloud, or any service dependent on them, including Handoff and AirDrop. Perhaps the most severe limitation resulting from this is that you can’t run the great majority of App Store apps, although Apple’s free apps including Pages, Numbers and Keynote can still be copied over from the host and run in a guest macOS.
That description reminds me of GreenArrays' (https://www.greenarraychips.com) Forth chips that have 144 cores – although they call them "computers" because they're more independent than regular CPU cores, and eg. each has its own memory and so on. Each "computer" is very simple and small – with a 180nm geometry they can cram 8 of them in 1mm^2, and the chip is fairly energy-efficient.
Programming for these chips apparently a bit of a nightmare though. Because the "computers" are so simple, even eg. calculating MD5 turns into a fairly tricky proposition as you have to spread out the algorithm to multiple computers with very small amounts of memory, so something that would be very simple on a more classic processor turns into a very low level multithreaded ordeal
> Every one agrees that the Turner Prize is much more than just a display of virtue signalling by the cultural elite, and I have decided to enter the Valve.Computer for the prize.
Uh, what? Where did this sudden "virtue signaling" by the "cultural elite" stuff come from?
Shit, how do I protect myself from evolving AI-based scams? I'm middle-aged and not in the IT industry anymore, and scams like the Booking.com (I think it was?) one where the scammers were able to send valid emails almost got me already.
Persisting login cookies if the user didn't explicitly consent to data collection is specifically _not_ exempted by ePrivacy. To quote a EU Working Group's opinion on this: 'Persistent login cookies which store an authentication token across browser sessions are not exempted under CRITERION B. This is an important distinction because the user may not be immediately aware of the fact that closing the browser will not clear their authentication settings. They may return to the website under the assumption that they are anonymous whilst in fact they are still logged in to the service. The commonly seen method of using a checkbox and a simple information note such as “remember me (uses cookies)” next to the submit form would be an appropriate means of gaining consent therefore negating the need to apply an exemption in this case.'
I think this could really benefit from documentation, and maybe a sort of tutorial that walks you through the steps of building something with these. Even just commenting the various parts of the examples, "here we need to foo so we can flerb the qux", "to do xyz, we need to …" and so on.
"Investing" in code readability & comments might also be worthwhile. If I wanted to use nux to build something, I really wouldn't know where to start even with the examples, as the comments on the header files are pretty terse and reading the code itself is pretty daunting as there's quite a lot of it and with fairly few comments, and there's a lot of acronyms and short identifiers. This'd also make it easier for others to contribute too.
But having a toolkit for testing out ideas and prototypes without having to worry about all the more boilerplate-y parts of kernels seems very useful.