sangeeth96

Damn, that’s awesome! Glad that was a help :D

TIL DecompressionStream, thanks. I managed to shave some more bytes by trimming the HTML bits, raised a PR in case you're interested.

Adam was a very prominent Chrome DevRel and top voices of the web platform. I personally owe to his content (blog, snippets, podcast, talks, youtube, social media etc.) to stay up-to-date on things.

It’s a bit of a shock to me that he of all people is getting laid off and that too in such an ugly way.

It's mentioned in the README:

  - If Caddy has not already generated a local root certificate:
     - Generate a local root certificate to sign TLS certificates
     - Install the local root certificate to the system's trust stores, and the Firefox certificate store if it exists and an be accessed.

So yes. I had written about how I do this directly with Caddy over here: https://automagic.blog/posts/custom-domains-with-https-for-y...

If you see some other way to resolve this, I'm sure Ice welcomes contributions.

FOSS solution that's actually really good: https://github.com/jordanbaird/Ice

Thanks for adding much-needed cool things to Windows lately — the Terminal and PowerToys and now this, all super appreciated. Do you see command palette evolving and becoming a core part of Windows itself in the future? :)

What's interesting about this vs. PowerToys Run is the "extensibility" aspect. Developers can create custom extensions that users can add using winget/MS Store. This feels very similar to Raycast and is something I miss whenever I switch to Windows. I know Raycast team is working to add Windows support but it's nice to see some competition.

Docs about creating an extension: https://learn.microsoft.com/en-us/windows/powertoys/command-...

Release notes: https://github.com/microsoft/PowerToys/releases/tag/v0.90.0

Probably referring to https://en.wikipedia.org/wiki/Padmanabhaswamy_Temple_treasur...

This has been my one wish as well, even if they stubbornly refuse to improve it in many other ways.

I'd personally try to stay away from anything built this way, if I can get a whiff of it (and it's not super hard to find the slop right now). But, even if learn to agree on this for the share of throwaway apps or internal tools that might not need sophistication or care, my point was that the same take applies to the backend side as well and I'd argue that's a more at-risk domain since data is usually in a serializable format to be fed into LLMs and doesn't have the challenges of visual input.

> I enjoy interfaces and workflows and visualizations. I don't want you to feel like I'm attacking frontend or frontend developers.

I hope you mean that but it's hard to see it that way based on your original comment and responses. The trope of "frontend is not a serious job" has been infuriatingly going on for a long time before LLMs took the center stage and that seeps out of the things you've said so far.

But, I'm glad if you mean what you said above.

> Here's where I'm coming from: A shockingly large amount of interesting frontend work can now be done, reasonably well, by an LLM. Sure, it's no staff frontend engineer, but you now have people who can't code at all who can dream up little apps and have the LLM actually just build it for them, something actually useful. That is absolutely incredible to me.

And this is where I'm coming from, based on your original reductive narrative on LLMs overtaking frontend and that the field is somehow at risk — if you feel the same way, you can apply these _exact_ arguments to a _shockingly_ large portion of backend too. I could say most are just glorified spreadsheets. Moreover, a lot of startups just use one of the "serverless" platforms and won't think twice about database, devops, security, authn/authz until they hit an escape velocity.

But I personally think meaningful engineering solving real-world problems at scale that is meant to be an enjoyable experience for the user should be well thought through, end-to-end, regardless of the smaller scopes within.

> Candidly, I just don't see the same momentum for AI in the database/infra space, and speaking personally, I thought it was the right move to shift in that direction.

Partly, I think you are probably forgetting that a lot of these startups promising all of this also promise the backend stuff, even if you might disagree with the choice of tech stack (usually React/Next w/ Supabase/Planetscale/Firebase) and the deployment environment (usually something like Vercel). And the reason why the frontend part is front and center is because... well... that's what the users ultimately interact with. They don't give two shits about the stack (front & back) as long as the product works and works well. But it'd be naive to think this didn't involve all the automated code being spit out on the backend side as well.

And let's forget AI for a moment, by this line of thinking, a large portion of the backend engineering you talk about have been available in simplified forms via serverless offerings or via low-code offerings. Same for databases, including branching and claims of seamless migrations and backup. So, maybe you should have started panicking way before modern LLMs hit the scene? :)

