Live data from Hacker News

Building a new Windows 3.1 app in 2019: A Slack Client

yeokhengmeng.com

141–150 of 248 posts

Re: Building a new Windows 3.1 app in 2019: A Slack Client

#141
post #45

Earlier quoted context omitted.

> More seriously, this is an excellent proof-of-concept that a Slack client does not need to use hundreds of MB of RAM and consume most of a modern CPU core to provide its basic functionality. If you’re so sure that this is possible, then where is the Electron competitor which allows us to build cross platform applications like this, with the same levels of productivity and a consistent and decent user interface? No…

There is Delphi and Lazarus as open-source clone of it Lazarus can use the Windows API on Windows, gtk/qt on Linux, and carbon/cocoa on Mac. There is also a custom drawn mode that draws the GUI directly rather than using platform apis. That also runs on Android, but it not maintained anymore, so only up to Android 5 or something Delphi is supposed to run on Android and iOS. And Delphi 1 ran on Windows 3.1, so you cou…

There is Delphi and Lazarus as open-source clone of it

Shhh! Ixnay on the Lazarusay. If people find out, I'll lose my magical secret weapon for blasting out little windows gui apps.

Seriously though, if you ever find yourself needing a few buttons on a windows desktop that do simple things, Lazarus is amazing for whipping that up in a few minutes and still looking professional.

Re: Building a new Windows 3.1 app in 2019: A Slack Client

#142
post #2

I built a Win 3.1 app during a company hackathon just for fun. Here, I detail learnings and process for how a new old app can be created with the aid of modern tools and hindsight of old technologies. And perhaps what lessons can it offer us today. Without the benefit of modern libraries and languages, I had to read up and take care of many low level details, socket programming, HTTP, JSON parsing, UI design in code…

We use Visual Basic 6 for a lot more than we should at work...going back to that from using Python, Ruby, and even PHP was a shok.

I thought porting a Python script to VB wouldn't be a big deal, but like you said, things youtake for granted like JSON and certain dictionaries are just lacking.

Re: Building a new Windows 3.1 app in 2019: A Slack Client

#143

Earlier quoted context omitted.

I've been programming since 1983. The internet opened up publishing to the masses, which means that non-professional people could also publish, resulting in much more documentation than ever before. But now the amateur documentation writers are competing with the professional ones; the quality of the professional documentation is still as high as ever, but it can be drowned out by the amateur quality documentation. A…

The quality of Microsoft's own documentation has also fallen considerably; the latest nail in the coffin is that docs.microsoft.com thing that started to replace MSDN several years ago, that created tons of ridiculous fuckups in the "migration process". While doing that they also "open sourced" their documentation on GitHub, which to me sounds more like they're just trying to rely on free labour from the "community"…

MSDN was a gold standard in the 90's. Now you have tragedies like social.technet.com

Re: Building a new Windows 3.1 app in 2019: A Slack Client

#144

Windows 3.1 and 16 bit would be a little too painful for me. Windows 95 was quite nice with 32 bit and preemptive multitasking though. I kind of miss this or Windows 2000.

If I had a month to do whatever I wanted, I've always wanted to 'go back in time' and try to write a Doom level editor for W 3.1

Re: Building a new Windows 3.1 app in 2019: A Slack Client

#145

Earlier quoted context omitted.

What are your criteria for something being an Electron competitor?

It was more or less a rethorical question (I guess that’s why I’m being downvoted), because there is no competitor. If there was, then Electron wouldn’t be so extremely popular in the first place, and we’d see a lot more popular apps made with all the tools mentioned in the other replies to my post.

You do realize that one thing can be more popular but still have competition, right?

Re: Building a new Windows 3.1 app in 2019: A Slack Client

#147
post #145

Earlier quoted context omitted.

It was more or less a rethorical question (I guess that’s why I’m being downvoted), because there is no competitor. If there was, then Electron wouldn’t be so extremely popular in the first place, and we’d see a lot more popular apps made with all the tools mentioned in the other replies to my post.

You do realize that one thing can be more popular but still have competition, right?

Sure, I’m just saying there is a huge gap and other tools, even though they technically work, haven’t proven to be good enough to become as widely adopted as Electron.

Re: Building a new Windows 3.1 app in 2019: A Slack Client

#148

Earlier quoted context omitted.

It was more or less a rethorical question (I guess that’s why I’m being downvoted), because there is no competitor. If there was, then Electron wouldn’t be so extremely popular in the first place, and we’d see a lot more popular apps made with all the tools mentioned in the other replies to my post.

You are being downvoted because the idea that electron is the only way to get cross platform GUIs is absurd and comes from inexperience and a lack of research. FLTK, Juce and Qt are just some of the options for creating cross platform UIs that end up being much smaller and MUCH faster than electron. Electron is popular because people learn javascript and don't want to learn C++. I can't completely fault this mentalit…

> toy programs

> false sweeping statements

OK.

Re: Building a new Windows 3.1 app in 2019: A Slack Client

#149
post #140

Earlier quoted context omitted.

It's kind of silly compare a bare bones get/post to an entire app. This reminds me of my attempts to write an IRC client in an evening. Creating a native Windows app to mimic the Electron Slack client would not be a trivial task.

His point is that this bare bones get/post app in Electron will be much, much "larger".

And that is why it would foolish for them to post a barebones slack client in electron. But they don't publish that. They have published a full featured client that is cross platform. I am not a fan of electron and would very much prefer a desktop app. But we are finally seeing emergence of desktop applications from major players for Linux because of electron. It's not ideal but so wasn't the previous solution.

Re: Building a new Windows 3.1 app in 2019: A Slack Client

#150
post #146

This is amazing, very well done. I think every programmer should from time to time build something for a very old platform and appreciate the progress achieved so far.

By which you mean that they'll recognize everything that's been stolen from the users, right? Win 3.1 & DOS was probably about the last time I really felt in control of my PC.
Post reply on HN