#lesley linux

[pandamugger]

i feel like such a nerd ass redditor 😞

all i wanna do is think and talk about my linux and the shit i’m figuring out, i’m having so much fun with this. It’s like research and art and a puzzle and it’s so cool!!!!!

I can do anything I want!!!!

[pupsmailbox]

STARTING WITH L

MASCULINE︰ lachlan. laird. lake. lamar. lambert. lamont. lance. landen. landon. landry. landyn. lane. lanford. langston. lanny. larry. laurence. lavern. laverne. lawrence. lawson. layne. layton. laz. leandro. ledger. lee. legacy. legend. leighton. leith. leland. len. lenard. lennie. lennon. lennox. lenny. lenox. leo. leon. leonard. leonardo. leonel. leonidas. leopold. leroi. leroy. les. lesley. leslie. lester. letter. lev. levi. levon. lew. lewin. lewis. lex. leyton. liam. lincoln. linford. link. linton. linus. linwood. lionel. liu. lloyd. logan. london. loren. lorenzo. lorin. lorn. lorne. lorrin. lou. louie. louis. lovel. lovell. lowell. loyal. loyd. luca. lucas. lucca. lucian. luciano. lucius. lucky. luis. luka. lukas. luke. luther. lyall. lyle. lyndon. lynn. lynton. lynwood. lyric.

FEMININE︰ laila. lainey. lakelynn. lana. laney. lara. laura. laurel. lauren. layla. laylanni. leah. leandra. leanna. leena. legacy. leia. leighton. leila. leilani. lena. lennon. lennox. leona. leslie. letter. lexi. lexie. leya. leyla. lia. liana. libby. liberty. lila. lilah. lilian. liliana. lilianna. lilith. lillian. lilliana. lillie. lilly. lily. lina. lindsey. lisa. liv. logan. lola. london. londyn. lonnie. loralai. lorelai. lorelei. louisa. louise. lucia. luciana. lucille. lucy. luisa. luna. lyanna. lydia. lyla. lylah. lynnette. lyra. lyric.

NEUTRAL︰ labyrinth. lace. lacy. lai. laiken. laine. lake. laken. lali. lam. lamar. lamp. lance. landry. landyn. lane. lang. lark. larkin. latch. lau. laurel. laurence. laurent. lavan. lave. lavender. lavey. lawan. lawin. layken. layne. layton. lazarus. le. leaf. leather. ledger. lee. left. legaci. legacy. legend. lei. leigh. leighton. leis. leith. lek. lemar. len. leni. lennie. lennon. lennox. lenny. lenox. leo. leon. leone. lesley. leslie. less. letter. levi. levian. levy. lex. lexi. lexington. leyton. li. liam. lian. liann. liberty. lie. liel. life. lilac. lille. lilo. lily. limit. lin. linae. lind. linde. linden. lindi. ling. lingxi. link. linn. linux. lio. lione. lior. lithium. liyan. lo. lock. logan. logic. lois. lok. loki. lolan. london. lone. lonnie. loose. loren. lorin. lost. lotus. lou. loui. louie. louis. love. loyal. loyalty. luca. lucca. lucid. lucka. lucky. ludo. lue. lui. luka. lull. lumi. lumière. lunar. lune. lurch. lurk. luscious. lutfi. lux. ly. lykke. lyn. lyndon. lynn. lynx. lyre. lyric. lyrik. lý.

[coldstarlightharmony-blog]

Craig Federighi talks open source Swift and what's coming in rendition 3.0 Quick is accessible under an Apache permit, and source similarity is coming soon.

When Apple divulged Swift 2.0 at WWDC back in June, one of the greater declarations was that the dialect would go open source before the year's over. The time has come—­just fourteen days before its deliberate due date, Apple has propelled Swift.org and is discharging a major lump of code (and some direction for Swift 3.0) to general society.

Ars had an opportunity to talk with Apple Software Engineering SVP Craig Federighi about Swift's openness, the future advancement of the dialect, and when designers can anticipate that it will develop and settle down.

The rudiments

