@matteocollina Matteo. Long time fan.
This thread is pretty damaging to your credibility. Incredible AI slop.
I'm sure this felt convenient, but it's pretty hurtful to anyone spending the time to read it.
I hope this is just a brief experiment.
The first thing I did at @tryramp was set up distributed tracing, structured logging, and metrics for Inspect, our background coding agent.
We now have full visibility in to everything the system is doing: the browser, CF workers/DOs, @modal sandboxes, database calls, etc.
Most importantly, Inspect now has visibility in to itself. It can self-triage runtime errors it encounters and create PRs to fix them.
Every morning, it reviews the past 24 hours of its own @datadoghq dashboard, identifies systemic issues, new errors, and long tail latencies, and has a summary + PR waiting for me at 9am.
@fscgo JS's biggest failing is its error handling model. This is the first framework I've seen handle this well.
However, it so drastically changes the shape of your codebase that people need to understand it for you to use it.
No strong opinions yet.
@LewisCTech Web components are solid - lit-html seems to be doing well for other folks. You're not going to find me arguing for react.
Web components lack some abstractions that companies find necessary, like pre-rendering and signals.
@LewisCTech The question is then what is the most consistent model - how do you design a system optimized for iteration. That's where the guardrails come from.
Annoyingly any abstraction you make is going to be leaky and the tradeoff is in types of leaks.
@LewisCTech The qualifier here is going to be on the size of your team. The standards from any system are usually born from a desire for consistency.
For anything reasonably complicated, the codebase cannot live in only one person's head and therefore needs enforcement of style.
@PixelCanuck@LewisCTech You mean by using html`` tagged template literals?
https://t.co/200aiVZN2H
Pretty sure JSX by definition uses a transform step, which means it requires a compiler/transformer of some sort.
I haven't tweeted in a minute, might as well shout something out super inflammatory.
@Cloudflare I genuinely believe one of your biggest obstacles for entering a more consumer-focused market (with enterprise follow-up) is your absolutely god-awful UX situation.
The solution here is hiring an executive (NOT a consultant) with focus over directly this problem.
You need someone with power to say "no, adding one more button or level of indirection will make the product worse".
I love Cloudflare's product offering, but I am unable to recommend it. This is a shared sentiment with many I've talked to.
Out of the 29 open position, not one is for Front-End development. Not one is for a UX researcher or designer.
This seems like a mistake.
@andreas_longva@pcwalton It kind of depends on your coding style.
I got in the habit recently of throwing a bunch of code at the wall that I write in a code-golf-esque way and just hitting my keyboard shortcut for the formatter.
Also helps if you’re working with someone else’s code.