kakuri

Ok but why didn't they do it sooner? The Steam client is terrible and there is no excuse for it.

I've been using VSCode Remote since it came out and it is indeed a godsend. I use it to develop from one trusted machine on my own LAN to another trusted machine on my own LAN and I want the experience to be as similar as possible to developing locally, which it is, and which is why I appreciate it.

I'm not surprised people trying to provide remote code editing to non-trusted clients are freaked out by it, but it is a great tool when operating in a trusted circle.

Notes provided an amazing platform. I think its fatal flaw was that it targeted unskilled developers. The result was a bunch of poorly made applications which were naturally hated by users. Also targeting unskilled developers resulted in a developer experience hostile to skilled software engineers so they went elsewhere.

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 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.

Yeah I'm not finding it compelling to listen to someone's ideas about "taste" when they think that font is tasty.

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.

> 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.

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.