sally1620

Ada actually trades blows with C in Debian shootout game. It is the language of choice for automotive and aviation safety certification. You cannot get safer than that. and it doesn't have oddities of Rust.

Game streaming technology has been ready for a long time now. It is not the technology or leadership of companies that make game streaming; it is the game studios that block game streaming from becoming main-stream.

Briar has been translated to Persian 100%. This is a good indicator that is must be in widespread use in Iran

This is the first time I hear about Ada package manager. You can always download GNAT, an Ada fronted for GCC, and start coding in terminal and a text editor. You don't need package manager and all of the other stuff.

Apple could solve this problem in Webkit. But Android is more complicated. On Android, third-party browser engines are allowed. Google cannot prevent an app from shipping its own browser engine for in-app browsing experience.

As the tidbits article says, only the client is proprietary. I am sure that eventually a fully open-source Linux version of this is going to be developed and integrated into Seahorse.

rclone already provides such a client and it is fully open source. In general, to have a zero-trust system, you need to have client and server developed by independent parties.

If it is output of some other tool, then it is a build artifact and there is no need to check it in.

I have this argument with people all the time and the conclusion is always like: "it is too hard to integrate the generator with the build system so we check them in".

The big problem with generated files is merge conflicts. How do you resolve a merge conflict on generated files. especially if they are binary.

Apple is already in [casual] gaming, they have Apple Arcade and hundreds of high quality games on app store. They also have "console" called Apple TV. Evey Apple store sells Playstation controllers.

Apple still considers Macbooks as trucks: they are for developers and professionals, not gamers or everyday users. They want non-developers to buy iPad and that is why there is no sub-$1000 MacBook.

Rosetta's biggest flaw is lack of AVX support.

We had to put so much effort to just run things on Rosetta because all of our compiled code had AVX enabled. We also needed to chase down pre-compiled binaries and re-compile them without AVX, we still haven't finished this work.

This sounds like a hype that is going to die at some point. SQLite has its own uses in client devices and small webservers, but it is not built to scale to millions of transactions per second.

It is possible to build all kinds of cool things on top of SQLite, but most of these articles sound like it is going to replace PostgreSQL or MySQL.

After reading the paper, I see that it is not built on top of SQLite, but shares some components with SQLite.

I always use Ethernet at the office because Wi-Fi sucks when everyone is connected to it at the same time. Even though they use commercial grade routers.

At home switching to Wi-Fi 6 has solved some f dead zone problems. I notice a stark contrast between performance of Wi-Fi 5 and Wi-Fi 6 devices.

This kind of initiative could take off. Only if it is backed by a big player. Basically Apple Google and Microsoft.

WebAssembly is not a stand-alone application development package. It doesn’t have many of the functionalities of Flash, Applets, Silverlight or even NaCl. It has no API on its own to interact with display or keyboard and mouse. and none of the features you find in a VM such as multi threading or a memory allocator

The physical attack Microsoft worried about is hacker extracting information from a stolen laptop. It only takes a single laptop (out of thousands) to infiltrate the company network and steal source code or whatever.

For enterprise users, this attack vector is a real threat. Microsoft definitely wants to dog food this technology to their own employees to avoid getting hacked.

One of the main advantages would be hardware accelerated encode/decode, but because every manufacturer supports it differently most software refuses to use it. And once you go to software encoding, why not use a more efficient and open codec.

These are only hard problems in Unix world. VisualBasic and Delphi always had really good auto-complete.

Next time someone asks me why you are writing a function yourself instead of using a library, I will show them this.

I cannot figure out if Bellard’s creations are hobby projects or serious production libraries. This one has a couple of issues: browsers have already settled on AVIF. And HEVC is patent encumbered which makes it not a good choice for deploying on devices.

It is just the simple fact that the user land API of all current operating systems is C. A programming language need to support at least C ABI for this purpose.

I thought the phrase "COMES WITH ABSOLUTELY NO WARRANTY" in most open-source licenses would make it clear. But obviously no one reads licenses or EULAs.

However, I would let people file issues and would just let them sit there if they are not a paying for it. This way at least the known issues are documented and there would be less duplication.

Letting people fix their own problems is a good strategy. However, if you are encouraging people to send PRs, then there is a maintenance problem. Especially if some eager people decide to add major feature or refactor the code.

This looks pretty secure to me. Most of the time, I just have to click forgot password and it is basically the same thing.

Most blog post miss a critical point in OSS software: OSS authors can't charge royalty for the use of their software, but they can charge money for maintenance of said software.

And yet most OSS doesn't do that. Almost all widely used OSS has some other revenue model (if any). Volunteer maintainers keep complaining about burnout, and yet they don't directly ask for money for writing the software.

OSS authors don't owe anything to users if the users are not paying back. This is exactly why all OSS licenses contain the pharese ABOSLUTELY NO WARRANTY.

The problem with Linux has always been lack of support for newest hardware. I keep going back to Windows because I just want all the cool features of the hardware like webcam, fingerprint reader, and reliable sleep/hibernation.

Linux always runs well on HW that is a few years old. or HW that was specifically certified for Linux, such as Thinkpads.

One of the main problems is that Linux is just the kernel, not an operating system (FSF has always been vocal about this with their GNU/Linux branding).

A minimal Linux system requires many GNU utilities and software from other projects to give you a basic command prompt with network connectivity. A Desktop system requires GNOME, KDE, etc.

Contrast this with BSD where a default install gives you a base system. There are BSD distros, but they only focus on orchestration and higher level components, not the base system.

It is quite interesting that most of the problems mentioned don't exist in recent version of C# on .NET Core, considering all the similarities of C# and Java.

I would even say, some of the problems didn't exist in C# in 2009. C# always had value types with configurable in memory layout. It also has a very good mmap solution. It also allows for hand optimize things using unsafe blocks.

Don Syme explains in history of F# that there were multiple efforts to port OCaml to .NET, (Nemerle comes to mind), but none of those felt natural to use.

For F#, they started with OCaml syntax and semantics; then modified it to make it a true .NET language. They added features that were not in OCaml like inheritance & interfaces. and removed features that were unnecessary in .NET like functors.

https://fsharp.org/history/hopl-final/hopl-fsharp.pdf Early F# compiler even had ml-compatibility mode which would make syntax closer to OCaml, it was probably used for bootstrapping.

I hope not. I was hoping that Unix and its shell would die out at some point. But it is a hydra that will live on and haunt our dreams.

FWIW, I have switched to Powershell & Python for most of my work. I only use Python when I have to share scripts with colleages, though. Powershell still beats Python for scripting.

It is not surprising that the manufacturer of the HW produces a better operating system for that HW than the third parties.

In the benchmarks, Clear Linux also beats Ubuntu for the same reason, Intel engineers understand Intel CPUs better than anybody else.

M1 makes this kind of comparison close to impossible. There is Asahi Linux now, but it is far from a production level Linux and I don't think it will ever perform as good as macOS. For the same reason above.

I find myself completely withdrawing from all social engagement at work because of this. our company even has a program for reporting micro-aggressions. So I basically refrain to talk about anything that is not work related at work.