Why I use KDE

Why I use KDE
Over the decades, my primary operating system of choice has changed a few times. As a wee child of six years old, we got out first PC through one of those employer buy-a-PC programs, where an employer would subsidize its employees buying PCs for use in the home. The goal here was simple: if people get comfortable with a computer in their private life, they’ll also get comfortable with it in their professional life. And so, through my mother’s employer, we got a brand new 286 desktop running MS-DOS and Windows 3.0. I still have the massive and detailed manuals and original installation floppies it came with. So, my first operating system of ‘choice’ was MS-DOS, and to a far lesser extent Windows 3.0. As my childhood progressed, we got progressively better computers, and the new Windows versions that came with it – Windows 95, 98, and yes, even ME, which I remarkably liked just fine. Starting with Windows 95, DOS became an afterthought, and with my schools, too, being entirely Windows-only, my teenage years were all Windows, all the time. So, when I bought my first own, brand new computer – instead of old 386 machines my parents took home from work – right around when Windows XP came out, I bought a totally legal copy of Windows XP from some dude at school that somehow came on a CD-R with a handwritten label but was really totally legit you guys. I didn’t like Windows XP at all, and immediately started looking for alternatives, trying out Mandrake Linux before discovering something called BeOS – and despite BeOS already being over by that point, I had found my operating system of choice. I tried to make it last as long as the BeOS community would let me, but that wasn’t very long. The next step was a move to the Mac, something that was quite rare in The Netherlands at that time. During that same time, Microsoft released Windows Server 2003, the actually good version of Windows XP, and a vibrant community of people, including myself, started using it as a desktop operating system instead. I continued using this mix of Mac OS X and Windows – even Vista – for a long time, while having various iterations of Linux installed on the side. I eventually lost interest in Mac OS X because Apple lost interest in it (I think around the Snow Leopard era?), and years later, six or seven years ago or so, I moved to Linux exclusively, fully ditching Windows even for gaming like four or so years ago when Valve’s Proton started picking up steam. Nowadays all my machines run Fedora KDE, which I consider to be by far the best desktop operating system experience you can get today. Over the last few years or so, I’ve noticed something fun and interesting in how I set up my machines: you can find hints of my operating system history all over my preferred setup and settings. I picked up all kinds of usage patterns and expectations from all those different operating systems, and I’d like to enable as many of those as possible in my computing environment. In a way, my setup is a reflection of the operating systems I used in the past, an archaeological record of my computing history, an evolutionary tree of good traits that survived, and bad traits bred out. Taking a look at my bare desktop, you’ll instantly pick up on the fact I used to use Mac OS X for a long time. The Mac OS X-like dock at the bottom of the screen has been my preferred way of opening and managing running applications since I first got an iBook G4 more than 20 years ago, and to this day I find it far superior to any alternatives. KDE lets me easily recreate a proper dock, without having to resort to any third-party dock applications. I never liked the magnification trick Mac OS X wowed audiences with when it was new, so I don’t use it. The next dead giveaway I used to be a Mac OS X user a long time ago is the top bar, which shares quite a few elements with the Mac OS X menubar, while also containing elements not found in Mac OS X. I keep the KDE equivalent of a start menu there, a button that brings up my home folder in a KDE folder view, a show desktop button that’s mostly there for aesthetic reasons, KDE’s global menubar widget for that Mac OS X feel, a system tray, the clock, and then a close button that opens up a custom system menu with shutdown/reboot/etc. commands and some shortcuts to system tools. Another feature coming straight from my days using Mac OS X is KDE’s equivalent of Exposé, called Overview, without which I wouldn’t know how to find a window if my life depended on it. I bind it to the top-left hotcorner for easy access with my mouse, while the bottom-right hotcorner is set to show my desktop (and the reason why I technically don’t really need that show desktop button I mentioned earlier). I fiddled with the hot corner trigger timings so that they fire virtually instantly. Waiting on my computer is so ’90s. It’s not really possible to see in screenshots, but my stint using BeOS as my main operating system back when that was a thing you could do also shines through, specifically in the way I manage windows. In BeOS, double-clicking a titlebar tab would minimise a window, and right-clicking the tab would send the window to the bottom of the Z-stack. I haven’t maximised a non-video window in several decades, so I find double-clicking a titlebar to maximise a window utterly baffling, and a ridiculous Windows-ism I want nothing to do with. Once again, KDE lets me set this up exactly the way I want, and I genuinely feel lost when I can’t manipulate my windows in this

