thethimble

> it's perhaps all about who one knows and making sure that everyone gets to tell a story of successful exits.

No. It's all about building a great product that people love. Vite is a foundational tool in the JS ecosystem.

Acquihiring the tool/team is entirely downstream from creating a foundational product.

Perhaps named closing tags like `</section>` are a factor?

Or users will realize that a trashy ads experience is bad and switch to a service that isn't trashy.

I don't understand why there's so much fearmongering about ads when heavy competition + zero switching costs will effectively guarantee good UX.

I feel like this is a solvable problem. If you emit an errant word that should be replaced, why not correspondingly emit backspaces to just rewrite the word?

I feel like this is the best of both worlds.

Perhaps a little janky with backspaces, but still technically feasible.

Handy is great but I wish the STT was realtime instead of batch

Why is this relevant at all?

Having humans in the loop at some level is necessary for handling rare edge cases safely.

If the world is built on AI infrastructure (models, compute, etc.) that is controlled by the CCP then the west has effectively lost.

This may lead to better life outcomes, but if the west doesn't control the whole stack then they have lost their sovereignty.

This is already playing out today as Europe is dependent on the US for critical tech infrastructure (cloud, mail, messaging, social media, AI, etc). There's no home grown European alternatives because Europe has failed to create an economic environment to assure its technical sovereignty.

The AI market is an infinite sum market.

Consider the fact that 7 year old TPUs are still sitting at near 100p utilization today.

Speak for yourself. I've been insanely productive with Codex 5.2.

With the right scaffolding these models are able to perform serious work at high quality levels.

The consumers are getting huge wins.

Model costs continue to collapse while capability improves.

Competition is fantastic.

As long as China continues to blitz forward, regulation is a direct path to losing.

This will absolutely help but to the extent that prompt injection remains an unsolved problem, an LLM can never conclusively determine whether a given skill is truly safe.

> And not delivering products

2024 revenue of >$100b is quite impressive for not delivering any products

Perhaps there should be an EU committee to draft a mandate for a working group tasked with identifying the necessary stakeholders for a preliminary report on digital infrastructure.

To each their own!

The Discord/Slack frontend reduces friction significantly - particularly on mobile.

With proper sandboxing you get real benefits while limiting the blast radius significantly.

Clawdbot is one of those things that's really hard to get unless you have experienced it.

It's got four things that make it great:

1. Discord/Slack/WA/etc integration so those apps become your frontend

2. Filesystem for long term memory and state

3. Easy extensibility with skills

4. Cron for recurring jobs

Sure, many of these things exist in other systems but none in a cohesive package that makes it fun and easy.

Or even zellij > tmux

I wish one of these models was fine tuned for programming.

I want to be able to say things like "cd ~/projects" or "git push --force".

But this strategy is also eligible to you. Nothing is stopping you from turning your Roth IRA into a multi billion tax free gain.

Borrowing against illiquid assets should be considered a taxable event. Seems like this would entirely fix the loophole.

> Running CI/CD pipelines can use significant amounts of energy. As much as it is tempting to have green checkmarks everywhere, running the jobs costs real money and has environmental costs.

> Unlike other giant platforms, we do not encourage you to write “heavy” pipelines and charge you for the cost later. We expect you to carefully consider the costs and benefits from your pipelines and reduce CI/CD usage to a minimum amount necessary to guarantee consistent quality for your projects.

So much pretentiousness

Absolutely. The limitations of AI (namely statelessness) require us to rethink our interfaces. It seems like there's going to be a new discipline of "UX for agents" or maybe even just Agent Experience or AX.

Software that has great AX will become significantly more useful in the same way that good UX has been critical.

100% of startups are just software engineering

Glad you like it! About to order one now as a baby car!

This doesn't fit the narrative of "Elon bad" therefore the Ford 29k vehicle steering loss recall gets two upvotes whereas the Tesla 6k vehicle dealer-installer light bar issue gets hundreds of upvotes.

I feel like LeCun has been plainly wrong about LLMs. He has been insisting that the stochastic nature of sampling tokens causes a non-zero hallucination property for any given next token such that as output length increases, this will inevitably converge towards garbage.

The reality is that while LLMs can make mistakes mid-output, those interim mistakes don't necessarily detract from the model's final output. We see a version of this all the time with agents as they make tactical mistakes but quickly backtrack and ultimately solve the root problem.

It really felt like LeCun was willing to die on this hill. He continued to argue about really pedantic things like the importance researchers, etc.

I'm glad he's gone and hopeful Meta can actually deliver real AI products for their users with better leadership.

You might be better served talking to ChatGPT/Claude so it can tailor explanations based on your level of understanding. I've found that being super clear about concepts you understand well vs concepts you're unclear about makes for really effective explanations.

GCP is growing 34% with a current annual run-rate of $60B in revenue. So I'd also say not too bad.

Is "mandatory" spending actually fundamentally mandatory? Characterizing it as such feels like a sleight of hand that prevents us from discussing whether that spend is truly necessary.

In an overspending crisis of such magnitude I wish there was more urgency in the culture to cut spending across every budget segment regardless of whether it's "mandatory" or not.

I wish there was more info on the article about actual customer usage - particularly whether it improved process efficiency. It's great to focus on the technical aspects of system optimization but unless this translates to tangible business value it's all just hype.