HOT TAKE
FRONT END DEVELOPERS SHOULD BE BANNED FROM USING THEIR HARDWARE FOR A MONTH EACH YEAR AND INSTEAD GIVEN A LOW END 10 YEARS OLD NETBOOK
HOT TAKE FRONT END DEVELOPERS SHOULD BE BANNED FROM USING THEIR HARDWARE FOR A MONTH EACH YEAR AND INSTEAD GIVEN A LOW END 10 YEARS OLD NETBOOK 130 comments
@ianrogers @systemz @halva I'd imagine we'd have "CSS framework" baggage to replace all the junky js Framework baggage ;o) @halva@wetdry.world I am a professional software developer and I work on a Thinkpad released in 2008. @halva@wetdry.world 10 year old netbook? cmon, do better. i use a 15 year old laptop most days (although its higher end than "netbook"). at least force frontend devs to make software that supports opengl version "fucking ancient lol only vlc runs on this" @halva already using a 10 year old netbook but developing extremely bloated frontends anyways mwahahaha :blobcatevil: /s @halva @halva I love this. I actually keep around a dual core Celeron laptop around for this purpose. If my web app is too painfully slow on that, I've got work to do @halva@wetdry.world reminds me of a 10 year old laptop review that was using up to date windows 11, and windows + edge itself crashed and froze multiple times but ran high end benchmarks without freezing or crashing (albeit at the worst score imaginable.) @halva frontend programmers should get 10 year old laptops, and city planners should not be allowed to drive
@halva Hotter take -- they should do this while using cellphone-tethered internet while riding the subway of the closest major city that has one. @wordshaper @halva https://infrequently.org/2024/01/performance-inequality-gap-2024/ has pretty decent suggestions @halva I wouldn't even suggest this is controversial. When developing an application, I get having a powerful computer to compile that code, but testing should happen on lower-end equipment. It's called meeting people where they are. If the experience is bad for the majority of people because your frontend requires too much oomph, nobody will want to use your app. @halva THIS FRONT END DEVELOPER USED A 15 YEARS OLD COMPUTER FOR TWO YEARS AND KNOWS HOW BAD NODEJS AND MODERN WEBSITES ARE. My website is mostlystatic with a bit of optional JS for some interactivity. https://jak2k.schwanenberg.name/ @halva alternative: Living in some areas in germany. Afterwards one might think differently about offline first 😁 @halva another month will be "Did You Think Everyone Preorders The New iPhone, Greg?" month, where they must live using a five year old Android handset on a metered data plan. Trust me: the experience will be eye-opening. @halva Also proposing "Did You Think Your Grandmother Wears Those Glasses For *Fun*?" week, where the designer must use their hardware (computer, phone, tablet, shit probably their TV now) at the lowest resolution / highest system font size selectable. If you're lucky your app still *functions,* many won't even render correctly! @halva + mouse removal. Every time enter or space does not perform a button action, every time TAB cannot move me from object to object, a disabled user is told their motility restrictions render them unwelcome. Source: it me, i am the unwelcome one. @halva I want to give all mobile developers a Galaxy S5 running the latest LineageOS build @halva And OS and productivity software developers should be using 5-10 year old mid-tier computers at best. @halva developing any kind of software on older hardware only has benefits. The performance target is much more strict then, with big focus on optimization and compatibility. And old hardware is a lot cheaper. @halva but they install anydesk and make a connection to a userland linux on there phone. Oh wait frontend.... @halva they should also have to test their interfaces among users of age 60, 70, and 80. @halva its 13 year old netbooks btw. I know because i have one running his business for the next 5 years. @halva Then once I'm in, the whole UI feels a bit sluggish. This is all on a Pixel 8 btw. On my older tablet, I can't even the read the textbook without giving up due to frustration. @halva@wetdry.world i5 5200U my old belo... well not beloved @halva Go work in big corporate, you'll probably have that exact setup by default & be forced to use IE. @halva Moreover, frontend developers in major cities must have their internet throttled @chris__martin @halva Throttled down to 33.6k because if the phone lines are bad, you're not getting near 56k Lol that would be a 4 year upgrade over the low-end netbook from 2010 :-) (But I am not doing frontend, though…) @halva I'm using a 1 year old chromium-based browser with network restricted to fast 3g and cpu slowed down 6x restricted to a single thread. . If I'm concerned about the speed of my product. @halva completely agree!!! I’ve said before that all devs should have to work on decade-old hardware for some portion of each year. Tools would improve, and so would products! so, I'm a release engineer, not a developer. I have my own opinions along these lines. but on this particular topic, I'll note that it's the user interface limitations that are topical in the OP and you want the frontend devs becuase PMs & CEOs are not going to be empathetic enough to wrap their heads around of a 10yr old's needs in the UI. and if you interpret the OP to mean the NOTEBOOK is 10yrs old, the PMs & CEOs will say it's great to drive purchase of replacement device. now we get into the release engineer part of the opinion. everyone seems to think that releasing apps & adding junk to them & unnecessary features & wrapping an entire damned browser in every last one is the bomb diggity but y'know what there is nobody on this planet wants their phone updating every other day with a binary that eats the entirety of the low bandwidth connection they share with their family it's the same idea: devs have amazing fast connections & hardware I do too and yeah, who is going to maintain a lab with old, slow stuff? but that doesn't mean it's not a problem Thanks to a power cut I've been using a years-old ThinkPad W540 instead of my usual machine (a recent Ryzen desktop). Electron apps are notably sluggish, and I can type faster than Slack's Web interface and render. It's why I code front end on an HP business machine. They just suck in general, so if it works there it should be good always @halva Same with browser. First thing I was told when working in a web company: "Please only use Chrome for development". Outside of work I test my hobby web pages in Firefox and Epiphany etc. It's not easy to design and implement for many environments, but you're a frontend WEB engineer, you are to anticipate diversity. @halva especially desktop guys..... Im looking at you KDE and GNOME devs @halva I disagree, but only because I think it should be applied 12 months out of the year! @halva@wetdry.world another month where their network connection is limited to 56k modem speeds. @halva Honestly, why stop at that, just give the front end devs a core 2 duo ( or a similarly perforant SBC) to do their work on, but with a normal screen and keyboard, since destroying their ergonomics is not the goal here, and force them to test their visual changes at a variety of window sizes. |
@halva no whyyyyyyyyyyy :neocat_sob: