Hacker News new | ask | show | jobs
by landerwust 2030 days ago
Totally loving this. Did you reverse engineer the layouts from screenshots? Please tell me somewhere there is a snippet of original HTML snarfed from archive.org :)

Finally you're totally missing a beat here -- MySpace lived and died by its community of indie bands. Ditch that dodgy mainstream iTunes Music wrapper and make the actual music function work again. You never know, you might strike a nostalgic retro chord within some niche of the indie community (and definitely that's where this thing should be shared!)

1 comments

Hey, I'm An, the creator of SpaceHey! Thank you!! Yes, I looked at a ton of old screenshots, wikipedia sites and archive.org pages! That's how I designed most of it! I'm currently looking into all of the legal stuff which comes with music sharing, but a dedicated music feature is definitely planned! The iTunes API is just a temporary thing to fill it with some content!
Do a soundcloud integration like poolside fm did
Yes this is a good point - people with music to share will probably have it on Soundcloud or Bandcamp already, just add Soundcloud/Bandcamp embedding and you're all set
What tech stack did you end up using for the backend?
for it to be legitimate you need to use ColdFusion and then do a half assed port to .net.
My wife worked there for the transition. Her very first .net page was the MySpace homepage (which was demoed by Steve Ballmer at CES, iirc). Microsoft was very unhappy with the decision to retain the .cf extension on web pages even after the transition to .net. There were some crazy levels of scaling happening behind the scenes—they had database requirements beyond the capabilities of sql server and there was code on the server side to route to different sql clusters based on the user's numeric id. They also had more page views than they could sell ads for. There was actually a pretty crazed level of new feature development happening at the same time—any time that friendster or some other site would release a new feature, Tom would insist that it be implemented on MySpace right away. At the same time, he was also requiring things like pixel-for-pixel identical output for existing pages/features through all of this.
> to route to different sql clusters

That's called sharding and is pretty widely used nowadays. There is even readily available middleware that handles this for you, so no need to put it into the backend.

Keep in mind this is more than a decade ago. Sharding was almost certainly state-of-the-art and exotic back then (hell, it's arguably pretty unusual in the wild even today, even if a lot more mature of a concept).
IIRC, this was actually a step beyond the sharding that MS SQL supported. They were really the first people to do big data.
> At the same time, he was also requiring things like pixel-for-pixel identical output for existing pages/features through all of this.

Break middle-school students' copypasta CSS rules for animated GIF backgrounds at your peril.

I was at a CF conference with MySpace as a speaker and they talked about how often they went down but that they were switching to another CF engine with .net capabilities (BlueDragon). Their discussions and jokes about instability and going down due to bad code updates were really cringy and gave the impression that their platform was a mess.
Pretty certain we were at the same conference. There development practices horrified the group I was with in the audience. At a time that a new competitor appeared (Facebook) they made the fatal mistake of rewriting their software in dot Net. No new features for a year or more. Joel Spolsky wrote a pretty famous essay about the wisdom of doing that.

https://www.joelonsoftware.com/2000/04/06/things-you-should-...

Performance was the feature. Friendster should have been social network of that era but they couldn’t scale and had to shutdown new user registration. Same thing happened to Twitter but they had no competitor in short form social networking.
Thanks for this one, it encapsulates a feeling I've had for a while but could never verablize so well.
I live by that blog post.
I had an older friend that worked at CF when I was a teenager. He taught me a bit about relational databases and some other important stuff as he was one of the only developers I knew growing up.

I remember him telling me how I was wasting my time building in php/MySQL since CF was the future and serious companies wouldn't be looking for php developers. Glad I never pulled the trigger and bought their expensive IDE.

No expensive IDE was necessary and there are open source servers now. Regardless, you made the right choice.
For proper early 2000s nostalgia, I reckon the backend should actually be Apache mod_perl, with the ".cfm" extension script aliased to Perl CGI scripts because management tell everybody "it's running on Adobe!"...
Aah yes, mod_perl. That brings back memories.
If you had enough rack space, mod_perl+Apache2 could scale to anything you needed. Hundreds of Gbps, hundreds of thousands of RPS. Inefficient, sure, but seriously flexible+performant and really easy to deploy. I miss the old stacks, as Nginx and the other httpds really suck in comparison (feature-wise) and Java is still such a huge PITA. I'd honestly rather use modern PHP than today's Java webapps.
<cfdump var="bad_memories"/>
Hilariously, ColdFusion strikes again. I should have used pound signs around the bad_memories variable. The above code would dump the string "bad_memories".

Corrected:

<cfdump var="#bad_memories#"/>

<cfdump var="#bad_memories#"/>

I don't believe that /> is needed anymore. You can just use >

I unfortunately work with coldfusion/cmfl on a daily basis at my company. I am moving the servers over to Lucee from Coldfusion 10 and trying to have any new systems built on C#/.net. The most difficult part is getting other people on board. My manager is fine with what I am doing. He saids he is too old to learn a new language so myself and the other programmer will have to support anything I built in .net

Let me tell you folks. Writing spaghetti code with no separation of concerns and no version control is not exclusive to php

I still can't believe someone came up with this syntax and thought it was a good idea.
How about the Dragon Hoard? Files are hosted on Archive.org, and have been for a year and a half without being taken down.

https://news.ycombinator.com/item?id=19569865