p_l

5 ms·

31.
by p_l 1mo ago
Baseway, and various other industrial control systems that also ran on VMS and related, tended to either use DEC-suggested (DECnet) protocols or implemented custom Ethernet-layer ones
32.
by p_l 1mo ago
Several Google apps do not work for me in Chrome (Maps, Earth) but work perfectly fine in Firefox... :D
33.
by p_l 1mo ago
Was it perhaps DEC Baseway[1] system? It would arguably qualify as a form of DCS, with central VAX servers and running high level software, PDP-11 "shop floor" computers, which in turn talked with PLCs and related devices. And add
34.
by p_l 1mo ago
Unfortunately every attempt at reforming it is blocked with "but my sovereignty!" - as EC and Council of Ministers are very much controlled and steered by member nations' governments . Not to mention it makes for perfect sca
35.
by p_l 1mo ago
input handling that does not explode under Proton would be one thing...
36.
by p_l 1mo ago
Depends on a country, not many try to get the backdoor through international trade (effort), and even then local law might make it problematic
37.
by p_l 1mo ago
Just remember it will more likely be the version from Dune Encyclopedia, not Herbert's sons' prequels
38.
by p_l 2mo ago
MEPs in many countries do not actually have immunity. However, the bigger issue is that european parliament is treated in many countries as essentially dumping ground between national elections.
39.
by p_l 2mo ago
Part of the problem is that the API you're supposed to provide externally depends on git packs which you might have to reconstruct on the fly from such a system.
40.
by p_l 2mo ago
FMCGs work very much like command economies, including specialized tooling to shift production between customers when orders fall through. Unlike USSR they simply do it on shorter timescales, too, and with better customer feedback. Somethin
41.
by p_l 2mo ago
Considering the biography having lines like: > Malcolm has only ever had three paid jobs, and so far he’s been fired from two of them. the irony is definitely intended
42.
by p_l 2mo ago
It's more that they implemented it for higher speed as the split bus meant instruction fetches didn't block data fetches and vice versa - but it meant that without glue logic you turned a von neumann architecture into half-broken
43.
by p_l 2mo ago
I'd say the insane bus arrangements on released chips (unrelated to ISA itself) had more to say there - the 3 & 4 bus configurations only make sense if you're throwing a bunch of extra chips onto it to make a proper CPU module
44.
by p_l 2mo ago
Both are based on RISC-2 design, yes.
45.
by p_l 2mo ago
Siemens for some software uses a license system that uses "secret" files stored on "dongle" that is just USB stick, and software that manages copying to hard drive etc. I have heard of several cases where Siemens technic
46.
by p_l 2mo ago
And now the legacy of Larrabee, AVX-512, is only properly available on AMD for consumers :D
47.
by p_l 2mo ago
X86 does not really need pipelined decoders like NVAX did. The complex decode for x86 is the fast path for NVAX without going into CSU. And CSU is where all the more complex addressing modes on VAX end up going - the complex instructions ar
48.
by p_l 2mo ago
I'd say RISC won, when you consider how "RISCy" x86 is[1] compared to the ur-CISCs (68k, VAX ) that RISC projects were in opposition to. [1] Not because of often-called "risc like" microcode engine, but because the
49.
by p_l 2mo ago
My personal idle walking-with-dog kind of design was a linear binary record file with regular marks letting you resynchronize where you are (and stamp cryptographically) with minimal seeks, and separate indexing files with bloom filters and
50.
by p_l 2mo ago
I would argue the described format is exactly the origin of the problem. It tries to optimize on disk footprint by deduplication and resulting in way more complex file format with many possible footguns leading to things like write amplific
51.
by p_l 2mo ago
I would argue the difference is that upstream is well known for being defensive about their ideas and pushing back. On LKML you might get cursed out, but if your fix is solid fix, it has high chances of getting through. Regardless of how tr
52.
by p_l 2mo ago
In this case, it's also a very ego-driven project. Honestly, the few times I went into systemd source (to deal with how they didn't document some critical information without which I couldn't ensure coexistence of other softw
53.
by p_l 2mo ago
Honestly, I would go append-only blocks that contain binary/compressed format with synchronizing marks so worst case you get some nulls but every reader can synchronize where they are in the stream without blocking anyone. Might take m
54.
by p_l 2mo ago
... Sounds like a signature on a patch that triggers an epic Linus rant on LKML[1] [1] Happened few times, I think RedHat as a whole even got banned from sending changes for a short while
55.
by p_l 2mo ago
The logic changes can be done without destroying investment in the current ecosystem though. So they are really handled separately in terms of planning/budgeting. Also, a lot of the problematic issues are related not to fixing the loca
56.
by p_l 2mo ago
systemd-journald has one of the most deranged log file formats I have ever dealt with, and one of the worse user interfaces, too. I am not again binary logs, or logs in a database. It's just yet another time I deal with good ideas impl
57.
by p_l 2mo ago
Oxide is shipping the baremetal server as well, with integrated hypervisor - so running kubernetes with kubevirt on it makes less sense than integrating with the host hypervisor
58.
by p_l 2mo ago
For manual entry, there were cards you'd mark with special pencil that would leave magnetically recognizable marks.
59.
by p_l 2mo ago
That's why HTMX and others use things like idiomorph
60.
by p_l 2mo ago
well, I wasn't implying full semantics. Or fast, to be honest. Still could be faster than vtable though...

More ›