But you probably won't because like me, you realize it's not that simple and it's not always practical. Same reason why I am not using Framer/v0/<insert fancy new tool here> to build a non-trivial front-end app with growing complexity.

I'm a cautious optimist in this space. I do think the tech we got so far is cool and groundbreaking and I use them extensively for noodling. But at the end of the day right now, they're still tools. We are seeing the AI leaders shifting goalposts every day, complain about lack of data etc. and I honestly believe we are many more breakthroughs away from getting to the dream world you're thinking of, especially when broadly generalizing things.

> Aside: I'm also pretty sure you can find plenty of "AI" companies promising automated DevOps/Backend/Database etc. just within https://www.ycombinator.com/companies (try keyword searches).

You once again seem to be thinking of trivial examples of frontend to say there is an “easy” way to verify the loops. I really wish it were that simple for anything reasonably complex I encountered that were customer-facing — often filled with plugins/apps/micro-frontends/libraries owned by other teams etc or clients. I also think if it were that simple, companies wouldn’t be popping up every now and then trying to solve challenges in this space w.r.t validating flows, interactions/animations are smooth and ensuring some weird stuff isn’t happening across all the browsers the customers of your product are using. But there are a lot of them gunning for a piece of the pie, more since the LLM frenzy. And this is largely just web stuff I’m talking about, I’m sure similar complexity exists for mobile apps if we are to count that also into the equation.

Re: backend risks, I once again think you try to rub this off by equating all of backend development is done the way you’re talking about — to perfection, with backups, tests for those backups and all that. I’m sorry to burst your bubble here but if we’re thinking about the same kind of scrappy development you’re talking for frontend, the backend side is about as bad or worse (given how critical you think all of this is, which I agree with). I doubt the backend engineers are sitting there, carefully reading manuals and crafting code instead of vibecoding.

> You can't just vibe code the infra configs and hope for the best, you need someone who understands the output well enough that they could have written it themselves.

It’s not vibecoding but I’ve seen engineers in this role google, copy-paste and modify configs and scripts that run multi-million dollar workflows which somehow worked at the end of the day. I bet LLMs can do a much better job than that, don’t you?

> It's also much harder to simulate the output of LLM infra changes compared to running a browser, so it's more expensive to get training data to boost the next version of the model's performance.

I disagree. It’s much, much harder to go and debug why your customer on X OS, Y Browser and Z GPU (to simplify) is seeing glitches when others are not. Sometimes that leads you to browser bugs. I am yet to see any AI-loop based tools come close to tackling the kind of real-life, serious prod-driven challenges. If you think running a browser is all it takes, I can say something dumb like “running a container is all it takes” but see how stupid that sounds? :)

And it’s also silly to think UI mistakes don’t have real-world implications. There are countless examples for this already — broken purchase flows resulting in losses, frustrated customers unable to complete their work and leaving apps, incorrect request flows causing small/big DDoS, sometimes even stuff that might lead to lawsuits.

——

I feel you have a bleak view of frontend as a whole or you never worked with teams who do a good job or you have been conned by the chest-thumpers who have been saying for years and YEARS that frontend development is pointless, not real CS and have zero value. Oh, and that JavaScript is not a serious language — classic!

If I saw backend/infra engineering the same way based on the # of devs and teams I had to hand-hold and # of their mistakes I had to help fix while working as a front-end engineer, I’d be shitting on them too. But I know better to see that there’s a right way to do it.

This is an extremely dumb take, I’ve worked on both areas before and I could say that infra work is mostly repeated and needlessly complex config sprayed into git. LLMs have seen enough of that to make head or tails of it by the way you’re characterizing frontend dev.

> Steer away from skills like web development that are clearly getting eaten by LLMs.

You had it going well there but then had to ruin it with a take like that.

If you’re talking about your trivial, github-filled example scenarios of frontend, sure. But then we could say the same for all other roles, including backend logic that’s regurgitated all the time.

Like with everything else, the non-trivial bits need work and skills.

Don’t want to be alarmist but even if not using this action directly, I wonder what implications might be if this has leaked tokens from prominent public-facing project repos which might be used by several folks? I spotted an issue[1] to fix this in Expo EAS CLI and I’m guessing there are many more. The payload I saw from the report only seems to dump things to stdout but I guess analysis is still in progress and IDK if it’s the same payload for all the tags.

[1]: https://github.com/expo/eas-cli/pull/2948/files

