Top
Best
New

Posted by vinhnx 20 hours ago

Why don't more developers “use the platform”?(nolanlawson.com)
272 points | 285 commentspage 5
groundzeros2015 10 hours ago|
Because using a platform requires reading and thinking carefully and occupying the mind of someone else. It means telling business people and designers no. It requires maturity and experience to understand the true cost of custom work.
mathgeek 11 hours ago||
> But for many developers, this sounds like fun! Think of how much you learn as you start building this thing.

I got a good chuckle when my brain finished this sentence with "and promptly forget so that you can learn it all over again years later the next time you need to touch that topic".

singpolyma3 9 hours ago||
> If you search for “sticky positioning” on npm, there’s no package that says “just use CSS position: sticky, you dolt.”

You could maybe find a component that all it does is apply position:sticky though?

littlecranky67 9 hours ago|
Maybe I'm too old, but remember position sticky is relatively "new" and I was around when browsers didn't support it, yet everybody demanded for "affix" solution [0] (the buzzword you would search to find a jquery plugin). Internet Explorer never had position: sticky, and FF only introduced it in 2014. And I dealt with projects until around at least 2017/2018 where enterprise clients would make any webdev required to run on IE12 too.

[0]: https://www.w3schools.com/bootstrap/bootstrap_affix.asp

codeulike 16 hours ago||
Things that are harder to do make your website seem more flashy.

Its like when rounded borders were hard to do without using clever tricks, people would try and add them to their website so that they looked different to everyone else. Once they became easy to do they weren't so desirable.

The equivalent today is wacky scrolling schemes where unusual things happen as you scroll down. Whatever is difficult can be used to distinguish your site.

prmph 12 hours ago|
I deeply detest "wacky scrolling schemes where unusual things happen as you scroll down".

But I guess (some) people without much technical exposure might be impressed by them. My and my strong dislike of the UIs is based on aesthetics mostly, I don't even care to consider the technical horrors behind them.

GoToRO 11 hours ago||
I did. At some point Claude figured out I didn't even check the code and it "minified" the code. Now only Claude can change it. It's a small side project I wanted to do for a long time and now it's Done.
jwsteigerwalt 9 hours ago||
My guess, based on my own and closely observed experiences, is that you can take a developer’s project history and carve out two pretty distinct categories that have huge significance: (1) projects they are most proud of and (2) projects that have the largest value/impact. I know for myself there is very little overlap in those groups.

The former being dominated by bespoke things that worked better than anything available at that time, but filled a tiny niche: “not using the platform”.

While the latter are the boring things that were built with unexciting bulletproof tools that keep churning and adding business value day after day, year after year: “using the platform”.

eviks 18 hours ago||
> The argument is simple: why build something yourself, in JavaScript, when the browser can do it for you?

And when it becomes real, you've got yourself an argument

YmiYugy 16 hours ago||
There have been countless times where I wanted to use some new fangled platform API, but couldn’t because it was buggy/unsupported in one of the browsers or didn’t quite match my use case. It does t help that the platform abandoned some of its efforts to introduce better primitives in favor of higher level APIs.
JSR_FDED 20 hours ago||
It’s funny, the article proceeds to answer the question in great detail: familiarity, level of abstraction, documentation, etc.

I agree with his point that learning to do it yourself can be fun and lead to a flywheel of improvement where the next time you’re faster and the next time faster still.

In the past that was the recipe for success as a developer, nowadays with AI many feel that’s no longer the case.

sodapopcan 20 hours ago|
Extreme apathy towards "learn to do it yourself" is exactly why "AI" is so popular right in programming right now.
TeMPOraL 16 hours ago||
It's not apathy towards "learn to do it yourself", it's apathy towards dealing with the recursive fractal of bullshit that is modern software. It's not 2000s anymore, we have orders of magnitude more of nonsense to learn (ironically, most of it are attempts at repackaging and hiding nonsense from lower layers), and learning that is just a waste of life. LLMs finally give us the option not to.
sodapopcan 4 hours ago|||
Web dev is absolutely a shitshow, but it wasn't necessary to learn all of it to have high paying job. There were plenty of jobs where you could specialize in frontend, backend, infra, data... even subsections of those. And yet a lot of those people still learned the bare minimum they needed. They wouldn't bother to learn the languages they were using every day deeply, and they wouldn't learn their tools deeply (editor, git, etc). I knew plenty of those people. If you were doing true fullstack then you sure, you have a bit of a point, but many people did not, at least at the places I worked.
xigoi 14 hours ago|||
Nothing prevents you from just using the lower layers of abstraction. I have developed a few games using Raylib and it was really fun.
Joker_vD 13 hours ago||
Yeah, except if we're talking about web development, then the lower layers is not Raylib. It's HTML, CSS, JS with its DOM API, plus whatever other bullshit WhatWG throws in.
markbao 17 hours ago|
People will just use the best tool for the job, putting aside some time it takes for practices to propagate.

Native date pickers suck, are ugly, and have no customizability, and look inconsistent between user agents. They don’t even really conform to the OS either (other than iOS). Everyone uses JS. Chrome’s native date picker shipped with a monospaced input font, for crying out loud.

Position sticky is amazing and the behavior is better than what JS can give you. A lot of people use it. Not much UI to make consistent between user agents.

Make the platform actually good and consistent and people will use it. Native APIs are always the better choice if they accomplish your need.

More comments...