but, if it's trying to respond in a natural way, with interruptions in both directions, it may still be a good idea. if there's a delay between you stopping and it starting talking, it feels weird

(you might be able to fake some of that on the client, but then you need a thicker client)

sucks for people that use issues/PRs for coordination and had a planning meeting scheduled, though

maybe if it was larger, thicker, and a more dense material. most of those matter more to the person holding it, rather than an observer, though

the big one is immediate mode UIs, which casey popularized back in 2005. Unity's editor uses it to this day, and if you do editor scripting, you'll be using it. for in-game UI, they switched to a component-based one, which also somewhat aligns with casey's opinions. and they shipped DOTS, which aligns even more with what he's saying

i think his lack of shipping is mostly because he switched to teaching and has absolutely no pressure to ship, rather than his approach being bad

might have to try it with AR glasses. but, the screen is bright enough that it's usable outdoors anyway

i've been using copilot with voice input, with a bit of on-screen keyboard usage when it's not cooperating. i'm mostly giving it fairly simple edit instructions ("write a for loop at line 50"), rather than full on vibe coding, and it's working much better than i expected

i'm not using emacs/vim, because the steam keyboard doesn't have a ctrl key, and i have to use a less ergonomic kde on-screen keyboard to push it (and i'm a heathen that prefers vscode anyway)

a lot of junior eng tasks don't really help you become a senior engineer. someone needs to make a form and a backend API for it to talk to, because it's a business need. but doing 50 of those doesn't really impart a lot of wisdom

same with writing tests. you'll probably get faster at writing tests, but that's about it. knowing that you need the tests, and what kinds of things might go wrong, is the senior engineer skill

with the LLMs current ability to help people research a topic, and their growing ability to write functioning code, my hunch is that people with the time to spare can learn senior engineer skills while bypassing being a junior engineer

convincing management of that is another story, though. if you can't afford to do unpaid self-directed study, it's probably going to be a bumpy road until industry figures out how to not eat the seed corn

it's not clear to me that an ad monopoly makes products cost more, even without getting into ads distracting the whole workforce

you'd probably want the rest of the programs, too. bash isn't too useful on its own. you can also find those on the same website

edit: even a steam deck is somehow less distracting than a phone, despite distraction being one of its main purposes

you generally need a stable IP, and a firewall that'll let people initiate connections from outside your house

there's iroh, which looks like a nice balance of batteries included, and not a bunch of bloat

and pkarr, which does exactly one thing: maps ed25519 keys to DNS records via bittorrent's DHT

i think the big blocker for wider adoption is that browsers, ISPs, and airport wifi are all hostile to general purpose network protocols. you're mostly stuck with TCP, or the quagmire of WebRTC right now. (iroh works in the browser, but it has to go through a relay)

so, it might make sense for US companies selling to US customers, if they can find suppliers. but even in the cases where it works for that market, multinational companies might prefer a "made in taiwan" or "made in mexico" sticker, or they might prefer to leave the sticker off

like, if it decides to a table of contents, or chapter summaries, rather than just diving in at page 1