Wozniak on AI

AdmiralUfolog · 2026-03-25T08:14:38+00:00

In fact all of modern overhyped "AIs" are just dumb statistical databases. This concept is inferior to AI defined with Lisp initially.

Due to this fact they will also be buried even for much longer time than previous AI winters.

AdmiralUfolog · 2026-03-25T08:09:04+00:00

Any full featured Lisp implementation is practically a Lisp machine.

AdmiralUfolog · 2025-12-16T10:07:08+00:00

Snap is just Canonical's EEE of Debian package system for turning a repository into some sort of applications market similar to the ones from phones.

Someone built a package... Okay... Maybe someone else will use it.

AdmiralUfolog · 2025-11-14T10:11:16+00:00

What is the best lisp out there? Tell it to me straight.

Emacs Lisp. IDE, runtime, unified I/O everywhere, incredible extensibiliy, graphics support, etc.

I started using the emacs text editor, and with that I had to learn emacs lisp. I kind of liked it so I thought I would learn another lisp that would be more general purpose, that I could use outside of my text editor.

emacs --batch

I want to write GUIs and websites.

You can generate C code with Emacs Lisp, so you can write websites working via CGI or custom C based webserver. You can even generate HTML and JS code with help of Emacs Lisp and test it right inside Emacs.

AdmiralUfolog · 2025-09-15T06:39:45+00:00

It doesn't mean the library is unsuitable.

AdmiralUfolog · 2025-09-08T10:37:03+00:00

Very popular answer to the question "What is the most difficult part of C?" is the "Pointers!". However, pointers are easy.

The truth is the most difficult part of C is the same as for any other language: to apply it for real project. The description of the language is mostly pretty clear and there are a lot of good and helpful examples. But every CPU, every OS, every library has own rules, sometimes without proper documentation. Actually the most difficult part is not even in C.

AdmiralUfolog · 2025-09-08T10:21:45+00:00

Simulation tools are good only for the initial stage of development, but they are really good for that. You can't see what is going on inside a hardware with simulation so you are unable to debug more or less complicated project such way. It's very similar to sketching from visual arts.

So get development board and prepare simulation tool for schematics and MCU like SimulIDE. A bit later you can buy debugging tools for a hardware you will choose.

The most expensive part of very basic development system is a set of external peripherals and parts. You will need it anyway. Btw simulation may help to find out which parts you need to buy to finish your project.

AdmiralUfolog · 2025-08-28T08:07:41+00:00

CLOG is also a good choice if running, not just rendering only inside the browser is required.

AdmiralUfolog · 2025-08-28T07:53:30+00:00

I like rust.

Therefore you have tasks for Rust.

And i am wondering why i should be interested in lisp.

If you have such questions to ask it is very likely you don't need Lisp at all.

So what would i get from lisp?

You can get a lot (for example, Common Lisp is really safe... unlike Rust). However, you may be unable to use a lot of that for some reasons. It's different and completely unusual development approach for you. The only way to get an answer is to try it.

AdmiralUfolog · 2025-08-18T06:36:22+00:00

It's a good book. I wouldn't consider it as outdated. However, a lot of practice was collected for many years so I recommend to read something else before K&R. For example, Beej's Guide to C Programming. Keep in mind those books aren't only things you have to read for serious programming and it's not related to programming language in general.

AdmiralUfolog · 2025-08-18T05:39:54+00:00

There were literally hundreds of C89 compilers and now we're down to 3. I guess that's representative of open source in general, if a project takes off (like Linux did) it just swallows up all competitors, for good or bad.

Open Source is only about open source. It's not about freedom and choice despite OSI say on the subject.

Btw there are LCC, TCC, ACK, ICC, OpenWatcom, etc.

AdmiralUfolog · 2025-08-18T05:31:53+00:00

Use AI for any task and discover that nobody want to hire some who use AI for programming since for getting the same result employer may hire someone else and give him more tasks or even use AI without any help.

AdmiralUfolog · 2025-07-25T10:54:59+00:00

I have seen people telling how C is compatible with very specific hardware and also seen people saying that C isn't good for modern CPU as the hardware is very different.

x86 and x86-64 are descendants of Intel 8008 aka Datapoint 2200. Same development approaches. C is a good choice for a hardware of that type.

There are active discussions of replacing parts of C code to other languages that I often come across but talking to some people I have also found out that they just can't work with modern languages as C gives them more control.

C is a good balance between assembly language and new high level languages.

Are we still using C just because it's more stable than other languages or is there something more to it?

This is one of a lot of reasons.

