595 karma · joined October 22, 2019
hn.scorn217@passmail.net
Gatsby is not a CMS. It would be very nice to have a well-designed and supported CMS that is actually secure and efficient by default.
> How much more complicated can it get then "Here is HTML, CSS and JS put it on a webserver."?
My favorite so far is the combination of WordPress and Gatsby in such a way that you get the worst of both worlds. E.g. building a single page requires creating 10-20 posts in WP, with zero ability to see what changes will look like without actually deploying the site. All this complexity instead of just setting rel="preload".
I often do want results from commercial sites such as nginx.com, but I want results that real people have found valuable and not results that some paid blog post linked to.
Some of use are, but we seem to be losing.
> Shouldn't someone be judged on their character and thoughts, not their biology or circumstances?
This is considered racist now. This was explained to me by a friend that if a person wants to be seen as a "$race man", than not seeing him that way would be offensive.
Do you have a source for this? I can't find anything but SEO junk.
Besides that, it's in extremely poor taste to marginalize someone's sacrifice of two years just because you think they're privileged. It's usually better to make much of someone's contributions than to minimize them.
That said, my take (and that of siblings) is that I'm much better off building my own containers than serving as unpaid Q&A for Bitnami. It would be smart to use containers built by people more expert than I am. Containers that are broken by default do not meet that criteria. So, "reach out to community support" is not helpful to people that have already decided to ditch Bitnami.
> We're careful to pin versions, and hadn't anticipated someone would re-write history and break published code.
This is exactly the kind of thing that will make me ditch a company forever and never look back.
With Clojure, I can think of 2 times ever when a dependency caused an issue. It was extremely obvious since the issue was "won't compile", and the fixes were simple.
With PHP, I expect any change to potentially break something. Bump your AWS SDK which uses a different minor version of guzzle? Fatal error.
There's a world of difference between breakage being an everyday thing and a true rarity.
Because many of us know people that worked their ass off and became wealthy. Does that not happen in Europe?
I've had similar experiences with broken Bitnami images that makes it seem like they aren't even tested before being released [1][2]. Their WordPress images do work, but the way file permissions are configured doesn't play well with the way they have WordPress set up [3]. Have I just had bad luck, or is this a common experience?
[1] https://community.bitnami.com/t/cant-authenticate-to-fauxton... [2] https://community.bitnami.com/t/couchdb-server-log-gives-wro... [3] https://github.com/WP2Static/wp2static/issues/598
> On July 10, 2009, Chadwick was ordered released from prison by Delaware County Judge Joseph Cronin, who determined his continued incarceration had lost its coercive effect and would not result in him surrendering the money.
14 years is pretty crazy, but all-time records are usually extreme.
> This describes my everyday experience with any language or codebase.
That is horrifying. That should absolutely not be normal. I don't know what you work with normally, but it's clear that we are working in completely different worlds.
I can't think of a single time that I've seen a bug exposed by language changes. I have seen dozens of bugs created by language changes, however. (Mostly crashes).
There are dozens of breaking changes in this release alone: https://github.com/php/php-src/blob/96c7d42a3ca9d822a08b3dd4...
Some of the changes are sadistic. "The precedence of the concatenation operator has changed relative to bitshifts and addition as well as subtraction." Have fun debugging code that worked perfectly well for years and now produces unpredictable results.
> This way of writing software is a double-edged sword of course. It works a lot better for a small team of good, trusted programmers than it would for a big company of mediocre ones, where bad ideas are caught by committees instead of the people that had them.
It's a nice demo though.
I believe the point of GP was to say "use an auth framework". If you're rolling your own auth, then your approach is fine.
By "typed language" I suppose you mean "statically typed language". This isn't relevant because A) JSON types exist and B) I've never had a problem with unexpected types from user data in a dynamic language, not even in PHP.
> Otherwise, how is this not caught when it enters your system?
It should be caught, and it's very important that it be caught all of the time and not have any issues due to bugs or version mismatches. That's why the schema should live in the DB.