It's a neat project. Write cross platform desktop apps in C. Presumably it would not have been very usable in practice in the late 1980s, because of all the OTHER system interfaces that still weren't portable, even if the windowing system was available in a portable way.
I can remember the subsequent period in which Java desktop apps were relatively common. They had cross platform UI by default. But the problem was:
1) cross platform GUIs are ugly by default, compared to fully native desktop apps, because they don't entirely replicate the affordances or the style of the platform;
2) in the Java case, it seemed heavyweight to install and sluggish compared to native apps;
Point 2 would not have applied to stdwin, as it would have produced small compiled binaries I suppose, but Point 1 would have.
So in the end, obviously web apps (and partly, Flash) took over the niche that "cross platform desktop apps" had once tried to fill, and then it was something of a dead zone until Electron, as far as I remember.
> cross platform GUIs are ugly by default, compared to fully native desktop apps, because they don't entirely replicate the affordances or the style of the platform;
I think this is an implementation detail. It's up to the software stack whether it leaves off before drawing the UI elements on screen, or goes ahead and takes on that responsibility too. The wxWidgets toolkit uses the runtime platform's UI, so it does not draw the widgets themselves. Java Swing took on the task of drawing the UI elements on the screen in its own style.
When OS X was new, Apple was still under the assumption that Java on the desktop was important, and they built an in-house Java with full Aqua support. It was still _terrible_! All the Aqua-specific affordances like animation or shadows were janky or absent. Sizing and positioning always felt weird because the application was written assuming Windows-shaped controls.
Basically, cross-platform GUI only looks good on the platform that it was originally designed for. Unless the other platforms make zero interesting choices, they will always look worse.
Honestly, "native UI" gets so much worse with every passing year that I don't even want native UI. I want old windows UI.
I saw a screenshot of GTK 1 and the first thing I thought is that I'd rather make something using GTK 1 than GTK 3. Unfortunately I asked an AI chatbot about it and they advised against it because of "security" :(
> As a ~20 year old this feels so weird to read. I'm still considered young in ~10 years?
One of these days, maybe as early as your mid-/late-40s, you will be consulting with your a medical doctor and realize that you are the oldest person in the room.
> As a ~20 year old this feels so weird to read. I'm still considered young in ~10 years?
An anecdote for you...
In Summer 1997 i was 24 at a family reunion, listening to my grandmother and several other seniors talk about some recent interaction my grandmother had had with a delivery person. One of her friends asked her, "how old was he?"
i'll never forget either her response or my jaw-dropping which followed:
I just turned 65. Own 1 person custom software development company and am very much active professionally. Started programming in the 80s while working as a research scientist.
It's all relative. When I was 20, I'd consider myself old at 36. Now when I am 36, my definition of old has shifted and it's now somewhere past 50. I guess "old" for a person is just that person 10+ years older :)
Careers could be very very long. My relative was kicked out of academia after finishing his postdoc and has to work manual jobs till the end of comunism in my country. His career actually started after 60 and he died just a few weeks before his announced retirement at the age of 96, teaching 5 to 6 classes a year in CS department.
It's a neat project. Write cross platform desktop apps in C. Presumably it would not have been very usable in practice in the late 1980s, because of all the OTHER system interfaces that still weren't portable, even if the windowing system was available in a portable way.
I can remember the subsequent period in which Java desktop apps were relatively common. They had cross platform UI by default. But the problem was:
1) cross platform GUIs are ugly by default, compared to fully native desktop apps, because they don't entirely replicate the affordances or the style of the platform;
2) in the Java case, it seemed heavyweight to install and sluggish compared to native apps;
Point 2 would not have applied to stdwin, as it would have produced small compiled binaries I suppose, but Point 1 would have.
So in the end, obviously web apps (and partly, Flash) took over the niche that "cross platform desktop apps" had once tried to fill, and then it was something of a dead zone until Electron, as far as I remember.
Point 2 nowadays feels like high performance when compared to Electron crap.
> cross platform GUIs are ugly by default, compared to fully native desktop apps, because they don't entirely replicate the affordances or the style of the platform;
I think this is an implementation detail. It's up to the software stack whether it leaves off before drawing the UI elements on screen, or goes ahead and takes on that responsibility too. The wxWidgets toolkit uses the runtime platform's UI, so it does not draw the widgets themselves. Java Swing took on the task of drawing the UI elements on the screen in its own style.
When OS X was new, Apple was still under the assumption that Java on the desktop was important, and they built an in-house Java with full Aqua support. It was still _terrible_! All the Aqua-specific affordances like animation or shadows were janky or absent. Sizing and positioning always felt weird because the application was written assuming Windows-shaped controls.
Basically, cross-platform GUI only looks good on the platform that it was originally designed for. Unless the other platforms make zero interesting choices, they will always look worse.
The other popular option for cross-platform UI apps was Tcl/Tk:
https://en.wikipedia.org/wiki/Tk_(software)
...which even leaked into other language ecosystems like Python:
https://docs.python.org/3/library/tkinter.html
Which had the ugliness problem then, although it is a lot better now.
Honestly, "native UI" gets so much worse with every passing year that I don't even want native UI. I want old windows UI.
I saw a screenshot of GTK 1 and the first thing I thought is that I'd rather make something using GTK 1 than GTK 3. Unfortunately I asked an AI chatbot about it and they advised against it because of "security" :(
This should be linked as the original post: https://ir.cwi.nl/pub/5998
It says 1988 there.
Still seems like it could be useful
the code from 1995
https://github.com/thomas-hori/mirror-cwi-stdwin
I find it amusing that the paper doesn't include any screenshots. Those were the days!
How old is this? 1989 or something like that? Guido was probably quite young when he wrote it. Looks like LaTeX?
Edit: Someone else wrote 1988 which I suppose makes sense, as the latest reference at the end is from 1988 too. So then Guido was 32 years old.
> quite young
> 32 years old
As a ~20 year old this feels so weird to read. I'm still considered young in ~10 years?
> As a ~20 year old this feels so weird to read. I'm still considered young in ~10 years?
One of these days, maybe as early as your mid-/late-40s, you will be consulting with your a medical doctor and realize that you are the oldest person in the room.
> As a ~20 year old this feels so weird to read. I'm still considered young in ~10 years?
An anecdote for you...
In Summer 1997 i was 24 at a family reunion, listening to my grandmother and several other seniors talk about some recent interaction my grandmother had had with a delivery person. One of her friends asked her, "how old was he?"
i'll never forget either her response or my jaw-dropping which followed:
"Oh, he was a _young_ man. About 50, I guess."
(Yes, she actually stressed the word _young_.)
I’m nearly 64.
Back when I was a teenager, people in their 20s were “old farts.”
Nowadays, I look at people in their 40s, as “kids.”
Here’s my first ever engineering project (1987): https://littlegreenviper.com/wp-content/uploads/2022/07/TF30...
I was 25, at the time, and a fairly newly-minted EE.
Brother in arms ;)
I just turned 65. Own 1 person custom software development company and am very much active professionally. Started programming in the 80s while working as a research scientist.
It's all relative. When I was 20, I'd consider myself old at 36. Now when I am 36, my definition of old has shifted and it's now somewhere past 50. I guess "old" for a person is just that person 10+ years older :)
> As a ~20 year old this feels so weird to read. I'm still considered young in ~10 years?
You'll still feel young too! It's really weird when you get to your mid 30's and realise that all the 20-somethings view you as old
And later too! I'm 51 but mentally I still feel like 50.
Consider that careers run from 20 to 70 or so.
Careers could be very very long. My relative was kicked out of academia after finishing his postdoc and has to work manual jobs till the end of comunism in my country. His career actually started after 60 and he died just a few weeks before his announced retirement at the age of 96, teaching 5 to 6 classes a year in CS department.
You'll always be young according to yourself.
Yes
Young is relative. To an 80 year old someone who is 40 is young. To an 8 year old someone who is 20 is old.
I would say roff, not LaTeX
(1988)