Site does look great. I’ve not used Claude Design. How much do you feel like you were able to give your own personal touch to it?
I ask as I see many vibe coded products that look well but are very generic. It signals vapourware to me. But honestly your site looks a cut above. Do you have a design background?
The syntax proposals look fine. But I don’t feel they are needed. Lua is easy to write and grok. I default to using LuaJIT, and have never had an issue with the actual code. Integration with the Lua ecosystem is the problem. Fix the compatibility issues with LuaRocks packages and PucRio. That would be the best dev ex update in my opinion.
Yea, not sure what “written in rust” adds to this. I would have thought that you could get the same functionality with a few shell scripts and a package.json.
I agree, this is why the term Software Engineer is in italics or quotes throughout.
The article is rant written whilst looking back on a career in tech. The author is clearly questioning the legitimacy of the role, and whether or not he actually provided any value throughout his time as a “Software Engineer”.
Zed are doing a great job at making the exact things developers don’t want. It’s clear that their focus is on raising funding rather than making a great text editor.
Yes, I have nothing against Tailwind as a technology. My gripe is that you can now prompt an LLM “make a stylish homepage for my product” and they almost exclusively spit out this Tailwind template.
If that’s all the effort you are going through to make your brochure site, I can only assume the same care was given to the actual product.
“Accidentally recording” sensitive data is happening pretty much everywhere. Last year I was tasked with removing sensitive payment information that had been stored in an insurance company’s database as “call transcripts”. The automated system would state that the payment information would not be stored. It was in fact always stored…
I’ve recently read the third edition of Bjarne’s “A tour of c++” (which is actually a good read). I feel the author of this post could benefit from doing so also.
I really like the concept of this. I'd love a html reference guide (pattern library?) with plain html no CSS or JS to document the basic building blocks of the web.
The server rarely has to render/build the html. It will do it once and then cache it. 99% of websites don’t have real time data. They are just boring webpages.
> What seems wasteful to me is to have the server spend CPU cycles rendering data into JSON, only to have the front-end decode from JSON into internal JS representation, then back into HTML (which is then decoded back into an internal browser representation before being painted on the screen). Seems better to just render it into HTML on the server side, if you know what it's going to look like.
Well put. I think the main issue is that we have a generation of "front end engineers" who have only ever worked with javascript apps. They have no experience of how easy it is to write html and send it via a server. The same html works now, worked 20 years ago, and will work 20 years from now.
I use html and server side rendering. The whole react thing has passed me by. If I need to use a js framework to add interactivity it’s Alpine. But then I just ask myself the question? Is this bad design? And if the answer is yes, I look for a vanilla html approach. Bye the way... the answer is always yes.
I ask as I see many vibe coded products that look well but are very generic. It signals vapourware to me. But honestly your site looks a cut above. Do you have a design background?
Also is the design system you mentioned public?