4 ms·

Holy shit the amount of overcomplications to serve simple HTML and CSS. Someone really has to justify their job security to be pulling shit like this, or they r

Holy shit the amount of overcomplications to serve simple HTML and CSS. Someone really has to justify their job security to be pulling shit like this, or they really gotta be bored. If anyone can _legitimately_ justify this, please do, I'd love to hear it. And don't go "booohooo at scale" because I work at scale and am 100% not sure what is the problem this is solving that can't just be solved with a simpler solution. Also this isn't "Netflix scale", Tudum is way less popular.

sunrunner 1y ago
> Tudum is way less popular I hadn't even heard of it until today.
- deleted 1y ago
  [deleted]
- moralestapia 1y ago
  I thought the article was about some internal Netflix piece of infra (well ... it is in some way) but it really is some website for some annual event ... wow. This has to be one of the most over-engineered websites out there.
  - yandie 1y ago
    And it’s still slow on my phone (and I’m not a logged in user)
- geodel 1y ago
  You don't know what your are missing :-)
motorest 1y ago
> Holy shit the amount of overcomplications to serve simple HTML and CSS. If you read the overview, Tudum has to support content update events that target individual users and need to be templated. How do you plan on generating said HTML and CSS? If you answer something involving a background job, congratulations you're designing Tudum all over again. Now wait for opinionated drive-by critics to criticize your work as overcomplicated and resume-driven development.
- bonesss 1y ago
  Don’t forget the part where people not even a little exposed to the massive tech infrastructure at hand and local skill pool make WAGs about what us and isn’t cheap. Kafka might seem like extra work compared with not Kafka, but if it’s already setup and running and the entire team is using it elsewhere suddenly it’s free.
- yodon 1y ago
  >How do you plan on... This isn't an engineering problem. It's a PM+Eng Lead failing to talk to each other problem. If you need 20 engineers and exotic text for what should be a simple static site or Wordpress site, you're doing it wrong.
- nchmy 1y ago
  > How do you plan on generating said HTML and CSS? Is this not what SSR html - via any backend language/framework - has been doing since forever?
- solid_fuel 1y ago
  I hear "content update events that target individual users and need to be templated" and immediately rule out any approach involving a background job. - Reddit doesn't use background jobs to render a new home page for every user after every update. - Facebook doesn't use background jobs to render a new feed for every user after every update. - Hacker News doesn't use background jobs to render a new feed for every user after every update. Why? Because we have no guarantee a user will access the site on a particular day, or after a particular content update, so rendering every content update for every user is immediately the wrong approach. It guarantees a lot of work will be thrown away. The sensible way to do this is to render the page on demand, when (and IF) a user requests it. Doing N*M work where N=<# of users> and M=<# of page updates> sure seems like the wrong approach when just doing N work where N=<# of times a user requests a page> is an option. There's lots of less exotic approaches that work great for this basic problem: - Traditional Server-Side Rendering. This approach is so common that basically every language has a framework for this. - Single-Page Applications. If you have a lot of content that only needs updated sometimes, why not do the templating in the users browser? - Maybe just use wordpress? It already supports user accounts and customization.
gf000 1y ago
https://news.ycombinator.com/item?id=44950901 https://news.ycombinator.com/item?id=44950901 My guess
geodel 1y ago
Come on. These guys are Avengers: Infinity war against simplicity.

sunrunner 1y ago

> Tudum is way less popular I hadn't even heard of it until today.

deleted 1y ago
[deleted]
moralestapia 1y ago
I thought the article was about some internal Netflix piece of infra (well ... it is in some way) but it really is some website for some annual event ... wow. This has to be one of the most over-engineered websites out there.
- yandie 1y ago
  And it’s still slow on my phone (and I’m not a logged in user)
geodel 1y ago
You don't know what your are missing :-)

motorest 1y ago

> Holy shit the amount of overcomplications to serve simple HTML and CSS. If you read the overview, Tudum has to support content update events that target individual users and need to be templated. How do you plan on generating said HTML and CSS? If you answer something involving a background job, congratulations you're designing Tudum all over again. Now wait for opinionated drive-by critics to criticize your work as overcomplicated and resume-driven development.

bonesss 1y ago
Don’t forget the part where people not even a little exposed to the massive tech infrastructure at hand and local skill pool make WAGs about what us and isn’t cheap. Kafka might seem like extra work compared with not Kafka, but if it’s already setup and running and the entire team is using it elsewhere suddenly it’s free.
yodon 1y ago
>How do you plan on... This isn't an engineering problem. It's a PM+Eng Lead failing to talk to each other problem. If you need 20 engineers and exotic text for what should be a simple static site or Wordpress site, you're doing it wrong.
nchmy 1y ago
> How do you plan on generating said HTML and CSS? Is this not what SSR html - via any backend language/framework - has been doing since forever?
solid_fuel 1y ago
I hear "content update events that target individual users and need to be templated" and immediately rule out any approach involving a background job. - Reddit doesn't use background jobs to render a new home page for every user after every update. - Facebook doesn't use background jobs to render a new feed for every user after every update. - Hacker News doesn't use background jobs to render a new feed for every user after every update. Why? Because we have no guarantee a user will access the site on a particular day, or after a particular content update, so rendering every content update for every user is immediately the wrong approach. It guarantees a lot of work will be thrown away. The sensible way to do this is to render the page on demand, when (and IF) a user requests it. Doing N*M work where N=<# of users> and M=<# of page updates> sure seems like the wrong approach when just doing N work where N=<# of times a user requests a page> is an option. There's lots of less exotic approaches that work great for this basic problem: - Traditional Server-Side Rendering. This approach is so common that basically every language has a framework for this. - Single-Page Applications. If you have a lot of content that only needs updated sometimes, why not do the templating in the users browser? - Maybe just use wordpress? It already supports user accounts and customization.

gf000 1y ago

https://news.ycombinator.com/item?id=44950901 https://news.ycombinator.com/item?id=44950901 My guess

geodel 1y ago

Come on. These guys are Avengers: Infinity war against simplicity.