#borland — Public Fediverse posts

#GitHub's interface if the platform had been created by #Borland in the 90s 😎

[Source: https://xcancel.com/ponceto91/status/2050901293124726900]

#mockup

#GitHub's interface if the platform had been created by #Borland in the 90s 😎

[Source: https://xcancel.com/ponceto91/status/2050901293124726900]

#mockup

#GitHub's interface if the platform had been created by #Borland in the 90s 😎

[Source: https://xcancel.com/ponceto91/status/2050901293124726900]

#mockup

#GitHub's interface if the platform had been created by #Borland in the 90s 😎

[Source: https://xcancel.com/ponceto91/status/2050901293124726900]

#mockup

#GitHub's interface if the platform had been created by #Borland in the 90s 😎

[Source: https://xcancel.com/ponceto91/status/2050901293124726900]

#mockup

Ahhh those were the times...

#borland #turbopascal #tp3 #retrocomputing

For so many years I’ve been wondering but never really knew what happened to Borland and Delphi.

I hated Pascal due to how discouraging our lyceum teacher was and how ancient TP felt in the early 2000s. Plus I learned QBasic at school and then logically moved on to Visual Basic 6.

Though I remember that indeed Delphi was better than VB in many ways, including not needing to provide a runtime.

https://youtu.be/Ubie5xxfdzE?si=lYYWW6imdzDys_ws

#delphi #programming #coding #history #visualbasic #microsoft #borland

I just realized something.. I used to love learning new things, i could get engrossed in something because it was simple to learn and easy to use.

New "tech stack" doesn't seem to be like that anymore. It feels needlessly complex and invents a new 'standard' every time. It makes me angry and I hate learning, cause its no longer fun.

Learning #borland #TurboPascal #pascal was fun and easy in High School. Moving to #C and #Perl in university was great and easy enough as well. Not that I was any kind of competent in C, but I felt I learned enough that it set me up on a trajectory to learn the finer details and gotchas.

Things like #Python are annoying AF. Oh, your python program only works on 3.11 and not 3.12 or 3.13? That shouldn't be at all. From 2->3 sure I expect changes, 3->4, i would expect great changes as well. But not a minor change!

Dabbling in #Go was fine actually, it didn't anger me much, and #Rustlang / #rust I'm still doing rustlings so I can't say much there.

CLI tools are weird today too. Do they want to be a TUI, a true CLI tool or what?

The #Unix philosophy made learning new tools nice and easy, at least I think so. Do one thing, do it well, make it so your output can be used as the input to another program and great!

Things don't seem to follow that idea anymore.

Or am I just old and biased cause my brain lost its elasticity?? I don't want to think i'm so egocentric as to not rule that out.

#programming #OldManYellsAtClouds

IBM 5150 и разработка под самый первый PC

Есть много интересных способов провести новогодние праздники, но поскольку я уже старенький — вместо классических алкогольного угара, ведра оливье и просмотра «Иронии судьбы» выбрал себе более редкое и необычное занятие.

https://habr.com/ru/articles/982954/

#5150 #pcdos #borland #си #эмуляторы #dosbox #pce #freebsd #8080

Modula-2, UCSD P-System, and the birth of Scala

I stumbled across this tidbit from Hacker News.

I never liked that #Borland stuffs. And used to program in #Pascal in #UCSD P-system (my alma mater). When I got to the US Department of Defense they wanted me for my #C and #COBOL skills and then they sent me to an Air Force School where I studied Modula-2 and Ada.

I did a lot of work in Modula-2, which doesn't exist anymore. Modula-3 does, but in the meantime Scala was in the works. #Ada is still actually a thing. We didn't want clever, like those one liner #Perl challenges that folks use to put in their signature lines to demonstrate how clever they thought they were through obfuscation.

Clever is bad. Clever opens up a whole universe of unexpected behavior and potential vulnerabilities. Maybe that's why #Rust became so organically popular - because it's safe by design and nowadays it's included in the Linux kernel more and more.

When you're designing software for missle guidance systems you most certainly do not want clever. The job is simple and ambiguity is potentially catastrophic in warfare.

Anyway, I really enjoyed this interview, I can identify with the #Timex_Sinclair - my dad bought me one and that membrane keyboard was horrendous, but I was persistent and eventually I was writing code in cutting edge languages on mainframes and #Vaxen.

Many of the stories about how one thing or another came about were through frustrations; like the impetus for #Linus the #Linux kernel coz #MINIX just didn't cut it, and who wants to trodge through snow drifts in #Helsinki to the computer lab when you can be warm and cozy, drinking beers in your dorm room?

This story is kinda like that too, which I can really appreciate, even though I've never played with #Scala.

I hope you enjoy it too.

https://www.artima.com/articles/the-origins-of-scala

#tallship #FOSS #Modula_2 #Modula_3

⛵

Modula-2, UCSD P-System, and the birth of Scala

I stumbled across this tidbit from Hacker News.

I never liked that #Borland stuffs. And used to program in #Pascal in #UCSD P-system (my alma mater). When I got to the US Department of Defense they wanted me for my #C and #COBOL skills and then they sent me to an Air Force School where I studied Modula-2 and Ada.

I did a lot of work in Modula-2, which doesn't exist anymore. Modula-3 does, but in the meantime Scala was in the works. #Ada is still actually a thing. We didn't want clever, like those one liner #Perl challenges that folks use to put in their signature lines to demonstrate how clever they thought they were through obfuscation.

Clever is bad. Clever opens up a whole universe of unexpected behavior and potential vulnerabilities. Maybe that's why #Rust became so organically popular - because it's safe by design and nowadays it's included in the Linux kernel more and more.

When you're designing software for missle guidance systems you most certainly do not want clever. The job is simple and ambiguity is potentially catastrophic in warfare.

Anyway, I really enjoyed this interview, I can identify with the #Timex_Sinclair - my dad bought me one and that membrane keyboard was horrendous, but I was persistent and eventually I was writing code in cutting edge languages on mainframes and #Vaxen.

Many of the stories about how one thing or another came about were through frustrations; like the impetus for #Linus the #Linux kernel coz #MINIX just didn't cut it, and who wants to trodge through snow drifts in #Helsinki to the computer lab when you can be warm and cozy, drinking beers in your dorm room?

This story is kinda like that too, which I can really appreciate, even though I've never played with #Scala.

I hope you enjoy it too.

https://www.artima.com/articles/the-origins-of-scala

#tallship #FOSS #Modula_2 #Modula_3

⛵

Modula-2, UCSD P-System, and the birth of Scala

I stumbled across this tidbit from Hacker News.

I never liked that #Borland stuffs. And used to program in #Pascal in #UCSD P-system (my alma mater). When I got to the US Department of Defense they wanted me for my #C and #COBOL skills and then they sent me to an Air Force School where I studied Modula-2 and Ada.

I did a lot of work in Modula-2, which doesn't exist anymore. Modula-3 does, but in the meantime Scala was in the works. #Ada is still actually a thing. We didn't want clever, like those one liner #Perl challenges that folks use to put in their signature lines to demonstrate how clever they thought they were through obfuscation.

Clever is bad. Clever opens up a whole universe of unexpected behavior and potential vulnerabilities. Maybe that's why #Rust became so organically popular - because it's safe by design and nowadays it's included in the Linux kernel more and more.

When you're designing software for missle guidance systems you most certainly do not want clever. The job is simple and ambiguity is potentially catastrophic in warfare.

Anyway, I really enjoyed this interview, I can identify with the #Timex_Sinclair - my dad bought me one and that membrane keyboard was horrendous, but I was persistent and eventually I was writing code in cutting edge languages on mainframes and #Vaxen.

Many of the stories about how one thing or another came about were through frustrations; like the impetus for #Linus the #Linux kernel coz #MINIX just didn't cut it, and who wants to trodge through snow drifts in #Helsinki to the computer lab when you can be warm and cozy, drinking beers in your dorm room?

This story is kinda like that too, which I can really appreciate, even though I've never played with #Scala.

I hope you enjoy it too.

https://www.artima.com/articles/the-origins-of-scala

#tallship #FOSS #Modula_2 #Modula_3

⛵

Episódio 160 – Integrados e Suítes – Parte B

https://retropolis.com.br/2025/02/12/episodio-160-parte-b/

#Podcast #aplicaes #atari #AtariWorks #Borland #BorlandOffice #CorelOffice #DeskMate #epson #HAL #Halnote #integrado #LibreOffice #Lotus #LotusSmartsuite #Micropro #microsoft #MSX #Novell #office #OpenOffice #PerfectOffice #podcast #QX10 #Retrocomputao #retrogaming #Retrpolis #Software #Starburst #StarOffice #suite #Valdocs #WordPerfectOffice #WordStar

Episódio 160 – Integrados e Suítes – Parte B

https://retropolis.com.br/2025/02/12/episodio-160-parte-b/

#Podcast #aplicaes #atari #AtariWorks #Borland #BorlandOffice #CorelOffice #DeskMate #epson #HAL #Halnote #integrado #LibreOffice #Lotus #LotusSmartsuite #Micropro #microsoft #MSX #Novell #office #OpenOffice #PerfectOffice #podcast #QX10 #Retrocomputao #retrogaming #Retrpolis #Software #Starburst #StarOffice #suite #Valdocs #WordPerfectOffice #WordStar

Episódio 160 – Integrados e Suítes – Parte B

https://retropolis.com.br/2025/02/12/episodio-160-parte-b/

#Podcast #aplicaes #atari #AtariWorks #Borland #BorlandOffice #CorelOffice #DeskMate #epson #HAL #Halnote #integrado #LibreOffice #Lotus #LotusSmartsuite #Micropro #microsoft #MSX #Novell #office #OpenOffice #PerfectOffice #podcast #QX10 #Retrocomputao #retrogaming #Retrpolis #Software #Starburst #StarOffice #suite #Valdocs #WordPerfectOffice #WordStar

Episódio 160 – Integrados e Suítes – Parte B

https://retropolis.com.br/2025/02/12/episodio-160-parte-b/

#Podcast #aplicaes #atari #AtariWorks #Borland #BorlandOffice #CorelOffice #DeskMate #epson #HAL #Halnote #integrado #LibreOffice #Lotus #LotusSmartsuite #Micropro #microsoft #MSX #Novell #office #OpenOffice #PerfectOffice #podcast #QX10 #Retrocomputao #retrogaming #Retrpolis #Software #Starburst #StarOffice #suite #Valdocs #WordPerfectOffice #WordStar

Episódio 160 – Integrados e Suítes – Parte B

https://retropolis.com.br/2025/02/12/episodio-160-parte-b/

#Podcast #aplicaes #atari #AtariWorks #Borland #BorlandOffice #CorelOffice #DeskMate #epson #HAL #Halnote #integrado #LibreOffice #Lotus #LotusSmartsuite #Micropro #microsoft #MSX #Novell #office #OpenOffice #PerfectOffice #podcast #QX10 #Retrocomputao #retrogaming #Retrpolis #Software #Starburst #StarOffice #suite #Valdocs #WordPerfectOffice #WordStar

Spending some of my #christmas #vacation #geeking around with #vintagecomputing and getting reacquainted with developing software for #msdos. Last time I did that must have been in the early #90s before I discovered #Linux.

So far I've given the #djgpp C compiler a go, but it seems a little messy and keep throwing internal errors. #OpenWatcom v2 seems promising, but has a horrible way of doing interrupt calls. The #borland suites seems outdated, but does come with a lot of libraries that the others don't have. I don't believe it can generate protected mode executables though.

Im actually only looking to do a couple of simple tools, and perhaps some sort of menu/launcher that can scan recursively for configuration files. For the ladder, word around the campfire is that #pdcurses is pretty good at drawing menus and other components in text mode. I'll investigate! Would be a new experience NOT starting by writing my own library for addressing the text mode screen directly.. AGAIN.. 😜

Here's something I wish would be open sourced.

The #TopSpeed C #compiler is an integral part of the #Psion SIBO C SDK.

Old timers might remember JPI as a group of developers who left #Borland in 1987, after Borland decided not to use the team's new compiler technology. They took their code with them, and it became the TopSpeed compiler.

From what I gather, the TopSpeed compiler IP is now owned by #SoftVelocity, the company who now also owns Clarion. I emailed them about 6 years ago, asking them if they would consider open sourcing the compiler code. I got no response, which I guess is to be expected.

I even found someone who had a copy of the source code (written in Modula-2), but they understandably wouldn't give it to me without the IP owner's approval.

This is the situation with so many bits of software (including the SIBO C SDK tools) from this time. We are lucky that copies of the applications still exist, otherwise the job of building C software for #EPOC16 would be significantly more difficult. But it is likely that the original source code, along with many other codebases, will disappear thanks to copyright laws that don't support digital preservation.

#retrocomputing #vintagecomputing #digipres

Has anyone got any tips on converting #TASM and #MASM code to a more modern assembler like #NASM? Even just between TASM and MASM would be helpful.

I've got a few old bits of #Psion 8086 assembly that I'd like to use with NASM. My aim is to remove as many proprietary tools as possible.

I guess I'm looking for some sort of Rosetta stone for 8086 Small Memory Model assembly.

Books, web pages and video suggestions welcome.

#x86 #Borland #RetroComputing

Just tried compiling Wari, a game written in #Psion OO C. The project uses #Borland Make 3.6.

Got it to compile first time with my SIBO SDK setup - all good!

However... Borland Make uses 16-bit DPMI, and its extender won't load 32-bit DPMI binaries. If I pre-load the 32-bit extender, it won't load 16-bit DPMI binaries, so Make won't run!

TL;DR: I can't use the new #ctran with Borland Make 3.6.

Looks like I'll be converting that Makefile to GNU Make or a #TopSpeed project.

#dos #dosbox

Repórter Retro 100

https://retropolis.com.br/2024/02/28/reporter-retro-100/

#ReprterRetro #1541 #1571 #AdrianBlack #AmstradCpc #Bendix #Borland #Calculadora #Centurion #Colossus #Comercial #Commodore128 #CPM #crime #Demo #Doom #DouglasEngelbart #Laptop #Macintosh #MSX #MSXVDP #NoelLlopis #Plasma #Robs #Samsung #SayakasDigitalAttic #SBC #SDMapper #SinclairQl #TByteCreator #TCPIP #Terminal #TheTaylorAndAmyShow #TurboPascal #UsagiElectric #vlvulas #Windows30 #ZilogZ80

Further little test, getting #TopSpeed to launch #Borland MAKE to launch #MASM.

Run TSC, and it complains properly about not having enough memory.

Run TSCX, and it locks up.

So, my uneducated guess is... Apps are using up all of the conventional RAM, and #DOSBox is letting them. Whereas "real" DOS doesn't let it allocate the RAM in the first place, killing the process before it starts.

#RetroComputing

Trying to compile Vector in #DOSBox, and something odd is happening.

If #Borland MAKE runs #MASM (specifically ML.EXE), a zero-sized .OBJ file is created and everything freezes. Run the same MASM command directly, and it works fine.

Tried it in regular DOSBox, Staging, and DOSBox-X - all the same. Dosemu fell over repeatedly, and I'm having issues compiling Dosemu2 on Arch. I could try it with MS DOS or FreeDOS in a VM.

#RetroComputing #DOS

Reading through the first manual in the SDK has reminded me what the "pure small memory model" is.

The ES register is never corrupted (DS=ES=SS).

#TopSpeed C implemented this, which was one of the main reasons why #Psion used it for the SDK.

I've heard that it's possible to implement this with #Borland C (and maybe #Watcom?), but I don't know how.

#16bit #retrocomputing #epoc16 #x86

I made significant progress in porting Ranish Partition Manager from #Borland #C and #TASM to #Watcom C and #NASM.

All the C files and about half the assembler files are translated. The Watcom built executable is running and a few quick tests revealed no unexpected behaviour. Thoroughly testing has still to be done after the remaining files are translated.

https://codeberg.org/boeckmann/ranish

Implementation defined behaviour in #C: Folgendes packt #Borland C einen char, #Watcom in einen int:

unsigned start_sect:6;
unsigned start_cylH:2;

Daher Struktur unter Borland 16 bytes und unter Watcom 18 🤡

Es muss leider ein char sein. Watcom erlaubt folgendes, um es gerade zu biegen:

unsigned char start_sect:6;
unsigned char start_cylH:2;

Nicht erlaubt laut Standard: "A bit-field shall have a type that is a qualified or unqualified version of one of int, unsigned int, or signed int."