Earlier quoted context omitted.
Users love it though.
If by "users" you include developers who spend most of their time with the system, the two thousand 1-star reviews ¹ will beg to differ. ¹ https://wordpress.org/plugins/gutenberg/#reviews
Websites have evolved back to static HTML/CSS/JS files
301–310 of 313 posts
Re: Websites have evolved back to static HTML/CSS/JS files
#302Earlier quoted context omitted.
We're back to "The boring solution has a long list of inconveniences and uglinesses that everyone knows about. If we chose the new solution, nobody would know where the bugs are and we can have exciting new ones." Really the problem is that the standard solution hasn't improved. Backends are still a hassle in the 2020s. People keep reinventing CGI. Every now and again I think "why doesn't someone just produce a simpl…
> "The boring solution has a long list of inconveniences and uglinesses that everyone knows about. If we chose the new solution, nobody would know where the bugs are and we can have exciting new ones." Is this C vs Rust again? (it's a joke, but go ahead, downvote).
Re: Websites have evolved back to static HTML/CSS/JS files
#303Earlier quoted context omitted.
The intent is for users to style it themselves.. or it was, until browsers stopped having that functionality.
Browsers never stopped having that functionality. It's still entirely possible to load custom user styles into a webpage.
Re: Websites have evolved back to static HTML/CSS/JS files
#304Earlier quoted context omitted.
If by "users" you include developers who spend most of their time with the system, the two thousand 1-star reviews ¹ will beg to differ. ¹ https://wordpress.org/plugins/gutenberg/#reviews
No, by "users" I meant... users. Those developers have basically nothing to do with using Gutenberg to write content, why do you think their opinion should prevail on that of actual users?
Re: Websites have evolved back to static HTML/CSS/JS files
#305There's nothing wrong with static HTML/CSS/JS. There's also nothing wrong with a rich SPA. And again, there's nothing wrong with using some kind of dynamic server-side HTML/CSS/JS presentation (like WordPress). Where there is a problem is the culture of software engineering, and the tendency to select the newest technology stack of the day for inappropriate applications. I think any seasoned software engineer has acq…
Have fun getting junior engineers interested in PHP, an objectively gross language. You'll get a stable system to begin with, but nobody younger than 45 who wants to touch it. It also has a large attack volume and curated security exploits that you buy into when you inevitably use plugins. This article is about static HTML/CSS/JS. You can accomplish a good, modern CMS in halfway-decent languages using netlify and any…
Re: Websites have evolved back to static HTML/CSS/JS files
#306Earlier quoted context omitted.
> It's slow and most people prefer the static html version. The only people I've ever heard talk about the static html version are a few HNers. I'd wager 99% of people don't care, don't mind their email client's first load being slow (they just keep it open in a tab anyways), and don't even know about the static html version.
> The only people I've ever heard talk about the static html version are a few HNers. I'd wager 99% of people don't care, don't mind their email client's first load being slow (they just keep it open in a tab anyways), and don't even know about the static html version. Are you claiming that because people are ignorant of an option that is clearly better for them, the option is redundant? So if people don't care about…
Re: Websites have evolved back to static HTML/CSS/JS files
#307Earlier quoted context omitted.
Quite the opposite, it does its job pretty well for me. It has good keyboard shortcut support, and the UI is only lagging if I go into 80-100 long email threads otherwise pretty good. What's unintuitive about a list of emails and few simple features? You also bog my mind :)
I don't like how it is formatted for starters. Also the reply button is impossible to find- since its not at the time like it logically should be. Reply all and other options are hidden instead of being exposed. When clicking on reply, it takes me to the bottom, away from the content so its impossible to read and response. It also doesn't have proper mailboxes, and rules are impossible to make. I do not like it at al…
Re: Websites have evolved back to static HTML/CSS/JS files
#308Earlier quoted context omitted.
I'm not sure it's junior/senior so much as personal taste: Plenty of junior engineers use Vim and Emacs, neither of which are trendy in any meaningful way, and I'm sure there are senior engineers who use Visual Studio with all of its whiz-bang. Similarly with websites, some have ideas which need AJAX and, possibly, WASM, and others have ideas which need static sites or, at most, "slightly dynamic" websites with only…
> Plenty of junior engineers use Vim and Emacs Pretty sure that’s not the case anymore, I have been a developer for 3 years and have never ever seen anyone use either of these for work
Re: Websites have evolved back to static HTML/CSS/JS files
#309Earlier quoted context omitted.
I don't like how it is formatted for starters. Also the reply button is impossible to find- since its not at the time like it logically should be. Reply all and other options are hidden instead of being exposed. When clicking on reply, it takes me to the bottom, away from the content so its impossible to read and response. It also doesn't have proper mailboxes, and rules are impossible to make. I do not like it at al…
Your critique doesn’t really carry a lot of facts but mostly your negative opinion. New Gmail isn’t the fastest but it’s interface is pretty much OK and its rules are great.
I don't understand how you can say "its rules are great" when I can't have two different message subjects go to the same mailbox.
Re: Websites have evolved back to static HTML/CSS/JS files
#310There's nothing wrong with static HTML/CSS/JS. There's also nothing wrong with a rich SPA. And again, there's nothing wrong with using some kind of dynamic server-side HTML/CSS/JS presentation (like WordPress). Where there is a problem is the culture of software engineering, and the tendency to select the newest technology stack of the day for inappropriate applications. I think any seasoned software engineer has acq…
Why not use Wordpress --> static generator --> Netlify (aka free hosting)?