sally1620

I think you are correct in some sense. It is just that kids who grow up in this culture will learn how to navigate it properly, while older people struggle to adapt and find their voice. Now I know what it is like to feel old.

The most important argument is that not all programming is systems programming.

A lot of projects choose C, C++ or Rust only because they need performance:

* Backend services

* Numerical computation

* Game development

* Rendering engines, e.g., browser engines

System programming is usually needed for what we consider Operating Systems, e.g. kernel, system libraries, and shell.

In my career as a C++ programmer I have worked on a lot of projects that I would otherwise write in C#, Java, Julia, or Go.

I remember reading that one of the main activities of FSF is to enforce GPL. Isn't this time they get involved.

The early free software was developed by the people using it, e.g. Emacs, GNU tools, Linux.

GPL is a code sharing agreement among the developers. You get value from the product and contribute back to it. If you need features, you add it yourself. If you find bugs, you submit a patch. The value is shared, and so is the cost, and so is the burden of maintenance.

It is only when people started commercializing free software that it became a problem.

Even Bill Gates was actually selling BASIC as Free Software, he had to make it proprietary because people were not paying him.

https://en.wikipedia.org/wiki/Open_Letter_to_Hobbyists

On another note, a lot of free software is also produced by universities, they get paid by research grants, and they don't need users to pay them. They do usually require attribution which increases the citation count on their papers.

This approach works, and the user experience may be great. But it is very costly to build, and very costly to maintain. Compared to Electron, you need a few Javascript devs to spin up an app that runs on every major operating system AND in browser.

I think economics is the real reason they won. And Google pumped a lot of money in this space, too.

A lot of players entered this space and some are actually profitable companies, but are none are as popular as Electron. aside from Javascript and WebAPIs, Electron is also free as in free beer.

Qt: is truly cross-platform, supporting Mac, Windows, Android, iOS, and even LG TV webOS. VLC uses Qt and is rock solid on all platforms it runs. It is very expensive for commercial development.

Xamarin: run on all major operating systems, and mobile, they were profitable. C# is much better language that C++ or Javascript. They became free to use once Microsoft acquired them

Qt has done a fantastic job in this space. It is also isn't cheap. It is only free for GPLv3 software.

I use Qt for anything cross-platform. The main problem is that C++ is not an easy language for UI developments. also consider the fact that C++ devs are paid higher that Java, JS or C# devs. Most other UI toolkits are really terrible for cross-platform development.

It is not really "obsession", it is economics. There is a high cost with maintaining different apps for different platforms.

This is really a win for Google, since most of these web apps are easily ported to ChromeOS. and it is going to continue as ChromeOS is gaining even more market share.

Pascal didn't fail, it was replaced by C. Both Microsoft (with WinNT) and Apple (with NextStep) left Pascal behind in the 1990s in favor of C to compete with other Unixes of the time. At the end of 90s, the only steward of Pascal was Borland; and Borland failed, and Pascal was forgotten.

Why can't they just do the same as dropbox or onedrive, where they use Windows file system filters on a regular folder (no mount points).

To all the people who suggest alternatives, our entire org is run by xooglers and they put everything in Google Drive. I have no choice but to use this crap. To make matters worse, I cannot use any third-party client (or even roll my own) because it is not allowed by the security policy.

Modern camera stacks use a lot of machine learning to figure out what kind of scene is being captured; primarily to apply specific tuning for that scene. For example, certain settings are applied for night time, portrait, landscape, beach, etc.

Xiaomi might be using an ML detector to figure out it is looking at something that resembles an official document, and refusing to take a picture of it.

I wonder if anyone is going to create a linux distribution with a base system baked in with pkgsrc managing the applications. It would be very useful for containers and WSL.

With IP addresses, it is not possible to validate TLS certificate as well. This should not work at all.

Also we have HTTPS everywhere, but DKIM is still not supported by most domains. That is a more serious issue and it also covers this as well.

Microsoft took this matter into their own hands and the result ended up being Powershell.

In the first iteration, they just ported Korn shell to windows but it wasn't that useful. So after a couple of iterations they ended up with Powershell.

What makes a Mac a Mac is hardware & software working together. Also the integration with other Apple things like watch, phone, and earbuds.

This kind of optimization actually drove me away from F#. I realized that high-performance F# is essentially imperative C# with F# syntax.

There is no place for high order functions and functional constructs in high performance F# code.

Is there a WSL version of this?

Except more often than not packages do their own thing and don't follow the convention. this is even worse if you compile from source.

There are different benefits and drawbacks of mmap. I only use mmap because it simplifies my code (I write experimental code).

But the OP and commenters are mostly concerned about the extra copy of read().

For video memory, DMABUF has been used to avoid extra copying. The idea is that the hardware directly DMAs into a buffer mapped in the userspace instead of copying into a kernel buffer and then copying into userspace. A system call is still involved, but no extra copying of data.

I wonder if anyone has actually implemented a disk I/O interface using DMABUF. There are a couple of low-level disk interfaces. But I don't know if any of them uses DMABUF.

A messaging app is not a personal choice like using Debian or FreeBSD, it is about community.

I have iMessage, Whatsapp, Telegram on my phone. Each one is used to reach a certain group of people. I also have Signal, but nobody is on there and I never use it.

I honestly think of Go as Java with an appeal to C programmers. And of course much better performance/memory usage than Java.

Go is a high-level language. It is not meant for low-level programming. and yet the authors keep claiming that it is.

I don't think Go lies about what it is. It is just a victim of its popularity.

The authors clearly say that is designed for writing scalable networked services. And they definitely don't care about GUIs, Windows, embedded, etc.

Overzealous programmers are constantly taking Go where it is not meant to be and complain about its shortcomings. Go's simplicity means that it makes a lot of assumptions about the system. I think authors should have been more upfront and explicit about this.

Linux is accusing Intel of killing ECC intentionally. But that is not really the case, they just wanted people to pay up.

If you care about ECC, you pay for Xeon. Majority of consumers don't run critical applications on their devices, so they are happy with a cheap device that may crash once in a while.

AMD is only changing the game because they are trying to undercut Intel. They have been putting pro features into all of their CPUs including over-clocking, extra PCIE lanes and ECC.

Honestly, what is the point of bullet-proof hardware when the software reliability (at least on consumer devices) has gone down to two nines.

There is a single XML variant of the open document format. although images and videos won't be embedded in the document that way.

I used this format when I was generating ODF documents using a script.

I wonder if anyone has implemented a document file format based on SQLite.

SQLite file format is documented and other implementations exist. I am sure given enough interest, it could get standardized.

They already did that with SQ1 and SQ2. They collaborated with Qualcomm on this.

Also, the main motivation is the cost. Any other vendor would want the highest profit out of their design.

NVIDIA has multiple generations of ARM SoCs. All of them are focused on GPU performance, though.

Also NVIDIA quit the mobile market a while ago. They are focused on Autonomous driving and embedded market. The only consumer product on the market with NVIDIA SoC is Nintendo Switch (which sells millions)

Bite the hand that fed. They are not going to get more funding by condemning philanthropist.