Quick is being discharged under an Apache 2.0 permit, which is by chance a similar permit Microsoft utilized when it publicly released a major piece of its .NET structure a year ago. The venture will be facilitated on GitHub and will incorporate the compiler, the LLDB debugger, the REPL order line condition, the standard and center libraries, and code from supporting undertakings. New to Swift (and furthermore open source) is the Swift Package Manager, depicted as an "early-arrange extend" that will fill in as a storehouse for Swift modules and will advance with contribution from the group.

A large portion of that is secured under the standard Apache permit, yet Federighi reveals to us that Apple has additionally incorporated a more tolerant runtime special case, "so that on the off chance that you manufacture code in Swift and parts of the Swift library are created in your own particular code, you don't need to give attribution all things considered."

Apple engineers taking a shot at Swift will begin utilizing the GitHub repos, building up the dialect out in the open.

"The Swift group will grow totally in the open on GitHub," Federighi told Ars. "As they're working everyday and making changes to the dialect, including their work on Swift 3.0, the greater part of that will be going on out in the open on GitHub."

So as opposed to getting a major Swift 3.0 information dump at WWDC 2016 in the late spring and afterward delving into the Xcode betas and adjusting, engineers can as of now discover a "development report" on the Swift site that maps out where the dialect is going in its next real form.

While the code itself will live on GitHub, the group encompassing Swift will locate its home on Swift.org. Here, engineers will have the capacity to get to a bug-announcing and - following framework, mailing records, a Swift building blog (something Apple as of now offers), group rules, Swift instructional exercises and documentation, and designer and API outline rules. As such, these are the sorts of things you see on the pages for any open source programming dialect.

Stages: Official OS X and Linux bolster, group bolster for the rest

Formally bolstered ports of Swift as of now incorporate those for Apple's stages and furthermore Linux, which is the thing that the organization guaranteed back in June when it made the first declaration. That makes a considerable measure of progress for Swift designers (who will by and large as of now be running OS X) and engineers when all is said in done (who most likely utilize Linux more broadly than the general people). Apple's Linux apparatuses incorporate support for the early bundle administrator, the LLDB debugger, and the REPL charge line condition.

With respect to different stages, including Windows, in any event at first Apple will incline toward the group to give that support if there's interest for it.

"[Windows support] wasn't something that as far as us catalyzing this underlying discharge that we needed to go up against specifically," Federighi let us know. "We think Linux and obviously our stages give an incredible establishment to begin. Yet, we're exceptionally open to ports to different stages being added to the center venture, and positively given that LLVM, Clang, and LLDB, which are foundational innovations to Swift, are now accessible, as of now ported to Windows. I believe it's predictable that somebody in the group, regardless of whether drove by Microsoft or others, would do that port."

Why open up Swift?

In publicly releasing Swift, Apple has two fundamental objectives as a main priority. The first and most clear is to make Swift code more convenient and flexible, empowering its utilization in ventures outside of applications for Apple's stages.

The organization's long haul vision is significantly more yearning. "We think [Swift] is the means by which truly everybody ought to programme for the following 20 years," Federighi told Ars. "We believe it's the following significant programming dialect.

"Various designers, including endeavor engineers like IBM, at an opportune time as they started building up their portable applications in Swift, truly needed to have the capacity to take the gifts that their engineers were creating and even a portion of the code and have the capacity to convey it in the cloud, for example," Federighi proceeded. "We thought the most ideal way [to empower that], at last, was open source."The other objective is instructive: when engineers put energy into learning Swift (or when instructors set aside the opportunity to show it), Apple needs those aptitudes to be all the more extensively relevant.

"We're working with instructors, and numerous educators are extremely keen on showing Swift since it's such an expressive dialect, to the point that's such an extraordinary approach to present a wide range of programming ideas," Federighi said. "Furthermore, empowering it as open source makes it feasible for them to fuse Swift truly as a component of the central subjects."

When we talked with engineers about the primary year of Swift back in June, Swift's openness to instruction was unquestionably a noteworthy offering point. As valuable as Swift may be to impart programming thoughts, it's at last more helpful to have the capacity to take that learning and utilize it in numerous spots.

