Rendered at 17:13:24 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
jbellis 1 days ago [-]
Anders Heljsberg GOAT. Turbo Pascal, Delphi, C#, TypeScript, just a phenomenal career marked with better taste than any other language designer I can think of, certainly any designer whose work is so mainstream.
tim333 16 hours ago [-]
This video with him on the history is good https://youtu.be/uMqx8NNT4xY
"The history of C# and TypeScript with Anders Hejlsberg | GitHub"
pjmlp 23 hours ago [-]
You are missing J++, several C# features were born in J++, e.g. P/Invoke was J/Direct.
ak39 23 hours ago [-]
Wasn't C# just a rebranding of J++ after the Sun Java trademark lawsuit?
pjmlp 22 hours ago [-]
Nope, J++ was on the Microsoft JVM, whereas C# was on top of a full new runtime.
However the language extensions that were the reason for the lawsuit did indeed transition from J++ into C#, with J# being J++ on top of .NET for easing code porting.
The features were events, J/Direct (later P/Invoke on .NET), COM interop (later RCW/CCW on .NET), and Windows Foundation Classes (later Windows Forms on .NET).
Given development speed is way up, I'd be interested to see what a from-basic-principles simple and efficient OS and programming system might look like. Or people trying radically different versions of efficiency and simplicity, like an OS that uses an existing battle-tested sandboxed execution environment like v8 for userspace safety/isolation.
Fundamentally, many inefficiencies were justified for developer productivity, and I'm not sure that makes sense anymore, and the cost of larger projects with clear abstraction boundaries has plummetted.
Isamu 1 days ago [-]
>Fundamentally, many inefficiencies were justified for developer productivity, and I'm not sure that makes sense anymore
Having lived through this period, I would disagree, quite the opposite we tended to develop in C and assembly specifically for runtime efficiency because we had to.
For developer productivity you could opt for Lisp or SmallTalk or some such, which ran much slower until high quality compilers for these became available, and even then your target machine might only have a C compiler.
SoftTalker 1 days ago [-]
I read GP's comment differently, that we ended up where we are today (bloated languages, IDEs and runtimes) due to chasing developer productivity at all costs.
Now, developer productivity is becoming less important as developers are factored out entirely.
LeFantome 17 hours ago [-]
We will end up with something that is easier for AI to write, efficient to execute, and possible for people to audit.
Rust is becoming popular as LLM output. The resulting code is very efficient. The compiler helps keep the LLM on track and holds it to a minimum level of quality. Humans can read it if they want to. But it is not great to read.
Python is also a popular target. Easy to audit. LOTS of training data. The “one way to do it” philosophy of Python helps. But the resulting code is not very efficient.
I think we will end up with a new language that balances all these things better.
majormajor 13 hours ago [-]
Rust isn't my personal favorite for having agents drive development because the compile time penalties add up fast unless you stay on the agents with prompts/AGENTS.md/etc directives to really keep it from re-running full compile/test suites every iteration.
It can be the difference in a loop that an agent can crank on in Go for 15-30min while I get a coffee vs taking multiple hours in Rust, sometimes.
Anything agent-focused language/ecosystem wise needs to focus on small-blast-radius/fast-iteration.
(Unless/until there's a generational leap in the raw coding ability of these tools to be able to get it "right" (for larger-and-larger definitions of "right") the first time.)
drfloyd51 16 hours ago [-]
I don’t think we will. Well maybe for a bit. But I think eventually LLMs will produce a kind of byte-code or IL.
Maybe it will have human words inside of it to explain the parts.
Most of the way we organize code is to support our brains. Code reuse via classes and functions. Extensible patterns. Classes.
AI doesn’t need all that stuff. Consider, AI needs what assembly needs. And assembly doesn’t have any of those conveniences.
At some point AI will stop writing code for us to pretend we own and start writing it for itself. I am curious to see what conventions arise to support a programmer whose brain has infinite storage capacity and can figure out what existing code does without having to remember or read documentation.
jiaaro 14 hours ago [-]
Not all of that abstraction is solely to help us understand. Much of it is to make iterating on the code over time simpler and more reliable: avoiding unintended side effects, for example.
pjmlp 9 hours ago [-]
Integration tests for AI.
Like "agent has to send email with specific content on trigger A", test "has to validate email arrives with expected content"
How the agent actually reacts on the trigger or sends the email, those are agentic runtime details.
See platforms like Boomi.
pjmlp 10 hours ago [-]
That is my view as well.
Already when coding on cloud environments like Workato and Boomi there is no code output to look at.
14 hours ago [-]
14 hours ago [-]
hawkice 1 days ago [-]
This was my intended meaning -- the clearest advocacy of this was from DHH about Ruby on Rails, although he's changed his mind about big questions lately and suspect he no longer endorses that set of trade-offs (I don't either, _sort of_ -- I think developer productivity means having simple ways to enable large-scale testing and oversight while minimizing context switching costs, although I think we are all figuring out what that means in practice).
za_creature 1 days ago [-]
Specifically, turbo pascal was entirely written in assembly according to wikipedia (I recalled only 50% but maybe that was some other pascal dialect)
userbinator 13 hours ago [-]
I'd be interested to see what a from-basic-principles simple and efficient OS and programming system might look like.
UNIX. Seriously. Look at what it could do with 1970s era hardware, that was unmatched even when DOS came out in the early 80s.
pjmlp 9 hours ago [-]
I rather look to the 1960's hardware with Burroughs, Multics and Lisp.
During the 1970's, VAX/VMS and Xerox PARC workstation OSes, ML, CLU, were more inspiring for 1970's hardware capabilities.
za_creature 1 days ago [-]
I think you have that backwards.
It's the lack of clear abstraction boundaries that causes decreased developer productivity.
A code generator will not save you from Conway's law.
pocketarc 1 days ago [-]
This is the thing - when the cost of iterating and grinding compiler warnings drops to virtually 0, what new paradigms might we invent to exploit that? Rust gives us an inkling of an idea of what might be possible, but that still predates LLMs and thus still makes concession for human ergonomics. What are structures, guardrails, and patterns, that our OSs, frameworks, and toolchains can put in place, which would result in whole classes of problems going away completely, at the expense of massively increased (but mechanical, and easily automatable with a prompt) developer effort?
The next few years are going to be fun.
drfloyd51 16 hours ago [-]
I imagine a kind of language which is just a bunch of declarative statements about conditions and what should happen. Basically BDD. Maybe we will just write the “unit tests” in human and AI writes more comprehensive specification to fill in the blank and for us to modify. And then AI makes code that satisfies the spec.
I don’t believe that source code is a spec. Source code has real time manipulation a kind of temporal dependency. Specs are declarative.
The difference is a spec would say: adding two and three should equal five. Code says you have a variable give it the value two. Now add three to it. Return that value. Maybe a unit test to assert it returned 5. Code defines how a spec is satisfied.
tomaskafka 1 days ago [-]
This would be fine grained type systems where invalid states are inexpressible.
StilesCrisis 23 hours ago [-]
Both humans and LLMs struggle with slow iteration times.
hedgehog 23 hours ago [-]
v8 is pretty complicated, and anything that depends on LLVM is going to be huge, so I think I would start smaller. You could try building around something like NuttX or an L4 + tcc or cproc and see what it takes to get to self-hosting as well as ability to do some job you care about. To me the bigger question is that last bit, you can shrink the platform code quite a lot relative to a typical Linux but what's the situation where that's a good trade vs say cross-compiling from a full C++ or Rust toolchain?
mike_hearn 8 hours ago [-]
Ahhhhh this is a common misconception and it's dangerous. V8 is not a battle tested sandboxed execution environment, not unless by battle tested you mean battle wasted. V8 is full of sandbox escape vulnerabilities practically "by design", always has been, probably always will be - and the Chrome engineers knew this from the start which is why from day one they invested so heavily in kernel-level sandboxing.
But the kernel sandbox is NOT A PART OF V8. It's not even reusable or modular, it's a hard coded part of Chrome's startup sequence and tuned for Chrome's exact needs. If you embed V8 via its API you don't get it.
I've seen this misconception several times now including in quite serious places, where people talk as if V8 on its own has a robust sandbox. It doesn't! This will blow up in people's faces eventually.
If you want a JS engine that's secure by design then the only one I know is GraalJS, as it's written in a memory safe language and uses partial evaluation to create its compiler so you can't get interpreter/JIT mismatches. It also has a proper sandboxing API and can transparently run code out of process. They're experimenting with integrated Landlock support now, so it actually will get a built in kernel sandbox on Linux out of the box, unlike V8.
This issue vexes me enough that I wrote a whole article about it:
While some comparisons may look silly, the fact that the touch command's binary should exceed Turbo Pascal is insane: the command basically creates an empty file or updates the file change date if the file already exists, not more.
There's no reason (other than laziness) why that should take more than 2k.
On the other hand, a lot of boilerplace code is repeated in each and every command. When I first learned as a kid about UNIX commands being ordinary programs, I was intrigued (there is nothing "special" about them, you can also write your own!) but also shocked about the overhead compared to an architecture in which e.g. the shell contained all (at least core) commands compiled into a single binary, which could share all the error handing, startup code, command line parsing code and so on.
zahlman 24 hours ago [-]
> the command basically creates an empty file or updates the file change date if the file already exists, not more.
GNU coreutils touch does a lot more than that. My local copy is about 95k; it allows for choosing from multiple different timestamps to update; suppressing the (default) creation of an empty file if it doesn't already exist; operating on symlinks directly rather than following them (if the system supports it); specifying a custom timestamp rather than "now" (including by parsing a date string), and of course outputting a help message and a version.
II2II 21 hours ago [-]
And how much of that feature-rich version touch is actual executable code?
I did a quick estimate by disassembling touch with objdump on macOS (163 kB executable), and it was approximately 6 kB (1500 instructions * 4 bytes/instruction). There is a lot more to an executable than executable code.
zahlman 6 hours ago [-]
Interesting. What else did you find taking up the space?
regularfry 23 hours ago [-]
I was going to suggest that even that logic wouldn't account for a binary size three times the RAM of my first machine, but from the man page:
> DATE STRING
> The --date=STRING is a mostly free format human readable date string such as "Sun, 29 Feb 2004 16:21:42 -0800" or "2004-02-29 16:21:42" or even "next Thursday". A date string may contain items indicating calendar date, time of day, time zone, day of week, relative time, relative date, and numbers. An empty string indicates the beginning of the day. The date string format is more complex than is easily documented here but is fully described in the info documentation.
There it is.
unnah 9 hours ago [-]
I would hope that the date formats parsed by GNU touch would still be at a lower level of complexity than the dialect of Pascal supported by Turbo Pascal... but you never know until someone checks.
Joker_vD 22 hours ago [-]
You'd think they'd put this bullshit inside some .so where it could be reused by all other coreutils; but no, it's re-included in every GNU tool that deals with parsing dates.
eterm 10 hours ago [-]
Better yet, in a completely different utility whose output could be piped into the parameter, but the lack of rich piping brings you back to parsing.
metaltyphoon 22 hours ago [-]
This can’t be right is it?
collinfunk 19 hours ago [-]
It is correct. But only 'date' and 'touch' use it, so I am not sure how much benefit there is in making it a shared library.
If size is really a concern, we have supported building a single 'coreutils' binary since 2014, which will be more effective in saving disk space. It can be done with './configure --enable-single-binary'.
Joker_vD 19 hours ago [-]
> But only 'date' and 'touch' use it, so I am not sure how much benefit there is in making it a shared library.
There is also the rest of the whole "gnulib" folder inside the coreutils repo. Yes, I know that Gnulib explicitly states in the docs that it's a source code library but it doesn't bother to explain why exactly it chose to be that instead of being a .so à la glibc (beyond some rather unrelated "but supply chain attacks!" segment in the docs — if I cared about that, I'd statically link the relevant parts of glibc as well, in fact, that would be a much higher priority).
collinfunk 17 hours ago [-]
Read section 2.2 [1]. Each package that uses Gnulib maintains a list of modules that its program(s) requires. I.e., each package has a different library built as libgnu.a.
Gnulib also doesn't make API stability guarantees like shared libraries do. If a distribution installs Gnulib as a shared (or even static) library, and then links programs to that instead of the vendored sources, they will likely end up with broken programs.
Yeah, I've read the section of 2.2 in its entirety — nothing you said in your comment is in it.
Also, "Gnulib doesn't make API stability guarantees like shared libraries do" — a) do you mean ABI? b) why not? The gnulib seems like something that's perfectly suited to be a shared library, even more so than the glibc, since it's not a language runtime.
collinfunk 11 hours ago [-]
For question A, both API and ABI. Question B is answered in the documentation.
Joker_vD 21 hours ago [-]
Yes, it can be. You can run `strings "$(command -v touch)"` yourself and then compare the output with the strings in parse-datetime.y [0]. Look for e.g. "FORTNIGHT", "sixth", and "error: parsing failed, stopped at '%s'", they're all inside the touch's executable.
But there ought to be some reason behind this that explains why that fence is there. No?
shiandow 19 hours ago [-]
Repeating the code is silly, but some degree of duplication in the binary makes sense. It's a basic size / latency trade-off.
regularfry 17 hours ago [-]
My first naive thought is never mind shared libraries, can touch just exec date when it has to?
15 hours ago [-]
mitxela 16 hours ago [-]
then people would be complaining about .so dependency hell
2/5
Joker_vD 15 hours ago [-]
Well, guess we have to be grateful that Ulrich Drepper never really got around to mess with gnulib, unlike he did with glibc.
And the .so dependency hell is real. You try to build some older version of a certain language runtime, it complains that your libssl/libcrypt lacks the functions it needs (those functions were in 1.0.1f, but 1.0.1k dropped them because that's how semver works), and of course your distro doesn't have the older version of libcrypt packaged for it so you take the package from the previous version of your distro, and it complains that your libc is too new and segfaults. Well, you sure as hell ain't rolling your system's libc to an older version so you try to rebuild libcrypt from the source, but the build with default config/flags still doesn't satisfy this certain language runtime and oh my god why am I even wasting my time on this, "docker pull certain-language:ancient" it is. Yeah, sure, this image has essentially Ubuntu 14.04 inside of it but at this point IDGAF. Why can the same 6.16 kernel run the user space both from today and from ten years before it, but the userspace from today can't run the program from eight years ago?
lelanthran 10 hours ago [-]
> There's no reason (other than laziness) why that should take more than 2k.
Well...
$ touch --help | wc -c
1580
Just the text for the help message compiled into `touch` is over 1.5kB.
It's not just laziness, it's also what the program needs to do, like (for example) print out all the options it supports (1.5kB), then parse those options, execute a different code path depending on what the user wants to do, etc.
If all you want to do is update the date or create a new empty file, I can write a very short program that does that, although the minimum program in C is around 16kB (hello world), so that's the minimum overhead needed to have a C program loaded by Linux.
pron 16 hours ago [-]
By "laziness", do you mean attention to costs? Because there's been a ~30,000x inflation in RAM between 1986 and today (probably much more, because we didn't have virtual memory, let alone fast SSDs), and what's silly is to ignore that 1GB of RAM has about the same impact on the machine as 20kB in 1986. Software back then (and even a decade later) was significantly more bloated than the "lazy" programs of today.
Of course we spent a lot of effort cramming as much as we could into every byte back then, but it wasn't because of laziness, but because there was no choice and the value of that work to the user was many, many times higher than it is today.
zvmaz 20 hours ago [-]
> There's no reason (other than laziness) why that should take more than 2k.
I presume you know some of the intricacies of coreutils or the touch program. I'll probably go and donate to whomever receives donations for coreutils; it's the least I can do: Show some respect to the developers of these free and open source tools.
raddan 21 hours ago [-]
If you run `strace` you can get a hint at why `touch` (and any modern, compiled C binary) might be big: it is doing way more than you think it does, and you definitely _want_ a lot of that. For example, any program that uses the C standard library needs to have that code available-- since virtually every C program is going to use it, it will be loaded and mmap'ped into some region of memory. The stack needs to be set up, memory protection bits will be set, a random value is read to be used as a stack canary, etc, etc. I count on the order of 50+ system calls.
Watching `mv` do its thing is even better. About 100 system calls, including playing nice with SELinux in case it happens to be installed, just to issue a single `renameat2` system call.
Don't forget that we're running on a 64-bit machine. MS-DOS in 1986 was a 16-bit machine? The word size on a modern machine is bigger because we have a bigger address space, more registers, and more instructions.
We want speed and security and convenience and pleasant error messages. All of this is put here by the compiler to ensure that we have nice things. It sounds awesome to have such a small Pascal compiler, and it makes the modern state of binaries seem bloated, but all those extra bytes are paying for things that we want. There's probably a little bloat, but really, there is not much bloat.
cowlevel 8 hours ago [-]
Most of that startup code is handled by the shared loader, which is a separate executable (masquerading as a library) at /lib/ld-linux-something
agumonkey 22 hours ago [-]
I'd love to have a graph of gnu [core]utils growth over time. IIRC in Unix days, these simple utils were simple.. until they had to support various flags, and various hosts ..
mitxela 17 hours ago [-]
The minimum size for a program is about 20k due to page alignment and sections. That's one page each for text, data, bss, rodata, and file headers that don't get loaded into memory at all.
1/5
teiferer 24 hours ago [-]
Agree with everything you wrote, but if you go look for bloat on your storage device, the last thing that will be of any significance is that overhead.
solyin 17 hours ago [-]
The biggest the things on my disk are VMs , docker images, and then I don't care to bother.
sroerick 1 days ago [-]
Why did Pascal basically die completely? It seems like a hugely influential language and was very loved, but there are plenty of other languages which still seem to have a lot of legacy code. Where is Pascal?
regularfry 23 hours ago [-]
In a way it didn't, the Lazarus project is the current most well-known incarnation. But that itself tells a story: it's for desktop applications, mainly. It never really had a "here's how you do a web app" story around it. There was a period 1998-2002 when Delphi was hot (and it genuinely was very good) but all the cool kids saw PHP3 and Flash and hopped aboard, and at that point, in retrospect, you can see the start of the decline of desktop applications. By the time Rails landed in (I think?) 2008 "do everything on the web" was what a lot of people were already talking about, even if the truth of that didn't really land until much later.
Really it could have been go-lang before go-lang and I'm not sure why it wasn't other than that it wouldn't have been controllable by the folks at Google.
marcle 7 hours ago [-]
I recently ported an old Delphi application to Lazarus (https://github.com/mclements/prevent). As my first experience with Delphi and Pascal, I was impressed with the smooth development experience (expected), the comparative richness of the libraries (unexpected), and the speed of the application (expected).
For a historical perspective, the original Delphi code was written by Jan Barendregt. After his death, I was the only person to have his source code -- where most of the comments are in Dutch:).
achikin 21 hours ago [-]
Because web was cross platform, didn’t need any “installation”, and had far better devtools included than any tech that days.
kragen 19 hours ago [-]
Not in 02002. In 02002 your JS devtools were that the browser crashed when you had a bug in your JS, so you would have to binary-search your recent changes to figure out which line of JS was crashing it, and you could evaluate expressions by typing javascript:(void)alert(f()) in the URL bar. No browser console, no web inspector, and the only portable DOM was image rollovers and form field values. If you wanted to generate document content in JS the only way that was portable to Netscape Navigator 4 was document.write().
I think we didn't even have bookmarklets at that point—the browsers supported them, but we didn't know that.
Really, it was because pascal was the go of its day with very little corporate backing (by modern standards). A language designed around developer ergonomics with some safety in mind: lovely for teaching, but only because it was a jack of all trades.
Web units were included, it's just that php became dominant because it was stupidly easy. I myself was a pascal programmer that started writing php around the time of lazarus 0.9 / fpc 1.9 and I recall that php felt like bash scripting by comparison. Today, I consider the cgi model to be rudimentary and php itself a pile of shit.
Delphi / Lazarus were GUI frameworks not different languages, and regarding Lazarus itself I'm gonna be RMS here and say that it's GNU/Linux (which it was, for some time).
Florian Klämpfl deserves some credit.
drfloyd51 16 hours ago [-]
Php stupidly easy to write something half-assed. Incredibly difficult to write something correct.
I am going to swipe at most dynamic type-unsafe languages: most developers think they are easy to write. And they are compared to type-safe. But the overall difficulty of actually maintaining a project over time and over a revolving door of coders far exceeds the difficulty of using a type-safe language to begin with.
The compiler is your friend. All the compile time error messages are runtime errors you don’t have to look for.
I get why PHP was adopted. A bunch of new coders on the web reaching for an “easy tool”. Not experienced enough to feel the slow encroachment of suck embracing them. It’s really kind of sad. We could have had better languages. Pascal in both the back and front end.
za_creature 10 hours ago [-]
I hope we don't make the same mistake twice with LLMs.
regularfry 17 hours ago [-]
Yes, but I'd say that Lazarus is the standard bearer for Pascal the way Delphi was back in the day. It would be the reason someone would pick up the language a lot of the time.
za_creature 16 hours ago [-]
Sure, in the same way Rails is why someone would pick up Ruby.
It's still called RoR though.
pjmlp 23 hours ago [-]
It didn't, despite all its management failures, several companies are still buying into Delphi (Object Pascal evolved from Turbo Pascal/Apple's Object Pascal), and there is at least an yearly conference in Germany.
Some of us are still using Turbo Pascal for CP/M on our Z80 systems. OK, a bit niche.
kragen 18 hours ago [-]
That sounds like fun. What have you written lately?
pjmlp 22 hours ago [-]
Ah, yeah, have to play with it sometime. TODO list is rather long. :)
Rochus 22 hours ago [-]
A project like this never gets finished.
pjmlp 22 hours ago [-]
Sorry for the misunderstanding, I meant my own TODO list of stuff to check out.
The project is rather cool.
AnimalMuppet 22 hours ago [-]
And that project (cool stuff to check out) never gets finished, because there's always more cool stuff.
atombender 17 hours ago [-]
ObjectPascal's downward spiral was tied to Borland's. When Borland started to struggle, there weren't any other implementations — Borland's was the only viable one.
Evne in its heyday, Borland's Pascal-based products were not that big in the developer tools market. Delphi was a huge hit in Europe, but in the US, they were dwarfed by Microsoft. So Pascal's influence is a bit like that Brian Eno saying (paraphrasing): “Only 30,000 people bought the first Velvet Underground album, but everyone who bought it started a band.”
Part of Borland's fall was betting too much on client/server database stuff at a time when the web was happening. They renamed themselves Inprise and marketed a suite of technologies called MIDAS which nobody remembers anymore. You used Delphi to build database GUIs on top of MIDAS and, say, Oracle. I don't know what they were thinking. They also did a Linux version of Delphi called Kylix which was just using Wine (!).
Even so, I suspect ObjectPascal would have failed eventually. A language tied to a GUI toolkit, without a standard spec, or a cross-platform open source implementation, just couldn't last forever.
I held onto Delphi far after it was evident that it was a dying language. I actually did a ton of my work in the 1990s and early 2000s doing non-GUI stuff in Delphi, including web backends and commercial games, which I suspect was not that common. ObjectPascal actually worked wonderfully as a server-side language. It was a strict, statically typed language, it had modern constructs like classes and threads, it was natively compiled, very fast, had a terrific interactive debugger. In many ways a perfectly fine alternative to C++ at the time, including for game development — I made my own bindings for DirectDraw, DirectSound, and so on.
At the time — say, around 2000 — I didn't find the alternatives compelling. Java was dead slow and didn't offer anything language-wise. Languages like Python were also slow and were not type-safe. But there came a point when Linux had just taken over, and ObjectPascal wasn't a viable option anymore.
Today, the closest thing in spirit to the ObjectPascal language isn't C#, I think, but Go.
pjmlp 9 hours ago [-]
It really isn't Go, it isn't even as half as rich as Turbo Pascal 7 abilities, let alone everything else Delphi added on top.
They refuse to even have Pascal like enumerations, rather pushing that stupid iota/const boilerplate without any of the nice features that Pascal enumerations had in 1970's.
Rather take C# when given the option.
atombender 6 hours ago [-]
In spirit, not in abilities. I think Go inherits many of the qualities of ObjectPascal:
• Extremely fast compilation (even if at the cost of throwing away generations of optimizations)
• Strict, somewhat impoverished type system
• Simple but pragmatic module system (Go has packages, OP has units)
• High focus on integrated tooling (e.g. built-in assembler/linker)
• Safe strings and dynamic arrays built into language
• Built-in reflection and a runtime that often makes use of it
I would argue that if you gave ObjectPascal a C-ish syntax and added built-in concurrency and GC, it would look and feel more like Go than anything else.
Yes, OP has enums and ranges and Java-style interfaces, but those are minor details.
pjmlp 6 hours ago [-]
Object Pascal at the time Apple created it as evolution from Clascal, not as when Borlad took it up.
> Extremely fast compilation...
> Safe strings and dynamic arrays built into language
Even Lisp and PL/I have these ones, we really lost focus with C's adoption.
> I would argue that if you gave ObjectPascal a C-ish syntax and added built-in concurrency and GC, it would look and feel more like Go than anything else.
That is C++ Builder.
atombender 6 hours ago [-]
Lisp is not natively compiled or statically typed. I think you're missing the point here. C++ Builder is nothing like ObjectPascal or Go.
pjmlp 4 hours ago [-]
Lisp surely is compiled, since the early 1970's.
I have used all Borland products starting with Turbo BASIC 1.0, moving into Turbo Pascal 3.0 and then all TP versions, Turbo C++ 1.0 all the way up to the last Turbo C++ for Windows 3.1 version.
Delphi up to Delphi 5, and the accompanying C++ Builder releases.
Go is really nothing like Object Pascal, nor in features, nor in spirit.
It is a mix of Limbo with Oberon-2 method syntax, from UNIX folks that were always quite against Pascal, none of the authors is fond of Object Pascal, and it shows.
atombender 4 hours ago [-]
Again, "in spirit". Go and ObjectPascal are both a pragmatic, engineering-focused, imperative/procedural, strict, simplistic, statically typed languages with mutability and no memory safety — the differences are superficial, and the philosophies are very close. There is a huge conceptual and philosophical distance between them and, say, Lisp or PL/I or indeed C++.
pjmlp 3 hours ago [-]
Again, only Object Pascal as initially released by Apple.
Though Borland had some commercial success, I remember Pascal mainly as a teaching language.
camtarn 17 hours ago [-]
IEC61131 Structured Text, used to program PLCs and other industrial automation systems, is also based on Pascal. Very niche, but definitely still alive.
cwnyth 1 days ago [-]
Odin borrows from Pascal as well.
SoftTalker 22 hours ago [-]
Can't believe I forgot PL/SQL, as I used that heavily for years.
Ada also was widely used in aerospace/military applications, though not sure it's still used for anything new today.
jll29 1 days ago [-]
Julia is also heavily influenced by Pascal syntax.
nl 8 hours ago [-]
In the 80s Pascal was a serious competitor to C for systems programming as well as applications. Large amounts of the original Mac Finder were in Pascal for example.
The lack of a good web platform has been mentioned but also there wasn't really any Unix heritage and on Windows the .NET platform and C# killed the advantages Delphi had over Visual Basic 6.
I was a Delphi developer for a bit and most of us moved to Java if we wanted to stay if Microsoft platforms.
kristianp 16 hours ago [-]
From about 1992 C and C++ became hugely popular. Microsoft was promoting their C/C++ compiler for example. In '92, MFC was available for Windows 3.1. Apple got on C/C++ the bandwagon too. Not sure of the timing, but the Mac was originally a Pascal development environment, with the toolbox in assembly.
Not sure if you are being sarcastic. Pascal strings are first class citizens, so it's trivial to add null-termination. Delphi actually does this to allow typecasting.
C, for example, doesn't have strings. It has pointers to memory that might contain characters and, if you are lucky and the stars are aligned, a zero to mark the end. I'll never understand how C strings were accepted as a string representation and not the mad source of bugs and insanity that they are.
tzot 20 hours ago [-]
> I'll never understand how C strings were accepted as a string representation
1972 was definitely not a good year for C standardization bodies. I blame that guy Ritchie and his audacity to hack a language on a whim. Even his GitHub page is empty (or misattributed).
pjmlp 9 hours ago [-]
UNIX source code being freely available against big bucks for the other systems kind of helped.
UNIX and C would never had taken off as they did, had they been sold just like VAX/VMS or MVS.
TacticalCoder 19 hours ago [-]
> Why did Pascal basically die completely?
It morphed into Delphi. The reason that it's not that successful anymore is that it was deeply tied to Windows (even if there were half-arsed Macintosh ports).
And then the Internet taking off happened.
And suddenly you had gigantic companies built on PHP/JavaScript/Linux (like Facebook), on open-source software (Google) and Pascal/Delphi got also attacked by actually portable stuff, like Java, which some of today's biggest companies were built on (like Amazon).
So on one hand Linux and it's myriad of open-source languages and on the other hand Java (which is what it is but it is portable) and then JavaScript in the browser.
Nowadays tens of billions of devices, including many servers powering the entire world, are running Linux. While Pascal/Delphi was that language you'd run on DOS and half-arsedly ported to Windows: not a winning proposition.
anthk 1 days ago [-]
Free Pascal/Lazarus it's rocking nice tools such as Peazip and other stuff like Carte Du Ciel and some RAD tools in the enterprise. On the niche geeky world, there's T3X at https://t3x.org which is semi-Pascal like.
coliveira 1 days ago [-]
The main problem with Pascal was not having a standard at a time when having a standard was important for adoption. There were several successful implementations like Borland's, and the version used in the Macintosh, but being closed products they never talked to each other. It's similar to the situation of Basic: lots of code was created in Basic but none was compatible with a standard and was essentially lost.
pjmlp 23 hours ago [-]
It certainly had a standard, two actually, however no one cared because Turbo Pascal was more relevant, and Modula-2 was designed to fix Pascal's shortcomings, which also has a ISO standard.
So it wasn't for lack of standard per se.
sehugg 1 days ago [-]
Carmack developing DOOM on a NeXT and porting it to PC was a very good advertisement for C.
pjmlp 23 hours ago [-]
The tooling was done in Objective-C.
twoodfin 23 hours ago [-]
Not just having a standard but being able to collectively evolve a standard.
In the absence of that, Pascal’s creators and commercializers invented follow-on languages, including the most successful thread via Hejlsberg as we’re discussing here: Object Pascal -> Delphi -> C#/.NET—with a brief detour to J++, which I don’t know enough about to understand if it belongs in this sequence.
pjmlp 23 hours ago [-]
Outside Borland and Apple, people tend to forget that already in 1976, Niklaus Wirth came up with Modula-2, exactly to fix all the shortcomings from a language originally designed for teaching, with one properly designed for systems programing from the start.
As for your sequence, from someone that was around back then, .NET and C# only exist as you know it thanks to Sun's lawsuit regarding Java language and runtime extensions introduced in J++.
Then an internal research language originally named Cool, became C#, the language extensions in J++ were made into C# features (events, J/Direct, COM interop), Windows Foundation Classes became Windows Forms, and J# was released in .NET 1.0 as transiton technology.
Had it not been for the lawsuit, Ext-VOS (.NET codename) would have been released with J++ instead.
Amazing, thanks! I was also there for the commercial and legal history of J++ but was unsure how much J++ incorporated what would become “Cool” ideas.
Can’t wait to read the VOS paper.
nl 8 hours ago [-]
There's also the Ada branch if we are talking about Modula-2.
Not Pascal but it comes from that tree.
pjmlp 7 hours ago [-]
Sure, but the point was about how everyone complains about the original Pascal, and the related dialects to fix its shortcomings, while ignoring that shortly thereafter its creator solved all of them, by designed another programming language actually targeted to large scale software development and systems programming from the start.
Given Niklaus Wirth pursue for minimalist systems programming design since Oberon, I doubt he was a big fan of Ada83, let alone Ada2022.
For reference, ZX-Spectrum has 48Kb of RAM out of which 8Kb is video memory, so unusable.
Then you have to load the Pascal compiler into the remaining 40k of RAM. Allocate some RAM for stack and environment variables for the editor where you write your program, plus space for the actual program. Then compile your program into the same 40k of space. And run it, using heap and stack memory from which memory space? You guessed right, same 40k.
To recap, on 40k of RAM you had back then:
- The Pascal compiler
- The Pascal source code in text form
- The Pascal executable form in machine code
- The Pascal data/memory. Of which, recently in a "tech demo" of automated tests, one colleague said "unfortunately we only have a very limited amount of RAM to be able to do basically anything [that's why the product is a mess with no tests]. Only 32Gb per [virtual] machine".
One of my first programs was a Tetris clone, because ZX-Spectrum BASIC was slow as molasses. All on top of only having tape for storage so if I fucked up a pointer (I don't think Pascal had the concept of access violation back then but I sure discovered it on my own skin), it would take 5 minutes to load the Pascal compiler + some backup copy of my Tetris game, hopefully not from a month ago and hopefully I remember what I changed. Lots to discover and have "fun" with.
About a year later I did find a compiler for BASIC and it turned the unplayable BASIC code for Tetris I wrote in the 9th grade into a totally playable Tetris game, without the need to learn another language and paradigm (pointers!) but the damage was done. Ignoring a year of databases, in 12th grade of high school computer science class (elite class, found there basically all the Math olympics I was competing with in gymnasium), I got introduced to C and from then on, here I am, 30 years later, doing C++ in finance for an S&P 500 company.
virgulino 24 hours ago [-]
Kaaaaaaaaaaaahhhnnn!!!
pron 16 hours ago [-]
Just keep in mind that the amount of RAM in an average PC in 1986 was about 30,000x smaller than the average amount of RAM in today's laptops, and Turbo Pascal was no less "bloated" than, say, VS Code.
15 hours ago [-]
ttoinou 1 days ago [-]
I’m tired of those senseless comparisons
Bytes have history, meaning, context of creation, different utilities and different cost associated with creation/transfer/storage/manipulation
We could also use those comparisons to praise how complicated our current world has become and how good we are at managing such complexity
atiedebee 19 hours ago [-]
Complexity is not something to strive for, but something to be avoided. I would also argue that we aren't good at managing that complexity at all.
ttoinou 13 hours ago [-]
We do software for people.
Engineers who complain about accidental complexity need to show that this complexity doesn’t come from the real world
Timwi 8 hours ago [-]
I think the issue isn't with the comparison itself, but with the conclusion drawn. Pascal compiler is smaller than `touch`, therefore Pascal compiler was amazingly efficient and `touch` is super bloated.
I think a better conclusion is that the Pascal compiler was very limited and modern `touch` is very feature-rich (many comments in this thread have explained how) and it shows that we've come a long way.
If you actually used that Pascal compiler from the 80s, you'd immediately notice the limitations.
t43562 8 hours ago [-]
Turbo pascal was incredibly impactful - it gave lots of people like me an efficient compiler in an IDE with a superb graphics library (BGI) and superb compile speeds and one didn't need to swap floppy disks to compile. It was an amazing learning tool.
Touch, on my 1980s computer, would have been seen as a caricature. It would have been a 200 byte .com file back then, if that. The comparison is about what you can do with what you have if you have no other choice, and how plentiful resources don't automatically create empowering outcomes.
mbfg 9 hours ago [-]
A much greater proportion of code written in 80s/90s was single user/run-and-done applications, not applications that stood up for weeks or months, used by thousands/millions of people. I believe much of the "bloat" came about because building robust memory stable systems is hard and relying on 3rd party libraries to do so was the rational choice for most.
t43562 8 hours ago [-]
There were memory safe operating systems at the time which could probably have worked once the 286/386 were out.
Everything was about compatibility - that's really why we were stuck with int 21 and almost no other help from the OS to insulate us from the hardware. There wasn't a standard C library with millions of features - or anything else - that could add overhead to hello world.
Every program had its own drivers - everything was optimised for that use case and not some general set of cases.
1 days ago [-]
oldjohnnylane 23 hours ago [-]
The wall of defensive, hostile replies to this simple post is expected. Today’s programmers need to feel like they are an elite class above the rabble and programming is their identity. When someone shows them an example of what talented programming really looks like, they have to pile on and dismiss it from a thousand cuts. The guy who wrote Pascal understood the system top to bottom, and understood computer science. There are maybe a few thousand programmers alive today with that kind of skill, and it hurts the egos of the average HN typescript scrum jockey to see something they just don’t comprehend so they lash out at it.
ejb999 22 hours ago [-]
well said.
tetha 23 hours ago [-]
It's always an interesting thought that I had meetings about the log aggregation dropping stack traces that would take ~3 3.5" floppies to store. Each.
Zabbix also confuses operators at this point. I recently had to increase a cache. I chose to go from a solid 4MB to a luxurious 256MB.
I know high-performance Java, so just a little jab there, but you don't size JVM parameters like that, except maybe code caches. And before Rust comes in, we also have a Rust application running without good resource control and it wouldn't like those resource constraints.
There is truth to this article.
mitxela 16 hours ago [-]
How did you manage to make a 4MB long stack trace? Recursive stack overflow with the middle part not omitted?
3/5
weinzierl 22 hours ago [-]
"And the whole thing was lightning fast, orders of magnitude faster at building projects than Microsoft's compilers."
Sure, I mean it had a turbo whereas Microsoft only ever had quick things. A shame no one thought of swift back then.
hollowonepl 21 hours ago [-]
I absolutely adore the level of irony and a bit of sarcasm in each bit of the comparison represented by the referred article
ilaksh 1 days ago [-]
This is only slightly related but I just made a Turbo Vision UI for Claude Code sessions.
Amusingly i also used Turbo Vision to make some agentic harness[0] :-P (though mine is meant to talk with llama-server via its OpenAI compatible endpoint since i'm using local models - the one in the shot is Gemma 4 E4B which i'm using for testing).
That said i never finished that and ended up making another one (using tvchat as a base since it had largely working communication and session management) that acts as a server/daemon inside the container is meant to run in the background and provides a web-based UI instead.
cool. can you drag & drop in files (e.g. screenshots, PDFs, video recordings, text files, etc.) for context when you work on features or bug fixes? Cursor is great at workflows like that.
ilaksh 1 days ago [-]
no, but good idea, I am having Claude add that.
EDIT: done. if your terminal doesn't support drag-and-drop (kitty and some others do) there is also a new File | Attach file(s) menu item
throwaway2037 1 days ago [-]
> zlib.h in the Mac OS X Lion SDK (80,504 bytes).
What a stupid comparison. zlib.h is probably 99% comments.
gmueckl 24 hours ago [-]
Is it such a stupid comparison? It's an absolutely trivial amount of data now, but back in the 80s, a few files of that size would fill out a floppy disk. It's also a source file - the input to a compiler.
01HNNWZ0MV43FF 22 hours ago [-]
But literate programming is the old hotness
ejb999 22 hours ago [-]
Way to miss the point entirely...
Lerc 20 hours ago [-]
I have been meaning to do an XKCD radiation/money style chart for memory for some time now.
Of course now it would be a trivial job for an AI to make the chart. Finding a authoritative source for byte counts, probably less so.
bell-cot 1 days ago [-]
Well, yeah. Back in the mid-80's, software needed to be usable on a computer with a single 360KB floppy drive. (No HD, no SSD, no USB, no network, no ...) And even a big budget for RAM - which cost many orders of magnitude more than today - would really not get you around Bill Gates' 640KB DOS memory limit.
Comparing to current-day stuff is kinda like comparing battery-powered bathtub toys to jetskis.
probably_wrong 1 days ago [-]
Those "bathtub toys" built the entire modern infrastructure, parts of which are still chugging along. If anything, I'd put the onus on software developers - like John Carmack said in 2005, "there is something deeply wrong when text editing on a 3.6 ghz processor is anything but instantaneous".
Software in the 80s showed what's possible when you really care about doing it. Software in the last 15 years feels like an exercise on what happens when you don't.
I remember Windows 98, where it crashed every few hours and took everything with it, but while it worked, it never missed a keystroke or mouse press. I could type ahead and click where I knew the button would appear in 10 seconds and it still wouldn't lose anything. Nowadays you just finish typing out a thought and then realise half of it never turned up, because something else claimed the focus or whatever.
More like comparing a racing kayak to a leaky container ship burning sulfurous bunker fuel carrying a load of short-lived consumer junk. :-)
MonkeyClub 1 days ago [-]
Yet at the same time, one is a pastime for an affluent lifestyle while the other is driving the global economy. Interestingly, or ironically, the former was probably put on the shelves by means of the latter.
If there is any positive progress to be made, the rethinking necessary must go much, much deeper than the superficial flesh of the problem, but there it’s bound to hit upon the sinews and bones of vested interests.
In all, as I’m growing older and see the world trudge along the same lines it did centuries ago, I’m more and more pessimistic about the possibility of people agreeing that the sacrifices necessary will be made.
Short-term stakeholder interests seem to trump any notions of longer-term greater good.
andersonpico 1 days ago [-]
> one is a pastime for an affluent lifestyle while the other is driving the global economy
which one is which?
MonkeyClub 18 hours ago [-]
The one that’s available off the shelf or by click to order and can be delivered to
your porch by a reasonably sized delivery van :)
1 days ago [-]
1 days ago [-]
1 days ago [-]
20 hours ago [-]
haaz 1 days ago [-]
[flagged]
MattCruikshank 1 days ago [-]
It's a full compiler and debugger. It's not at all obvious that it could be smaller than an image.
jsymolon 20 hours ago [-]
After creating a C11 (-ish) compiler in 65816 assembly that barely fits into 64K, how the heck does the compiler and ide fit into 39k ?
Gibbon1 8 hours ago [-]
My hunch is because it's easy to build a pascal interpreter it's easy to extend that as a code generator.
mikestew 1 days ago [-]
“Obviously”. Look, if you don’t really know what a development environment is, that’s okay. But a dismissive comment such as this makes it obvious to the rest of us that you don’t know, when I’m confident that isn’t your goal.
noir_lord 1 days ago [-]
If you want to be entertained have a look at their comment history.
However the language extensions that were the reason for the lawsuit did indeed transition from J++ into C#, with J# being J++ on top of .NET for easing code porting.
The features were events, J/Direct (later P/Invoke on .NET), COM interop (later RCW/CCW on .NET), and Windows Foundation Classes (later Windows Forms on .NET).
Thanks to the good work of internet archivists,
https://archive.org/details/microsoftvisualj00micr
https://download.microsoft.com/download/1/6/d/16d24ada-5317-...
https://www.microsoft.com/en-us/download/details.aspx?id=559...
The irony is that two decades later Microsoft has an OpenJDK distribution, and they were the ones that initially provided the ARM port for Windows.
https://www.microsoft.com/openjdk
https://www.zdnet.com/article/microsoft-completes-phase-one-...
Fundamentally, many inefficiencies were justified for developer productivity, and I'm not sure that makes sense anymore, and the cost of larger projects with clear abstraction boundaries has plummetted.
Having lived through this period, I would disagree, quite the opposite we tended to develop in C and assembly specifically for runtime efficiency because we had to.
For developer productivity you could opt for Lisp or SmallTalk or some such, which ran much slower until high quality compilers for these became available, and even then your target machine might only have a C compiler.
Now, developer productivity is becoming less important as developers are factored out entirely.
Rust is becoming popular as LLM output. The resulting code is very efficient. The compiler helps keep the LLM on track and holds it to a minimum level of quality. Humans can read it if they want to. But it is not great to read.
Python is also a popular target. Easy to audit. LOTS of training data. The “one way to do it” philosophy of Python helps. But the resulting code is not very efficient.
I think we will end up with a new language that balances all these things better.
It can be the difference in a loop that an agent can crank on in Go for 15-30min while I get a coffee vs taking multiple hours in Rust, sometimes.
Anything agent-focused language/ecosystem wise needs to focus on small-blast-radius/fast-iteration.
(Unless/until there's a generational leap in the raw coding ability of these tools to be able to get it "right" (for larger-and-larger definitions of "right") the first time.)
Maybe it will have human words inside of it to explain the parts.
Most of the way we organize code is to support our brains. Code reuse via classes and functions. Extensible patterns. Classes.
AI doesn’t need all that stuff. Consider, AI needs what assembly needs. And assembly doesn’t have any of those conveniences.
At some point AI will stop writing code for us to pretend we own and start writing it for itself. I am curious to see what conventions arise to support a programmer whose brain has infinite storage capacity and can figure out what existing code does without having to remember or read documentation.
Like "agent has to send email with specific content on trigger A", test "has to validate email arrives with expected content"
How the agent actually reacts on the trigger or sends the email, those are agentic runtime details.
See platforms like Boomi.
Already when coding on cloud environments like Workato and Boomi there is no code output to look at.
UNIX. Seriously. Look at what it could do with 1970s era hardware, that was unmatched even when DOS came out in the early 80s.
During the 1970's, VAX/VMS and Xerox PARC workstation OSes, ML, CLU, were more inspiring for 1970's hardware capabilities.
It's the lack of clear abstraction boundaries that causes decreased developer productivity.
A code generator will not save you from Conway's law.
The next few years are going to be fun.
I don’t believe that source code is a spec. Source code has real time manipulation a kind of temporal dependency. Specs are declarative.
The difference is a spec would say: adding two and three should equal five. Code says you have a variable give it the value two. Now add three to it. Return that value. Maybe a unit test to assert it returned 5. Code defines how a spec is satisfied.
But the kernel sandbox is NOT A PART OF V8. It's not even reusable or modular, it's a hard coded part of Chrome's startup sequence and tuned for Chrome's exact needs. If you embed V8 via its API you don't get it.
I've seen this misconception several times now including in quite serious places, where people talk as if V8 on its own has a robust sandbox. It doesn't! This will blow up in people's faces eventually.
If you want a JS engine that's secure by design then the only one I know is GraalJS, as it's written in a memory safe language and uses partial evaluation to create its compiler so you can't get interpreter/JIT mismatches. It also has a proper sandboxing API and can transparently run code out of process. They're experimenting with integrated Landlock support now, so it actually will get a built in kernel sandbox on Linux out of the box, unlike V8.
This issue vexes me enough that I wrote a whole article about it:
https://medium.com/graalvm/writing-truly-memory-safe-jit-com...
There's an introduction to the sandboxing APIs here:
https://medium.com/graalvm/sandboxing-script-extensions-with...
There's no reason (other than laziness) why that should take more than 2k.
On the other hand, a lot of boilerplace code is repeated in each and every command. When I first learned as a kid about UNIX commands being ordinary programs, I was intrigued (there is nothing "special" about them, you can also write your own!) but also shocked about the overhead compared to an architecture in which e.g. the shell contained all (at least core) commands compiled into a single binary, which could share all the error handing, startup code, command line parsing code and so on.
GNU coreutils touch does a lot more than that. My local copy is about 95k; it allows for choosing from multiple different timestamps to update; suppressing the (default) creation of an empty file if it doesn't already exist; operating on symlinks directly rather than following them (if the system supports it); specifying a custom timestamp rather than "now" (including by parsing a date string), and of course outputting a help message and a version.
I did a quick estimate by disassembling touch with objdump on macOS (163 kB executable), and it was approximately 6 kB (1500 instructions * 4 bytes/instruction). There is a lot more to an executable than executable code.
> DATE STRING
> The --date=STRING is a mostly free format human readable date string such as "Sun, 29 Feb 2004 16:21:42 -0800" or "2004-02-29 16:21:42" or even "next Thursday". A date string may contain items indicating calendar date, time of day, time zone, day of week, relative time, relative date, and numbers. An empty string indicates the beginning of the day. The date string format is more complex than is easily documented here but is fully described in the info documentation.
There it is.
If size is really a concern, we have supported building a single 'coreutils' binary since 2014, which will be more effective in saving disk space. It can be done with './configure --enable-single-binary'.
There is also the rest of the whole "gnulib" folder inside the coreutils repo. Yes, I know that Gnulib explicitly states in the docs that it's a source code library but it doesn't bother to explain why exactly it chose to be that instead of being a .so à la glibc (beyond some rather unrelated "but supply chain attacks!" segment in the docs — if I cared about that, I'd statically link the relevant parts of glibc as well, in fact, that would be a much higher priority).
Gnulib also doesn't make API stability guarantees like shared libraries do. If a distribution installs Gnulib as a shared (or even static) library, and then links programs to that instead of the vendored sources, they will likely end up with broken programs.
[1] https://www.gnu.org/software/gnulib/manual/gnulib.html#Libra...
Also, "Gnulib doesn't make API stability guarantees like shared libraries do" — a) do you mean ABI? b) why not? The gnulib seems like something that's perfectly suited to be a shared library, even more so than the glibc, since it's not a language runtime.
[0] https://github.com/coreutils/gnulib/blob/master/lib/parse-da...
2/5
And the .so dependency hell is real. You try to build some older version of a certain language runtime, it complains that your libssl/libcrypt lacks the functions it needs (those functions were in 1.0.1f, but 1.0.1k dropped them because that's how semver works), and of course your distro doesn't have the older version of libcrypt packaged for it so you take the package from the previous version of your distro, and it complains that your libc is too new and segfaults. Well, you sure as hell ain't rolling your system's libc to an older version so you try to rebuild libcrypt from the source, but the build with default config/flags still doesn't satisfy this certain language runtime and oh my god why am I even wasting my time on this, "docker pull certain-language:ancient" it is. Yeah, sure, this image has essentially Ubuntu 14.04 inside of it but at this point IDGAF. Why can the same 6.16 kernel run the user space both from today and from ten years before it, but the userspace from today can't run the program from eight years ago?
Well...
Just the text for the help message compiled into `touch` is over 1.5kB.It's not just laziness, it's also what the program needs to do, like (for example) print out all the options it supports (1.5kB), then parse those options, execute a different code path depending on what the user wants to do, etc.
If all you want to do is update the date or create a new empty file, I can write a very short program that does that, although the minimum program in C is around 16kB (hello world), so that's the minimum overhead needed to have a C program loaded by Linux.
Of course we spent a lot of effort cramming as much as we could into every byte back then, but it wasn't because of laziness, but because there was no choice and the value of that work to the user was many, many times higher than it is today.
I presume you know some of the intricacies of coreutils or the touch program. I'll probably go and donate to whomever receives donations for coreutils; it's the least I can do: Show some respect to the developers of these free and open source tools.
Watching `mv` do its thing is even better. About 100 system calls, including playing nice with SELinux in case it happens to be installed, just to issue a single `renameat2` system call.
Don't forget that we're running on a 64-bit machine. MS-DOS in 1986 was a 16-bit machine? The word size on a modern machine is bigger because we have a bigger address space, more registers, and more instructions.
We want speed and security and convenience and pleasant error messages. All of this is put here by the compiler to ensure that we have nice things. It sounds awesome to have such a small Pascal compiler, and it makes the modern state of binaries seem bloated, but all those extra bytes are paying for things that we want. There's probably a little bloat, but really, there is not much bloat.
1/5
Really it could have been go-lang before go-lang and I'm not sure why it wasn't other than that it wouldn't have been controllable by the folks at Google.
For a historical perspective, the original Delphi code was written by Jan Barendregt. After his death, I was the only person to have his source code -- where most of the comments are in Dutch:).
I think we didn't even have bookmarklets at that point—the browsers supported them, but we didn't know that.
Hem hem,
https://www.freepascal.org/
---
Really, it was because pascal was the go of its day with very little corporate backing (by modern standards). A language designed around developer ergonomics with some safety in mind: lovely for teaching, but only because it was a jack of all trades.
Web units were included, it's just that php became dominant because it was stupidly easy. I myself was a pascal programmer that started writing php around the time of lazarus 0.9 / fpc 1.9 and I recall that php felt like bash scripting by comparison. Today, I consider the cgi model to be rudimentary and php itself a pile of shit.
Delphi / Lazarus were GUI frameworks not different languages, and regarding Lazarus itself I'm gonna be RMS here and say that it's GNU/Linux (which it was, for some time).
Florian Klämpfl deserves some credit.
I am going to swipe at most dynamic type-unsafe languages: most developers think they are easy to write. And they are compared to type-safe. But the overall difficulty of actually maintaining a project over time and over a revolving door of coders far exceeds the difficulty of using a type-safe language to begin with.
The compiler is your friend. All the compile time error messages are runtime errors you don’t have to look for.
I get why PHP was adopted. A bunch of new coders on the web reaching for an “easy tool”. Not experienced enough to feel the slow encroachment of suck embracing them. It’s really kind of sad. We could have had better languages. Pascal in both the back and front end.
It's still called RoR though.
https://entwickler-konferenz.de/en
Then there is still FreePascal, Mikroe Pascal and RemObjects Pascal to chose from.
And now also Micron, which re-added Pascal features to Oberon (https://github.com/rochus-keller/micron/).
The project is rather cool.
Evne in its heyday, Borland's Pascal-based products were not that big in the developer tools market. Delphi was a huge hit in Europe, but in the US, they were dwarfed by Microsoft. So Pascal's influence is a bit like that Brian Eno saying (paraphrasing): “Only 30,000 people bought the first Velvet Underground album, but everyone who bought it started a band.”
Part of Borland's fall was betting too much on client/server database stuff at a time when the web was happening. They renamed themselves Inprise and marketed a suite of technologies called MIDAS which nobody remembers anymore. You used Delphi to build database GUIs on top of MIDAS and, say, Oracle. I don't know what they were thinking. They also did a Linux version of Delphi called Kylix which was just using Wine (!).
Even so, I suspect ObjectPascal would have failed eventually. A language tied to a GUI toolkit, without a standard spec, or a cross-platform open source implementation, just couldn't last forever.
I held onto Delphi far after it was evident that it was a dying language. I actually did a ton of my work in the 1990s and early 2000s doing non-GUI stuff in Delphi, including web backends and commercial games, which I suspect was not that common. ObjectPascal actually worked wonderfully as a server-side language. It was a strict, statically typed language, it had modern constructs like classes and threads, it was natively compiled, very fast, had a terrific interactive debugger. In many ways a perfectly fine alternative to C++ at the time, including for game development — I made my own bindings for DirectDraw, DirectSound, and so on.
At the time — say, around 2000 — I didn't find the alternatives compelling. Java was dead slow and didn't offer anything language-wise. Languages like Python were also slow and were not type-safe. But there came a point when Linux had just taken over, and ObjectPascal wasn't a viable option anymore.
Today, the closest thing in spirit to the ObjectPascal language isn't C#, I think, but Go.
They refuse to even have Pascal like enumerations, rather pushing that stupid iota/const boilerplate without any of the nice features that Pascal enumerations had in 1970's.
Rather take C# when given the option.
• Extremely fast compilation (even if at the cost of throwing away generations of optimizations)
• Strict, somewhat impoverished type system
• Simple but pragmatic module system (Go has packages, OP has units)
• High focus on integrated tooling (e.g. built-in assembler/linker)
• Safe strings and dynamic arrays built into language
• Built-in reflection and a runtime that often makes use of it
I would argue that if you gave ObjectPascal a C-ish syntax and added built-in concurrency and GC, it would look and feel more like Go than anything else.
Yes, OP has enums and ranges and Java-style interfaces, but those are minor details.
> Extremely fast compilation...
> Safe strings and dynamic arrays built into language
Even Lisp and PL/I have these ones, we really lost focus with C's adoption.
> I would argue that if you gave ObjectPascal a C-ish syntax and added built-in concurrency and GC, it would look and feel more like Go than anything else.
That is C++ Builder.
I have used all Borland products starting with Turbo BASIC 1.0, moving into Turbo Pascal 3.0 and then all TP versions, Turbo C++ 1.0 all the way up to the last Turbo C++ for Windows 3.1 version.
Delphi up to Delphi 5, and the accompanying C++ Builder releases.
Go is really nothing like Object Pascal, nor in features, nor in spirit.
It is a mix of Limbo with Oberon-2 method syntax, from UNIX folks that were always quite against Pascal, none of the authors is fond of Object Pascal, and it shows.
Though Borland had some commercial success, I remember Pascal mainly as a teaching language.
Ada also was widely used in aerospace/military applications, though not sure it's still used for anything new today.
The lack of a good web platform has been mentioned but also there wasn't really any Unix heritage and on Windows the .NET platform and C# killed the advantages Delphi had over Visual Basic 6.
I was a Delphi developer for a bit and most of us moved to Java if we wanted to stay if Microsoft platforms.
https://en.wikipedia.org/wiki/Macintosh_Programmer%27s_Works...
C, for example, doesn't have strings. It has pointers to memory that might contain characters and, if you are lucky and the stars are aligned, a zero to mark the end. I'll never understand how C strings were accepted as a string representation and not the mad source of bugs and insanity that they are.
1972 was definitely not a good year for C standardization bodies. I blame that guy Ritchie and his audacity to hack a language on a whim. Even his GitHub page is empty (or misattributed).
UNIX and C would never had taken off as they did, had they been sold just like VAX/VMS or MVS.
It morphed into Delphi. The reason that it's not that successful anymore is that it was deeply tied to Windows (even if there were half-arsed Macintosh ports).
And then the Internet taking off happened.
And suddenly you had gigantic companies built on PHP/JavaScript/Linux (like Facebook), on open-source software (Google) and Pascal/Delphi got also attacked by actually portable stuff, like Java, which some of today's biggest companies were built on (like Amazon).
So on one hand Linux and it's myriad of open-source languages and on the other hand Java (which is what it is but it is portable) and then JavaScript in the browser.
Nowadays tens of billions of devices, including many servers powering the entire world, are running Linux. While Pascal/Delphi was that language you'd run on DOS and half-arsedly ported to Windows: not a winning proposition.
So it wasn't for lack of standard per se.
In the absence of that, Pascal’s creators and commercializers invented follow-on languages, including the most successful thread via Hejlsberg as we’re discussing here: Object Pascal -> Delphi -> C#/.NET—with a brief detour to J++, which I don’t know enough about to understand if it belongs in this sequence.
As for your sequence, from someone that was around back then, .NET and C# only exist as you know it thanks to Sun's lawsuit regarding Java language and runtime extensions introduced in J++.
Then an internal research language originally named Cool, became C#, the language extensions in J++ were made into C# features (events, J/Direct, COM interop), Windows Foundation Classes became Windows Forms, and J# was released in .NET 1.0 as transiton technology.
Had it not been for the lawsuit, Ext-VOS (.NET codename) would have been released with J++ instead.
https://web.archive.org/web/20190111203733/https://blogs.msd...
Follow the linked paper for Ext-VOS, aka COM+ Runtime, aka .NET.
Microsoft would revisit this COM+ Runtime a decade later with WinRT,
https://arstechnica.com/features/2012/10/windows-8-and-winrt...
Can’t wait to read the VOS paper.
Not Pascal but it comes from that tree.
Given Niklaus Wirth pursue for minimalist systems programming design since Oberon, I doubt he was a big fan of Ada83, let alone Ada2022.
Here's a page from the book I was reading in 1993: https://imgur.com/a/7UWdGgS
For reference, ZX-Spectrum has 48Kb of RAM out of which 8Kb is video memory, so unusable.
Then you have to load the Pascal compiler into the remaining 40k of RAM. Allocate some RAM for stack and environment variables for the editor where you write your program, plus space for the actual program. Then compile your program into the same 40k of space. And run it, using heap and stack memory from which memory space? You guessed right, same 40k.
To recap, on 40k of RAM you had back then:
- The Pascal compiler
- The Pascal source code in text form
- The Pascal executable form in machine code
- The Pascal data/memory. Of which, recently in a "tech demo" of automated tests, one colleague said "unfortunately we only have a very limited amount of RAM to be able to do basically anything [that's why the product is a mess with no tests]. Only 32Gb per [virtual] machine".
One of my first programs was a Tetris clone, because ZX-Spectrum BASIC was slow as molasses. All on top of only having tape for storage so if I fucked up a pointer (I don't think Pascal had the concept of access violation back then but I sure discovered it on my own skin), it would take 5 minutes to load the Pascal compiler + some backup copy of my Tetris game, hopefully not from a month ago and hopefully I remember what I changed. Lots to discover and have "fun" with.
About a year later I did find a compiler for BASIC and it turned the unplayable BASIC code for Tetris I wrote in the 9th grade into a totally playable Tetris game, without the need to learn another language and paradigm (pointers!) but the damage was done. Ignoring a year of databases, in 12th grade of high school computer science class (elite class, found there basically all the Math olympics I was competing with in gymnasium), I got introduced to C and from then on, here I am, 30 years later, doing C++ in finance for an S&P 500 company.
Bytes have history, meaning, context of creation, different utilities and different cost associated with creation/transfer/storage/manipulation
We could also use those comparisons to praise how complicated our current world has become and how good we are at managing such complexity
Engineers who complain about accidental complexity need to show that this complexity doesn’t come from the real world
I think a better conclusion is that the Pascal compiler was very limited and modern `touch` is very feature-rich (many comments in this thread have explained how) and it shows that we've come a long way.
If you actually used that Pascal compiler from the 80s, you'd immediately notice the limitations.
Touch, on my 1980s computer, would have been seen as a caricature. It would have been a 200 byte .com file back then, if that. The comparison is about what you can do with what you have if you have no other choice, and how plentiful resources don't automatically create empowering outcomes.
Everything was about compatibility - that's really why we were stuck with int 21 and almost no other help from the OS to insulate us from the hardware. There wasn't a standard C library with millions of features - or anything else - that could add overhead to hello world.
Every program had its own drivers - everything was optimised for that use case and not some general set of cases.
Zabbix also confuses operators at this point. I recently had to increase a cache. I chose to go from a solid 4MB to a luxurious 256MB.
I know high-performance Java, so just a little jab there, but you don't size JVM parameters like that, except maybe code caches. And before Rust comes in, we also have a Rust application running without good resource control and it wouldn't like those resource constraints.
There is truth to this article.
3/5
Sure, I mean it had a turbo whereas Microsoft only ever had quick things. A shame no one thought of swift back then.
https://github.com/runvnc/tvclaude
That said i never finished that and ended up making another one (using tvchat as a base since it had largely working communication and session management) that acts as a server/daemon inside the container is meant to run in the background and provides a web-based UI instead.
http://runtimeterror.com/pages/iv/images/25b1d4b43bb3467e392...
Of course now it would be a trivial job for an AI to make the chart. Finding a authoritative source for byte counts, probably less so.
Comparing to current-day stuff is kinda like comparing battery-powered bathtub toys to jetskis.
Software in the 80s showed what's possible when you really care about doing it. Software in the last 15 years feels like an exercise on what happens when you don't.
IBM’s 640 KB limit, to be fair.
https://www.xtof.info/the-640k-memory-limit-of-ms-dos.html
If there is any positive progress to be made, the rethinking necessary must go much, much deeper than the superficial flesh of the problem, but there it’s bound to hit upon the sinews and bones of vested interests.
In all, as I’m growing older and see the world trudge along the same lines it did centuries ago, I’m more and more pessimistic about the possibility of people agreeing that the sacrifices necessary will be made.
Short-term stakeholder interests seem to trump any notions of longer-term greater good.
which one is which?
Their comment was entirely on brand.