> However, the above is a tall order for someone just wanting to dip their toes in, to see if they have any interest in Coalton or Common Lisp. A couple hours on the weekend is easily sunk into getting configurations right, and the right subsystems installed, and the right paths setup, just so the first line of code can be executed.
> mine is not Emacs. It aims to eliminate all of that, and be a Coalton/Lisp-first development environment, whose only job is to be a Coalton/Lisp-first development environment. But more than that, it needs to be accessible. A non-programmer should find it easy to download, install, and run mine with nothing more than a download link.
I think the number of non-programmers who think 'I want to learn to program; I'll start with common lisp but emacs is too difficult!' is so small it is not a group worth considering. It's probably MIT & Stanford undergrads?
It's their IDE and they can design it how they want, but that's a weird goal for a CL IDE.
"It should be easy enough for" sets a UX bar, not a target audience. Kind of like the English phrase "X is so easy that even a toddler could do it," regardless of whether such a statement is figurative or literal.
I personally suspect that the overwhelming majority of those complaining would find a different reason to not learn lisp if the Emacs barrier were removed, but I very much might be wrong.
Acorn’s UNIX had the IXI desktop, which was, back then, the absolute pinnacle of user friendly Unix. IIRC, IBM’s AIX for the PS/2 also had it or something very similar.
Why not just add the GOG games to Steam as non Steam games?
Isnt that better anyway than having to launch GOG from the Steam BPM just to launch a game from their BPM?
Why would i want to launch a seperate launcher to launch my games?
It seems to me that if there were as much of a customer base for custom ICs as there is for PCBs, a fabricator like TSMC could easily offer a batch prototyping service on a 28 nm node, where you buy just a small slice of a wafer, provided you keep to some restrictive design and packaging rules.
They already do offer that - it’s called a multi-project wafer or MPW. But it’s prohibitively expensive on a per-chip basis. It’s mostly used for prototyping or concept proving and not for commercial use.
One problem is, you need to create a photolithography mask set for any volume size of fabrication and those aren’t cheap. But that’s far from the _only_ problem with small volume.
> However, the above is a tall order for someone just wanting to dip their toes in, to see if they have any interest in Coalton or Common Lisp. A couple hours on the weekend is easily sunk into getting configurations right, and the right subsystems installed, and the right paths setup, just so the first line of code can be executed.
> mine is not Emacs. It aims to eliminate all of that, and be a Coalton/Lisp-first development environment, whose only job is to be a Coalton/Lisp-first development environment. But more than that, it needs to be accessible. A non-programmer should find it easy to download, install, and run mine with nothing more than a download link.
reply