1993 seems very unlikely?
I'm a fucking webmaster (2016)
161–170 of 229 posts
Re: I'm a fucking webmaster (2016)
#162Earlier quoted context omitted.
This does indeed work fine. The major problem is still finding somewhere to host it, and incurring the still non-trivial risks thereto, since among the many things students want to do with free web space, hosting warez and other things that will get you in trouble quickly is still pretty far up the list. Plus someone has to pay for a domain name or something. If you can get a modern text editor that can use SSH or so…
Huh? Just use neocities.org. Even has a built-in editor on the site.
Re: I'm a fucking webmaster (2016)
#163Earlier quoted context omitted.
What do you believe web3 is?
I believe it's what the spider drawn by David Thorne produces: https://27bslash6.com/overdue.html Ironic that payment via random drawings became a "reality" in this crazy world after all.
Re: I'm a fucking webmaster (2016)
#164My 1996 self feels very seen. I think a lot about the way the web was back in the mid 90s, compared to the bleeding-edge technologies of today, particularly blockchain and cryptocurrency. And one major aspect I keep coming back to is that web technologies in the 90s, and even their descendent technologies now, are simple enough for most technology-literate people to understand, and that carried with it a lot of comfo…
> Why is Hacker News so anti-crypto? I have missed the discussion you have mentioned. But I remember 10 years ago HN was opposite to anti-crypto. And the anticryptoness of nowadays for me seems like stupid ppl who don't understand some basic principles and downvote me if attempting to criticize their misunderstanding.
Re: I'm a fucking webmaster (2016)
#165Back in the early 2000's, I taught "computers" to a bunch of kids in DC. I first started off with how a computer work; IO, CPU, storage and their eyes glazed over. I quickly ditched that topic and went right to building a web page. Taught them a few HTML tags and they instantly became "webmasters". They were so thrilled. They could create blinking text, could make all the fonts pink. All just by moving around some si…
My first experience of programming was walking up to an Apple II in grade school (this was in the 2000s, those were some old machines) and punching in code listing from a book. The machines didn't do anything when you powered them on, just waited for you to enter code or commands. It was so simple, and it just begged you to start writing programs. Now people talk about getting their kids started with programming, and…
I am reminded of the old Kids React videos (which themselves are now nearly a decade old)... Kids React to Technology (an old Apple ][+) https://youtu.be/PF7EpEnglgk
Re: I'm a fucking webmaster (2016)
#166I really wish I could experience the web back then at 1993 (I'm 25). I imagine much faster, and intuitive websites than nowadays. Beautiful UX is one thing but making a website feels natural, that's what I think the internet is missing today.
It was an easier time back then.
Re: I'm a fucking webmaster (2016)
#167Earlier quoted context omitted.
You can still just use HTML.
This does indeed work fine. The major problem is still finding somewhere to host it, and incurring the still non-trivial risks thereto, since among the many things students want to do with free web space, hosting warez and other things that will get you in trouble quickly is still pretty far up the list. Plus someone has to pay for a domain name or something. If you can get a modern text editor that can use SSH or so…
Re: I'm a fucking webmaster (2016)
#168Re: I'm a fucking webmaster (2016)
#169Back in the early 2000's, I taught "computers" to a bunch of kids in DC. I first started off with how a computer work; IO, CPU, storage and their eyes glazed over. I quickly ditched that topic and went right to building a web page. Taught them a few HTML tags and they instantly became "webmasters". They were so thrilled. They could create blinking text, could make all the fonts pink. All just by moving around some si…
Create an HTML file and open it up in the browser without a web server (though some advanced stuff will need a web server running). The developer tools built into the browser can be used to interact with the page and see how changing HTML, CSS, or JavaScript affects it.
Web console can be used to experiment with JavaScript, https://firefox-source-docs.mozilla.org/devtools-user/web_co...