News for hackers. Stuff that matters.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by alexb_ on Friday May 27, 2022 @05:06AM (#31527505)
Was going to edit this in but it quickly turned into a related rant about the state of things: if you don't want that, scroll past.

The real problem is that there's no more room for the technological "middle class". We've gotten to the point where you cannot be SLIGHTLY interested in computers, want to make a quick app for yourself, or make something small to share with the world. You either have to have no interest at all (and live in blissful ignorance) or be so into this type of stuff that you might as well just make it a career. In between these two extremes lies a valley of frustration and needless complexity, where everything is always breaking and changing because we found out what was used 2 years ago is actually bad but THIS TIME IS DIFFERENT! because now we found a solution that is totally going to work forever this time. It's exhausting to even think about.

Many people got their start programming with something like messing with simple Visual Basic stuff. I, and I'm sure many others who are reading this, started with a TI-83 and a desire to cheat on my math quiz. I know that I'm going a little off the rails here, and this has become more of a rant than anything meaningful, but I really, really hate how there's quickly becoming no space for that sort of thing - nowhere for people formerly uninterested in technology and programming to get their feet wet, nowhere to make a quick application to accomplish a small task, etc..

Re:Today’s JavaScript, from an outsider’s perspective (2020) by jerf on Friday May 27, 2022 @09:32AM (#31529426)
I've been programming on the web since 1997. All the techniques developed since then still work. I still have a couple of "web 2.0" websites I've developed running at work... because while I nominally have all the language skills, I only dip my toes into the chaotic world of "the latest JS best practices" a few times over the years and have not been able to justify the effort of keeping up when it is changing at a higher frequency than I have needs. If someone drops me into a functioning project I can adapt quickly, but starting from scratch has become virtually impossible in any reasonable period of time anymore.

This really only hurts with UI stuff. Other JS I can write just fine; pure Javascript in the browser has gotten pretty powerful, it all but has jQuery built in now, you've got XPath, a templating language (simplistic, and needs a bit of XSS care, but adequate for small needs) and a lot of other useful things all just sitting there, but if you want a big widget setup there's a huge learning curve to get there, even for an expert programmer.

For the novice, "classic web" would still be a very powerful thing to learn that isn't too hard, but it's hard to find those references now underneath the pile of not quite functional tutorials, broken install instructions, entirely different languages creeping in (Typescript), etc. It's a total disaster for someone trying to learn this way.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by aahortwwy on Friday May 27, 2022 @05:44AM (#31527693)
This just isn't true, though.

I have quite a few non-technical colleagues who know just enough Python to Get Shit Done.

My father (a writer) taught himself R for research purposes and is productive with it.

Universal Paperclips has a super-basic JavaScript codebase[0] but was a really popular game.

Thing is, if you search "how to do X in Python" you're going to get a bunch of resources aimed at professionals because they're the ones looking for that stuff most of the time. That doesn't mean the resources are prohibitively complex, they're just for people solving a different problem.

[0] https://github.com/jgmize/paperclips/tree/master/docs

Re:Today’s JavaScript, from an outsider’s perspective (2020) by wly_cdgr on Friday May 27, 2022 @12:00PM (#31531156)
Oooooh did you just call Frank Lantz super-basic kek
Re:Today’s JavaScript, from an outsider’s perspective (2020) by aahortwwy on Friday May 27, 2022 @07:46PM (#31536229)
I think he's a good contrast to the "great computer scientist, but not a JS person" in the linked article.

He initially built Universal Paperclips to learn JavaScript. It's a cool thing, a lot of people played it, and it doesn't rely on an incomprehensible ecosystem. It's two HTML files, four scripts, two CSS files, and an image.

You don't _need_ all the stuff people complain about to do cool things with JavaScript. Especially if you're just getting started with the language.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by wly_cdgr on Friday May 27, 2022 @08:02PM (#31536330)
I agree. You just need to actually be a good designer :) When you have a fun and clear vision for what you want to build, it's hugely motivating and you're way more likely to finish
Re:Today’s JavaScript, from an outsider’s perspective (2020) by wrp on Friday May 27, 2022 @07:13AM (#31528208)
But are they building software tools that are useful and stable enough to distribute? That's the level of capability he is talking about.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by aahortwwy on Friday May 27, 2022 @07:31AM (#31528317)
That's not what the linked Twitter thread is talking about, nor is it how I interpret "make a quick app for yourself, or make something small to share with the world" or "make a quick application to accomplish a small task." Those things are eminently achievable without having to embrace the level of complexity that's so popular in professional software development.

And I actually think the level of capability you're talking about is within closer reach than most people realize. Certainly it's much easier now than it was even 10 years ago. Probably not something that a non-programmer can accomplish on day 1, but I'm not sure there's many crafts that can be learned that quickly.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by wrp on Friday May 27, 2022 @07:51AM (#31528452)
By "distribute," I didn't mean as a commercial product. I meant just sharing with other people. There is a huge difference between being able to tinker with Python/R and being able to make a package usable by strangers.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by prionassembly on Friday May 27, 2022 @09:53AM (#31529654)
The onramp from

- script without a main function

- to personal or ad hoc codebase for non-tech workplace

- to packaged code to cope with namespaces + type hints + general best practices

- to code that reads like good code from the major open source project

is long, but the slope is easy. There are no discontinuities. Basically anyone who can use Python to glue together networkx/sklearn etc. can eventually write software tools that are useful and stable enough to distribute.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by moochmooch on Friday May 27, 2022 @11:12AM (#31530520)
That should not be the litmus test for writing software. Lots of software can have 1 user, yourself. Stability and ability to distribute be damned
Re:Today’s JavaScript, from an outsider’s perspective (2020) by BlargMcLarg on Friday May 27, 2022 @05:45AM (#31527701)
If we have a middle class in tech, we also have the "temporarily embarrassed millionaires" pretending to be the top claiming everyone below them isn't good enough for something as simple as creating a few endpoints and vibechecking rather than checking skills.

And this extends all the way to the job market, where you now need 3 years of experience for a skill most people know how to use in about a week tops, and only lack the exposure of that skill used in a corporate setting. Where people will parrot "you need 3 months to not be a liability! (or more)" when those individuals will easily earn themselves back in the same timeframe. For projects where all you really do is create endpoints, process the most basic of information and expose it in certain ways. For reference, most people in STEM majors need to learn more difficult stuff in a shorter timeframe, with less help.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by Tade0 on Friday May 27, 2022 @06:50AM (#31528057)
I had an interesting conversation the other day with our delivery manager and two other developers from another team, who had a wildly different than me assessment of a recent candidate.

Their argument was that he didn't know this and that and how is it that I deemed him worthy?

I interjected by saying that during these 30min I get to ask questions I don't have nearly the time to check one's skills throughly. And the same is true for them.

The most I can achieve in this timeframe is check whether the person won't be actively harmful to the project by e.g. being a charlatan or just malicious.

This was news to the delivery manager and they didn't approve of that.

I refrained from replying that our rates vs the market don't really put us in a position to be picky.

But I did tell them that I worked with "net negative" people(with examples) and it's really not about the skills at the moment of hiring.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by BlargMcLarg on Friday May 27, 2022 @06:59AM (#31528110)
I'd like to see more of this.

It astounds me that software dev, historically seen as a field with and for "poor communicators", somehow believes its interviewers can do what top psychologists consider almost impossible to do. Same happens across almost every industry, but really, tech? "Cold hard logic" tech somehow became "yeah we can totally psychoanalyze someone in 30 minutes by talking"?

Worse, the lack of structure across the entirety makes it more of a lottery and a guessing game which is more or less sold as one's personal (in)capabilities. It's far more harmful than people make it out to be.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by chiefalchemist on Friday May 27, 2022 @07:30AM (#31528310)
Or perhaps the interviewers are under-experienced, under-perpared and/or under-trained?

True story: I had an interview a couple of weeks ago. I was interviewed by two people who were younger than me, and relatively less experienced than me.

My CV has a number of links to repos for various side projects and such. Best I could tell, neither of them looked, at least not more than a minute. Not a single "Your ____ repo looks ____ let's discuss a bit..." Instead I got ovetly basic questions, some of which didn't map to the role / opportunity.

Furthermore, I could only find one of them on GitHub and it was routine stuff (e.g., wedding website). Apparently, neither understood I was interviewing them as well.

I'll never get that hour of my life back.

I have a phrase:

"How you hire is who you hire."

It's sadly funny how many outfits still don't get that.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by BlargMcLarg on Friday May 27, 2022 @07:53AM (#31528467)
My theory: most hiring absolutely doesn't matter (from the interviewer's side).

Most people will either have the skills needed or the capability to learn said skills. Weeding out obvious poor cases is easy, the remainder is semi-arbitrary weeding out of true positives in hopes of weeding potential false positives. Much of higher education alone does a good job at pushing people to learn difficult things in a short timeframe, with little incentive beyond "getting that paper".

Also, hiring is a lot like parenting, but the bad aspects magnified at least a few times. As you say, barely anyone knows what to do. No one has experience. Almost everyone claims to be an expert (not verbally, but they do act like it). Non-obvious bad choices often go undiscovered; as above, most picks themselves aren't bad (they just aren't great), or something else is blamed instead. Pride, neuroticism and personal bias play huge parts in the decisions.

Worst of all, no one actually reads the studies showcasing most of what hiring managers do have close to zero correlation to anything. I'm really just waiting for a mass study where two companies do an initial vetting, then company A throws darts at a dartboard and company B does the whole job interview shtick, and compare the results 2 years down the line. And maybe add a company C which actually does what studies suggest.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by chiefalchemist on Friday May 27, 2022 @09:58AM (#31529717)
Agreed. But now we're back to:

"How you hire is who you hire."

And I have a new one...

"You're not only the interviewer, you're an interviewee as well."

Understanding these two basic are essential to a decent hiring process. Ignore these and you're just another fool in a sea of fools.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by corrral on Friday May 27, 2022 @10:43AM (#31530233)
> Best I could tell, neither of them looked, at least not more than a minute.

I once interviewed a guy with a nice, short 1-pager résumé—not from lack of experience, just a solid, terse document. Not just out of school. Had three or four tech jobs in his history.

He listed one research paper near the bottom, that he'd co-authored in grad school.

I found the paper, skimmed it, and asked him about it in the interview (a lot of times in interviews I just ask candidates about stuff that it seems like they'd know about, that I don't know about, to satisfy my curiosity—I have no idea whether this is good or bad interviewing technique, but my intuition is having someone teach you about something you don't know, that they do, is probably at least as good as asking them to tell you stuff you already know) and he told me I was the only interviewer who'd ever brought it up at all.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by scruple on Friday May 27, 2022 @12:51PM (#31531780)
My resume is quite similar. On the bottom, I have a link to something that I'm quite proud of under a small heading titled, "Ask me about it!" I've been interviewing passively / casually for the last 18 months. I've spoke to a couple dozen different organizations in that time. I've had exactly 1 person ask me about it. I've thought about removing it from my resume with the thought that maybe people are just put off by it.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by chiefalchemist on Friday May 27, 2022 @08:40PM (#31536528)
Put off? Or lazy? At the end of the day the relationship comes down to "fit". Time and signals are very limited. A bad decision by either party is costly in a number of ways. You threw them a softball and they...couldn't be bothered?

Moi? I'd leave it. Them not looking tells as much as if they do.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by chiefalchemist on Friday May 27, 2022 @04:11PM (#31534319)
I think it's a good approach. My position is: we're considering a possible long term relationship. We both have an interest in this meeting. That is, I hold as many cards as you do.

Those that see it otherwise? That to me a culture red flag. It's an easy swipe left.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by Tade0 on Friday May 27, 2022 @07:25AM (#31528282)
I've found that unfortunately it's most often people at the peak of the Dunning-Kruger effect who volunteer to do interviews, so hiring decisions are ultimately made in part by those who vastly overestimate the scale of insight they can get from those relatively short conversations.

I had people get visibly angry during interviews where I was the candidate when I called them out on giving me a problem to solve, that they obviously had in their project and spent weeks on figuring out, while I was somehow supposed to do that in less than an hour.

Oddly specific interview questions are a red flag to me, because they indicate someone had a strong opinion on what's the "proper" way to solve a given problem.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by scruple on Friday May 27, 2022 @12:41PM (#31531619)
I've gone through this before. The end result was that I was quite literally dis-invited from interviewing candidates. I left that place shortly thereafter.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by jquery_dev on Friday May 27, 2022 @05:49AM (#31527719)
I've started programming around 10 year ago without any Visual Basic code. There are so many more resources nowadays to get started programming, back in the day there was no way in hell you'd get something like repl.it where you don't even need to install anything.

What stops you from creating the most simple html page and playing with CSS? That counts as programming to me, there's also scratch for people who are completely new and want to learn.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by ratww on Friday May 27, 2022 @07:59AM (#31528507)
A big issue is that 10 or 20 years ago the steps for creating a webpage were simple: just open notepad (or whatever) and put some HTML.

Today you "gotta" install node, yarn, webpack, react. Then you gotta make a package.json and configure webpack. Or replace webpack with something called "crap". At least that's what all the "for beginners" tutorials that everyone recommends says! Nobody ever said I could just use notepad!!!

But that's not exclusive for frontend.

20 years ago you'd get a random server with Perl. Probably free. 10 years ago you'd get a random server with PHP. You would use FTP and notepad to learn the ropes.

Today you must install some advanced editing software with some plugins, use a terminal, install some runtime or compiler, get some packages, which won't work, so Google tells you to use "sudo" so it works, but that's very suspicious. Stack Overflow says shouldn't be "sudoing" by the way, this is dangerous, you should actually install this "version manager" thing here to install the first tool you installed, so maybe uninstall the first tool, although there's no uninstaller. Oh, and you need this "package manager" tool that install the version manager in the first place. Then you gotta learn to deploy. At this point you're already too old for this shit.

Desktop apps? Good luck with that.

OF COURSE there are simpler solutions, like just making a website with HTML as you could before, or Jupiter Notebooks. But few people today will stumble on that by accident.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by satao on Friday May 27, 2022 @08:29AM (#31528784)
You can still do a webpage just like you did 20 years ago, inserting a couple HTML tags in a notepad.

Now the scope of what a webpage is capable of is infinitaly larger, and so is the complexity required for using all the new possibilities. If you want to use advanced stuff without learning the basics, than of course you're going to have a bad time.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by corrral on Friday May 27, 2022 @10:58AM (#31530394)
3rd party JS code used to be snippets you were expected to copy-paste into your own code, or whole files you were expected to save and then load with a <script> tag before your own code.

Now there are like 50 ways to import JS code, most of them don't work most places, a lot of the code itself won't work in a browser at all (node-only), and a great deal of it is a pain to get into a browser if you're not fully bought into Node and probably also serving the whole "app" from Node.

It's about as easy to write your own JS in a browser, now, but it's vastly harder to start using code from the overall JS ecosystem.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by ratww on Friday May 27, 2022 @08:34AM (#31528817)
> You can still do a webpage just like you did 20 years ago, inserting a couple HTML tags in a notepad.

Yes, I agree. That's exactly what I said in several parts of my message. However I believe you missed the point and didn't notice the sarcastic tone.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by igouy on Friday May 27, 2022 @02:00PM (#31532670)
Perhaps expecting readers of a message board to pick-up on your sarcastic tone is not going to be an effective way to communicate your point.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by ratww on Friday May 27, 2022 @02:29PM (#31533047)
I believe I did fine conveying it. The last paragraph makes it pretty clear I know there are other solutions. The problem with the reply wan't the sarcasm, but not reading the whole message.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by Merad on Friday May 27, 2022 @09:34AM (#31529449)
Not to be an ass, but playing with css and html isn't programming. At all. It's making web pages. The web is so universal today that many people conflate "making web pages" and "programming". And there's nothing really wrong with that _if your goal is to learn to make web pages,_ but I'm pretty sure there are still more than a few people out there who want to solve problems with code, or just learn to code, with little or no interest in the web. Telling them to start with html + css is kind of like telling an aspiring painter that it's easy to start making sketches with a pencil and paper.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by mhuffman on Friday May 27, 2022 @10:41AM (#31530215)
>Not to be an ass, but playing with css and html isn't programming. At all. It's making web pages.

... except you can literally make desktop and mobile applications now by "playing with css and html"! ^electron -- shudder!^

Part of the reason for the JS mess (which people have been bitching about for years and years) is how easy it is to dip your toes into. Match that with how easy it is to create a "gui" now with HTML and CSS, stir in an endless bunch of half-baked support libraries built by people that just learned JS last month and you get the perpetual hell of the JS ecosystem.

And now that it has been adopted by startups and traditional companies, it is here to stay for a while.

Half of my development time when dealing with a new JS project is un-fucking some JS dependency that I never wanted that lives deep in the bowels of npm_modules.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by potta_coffee on Friday May 27, 2022 @02:04PM (#31532723)
There's a whole lot more to Electron than HTML / CSS and getting started with it is honestly a huge PITA, in my opinion. This is coming from someone well versed in full stack web development who has delivered substantial projects.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by throwaway675309 on Sunday May 29, 2022 @05:00PM (#31552826)
Maybe but it depends on what you mean by "back in the day". Because back in the day a lot of computers came preinstalled with some version of a BASIC interpreter, And some machines literally booted into basic by default, so programming became just a natural extension of the users daily computing process.

However, If you're referring to 2012 as back in the day, visual basic was by far and away completely deprecated by that point, if anything people would've been using Visual Studio community edition to do net programming and maybe visualbasic.net

Re:Today’s JavaScript, from an outsider’s perspective (2020) by wrp on Friday May 27, 2022 @07:00AM (#31528118)
This has been a professional concern for me for many years. I lead grad students with no programming experience into making their own tools for research and sharing. I've completely given up on learning a programming ecosystem and building programs from scratch. Rather, I work within applications that can be scripted to a task. I envy the engineering students for whom Matlab is enough, because that seems to be the closest modern equivalent of Visual Basic. Mathematica is sort of there, but much harder to learn and not easily shareable.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by a_square_peg on Friday May 27, 2022 @09:05AM (#31529142)
Yeah - I work with Python for my main work dealing with weather & climate data but things still throw me off. It feels like every example I run into is an easy to follow "20-steps + 10 packages + 64GB cloud server instance" process when all I want to do is to download some historical temperature data to CSV.

Example: https://github.com/jwagemann/era5_in_gee#workflow-overview

Re:Today’s JavaScript, from an outsider’s perspective (2020) by o-o- on Friday May 27, 2022 @06:09AM (#31527840)
I think you sum it up well. That gap extends to more than JavaScript.

When I was four I could operate our TV: turn on, choose channel and adjust the volume. One device. One remote control. Bach then four year olds could also operate phones and record players. When I was five me and my friends could operate a tape recorder, copy music, record music, create tapes and physically share with friends and family.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by wly_cdgr on Friday May 27, 2022 @11:59AM (#31531141)
There's space in tools like Godot, which has a relatively stable API, tight and helpful integration with its custom scripting language as well as support for both C# and C++, solid docs, first-class support for 2D, the ability to export to mobile as well as web and desktop, and the ability to toggle between a continuous rendering mode suitable for games and a reactive rendering mode more suitable for apps.

GameMaker, too, has a very stable API for its proprietary scripting language and, though it is made with 2D gamedev in mind, can work just fine for simple apps for personal use.

Defold is worth mentioning as well

Re:Today’s JavaScript, from an outsider’s perspective (2020) by elorant on Friday May 27, 2022 @07:10AM (#31528191)
Or you just ignore all the shiny new things and go with older technologies that work like a charm. I for one, still write code in jQuery, and don't plan to switch at least for the next five years.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by mbrodersen on Saturday May 28, 2022 @09:38PM (#31545456)
Yep exactly right. Do as much as you can with plain HTML, CSS and JavaScript. Learn the basics without depending on any packages. And only then maybe add a package if it really absolutely is worth it compared with writing a bit of extra stuff yourself. Every build system or package you rely on will become a liability and a major pain point down the road. Guaranteed.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by wonderbore on Friday May 27, 2022 @09:31AM (#31529410)
I’m pretty sure you can still write some js and load it into the browser or node. The issue is that 10 small instructions become a hundred (thankfully) and so if you read the wrong article you will be lost.

If this guy was told to use `require` instead of `import` it would have most likely just worked. The instructions were wrong so he failed.

Even back then though you still needed to RTFM. The first time I wanted to do a bubble menu (the one that follows your cursor, focusing an item of the menu) I was redirected to Flash.

Re:Today’s JavaScript, from an outsider’s perspective (2020) by bennysomething on Friday May 27, 2022 @09:39AM (#31529508)
On a related note I think this is what is sort of wrong about the raspberry pi as tool for teaching beginners: the first thing the user sees and interacts with is Linux. In the 80s on a bubber key spectrum as far as I can recall it booted straight into a basic prompt / repl (or whatever the right term is). Even 8 year old me could start programming. Compare that to trying to get anywhere with Linux as a beginner.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by alex_smart on Friday May 27, 2022 @06:12AM (#31527849)
I think in this particular case, the problem was just picking the wrong tool for the job. Python is the primary language used for data science these days, but it is not particularly designed for it. It is a general purpose programming language. If they had chosen something like R, their path would have been a lot smoother.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by wrp on Friday May 27, 2022 @07:22AM (#31528266)
Smoother but not smooth. I once, not by choice, taught R to humanities grad students who had never programmed before. The wailing and gnashing of teeth over the course that semester was considerable, and I have stoutly refused to ever do it again. The irony of it was that they really didn't need to do anything that couldn't be done in Excel.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by rvba on Friday May 27, 2022 @09:53AM (#31529652)
> We've gotten to the point where you cannot be SLIGHTLY interested in computers, want to make a quick app for yourself

it seems Excel is the last place like this - to make small pseudo apps, but it comes with its own fair share of problems (mostly calculations or Excel as a database, no sharing)

I think VBA used to be the thing, but the one inside MS Office is "technologically" stuck around year 1996

Re:Today’s JavaScript, from an outsider’s perspective (2020) by Angostura on Friday May 27, 2022 @06:07AM (#31527823)
Whatever you think of it, I think that MS tries to cater for these people with things like Flow and PowerApps with Office 365
Re:Today’s JavaScript, from an outsider’s perspective (2020) by tosh on Friday May 27, 2022 @05:33AM (#31527633)
In a sense no-code tools are today’s Visual Basic.
Re:Today’s JavaScript, from an outsider’s perspective (2020) by mike_hearn on Friday May 27, 2022 @05:47AM (#31527706)
Well, not really. The no-code tool of the 90s was Access or maybe Excel. VB was useful exactly because it was code, but simplified. One thing the Microsoft stack really nailed was a smooth(er) on-ramp. There was a big gap between VB and C++ which is partly what motivated the development of C#/Java but otherwise, you could start with Excel or Access, move up to VBA and build an actually useful app that delivered business value. Then you could take those skills and move to VB6 and build "real" apps that you could ship to users and charge money for, build whole businesses around. You could learn some Win32 using VB/Win32 interop and then progress to C, and from there, to C++, or later from VB to VB.NET and then C#.

The web stack sort of killed all that. You can start with HTML and get some results pretty fast but you'll very rapidly hit the limits of what can be done there and suddenly be hit with this giant wall of complexity. NodeJS helps because now you can use the same language on backend and frontend, but even getting to the point where you have a frontend and backend requires mastering a heap of tech with appalling usability (like UNIX). And the modern JS ecosystem is sufficiently complicated that you'll hit problems like the ones described in the article.

One way to fix this is to bring the VB6 model back, by making desktop apps great again. It can be done. There are toolkits that make it easy to write standalone cross-platform apps (e.g. JVM languages+JavaFX, Flutter, the new C# stuff, Qt, etc). There's no fundamental reason distributing desktop apps must be difficult, it's just a neglected area of tooling.

And that's a nice segue to my current startup, which is tackling exactly that problem. We've produced a tool that makes distributing desktop apps as easy as distributing web apps is (or easier!). It takes the output of your build system (if any) as inputs, and builds self-updating packages for Windows, macOS and Linux without needing you to actually have any of those platforms. It can also fully sign those packages itself (without needing macOS or Windows), or self-sign them in which case you get a `curl | bash` type install experience and the PowerShell equivalent for Windows. Finally it produces a simple download HTML page that detects the user's OS and gives them a nice big green button to click.

We've talked to one well known tech firm that wants to integrate this into their products and a driving reason is, in fact, educational. They have a lot of new programmers who use their developer tools and who learn with a desktop toolkit because it's easy to get things on the screen, there's one language to learn, it's all cleanly following the principles they're taught in class (like objects) and so on. But then they hit a wall when they want to show their friends and family what they're doing, or graduate to actually getting real users. Smoothing that on-ramp should help a lot.

At the moment the tool is in private beta, but if you want to try it email me (address in my profile). After public launch it'll be free for open source projects, licensed for commercial projects. Thinking about a feature that automatically bundles source and adds a "view source" button to the apps, to help students who haven't yet mastered uploading code to GitHub.