The taxes are 'abusive' because they are sometimes very carefully "hidden". Ryan Air is wonderful compared to the nightmare called WizzAir.
The issues with WizzAir:
-Administrative fees of 9 Euro on each flight, for each passenger.
-Trolley bag (10 kg) an extra of around 60 Euros.
-Want have the same fare for 48 hours? Pay an extra 12 Euros.
-After that, checked in bag, is around 40 Euros per flight.
-Check in at the airport costs around 40 Euros.
-Online check in costs 5 Euros, and the say they mail you the tickets two days before.
-They don't mail you the tickets and they don't say anywhere you can only print the tickets on the same day of the flight (atrocious if the flight is at 6 am).
-You can get a refund for a cancelled flight, but the refund link cannot be found on their site. You have a post on Trip Advisor that points to that site.
-If you have paid for a small check in bag (10 kg) but bring that bag to the plane that's an extra 58 Euros (I can live with that).
-The boarding queue may stop for around 15 minutes, because a client needs to pay 58+58 Euros and the boarding attendant is unable to calculate such a complicated mathematical operation, needing the intervention of another boarding attendant (busy). That is a big no NO!
-Of course the web site has "bugs" and you may encounter "issues" that may force you to restart your session, specifically when asking for a refund...
-The "bugs" do not depend on the browser, or the OS (tested on Windows, OSX and Linux).
I don't think there is any evidence of this. Open Source tools fully support Lattice (low end) FPGAs, and support for Gowin FPGAs is not quite as mature.
It seems that many of the initial FPGA patents have expired, and that's why many small FPGA vendors are appearing. Please correct me if I am wrong.
I agree. IP theft is a bold claim, that is why I was asking for more citations.
Not only are the patent expired, but there are three projects that generate FPGA fabrics programmatically. FPGAs are extremely easy to construct as they are a repeating lattice.
The trouble is not supporting all the different Operating systems/compilers, as make can do that. The issue is when the OpenGL library location varies, even on the same OS/compiler set.
It's kinda both. The problem is that it doesn't really make sense to do all of this work to configure the build directly in Make, so if you need any kind of expensive detection (like calling pkg-config or testing if some library function is available) it's best to do it in a configure script. Most projects don't have terribly special needs, so it would be both overkill (too much effort) and insufficient (not supporting enough use cases) to do a lot of custom configuration code. So most projects wind up using something like Autoconf, which has already done a ridiculous amount of work to work on almost everything, supporting important use cases like out-of-tree builds and cross-compilation, but even then it has some unfortunate limitations.
As much as I don't think CMake is elegant or perfect by any means, CMake is nice because it does work, and there generally is a proper way to do things even if it's not always intuitive. And for how bad it can be, honestly, it's much less of a pain in my opinion than dealing with autotools, for many reasons. Just to be concrete about it, one thing I find really painful with autotools is trying to find the exact combination of versions that will actually work with a given project... With CMake, usually newer versions are always OK, and there's a decent focus on both backwards compatibility as well as explicitly declaring the required CMake version. There's more, but it's probably not worth getting into, as I don't think most people defend autotools as being particularly nice to use.
Some projects, like the Linux kernel, can definitely get away with Make and custom configuration, since a lot of higher-level general purpose tools are not really well-suited for their needs anyways. I feel like most projects (somewhere on the order of >99% of them) are not really in this boat.
OpenOCD is scriptable/configurable using a small variant of TCL called JimTcl.
https://openocd.org
https://jim.tcl.tk/index.html/doc/www/www/index.html