11 ms·
Programming COULD use a lot of simplification and removal of barriers. But still, just like you, I really hate the base attitude here. And for a different reas
by izacus 6y ago
Programming COULD use a lot of simplification and removal of barriers. But still, just like you, I really hate the base attitude here.
And for a different reason: I find that programmers who think like this, are also lazy when it comes to respecting the user. They're lazy when it comes to supporting accessibility. They're lazy when it somes to properly supporting i18n and making experience great for non-Americans. They're lazy when it comes to respecting privacy and not burning 8GB of RAM just to render a webshop frontend.
They'll say "this is hard" and add Facebook SDK to do things for them. They'll say "this is hard" and make the page inaccessible for people that don't own a 4000$ 16" MBP and has perfect vision.
That's the core issue of this attitude for me, which I'm seeing by too many people I mentor. Development is sometimes hard and requires hard work to do right by people.
- lionkor 6y ago> Programming COULD use a lot of simplification I disagree, actually. There are plenty of languages, and even visual programming (via flow-diagrams, like Unreal Engine's "Blueprint" and Blender's shader flow diagrams), for those who just want to play around. For people who want to write a quick and dirty script, languages like python make it very easy already (relative to what they actually do). > Programming COULD use [...] removal of barriers Absolutely agree with this, though. There's an unnecessary elitism in many places that really needs to go.. > Development is sometimes hard and requires hard work to do right by people. This is *so* important for these people to understand. There are languages and domains where the "elitism" is fully justified. If someone decides they want to write a high performance, easy to use, cross platform native application and complain about C++ or Rust being too complicated, then they should find an easier job. There is justified and unjustified elitism, and there are domains which could use, if anything, even more "complication" and more specifications, more "barriers" to ensure higher quality.
- aspaceman 6y agoYeah like there's 20 years of programming language research that studies exactly what this person is talking about. Graphical programming languages, removing barriers to learning, etc. They've been chugging away for decades and visual programming, Blender, Blueprints, Scratch, etc are all we got out of it. Does the article writer just think research doesn't exist? That CS sprouted from existence fully formed as a web browsing experience?
- naavis 6y ago> Yeah like there's 20 years of programming language research that studies exactly what this person is talking about. More like 50 years. :)
- monetus 6y agoRelevant alan kay video from 1968 https://youtu.be/QQhVQ1UG6aM https://youtu.be/QQhVQ1UG6aM
- alickz 6y agoThat is extremely impressive. I'm not sure I want to code like that, but damn is it impressive.
- phkahler 6y agoEverything looks better on a vector display. :-)
- Ygg2 6y agoThat's impressive demo. But graphical representation literally have an extra dimension of problems. Namely navigation and serialization.
- azinman2 6y agoNothing in the article said “why hasn’t this been researched by the CS community?” The author was complaining about the state of things, and I don’t disagree. Programming is too hard. Error messages are always funky and assume expertise. And perhaps the node folks should better understand that beginners are often a target of their product and should find ways to make it more accessible to them. Blueprints and Scratch are widely used and are important tools. Your comment sounds very dismissive, and if you meant to be, then I think you’re unaware of their impact and reach. That said I don’t fully buy the author’s exact argument: - node.js local install IS for a traditional programming environment on the CLI - you don’t need node built in when you have the browser - plenty of web IDEs exist that do as the author wishes… run node code in the browser while also editing it.
- AnIdiotOnTheNet 6y ago> There are languages and domains where the "elitism" is fully justified. If someone decides they want to write a high performance, easy to use, cross platform native application and complain about C++ or Rust being too complicated, then they should find an easier job. I disagree. I follow a lot of game developers and you'd be hard pressed to say they don't do high-performance corss-platform native application development. They almost universally think C++ (and by extension Rust) are too complicated. They generally use C++ anyway because that's the industry standard, but they think there is definitely a conceptually less-complicated way to do things. See: Jonathan Blow and Casey Muratori, for instance. The former is so sick of C++ he's making his own programming language, and the latter routinely complains about C++'s complexity and eschews all but the simplest features of it.
- bccdee 6y agoI'd argue that Rust is meaningfully simpler than C++. Mind you, it's also a fairly feature-rich language, but the complexity of C++ comes from decades of new features building up trying to supersede older features. C++ is several different languages by now depending on which feature set you use, but Rust is still just one language. C++'s complexity is also a product of design choices like using templates to do both generics and metaprogramming, which in hindsight probably made things much harder than they needed to be. Rust has the benefit of being able to avoid decades of C++'s missteps.
- AnIdiotOnTheNet 6y agoI don't know much about Rust, because it doesn't seem to be the kind of language I want to use, so I can't personally speak to its complexity. However, I do know that a lot of objections to it from the people I follow are around the borrow checker and both the friction and high[0] compile times it causes. [0] to put that in context, Jon is frequently annoyed by the sub-second linking time incurred by LLVM because it is more than an order of magnitude longer than his largest program (~60k line game, IIRC) takes to compile.
- shrimp_emoji 6y ago
- bccdee 6y agoTo be fair, c++ is too complicated, but that's an unrelated conversation, haha.
- marcus_holmes 6y agoAnd yet... when Flash provided a simple, easy, way for people to get into coding using a GUI, there was an explosion of creativity. Flash was terrible for all sorts of other reasons. But it did demonstrate that there is a class of incredibly creative people out there who can create amazing things, but not on the command line, and not using the tools currently available. How do we get them doing that again?
- TeMPOraL 6y agoShut down YouTube. I'm serious. I don't think there can be another "explosion of creativity" of the (relative) magnitude of Flash, because people now express themselves by recording videos. It's both easier and more social than making interactive software, even with Flash.
- virgil_disgr4ce 6y agoThat doesn't make any sense. You don't inspire creativity-explosions by shutting down existing platforms, you do it by providing new affordances, which is what Flash did. And videos aren't even interactive! There's not even any comparison here.
- TeMPOraL 6y agoMass creativity follows the path of least resistance. Existence of YouTube - as a much easier and more social venue for self-expression - precludes mass popularity of Flash vids/games. To beat YouTube, a new affordance must be both easier and more socially appealing (because mass creativity tends to be done mostly to show off in front of friends/colleagues or romantic interests).
- virgil_disgr4ce 6y ago> because mass creativity tends to be done mostly to show off in front of friends/colleagues or romantic interests ?? What kind of bizarre red-pill nonsense is this? You think all those interactive Flash microsites were to impress girls? lol
- accountLost 6y agoEven hardworking developers will sometimes don't care about the user experience. For example, Linus could have spent a few hours polishing the git CLI. Instead we have had millions of developer hours wasted in making sens of the CLI inconsistencies...
- humanrebar 6y agoThere is also infinite configurability and plugability through aliases and plugins. If you really hate `git checkout -b`, ship `git make-branch` that suits your taste. You can even package it as a trivial script to redistribute if you wanted.
- recursive 6y agoIMO sane defaults are sometimes worth more than infinite extensibility.
- phkahler 6y agoIMO extensibility generally means the authors dont know how real people will use software. Programmers do things by writing code, compiling, deploying, etc... so the notion of customizing an app through anything that looks like their workflow seems fine to them. OTOH I write code for a living and I often hate the tools we use...
- austincheney 6y ago> Programming COULD use a lot of simplification I so completely disagree. Writing JavaScript is already so simple that almost nobody knows how to do it any more. You can download a colossal framework and a billion NPM packages to write some completely unoriginal CRUD application and bitch about how hard life is. Fearing writing original code is the name of the game.
- KronisLV 6y agoBut isn't using the code that people smarter/more proficient than you have developed a rather good way to go about things? If not, where do you draw the line? Should you write your own business logic? Should you write your own logic to allow implementing that business logic (e.g. request parsing, validators, data transformations and processing etc.)? Or maybe you should write your own web framework that routes and handles HTTP(S) requests? Or maybe the entire ORM (if you're using one in the first place) as well? But that ORM probably uses JDBC/ODBC or some other driver as well, and the HTTP(S) requests also can be processed because of some additional code and libraries. Should you write those as well? What about the operating system itself, and the code that allows it to interface with the hardware? What about the kernel? I don't necessarily agree with the OP's point about making a browser that has Node.js packaged (though it's a novel idea), but i definitely agree that defaults and tools matter. Tools like XAMPP ( https://www.apachefriends.org/index.html https://www.apachefriends.org/index.html ) or the CLIs for automatically generating projects and helping automate everything from creating project files, like in Ruby on Rails Generators ( https://guides.rubyonrails.org/generators.html https://guides.rubyonrails.org/generators.html ) or entire apps, like with JHipster ( https://www.jhipster.tech/ https://www.jhipster.tech/ ) or create-react-app ( https://reactjs.org/docs/create-a-new-react-app.html https://reactjs.org/docs/create-a-new-react-app.html ) all seem to decrease the chance of human error and make development safer, more consistent and easier. Even IDEs that are aware of the specifics of the frameworks you're using can be very useful! In addition, they can improve the developer experience (DX) a whole bunch, since in larger projects time can be invested to address common problems. For example, see Dylan Beattie's conference talk on the topic: https://youtu.be/lFRKrHE8oPo?t=431 https://youtu.be/lFRKrHE8oPo?t=431 I've seen people trying to write their own web frameworks and most of the time the results have been poor, both in understanding the system and maintaining it in the long term, in addition to which you can't hire people that are familiar with "Random Company's Web Framework". Unoriginality is good for being to maintain the project, as far as i'm concerned. Here's another conference talk, by Venkat Subramaniam about deciding between using existing code or writing your own: https://youtu.be/OheeK7Ux2-8?t=727 https://youtu.be/OheeK7Ux2-8?t=727
- uCantCauseUCant 6y agoWe have been there, the cycle has passed three times. We had had them all, the paradigms of self-repairing, self-correcting, best effort software. Resulting in major it disaster created by newbs, burning away years of life of the professionals. This conversation is so cyclic, that even the longing for "simple software" is by now a meta-perpetum-mobile. This all becomes much more easier to grasp, once you replace "easy to use software" with "cold fusion" or "free energy". I dread the day, were AI is used to deduce how the story ends, and the "autocomplete my thought" software world gives birth to a new horror. PHP, Javascript, Python -> I wonder why the simple things never stayed simple and grew complexity warts. Maybe humanity just doesn't know what it is doing.