"When you're first taking in, it's more often than not about whether your code orders or not, and I like that Swift won't let you arrange sometimes without beginning to think about some of those things," said Lesley Baker, an iOS engineer and an instructor with App Camp for Girls. "Ideally that will prompt a superior comprehension of what's happening and not be excessively disappointing."

All things considered, as indicated by Swift.org, engineers submitting applications written in Swift to one of Apple's application stores still should utilize Xcode on a Mac.

In what manner will this change the dialect? What's more, when will Swift balance out?

Making Swift open source and growing new forms out in the open makes it less demanding for engineers to perceive what Apple is doing, yet it additionally makes it less demanding for them to add to the venture straightforwardly. Apple says that engineer criticism has as of now been instrumental in creating components and taking the dialect from beta to 1.0 to 2.0, yet in any event hypothetically, the organization will never again be the sole mediator of what does and doesn't wind up in the dialect. Engineers can submit pull solicitations, and Swift.org traces the procedures that ought to be utilized when designers need to propose changes.

"When you take a gander at a significant number of the dialect includes that we reported in Swift 2.0 that are presently out regarding mistake taking care of and the protect explanations, accessibility, controls, et cetera, these were altogether in light of that discourse that has been progressing with designers who've been receiving Swift in their genuine applications," Federighi said. "With Swift being created out in the open in open source, we believe it will develop that association significantly."

Quick is as yet a youthful dialect, and too got as it has been, that still makes disappointment for designers attempting to create and look after code. Quick 1.x code made six or 12 months prior won't not order today in current variants of Xcode, an issue Apple is certainly mindful of.

"We've been exceptionally open in saying we would give source advancement devices to our designers," Federighi told Ars, "so on the off chance that they compose their Swift code and after that as we develop the dialect we'll give the devices to help them propel their source code."

Be that as it may, the organization likewise has arrangements to settle the more extensive issue, a settle that is just going to wind up noticeably more imperative now that more designers can contribute all the more specifically to the dialect. One of Apple's objectives for Swift 3.0 is source similarity going ahead so Swift code that is composed may should be recompiled as the dialect keeps on advancing, yet it should be revamped or changed less regularly or not in the slightest degree.

What's more, where does this leave Objective-C?

Concerning Objective-C, Swift's recently discovered openness doesn't transform anything about its position in Apple's biological community. It has been around for a considerable length of time, it's as yet being utilized to code numerous applications running on Apple's stages (counting Apple's own), and Apple is as yet adding to it as it esteems essential. Yet, Swift is plainly where the greater part without bounds speculation is going, and Apple would incline toward that designers beginning new activities begin them in Swift if conceivable.

"Objective-C is not leaving. Regardless we adore Objective-C as a dialect; we still especially rely on upon Objective-C and do a colossal measure of work in Objective-C here inside at Apple," Federighi told Ars. "We'll be supporting Objective-C and proceeding to advance it as important to fit into this developing world. We do surmise that Swift is the dialect that we prescribe for new engineers to our stage who are contributing for the future and building new applications. We think Swift is totally the opportune place to begin. Be that as it may, we'll keep on maintaining, progress, and bolster Objective-C to the extent we can see."

That announcement for the most part tracks with how designers have revealed to us they're utilizing Swift and Objective-C. Some are staying with it due to nature or in light of the fact that they would prefer not to blend their Swift code with Objective-C code, however more regularly we've been informed that new undertakings and new pieces of old activities are being composed in Swift.

[malto444-blog]

Craig Federighi talks open source Swift and what's coming in adaptation 3.0 Quick is accessible under an Apache permit, and source similarity is coming soon.

When Apple revealed Swift 2.0 at WWDC back in June, one of the greater declarations was that the dialect would go open source before the year's over. The time has come—­just half a month prior to its deliberate due date, Apple has propelled Swift.org and is discharging a major piece of code (and also some direction for Swift 3.0) to the general population.

Ars had an opportunity to visit with Apple Software Engineering SVP Craig Federighi about Swift's openness, the future advancement of the dialect, and when designers can anticipate that it will develop and settle down.

The fundamentals

