koffiezet · HackerTrans

قبل 3 أشهرdiscuss

No Belgium either, which I would have expected since tax rates here...

قبل 6 أشهرdiscuss

It however shifts a lot of the complexity of building the application to the distro maintainer, or a software maintainer has to prioritize for which distribution they choose to build and maintain a package, because supporting them all is a nightmare and an ever shifting moving target. And it's not just a distribution problem, it's even a distribution version/release problem.

Look at the hoops you sometimes have to jump through or hacks you have to apply to make something work on Nix, just because there is no standardization or build processes assume library locations etc. And if you then raise an issue with the software maintainer - the response is often "but we don't support Nix". And if they're not Nix/Nixos users, can you blame them?

If you've ever had to compile a modern/recent software package for an old distro (I've had to do this for old RH distro's on servers which due to regulations could not be upgraded) - you're in a world of pain. And both distro and software maintainers will say "not my problem, we don't support this" - and I fully understand their stance on that, because it is far from straight forward, and only serves a limited audience.

koffiezet

قبل 7 سنواتdiscuss

And this is why many people like me stick to Mac. Yes there's a solution for it on Linux, but no I don't want to look for it, maintain it, and at some point when a new 'best solution' is available keep up to date with all that...

koffiezet

قبل 7 سنواتdiscuss

I've had a few Macs - and my 2013 MacBook Air is still going very strong, but my 1yo MacBook Pro's keyboard has been replaced already, which is a serious issue, to the point where I doubt my next laptop will be a Mac again for that alone.

Other than that though, I think you might just have been unlucky. In professional env, I've seen bad units with pretty much every brand out-there. It shouldn't happen, but it does. In my experience, Apple will replace these without much fuzz, but their service, certainly towards businesses, is a far cry from that of for example Dell.

The Touch Bar complaint is just you not investing enough time with the system to get to know it. You can disable siri, and completely customise the touch bar.

koffiezet

قبل 8 سنواتdiscuss

Depends on the hardware and the anti-tamper measures. I've seen POS terminals where the pcb was completely encased in security plastic, where any attempted breach would wipe the internal security keys, which meant the hardware just became a useless. They're so sensitive that these things enter "tampered state" from time to time without any tampering. I developed software on these things - and bricked multiple devices by accident, even though this was 'development' hardware.

koffiezet

قبل 8 سنواتdiscuss

Certification. Worked in the same industry, and there were very strict both hardware and software requirements for POS software. Having gone trough credit-card audits, early EMV certification programs, and certification to place non-payment software next to payment software on such systems, I can tell you - it's no joke :)

koffiezet

قبل 9 سنواتdiscuss

This is probably also why Cygwin and even the WSL subsystem in general are a lot slower when running more complex shell scripts, which is typically spawns tons of processes.

I wrote a pretty simple shell script to test WSL process spawn speed, which loops over a simple echo piped to a grep, and add 1 to a counter until it reaches 1000.

On my windows machine, in a Linux VM, I consistently get times like this:

  real    0m1.381s
  user    0m0.073s
  sys     0m1.472s

On the same machine in WSL, I get results like this consistently:

  real    0m14.878s
  user    0m0.469s
  sys     0m12.109s

That is 10 times slower... I don't have cygwin installed anymore, but when I tested it initially when trying out WSL, it was even slower...

comments