201984

AI said to do it.

I liked it. It has character.

So you'd switch USA for China, and still have a foreign dependency embedded into the very fabric of your society. Do you not see a problem with this?

What, like electronic payments using phones running American operating systems? With the bonus that you have two new gatekeepers that can lock your citizens out (Apple and Google).

Exactly, do they want people to buy their FPGAs or not? Charging per-seat licenses for developers and heavily restricting the free version mean people will buy from other vendors or just not use an FPGA at all.

I'll bite. Why is it the fault of the organization that gets broken into, rather than the fault of the attackers breaking into it? Even if the defender takes every reasonable defensive measure, they could still get pwned from some zero day that they had no defense against. Should they be fined into oblivion for something like that?

Is this why every healthcare website has 2FA now? It's so annoying.

>an unaligned pointer in itself is UB, not only an access to it.

Can someone point to where the standard states this?

Why wouldn't 8 be enough? Surely 18,446,744,070,000,001,024 characters is enough for every writing system in the world.

>There are studies out there, that sometimes it is even benefitial to be slow and show a loading indicator because it could increase trust from users,

And I as a user absolutely hate programs that do this. Put an "updated" message with a timestamp if you want, but don't pointlessly waste my time.

I'm 23 and IMO, the Windows desktop style peaked somewhere in Windows 95-2000. The first Windows I ever used was XP, so I'm mostly making that decision based off screenshots and emulators.

UIs back then were dense, didn't waste large amounts of space in a misguided attempt to be "minimalist", and had affordances for ease of use. There was no scrollbar hiding, no animations that made the user wait for no reason other than the designer's ego, very visible borders on windows and buttons that made finding/resizing them easier, large bars at the top of windows that let you move them around, and actual text for most buttons instead of icons that are anyone's guess what they mean. Thankfully some of this can be dialed back in the Windows 11 accessibility settings, at least for missing scrollbars and getting rid of time wasting animations, but a lot of programs don't respect those.

That's right there is a good indicator for which programs care about their users. I'm using your program because I want to actually do something, not waste time watching your designers show off.

I've disabled animations on my Android phone too, and it gives an extremely noticable speedup. Menus appear right when I click them, instead of a second later as they slide into existence. Too bad iPhones just replace the slide with a fade of equal duration; disrespect for the user's time like that is yet another reason I will never buy one.

Those older GUIs didn't try to hide the filesystem hierarchy either. It infuriates me to no end when I use a new OS and have to hunt down the way to show the disk root, or filename extensions, or hidden files. MacOS was especially bad; I had to look up a freaking keyboard shortcut that I never would have found on my own. The common reason is so "normal people" can use the interfaces, but I think that's infantilizing and is why tons of Gen Z don't know what files or folders are. Most people can learn .docx means a Word document, and C:\Users\TheirName is where their files are.

(Notable shoutout, the GNOME open/save dialogs are the absolute worst. I wish distros wouldn't default to it. People will just go right back to Windows 11 because it's somehow better.)

There's some improvements possible, for sure. I'd like to see some programs put hint letters over buttons when you press a modifier like Ctrl so you can easily see what the shortcuts are. I don't know of any that do, but it'd be very useful for more complex software like drawing programs or word processors.

edit: typo

The "constant migration to a new best thing" is a big problem. Once written, a program should be able to run forever, but this is only true on Windows for GUIs and on Linux only for some CLIs. Arch just recently dropped the original vi from its repos because "it no longer compiled" with stricter GCC settings, and if you want to run an older GUI, just forget about it. It's hars to blame people for only targeting the Web or Windows when those two will work forever, but on Linux you have to keep up with the endless treadmill of X11 to Wayland, GTK 2 to 3 to 4, Qt 3 to 4 to 5 to 6, pulseaudio to pipewire, etc., and if you miss just one you may as well give up.

> Can you imagine if every button on every site was the same Windows button gray color, regardless of the site's color?

Not a webdev, but can't you just use CSS on the <button> element for that?

Most embedded processors sadly don't have a BIOS, and the signing key is permanently burned into the processor via eFUSEs.

Where is this "extremely well documented process" to enroll new signing keys on an embedded device? I don't see one for any of these embedded processors with secure boot.

https://pip-assets.raspberrypi.com/categories/1214-rp2350/do...

https://documentation.espressif.com/esp32_technical_referenc...

https://docs.amd.com/v/u/en-US/ug1085-zynq-ultrascale-trm

And how do you do that on some locked down embedded device? Say, a thermostat for instance.

If it's compiled code, it's native.

And what if that customer wants to run their own firmware, ie after the manufacturer goes out of business? "Security" in this case conveniently prevente that.

He's saying the EU's capital city is Washington.

Most toolkits, including WebUI 3.0, render widgets on their own, so you can't distinguish just on that. I'd say anything written in an interpreted language is not native, and Javascript falls into that category. Dart at least is possible to compile ahead of time, and so is C#.

>Native means system libraries only.

Since when? To me, anything not webview-based is native, though you have varying degrees of integration into the platform.

A big complaint in TFA is that Win32 is much much easier to use than Wayland is:

>Getting any example application to work is so incredibly ridiculous, that every second I program on Wayland, I yarn for the times I did Win32 programming.

And that comes from the core of how Wayland is designed.

In Win32, the stable interface / ABI is the set of C functions provided by the operating system through DLLs. These are always dynamically loaded, so Microsoft is free to change the internal interface used for controlling windows at any time. Because of this, decades-old .exes still run fine on Windows 11.

In Wayland, the stable interface is the binary protocol to the compositor, in addition to the libwayland-client library plus extensions. Instead of that socket being an "implementation detail", it's now something that all programs that just want to make a window have to deal with. You also can't just use the socket and ignore the libwayland libraries, because mesa uses libwayland-client and you probably want hardware acceleration.

The other big issue is the core Wayland protocol is useless; you have to use a bunch of protocol extensions to do anything, and different compositors may implement different versions of them. On Win32, Microsoft can just add another C function to user32.dll and you don't have to think about protocol how that gets transformed into messages on the socket layer, or compatibility issues with different sets of extensions being supported by different compositors.

He's writing a client, and wlroots is a library for writing servers. It would not have helped at all.

How do you make a global hotkey in all compositors with Gtk or Qt?

I don't have a program that uses it, so it's not my place to watch mailing lists for it getting deprecated. Basic searching of Github however (what I'd have expected them to do before removing it) reveals 20k files that contain IPPROTO_UDPLITE, and many projects that use it directly. Probably the most renowned is FFmpeg (!!!).

https://github.com/FFmpeg/FFmpeg/blob/master/libavformat/udp...

https://github.com/search?q=IPPROTO_UDPLITE&type=code

https://github.com/tormol/udplite

https://github.com/nplab/packetdrill

https://github.com/python/cpython/blob/4e96282ee42ab51cf325b...

https://github.com/search?q=repo%3Aviveris%2Frohc%20udplite&...

So much for never breaking userspace.

Yep, and a disturbing amount of people here want to pull the ladder up behind them.

>C++ has its own atomics, threads etc.

It does indeed, but they are not compatible and at least the C atomics cannot be used from C++.

>C++ also has it's own designated initializer like syntax.

One that is far more limited. This is valid C, but not C++.

  struct bar {
      int a;
      int b;
  };
  
  struct bar tmp = {
      .b = 0,
      .a = 0,
  };

C11 atomics, C11 threads, variable length arrays, safely reading from an inactive union member, designated array initializers, compound struct literals, implicitly converting a void pointer to a typed one, and the list goes on.