Yeah. I don’t want to see “wow look at how pretty this markup is”. I want to see “look how flexible and easy to change this is, without redoing everything”.
If you’re not talking about change, the other stuff is pointless.
I gather by the mention of fascism that the correspondent is a bad person. So it makes sense that Russell told him to get bent. But, that is all that he's really saying here.
I can only guess this is noteworthy due to the parties corresponding because it isn't very interesting outside of that.
Have you been reading the news? Perhaps about someone who engaged people in debate while holding extreme views? In the process, they gained some measure of credit amongst people with less radical views, merely for the act of having conversations. Except in this case the debates were not with Bertrand Russell, but with 18 year old college freshman.
I understood the posting to be a subtweet-style comment on that.
It is a lot of work but it is work that for the most part should not have been done. I took a quick look at the code (since I know PG very well) and I would not recommend anyone to use that mess off Bash code which configures PostgreSQL in an annoying and incorrect way and exposed some arbitrarily select settings in the environment (some very rarely used) while you have to do most in the config file. Better to just write your own Docker image for scratch, or use the official PG image of your needs are simple.
This is what happens if you merge every feature request you get and do not have a clear plan or architecture. After reading the code I am happy they are deleting the images, at least if this one is typical.
As a PostgreSQL expert I can write a much better image which suits my needs in one day, which I have also done several times. It would be harder for a non-expery but I do not think a non-expert should use this image due to some footguns I spotted. This kind of generic image is a bad idea and very hard to build.
Hindsight is 2020, there’s now helm/kubernetes operator under the cloud native umbrella. I’m sure they took in all the mistakes from here. This helm chart is getting long in the tooth, but is still monumental. Imo running psql on kube is a mistake to begin with but here we are.
Not only that, but if the trial works that way, you can repeat it any time you need to record something. The app probably dropped a prefs file somewhere (the old-style Mac XML preferences files), delete that and go again.
I'm often saddened by all the normalization of all the things people do to cheat their way through life. Why does everything need to be physically prevented just so people don't find a loophole to exploit? And then just act like it's nothing or are even proud of it? There is a trial period + you are asked to pay if you keep using it after? Well, pay up if you do. You also (hopefully) don't steal candy from the supermarket, even though it's "actually easier than just paying". Why would it be any different for software?
We have the editor plugin configured so we can see lints in-editor. But the rules are not yet sufficiently configurable for us to use it in CI. It seems they have their own rule-config schema, and it doesn’t expose everything you might need.
For example the banned import rule- you can list specific imports to ban, but you can’t configure a pattern. The actual lint rule supports patterns already but biome’s config doesn’t accept a `pattern` property.
