kanonieer

Obviously. This is a consecrated codebase[1].

[1]: https://www.sqlite.org/codeofethics.html

It seems that some TypeScript and Rust devs are converging in their holier than thou approach, never missing an opportunity to belittle people for not choosing a tool they would have chosen.

Indeed.

Interesting project but terrible naming.

Managed would be great.

Can anyone recommend a good Docker Hub alternative for simple image hosting excluding AWS/GCP/Azure products?

It's up there indeed.

> We’re excited to announce the availability of a new PWA feature that closes this gap and helps blur the line between apps and websites even more.

I don't see how they can use "blurred line" as a positive trait here. There are important differences between native apps and web apps, why hide this information from a regular user, especially when this information can be conveyed by 30 pixels.

Same reason why people are proud of things that are totally outside of their influence: tribalism, nationalism etc.

Educate yourself on the topic and it will. Maybe start here?[1][2]

[1] https://en.wikipedia.org/wiki/Halloween_documents

[2] https://www.gnu.org/software/fsfe/projects/ms-vs-eu/hallowee...

There are some neat suggestions on this post[1] that can help you share your work more effectively:

[1] https://news.ycombinator.com/item?id=22336638

> I too have seen the articles proclaiming that devs should stop implementing auth themselves > and instead use some Auth as a service product.

It's a moved goal post which sneakily tries to position itself on top of the old adage "never roll your own crypto". Problem is, that adage is really about security whereas "don't roll your own auth" is about not wanting to do a mostly boring part of your job. I'd take my hat off if they'd admit it, but it's much easier to get budget with potential security scares compared to "we don't wanna".

10 years of Meteor... Well thanks, now I feel old. I haven't personally used Meteor but I remember looking into it seriously few times.

If anyone wants to explore an open-source Meteor project in the wild, a kickstarted project named Pixel Art Academy[1] comes to my mind. Looking through the repo[2] takes me back to CoffeeScript days.

[1] https://pixelart.academy

[2] https://github.com/Retronator/Pixel-Art-Academy

I don't think certifications will make a significant difference from the HR point of view (maybe in Enterprise) but one thing I observe in my network is that some people really benefit from certifications purely because it boosts their self-confidence or help them get over a nagging case of impostor syndrome.

I find that these people feel lost when you tell them they'd be better off just being curious and learning by doing the thing itself. They tend to find comfort in systems like the belt system in martial arts. So, if you feel this way- it might be worthwhile to pick up a few certifications just for yourself.

Where's the take? As it stands it's a silly flame-bait.

Ling's Cars

https://www.lingscars.com/

> There is only two kinds of people. The ones that don't like Tailwind and the ones that have used it.

I know a lot of people who have tried but didn't like Tailwind. I think most people like it on a greenfield project, but that number drops off when they go back to a Tailwind project after some time.

I got my last full-time gig via referral from a friend. Switched to contract/freelance work afterwards.

Considering the normalization of spending hundreds of hours grinding LC questions and the industry built around whiteboard interview preparation, my (n=1) conclusion is that LC interviews is not about technical assessment at all.

It's an assessment that's designed to find people who are ready to submit to an endless grind with little to no skepticism. Developers who question the technical usefulness of LC interviews are simply not the target audience anymore. The target audience seems to be potential employees that are hungry and without leverage.

Myth and mythology are not the same thing. Example contrast: Mythbusters vs. Mythologybusters.

The curriculum on your project looks like any other web dev oriented bootcamp to me. Not that anything is wrong with that, it's just in my mind a CS oriented curriculum would be something like teachyourselfcs.

It's not just arrogance, it's called being a "modern JS developer". The bubble some of these people are living in is so rigid, they can't simply accept when someone does things differently. Some quotes from the parent are as follows, accompanied with some sarcasm on my end:

> nonstandard web framework (go-macaron)...

The "standard" is React and Vercel offerings. Get with the times.

> ditching go-macaron and xorm for something more widely used...

You're only supposed to use libraries that are #1 popularity in their respective category, few weeks of no commits means the library is dead.

> I would also add that I don’t even like NextJS. I’m recommending it because it’s a better engineering choice...

Yes, you read that right. This is the advice for Gitea: Github, Gitlab, SourceHut all used server-side templates, so much so that latter two are quite useful even when JS is disabled- but the "better engineering choice" (citations sorely needed) is NextJS.

0. Writes a numbered list all on the same line.

> on their way to at least a 3x

I'd say this is getting pretty close to a 4.5x /s

Interesting. This has some _why vibes.

As deep as the rabbit hole takes me. Nowadays I became very picky as to what "new" thing I decide to incorporate into my workflow, so when something checks all the marks, I'll go all in.

Have you read the article? Because what was proposed back then is not what NGINX is doing.

I stopped considering using Caddy when the following happened:

https://web.archive.org/web/20170913160203/https://caddyserv...

The project lost tons of good faith back then, and in my eyes (as a brand) never recovered.

You're absolutely right, it was a dumpster fire and it tarnished the name for me as well.

https://web.archive.org/web/20170913160203/https://caddyserv...