SalveMonos: la app que protege la vida silvestre

En Tamarindo, Costa Rica, la vida silvestre convive diariamente con un peligro mortal: los cables de alta tensión. El mono aullador está más expuesto a morir electrocutado, ya que utiliza los cables para desplazarse por la ciudad al quedar su hábitat fragmentado. Ahora, una app impulsada por inteligencia artificial, facilita el trabajo de rescate y ofrece datos para prevenir más incidentes.

Vous êtes en train de créer un monstre en mettant des pouces rouges à Pop It Mania

Pour parler de la vidéo avec des gens passionnés tech : / discord

Mon setup COMPLET (PC / Caméra / Autres) : http://textup.fr/248446PT

Si vous voulez me soutenir, vous pouvez le faire en achetant vos produits technologiques avec ce lien : https://leotechmaker.com/me-soutenir
(Vous ça ne vous change rien au prix de ce que vous achetez, moi je récupère un % de la vente, merci ❤️❤️)

SUIVEZ MOI ICI PARTOUT POUR NE JAMAIS ARRÊTER D’APPRENDRE !
—————————————————
Twitter: / leotechmaker
Instagram: / leotechmaker
TikTok: / leotechmaker
Twitch: / leotechmaker

Mon extension Chrome à installer ABSOLUMENT : http://leotechmaker.com/addon

Si tu es descendu jusque-là, n’oublie pas de liker la vidéo, après tout, t’as bien cliqué sur “en voir plus”, tu peux bien utiliser un clic de plus…

Godrej Neopolis: Spacious 3 BHK and 4 BHK Apartments in Kokapet, Hyderabad

Godrej Neopolis, a premium residential project located in Kokapet, Hyderabad, offers luxurious 3 BHK and 4 BHK apartments in a gated community. Spread across 3.5 acres, this project consists of a 49-floor tower housing 350 spacious apartments. The size of the 3 BHK apartments ranges from 3000 sq. ft., while the 4 BHK apartments offer an expansive 4000 sq. ft., catering to families seeking a lavish lifestyle.

https://forum.game-labs.net/profile/40521-psouthernstars/?tab=field_core_pfield_11
http://fudo.booktype.pro/accounts/psouthernstars/
https://www.stampstampede.org/society-stampers/members/PSOU/
https://www.hiddenpeakteahouse.com/profile/prestigesouthernstarapartments/profile
https://galleria.emotionflow.com/138807/profile.html
https://progresspond.com/members/psouthernstars/
https://www.speedway-world.pl/forum/member.php?action=profile&uid=377757
https://playeur.com/u/psouthernstars
https://livevictoria.com/index.php?user_action=info&userid=456885
https://zbrush.dpi.upv.es/wordpress/artistas-2/godrejneopoliss/profile/
https://www.wantedly.com/id/godrej_neopoliss
https://collab.sundance.org/people/godrejneopoliss-1728377119

Tech/News/2024/41

Tech/News/2024/41
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available. Weekly…

Talking Drupal: Talking Drupal #470 – Creating Recipes

Today we are talking about Creating Recipes, What Recipes already exist, and helpful tips and tricks with guest Jim Birch. We’ll also cover Features as our module of the week.

For show notes visit: https://www.talkingDrupal.com/470

Topics

  • What are recipes
  • How do you recommend someone get started writing recipes
  • Where can people find recipes
  • Can you include sub recipes
  • How should you test recipes
  • Any tools that make writing recipes easier
  • What recipes are needed that do not exist
  • How can people move recipes forward

Resources

Guests

Jim Birch – linkedin.com/in/jimbirch thejimbirch

Hosts

