61–70 of 212 posts
I am not even able to mame changes to gnome-terminator 1XX version because of this.
Earlier quoted context omitted.
> you’re only really committing to git You don't use github just for git. You use it for issue tracking, pull requests and code review, CI hooks, wiki, github pages, kanban boards, bot integration, and so on. That's all stuff that locks you in to Github, and is non-trivial to migrate to another provider.
> "You don't use github just for git." Well, some people do. I don't, apparently you don't, probably most people don't. But you could and some people do. I've seen a few projects on github with notes to the effect of "don't bother submitting issues/PRs here, do it through our [mailing list/etc]"
Unrelated, but GitLab has a pretty slick cookie notice. Tells you exactly what they're doing and lets you opt out of non-essentials.
They currently use the JS engine from Firefox 45 (over 2 years old) and are looking to move to 52 (almost 15 months old). Let's not forget that the update before that was from FF25 which was from 2013.
It's past time to port your stuff to N-API and actually allow devs to have access to standard dev tools using standard dev practices.
It would be a great change for Gnome devs too. Rather than spending weeks of dev time trying to shim in the latest SpiderMonkey version and make sure nothing broke, they could rely on N-API being stable, so they can focus instead on updating the JS interface to ES6+.
Earlier quoted context omitted.
The maximum age of a bug in a bug tracker is not really a meaningful metric. All software has bugs, and all large, widely used software has some problems or limitations that no-one is working on. You can close those issues to tidy things up, but that's also a good way to annoy people. So the only conclusion you can really draw from "one bug was 11 years old" is that they had been using that issue tracker for at least…
It was a persistent and substantial bug, people jokingly suggested getting it a birthday cake because it was so neglected.
Earlier quoted context omitted.
I really wish more people would implement cookie notices like theirs. I really like the one that https://www.bosch.us/ uses too.
Are there really people who appreciate these redundant notices? Do you need a notice that a website uses TCP/IP too?
Now it's time for them to move to Node. They currently use the JS engine from Firefox 45 (over 2 years old) and are looking to move to 52 (almost 15 months old). Let's not forget that the update before that was from FF25 which was from 2013. It's past time to port your stuff to N-API and actually allow devs to have access to standard dev tools using standard dev practices. It would be a great change for Gnome devs to…
V8/Blink already runs 70% of browsers and a massive amount of software, don't you think at some point it's enough with giving Google control over everything?
Now it's time for them to move to Node. They currently use the JS engine from Firefox 45 (over 2 years old) and are looking to move to 52 (almost 15 months old). Let's not forget that the update before that was from FF25 which was from 2013. It's past time to port your stuff to N-API and actually allow devs to have access to standard dev tools using standard dev practices. It would be a great change for Gnome devs to…
That'd mean even more of the world relying on a monopolist of ecosystem of V8/Blink. V8/Blink already runs 70% of browsers and a massive amount of software, don't you think at some point it's enough with giving Google control over everything?
N-API was specifically added to make multiple back-ends possible (by removing dependency on the V8 FFI). You can currently use either Chakra or V8. Spidermonkey could be added (there's an outdated spiderNode around) if Mozilla ever got their act together.
EDIT: I really wish Apple would add JSC support to node. It would potentially allow more standard integrations on iOS. Aside from that, JSC is very fast (faster than v8 at quite a few things) and also supports proper tail calls (as specified by the ES6, 7, and 8 specs).
Earlier quoted context omitted.
I really wish more people would implement cookie notices like theirs. I really like the one that https://www.bosch.us/ uses too.
Are there really people who appreciate these redundant notices? Do you need a notice that a website uses TCP/IP too?
It's just that in recent years the operators of the website have decided they'd like to track and/or analyze their users (best case), or even send that data of to some 3rd party ad network. So I appreciate the heads-up. (Not that it matters, I delete the cookies anyway when I leave the site.)
Earlier quoted context omitted.
I really wish more people would implement cookie notices like theirs. I really like the one that https://www.bosch.us/ uses too.
Are there really people who appreciate these redundant notices? Do you need a notice that a website uses TCP/IP too?