skysight-inc/HackerNews huggingface dataset:
> if the author's rant truly reflects the attitude of the community, it's sounds pretty toxic.

There's been a lot of external hostility and conflict over the years. Which unsurprisingly affects community culture.

And the reverse too. I recall encountering surprising "yikes!" even early on, from excursions from professionalism, tone-deafness, and groupthink. Which didn't help with external harmony.

It might be interesting to explore sometime, what might have been done differently long-term, to perhaps have gotten different dynamics. For instance, if replacing X11 had been envisioned as first a broadening of alternatives, and only then a narrowing to a new standard. Open source often uses forking and competing projects to defuse hostility and keep people engaged and productive. Coping gracefully with "lots of diverse everyone trapped on the same boat" isn't its strength.
He's saying, literally,

> So my new approach is “fuck you”. None of the Wayland detractors have a clue.

Lumping everyone who may not have a rosy view of Wayland together.

There's a good comment by an (alleged) pentester mentioning how Wayland doesn't really buy you that much. He's right. The bigger issue is lack of isolation within a gid. I can still debug your terminal and try to get your root password.
Summary: "we failed on outsourcing so many times that the costs exceeded any possible cost savings, even taking into account future projections."

Imagine how much it cost them to build up and tear down development teams six times. Not just in real costs of contracts and such, but also the logistical costs of training the new teams, building the relationships, finding faults, correcting errors, determining alternatives, knowledge transfers, etc... Not to mention opportunity costs of all the time spent.

Effective outsourcing is paying AWS/GCP or Heroku for whatever they can provide. Not trying to turn an expensive employee into a cheap one.
One of the original selling points of the iPod touch/iPhone was that it could display full desktop websites...
Every other boundary can be restricted relatively easily. For example, flatpak already solves the issue you mention.

But the X11 boundary can’t be resolved unless you put a whole X server into every single application’s container with XonX, or you replace X11.

Which is part of why wayland exists.
ummm, how? When I hit the green button for full screen, it takes over the screen like a Spaces screen. How are you able to have side by side full screen of 2 apps. That seems like you are breaking the definition of the word full. If 2 apps are "full" screen side by side, you either have "half" screen views or 2 monitors.
Yeah, bought a M1 Mac Mini to tide me over until I can see more directly where Apple is going with iOS/MacOS and touch devices.

