Edit/Add: cf the part about language rules in this comment from a person who says they're a former bazel developer: https://news.ycombinator.com/item?id=35477309
205 karma · joined February 27, 2023
Edit/Add: cf the part about language rules in this comment from a person who says they're a former bazel developer: https://news.ycombinator.com/item?id=35477309
Practical as it may be, that's not a natural right but merely a physical possibility. More generally, the concept of natural rights - except for a very narrow niche of special subjects closely centered on the individual's own life and bodily autonomy - is a shortcut to total subjectivity at best. And even for that very narrow niche, the "rights" part is a normative civilizational convention/construct, whereas nature conspicuously ignores such "rights" (as do humans for the most part when it comes to other species)
That being said, I've way too often encountered people for whom git oddly only exists in the form of Github, to the point of those being synonymous to them. The concept of a self-hosted repo seems totally foreign to them, and the only local git trees they have is what their IDE created for them in the directory of their checked out or created source project. It's weird, but such people exist… and lots of them.
though that too comes with its own set of privacy issues, especially when done at a larger scale with strangers on the internet as opposed to just with your personally known and trusted buddies… and rare are the people for whom the latter happen to contain enough people with strong enough hardware that that pool would be sufficient.
Practical as it may be, that's not a natural right but merely a physical possibility. More generally, the concept of natural rights - except for a very narrow niche of special subjects closely centered on the individual's own life and bodily autonomy - is a shortcut to total subjectivity at best. And even for that very narrow niche, the "rights" part is a normative civilizational convention/construct, whereas nature conspicuously ignores such "rights" (as do humans for the most part when it comes to other species)
That would be somewhat unfair towards MOSFETs and their quite versatile spectrum of applications though: MOSFETs are actually also being used for lots of linear applications. For high power linear stuff, they have to be designed slightly differently than cheaper MOSFETs designed solely for switching, so as to not run into ETI (electro-thermal instability) problems, but it's not uncommon. So, maybe "an ideal transistor for switching/digital purposes"?
* other such very practical consequences that I didn't even mention in my last comment include the following classic: when you make your product and business dependent on another (external) product, it is crucial to have some sound risk assessment: what about the bus factor of that external provider? What if they close? What if they suddenly change their licensing terms to the worse? What mess do I risk to find my business in and how hard is it to get out of that situation? With a permissive open source license, the maintained collective development can go on, whatever happens to the original developers and however they decide to change their course. With a closed license, the users and/or their businesses are doomed.
So the one part where I agree is that merely "getting the job done" for its technical part is not the ONLY thing that matters and not the ONLY relevant selection criterion. There are other very relevant and very pragmatic make-or-break criteria/issues, such as legal and business-critical questions like those that come in consequence of the license… not of their "label", but of their actual content.
That being said, there are actual factors for which the US might indeed plausibly be the best location choice specifically for most AI companies in the current hype context. For example funding:
* while there is also some proportion of actually promising sustainable business models based on AI, the fact is that a very large proportion of AI companies are surfing on a hype/bubble and have somewhat of an exit strategy (e.g. being bought by some bigger player) but not a business model that would otherwise sustainably stand on its own feet.
* the US is arguably indeed the best location for most high-risk ventures in need of big funding… including and especially so for hype/bubble surfers. Nowhere else can you find that much early investment money with such a willingness to take risks and to ride a hype/bubble. For most AI companies, the US as a location means they are able to raise more at a better (for the founders) valuation.
And if I want "Access to sources, 1 year", I have to choose between one of a number of commercial license options that for cross-platform (*) range from "INDIE+" (limited to "companies having three or less employees") for 620 US$ + 310$ per following year(s), via "BUSINESS+" (to escape the limit on employee count) for 2720 US$ + 1720 US$ per following year(s)… both of which still require me to mention “this code contains Sciter engine” in “about” screens or the like… a requirement which only goes away with the "ENTERPRISE++" option which is on a "Please contact us for the price" basis… as is the "OEM/FIRMWARE" option for embedded stuff.
(*) cross platform, as per https://sciter.com/sciter/crossplatform/ meaning Windows, Mac OSX and Linux / other Unixes (GTK3 based), whereas mobile OSes are mentioned as:
> "Other OSes: In principle Sciter can be ported to any OS that has graphical primitives ready. For example Sciter can be compiled to run on iOS. Or with some effort to work on Android using either existing Cairo backend or Skia graphics layer"
In our case, even aside from the the licensing and the "with some effort" for Android that makes me wary and that I can't evaluate for lack of access to the source code, It just so happens that we have a number of other libs to integrate, some of which add their own rendering (which requires access to e.g. a Vulkan context, not merely HTML/CSS or other high-level UI elements)… so that I can't justify to blindly pay that much upfront before even having a possibility to evaluate the source code first, just on blind hope, for a UI toolkit that may or may not, depending on the source code that I don't have access to otherwise, turn out to very hard or even impossible to integrate with the other libs.
Sorry, but I'll have to pass.
What I did mean with "native" in my last comment was simpler than that: I just meant "native" as in: not a web app or similar detached via abstraction layers and bundled with a browser that interprets it, but a natively compiled app that is directly linked to the rendering GUI lib. That would even be enough for me. But even for that, I find there isn't a satisfying cross-platform solution.
… no, what's really sad is that there is still no satisfying solution to the problem that XUL was trying to solve, i.e.: the need for a native cross-platform GUI lib; and apart from the special situation of the likes of Mozilla (where a Web browser engine is the central major part of the product and its UI anyways so it makes sense that they use that engine for what little and relatively simple and not performance-sensitive GUI is added to or around the browser view as well)…
… apart from very few such cases, Web isn't the answer either. In particular, Electron apps suffer from the unnecessarily enormous added deadweight of the de-facto-integrated browser and while its performance is good enough for simple use cases, it quickly becomes limiting when the UI gets more complex or when you need to integrate stuff that is performance-sensitive or requires a different rendering.
There are a couple cross-platform UI libs out there, but compared to other domains (where it's often easier to find a satisfying lib), I find that they all have some major problems, in particular:
* Qt, which did look promising in its Nokia days, went down a sore downhill shitslope since Microsoft mole Stephen Elop threw it out to Digia, where (especially since splitted out as QTCOM) the licensing focus of Qt has shifted from "make it more open and permissive so as to gain wide dev community/traction" (the strategy under Nokia) to "try to force devs into commercial licensing schemes and monetize to the max you can milk out of it while it lasts"… and as a consequence, more and more previously Qt-oriented devs looking elsewhere.
* neither GTK nor Flutter are satisfying answers either.
I think there is really a big window of opportunity and gap to be filled by a new modern cross-platform UI toolkit with wide portability (at least Windoze, Linux, MacOS, iOS, Android, embedded; though a Vulkan-based renderer can be made to run pretty much anywhere), a permissive open source license, a C interface/wrap to allow a wide programming language binding support, and an easily extensible and themable set of basic widgets.
What I'd like to see come up is a distribution that in addition to immutability provides the following:
1. separate install prefix directory for each currently installed package version (except for a minimal immutable core), thus allowing the coexistance of difference versions … and making access control policies practicable without the mess they are on a filesystem where there is a wild and hard to separate mix of stuff from lots of packages and other origins.
2. a modern and secure binding/mapping mechanism between the package install prefixes and what each of those and the user are supposed to see (dependig on profiles that can vary not only between packages but also e.g. between different users, different use cases etc). The "modern and secure" part meaning: not an old symlink based thing but something that uses the modern isolation techniques, cgroup/namespace, bind mounts, and the other mechanisms the kernel provides today.
3. a nice frontend for making the administration of those package-versions/mappings and the setting of access control policies based on them easy, with a sensible set of distribution curated profiles for the mappings, isolation settings and access control policies.
Parts of that already exist, e.g:
1. (the per-package version install prefix) has been spearheaded by Nix/NixOS … (but it's missing 2. and 3.)
2. the secure isolation, cgroups, namespaces, bind mounts etc part of 2. has been spearheaded by Containers… but their simple layering structure doesn't allow to map the more complex depndency graph of a package management system.
^ found the AI-based Chatbot
That being said, I suspect that the following quote would be a major hindrance for a lot of developers looking for a rendering engine:
> "This code base will not work on MacOS. Linux and Windows should both be fine so long as the graphics driver supports OpenGL 4.6 (…)"
These days, most projects/developers looking for a 3D rendering engine - including those who, like me, don't have any sympathy left for Apple and their business practices - will need a wide cross-platform compatibility including MacOS and mobile (both android and iOS). So the point "Porting the renderer to Vulkan" that you list under "Future of StratusGFX" does indeed seem like a priority.
In that same vein, I'd point out that given the very large proportion of end users that have relatively weak hardware, especially on the GPU side, and even more so with the ongoing tendencial shift from desktop to mobile, it is crucially important to keep in mind that while maximal realism capabilities are indeed an important goal, the engine also needs to have good fallback compromise capabilities for less powerful hardware, i.e. cutting back on the most computationally expensive parts and details while still delivering a decent enough result at a good enough speed.
And that's just for projects that happen to be FOSS anyways. The thing is: very few software developers have the luxury of releasing ALL their software projects as FOSS. Something has to pay the rent and food. There are a few select domains where developing FOSS software can be a the base for a business model that pays a sustainable living… but those tend to inherently have a very small intersection with the kinds of software typically developed with Qt.
And huge complex frameworks aren't something a developer changes all the time like underwear. It's something devs tend to stick to, because it takes quite a significant time investment to master and to build your workflow, tooling etc. around. In other words: developers largely tend to do their FOSS projects in the same framework that they use for the work projects that pay their rent and food.
If big framework A disqualifies itself for the latter and gets replaced with framework B for that, chances are that their FOSS projects will be centered around framework B as well and no longer around framework A. As long as Qt was a viable option for work, it made perfect sense to center one's FOSS efforts around Qt as well and thus around KDE, which is the primary Qt-based Desktop. But since the licensing situation of Qt deteriorated, that is no longer the case. So that's another factor where it impacts KDE.
No, they are both about relative increases. I didn't even write about absolute increases because (unlike relative increases, where the article makes a mistake) absolute increases were the part that the article got right: a rise from 5% to 15% would be an (absolute) increase of 10% … just like the article says.
> 300% relative difference just means 300/100 = 3x
…My point was: 300% relative INCREASE (i.e. positive relative difference) means that it's the DIFFERENCE (increase) between the initial value and the end value that is 300% RELATIVE TO the initial value (thus the end value being 400% of the initial value), not that the end value is 300% of the initial value (which would only be a 200% relative increase).
Let's take, to better illustrate the point, an example with a relative increase below 100%. Let's go with an example with 40% relative increase. So let's say:
* in the reference year, your company made a profit of 5 million dollars out of a revenue of 100 million dollars, i.e. a profit margin of 5%.
* the next year it still made a revenue of 100 million dollars but managed to be more profitable, making a profit of 7 million dollars i.e. a profit margin of 7%.
* The ABSOLUTE increase of the profit margin is (7%-5%)=2%,
* The RELATIVE increase of profit margin is the absolute increase of profit margin divided by its initial reference value i.e. (7%-5%)/5% = 40%.
And my point is: having a 40% relative increase of profit margin means that your end profit margin is 40% higher relative to your initial reference profit margin and is thus (100%+40%)=140% of your initial reference profit margin, not that your end profit margin is 40% of your initial profit margin… which would be a 60% relative DECREASE (i.e. -60% relative increase) of the profit margin.
> "Note that there are two ways to calculate increases. We can measure an increase in absolute terms, e.g., a rise from 5% to 15% of teens with a diagnosis is a ten percentage-point increase, or we can report it in relative terms, e.g., a rise from 5% to 15% is a 300% increase, relative to the anchor point"
Uhm… maybe in an "alternative mathematics" universe? Where I learned math, an increase from 100% of the anchor value to 300% of the anchor value is not a relative increase of 300% but of 300%-100%=200%.
In contrast, A "300% increase, relative to the anchor point" would be adding 300% of the anchor value to the 100% of it that it already has, i.e. resulting in an end value of 400% of the anchor value. So in the case presented by the article quote, to come back to the absolute terms, it would be a rise from 5% to 20%, not to 15%.
But it goes further: even for what is still FOSS (i.e. the non-LTS), the licensing gets progressively more and more restrictive: * whereas Nokia made Qt available under the relatively permissive LGPL2.1, that since changed to a mixture of LGPL3 and GPL, with a clear shift towards the latter: that is: for new modules, you typically only have the choice between commercial and GPL. Unless you are content with that for all of your software projects, that's quite the problematic constraint.
That being said, it seems like an almost inescapable consequence of the fact that the software itself is also data and as such subject to a similar problem: in times of ubiquitous high-speed internet access where you can't protect software (data) from being widely copied and shared over the network once anyone else gets hold of it, the only simple and reliable way for a software company to keep control over the distribution of their software (and thus its monetization) is to never share it in the first place but only provide access to it as a service.
So in the end, the shift from locally installed software to remote services kinda comes down to the fact that most users don't have the same level of awareness or care about their own data and keeping control over it as the software/internet service companies have for their data (e.g. software).
In all fairness: Gnome was absolutely great at its beginnings… until the clique around Havoc Pennington took over and decided they know better than the users what's good for them and ruined Gnome… thus earning them the affectionate title "interface nazis" dished out by Linus Torvalds.
https://www.cio.com/article/220271/11-technologies-that-tick...
> after the Qt license issues were sorted out
Much as I'd agree that GTK has proven to not be the way (either), I don't see the "Qt license issues" as being "sorted out" at all.
It did look like it for a short while after Nokia bought Trolltech and made Qt available under LGPLv2.1, but that didn't last long: Shortly after, Microsoft managed to place their mole Stephen Elop onto the CEO seat of Nokia, and Elop methodically ruined Nokia in preparation for a Microsoft takeover and threw out Qt (which represented cross-platform, a concept Microsoft always saw as as a threat to their business model), replacing it with the ill-fated Windows Phone platform. Under Digia, and even more so once splitted out as QTCOM, The licensing focus of Qt has shifted from "make it more open so as to gain wide traction" (the strategy under Nokia) to "try to force devs into commercial licensing schemes and monetize to the max you can milk out of it", and it has been a sore downhill slide into a shitty situation.
The "Qt license issues" we have today aren't the same as way back then in the QPL days of early KDE-vs-Gnome forum wars, but they are at least as bad imho. A lot of developers who used to develop mainly with Qt (me included) have since jumped ship because of that and prefer to avoid Qt too now, though the sad reality is that while there are better alternatives depending on the project, there isn't really a good free cross-platform allround alternative for Qt either. I think there is really a big window of opportunity and gap to be filled by a new modern cross-platform UI toolkit.
"Mondschein Sonata"? WTF Apple? Not only is that factually wrong, but… that's not even German - neither as a whole, nor the "Sonata" nor the space (Deppenleerzeichen). Maybe Apple should ask someone else than Siri or a marketing intern to write texts with factual claims outside of their fields. The actual popular German sobriquet for that Sonata is "Mondscheinsonate". As for "Sonata", that's part of the (Italian) title of its first published edition: "Sonata quasi una Fantasia".
Lemme guess: you generated that prompt by writing it in English and asking GPT (or Google translate, but not DeepL) for a German translation?
really? that's a nice gesture… so where can I download it?
nCuLitho … I wonder how Spanish-speaking people would like that one. Or maybe that added letter makes it too long anyways and it could be shortened to… nCuLo