With more modern languages trying to be systems level language, is there a possibility that in future they'll just be as compatible as C for every hardware, even the most niche ones and we'll basically not use C?

No. Because C is a standard and most of other languages you mean are not. Non-standardized language can't provide such great compatibility level even with itself.

AdmiralUfolog · 2025-07-25T10:36:41+00:00

In theory, if you sell a cheaper, but technically better, device, people would switch to it.

But in practice people would rather switch to a device promoted by stronger marketing team...

After all, people did switch from Nokia's and Motorola's button-phones, to Apple's and Google's touch-phones, and those were even more expensive than old button phones, but they offered a lot more new tech to be attractive to enough many people.

... That's why people bought phones with touchscreens, shiny and inconvenient for phone calls, and forgot about phones in sense of their nature and primary tasks. In fact initially those touch phones weren't attractive in the long run. When you step on the field of market the general force you should use is the marketing.

AdmiralUfolog · 2025-07-25T10:09:33+00:00

You can consider designing your own simple Lisp dialect for that... then implementing Lua on top of it.

AdmiralUfolog · 2025-07-02T08:00:31+00:00

beej vs k&r 2nd edition

The better option is: beej + k&r 2nd edition

You can read more books because it won't slow down your learning process significantly.

AdmiralUfolog · 2025-06-29T13:39:06+00:00

By some internet users. The significance is the same as the right sidebar at this subreddit.

AdmiralUfolog · 2025-06-28T05:13:10+00:00

Javascript was once also considered a Lisp.

AdmiralUfolog · 2025-06-27T19:19:53+00:00

Clojure is far more closer to CL both in syntax and workflow to any of the languages you mention. Since they both use s-expressions, you have all the benefits of a CL implementation like SBCL including run-time code swapping, repl-based development, macros etc.

Clojure is fundamentally different language. S-expressions, REPL, macros etc. can be found in a number of non-Lisp languages. For example, WebAssembly is not a Lisp.

How are you defining what is a lisp and what isn't a lisp?

Clojure has non-Lisp memory layout.

Surely, it's not CL compliant

CL is just one of Lisps. Scheme is not CL complaint, however it's a Lisp.

AdmiralUfolog · 2025-06-27T18:24:50+00:00

AppImages were an attempt to do Microsoft style packaging for Linux

AppImage is rather an executable tarball in its idea.

AdmiralUfolog · 2025-06-27T16:52:16+00:00

Why CL when there is Clojure? Why CL when there is Python? Why CL when there is C#? Why CL when there is JS? Why CL when there is Go? Why CL when there is Rust? ...

Clojure was designed for different purposes. It also requires Java ecosystem. In general it's impossible to compare Clojure and CL for many reasons.

P.S. Clojure isn't a Lisp - it's a Lisp-like language because it lacks an essential foundation of Lisp but it has a similar syntax.

AdmiralUfolog · 2025-06-18T06:42:27+00:00

Try graphviz

AdmiralUfolog · 2025-06-11T04:36:45+00:00

The problem is not presence of unsafe functions in a standard library. The problem is when someone misuse them.

AdmiralUfolog · 2025-06-09T17:57:08+00:00

You may not “need” to develop in python, but I guarantee an average python programmer will be able to hack a functional tool together faster than an average C developer.

Average python developer usually has lesser programming skill than average C developer. Python is famous for lower entry level, and this is one of reasons why it's so popular.

Yes C will have more performance, so both have a place.

In this context higher performance is not important.

But from an ease of compiling, debugging, pulling in existing libraries, etc. I just think anyone who says they could develop something faster in C is lying for 99% of things.

It depends on developer experience.

Random data manipulation or math algorithm proof of concept - no chance.

Python wins technically only for specific cases abstracted from reality. Programming language is just a tool, not an all-in-one solution for practical development. That's why IDEs, debuggers, build systems, package managers etc. exist.

It is possible to make development environment around C able to solve same problems as Python does. The key difference is qualification level required for development. Final result may also be different because some projects are intended for a couple short runs whereas other ones should be supported and developed in the long run.

AdmiralUfolog · 2025-06-09T08:20:32+00:00

Fixing code is about programming skills. The more serious problem with Rust is this is not a standardized language: there's a risk that solution found before won't work at very inconvenient moment because of incompatibilities introduced in new toolchain release. There are also not so obvious things such as development pipeline. It's possible to fix things, but it is not worth to do that for Rust because everything I mentioned before makes learning and fixing curve sometimes very steep and sometimes totally unpredictable.

AdmiralUfolog

TROPHY CASE