43 karma · joined June 18, 2016
That said, do US products not carry detailed ingredient lists or is this product discussed in the article part of a group of products that are exempt?
I must say I don't understand the reasoning behind Microsoft not providing a Pro or Enterprise Windows version that doesn't use the existing users as tester for UI experiments or how much sensitive information they're willing to share on a desktop machine intended for very likely private work (authoring text, media, code, etc.).
They're making the same mistake as GNOME and KDE are, with trying to shoehorn Tablet feature onto the desktop, while pretending the keyboard and mouse are less relevant now.
I admit that there are those who are not power users and run Windows, but those that aren't are most likely better served with a lower maintenance solution like a Tablet with a bluetooth keyboard for writing sessions, and there the privacy invasion is already accepted by using a mobile OS.
PC Gamers and creators are the power users who use Windows for various applications, and Microsoft is making life very hard for them by bundling the improvements in the subsystems with the mobile OS experience on top without offering the new kernel features and such with the old user experience and trustworthy environment.
If you think about it, using a desktop environment that leaks like that for sensitive works doesn't make sense. Someone writing a book or movie script or working on an unpublished program doesn't want even only metadata about it to leak into cacheandclipboard.mscloud.azure.com.
This is all very weird and self-destructive and provides fodder for those who would like to believe Microsoft, Google, Apple are adding these features on request by monitor+control agencies.
Just to be clear, I'm not agains taxes, because not paying taxes is like swatting an apartment, and generally taxes make sense to be paid, although most places also have several unfair tax codes, so I understand the common perception of taxes as "highway robbery".
Do the IRS and say Turkey's tax office tracks these as well? Assuming that you don't try to deposit the exchanged for bills in a bank.
Couldn't someone offer Bitcoin exchange in existing currency shops or the same service via Bitcoin ATMs? How would the IRS and its equivalents track that without requiring identification and registration before use? I suppose a small amount would be allowed for the tourist aspect but then you could use a group of friends or employees to wash small amounts. If you require ID for that, including tourists, then you can track it.
What I'm trying to say is, if this comes out of the box and works reliably, then it'll attract more developers given the other ease of deployment aspects of Go.
(* this is a comment *)
vertically centered. My usual choice is Fira Mono because it looks great and centers * vertically, though I would love a serif monospace font. Maybe Go Mono will be revised but I doubt it will be updated anytime soon.When you say "6 point" do you mean it's bigger than usual?
Is there a place to obtain SF Mono without an Apple Developer account if you don't happen to have a macOS installation handy?
Did anyone else try to use it in xterm or rxvt-unicode?
In xterm and Emacs the vertical spacing seems to be too small, making it look pressed together.
In rxvt-unicode the only problem is that the renderer displays it stretched horizontally like a short but wide block.
I'd be the first to build and use a Firefox where the Qt port was updated and made to work but GTK is the GUI toolkit used by Firefox outside Android, macOS and Windows. That said, GTK2 was and still is very good at what it does. It just works but doesn't support Wayland.
I cannot move to Wayland anyway until xterm or rxvt-unicode are ported since XWayland integration is still imperfect. Like they wrote in the bug report, while GTK2 doesn't have a Wayland backend, GTK3's backend isn't really production quality either with dialogs sometimes opting to zoom out rather than scale out or general stability issues. If you try to start Firefox under Wayland by telling GDK to use Wayland, it just crashes on startup.
I agree with what you say and want to add that there two issues here. First is the GTK3 port of Firefox not working as a native Wayland GTK3 window. Second is the themeing issues with GTK3 that people ran into, which is something you can live with. Finally, it's the serious regressions of GTK3 itself which go unnoticed or ignored as evident in the gnome.org bug-tracker and the tickets I've linked to in a sibling comment.
The most important argument for Mozilla providing GTK2 builds is that otherwise the likelihood of the code bitrotting is very high as it happened with the Qt port. The interesting aspect of the Qt port was that at that point in time GTK2 was the best choice, but now for substantiated reasons major applications chose to rather port to Qt than GTK3. Therefore, if the Qt port were to be revived it's much more likely to be of interest and maintained than back when the GTK2 port was good enough that nobody cared about Qt.
I know X11 and Wayland are not Mozilla's main platforms of interest and I'm grateful that they do support with the feature set they do. I'm surprised at the seemingly isolated echo chamber perspective of the GTK3 devs. It's an interesting behavior to observe since without non-GNOME users it could just as well be rolled into GNOME itself. Interesting times, having lived through the times when jwz in 1998 was debating whether GTK1 was any good for Linux.
Why do we use Mozilla binaries of Firefox on linux distro where there's Firefox builds in the package repository? Many reasons:
1. fast access to security fixes
2. access to EMEfree builds
3. access to different channels
While it is easy to build with cairo-gtk2 as the backend, that code path, as I wrote in a sibling comment, reliably crashes for me anytime I try to do File-Open. I'll try to find out if that AUR recipe or Gentoo ebuild do something different that makes it stable, but the fact remains that GTK2 is about to be unsupported by Mozilla while GTK3 hasn't gotten stable yet, which will make life for anyone that tries to build a GTK2 variant very hard. Therefore, I wouldn't really say it's an easy choice.
Somebody requested this and the reality has been ignored so far: https://bugzilla.mozilla.org/show_bug.cgi?id=1268234
https://bugzilla.gnome.org/show_bug.cgi?id=771708
Firefox GTK3 has regressions too, for instance the bookmark manager not remembering where you were last which works with Firefox ESR (GTK2).
https://bugzilla.mozilla.org/show_bug.cgi?id=1267863
Also GTK3's file dialog is subjectively a huge regression, but others may prefer it, just like Apple's finder changed over time. I still haven't figured out how dconf and gconf work with GTK3, not using GNOME3 as a desktop.
There are more issues with GTK3 but these are the most visible for those of us who don't use GTK3 regularly as part of GNOME3 and have been forced to use it via Firefox. The way I read the GTK3 bugreport it seems like the devs don't test GTK3 outside GNOME3 and hence do not consider it a priority. That one dev has been stressing that a compositor is needed and multiple answers by the reporter that they're using a compositor seem to be missed during reading on the other side. It's a weird exchange. I'm with the reporter. If GTK3 is not supposed to or not tested outside GNOME3, then this should be communicated so that everyone can make an informed decision to use something else or revive the Firefox Qt toolkit code.