I really want a new iPad (still using an original iPad Pro 9.7") and a new MacBook (using a Pro 2016 for now) but I'd prefer a device that could replace both.
Absolutely. When I read the headline, I frowned, because I’d call it quite rare for sites to mishandle my 1080×1920 displays, though not unknown.

But then I read to “720×1280”, and… well of course, what did you expect?
No I do agree it's a general problem with software, but we're not talking about some rando throwing leftpad code up on GH. We're talking about a set of operating systems that clearly want more mainstream adoption being bewildered when they suck at respecting the user.
It just has to meet the standardised baseline that is already defined and all Linux distros use. For all the extensions, Linux has various well established mechanisms to detect and utilise varying CPU capabilities, these are necessary and used on many other platforms.
What was one example where a simple solution was over-engineered?
(I ask this in order to help me better avoid my own over-engineering habits.)
That is what the OP says: they sound great but you will not be able to reproduce that kind of sound with other headphones because it is dynamically modified (it is what OP calls "fake").

Not criticizing, just stating OPs argument.
Which proves the point that even when games happen to be natively written against a Linux userland, with native support for Vulkan, it isn't economically viable to sell them on GNU/Linux.
First, back to basics:

1. Hammurabi: Limit violence, don't create it.

2. Magna Carta: Apply the law equally, or there is no law.

3. Bill of Rights: You can't really tell someone else what to do all the time without their consent first. You do it. If it works, I'll do it too.

4. Nonviolence and Forgiveness: Keep up the bullying, and eventually those who don't fight will find someone who will, and they will be far worst than what you have now.

5. Mutual Respect: No one is ever defeated. There is an infinite amount of people in line waiting to take their shot at you. Victory in battle only means a tougher enemy has left home and is on their way to defeat you. Learn to control your own emotions, worry about yourself leave other people alone, and not provoke other people.

6. Natural Law: Don't cross great rivers. Don't build expecting uphill flow or the western sunrise. While others have to stand for all Russian speaking peoples or mandate under heaven or the green flag of Islam is to fly over the White House, take the other side of the table. What's the minimal you have to do to be called a government, and just do that and nothing more.

With a strong basis of above, you can finally have some fun:

7. Keep Lofty Goals: To hell with solar panels, childish toys bought on loan, callous authority just to make another boring tv star. Sail to the center of the sun itself. Envelope our solar system. Melt anything that dare offends me. This is not some far off dream. With advances in matter waves, gravity applications are on the table. Humanity is the king of the sun. All revolves around them. After them, darkness, and the flood.

Start with the mass driver.
We do, wlroots. But it came _after_ mutter, and maybe even kwin, so right now there are basically three.
This is confusing - "works for me" is a common joke. The point of that phrase is usually that it is not a good reason to minimize those for whom it does not work.
Ah, yes, though that reverses each line of text individually while maintaining line order, versus reversing the whole file.
It started as a fork of Firefox when Mozilla decided to restrict UI customization, and make most existing add-ons incompatible. Partly it was also about how these changes were communicated. That was a couple of years ago.

For a while it was a better choice over the redesigned Firefox ("Australis"). I then switched to using Chromium, so not sure what the situation is now but it can't hurt to have more choice.
How did you validate your idea? With this hackernews post?
There is no formatting support for it, it seems you can use Unicode bold formats or something. Doesn't seem approachable or trivial...
The entire article reads like it was generated by GPT-3 after being fed a bunch of early 2000's MBA material.
The point is that RISC-V allows people to build their own tweaked / extended processors without having to pay an ARM and a leg for it.
My limited experience has been that you get what you pay for. I have worked with some really top tier developers based in India, but they were quite expensive (relatively).
Thanks, I do think it's useful and practical to think about docs this way in four quadrants, and identify where your current document should live on the plane.

FastAPI's docs (recently front page on HN) are a great example of focused, concise documentation that knows exactly its purpose.
Pure Wayland (no xwayland) sway user here.

Screen sharing is a pain, I did get it working on Arch finally though, but it's still a pain at this point. And I only got "screen" sharing i.e. not "app sharing" or "monitor/virtual-monitor sharing" working. Latter part could well be some more config or tweaking I need to do, regardless it's not the users fault if they can't figure this out in Wayland when it works fine everywhere else out of the box. I've gotten it to work well enough for my personal use case but it's definitely not far enough along for the typical use case.

X11 isn't that great with monitor setups with multiple DPI. It's certainly one of the biggest user facing "wins" for Wayland but much like you dismiss playing WoW as something you don't do most users don't deal with mixed DPI setups so the biggest "win" really doesn't mean much to most. That doesn't mean it can't be a great reason for you to prefer Wayland though.

Sway won't even launch on my Nvidia computers so I've just got them running Windows with WSL. I don't think it's X11/Wayland's fault on this one, Nvidia is just a bit too locked down when it comes to Linux preventing good support from anybody. At the same time the professional hardware is just better so you don't always have a choice to just use an AMD card even if you were willing to change hardware for better support.

I really like my Wayland setup but it's important to understand the tradeoffs I was willing to make and the efforts I was willing to put in don't mean Wayland was perfect it means it was better for my situation. For another user it's probably a HORRIBLE fit right now. That's not their fault, nor anyone else's fault, it's just a difference in use case.

I think Wayland is getting pretty close (particularly for the less stubborn willing to let xwayland run as well) to being ready for most users but that's what many have been trumpeting for 5 years so it's created a bit of pushback when you say it is now.
That makes sense on the surface, but you should design for all possibilities, current and future.

I learned this lesson the hard way. The client was on desktop. The users were 40% phones. Everything was great for months and months.

Then one day the owner of the company that owned the company tried to look at the web site on her grandkid's iPad. Fan met shit that day.
By Sale's measures, and since the time of Sale's prediction. I don't care for comparing this year to the past 400 years on issues like poverty, etc, people only do that because it makes them feel better so they can continue on ignoring problems. Equality and environment are clearly on a downward trajectory.
Outsourcing looks attractive only to bean counters. There are prohibitive issues that take full-time competent management, even to break even. Such as time zones, language, currency and banking, export rules, contracts, internet delays and outages, cultural conflicts.

We even had politics interrupt development once (on the daily conference call, he said "We're having a revolution outside my window. I have to go.")
Your entire staff would never ever leave at once UNLESS you really messed up big.

Thinking anything otherwise is ridiculous nonsense.

This specifically reminds me of when a company I worked for fired my two developers by making it so they couldn't clock in. They didn't have the respect to tell them to their faces or to tell me who they reported to!

Yet they seem surprised when I quit the same day.
Cool, that's the theme WordPress recommended to use as default in 2020? Maybe I should ask them to buy me a Hi-DPI monitor... that would display a bit more content, but actually I'm afraid the lonely column of text in the middle of the screen would look even worse.
>And yet quotes don't wrap to any specific size, so you end up with an awful horizontal scroll bar.

HN doesn't have a "quotes" feature. Some users here have the unfortunate habit of abusing the code formatting feature for quotes.

>There is no way to have avatars or some other ways to distinguish users

Thank god. There's a lot I miss about forums, but avatars and huge signature blocks are better left in the trashbin of history.
Many words, few ideas. I was hoping for an argument based on ... well, anything. There's no real criticism of the scientific support for the idea that human minds are predictive. Just some vague connections to economics and a vocabulary that suggests anti-capitalist sympathies. Your attention is better spent elsewhere.
I acquired an old Mac SE/30, a Quadra 650 w/ a Radius Rocket, and a NeXTstation Turbo specifically because I wanted UX & UI inspiration (and sanity checking) as my company began to transition from the nuts and bolts of our first product to the facets that are user facing. Everything from the workbench GUI, to the CLI, to even the config files & SDK.

It was immensely helpful to be able to sit down in front of something and interact with thoughtful pervasively reused metaphors & mechanisms all seemingly integrated individually with the global goals of the software always front and center. It was a great mental counterweight to what I find to be much more common today, which is disparate components seemingly made by different teams, each with their own non-overlapping set of human interface guidelines, all crammed together on screen in ways that seem to indicate the organization structure of the company that created it rather than the needs and enjoyment of the user who's going to work with it. Egregious examples of this that are top of mind are JIRA and Salesforce, but they're hardly alone in this regard.

Using those old systems w/ their extremely dated UI aesthetics, but still being extremely enjoyable & productive to use was a constant reminder that the UX being well integrated and consistent is at least as valuable to the experience as it looking slick.

That said, I think this matters a lot less in an "appified" world where your tasks as a user are already incredibly discrete and faceted for you. The scope of interaction is narrow and focused and so there's not nearly as much need or incentive to have a "globally" consistent narrative that stitches together with everything else, because you're mostly having transient task-specific interactions. For example there's not as much need for hailing a ride in the Lyft app to compose well with picking a show to watch on the Hulu app. Everything is a discrete purpose built experience, and to some extent I actually think this is appropriate for the use and medium of apps. The challenge seems to be that software which isn't like that, and is something you actually sit in front of an work with at length as a central hub or part of a much larger workflow, is being put together in the same way as discrete little purpose built apps instead of as a coherent broader interaction framework.
This is likely not a useful explanation if you do not specifically know what a a Phase-Locked Loop is, but I want to say that it is yet another example of how negative feedback can give you an implementation for the inverse of a component.

In this instantiation of the concept, a frequency divider (dividing by a whole number) is something that's easy to build: it's a counter. For example, to divide by 100, count the input clock, when you increment from 49, wrap around to 0, and toggle the output.

Putting that divider in a negative feedback loop gives you a multiplier.

Another common instantiation: if you put a voltage divider (easy to build with a couple of resistors) in the feedback path of an operational amplifier and you get a voltage multiplier.

Another instantiation with op-amps: Put a capacitor in the feedback path, and you "get" an inductor. This one is also a big deal because, practically speaking, it's easier to engineer close-to-ideal capacitors than it is inductors, which are heavy and lossy.

And if you really want to take a ride on this conceptual train, consider that it's easy to square a number. Need the square root? Use negative feedback: https://en.wikipedia.org/wiki/Newton%27s_method#Square_root
Hi, author here. This is precisely the takeaway of the post.

It's more of a collection of pet peeves about AES (in general) and AES-GCM (in particular).
A Review of Two-Dimensional Programming Languages (1972) [pdf]
How to implement React useState patterns in Svelte
Ah, I remember 7 years ago trying to decide whether I'd switch to GoboLinux or Nix. I choose the latter and don't regret for a moment, but I'll continue respect GoboLinux and have the found memory.

I think the big difference is:

- Nix: the filesytem is rarely the right datastructure (I agree) other things are needed.

- Nix: Store and Nix too is more freeform, package / distro norms provided by higher layers (Nixpkgs, NixOS)
Agreed. And yet it's somehow ascended to being the default environment for Fedora, Ubuntu, Pop!_OS...
A lot of nonsense in this article, but I'll try to address his points:

(1) There are several royalty free implementations, ranging from the minimal (PicoRV32) to widely-used embedded (Rocket) to reasonably high-end (BOOMv*). There are also proprietary implementations, and this is how it should be.

(2) RISC-V has defined various platform specifications which means in practice ISA fragmentation is not going to be a thing. The platform will define the minimum set of extensions, and the rest will be probed at runtime (which is exactly the way x86 works).

(3) About economics - the author ought to read some Clayton Christiansen, or maybe take a look at how companies like Intel, AMD and Arm came to prominence.

(4) Yes, open spec != open implementation, but see point (1).

(5) RISC-V has been designed by experts in the field and adopted by some very large hardware companies with experience and who ship in very large volumes (millions and billions of chips). It may well not be perfect, but it doesn't need to be in order to be successful (see also x86).
I think that's fair, but they have done a good job of bringing much of the industry on board, rather than just being an esoteric hobbyist project.
Show HN: Payymail – Turn followers into paying clients
Sounds a bit like how Homebrew works (or used to, anyway). Based on my experiences there, one of the big issues with just keeping all versions of everything is that you end up with problems when you're trying to build/use packages with a large pool of dependencies, especially when the dependencies are interlinked.

We used to get problems like this when building ROS on homebrew where you'd have a bottled version of Gazebo (a robot simulator) which had been linked against specific versions of boost, python, opencv, whatever. And then a new version of one of those dependencies would come out, and something else in the tree would update ahead of Gazebo; now suddenly you've got Gazebo plugins which crash with ABI issues and you have to go spelunking to find out which binaries are linked to what and where the conflict is.
Real-Time Analytics with Presto and Apache Pinot
Haha, yes, it's definitely a balancing act! Thankfully analytics and heatmaps are a good start to figuring this out (even without applying common sense fundamentals)!
Do you seriously believe that was a response, by the CIA, to this raving conspiracy theorist?
I don't think you'd need to bond them.

I imagine you could put down a "wire" of metal atoms without too much trouble. Something like a capacitor shouldn't be too difficult if you could put down a dielectric.

Not sure about how to do a transistor - maybe there could be an alternative "switch".

Yeah, I'm hand-waving. And maybe the metal substrate an STM uses is a non-starter.

But still, atomic precision seems to be in hobbyists reach and I imagine SOME approach to low volume tiny circuits are possible that would not be economically viable in terms of RnD and fab for "big silicon".
Or, alternatively, that companies with large codebases face similar issues of complexity and legacy interactions that aren't easy to just throw people/resources at, they just take the time they take in order to get it accomplished and persistence is preferred over alacrity.
It also brought to mind this probably-apocryphal story (from Anton Braun Quist, "Excuse me... what was that?" (1982), a collection of engineering tall tales):

"Secret Weapons"

"The U.S. engineers perspired over their task, rapid development of several identical, extraordinarily complex machines. The work was finished on time, and the machines were flown away to be parachuted into various parts of Germany. It turned out that all the devices were discovered by the Germans."

"Then the German engineers perspired, throwing heavy manpower and resources into examination of these new weapons. What were they for? They were designed to occupy a large number of German engineers; that's what. And they did."
I guess I interpreted the original comment as RISC vs CISC and an M1 is RISC, though not RISC-V.
Pencil Tower Hotel Sydney Skyscraper
Hi guys, quarantine 3 project 3 (2 previous were fassttt.com and searchiiing.com).

Trying to simplify how experts communicate with clients.

Expert set a weekly price and an alias email to interact. I only forward emails from paying clients and automatically bill the others.

Stack is AWS (Lambda, SES, DynamoDB, API Gateway, S3 and CloudFront) with Bluesnap for payment.

Are you an expert/consultant? What are you currently using to manage clients? How do you bill them?
I am 100% convinced that if Twitter expanded their verified account program then these types of attacks would be rendered obsolete very quickly.

It just doesn't make sense that there is no way for an average real person to get verified and display an instant signal that differentiates them from a fake bot. It's absurd and it causes real harm.
> Such as your screen locker, [...] or your graphical Apt client?

No, not if input is grabbed, sorry.

> your terminal with a sudo prompt in it,

Pinentry&co are mainstream for a number of years.
Nobody's making you use it and calling somebody's work "cringe" is pretty rude
WasteNet: A botnet designed to waste as much advertising cash as possible as quickly as possible.

Download the Chrome extension and you can "adopt" bots which will be used to destroy more and more ad value.
That's fine, I know. But acting like Wayland is feature complete when it obviously isn't is pretty ridiculous. Instead of solving hard problems the Wayland maintainers are acting like you're stupid to want to have the features solving the hard problems enables.
Because it's hard to write a "you're being a dick" cookie cutter response for every possible case. People are dicks in a huge variety of ways. I don't enjoy figuring out prose that won't offend people, I enjoy writing and reviewing code, so I do that instead.

No solution is perfect, but this one keeps me sane.
Interview with Maryam Mirzakhani, first woman Field medalist (1977-2017)[pg. 13]
> Claiming that humans are 'better' ignores my point that bacteria will happily exhaust whatever resources are given to them.

So will most other animals. This isn't something unique to humans.

> I notice both commenters referenced cats - a domesticated and invasive species.

Foxes and coyotes, which I mentioned, aren't. Most predators do this (gratuitous killing) to some degree or another. Even some none-predators engage in "pointless" violent aggression towards other species.

> It is apparent to me that no other species (ever) has been implicated in a mass extinction event.

Only because most other species (since cyanobacteria) are drawing from a more limited pool of resources. Other species certainly do radically transform their local ecosystems which leads to disruption until other species move in to fill the new niches. What makes humans different is that our "resources" encompass a much broader area and array of material than other animals.

There is no steady state in the absence of human intervention. I am not claiming that humans are 'better.' They aren't. They're just another animal, just one unusually adaptable thanks to big brains, language, and thumbs. I'm not assigning any more value to that. In the long run, it might be a 'bad' thing, in that, as the comments here show, we tend to be much too proud of those big brains.
Sure, I admit that it's a generalisation. I'm just offering my experience with outsourcing.
His problem is not really the vertical screen, but that he is virtually scaling the monitor down to 720px wide.