Carpetsmoker

Perhaps this is a cultural difference, but the entire thing just seems strange from my own (European) perspective. Only in the US do people seem to take pride in their measurement system as some sort of patriotic symbol, which is why I originally thought it was a parody shrug

I'm not even going to get started with all the problems I see with "God bless America", which would be long, tedious, probably inflammatory, and fairly off-topic.

I guess ... but "God Bless America!" seems like a statement to me.

I can't tell if this is intended to be serious or a parody? "All units set in inches" makes it sound like a parody, but the "God bless America" footer makes it sound serious? Hmmm

What advantage does this give you? DDG just gave you a list of URLs, so how can it be "tracking" the results it just presented to you?

The issue, as I understand it, is that the Android app loads the favicon service for search results you actually open in the app.

Yeah, maybe. I don't really know much of the Windows internals, so I try not to assume too much (hence my question in the top comment[1], which was very much a "curiosity"-question, and not a "omg, wtf"-question).

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

The device was released in Oct 2018 though, so at the time it was the newest Android version (9 was just released, probably too late in the Palm dev cycle).

The $280 price tag is a biggest show-stopper IMO (and according to the Palm website that's a "sale" from the $400 price tag, although I never quite trust that). I paid $70 for my basic Android device (Samsung Core A2) and that works just fine as well (with some minor caveats/limitations of Android Go, such as the screen not lighting up when there's a notification).

I think that might actually be harder than it sounds though, since Windows is such an integrated system.

I don't think there's anything wrong with that, but if you're going to do forced updates then you might as well spend some time making the entire user experience nicer. I don't know what the technical challenges are exactly, but not forcing a reboot unless there's really a critical patch might be a good start.

So what is the latency on seL4 then for a similar program? And how well is the performance under real-world desktop conditions compared to Linux, macOS, Windows, etc? I read through that PDF and it doesn't really contain concrete answers to that.

But there are also a lot of drawbacks of RTOS systems, no? Just searching "Real-time operating system downsides" shows a lot of drawbacks that makes it seem like a poor fit for a general-purpose OS: multi-tasking is limited, it's less efficient, and much more complex. There are certain use-cases where this is a good trade-off, but for my desktop OS? Probably not.

I'm sorry, but this is such a non-answer. What am I supposed to do with this? Clearly things aren't that simple to achieve negligible latency, otherwise we would have it. I bet there are a lot of trade-offs involved here (there usually are), and simply stating "take latency serious" isn't helpful in having any meaningful conversation about this.

What would a "non-pathetic" latency look like? What improvements in "the stack" would be needed?

The 130ms is "the time from light hitting the camera to when it appears on-screen on the other side". The article doesn't really specify where the latency happens, but with just the encoding/decoding of video alone I think you'll very quickly get latencies in roughly the ~100ms ballpark no matter what.

BitCoin has fluctuated much more than 10% in the last year though: https://www.xe.com/currencycharts/?from=XBT&to=USD&view=1Y

Certainly much more than USD/EUR: https://www.xe.com/currencycharts/?from=EUR&to=USD&view=1Y

Discounting an entire tool just because you don't like their recommended installation method (which you're hardly forced to use) sounds rather strange to me.

Sponsored search results are marked as such in the Google results, it's nothing like the automagic redirect Safari is showing here.

You don't need anything, but it's a useful way to do it without any significant drawbacks. In many cases, it's more or less the only option.

IMO it's pretty much useless (and possibly even harmful) and a failed experiment. GoatCounter intentionally ignores it. Context: https://www.arp242.net/dnt.html

> I was surprised matomo wasn't listed here. Does anyone know if that was intentional? Seems like it fits the criteria of the post and the goals of open source.

Yes, this was intentional as this article was focused on "light-weight" analytics. I think they'll do an article about Matomo at some point in the future as well.

Counting how many people come in to your store and how many of them actually but something is not "spying".

GA alternatives are a fairly new thing. When I looked at this in May last year there was essentially only one alternative: Matomo. It seems some sort of "critical mass" has been reached, and in the last year quite a few people have independently started working on alternatives.

I agree for many features are still lacking, but as a counter-argument 1) not everyone needs those features (not every product needs to solve 100% of the use cases), and 2) a lot of these products are still quite new, and are actively working on adding a number of those features.

SimpleAnalytics does this.

There may actually quite a lot of PII in the HTTP headers: IP address, Accept-Language, and User-Agent being the most obvious (especially mobile browsers often send a ridiculous amount of PII in the User-Agent header).

There's also some very useful information that's hard to get from HTTP headers, screen size being the most obvious one.

I don't think it's fundamentally more privacy-friendly. The real problem with JavaScript trackers from GA and ad networks is that they'll try to profile you with tricks like font metrics, audio API, set cross-domain cookies, and whatnot. But that doesn't apply to either Plausible or GoatCounter (and in the case of GoatCounter, the count.js script is intentionally unminified so it's very easy to see what exactly it does if you care to do so).

GoatCounter runs fine on constrained environments; it has a RES memory size of about 30M, and for the first few months goatcounter.com ran on a $5/month VPS which was mostly just sitting idle.

GoatCounter author here: yeah, that's not perfect; this also came up in the HN discussion for the article a while ago[1]. I've been in touch with one of the authors of the EUPL since and the short of it is that they don't really think it's an issue.

I've thought about this for quite some time, and decided I'll use a slightly modified version of the EUPL which removes GPL from the compatible license appendix. Just haven't gotten around to that for no reason in particular.

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

You can set up a proxy, which isn't too hard (and operating a proxy is a lot simpler than operating an analytics service)

> And I disagree with another commenter here saying Analytics is just for vanity. That's not true — even for a personal blog analytics are useful to see which articles are still being visited and thus need to be kept up to date, or in case content is deprecated, the least you could do is to put up a warning.

Some examples: I maintained a Vim ChangeLog for a while (which is quite some work), and turned out no one was reading that, so ... why bother?

In another case, I wrote an article about "how to detect automatically generated emails" and I thought it wasn't actually that interesting and no one read it so considered archiving it, but turned out quite a few people end up there through Google searches etc. and I ended up updating it instead of archiving it, as it was clearly useful to people.

I did a write-up of solutions that I'm aware of here: https://github.com/zgoat/goatcounter/blob/master/docs/sessio... – happy to add more if anyone knows of any.

The Go authors acknowledged the usefulness of generics as far back as 2009, shortly after its public release: https://research.swtch.com/generic

It works, so it's suitable.

You don't think it's strange for a service provider to tell people that "mercurial isn't suitable for this" (even though it clearly works, and has been working for many years) and "you're writing your program wrong"?

It's fine to not support certain use cases because it's too much effort or otherwise too expensive. It's not fine to, as a service provider, tell people that their programs are (and I quote) "wrong".

If you're okay with that then that's your choice, but for me it really turned me off sourcehut.

e.g. https://lobste.rs/s/j1gl4t/sourcehut_prohibits_repos_with_la...

Both the original story as well as the comments regarding Andrew's usage for Zig.