Language Selection

English French German Italian Portuguese Spanish

KDE/Qt: Go, Qt, Krita, Calamares, BSD, and Windows

Filed under
Development
KDE
  • New help porting to Go >= 1.12

    What no one? Actually no, we have kdeclose, a bot that will go over all Pull Requests and gracefully close them suggesting people to move the patch over to KDE infrastructure where we are watching.

    The problem is that I'm running that code on Google AppEngine and they are cutting support for the old Go version that it's using, so I would need someone help me port the code to a newer Go version.

  • #QtWS20 Rock Star Speakers, Super Early Birds & Training

    Great things are happening in 2020 including the release of Qt 6 and a whole new decade of innovations to come.

    We are very thrilled to announce the Rock Star speakers at Qt World Summit 2020 who will share the vision in software development and how to create successful UI/UX in 2020 and beyond:

    Lars Knoll, Chief Maintainer of Qt Project
    Herb Sutter, Leading C++ authority and chair of the ISO C++ standards committee
    Joe Nuxoll, Design Director of Digital Products & Experience, Polaris
    Euan Cameron, CTO of Esri
    Matthew Hungerford, UX Team Lead at Chargepoint

  • gnu linux debian – install qtcreator and qt5-default – qt c hello world – qtcreator no valid kits found
  • Krita Weekly #10

    Honestly, you don't want to know the number of bugs in our bug tracker at this point. But I assure you these are just our broken unit tests rather than bugs. Recently Boud decided to mark every broken unit test as a bug in the hope that it would have higher chances of getting fixed. Why do we need to fix the broken unit tests? Of course, if all of our unit tests ran properly the chances that a bug would trickle down a release would be lesser.

  • KDE FreeBSD updates (february 2020)

    Some bits and bobs from the KDE FreeBSD team in february 2020.

    We met at the FreeBSD devsummit before FOSDEM, along with other FreeBSD people. Plans were made, schemes were forged, and Groff the Goat was introduced to some new people.

  • Assamese in Calamares

    Calamares welcomes an Assamese translation.

    During conf.kde.in in Delhi in january 2020, I met Wrishiraj Kaushik of SuperX. SuperX is a Linux distribution that is built in Assam.

    We got to talking about translation and he said he’d get right on it. A week later I added Assamese as a language to the “ok” list (that just means there’s a translation, and it’s between 5% and 75% done). Two weeks later, Assamese is now at 100% and part of the “complete” list.

  • Git quality of life
  • [KDE Developer] Sway and the Dock station

    I just moved permanently from awesome to Sway because I can barely see any difference. Really.

    The whole Wayland ecosystem has improved a LOT since last time I used it. That was last year, as I give Wayland a try once a year since 2016.

    However, I had to ditch an useful daemon, dockd. It does automatically disable my laptop screen when I put it in the dock station, but it does relies over xrandr.

  • Windows Store Status

    If you want to help to bring more stuff KDE develops on Windows, we have some meta Phabricator task were you can show up and tell for which parts you want to do work on.

    A guide how to submit stuff later can be found on our blog.

More in Tux Machines

Rugged, Linux-driven IoT gateways are optimized for sensor monitoring

Neousys’ IGT-33V and IGT-34C gateways run Debian on a TI AM3352 and offer PoE+ PD, isolated DIO, and 8x 0-10V (33V) or 4x 4-20mA (34C) analog inputs. They follow similar IGT30 and IGT-31D models that focus on digital outputs. We missed Neousys’ January announcement of its IGT30 and IGT-31D IoT gateways, both of which run a Debian 9 Linux stack on a Texas Instruments Sitara AM3352 SoC. Now, the company has followed up with similar IGT-33V and IGT-34C models. The rugged new DIN-rail systems specialize in analog inputs and digital outputs compared to the earlier digital input focused models. All four IGT-30 series models, which are aimed primarily at sensor monitoring, among other industrial IoT applications, are covered below. Read more