Quick is being discharged under an Apache 2.0 permit, which is by chance a similar permit Microsoft utilized when it publicly released a major lump of its .NET system a year ago. The venture will be facilitated on GitHub and will incorporate the compiler, the LLDB debugger, the REPL order line condition, the standard and center libraries, and code from supporting activities. New to Swift (and furthermore open source) is the Swift Package Manager, portrayed as an "early-organize extend" that will fill in as a store for Swift modules and will advance with contribution from the group.

The vast majority of that is secured under the standard Apache permit, yet Federighi reveals to us that Apple has likewise incorporated a more lenient runtime special case, "so that in the event that you assemble code in Swift and parts of the Swift library are produced in your own code, you don't need to give attribution all things considered."

Apple engineers chipping away at Swift will begin utilizing the GitHub repos, building up the dialect out in the open.

"The Swift group will grow totally in the open on GitHub," Federighi told Ars. "As they're working everyday and making alterations to the dialect, including their work on Swift 3.0, the greater part of that will be going on out in the open on GitHub."

So as opposed to getting a major Swift 3.0 information dump at WWDC 2016 in the late spring and after that delving into the Xcode betas and adjusting, designers can as of now discover an "advancement archive" on the Swift site that maps out where the dialect is going in its next significant variant.

While the code itself will live on GitHub, the group encompassing Swift will locate its home on Swift.org. Here, engineers will have the capacity to get to a bug-revealing and - following framework, mailing records, a Swift building blog (something Apple as of now offers), group rules, Swift instructional exercises and documentation, and designer and API plan rules. As it were, these are the sorts of things you see on the pages for any open source programming dialect.

Stages: Official OS X and Linux bolster, group bolster for the rest

Formally upheld ports of Swift presently incorporate those for Apple's stages and furthermore Linux, which is the thing that the organization guaranteed back in June when it made the first declaration. That makes a great deal of progress for Swift designers (who will for the most part as of now be running OS X) and engineers as a rule (who presumably utilize Linux more broadly than the general people). Apple's Linux apparatuses incorporate support for the incipient bundle supervisor, the LLDB debugger, and the REPL charge line condition.

Concerning different stages, including Windows, in any event at first Apple will incline toward the group to give that support if there's interest for it.

"[Windows support] wasn't something that as far as us catalyzing this underlying discharge that we needed to go up against specifically," Federighi let us know. "We think Linux and obviously our stages give an awesome establishment to begin. In any case, we're extremely open to ports to different stages being added to the center venture, and absolutely given that LLVM, Clang, and LLDB, which are foundational innovations to Swift, are as of now accessible, as of now ported to Windows. I believe it's predictable that somebody in the group, regardless of whether drove by Microsoft or others, would do that port."

Why open up Swift?

In publicly releasing Swift, Apple has two fundamental objectives as a primary concern. The first and most evident is to make Swift code more convenient and adaptable, empowering its utilization in undertakings outside of applications for Apple's stages.

The organization's long haul vision is significantly more aggressive. "We think [Swift] is the means by which truly everybody ought to programme for the following 20 years," Federighi told Ars. "We believe it's the following real programming dialect.

"Various designers, including undertaking engineers like IBM, at an early stage as they started building up their versatile applications in Swift, truly needed to have the capacity to take the abilities that their designers were creating and even a portion of the code and have the capacity to convey it in the cloud, for example," Federighi proceeded. "We thought the most ideal way [to empower that], eventually, was open source."The other objective is instructive: when designers put energy into learning Swift (or when instructors set aside the opportunity to show it), Apple needs those abilities to be all the more comprehensively appropriate.

"We're working with instructors, and numerous educators are extremely keen on showing Swift since it's such an expressive dialect, to the point that's such an incredible approach to present a wide range of programming ideas," Federighi said. "What's more, empowering it as open source makes it feasible for them to join Swift truly as a major aspect of the central subjects."

When we talked with engineers about the principal year of Swift back in June, Swift's openness to instruction was certainly a noteworthy offering point. As helpful as Swift may be to convey programming thoughts, it's at last more valuable to have the capacity to take that learning and utilize it in numerous spots.

