Earlier quoted context omitted.
It's a legit April Fools'. On the initial commit: > Some content is hidden > Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden. This for "a spiritual successor to WordPress".
Isn't it normal for the initial commit to be large?
EmDash – A spiritual successor to WordPress that solves plugin security
341–350 of 558 posts
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#342> Most abstractions in software exist because humans need help...It's not clear yet which abstractions are truly foundational and which ones were just crutches for human cognition... We took an API contract, a build tool, and an AI model, and the AI wrote everything in between.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#343Re: EmDash – A spiritual successor to WordPress that solves plugin security
#344Earlier quoted context omitted.
Websites used to be static html files. You either write them by hand, or use a tool that generates it locally, upload everything and you're done. Perfect security. Great performances. It's in this sense that static generators go back to the source, the simply produce dumb HTML files that you upload/publish to a web server that doesn't need to run any code. Just serve files.
Imho CMS is just a tool that generates static html files on the server. The distinction is a bit artificial. CMSes have static html cashing and CDNs will allow you to "one-click" firewall the dynamic administration and cache the static html for you. Static website generators are cool way for programmers to do that work on their machine but in the end the distinction of what gets served is very small (if you set up th…
Go ahead and give your content people access to a static site builder and see how quickly the process falls apart. Static site generators are perfect for engineers but terrible for the marketing people that are the actual "customers" of your public-facing website.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#345Serious question: Why is everyone still using JavaScript to AI-code projects? You can vibe-code apps with real languages now. There's no reason to use an interpreted, bloated, weird language anymore. The only reason interpreted languages were a thing was so you could edit a file and re-run it immediately without a compile step. Compiling is now cheap, and you don't have to build expertise in a new language anymore. A…
But it's correct that it is odd. As long the lang is mainstream enough, it hardly matters. My assumption is that JS/TS coders have the highest resistance to switch platforms, the ecosystem is huge, it's cross BE/FE, performance isn't complete trash, everyone they know knows the platform as well. Why switch? It's a screwdriver, if your passion is to screw things, you will.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#346Earlier quoted context omitted.
> wordpress is valuable because it allows very bad developers / marketing people to write very bad code and get away with it, driving extremely low cost solutions for clients who are cost concious. You've sort of nailed it, but this isn't a bad thing. An alternative for these customers does not exist. There's another vertical which is organizations that have armies of writers churning out content. Any kind of publish…
>> wordpress is valuable because it allows very bad developers / marketing people to write very bad code and get away with it, driving extremely low cost solutions for clients who are cost concious. > You've sort of nailed it, but this isn't a bad thing. An alternative for these customers does not exist. Yes! I'm locked into WordPress, which I hate, because it's the only platform that will allow a non-developer to ma…
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#347Serious question: Why is everyone still using JavaScript to AI-code projects? You can vibe-code apps with real languages now. There's no reason to use an interpreted, bloated, weird language anymore. The only reason interpreted languages were a thing was so you could edit a file and re-run it immediately without a compile step. Compiling is now cheap, and you don't have to build expertise in a new language anymore. A…
The problem with Go specifically is that it's not great for processing arbitrary JSON and especially not your typical frontend code. One issue is that you don't write Go code, you write Go plus some templating language (like html/template or go templ). Not being able to seamlessly move from regular code and template code adds friction and is limiting while developing, figuring stuff out and iterating. Another problem…
Wow that is the cheapest excuse I've heard recently. Templating languages can certainly be dogshit, but demanding it to be the native language is pretty weird. Also it's not like the JS ecosystem spawned their own weird abominations to do simple string concatenation. Sorry for being harsh, I understand that as a general inconvenience but attributing JS as superior is just bold.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#348Serious question: Why is everyone still using JavaScript to AI-code projects? You can vibe-code apps with real languages now. There's no reason to use an interpreted, bloated, weird language anymore. The only reason interpreted languages were a thing was so you could edit a file and re-run it immediately without a compile step. Compiling is now cheap, and you don't have to build expertise in a new language anymore. A…
a) llms are good at writing typescript b) typescript fixed a lot about javascript and is somewhat decent c) multiple fast and performant runtime engines d) deployment story is php levels of easy that's it.
Yeah just invalidate the SSR cluster for your tiny footer update and let it prewarm until coffee break. Easy.
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#349Earlier quoted context omitted.
> with real languages now. how is javascript not a real language? > There's no reason to use an interpreted there are loads and loads of reasons to use "interpreted" languages. that you can't think of even a single one while still pretending to be knowledgeable in the field is really intriguing. > bloated, weird language oh, i see, this is all just a religious rant. carry on!
Typescript is legitimately weird. You start off with Javascript, a language made to validate HTML forms. Then you implement a bytecode compiler so it's not unusably slow and buggy. Then you implement "frameworks" to try to make it create real applications across the insane platform that is the web browser. After twisting yourself into a pretzel just to avoid learning or making a new language, you finally invent anoth…
coding in go (or whatever) and transpiling is just an extra step on top of that. not without benefits, mind! there are surely many situations where that is appropriate. but that still doesn't mean it is universally the "right thing". which brings me to:
> just to avoid learning or making a new language
there simply is no "one language to rule them all" nor there ought to be one. my entire career has been about learning different languages, techniques, tools, systems, environments and workflows. lots of them, nearly non stop. javascript has its nice place, and i like it vanilla, in all its weirdness and unapologetic untypedness. :)
Re: EmDash – A spiritual successor to WordPress that solves plugin security
#350This is very interesting. I've worked with WordPress on and off for 10 years, and I'm convinced that this project has got 2 things absolutely spot on. TypeScript and Worker plugins. I've given the security, or lack of, WP a lot of thought recently. In WP malicious plugin has access to the database, enfironment variables, rendering text on screen (think XSS). Luckily, a thoughtfully designed plugin system can mitigate…