Nic Laflin – nLighteneddevelopment.com nicxvan John Picozzi – epam.com johnpicozzi Aubrey Sambor – star-shaped.org starshaped

MOTW Correspondent

Martin Anderson-Clutz – mandclu.com mandclu

  • Brief description:
    • Have you ever wanted an admin UI to manage sets of configuration, to version and share across Drupal sites? There’s a module for that.
  • Module name/project name:
  • Brief history
    • How old: created in Mar 2009 by yhahn, though recent releases are by Dave Reid
    • Versions available: 7.x-2.15 and 8.x-3.14, the latter of which works with Drupal 9.4 and 10
  • Maintainership
    • Minimally maintained
    • Security coverage
    • Test coverage
    • Documentation: Has a documentation guide and probably hundreds if not thousands of of tutorials available
    • Number of open issues: 610 open issues, 54 of which are bugs against the 8.x branch
  • Usage stats:
    • Almost 117,000 sites, though the majority are using the D7 version
  • Module features and usage
    • Many listeners will remember Features as the de facto solution for configuration management in Drupal 7 and earlier
    • As the name implies, it was really intended to share common capabilities across different Drupal sites
    • Unlike recipes, Features can have version numbers, because there is a path to sync configuration updates across sites using a Feature, though this is where a lot of teams found Features could be complex to use
    • We did previously cover Features as MOTW all the way back in episode #147, but I thought it was relevant to today’s discussion because of the way it provides a UI for organizing and exporting specific sets of configuration
    • There is an open issue for Features to directly export recipes, because it already does a lot of the time-consuming work of collecting together necessary config files, including dependencies
    • Even its current state, it could be a time saver for anyone wanting to start creating their own recipes

Ruby 3.4.0 preview2 Released

We are pleased to announce the release of Ruby 3.4.0-preview2.

Prism

