Earlier quoted context omitted.
I dunno, I thought part of Facebook's instant success was because, with the exception of wilfully-obtuse student columnists, most students instantly "got" it because they'd had some sort of internet profile and compulsively-updated statuses since their parents had finally succumbed to the avalanche of AOL CDs in 1997. Even the university, moving at such glacial pace it still ran a nineties Windows NT, was trying to g…
The original Facebook didn't have a status to update; that didn't come until around late 2007 or early 2008. There was no chat until that time as well, just "poke." In 2004 it still managed to be "social" for its time though, especially with its focus on a campus. For a very long time Facebook was just mostly static pages with a list of friends and a "wall" your friends could write on, and maybe, IIRC, photo upload.…
TheFacebook.com’s darker side (2004)
51–60 of 141 posts
Re: TheFacebook.com’s darker side (2004)
#52Earlier quoted context omitted.
Pure HTML y'all. No megabytes of css, no bootstrap, no webpack with plethora of dependencies to load, parse and execute. We went the other route.
which is odd since a lot of css "frameworks" are now back to promoting inline css. https://acss.io/ I like this idea, but I wonder how long it would take my brain to think like this.
I feel like new people keep entering the web field and forgetting all the lessons learned from the (very very recent) past.
The inline approach might work for a small site. But in that case, why use a pre-processor at all and why would you need config objects?
CSS doesn't need to be rocket science. If you want atomic CSS then leverage CSS and style the base elements, it's actually pretty good at what it does.
Edit: I may have misinterpreted it's use case, I am all for compenent based styles. I still think there is no need for a pre-processor of inline styles with a completely new lexicon. If you are already in the context of a component you already have the beauty of a scoped and simplified CSS workspace, why make that so much more complicated with a new build pipeline and completely new syntax and lexicon?
Re: TheFacebook.com’s darker side (2004)
#53Earlier quoted context omitted.
What do you mean? According to WHO, measles caused 2.6 million deaths a year before 1980, but only 134 200 in 2015. Polio dropped from 350 000 cases in 1988 to 74 in 2015.
I think he was making a passing joke at the anti-vax crowd
Re: TheFacebook.com’s darker side (2004)
#54Re: TheFacebook.com’s darker side (2004)
#55Re: TheFacebook.com’s darker side (2004)
#56Jesus christ. It's so hard to believe that's only from 2004. I feel like that era transpired 40 years ago. The period of time before smartphones feels like it happened in the 1970's to me. The difference between 2000 and 2015 is so absurdly radical it begs disbelief.
Now that you put it that way, man... things have changed. I can't help thinking about further back, too. Just imagine how it felt to live around the turn of last century! Planes, [newer] trains, and automobiles! Electricity, plumbing, underground subway transportation. Hygienic medicine. Vaccines. Telegraphs reaching out overseas and powering thousands of morning daily papers; becoming a commodity instead of luxury.…
Re: TheFacebook.com’s darker side (2004)
#57Jesus christ. It's so hard to believe that's only from 2004. I feel like that era transpired 40 years ago. The period of time before smartphones feels like it happened in the 1970's to me. The difference between 2000 and 2015 is so absurdly radical it begs disbelief.
>The difference between 2000 and 2015 is so absurdly radical it begs disbelief. The first movie I watched on my GearVR headset was called Strange Days, a 1995 film rather aptly about the introduction of Virtual Reality and how the government is involved in all sorts of dirty cover-ups. The movie was terribawesome, but it was amusing to see what 90's ideas of the future were getting right and wrong. Though, the time b…
Written by James Cameron and directed by his then-wife Kathryn Bigelow. It's such a great movie. And has a great track by Peter Gabriel at the end as well!
Re: TheFacebook.com’s darker side (2004)
#58Jesus christ. It's so hard to believe that's only from 2004. I feel like that era transpired 40 years ago. The period of time before smartphones feels like it happened in the 1970's to me. The difference between 2000 and 2015 is so absurdly radical it begs disbelief.
> It's so hard to believe that's only from 2004. It's surprising Holt could still get away with writing "Cornell girls are hideous" as late as 2004!
Re: TheFacebook.com’s darker side (2004)
#59Earlier quoted context omitted.
I dunno, I thought part of Facebook's instant success was because, with the exception of wilfully-obtuse student columnists, most students instantly "got" it because they'd had some sort of internet profile and compulsively-updated statuses since their parents had finally succumbed to the avalanche of AOL CDs in 1997. Even the university, moving at such glacial pace it still ran a nineties Windows NT, was trying to g…
The original Facebook didn't have a status to update; that didn't come until around late 2007 or early 2008. There was no chat until that time as well, just "poke." In 2004 it still managed to be "social" for its time though, especially with its focus on a campus. For a very long time Facebook was just mostly static pages with a list of friends and a "wall" your friends could write on, and maybe, IIRC, photo upload.…
there was one screen where you could check on who's online, then you'd write on their wall
Re: TheFacebook.com’s darker side (2004)
#60Earlier quoted context omitted.
Pure HTML y'all. No megabytes of css, no bootstrap, no webpack with plethora of dependencies to load, parse and execute. We went the other route.
Why the drive-by attacks on good tools? This kind of stuff is tiring and just adds to the noise. > No megabytes of css Why would there ever be megabytes of CSS for such a site, apart from for ads, which is the main problem with modern 'content sites'. > no bootstrap Bootstrap can be tiny, and a big win in productivity/quality, so 'no Bootstrap' likely cost the devs in its lack of availabilty at the time. It looks far…
To be fair, there really wasn't any "mobile" to speak of back then, so the developers couldn't even try to make it look good on mobile.