I don't think that's the case. This is from anomalyco, the company who made sst.dev. Crush is from Charm. I think OpenCode may have originally been written in Go but nowadays their codebase is TypeScript.
Edit: I'm missing some context others have pointed out.
I figured Slack referred to slack in task time estimation i.e. the amount of extra time allowed in a task. Collaborating on Slack would count towards that time.
Personally, I think the worst possible use case is the one that's being pushed for; personalised agents.
I think a much better use case is one where it's not visible to the user at all, like spam filtering or helping an accountant do their monthly run in a few hours rather than a day. To me, that's likely a much better use of AI than trying to shove a chat interface or agent harness into an existing app.
That being said though, I did see a startup in my area basically offering a Resend/Mailchimp competitor as a Claude plugin, so maybe it'll just be integrations to their existing chat interface.
I've always struggled with doing basic life stuff. Paying bills on time. Remembering birthdays and to buy presents. Doctor appointments. Setting up play dates for the kids. Getting my teeth cleaned regularly. Booking in vaccines for the kids. Renewing passports. Booking flights. Etc. It feels like so much of my life is consumed by this useless administrative bullshit. I LONG for personal agents which take away all this friction from my life so I can focus on the things I love: my family and my hobbies. A personal agent will revolutionise my life in a way no other technology has.
At the expense of your privacy, potentially acting irrationally on your behalf, with the inherent weakness of being able to be prompt injected. All of that is not even to mention the grey area of who is responsible when your agent breaks the law.
These aren't hypothetical, and in the hands of non-technical users let alone technical users, they have are far too unpredictable.
A technical person (such as yourself, presumably) can make an informed tradeoff, but a non-technical person i.e. the general public as OP described just sees it as a black box that makes purchases and appointments, and then gets surprised when their bank details end up in Slack[0], hacks a local gym[1] or the agent sends a stranger their address[2].
It's better in just about every way, and if you have a copy of TA (such as from GOG), you can load the soundtrack from TA into BAR's music folder and it'll change the soundtrack to the TA soundtrack.
It's very sad. I was excited about Deno from day one, and I wanted to see it succeed.
Deno's ability to run TypeScript files - stripping types - was arguably implemented in Node because of Deno. The consolidated tooling approach was a good attempt at solving tooling fragmentation that Node suffers from.
I think for Deno to succeed, it would've had to have been under a non-profit and maybe that can still happen.
It would certainly be nice if someone continued the work. But I wouldn’t hold my breath for it. Seems like an unthankful job (although I’m sure many projects using Demo now would be happy if it’s still supported, at least).
The Bevy team are doing amazing work and it's great to see it being worked on all the time. I'm not a game developer, but it's interesting to see it listed in some jobs for companies building simulations.
I wonder if this is an HDR problem? I have played these for hundreds of hours and I do not have the same issue. Also mine is 1 gen newer so it could be related to that as well.
I also wonder what brightness people who are running into burn in issues are runing these monitors at. Surely using settings apropriate for a effectively being outdoors vs. a dimmed room don't get the same level of burn in but it would be interesting to find out if the relationship between brightness and burn in was liniear or if reducing brightness only a little bit can already prevent most of the problem.
Nothing out of the ordinary, to be honest. If you read forums such as reddit, you'll notice that these are not unique issues but widespread for the generation of panels in question.
Well, the burn-in is a function of brightness, so surely HDR usage contributes to it as it highlights certain gameplay or UI elements close to max brightness of the panel.
I have many criticisms of Apple and their hardware, but the Mini-LED screen on the M1 MBP I had at a previous job was stunning. I was in the market was a Mini-LED monitor last year and ended up settling with an IPS LCD in the end due to the lack of premium high-refresh 1440p options at the time.
I wanted Deno to succeed to have a single standardised toolchain, but with Deno having its own APIs you'd effectively have to architect your application to be a "Deno app" and it created two different ecosystems. The best way to make your app portable would be to use the provided Node APIs, cutting a lot of the value from Deno.
Edit: I'm missing some context others have pointed out.
reply