dbl9

In that case it's clear fraud and will be dealt with, I assume. Given the comments here about a liberal market, I assumed labeling requirements are less strict over there.

In Germany and many places if not all of west and central Europe products get detailed labeling of ingredients. For instance if you buy what's supposedly a brand name syrup of plums and therefore should be 100% the result of cooking plums and nothing else except maybe conservatives, what you actually get according to the label is 99% various forms of industrialized sugar and then a little bit of plum flavor. This is great because I've also found such syrup which was what you'd expect and pretty much the same thing you get when you do at home, but it wasn't from the most famous brand in Germany, which is disturbing given the price you have to pay for the brand. Same with stuff that's supposed to be honey or all those fancy teas which have no trace of what the label says if you look into the ingredients list. Most people do not bother to read it, and I don't blame them, but if you do, you start to put many products on a personal blacklist of fakes.

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?

As long as Microsoft isn't addressing the real blocker for people to skip Windows 8 and 10, they won't convince that user base. Those users might eventually move to 10, but will stick with 7 as long as they possibly can and the Windows apps they rely on support.

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.

I've been thinking about this and wondering how they could prevent people moving to a WeChat like app and doing all financial transactions within that. If you enable anonymity in that there's no need to identify your meat life persona with your WeChat profile, how would the control be retained? Short of illegalizing mobile devices that allow installing a banned app like WeChatAnonEdition and having traffic police carry inspection devices that would allow them to detect illegally open Android devices in a driver's pocket, I don't see how it can be prevented. If you sell and buy inside WeChatAnonEdition and also get your salary inside WeChatAnonEdition, there is no monitoring and control anymore.

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".

When I visited Istanbul, I passed through a district with an endless number of exchange shops, and it seemed like a place where you could easily wash money without any bank account involved. I believe Turkey isn't alone in having such a culture of buying/selling US dollars by tracking the USD rate.

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.

I think I figured it out. Somehow Skia was enabled in Firefox and resetting that seems to have fixed the rendering bug. Given that 51 will turn Skia on by default I hope this will be fixed before the switch.

Centered double quotes?

If you consider that many gui apps are written with HTML right now, I wouldn't worry about the looks of the toolkit as much, as long as it integrates and behaves as expected in X and Wayland and Windows and macOS and iOS and Android. That's more important than a skin, although I know many users prefer their platform's "native look", but what's native anyway, with mobile apps and web apps styling in many different ways. Even native Windows and macOS apps, which has a native look and feel, these days prefer to use a custom style, with most of the time following the design of vast empty white spaces and large controls, assuming everybody uses a 4k display.

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.

I love serifs and haven't found a good monospaced serif font yet. This one looks good but has some minor bugs like spacing and * not being centered vertically for the times you write OCaml or C comments. I'm trying it out anyway because I've been missing serifs in my terminal and editor for too long.

Was there a font thread you're referring to?

Do you write OCaml or C (comments) by any chance? I've often found it hard to discover a typeface that has

    (* this is a comment *)

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?

Sorry I can't because it's something that happens and doesn't stay. If you run Firefox 50 on Arch Linux, you will see what I mean.

This looks like an improved version of Luxi. I couldn't use Luxi Mono because O and 0 look the same, but this fixes that. I had been looking for a serif monospace font for a long time and this looks great.

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've actually been trying to find a PCF or TTF variant of that Sun font. If anyone can point me to it, I'd be grateful. Maybe in some folder of opensolaris or illumos?

Built 50.0 with cairo-gtk2 backend using it right now but something different with the font rendering in 50.0. For instance there's a weird washed-out effect of the text in this very same text control I'm writing the comment in which comes and goes with the amount of text changing/wrapping etc.

I love GTK2, but I can do without GTK3, seeing we're at 3.22 and it's still not as stable or regression free as GTK2.

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.

Good points. Just finished building firefox 50.0 with for cairo-gtk2 and trying it out now. Hope there are no crashes.

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.

Good to know. I thought it doesn't include and prevent the download of some DRM blobs.

I love 2.7's rendering engine and 49.0.2 looked great, but 50.0 looks washed out. Tried ESR 45.5.0 and it looks great again. I'm confused as to what may have happened from 49 to 50 that caused this.

I'm with you and cannot stand the way Opera does it but it also has a quick tab switching mode. I haven't encountered a single switch-with-preview implementation that didn't leave me with forced slowdown and delay of the action I was about to do. I also configure Firefox to not close the window when it's the last tab, which is hard-to-impossible to emulate in Chrome but is the default in Opera and Vivaldi.

In the past the GTK3 code path was tested only by Red Hat as the primary developer of all things GTK and GNOME. At that time, there was only a GTK2 build from Mozilla, and now instead of doing the same as Windows 32-bit/64-bit we're presented with just GTK3 support with the promise to obsolete the GTK2 code, while seemingly not considering the regressions of GTK3.

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.

Do you know how to run Firefox 50 with GTK 3.22.0 and the native Wayland backend? If I try it, it crashes instantly, and I was surprised to see gtk3 and gtk2 linkage in the xul libs. Any idea?

I'm glad you like it. This is one of those personal UX preferences that has you either one or the other camp. Am I right to assume you liked this from your past Opera use?

Did something change in font rendering with Freetype on Linux? While 49.0.2 with FreeType 2.7 looked the best (subjectively) I've seen any font rendering (including Windows 10 and OS X Snow Leopard (been a while)), something off with 50.0's rendering. I haven't enabled any custom render options, just your typical archlinux freetype 2.7 desktop. Time to get ESR and compare with that but would be great to hear back from others with a similar environment.

I had been using their binaries due to security updates and having to build at inopportune times for an hour or three (depending on machine), but like I wrote in a sibling comment, enabling the cairo-gtk2 backend resulted in crashes when trying to select a file with the gtk file dialog. So I bit the bullet and am struggling with the drawing regressions of GTK3.

For the same reason they haven't made 64-bit the default on Windows and provide two versions. There are many users for whom only one variant works reliably. If upstream, like in the case of cairo-gtk3, decides GTK2 is not supported anymore, it's a matter of chance whether your cairo-gtk2 build of Firefox works at all. For instance, for me 49.0.2 gtk2 local build on Arch crashes anytime I try to use the file dialog, while of course the file dialog of both GTK2 and GTK3 doesn't crash in other gtk apps on the same machine.

Somebody requested this and the reality has been ignored so far: https://bugzilla.mozilla.org/show_bug.cgi?id=1268234

My local cairo-gtk2 build of Firefox 49 reliably crashes anytime you try to use the GTK file dialog. Does it work for you (arch or gentoo)?

GTK3 itself has various regressions and is slower than GTK2 despite the architectural refactoring lending itself to a snappier experience.

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.

The programming and styling like a web page might be it and maybe it's also easier to consume random web feeds.

There's Electron-powered terminal emulators, so we're already there.