Re:Twitter web app now runs ES6+, reducing polyfill bundle s...
by Haydos585x2 on Thursday August 06, 2020 @08:14PM
(#24076732)
I think you'd find most front-end developers don't love reimplementing widgets from scratch but instead are required to because designers, product owners and customers expect this sort of experience. I just don't think Twitter would remain competitive if it had the interface of Hacker News.
Re:Twitter web app now runs ES6+, reducing polyfill bundle s...
by theandrewbailey on Thursday August 06, 2020 @08:31PM
(#24076820)
Tell that to Craigslist.
Re:Twitter web app now runs ES6+, reducing polyfill bundle s...
by itake on Thursday August 06, 2020 @08:54PM
(#24076939)
Craigslist has lost a ton of market share to literally every other company. I haven’t used it in years cuz there are just better products.
Re:Twitter web app now runs ES6+, reducing polyfill bundle s...
by maple3142 on Friday August 07, 2020 @01:31AM
(#24078688)
Or because their requirement aren't just plain text. Browser's builtin controls isn't really customizable, for example you can't change a color of a specific word in a textarea.
Re:Twitter web app now runs ES6+, reducing polyfill bundle s...
by hakfoo on Saturday August 08, 2020 @02:53AM
(#24089651)
I always wondered why we never added any more form control tags. Everything has to be re-engineered as a huge ball of ugly JavaScript.
A <richtextarea> that yielded HTML or even RTF seems like it was an obvious need by time of the end of the Netscape/IE browser wars.
ah yes, because webdevs love reimplementing widgets from scratch. that's no a problem in and of itself, but they also implement it half-assed, so you end up with gems like what OP described, or links being implemented as <a href="#"> with an onclick.