__d

61 ms·

751.
Plan 9 from Bell Labs in Cyberspace(bell-labs.com)
865 points by __d 6y ago|261 comments
752.
by __d 6y ago
What I'm curious about is why the author doesn't just use Doom, rather than seeking to reimplement all the things it does in Neovim. The whole notion of being a productivity platform has been the emacs way for 35 years ...
753.
by __d 6y ago
I've used Visio, Dia, OmniGraffle, and lucidchart.com. Dia is pretty terrible, sadly. OmniGraffle seems to be fading away. Lucidchart is ok, the sharing is good, and the Confluence integration is widely used. Visio is kinda the best.
754.
by __d 6y ago
No resources, but I found the easiest thing was to get agreement that FOSS components could be used to develop the software, subject to suitable licensing, and that any required changes to FOSS components could be contributed upstream. By
755.
by __d 6y ago
I read the Rekursiv article too! It sounded like a great project.
756.
by __d 6y ago
FWIW, it's available here: http://www.classiccmp.org/transputer/software/languages/modu...
757.
by __d 6y ago
I think it’s likely that they were either independent or the Helios folks had a brief overview of Plan9. While Helios did a lot of quite cool stuff, I don’t think it was as general as 9P. It felt like it was produced by a small number of sm
758.
by __d 6y ago
I didn’t. It was the Rowley compiler iirc?
759.
by __d 6y ago
I always loved the look of the CM1. I wonder if, rather than just a single LED for each CPU, you could use an old eg. 1280x1024 LCD panel instead, so you could set the display to show different configurations of the inter-CPU links for diff
760.
by __d 6y ago
Helios (the OS of the ATW) came with a port of GCC. It was, ironically, hard to use Occam on the ATW. I think you could also get Fortran, Modula2 and Ada compilers for Helios.
761.
by __d 6y ago
There was a multi-vendor standard for Transputer modules called TRAMs: they were a bit shorter and a bit wider than a modern DIMM, and used pins on the short ends rather than PCB fingers. A common TRAM had a CPU and 4MB of RAM. You'd
762.
by __d 6y ago
That's about right, yes. There were 4 x 20Mbps links and you could use them to directly connect to other CPUs (so, a mesh or torus) or to a fabric. The link protocol was very simple. Each CPU had local DRAM, but there usually wasn&#x2
763.
by __d 6y ago
It did, yes. Helios ran on a bunch of different systems, 68000, Transputer, i960, and later ARM, I think. It was a fun system to program: the server protocol is a bit like Plan9's 9P. It was pretty cool at the time to have all your CP
764.
by __d 6y ago
Josh & Belle, sorry to hear this, but pleased to see you're tackling it head on. Best of luck with the sale!
765.
by __d 6y ago
My first computer had a 2MHz CPU; my current has roughly 4GHz (2000x faster). My first computer had an 8 bit CPU; my current has 64 bits (8x, so ... could try harder :-) My first computer had a single core; my current has 16 cores (so 16x).
766.
by __d 6y ago
It's not possible for every 25yo programmer working today to become a consultant or CTO by the time they're 40 (or in fact any age). There's just not that many CTO/consultant jobs! Similarly, not everyone can become a p
767.
by __d 6y ago
I agree that reliable operation is paramount. While it might not work for everyone, having a standard hardware platform with the ability to get firmware updates applied, or even hardware fixes, helps. So, something like the PINE64 PineTab c
768.
by __d 6y ago
Depending on your interests, embedded systems programming might be an opportunity worth pursuing. In my experience, it's much more a stable "stack" than most other areas, and there are plenty of programmers who continue to wo
769.
by __d 6y ago
In my experience, companies mostly use Confluence, Atlassian's Wiki, for this sort of thing. It has a bunch of plugins for diagrams, from Visio-like stuff, to more Photoshop-style. The problem is that it's simply awful to use.
770.
by __d 6y ago
Which makes sense: compartmentalise. Otherwise, a failure of one domain would compromise all the others. I hope there's some automated assistance for scanning inbound source code too. Imagine reviewing everything , line by line, mil
771.
by __d 6y ago
I used to do a regular 15h flight (MEL-LAX or LAX-MEL, I forget which was the longer one). I'd add: Get on board tired. Stay up late a few nights before you leave, get up early, do a bunch of exercise, whatever it takes. Be ready to
772.
by __d 6y ago
Because why would anyone adopt a Google-owned messaging system after seeing their history of messing this up?
773.
by __d 6y ago
Nothing about sustainability or environmental preservation at all? In 2021?
774.
by __d 6y ago
I recently looked into this, and found this article claiming neither NZ nor Oz were the originator: https://www.rnz.co.nz/news/on-the-inside/423073/the-surprisi...
775.
by __d 6y ago
I'm interested to see what Apple comes out with for the higher-end MacBook Pros, iMac Pro, and Mac Pro. I expect to see the M1 used in the iMacs, although ... That could be a single higher-end chip, with possible multi-socket support
776.
by __d 6y ago
1. x86 (and then AMD64) has had vast amounts of R&D money and talent thrown at it for decades, with the result that it has out-performed every competitor: SPARC, MIPS, Alpha, PA-RISC, Itanium, etc. As a consequence of this domination,
777.
by __d 6y ago
I think that's the entire point of this article: the existing system software APIs that we use aren't a good abstraction for the capabilities of the underlying hardware, leading to poor performance.
778.
by __d 6y ago
The most valuable property of UTF-8 from a C-string point of view is that it guarantees there are no embedded NULs in a UTF-8 string. If you naively put the bytes of UTF-16 or UTF-32 encodings into a buffer, they might contain NUL (zero) by
779.
by __d 6y ago
C++ has string support in the standard library. It doesn't have the same breadth of features as, say, Python's string class, but it's ok. See, eg. https://en.cppreference.com/w/cpp/string
780.
by __d 6y ago
The decision to use this chip (vs the WD) in the BBC Micro made me wonder if there were other obvious-in-hindsight bad/weird/hackish choices in classic computer design? The PC-AT's use of the keyboard controller to control A2

More ›