Show HN: Revived my personal website to join the nostalgia(gasoved.github.io) |
Show HN: Revived my personal website to join the nostalgia(gasoved.github.io) |
The websites themselves weren't much in the way of a destination, rather they tied you into other real world things: family, computers systems, hobbies. They were relevant only as much as they enriched real life.
Now the website is the full app and experience. No need to go anywhere else. In fact it's desirable that you stay on one property, such as Facebook for as long as possible. It's like a big box store.
But back to the point I wanted to make originally: the work has fundamentally changed. I remember coding a backend to get old scientific python scripts to run from commands via Sharepoint buttons. The web couldn't do anything so you had to tie it to systems that could. Now you have to get it all running in Javascript --- not sure how many people saw that coming :-D.
I wonder if anyone has any thoughts along those lines?
I remember in 2001 my brother's community college in rural America taught HTML and Flash development. Not only could you learn to make websites quickly, but you were learning technology that was exactly what you would be using when working at a company.
You could argue the technology is better these days, but it's certainly not more clear to newcomers. I recently described to my younger sister that she should learn React through FreeCodeCamp in order to make websites - but suddenly you are dropped into a world talking about declarative programming paradigms, unidirectional data flows, and lots of other foreign concepts described as magic (the virtual DOM, Babel, etc.)
If my experience had been this growing up I would have never gained interest in learning the specifics / details of what was going on when writing HTML/CSS/JS code. I would've chalked it up to "there are layers upon layers of magical things I don't understand, I guess I only need to interact with them and slap them together."
I also think the incentives have changed - it's less about making something cool and sharing it with your internet friends these days because there is money to be made - it's about buffing your GitHub profile to get a job, creating a startup that extracts $$$ from people, etc.
I feel it is very similar to early days YouTube vs. YouTube these days, and that saddens me.
That's fine though.
If someone learns C++ today without knowing any ASM very few people would tell them they're "doing it wrong". If someone learns Unreal Blueprints without learning C++ senior game developers still see them as productive game developers. If someone writes a great GLSL shader on shadertoy without knowing how to use WebGL that's OK too. You don't have to understand all the layers in order to use them and make good stuff.
The web is no different. I see no reason why people can't just concentrate on learning the top level abstraction to make things until they encounter a problem that they need to know more about the lower levels to solve. They might never have that problem.
All of this "You have to learn the underlying tech in order to use the framework on top of it" just sounds like gatekeeping to me.
The last thing I would tell him/her is to learn React to build a website. A web app sure. But not a website. Instead I would recommend going to the local community college and learn HTML/CSS (and god forbid some WordPress) and while attending community college start forming your tech circle of fellow hopeful web developers and enjoy the journey.
> learn React
IMO that's not the same. Just change Flash for JS, it's still exactly the same technology you would be using when working at a company.
Sure, there's a whole load of ~crap~ tooling built on top of JS to learn too, but I'm sure there was for Flash. It's still the same at its core.
But even so, with things like netlify, expo, etc. creating an interactive web or mobile app is not any more difficult.
In fact, with netlify, I could have a website publicially visible without all the horrible custom web management uis of the past (like cpanel).
If all that is needed is a simple html page, that’s literally minutes of following a few instructions and you are up in running.
Perhaps the problem is that there are so many options now that we have paralysis from too many choices. But the role of the teacher is to find the right tools that enable this easily.
Half the large companies today will present you with a blank screen instead of writing one line of a <noscript> tag.
Load times have remained pretty much flat for the past decade despite page weight and page complexity going up. I think the fact they haven't got worse is a good thing.
Possibly. But if you want to master your craft, you need to learn the “underlying tech.” That’s why we have computer science degrees, after all. Not all programmers have computer science degrees and in many cases, it shows. Someone who understands fundamentals is often more effective at debugging and problem solving when the s* hits the fan.
If you just want to bootcamp it without a deep-dive, that’s fine and I agree with you.
Some programmers do have computer science degrees, and in many cases it doesn't show. In my experience whether or not someone has a computer science degree is a very poor indicator of how good a developer they are.
And it's pretty easy to host some basic HTML/CSS and even easier to just go directly with a blogging platform or something like Square Space.
I might be putting words in GPs mouth, but I read the comments as 'making a swf and embedding it in a HTML file used to be good enough. Now everything is way more complicated'.
I tend to agree with GP. Flash and it's desktop counterparts Delphi etc certainly had their warts but they were much more intuitive on the wetware. Such that accountants and non professional / semipro users could use them.
We made a mistake by throwing them out, when we IMHO should have corrected them or replaced them with less warty programs that we're still using the same paradigm to be easy and intuitive to create.
In the old days, it didn't matter how _good_ you were; basically, your site was going to look more or less like the site created by someone who just started and tried really hard for a few days. You could copy/paste HTML from other people's sites _and just have it_. Now, nothing works because there are tokens and authorization and APIs everywhere.
I don't see anyone complaining that you can't just build a car from scratch in your garage. That would be crazy, right? Yet, somehow, anyone should be able to learn how to code professional internet software with little effort and understanding.
If you want to use React, I don't understand what's so hard about the [introductory documentation](https://reactjs.org/docs/add-react-to-a-website.html)? It's almost pure HTML and has [a lot of help](https://reactjs.org/docs/getting-started.html#try-react) for extending it from there.
This is honestly a lot easier than what we had at the beginning, where even documentation for HTML tags wasn't so easy to find.
Maybe this is still too complicated, but the lower bar is there, whether you like it or not. If I don't know how to use scissors, I'm going to be a shitty barber.
Check this issue: https://github.com/flutter/flutter/issues/11609
Many functional aspects of react can be hard to grok. HOC and currying isn't obvious to everyone.
The surrounding tooling sure is complex af and the little inconsistencies in how everyone does things in the community doesn't help. If the person wants to keep themselves to using a blackbox, they will face problems with react at some point which will force them to learn about how all of this works. React will introduce performance issues that normal js/html/css can easily forget about if you are not careful. Then you will need to learn about lifecycles, debugging tools, and lot of other things simply to make your app not suck.
But you might be too far down the rabbit hole. To use react involves learning a series of things (npm/react/command line). To use Jquery copy 5 lines. It is so easy to get started and so simple to work with.
JQuery is the right choice when you are not managing complexity. When you want a simple powerful abstraction. It's usually the right choice for non-programmers who want to do a few things. It's a good choice for programmers who are not building applications.