James_K

I dislike when people use the term “power” to describe making code slightly shorter to type. Operator overloading is not in any meaningful sense more powerful than a language which lacks it.

I think the better conclusion here is that most programming languages don't deserve Wikipedia articles. You wouldn't want one for every brand of screwdriver or kitchen appliance. Programming languages are likewise, just tools. An article restating the information on Odin's website is a net negative to anyone who reads it, as they'd be better served by visiting the website directly. A bad article should be deleted.

Suppose you wanted to make a Wikipedia article on a certain brand CNC milling machine, would that be useful? Not really. The only thing ever written about it is its own manual, and it doesn't feature notably with the exception of being used by some companies for manufacturing. Programming languages are the same thing. It seems rather entitled to demand Wikipedia articles for random brands of tools that don't have anything particularly significant about them.

And beyond that, it's perfectly useless. A Wikipedia article restating the information on Odin's website is a net negative information wise. You've got duplicate content for no good reason. The point of Wikipedia is to take a topic about which much has been written, and distill that into a smaller and more information dense summary. A person who finds the Odin language on Wikipedia would always be better served looking at the website instead, and thus the article is actively harmful to their understanding of the topic.

Sad that we don't see more high praise of simple things. Not exciting enough, I guess.

Letting users pick their own passwords has always been a mistake. If passwords are needed, the system should choose them.

This could have all been solved if they added a setting for bread, pizza, or cake.

I've always doubted this stuff because I have some memories of things that happened when I was 2.

I will never stop singing the praises of plain HTML. It's accessible, it's portable, it's simple, but for some reason we need horrid JavaScript nonsense to operate.

POLAND MENTION!!!!!

Meditation from first principles.

I feel that Postel's law probably holds up the worst out of these. While being liberal with the data you accept can seem good for the functioning of your own application, the broader social effect is negative. It promotes misconceptions about the standard into informal standards of their own to which new apps may be forced to conform. Ultimately being strict with the input data allowed can turn out better in the long run, not to mention be more secure.

But it's not “lots of people,” it's everyone. Everyone has a picture of their face on their phone. And the information is encrypted because phones use disk encryption by default. “Someone can get a photo of your face and passport if they have full unencrypted access to your phone's hard drive” is like saying “someone could turn off your alarm and make you late for work if they break into your house.” There are simply bigger concerns in that situation.

The “hack” in question is pointing out that the app forgets to delete images of the user's face and ID (stored). A lot of people have pictures of their face already on the phone, and often their ID as well so this is hardly a security flaw in any real sense.

She could have accepted the Email, then printed the documents off and said it was faxed. I highly doubt anyone checks.

Working for an organisation which systematically abuses and degrades disabled people is not a morally neural act. If you're life is difficult then that's sad, but not an excuse to exact that difficulty 100 fold on other people.

I'm almost certain this is from the UK, and here we have a government that is absolutely obsessed by the concept of benefits fraud. Every real analysis has shown that virtually none exists, but it is a good excuse to tighten up the government budget by trimming some fat (disabled people).

That is not a problem with Wayland because specifying this is not a within the purview of Wayland. People like you don't seem to understand that Wayland is specification, and not an implementation like X11.

I think you've got it backwards. Applications like OBS do not typically register default global keybindings to avoid clobbering, you have to do it manually in their settings menu. The only difference with a generic interface is that the dialogue opened from the setting menu would be from the WM instead of OBS.

Or you could write portable software that doesn't rely on reading global input. OBS you give as an example, and it is a good one. They could simply register a D-Bus handler and provide a second binary that sends messages to the running instance. The software is more general in this way as it allows full programmatic control. A Sway user, for instance, could add

  bindsym $mod+r exec obs-control toggle-recording

If your disdain for desktop isolation is so great, you needn't even use D-Bus. Registering a simple UNIX socket that accepts commands would work equally well in this case.

What's really desired here is a standard way for programs to expose user-facing commands to the system, which is clearly not within the scope of the specification for a display server. The problem with X11 is that it has for a long time exposed too much unrelated functionality like this to the user, and so many apps have become reliant on this and developers have neglected the creation of portable ways to achieve these objectives. A new specification for display servers that excludes this harmful behaviour is a clear long-term positive.

How many keybings do you have and how often do you try new window managers? Compromising the security of the whole system just to save you a few `sed`s when writing some config files seems like a bad trade off.

I'm using Sway right now and I have key binds. Not sure why you think that's impossible.

Reminds me somewhat of Vulkan. I think the trend of making the actual specification of something lower level and less convenient is rather logical. Why burden implements with a load of convenience functions when that could be left up to libraries?

The biggest fertility distributor is probably sugar by a country mile. Being fat screws with your hormones.

Performance and size can easily be added to any specification, maintainability is not a problem if you never have to maintain it, UI/UX are design issues not code issues. If you specify a UI, it will have the UX you want. We can already do UI creation with visual editors.

  import Mathlib
  def Goldbach := ∀ x : ℕ, Even x → x > 2 → ∃ (y z: ℕ), Nat.Prime y ∧ Nat.Prime z ∧ x = y + z

Just use RSS at that point. I don't see the value of encrypting everything, like people are gonna be spying on your random static blog entries.

If you are interested in multi-byte access to GCed arrays, something similar can already be accomplished. You can hold the array data in Wasm linear memory, then have an object that wraps a pointer to it, and using JS code, associate a finalizer with that object that frees the related section of linear memory. It's essentially how FFI memory is handled in most native GCed languages.

Taste is about understanding what people want, and what they don't even know that they want.

This perception, for what it’s worth, runs counter to statistics: Between 2000 and 2022, the years for which data is available, only 0.5 percent of startup venture funding went to LGBTQ+ founders.

The article seems to admit that its central premise is entirely made up. If a conservative 3% of people are some flavour of gay, then they are 6-fold underrepresented, at least in this area.

Describing it as a market is not entirely correct. The clothes these people wear are garbage. As a species, we produce more clothes than we could ever wear. I am reminded of a story of a charity that accepted clothing donations for the victims of an American hurricane, and immediately had to stop because their warehouse filled up. Many clothes are not even worn once before they're thrown away, and one of the cheaper ways to dispose of them is dumping them on 3rd worlders. It's quite dystopic really the underclasses who dig through our trash.