This Under-the-Radar AI Stock Could Double Your Money by 2028 https://www.byteseu.com/1292394/ #AI #ArtificialIntelligence #AttractivePrice #CreditRisk #InterestRates #Upstart #UpstartStock
This Under-the-Radar AI Stock Could Double Your Money by 2028 https://www.byteseu.com/1292394/ #AI #ArtificialIntelligence #AttractivePrice #CreditRisk #InterestRates #Upstart #UpstartStock
@mcc @dalias @whitequark @becomethewaifu
It didn't replace van Smoorenberg init+rc. It replaced Upstart. The existence of Upstart is the part of history that many people forget or gloss over.
van Smoorenberg init+rc always was a straw man. The Debian committee included it, but everyone acknowledged at the time that the main contenders were systemd, Upstart, and OpenRC.
@CursedSilicon @gettie mostly because #systemD (and it's competitiors) took all the right lessions:
And basically everyone (#OpenRC, #Upstart, etc. Even #LaunchD [the #init for #macOS that is literally the SystemD but before SystemD and by Apple] and #SMF [#Sun's SystemD for #Solaris] did that to allow for boot times in secinds, not minutes…
@BoydStephenSmithJr @dvandal @david_chisnall @strlcat
This reasoning is based upon a fallacious dichotomy. In the real history, Upstart existed and had a strong competing maintainership, to the level that the #Debian TC itself was nearly split down the middle on #RedHat/#Canonical lines, and the choice was *never* between van Smoorenburg init+rc and systemd.
It was between #Upstart and #systemd, the latter indeed being a reaction to the former, with #OpenRC as a late entrant.
@fabiscafe @okapi OFC @chesheer 's criticism is understandable on #FreeBSD given that #SystemD is inherenty focussed and intertwined with #Linux (just as it's Inspiration, #LaunchD, is intertwined with #macOS's Darwin/NeXTstep kernel).
And sadly there's nothing they (or anyone else) could've done unless they had multiplied suddenly and being able to keepcthe old tech stack maintainable.
OFC I wish for more diversity in solutions, but #Linux being #streamlined is what makes #portability across distros easier and boosted adoption as well as providing massive gains in solutions like #DXVK, #Proton and #Wine in general.
https://www.europesays.com/2049985/ 2 Millionaire-Maker Artificial Intelligence (AI) Stocks #AI #ArtificialIntelligence #MarketOpportunities #Roblox #Upstart
I enjoyed how spot-on you accidentally were. (-:
Interestingly, people still argue today (as you've probably seen in these threads) as if it were van Smoorenburg rc that was the other choice for Debian et al. back in 2014; which was in reality either Upstart or OpenRC. It's a very persistent erroneous dichotomy.
Right more than you know in one respect; but wrong in another.
#systemd came from #RedHat, not Microsoft; and the upstart was not Linux but a software package from #Canonical that was literally named "Upstart". (There's a whole backstory about the copyright licence that Canonical initially granted.)
Amusingly, Windows NT's Service Controller, its WININIT, and its Session Manager are three distinct things; not like systemd's architecture at all.
11 AI-Powered Fintech Companies Leading the Transformation of Financial Services.
See here - https://techchilli.com/fintech/top-ai-powered-fintech-companies/
@nuintari @stefano no, it's not inherently bad because if #SysVinit and all the.otherbthings were fine, noone would've even considered adoping #systemd.
https://infosec.space/@kkarhan/112660144122509736
Claiming "it's #RHEL's fault" also goes way too short, cuz they - like #SUSE and #Canonical - do weird stuff all the time.
OFC you can get non-systemd distros and for #embedded applications, the tradeoff of "space" vs. "complexity reconfiguring" stuff does make even a classic init script sufficient (i.e. some #InternetOfShit device that isn't expected to constantly switch WiFi networks doesn't need a config more complex than the config
txt from #RaspberryPiOS)...