today's leftovers

  • 2020-04-08 | Linux Headlines

    The GNOME Foundation and Endless launch a new contest aimed at engaging young coders with FOSS, Tails 4.5 brings support for UEFI Secure Boot, the first release of Krustlet brings WebAssembly to Kubernetes, and Qt considers further limiting access to its releases.

  • People of WordPress: Mario Peshev

    Mahttps://wordpress.org/news/2020/04/people-of-wordpress-mario-peshev/rio has been hooked on computers ever since he got his first one in 1996. He started with digging into MS-DOS and Windows 3.1 first and learned tons by trial and error. Following that adventure, Mario built his first HTML site in 1999. He found development so exciting that he spent day and night learning QBasic and started working at the local PC game club. Mario got involved with several other things related to website administration (translating security bulletins, setting up simple sites, etc) and soon found the technology field was full of activities he really enjoyed. [...] For Mario, one of the key selling points of WordPress was the international openness. He had previously been involved with other open source communities, some of which were US-focused. He felt they were more reliant on meeting people in person. With events only taking place in the US, this made building relationships much harder for people living in other countries. While the WordPress project started out in the US, the WordPress community quickly globalized. Dozens of WordCamps and hundreds of Meetup events take place around the globe every year. All of these events bring a wide variety of people sharing their enthusiasm for WordPress together. For Mario, the birth of WordCamp Europe was something magical. The fact that hundreds, and later on thousands, of people from all over the world gathered around the topic of WordPress speaks for itself. Mario has been involved with organizing WordCamp Europe twice (in 2014 and 2015).

  • FINOS Joins Linux Foundation [Ed: For the second time in two days, the "Linux" Foundation announces backing a non-Linux OS (seL4 and now FINOS), this time it's announced by "Editorial Director, Project Insights at Linux Foundation" who came from Microsoft (yes, Mircrosofters run and speak for the Linux Foundation now)]

    During the 1960s and 1970’s, software developers typically used monolithic architectures on mainframes and minicomputers for software development, and no single application was able to satisfy the needs of most end-users. Vertical industries used software with a smaller code footprint with simpler interfaces to other applications, and scalability was not a priority at the time. With the rise and development of the Internet, developers gradually separated the service layer from these monolithic architectures, followed by RPC and then Client/Server. But existing architectures were unable to keep up with the needs of larger enterprises and exploding data traffic. Beginning in the middle of the 1990s, distributed architectures began to rise in popularity, with service-oriented architectures (known as SOA) becoming increasingly dominant. [...] Today, on March 10th, 2020, The Linux Foundation is excited to announce that the TARS project has transitioned into the TARS Foundation. The TARS Foundation is an open source microservice foundation to support the rapid growth of contributions and membership for a community focused on building an open microservices platform.

  • Microsoft Buys Corp.com So Bad Guys Can’t

    Wisconsin native Mike O’Connor, who bought corp.com 26 years ago but has done very little with it since, said he hoped Microsoft would buy it because hundreds of thousands of confused Windows PCs are constantly trying to share sensitive data with corp.com. Also, early versions of Windows actually encouraged the adoption of insecure settings that made it more likely Windows computers might try to share sensitive data with corp.com.

Programming Leftovers

  • Bootlin toolchains updated, edition 2020.02

    Bootlin provides a large number of ready-to-use pre-built cross-compilation toolchains at toolchains.bootlin.com. We announced the service in June 2017, and released multiple versions of the toolchains up to 2018.11. After a long pause, we are happy to announce that we have released a new set of toolchains, built using Buildroot 2020.02, and therefore labelled as 2020.02, even though they have been published in April. They are available for 38 CPU architectures or architecture variants, supporting the glibc, uclibc-ng and musl C libraries when possible. For each toolchain, we offer two variants: one called stable which uses “proven” versions of gcc, binutils and gdb, and one called bleeding edge which uses the latest version of gcc, binutils and gdb.

  • Squeezing the most out of the server: Erlang Profiling

    An obvious way to reduce costs is to make the system more efficient and this means entering the hazardous land of software optimization. Even for experienced programmers, identifying bottlenecks is a hard enough problem when using the right tools; trying to guess what could make the code run faster will not only waste time but is likely to introduce unnecessary complexity that can cause problems down the line. The cousin of premature optimization is necessary optimization without profiling first

    While Erlang is famously known for its concurrency model and fault-tolerant design, one of its biggest strengths is the level of live inspection and tuning it offers, often with little or no setup and runtime cost. In this article, we outline how we leverage those features to profile our system, driving the optimizations that can lead to cost reductions.

  • S. Lott: Why Isn't COBOL Dead? Or Why Didn't It Evolve?

    In short, why is FORTRAN still OK? Why is COBOL not still OK? Actually, I'd venture to say the stories of these languages are essentially identical. They're both used because they have significant legacy implementations. There's a distinction, that I think might be relevant to the "revulsion factor." Folks don't find Fortran quite so revolting because it's sequestered into libraries where we don't really have to look at it. It's often wrapped into SciPy. The GCC compiler system handles it and we're happy. COBOL, however, isn't sequestered into libraries with tidy Python wrappers and Conda installers. COBOL is the engine of enterprise applications. Also. COBOL is used by organizations that suffer from high amounts of technical inertia, which makes the language a kind of bellwether for the rest of the organization. The organization changes slowly (or not at all) and the language changes at an even more tectonic pace. This is a consequence of very large organizations with regulatory advantages. Governments, for example, regulate themselves into permanence. Other highly-regulated industries like banks and insurance companies can move slowly and tolerate the stickiness of COBOL.

  • Google's Propeller Is Beginning To Be Upstreamed For Spinning Faster Program Binaries

    We have begun seeing the start of upstreaming on Google's Propeller Framework for offering post-link-time binary optimizations in the LLVM compiler stack to offer measurably faster (re)generated binaries. Propeller was developed by Google engineers as a result of Facebook's BOLT post-link optimizer for speeding up applications by optimizing the generated binary after being linked.

  • 5 tips for working from home from a veteran remotee

    Due to the outbreak of COVID-19 and its rapid development, we are all being called to take protective and preventative measures, including avoiding social contact as much as possible. Events are canceled, trips are postponed, and companies are asking their employees to work from home. It's an exceptional situation for everyone, as remote work cultures with distributed teams are being introduced overnight. Many companies are being challenged to quickly organize a team that works completely remotely. Many articles and recommendations on remote work, home offices, and teleworking are circulating. For example, GitLab, a pioneer in remote work, has recently published a detailed manual on remote working. I highly recommend it to anyone who is facing the challenge of setting up and managing a remote team. At OpenProject, we have been working in distributed teams for over 10 years.

  • Love or hate chat? 4 best practices for remote teams

    I encourage you to explore open source alternatives to chat like Mattermost, Rocket.Chat, and Riot.

  • Create web tutorials with Reveal.js and Git

    Whether you're a learner or a teacher, you probably recognize the value of online workshops set up like slideshows for communicating knowledge. If you've ever stumbled upon one of these well-organized tutorials that are set up page by page, chapter by chapter, you may have wondered how hard it was to create such a website. Well, I'm here to show you how easy it is to generate this type of workshop using a fully automated process.

  • Three Comics For Understanding Unix Shell

    I just optimized Oil's runtime by reducing the number of processes that it starts. Surprisingly, you can implement shell features like pipelines and subshells with more than one "process topology".

    I described these optimizations on Zulip, and I want to write a post called Oil Starts Fewer Processes Than Other Shells.

    That post feels dense, so let's first review some background knowledge, with the help of several great drawings from Julia Evans.

  • Targeted string replacements with sed and AWK

    Global replacement of A with B with sed or AWK might be a mistake unless you're 100% sure that you really, truly want to replace every instance of A with B in the data file. Even more risky (says he, who has done it more than once to his regret) is globally replacing over a whole set of files:

  • Robotic Process Automation (RPA): 6 open source tools

    As with many new software implementations, there’s a build-or-buy choice when getting started with Robotic Process Automation (RPA). On the build side, you can write your own bots from scratch, provided you’ve got the right people and budget in place. On the buy side, there’s a burgeoning marketplace of commercial software vendors offering RPA in various flavors, as well as overlapping technologies. (Some market themselves under different but related terms like “intelligent automation.”)

  • Things that are called ML/AI that really aren’t

    Artificial Intelligence (AI) is a genuine technical term to describe something that doesn’t quite yet exist in a truly cognitive form. However, AI is also a marketing buzzword used to distinguish items with extra usability or computing-power oompfh. The acronym often attempts to differentiate ordinary things, such as phones, from extraordinary things of the same ilk, such smartphones. Because there’s no legal governance over the use of AI in marketing, the label is abundantly applied to hardware or software use traditional algorithms as well as to things that actually learn. Calling all these things “smart” muddies the waters even more – and makes it difficult to make rational decisions. “Many times companies use the term ‘artificial intelligence’ to describe technology that operates without human interaction, but most times it’s just a sophisticated algorithm,” says Scott George, CEO of U.S. Consumer Healthcare Advocacy Group (USCHAG), a consortium of healthcare professionals, institutions, and organizations. He cites website chatbots as an example, which some consider AI – but usually don’t meet the technical criteria. “The confusion here is that for something to qualify as AI doesn’t actually require it to have an advanced form of cognition,” says Benjamin Nussbaum, AI/ML advisor to the Greystones Group, a technical support provider for the Department of Defense (DoD) and commercial clients. So many companies can tout what they do as AI is because the definition of AI was established back in the 1950s and only requires that a machine can do as well or better that which a human can do. “This opens the door for basic automation, analysis algorithms, etc. to all be categorized as AI,” adds Nussbaum. Naturally, that is extremely confusing for anyone who wants to assess any system’s value. The average algorithm is so sophisticated today that spotting the difference can be nearly impossible for the average buyer. The solution is to look at the system’s value without regard to how it’s built. If it genuinely uses AI or machine learning, great; but what matters is whether it makes life better.

  • An existential threat (that isn't COVID-19)

    Many of you will know my good friend Peter Scott as a Perl luminary. More recently he has turned his attention and his considerable talents to focus on the future of AI, both as an unprecedented opportunity for our society...and as an unprecedented threat to our species. A few years back, he released an excellent book on the subject, and just recently he was invited to speak on the subject at TEDx. His talk brilliantly sums up both the extraordinary possibilities and the terrible risks inherent in turning over our decision-making to systems whose capacities are increasingly growing beyond our own abilities, and perhaps soon beyond even our own understanding.

Linux Magazine's Latest Issue (With Paywall)