Would you be comfortable sharing some numbers ? Old compensation vs New one ?
I'm asking because I recently moving to the EU and all I see here is 40-60K ranges and I'm curious if there are some engineers making 100K or something salaries
country/region matters more than just being in the EU. There is a big difference between fx spain-germany-switzerland-denmark. What is a decent pay in germany is low in switzerland or denmark.
Last time I profiled jq in my particular use case - querying large GeoJSON files - I discovered it spent practically all of its CPU in assert, and it went a lot faster when built with -DNDEBUG, but since I could not rule out that some of its asserts have side effects I went back to the upstream package.
I think beating the performance of jq would be very easy for anyone who set out with that as a goal. It also has its own internal strtod and dtoa which are easily beaten by ryu or C++'s from/to_chars, so I would start there after dumping the weird asserts.
Great idea to use Github for this, I've been working on https://app.trackwebpage.com/ which also tracks the changes on web pages and sends email notifications when changes happen (if you wanted to), it's totally free now, you can just sign up and track as much web pages as you want.
I don't know why you're getting down-voted, it's a legitimate question since the main page doesn't mention wine once.
It is a Wine frontend though, seems to also integrate wine-tricks for dependencies, DXVK and other things from the wine eco-system.
Bottles are isolated Wine environments, similar to containers or VMs. This allows you to install components (e.g. msxml3) to, and modify the configuration of that environment to make the program work without having it affect other applications.
Every WINEPREFIX defines its own Windows disk drives, so the filesystem is effectively sandboxed. Conventionally, there's (often? always?) a Z:\ drive which points to / on the Linux filesystem, but there doesn't have to be. You can add or remove drive mappings without any additional tools beyond WINE itself, and applications running under WINE can't see files that don't have drives mapped to them, afaik.
>Every WINEPREFIX defines its own Windows disk drives, so the filesystem is effectively sandboxed.
No, it is definitely not effectively sandboxed. You only need to access / instead of Z:. Wine has no sandbox mechanisms built in. It is also a fairly large codebase which definitely has a bug or two that could be exploited to get around such mechanisms if they existed.
To effectively sandbox, you need the kernel's help. Linux offers namespaces and control groups.
The way you use these comfortably behind a layer of abstraction is through containers. Bottles uses flatpak for the purpose.
> No, it is definitely not effectively sandboxed. You only need to access / instead of Z:. Wine has no sandbox mechanisms built in. It is also a fairly large codebase which definitely has a bug or two that could be exploited to get around such mechanisms if they existed.
If you don't have Z:\ enabled, how do you actually access those Unix-like paths? When I launch a WINE command prompt in a prefix with no Z:\ enabled, I get:
wine: could not open working directory L"unix\\home\\pxc\\", starting in the Windows directory.
Microsoft Windows 6.1.7601
unix\home\pxc>dir
Syntax error
unix\home\pxc>cd ..
unix\home>dir
Syntax error
and so on. What Windows APIs are Windows programs supposed to use that will let them see parts of the Linux filesystem that are not mapped as Windows drives in WINE?
> To effectively sandbox, you need the kernel's help. Linux offers namespaces and control groups.
> The way you use these comfortably behind a layer of abstraction is through containers. Bottles uses flatpak for the purpose.
This is an improvement for sure, but I've never, ever had some WINE program run amok on my hard disk outside of the drives letters defined for it in the WINE configuration.
Thanks for pointing out the more thoroughgoing sandboxing that Bottles uses beyond just the WINE drive mapping, though.
WINE will automatically create the WINEPREFIX directory for you if it doesn't exist, so it's even simpler than that :)
The real value of bottles (or crossties, or PlayOnLinux definitions, or whatever) in in encoding all the tips and tricks required to get some piece of software running under WINE in a form that lends itself to easy distribution and automation.
I'm asking because I recently moving to the EU and all I see here is 40-60K ranges and I'm curious if there are some engineers making 100K or something salaries