I am a frontend dev and use Firefox as much as I can. But I can't use it for development. Firefox's dev tools need to be better. I use Chrome for development because Chrome has great dev tools.
I've used Firefox as my daily driver for years on a high end gaming laptop and have the same gripe. The dev tools are truly bad. Even outside of dev work, there's sites where I want to hide paywall or login banners by simply setting a container to "display: none;", but opening up the inspector (slow) and doing so causes the browser to freeze.
The name is in keeping with a lineage of animal tools for ad hoc page manipulation in Firefox. First was Aardvark, then Platypus. https://github.com/dvogel/AardvarkDuex
I was an original early user of Aardvark. These tools have remained obscure, but with a cult following because they’re such a quick and easy way to rip up a page to your liking. They were the direct inspiration for modern browser dom selector tools.
For hairy edge cases, uBlock Origin’s element picker is the gold standard for manipulating pages.
I've been trying to use GIMP for years (since Corel destroyed Pain Shop Pro). I don't do a lot of photo manipulation so I don't put in a lot of time learning. PSP had a UI that was discoverable for an amateur occasional user. GIMP has a UI that is completely inscrutable. +1 for Photopea, it has become my go-to.
If you are having problems with Windows RDP then the problem is somewhere else along the pipeline, not RDP itself. No other remote solution I've used is even in the same ballpark as RDP in terms of responsiveness and quality. RDP on a LAN is very usable for actual coding work.
Keep in mind that many (most? all?) LLMs are not trained strictly on factual data, and are probably not trained to differentiate between factual and non-factual information. If you ask an absurd question you will likely get a (delightfully) absurd answer. If you ask a question somewhere in the borders between reality and fiction... results may vary.
I interviewed for a software engineering position at USAA. After seeing the incompetence of the interviewers none of the nonsense they do surprises me.
> But, they still use proprietary TOTP from Symantec which is annoying.
They at least used to, but I'm not sure they still do.
(And when they did, I was able to copy the key into a MFA app of my choice.)
But now as an end-user, it's all built in to their own banking app. I don't use the code from the app though, because I just use my personal 4 digit pin (after entering in my unique password from my password manager).
Yeah I've never worked there, but been a customer since 2005. For many years there, USAA was really cutting edge of tech and highly competent. The system has slowly gotten a little less usable though, but at least it still works most of the time
> I’ve said this before, but Apple is forcing third party devs to be in service of Apple
I got my first taste of computers on early 90's Macs and was enchanted. Within a year I discovered DOS, Windows - and freedom. I did tech support for both Mac and Windows computers for several years. It's always been abundantly clear that the Empire of Mac exists for its own glorification (and obscene profits) - customers, developers, partners - they are all in service of Apple. It's unfortunate that Apple does some things with unparalleled quality and maintains a loyal following, because the apple has always been rotten at its core.
I loved Chrome's debugger for years, then build tools and React ruined debugging for me.
Built code largely works with source maps, but it fails often enough, and in bizarre ways, that my workflow has simply gone back to console logs.
React's frequent re-renders have also made breakpoints very unpleasant - I'd rather just look at the results of console logs.
Are there ways I can learn to continue enjoying the debugger with TS+React? It is still occasionally useful and I'm glad its there, but I have reverted to defaulting to console logs.
I find myself doing a mix of both. Source maps are good enough most of the time, I haven't seen the bizarre failures you're seeing - maybe your bundling configuration needs some tweaking? But yes, the frequent re-renders are obnoxious. In those cases logging is generally better.
Conditional breakpoints help alleviate the pain when there are frequent re-renders. Generally you can pinpoint a specific value that you're looking for and only pause when that condition is satisfied. Setting watch expressions helps a lot too.
Console logs in the browser have some unique advantages. You can assign the output to a variable, play with it etc.
But yes, any code that is inside jsx generally sucks to debug with standard tooling. There are browser plugins that help you inspect the react ui tree though.
My thoughts exactly. JSX provides the best templating syntax I have seen - it's just JS, and it uses curly braces to delineate JS. Putting JS, or worse, custom syntax in strings is terrible, and every other delineator choice is less idiomatic and uglier than curly braces.
