7 ms·
I remember reading articles like this years ago. ... Except that they were lamenting the rise of GUI operating systems and how those eliminated the easy on-ram
by munificent 8y ago
I remember reading articles like this years ago.
... Except that they were lamenting the rise of GUI operating systems and how those eliminated the easy on-ramps that command line OSes had where you could write a simple BASIC program that felt like something real.
It is important to be thoughtful about how people can easily get into computing. But it's also important to not idolize or idealize the particular on-ramp you took X years ago. Those ramps are going to die and get replaced by new ones. It's part of technological progress. As long as new paths come along — and they always seem to — it's gonna be fine.
Frankly, raw HTML and CSS is already a dying path. If you get someone to build a simple web page from scratch, it won't feel like a "real thing" to them. Because, today, "real" now means it has social sharing, interactivity, and a certain level of visual polish your web page will lack.
A WordPress install is a better path because it looks nice. And then they can start tweaking the template and the next thing you know they are learning a little HTML and CSS, but in the context of something that already feels real.
Forcing them to start with an empty notepad document is like getting someone interested in cooking by making them grow wheat.
- wwweston 8y ago> Frankly, raw HTML and CSS is already a dying path. If you get someone to build a simple web page from scratch, it won't feel like a "real thing" to them. Because, today, "real" now means it has social sharing, interactivity, and a certain level of visual polish your web page will lack. Social sharing, interactivity, and reasonable-to-high levels of visual polish were all frequent features presented with raw HTML/CSS a decade ago. If you have a decent designer available to you, some of them can hand you a quality original screen design in an day or less in a PSD/Illustrator/whatever file, and it's possible for most cases to convert it to HTML/CSS from scratch in about the same time (at least, it was for me by the time I'd done a hundred or two of them). Responsive may add time depending on the layout conception. All of this can work pretty much the same today. If you don't have a good designer and/or design isn't going to distinguish you (or you want the benefits from fitting into widely-present framework styles), a template or framework can make a lot of sense. But that's a different proposition from saying HTML/CSS is a dying path. Interactivity & Sharing: up to a certain point, interactivity via progressive enhancement costs no more time/effort than application-centric approaches unless you're truly building an application over a hypertext document with some added features. Possibly less. Social sharing is usually a matter of dropping the right widget into a page. > Forcing them to start with an empty notepad document is like getting someone interested in cooking by making them grow wheat. It's more like having people start with buying/using their own staples instead of a meal kits or deli meals. The latter can be delicious and convenient, but it doesn't mean the staples aren't a viable path.
- duckMuppet 8y agoAdditionally, relying on another app such add WordPress leaves you at the mercy of that app and it's development.
- onion2k 8y agoMost Wordpress-driven websites these days are essentially temporary marketing assets. You can use Wordpress to build a site that'll be online for a decade, and people have done, but the overwhelming majority of websites don't last more than a couple of years. Using a platform that doesn't lend itself to long-term stability is fine in that use case.
- gdfasfklshg4 8y agoWorking with a good designer that knows HTML+CSS is amazing. It is lovely to get delivered working responsive HTML documents to convert into the web site or web app compared to getting delivered photoshop/illustrator files. Apart from anything else a designer that knows HTML+CSS produces designs that actually work on the web. Designers that only know photoshop/illustrator invariably produce unworkable designs.
- Sharlin 8y agoAgreed wholeheartedly. The whole concept of a graphic designer creating static images of layouts, which are then translated into code by a programmer, should die in fire. It's just another instance of nontechnical people writing specs for applications and having programmers translate them into code. UI/UX design is not graphic design or programming. It is both and neither.
- collinmanderson 8y agoThough some designers really do know UI/UX design, they just aren't as much of an expert with HTML/CSS.
- 8y ago
- samirm 8y agoI agree that old "ramps" are going to die and get replaced by newer ones as part of general technological progress, but your comparison to cooking is just nonsensical. Using HTML+CSS to build a site from scratch is not at all like growing wheat... let's not make false equivalence fallacies here.
- Townley 8y agoI love the wheat analogy on a few levels An excellent chef may know that midwestern wheat makes tougher bread than southern wheat, and that White Lily flower is a great brand for softer wheat with less proteins. But that's useless knowledge--and added complexity--for a total newbie who's never thought about what "rising dough" means. One of my friends got into programming recently by building netlify-hosted react websites. Yes, his need to learn JSX and the strange capitalization of reactifiedHtmlAttributes is additional mental overhead, but because some onramps have gone away entirely, he won't have to worry about FTPing files up to a server, or Linux file permissions, or configuring Nginx, until he's established. So whether it's cooking or programming, the "on ramps" have definitely changed, but it's never been easier for anyone to get started building high-quality products.
- dccoolgai 8y agoWait, are we seriously saying HTML and CSS are "useless knowledge" for web development. Wheat is a horrible analogy... it's like trying to be a cook without knowing how to use an oven. "Ovens are useless since George Foreman grills came out." You probably could cook most things on a Foreman grill, but that doesn't make you a good chef.
- otras 8y agoYou may have missed it with the aside, but GP wrote “useless knowledge--and added complexity-- for a total newbie” (emphasis added)
- learc83 8y agoHTML and CSS aren't useless knowledge even for a total newbie. It's all HTML and CSS in the end. Maybe one day the abstractions will be good enough, but for now they are way too leaky to try to pretend they don't exist, even for total newbies.
- zorronimous 8y agoWe have microwaves now. Forget everything you know - this is the future. And with the future I mean the bullshit.
- zanny 8y agoI recently started making a personal reddit clone mostly to learn Grid properly but I'm having no problem making custom controls (checkboxes, search bars, forms, etc) that look "professional" with just a consistent color palette, some borders, shadows, gradients, and linear transitions. A lot of it in my experience is because you can use flex / grid almost everywhere to evenly space / proportion content now so you don't have to do as much pixel fidgeting to get things looking right. I'm using .5rem gaps and padding everywhere and it just looks pretty dang crisp out of the box. At least compared to what you could do even five years ago its lightyears ahead in ergonomics. Still rubbish because its still html and css at the end of the day, but a far cry from floating half the page.
- themodelplumber 8y agoI appreciate the thoughtfulness you've put into this, but I have to disagree a little bit. First, I am perpetually shocked to find peers in tech who still use BASIC or other tools that others see as outdated. The last one I found was a food product company; their lead tech guy, a member of the family, had given new meaning to NIH with the system he showed me. His website spec document literally started and ended with DO NOT WANT WORDPRESS, in large part, he explained, because he wanted someone who brought the same mindset to technology that he did: Invent something that fits the problem like a glove. And--that probably will not even closely resemble WordPress. I've since learned that what really happens to influence a technology decision is not trend or "technological progress" alone. At the root of this stuff is human psychology. And not even individual human psychology, but human _relational_ psychology. In some human relational systems you get things like this: A family that is technologically backwards _by psychology_ sells a high-demand food product. They displace all of their technology thinking onto their son, or whoever is even remotely interested. And _that_ person does whatever they're comfortable with and good at. Voila: The rich and hidden empire of yesterday's tech! And...you want to work with that person, you want that company to give you access to their funding--you have to kind of protect their on-ramp and you even quickly realize: Gosh, it still works and even surprisingly well! Otherwise they will tell mom and dad: "Sorry, we still have to use yesterday's tech." Well: Mom and dad actually love hearing that. We will always need students who are ready to work with people and companies like this. So I disagree that raw HTML and CSS are a dying path in a way that rules them out except for that set of new learners for whom it's less "specific problem solving" and more "build a website as you see them on the web". Clients who ask for WordPress these days are sometimes simply asking for what friends told them to ask for. For those building the websites, it can be a golden opportunity to step in and really bring problem-solving skills to bear, where the client can't be bothered to do so. Otherwise you paint a big target on your back for competition with other "WordPress companies" and the like. $300 gets you a new website, that kind of thing. I absolutely agree about the overall risk of starting students out with an empty Notepad document too. I got into WordPress and Mambo/Joomla back in 2006 and had a blast right up until I was using gobs of plugins for everything and then they started to die, or get bought out by e.g. a company that tried to spam my clients with telecommunications equipment advertisements. What is there to do but start really figuring out how to solve problems without the plugins, in a situation like this? Then I found Textpattern, which was an amazingly great way to start dipping toes into template design and eventually PHP and SQL. When I taught people web design at our local college, I made sure they knew the advantages and disadvantages of Photoshop HTML Export, and then taught them how to do it in the best way possible. I gave extra credit points to those who would dive into the code a little bit.
- jm2 8y agoAt first I suspected I was becoming lazy now, only because I believed, against my own unsettling self ridicule I recognise that nervous giggle was, that I should have a pure distilled and faultless prompt / repl / vim / emacs install / ide / visual studio enterprise edition / PGI suite crystallised as if my own personal x-kryptonite shard, pulsing invitingly in my minimalist polar cave. Imaginatively my infallible future perfect hindsight convinced me that I would be mad to expect a 10 year old me to build a current development system. Oh my, how preposterous of me. The lengths I went to to get my mitts on my first very own workstation I think can't be repeated on grounds of antisocial hubris. I was monomanaical. Over years. I ditched a first rate education for which I (to my retrospective surprise) knew I was a second rate candidate by this obsessive proto virtue if nothing else. I have since learned that this is a universal human counterfactual and misconception: we inevitably one day look around us and fail to find the totemic beautified objects of our youthful ambition. ("Where is my beautiful house?") But we have already grown up, and in so doing, found human cares supplant the material and abstract and idealistic, it happened with the most materially successful people I know even more acutely to my experience. Whether religious or atheist I think we can all take solace in the drive and determination and inventiveness of the next generation to face the similar issues. Meanwhile, echoing just about everyone who has responded, I think we've reinvented enough prompts and repls and gui libraries and stdios sufficient there likely will be some of them to survive the apocalypse.
- Waterluvian 8y agoYour writing style is verbose and bombastic. Do you write often? I'd enjoy more of this.
- selimthegrim 8y agoSeconded. 10/10 would Patreon (again if necessary)
- maroonblazer 8y agoAgree, it is verbose and bombastic. But I prefer clear and simple (but no simpler). I'd enjoy less of this.
- exodust 8y ago> Because, today, "real" now means it has social sharing, interactivity, and a certain level of visual polish your web page will lack. Apparently a real website has social sharing and "interactivity" that can't be achieved with raw code! I'm guessing you're not a developer. > * A WordPress install is a better path because it looks nice.* That's the saddest statement I've read all week, only topped by.. "Growing wheat?" Nobody suggested "notepad". A basic HTML structure can be achieved in 5 minutes in your code editor. From there it's about populating that structure with layout components. Yet more minutes coming your way. What, you wanted to have your site made by clicking a few buttons? "Tweaking the template" in Wordpress is an exercise in extreme patience. A lot of faith in the black box under the Wordpress hood, and a spammy, over-commercialized "do you want fries with that" plugin ecosystem. The fragmented style of adding custom CSS or HTML in wordpress... you end up with a bloated unsustainable, messy maintenance headache. That's how you want people to learn web dev? > Frankly, raw HTML and CSS is already a dying path Rubbish. When it comes to doing interesting polished "modern" things with transitions, nested flexbox layouts, interactivity, and custom light-weight modules, there's no better way to control the quality and details of a web product than with raw coding.
- zorronimous 8y agoIll suggest notepad. Ill slap together some basic html doctype a head with style and script tags, yes inline, a body with some simple divs and in no time at all it will look as good if not better than the hipster 50 000 line Frankensteins monster of bloat. In the 80's we knew that a single small optimalization was worthless but if you acumulate enouh of them the sum of the parts blew the mind of even the most sophisticated software wizards. The trend nowadays is to hoard deoptimalizations while arguing it doesnt mater. I keep wondering why popular modules so rarely make it into the language. I joked the other day that it would be nice to have sortable <table>'s out of the box. Imagine the table code was <table json="{}"/> and that we could do <form json="{}"/> too. The amount of code we could discard. lol
- pbhjpbhj 8y ago>and in no time at all it will look as good if not better // Back in the day, you then tested it on IE and did the other 50% of the work. Then you basically created a framework to ease that, and include fixes for it browsers too, and then you realised you were making a framework and that it was more optimal to use an established framework that 50,000 man hours had already been spent on ... Before you know it you're theming WordPress on a shared hosting server, rather than ./configure-ing httpd and writing everything in nano.
- yc12340 8y ago> I remember reading articles like this years ago. >... Except that they were lamenting the rise of GUI operating systems and how those eliminated the easy on-ramps that command line OSes had where you could write a simple BASIC program that felt like something real. Are you implying, that they were wrong? "The rise of GUI operating systems" haven't killed off the existing programming paradigm. It still exist, — it is called "back-end". And I can testify, that back-end programming is order of magnitude simpler, faster and leaner than modern front-end or Android development.
- pjmlp 8y agoAnything is leaner, faster than whatever Google does with Android Studio, and their continuously WIP SDK, where stable releases are a synonym for beta.
- soperj 8y agoThis seems like the whole don't learn CSS, learn bootstrap, foundation, bulma, etc. Don't learn javascript, learn react, or vue or angular. You can do a hell of a lot with css and html(including interactivity), and considering the amount of cross browser support you don't even really need a framework these days.
- austincheney 8y ago> Those ramps are going to die and get replaced by new ones. It's part of technological progress. That completely misses the point. This makes sense as technology changes, however, HTML and CSS are not dramatically different now than they were 20 years ago. Despite that lack of significant difference the approach and entry points have radically changed and continue to change. This is problematic for a number of reasons addressed in the article. The article touched on only one of the two biggest problems. The article did a great job talking about the churn every couple of years and the associated disconnect between a former group and a later group of developers. That disconnect is incredibly understated and important. The article fails to talk about performance. Many sites today are not more performant than sites more than a decade ago even though hardware and JavaScript are orders of magnitude faster. If everything is 10s or 100s of times faster and yet the end products remain the same what got lost? The technology got lost behind layers of abstractions. These abstractions, in almost every case, don't exist to supplement (enhance) the technology. They exist to supplement the developer. My personal single page app pushes nearly 1.5mb of JavaScript doing really heavy computing to the user and yet the site is still fully loaded in about 1.6s. The techniques I use scares the shit out of younger developers, because they are old and primitive (and yet stupid fast). I can remember the last big dot com I worked at struggled to get back down to 16s homepage load from 24s even though there is very little code doing anything the user would care for on site load. > there is something deeper and more worrying than a company having to throw away a couple of years of work and rebuild because they can’t support a poorly chosen framework. In my experience every framework or technology stack becomes poorly chosen on a long enough timeline by the incoming developers. Consider other solutions before thinking about abstraction, abstract only as an exception to policy, and then document the measured costs. Consider the current most popular web abstraction: React. There are now numerous abstractions for React. It is only a matter of time before those abstractions over abstractions have their own abstractions until somebody wants to reinvent the framework again. People now spend more time and energy learning the abstractions than I spent learning the base technologies, but then difference is that my comfort with the base technologies allows me to spit out a solution in less time, that is smaller, and performs faster to the shock and disgust of framework advocates. That makes perfect sense realizing that the abstractions are there to supplement the technology but to supplement the developer.
- arethuza 8y ago'it won't feel like a "real thing" to them' I always find it amusing that we are having these discussions on HN which is about as old school as web technology gets and which doesn't seem to suffer too badly....
- pjmlp 8y agoBecause we are Wizards discussing how to get Muggles into our world.
- teddyh 8y ago> important to not idolize or idealize the particular on-ramp you took X years ago. I agree tremendously. As I wrote four years ago¹: It’s not too late in 2015 to get started in computers. People who got started in the 1990’s feel that way because they started in assembly language and compilers and all that, and how could anyone starting now possibly learn all that? What they don’t realize is that people who got started in computers in the 1960’s feel that since they started with soldering and electronics and radio and circuits, nobody could possibly learn all that. It’s easy to start in computers at any time. You simply ignore all the stuff that’s too low level to be worth your time to get bogged down in. And two years ago²: You were frustrated by Windows 98 because you could not reason about it on the level you were used to. But think back on the earlier electronic enthusiasts who were used to thinking about resistors and voltages – they would have been just as frustrated by your ZX Spectrum because they would not have been able to reason about machine code by thinking about what voltages they mean. The level to reason about Windows 98 would instead be by thinking about installed programs, registry settings, DLLs, etc. If someone came to computers fresh and started with Windows 98, this level is what they would know. And three months ago³: […] Hasn’t it always been the case that the current generation skips learning about useless lower layers used by older generations? How could it be that the layers you grew up are the special ones which are still useful, when all the layers which came before, which people at the time thought essential, have turned out not to be so? […] 1. https://news.ycombinator.com/item?id=8952800#8953744 https://news.ycombinator.com/item?id=8952800#8953744 2. https://news.ycombinator.com/item?id=13675268#13677390 https://news.ycombinator.com/item?id=13675268#13677390 3. https://news.ycombinator.com/item?id=18228740#18240422 https://news.ycombinator.com/item?id=18228740#18240422
- darepublic 8y agoDon't disagree with you but you can still create something 'real' with HTML, CSS, _Javascript_ and notepad :)
- sly010 8y ago> Those ramps are going to die and get replaced by new ones. No. They will be perhaps covered with a shiny rug, but not replaced. Technology is not "changing" there is just more of it. And it's just as important to be aware of that.