Blew my mind! Dimitri talks about it in the video but I love the mention of how this project came to be[0]:

> This engine was built to service a project that aimed to demonstrate why Doom can't run in TypeScript types. Well. The funny thing is.. It can.

[0]: https://github.com/MichiganTypeScript/typescript-types-only-...

I should've linked to the YouTube video announcement: https://youtu.be/sHIlFKKaq0A

> What do you think framework is missing hardware wise?

Compared to MacBooks, there's the sheer build quality of not just the whole package, but each and every component. Ever since Apple Silicon, the MacBooks IMO are on a league of their own. My M1 Air is still my most favorite laptop to date and the newer MacBooks define what a "laptop" should be. I realize that Framework's goal makes them approach it from reliability/repairability/upgradeability standpoint but I do hope those laptops converge to the point of having just enough perf, quality and looks to make me want to completely jump ship again.

> Software wise they can't do much

I'd like to hope they think otherwise. I still think there's a big gap on the OS market where h/w+s/w wins can be realized together. Somewhere in between macOS and Linux and just the right bits from Windows. Unfortunately, I don't see anyone attempting to make that happen in meaningful ways. Framework could very well try to do that at some point but not holding out hopes given their current goals.

I'm happy to see Framework going after different laptop/PC segments and trying to break the long cycle of terrible products/cash-grab from all the big manufacturers in the Windows/PC market. I hope everyone eventually has a choice to go for one of these vs. whatever crap Dell/Acer/HP barfs out every year.

I've given up hopes of someone making truly exceptional products for Windows/Linux the way Macs/MacBooks get built. Surface was supposed to get us there but Microsoft just... gave up. Framework is approaching this from a totally different angle, focusing on reliability/upgradeability first and I do hope they eventually crack the formula to build the perfect products.

Who doesn't?

IMO, this is a great wake-up call for every country out there that over-relies on US tech and considers them a messiah. On the short term, this is going to be painful if US continues to bully and holds tech hostage but in the long term, trying to be as independent as possible will only prove to be advantageous (if done seriously and done right). China is a good example.

Umm, isn’t this related? https://www.theverge.com/2024/4/26/24141801/ftc-amazon-antit...

Looks like JetBrains Mono.

I really wish there existed a central platform that tracks/links to all tech conference videos from past to present because YouTube just plain sucks for this and in general, to focus. They've had DECADES to polish this experience (in general for any educational content), at least under the premium tier and I've given up all hopes of them ever getting this right.

Off the top of my head, such a platform could:

    1. Encourage and foster great discussions (and support markdown!)
    2. Have a "community notes" kind of feature to highlight outdated info, errata, related talks etc.
    3. Expose brand new conferences and lesser known ones
    4. Allow people to share curated lists
    5. Likes/dislikes restored
    6. View count tracking from across multiple sources (some confs host on their site before YouTube upload)
    7. Support for interactive viewing of decks, source code etc.
    8. Speaker profiles (w/ verification)
    9. Automation to help conferences/speakers/etc. to submit/update content they own/keep things in sync

etc.

I don't think such a platform exists today but would love to be wrong.

True, this should be fine for straightforward stuff but extremely annoying as soon as you have for eg, quoted strings with whitespace in it which is where it breaks. Have to keep that difference in mind when writing scripts.

The link I posted in my original reply has a good explanation of this behavior. I was the one who asked the question there.

Hmm, I haven’t run this experiment myself but I have in the past faced problems overriding default python/ruby commands in PATH that caused some stuff to fail and had to add some specific overrides for `brew` command, for example.

> Basically software will either use absolute paths

I’ve personally written scripts that break this assumption (that’s a me problem, I guess) so I am quite sure there’s a lot of scripts at the very least that do this.

Nevertheless, you’ve given me something to consider.

I'm aware of this package for getting other utilities but:

1. I'm worried about this conflicting/causing other programs to fail if I set it on PATH. 2. This probably doesn't fix the shebang parsing issue I mentioned since it's an OS thing. Let me know if that's not the case.

It's frustrating this is not the same behavior on macOS: https://unix.stackexchange.com/a/774145

The internet never forgets as they say. I'm not sure why this person and their lawyers even thought it was a good idea to bring this into court and drag it out long enough for even more news outlets to pick it up and links to be indexed by search engines. This is never getting erased. I'd be shocked if the plaintiff somehow wins, doesn't make any sense to me.