m90

This exists over here: https://github.com/ibericode/koko-analytics - never used it myself though.

There's been a recent thread with lot of options discussed here: https://news.ycombinator.com/item?id=23560823, also https://lobste.rs/s/lvdj3w/lightweight_alternatives_google

I tried to do the exact same thing and had to stop considering DNT as it would essentially collect Chrome only back then. Good thing they have reverted this I guess. DNT makes a lot of sense as a concept still.

Apparently this repo contains "Fathom Lite", a (from a codebase perspective) unrelated predecessor of what is currently being sold as a SaaS.

Interesting, did Firefox revert their decision towards DNT? I remember being confronted with the behavior of it sending DNT headers no matter what, which must have been something around spring 2019.

Out of interest, if you say you honor DNT, how exactly do you handle browsers that do not allow setting this as a user preference anymore (Firefox, Safari)?

Not every bug results in an error being thrown or any other signal that you could automatically detect. From my experience most of them are way more subtle.

I think I've never noticed that red-yellow in 40+ years of living in Germany. Interesting. Maybe it's a good thing I never get to drive a car these days.

Slightly OT, but:

> In Germany traffic lights go green -> yellow -> red -> yellow -> green, but let's pretend they're only green -> yellow -> red -> green.

is not correct if I'm not missing something major. Is there any situation where they turn yellow before turning green?

> The guideline was to always use the imperative form

Has this team been distributed in some way or did it consist of people that have regular in-person interaction?

Not everyone has near perfect vision, in which case a better monitor won't fix too much if contrast is bad.

Not to dismiss anything you mentioned, but looking at the big picture Facebook also published things that went awry / never really gained adoption. Flow, Buck, Hack to name a few.

I mean, the cool things are cool (even if I have a really hard time with Facebook as a company) but I think it's a bit of a stretch to say Facebook has "the recipe".

I think your example rather exemplifies what kind of cliches "Disney and Coca Cola" have established. This kind of role models is the universal monoculture, not a nurse called Vladimir.

I would honestly be interested in what the author(s) consider to be the advantage of such a setup over things like for example GitHub Pages, Netlify, S3 + Cloudfront, a plain Apache Server?

> None of them have chosen the "micro-package" way of NPM.

This is not something inherent to npm itself, it's what the people using npm choose to publish.

No matter if people like small modules or not, it's not at all related to the topic discussed.

Things like this make me phrase the following question (which I never see answered): if crypto is so incredibly hard - N.B.: I do think it actually is very hard myself - what is a run-off-the-mill developer to do? Shouldn't I even try to build a secure application using what is out there, even if it has possible attack vectors? If I get it 98% right, isn't this a win for users already?

I certainly don't mind such experiments, but after living in Berlin for quite a while now, I still have to hear anyone complain about that the transit map is hard to read.

I personally would even say that it's one of the easier ones I have used regularly (compare to Stuttgart for example, which is pretty cryptic due to the city's geography).

> My guess is that it will take more time maintaining it than it will save you in the majority of cases.

From my experience, this has almost never been the case. Exceptions were when there was infrastructure for the sake of infrastructure.

Which ones? Which feature?

While I think you can definitely get too fancy with all of that sweet infra, I feel this is missing an important point:

Once you have a working pipeline in place, you can focus on the features, that's the whole point of the exercise: enabling developers to ship features for users. If I have to SSH into some machine and restart a set of services manually in the correct order, it will keep me from releasing features. I am afraid / lazy / whatever. Spending time on this is not something that will never ever reach the user in any way.

The user does not care if something is using Heroku, K8s, or something else, yes, but the user definitely appreciates a product that can reliably iterate on things without major downtime or similar problems.

It's kind of like saying, "well unit tests are nice and stuff, but does the user ever notice?". I would strongly argue the user will notice unit tests in the long run as they ensure the software keeps being maintainable.

I love how the blog itself serves pixels and ads galore. Apparently it's ok if it does yield revenue for the right persons.

I wouldn't be wired for that kind of life either, but the only thing that allows me to make that statement is my own experience as an individual. Which does not apply to anyone else but me.

50 years ago many people would have told you that homosexuality is not something people are wired for based on biological norms. Luckily, this has changed.

Maybe you have never made the experience yourself, but being told you need to change something about yourself that you are happy with just because it is not "normal" is a pretty terrible thing.

Before prescribing something that is "better" you might want to find out if the OP considers their situation worth improving. I can't find any hints on if they are happy or unhappy about it.

I get that you are acting in good faith, but at the same time I get the feeling you consider the OP to be in "a sad place" based on nothing but social norms.

> Of course you can say “just don’t do that”

This exactly. The beauty of Go is that currently you do not need a book called "Go, The Good Parts".

Yes, generics would make a lot of things easier, but almost everything more complex and footgunnish.

I'd be interested in a few real world examples of these cases where you are able to apply the CS knowledge in your day job. Would you mind sharing one or two?

discreet logic flame from around 2001, I think it should have been version 6 or 7

Pivotal Tracker is so incredibly good, it's a shame it's kind of niche (compared to Jira).

When Jira gives you the mightiest of tools to postpone and reconsider everything into oblivion by discussing and custom-workflowing it in epic Cinemascope, Pivotal Tracker will give you just that little amount of space for collecting what you need, and then get things shipped.

It may be weird, but a company using Pivotal Tracker has a big +100 from my side when looking for a job.

Any chance for a less biased title? I'm fine with you being skeptical, but maybe there are better ways for expressing that than a HN post title.

We had stores even before online stores existed. All you needed is to go there.

The PR states you can have your contribution removed if you disagree: https://github.com/lerna/lerna/pull/1616#issuecomment-416820... (however that might work)