Switch the default parser from parse.y to Prism. [Feature #20564]

Language changes

  • String literals in files without a frozen_string_literal comment now emit a deprecation warning
    when they are mutated.
    These warnings can be enabled with -W:deprecated or by setting Warning[:deprecated] = true.
    To disable this change, you can run Ruby with the --disable-frozen-string-literal
    command line argument. [Feature #20205]

  • it is added to reference a block parameter. [Feature #18980]

  • Keyword splatting nil when calling methods is now supported.
    **nil is treated similarly to **{}, passing no keywords,
    and not calling any conversion methods. [Bug #20064]

  • Block passing is no longer allowed in index. [Bug #19918]

  • Keyword arguments are no longer allowed in index. [Bug #20218]

Core classes updates

Note: We’re only listing outstanding class updates.

  • Exception

    • Exception#set_backtrace now accepts an array of Thread::Backtrace::Location.
      Kernel#raise, Thread#raise and Fiber#raise also accept this new format. [Feature #13557]
  • Range

    • Range#size now raises TypeError if the range is not iterable. [Misc #18984]

Compatibility issues

Note: Excluding feature bug fixes.

  • Error messages and backtrace displays have been changed.
    • Use a single quote instead of a backtick as a opening quote. [Feature #16495]
    • Display a class name before a method name (only when the class has a permanent name). [Feature #19117]
    • Kernel#caller, Thread::Backtrace::Location’s methods, etc. are also changed accordingly.
    Old:
    test.rb:1:in `foo': undefined method `time' for an instance of Integer
            from test.rb:2:in `<main>'
    
    New:
    test.rb:1:in 'Object#foo': undefined method 'time' for an instance of Integer
            from test.rb:2:in `<main>'
    
  • Hash#inspect rendering has changed. [Bug #20433]
    • Symbol keys are displayed using the modern symbol key syntax: "{user: 1}"
    • Other keys now have spaces around =>: '{"user" => 1}', while previously they didn’t: '{"user"=>1}'

C API updates

  • rb_newobj and rb_newobj_of (and corresponding macros RB_NEWOBJ, RB_NEWOBJ_OF, NEWOBJ, NEWOBJ_OF) have been removed. [Feature #20265]
  • Removed deprecated function rb_gc_force_recycle. [Feature #18290]

Implementation improvements

  • Array#each is rewritten in Ruby for better performance [Feature #20182].

Miscellaneous changes

  • Passing a block to a method which doesn’t use the passed block will show
    a warning on verbose mode (-w).
    [Feature #15554]

  • Redefining some core methods that are specially optimized by the interpeter
    and JIT like String.freeze or Integer#+ now emits a performance class
    warning (-W:performance or Warning[:performance] = true).
    [Feature #20429]

See GitHub releases like Logger or
changelog for details of the default gems or bundled gems.

See NEWS
or commit logs
for more details.

With those changes, 4422 files changed, 163889 insertions(+), 243380 deletions(-)
since Ruby 3.3.0!

Download

  • https://cache.ruby-lang.org/pub/ruby/3.4/ruby-3.4.0-preview2.tar.gz

    SIZE: 22722332
    SHA1: c23265acf6c07b4c1df1e41eebf8b4cf2f25b97b
    SHA256: 443cd7ec54ade4786bc974ce9f5d49f172a60f8edc84b597b7fe2bd2a94b8371
    SHA512: 0946d256587597bdf13437a50f7a3298c151133edea161a1c4806a04dcbd8c2e8a7fd617f3eda16c5c05f6e6346317562cc30ba67698f1fdd92237c03bdbd23e
    
  • https://cache.ruby-lang.org/pub/ruby/3.4/ruby-3.4.0-preview2.tar.xz

    SIZE: 16878876
    SHA1: dbff404b969012702dc500cac72f4d6b3822068e
    SHA256: 626bf4fe952323c15ec9a8999f470ec136ef91c0fc34c484646aaaa9a0b62ca7
    SHA512: f23257896a35d3a581cbf5e8c94fe28e45725e39608a7669f47f31085338b1b4929a4db40d826d8fee628afb97b0c25b2f9e7bda4cd42e80c1208c46caf54265
    
  • https://cache.ruby-lang.org/pub/ruby/3.4/ruby-3.4.0-preview2.zip

    SIZE: 28101194
    SHA1: 479bd223bca3225fb3a15984e3eae4efb9a40189
    SHA256: e00a6fbf6f9e25a725711a8aac7e38be6bed61de4db9862a405172b96bf38b5b
    SHA512: 0d9ee1c41920e4d594b0f2c40d02339b4e9a2cd5232f5ee914cab5a685cb4a2279fbbfd8fbad40ef0a53866db4e1de96068c62580ede6d8fab02550393bcbe81
    

What is Ruby

Ruby was first developed by Matz (Yukihiro Matsumoto) in 1993,
and is now developed as Open Source. It runs on multiple platforms
and is used all over the world especially for web development.

Posted by naruse on 7 Oct 2024

Python 3.13.0 (final) released

 

Python 3.13.0 is now available

This is the stable release of Python 3.13.0

Python 3.13.0 is the newest major release of the Python programming language, and it contains many new features and optimizations compared to Python 3.12. (Compared to the last release candidate, 3.13.0rc3, 3.13.0 contains two small bug fixes and some documentation and testing changes.)

Major new features of the 3.13 series, compared to 3.12

Some of the new major new features and changes in Python 3.13 are:

New features

Typing

Removals and new deprecations

  • PEP 594 (Removing dead batteries from the standard library) scheduled removals of many deprecated modules: aifcaudioopchunkcgicgitbcryptimghdrmailcapmsilibnisnntplibossaudiodevpipessndhdrspwdsunautelnetlibuuxdrliblib2to3.
  • Many other removals of deprecated classes, functions and methods in various standard library modules.
  • C API removals and deprecations. (Some removals present in alpha 1 were reverted in alpha 2, as the removals were deemed too disruptive at this time.)
  • New deprecations, most of which are scheduled for removal from Python 3.15 or 3.16.

For more details on the changes to Python 3.13, see What’s new in Python 3.13.

More resources

We hope you enjoy the new releases!

Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation.

Choo-choo from the release train,

Your release team,
Thomas Wouters 
Ned Deily 
Steve Dower 
Łukasz Langa