Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A framework that makes things worse on purpose

postmodernize.telnet.asia

Post reply on HN
Print view View original

41–50 of 60 posts

Re: A framework that makes things worse on purpose

#41

Post by ratww »

Tade0 wrote: post #22
ratww wrote: post #19

Earlier quoted context omitted.

What tech do you use? Also which kind of app is it? Does it have some special feature that causes the code bloat, or is it just lots of screens?

Just Angular 10 and associated libraries. The app itself is a run-of-the-mill "tables, details and forms" SPA, but there are indeed a lot of screens. I see no reason why something like this should take so much space, but here we are.

Ah, gotcha! Thanks for answering.

I've seen similar situations before. In my case it was mostly due to having a team that is larger than than necessary. Having multiple UI designers with differing opinions, developers that don't question redundancy in UI (or don't have time to check), managers that don't coordinate, and just communication problems in general.

This led to a lot of reimplementation and duplicate code. In the end they changed the frontend framework a couple times, but the issue started creeping up again.

Re: A framework that makes things worse on purpose

#42

Post by nucleardog »

Zelphyr wrote: post #15
ArchIsGreat wrote: post #2

Sometimes I wonder what the point of those web frameworks are. I find them harder to use than plain HTML/CSS/JS.

Part of the downvotes to your comment may be coming from the fact that this framework is (I'm assuming?) a joke. Otherwise, I completely agree with you. The last few projects I've worked on I used vanilla HTML/CSS/JS and I found it so much better than using any of the popular front-end frameworks. I didn't have megabytes of dependencies before a single line of production code was written. I didn't have to spend time…

Honestly this stuff all just makes me feel really old.

In a past life that wasn't even that far away, I implemented single page sites with smooth transitions and all sorts of fun stuff in a few lines of CSS. There was like 1kB of JS thrown on top to add a bit of "nice to have" functionality.

I implemented an entire clone of Flappy Bird in like 50kB. The bulk of that was a polyfill so it worked on IE8.

I implemented a curling game that would open up a webcam in the background and continuously capture and process images to try and detect shapes you'd drawn on paper. When it detected one it would trace the shape and decompose it into a convex shape as that's all the physics engine supported, then render this on a 65" touchscreen coffee table and let you curl with your custom shaped rock with realistically calculated physics including an appropriate density for your curling rock based on the volume of the same you'd created. It would calculate scoring and use websockets to communicate that to another device which was hooked up to a TV that displayed a leaderboard. This was all in about 500kB, and the bulk of that was the physics engine (what could've been a "computer vision" library was like a kilobyte of vanilla JS). There was no effort made to prune unused code or anything because it was never loaded over the network or required to be optimized for load times and I only had a week to build it.

I honestly cannot even begin to comprehend how we're shipping static websites with 1MB+ of JS. Damn kids, get off my lawn.

Re: A framework that makes things worse on purpose

#43

Post by austincheney »

polka_haunts_us wrote: post #4

Making it look like you're doing things poorly when you're doing exactly what you intend to do is a real skill. It's the basis of a lot of circus acts. Making your files extremely large to mock modern web dev is maybe a little bit esoteric of a joke to be compared to someone pretending like they can't control a unicycle though. What this comparison says about modern web dev I'll leave as an exercise to the reader.

It’s all a matter of perspective. When I saw the title I immediately thought Angular JS.

Many, possibly most, UX developers cannot actually do their jobs. Instead they are hired to use some crappy framework to outsource the required competency. For many of these people dependency on some bullshit framework is the expected reality and anything different must then be poor execution... all objective metrics aside.

Re: A framework that makes things worse on purpose

#44

Post by StavrosK »

isaacimagine wrote: post #32
thunderbong wrote: post #30

Earlier quoted context omitted.

What? You mean it's not been maintained and there is no latest version? I've been using this on many of my sites, which I'm sure now is full of security holes and will break in modern (or ancient) browsers. Please someone suggest an alternative.

I personally use http://nojs.io/

It only has 103 stars on Github, can't be that good.

Re: A framework that makes things worse on purpose

#46

Post by chasd00 »

durnygbur wrote: post #35
winrid wrote: post #34

I recently tried to make as terrible of an app backend as possible: https://github.com/winrid/terrible-express-app Challenge: figure out how it starts, and how content is rendered. (It's not that hard, but a little funny)

Love the .idea directory in the repository (despite large .gitignore) and how you lie about package-lock.json. PwC, or Accenture would charge 5mln EUR for it and be perfectly self-confident about it.

Yeah and at Accenture there would be one person in the whole company that knows anything about the internals. Oh, and they left the firm 3 months ago.

Re: A framework that makes things worse on purpose

#47

Post by hestefisk »

spacemanmatt wrote: post #29

Good times. I used to replace .jsp with .aspx at the reverse-proxy.

Back in t get late 90ies I wrote my markup in XML and be then used mod_perl to transform it to XHTML using XSLT on the fly. But to be extra 1337, I renamed my index.html file to index.xml,

Re: A framework that makes things worse on purpose

#48

Post by hestefisk »

hestefisk wrote: post #47
spacemanmatt wrote: post #29

Good times. I used to replace .jsp with .aspx at the reverse-proxy.

Back in t get late 90ies I wrote my markup in XML and be then used mod_perl to transform it to XHTML using XSLT on the fly. But to be extra 1337, I renamed my index.html file to index.xml,

Btw the mod_perl XML server was called AxKit. I don’t think anyone even remembers it.

Re: A framework that makes things worse on purpose

#49

Post by spacemanmatt »

hestefisk wrote: post #47
spacemanmatt wrote: post #29

Good times. I used to replace .jsp with .aspx at the reverse-proxy.

Back in t get late 90ies I wrote my markup in XML and be then used mod_perl to transform it to XHTML using XSLT on the fly. But to be extra 1337, I renamed my index.html file to index.xml,

I contributed to a monstrosity based on Xalan and XSLT at runtime. What a beast. I don't know how we planned to support 5 concurrent users.

Re: A framework that makes things worse on purpose

#50

Post by krylon »

hestefisk wrote: post #48
hestefisk wrote: post #47

Earlier quoted context omitted.

Back in t get late 90ies I wrote my markup in XML and be then used mod_perl to transform it to XHTML using XSLT on the fly. But to be extra 1337, I renamed my index.html file to index.xml,

Btw the mod_perl XML server was called AxKit. I don’t think anyone even remembers it.

I do remember the name, but I never used it or got into direct contact with it.
Post reply on HN