"When you're first taking in, it's normally about whether your code incorporates or not, and I like that Swift won't let you gather now and again without beginning to think about some of those things," said Lesley Baker, an iOS engineer and an educator with App Camp for Girls. "Ideally that will prompt a superior comprehension of what's happening and not be excessively disappointing."

All things considered, as per Swift.org, engineers submitting applications written in Swift to one of Apple's application stores still should utilize Xcode on a Mac.

In what capacity will this change the dialect? What's more, when will Swift balance out?

Making Swift open source and growing new forms out in the open makes it less demanding for engineers to perceive what Apple is doing, yet it additionally makes it less demanding for them to add to the venture specifically. Apple says that designer input has as of now been instrumental in creating components and taking the dialect from beta to 1.0 to 2.0, however at any rate hypothetically, the organization will never again be the sole referee of what does and doesn't wind up in the dialect. Engineers can submit pull solicitations, and Swift.org plots the procedures that ought to be utilized when designers need to propose changes.

"When you take a gander at a considerable lot of the dialect highlights that we declared in Swift 2.0 that are currently out regarding mistake taking care of and the protect articulations, accessibility, controls, et cetera, these were altogether in view of that discourse that has been progressing with designers who've been embracing Swift in their genuine applications," Federighi said. "With Swift being created out in the open in open source, we believe it will extend that collaboration significantly."

Quick is as yet a youthful dialect, and also got as it has been, that still makes dissatisfaction for designers attempting to create and look after code. Quick 1.x code made six or 12 months prior won't not aggregate today in current renditions of Xcode, an issue Apple is certainly mindful of.

"We've been exceptionally open in saying we would give source advancement devices to our engineers," Federighi told Ars, "so on the off chance that they compose their Swift code and after that as we advance the dialect we'll give the instruments to help them advance their source code."

Yet, the organization likewise has arrangements to settle the more extensive issue, a settle that is just going to wind up noticeably more essential now that more designers can contribute all the more straightforwardly to the dialect. One of Apple's objectives for Swift 3.0 is source similarity going ahead with the goal that Swift code that is composed may should be recompiled as the dialect keeps on advancing, however it should be revamped or changed less oftentimes or not in any way.

What's more, where does this leave Objective-C?

With respect to Objective-C, Swift's freshly discovered openness doesn't transform anything about its position in Apple's biological community. It has been around for a considerable length of time, it's as yet being utilized to code numerous applications running on Apple's stages (counting Apple's own), and Apple is as yet adding to it as it esteems vital. However, Swift is unmistakably where the vast majority without bounds venture is going, and Apple would lean toward that designers beginning new activities begin them in Swift if conceivable.

"Objective-C is not leaving. Regardless we cherish Objective-C as a dialect; we still especially rely on upon Objective-C and do a colossal measure of work in Objective-C here inside at Apple," Federighi told Ars. "We'll be supporting Objective-C and proceeding to develop it as important to fit into this advancing world. We do imagine that Swift is the dialect that we prescribe for new engineers to our stage who are contributing for the future and building new applications. We think Swift is totally the opportune place to begin. In any case, we'll keep on maintaining, progress, and bolster Objective-C to the extent we can see."

That announcement for the most part tracks with how engineers have disclosed to us they're utilizing Swift and Objective-C. Some are staying with it as a result of recognition or on the grounds that they would prefer not to blend their Swift code with Objective-C code, yet more frequently we've been informed that new undertakings and new pieces of old ventures are being composed in Swift.

[pandamugger]

finally took the time to set up hyprpaper and i have a cute wallpaper now :3

that was so easy i literally have no idea why i couldn’t figure it out before

[pandamugger]

WHY DO I HAVE A WALLPAPER??? WHO IS THIS?

[pandamugger]

creature doing dark linux magic on da steam deck so we can watch lain on the tv

[pandamugger]

I need to work on my rice and i got EWW working but now i actually have to learn how to make the widgets 💀

[pandamugger]

linux maxxing… i want my fancy toolbars and widgets. I’ve been TOLD i need to learn rust to use this program but im powerful so i think i can do it