> and the GPL would prevent outright exploitation by our competitors, but those were to allay fears of my partners to allow me to make the gift.
I can understand his stance on AI given this perspective. I have a harder time empathizing his frustrations. Did he also have a hard time coming to terms with the need for AGPL?
Replace GPL in his sentence with something anti-AI and think of back in time when Carmack did that, it's exactly the same situation now except he's in a much more favorable position to make that stance, it's ironic if he can't see that most of us are on the other side of that fence with AI right now.
I just read the article and I didn't get away with that rationale. Now, this isn't to say that I agree with the author. I don't see why go would *have* to add typed error sets to have a try keyword.
Yes, mimicking Zig's error handling mechanics in go is very much impossible at this point, but I don't see why we can't have a flavor of said mechanics.
Unironically have been migrating my static pages (from Nextjs and Eleventy) to plain HTML and love it.
Of course depends on your use case if that is feasible.
First, it doesn't have any provisions for code reuse. So, if you have multiple pages that use the same header, same footer, or same navigation menu, your options are either to copy-paste it (gross), or to build the final html out of smaller pieces, at which point you've reinvented either a static site generator or a web server.
Second, if you write long stretches of text, the html markup can get in the way, as opposed to unobtrusiveness of something like markdown.
Yea I think I’ll write my own static generator that just combines 3 templates for header/body/footer and converts markdown from the body.
Should be fun project.
I’m tired of the constant update pressure from existing solutions and I only need something dead simple.
> at which point you've reinvented either a static site generator ...
It doesn't have to be Astro though. You can build something super simple that just includes the header, footer, and nav. Leaving most of the site as plain HTML.
How would this help? You would want your header render on the server, wouldn't you? Not to incur a CLS penalty, right? How does a web component help in this scenario?
Same, and I was starting to feel kind of strange doing anything in html/php in 2026 but then I looked at everything else and realized I'd have to start from scratch again. Plain ol' HTML has worked great.
I recently rebuilt my site with Parcel + React Server Components. RSC are designed to solve many of the same problems that Astro does. And Parcel is “just” a bundler and not a framework, so it has less magic and gives you more control.
I experimented a lot with bootstrapping React projects this past fall, and Astro was by far the least painful to use. Notably, it was the least goofy of all of the React starter kits to use for server API development.
Well, there's this other project that recently secured funding from a company that has a proven track record of supporting great open-source projects like Astro, TanStack, and Hono without trying to capture or lock anything down.
Disliked the templating solutions, the messy documentation, the loss in momentum, and liked a lot of the stuff (especially the tooling and principles) in astro.
Also strongly disliked how political eleventy got.
I just wanted a website, not a an internal debate about what I am potentially being absorbed into. I can vote, and spend money on donations, I don't need to enact change through my tech stack.
I have a very similar story. It went from ibuprofen and water to antibiotics the following day, to different antibiotics the next day, and finally to having my tonsils purged (i.e., cut open) with local anesthesia in 4 days. By this time I no longer could speak. It was the most pain I felt in my life.
I still trust doctors, but this made me much more demanding towards them.
That (peritonsular abscess) was also the most painful thing I have ever experienced in my life. I was genuinely hoping a lightning bolt would come out of the heavens and kill me.
Totally. I was in the ER, hitting my head against the wall because of the pain. And when the doctor cut it open... it was so painful, but the almost instant relief was worth it.
SWE jobs are in fact, not safe, if vaguely defined specifications can be translated into functioning applications. I don't think agents are good enough to do that in larger applications yet, but it is something to consider.
Depends on the software. IMO, development speed will increase, but humans will continue to be the limiting factor, so we are safe. Our jobs, however, are changing and will continue to.
It didn't. Or rather it did, but not for the obvious reasons.
Taxes are not required for spending. Spending isn't required for spending, because ultimately government money is a proxy for power differentials and collective strategy.
Money defines which behaviours and which demographics are rewarded, and which are starved and punished. There are numbers and flow dynamics, but it's primarily a social credit system, not a substance.
Taxes are really a way to control the relative power of some groups over others - a form of regulation.
So when you have events like the New Deal and high taxes on the super rich, that means the economy is tuned towards diminishing power differentials, expanding infrastructure, and access to opportunity.
Low taxes on the super rich means expanding power differentials, more rigid hierarchy, diminishing collective infrastructure, and decreasing access to opportunity.
Likewise with provision of public services. If healthcare is cheap, guaranteed, and widely distributed, that increases individual agency and diminishes hierarchy.
If it's expensive and rationed by/for corporate monopolies, it increases hierarchy and diminishes agency.
>WCET ("worst case execution time") is an important consideration: Operations should take a fixed amount of time and the produced machine code should be predictable.
Good luck. Give the avionics guys a call if you solve this at the language level.
reply