skysight-inc/HackerNews huggingface dataset:
Why did Apple require a 1 day minimum?
Please see https://news.ycombinator.com/item?id=26002420
Because the examples on Google play are even worse?
Even if it does do exactly what it’s supposed to, free software requires marketing, same as commercial software. Make it obvious how to do it, or create a utility that does it for you if necessary.
You can run steam games on Wayland. Spent over 30 hours playing Hollow Knight on SwayWM, even with fractional scaling.
Maybe, but I think it matters when discussing it. If we talk about it like this, it seems that Wayland is to blame. But there's nothing wrong with Wayland [1].

Wayland here ends up often being the scapegoat of a Linux community that looks to want to change but can't sort itself out. The result of blaming these issues on Wayland instead of - mostly - Gnome and KDE means that we're not going to the right places to have this fixed. In terms of bug reports, and contributions of code and money.

[1]: I mean, if you can come to terms with the substantial architectural differences implied by Wayland w.r.t. to X11. But that's a discussion on another level.
Right. 500k / 3 years is well within the "Pocket Veto" levels of funding. I bet they gave some money to cover the development of reports stating definitively that it won't work, in the off chance there might have been something there and someone might get a burr in their butt about it not being evaluated.
TLDR

> The trickle-down theory is all but dead, but there is more to the supply side of the economy than taxes. Thousands of government decisions affect real output and economic productivity. A new supply-side economics would recognize that productivity growth is the right target, but it would reject tax policy as the primary means of stimulating productivity. Instead, it would examine how everything government does — from permitting to procurement — could be improved to increase productivity.

Which is basically saying that lowering taxes is not the only way to achieve trickle-down.

The rest of the article is stating the obvious fact that the poor spend a higher proportion of their income on things that are essential - and it's possible to make those cheaper.

But the criticism of tickle-down was never that it targeted the wrong services (e.g. entertainment instead of housing). The main criticism is that it increases inequality.
Hosting a PR Workshop (Feb.12)
Getting your business media attention takes time and effort but the rewards are worth it.

Do you want to learn how to do PR properly for your startup? Join us on February 12th (12pm ET/6pm CET/4am (+1 day) Sydney) for the PR workshop by our friend Lori, founder of Elssus, a multi-disciplined communications consulting firm. As always, limited amount of free tickets -https://www.growthclub.online/pr-workshop-for-startups

Also a big shoutout to https://guestra.io for making the collaboration happen!
RFID tags inside Amazon products
Did you read the article (which provides numbers to demonstrate that Europe on the whole has kept far more of its schools open than the U.S.), or are you just conflating "the UK" and "Europe"?

Sorry to hear your politicians are inflicting the same pointless abuse on schoolchildren there as ours are here in the U.S.
Amazon’s next headquarters is a glass poop emoji covered in trees
Pinch zooming works on HN, which helps me hit the buttons. I might prefer slide-to-action like narwhal's Reddit interface, but I'm OK with HN not being quite that fancy.
This is be a fine distinction to make if there is an implementation of Wayland that is there. Then we can say this is just about a particular implementation, and not Wayland itself.

If no implementation of Wayland is ‘there’, it seems pretty reasonable to say Wayland is not there yet.
Unfortunately everything became political in this pandemic. Nothing wrong with a bit of national price. Russia inherited a very good scientific base for vaccine research and didn't squander it all, so I think they had a good case to be so risky.
The question is then: is this isolation even useful? There are a lot of attacks that still exist when a program runs in userspace and that are not inherent to GUI programs. Example: creating an executable named sudo somewhere in a directory that is in your ~ and PATH.
I've emailed one of YC's huge successes multiple times over years about how it's frustrating to have horizontal scrolling on a browser that's half of a 1080p display wide (i.e., nearly 1000px).

Unfortunately, the horizontal scrolling UX with substantial wasted whitespace on the sides remains.
And don't fail the same way over and over again
AlmaLinux, the CentOS Linux replacement, beta is out
Who is CB?

Anyway - Extensions based on a minimal subset allow for fragmentation. Yes. Which is probably intended? This can become a problem. Yes. Therefore it should be possible to declare a use case like "all purpose computing" (personal computer) and define a required superset with specific requirements.
e.g. RISC-V "Personal Computing Rev01" shall support the following extensions {list}

And please tell me why a closed source, patented, licensed ISA would be better instead of just saying it's open and therefore fragmented and bad.

PS: Insert here the usual "What's about" for Intels notorious CPU-Extensions or ARMs track of compatibility.
I think the point about root is not so much about whether Xorg is run as root, but rather that any application can then elevate itself as root by listening to the key events to catch your password (for example when unlocking your screen) and then sudo with it.
Chat Yap
Türkiye'de sohbet etmek için ideal bir ortamda yer almak sizlere kurulduğundan beri hizmet veren en iyi siteyiz.
One thing I rarely see discussed - and one of the reasons I don't like Wayland personally - is the second order effect of putting everything in the compositor: It is now really hard to write a "window manager" or window tools. And this leads to a certain uniformity of desktop environments (the big ones, GNOME + Plasma, and then a bunch of keyboard driven minimal environments "for hackers")

What I mean is, back in the day with X11, all clients were equal and there were nice little tools that let you switch between virtual desktops graphically (desktop pagers). I myself wrote a little taskbar (with the kind of glow animation that moves with the cursor that Windows 7 made popular), but never published it unfortunately. A lot of people wrote or hacked on window managers. It was never really easy, but at least it was possible.

Now with wayland, you have to write not only the code that draws the titlebars, but the code that puts the pixels on the screen, input handling, clipboard handling and all kinds of stuff.

Of course you can fork an existing window manager, or use something like wlroots, but they are all opinionated. If you just want "GNOME with different titlebars" someone else wants "KDE with different titlebars" - you're out of luck. So this makes the barrier to entry really high.

On the other hand, if somebody would write a "window decorator" interface, you could write a small window decorator process (like we had with Compiz). I don't believe this will happen, because it would have to be adopted by multiple compositors to make sense. If it did, I would have a bunch of ideas I'd like to try out one day.
> just to maintain that broken pile of shit.

> It has a real cost, you know, being a dick to maintainers.

Which way is it, chief?
The distinction really really does matter, if your argument is "wayland is shit".
Emacs works perfectly fine under xwayland. The recent pgtk feature branch does not use X anymore under wayland. What is not working for you?
Eh, he's probably doing good work in other areas and convinced someone to try out this newfangled doohickey. It didn't pan out, and he's on to other things. That's quite normal in R&D at these levels.
It is actually one of the big, unfixable, conceptual problems of Wayland that all the effort is duplicated in each compositor. The Wayland concept pushes out most of the work to the DEs. That of course will result in tons of predictable inconsistency, incompatibility, bugs, delays, consolidations and general pain. Wayland devs are then generally in the lazy "worksforme, use sway (or whatever)" position while the user (of some other compositor) will be out there complaining to yet another maintainer duplicating yet another feature badly. Lather, rinse, repeat.

Wayland is bad design, and it shows in the users' and maintainers' attrition.
> is there a gop.wikisomething.org

https://conservapedia.com/Main_Page

I have been aware of this site for a while. I always thought it was a parody because everything is so over the top. But a few years ago the admin got in a fight with a left wing YouTuber I watched and I learned it is apparently a real and serious project.
I think the most important factor is not really screen resolution or size, but "cursor precision".

I'm fine with HN on mobile, but it is really hard to press the buttons with my large fingers on a mobile screen. But much easier on a 800x600 monitor using a ball mouse. For HN I don't really mind, as a pinch to zoom.

To check for touch, there is `Navigator.maxTouchPoints` but this might backfire on some laptop which have touch screen (which you usually use for drawing rather than UI, but your mileage may vary).

But I think the core issue is much earlier in design. Many websites and app have complicated design/UI while it could be simpler, and they split their UI into mobile and desktop very early in the design process, which leads to two very different version. And while I agree that mobile and desktop are different experience, I think you can keep them close in term of UI and UX.

For example, let's say you want tooltip, on desktop this is a normal UI control which is natural, but on mobile it is not, so instead of using tooltip on desktop and "think of something" when doing the mobile version, we need to design early for both. Today, many website and apps are designed with a "mobile first" mindset, and this cause problem when used on desktop. The solution is not better detection of either platform, but better design to keep them as close as possible.

Of course, there is also the issue of scaling text vs scaling the whole site, and this is not very well handled by many website, even with the "let's use em/rem units".
No need to be sorry, you do a great job moderating HN dang!

I just felt let down because the promise of the title (which I was excited by) doesn’t match reality in that it’s quite impossible to deliver Datadog’s feature set for metrics, traces, and logs — and tie all three together — on top of prometheus+grafana because the underlying TSDB doesn’t even support the notion of user-customizable indexing. Prometheus indexes all labels, which is why most Prometheus users even have to worry about high cardinality and time series explosion. This is one point highlighting how OpsTrace’s current architecture can not satisfy their positioning; there are many more. I’m sure they’re aware of them.

As an aspiration, the title makes sense. As someone in their target market, I was a bit turned off by the embellishment.
Precisely this.

There's a meta-lesson useful here for anyone who doesn't know it yet: modern software has network effects. And the same phenomena you see with other networks apply to software stacks. If everyone else has implemented a protocol wrong, for example, and your software comes along that has implemented the protocol correctly, but as a result your software doesn't work with the existing stack,

a) Odds are, the rest of the world will not change to work with your software

b) New users, using your software, will perceive the problem is your software doesn't work, not that the rest of the stack is wrong and you're the only one that did it right.

Maddening, but it's the nature of complicated systems built by thousands of people in a distributed fashion.

(I can't lay hands on the link right now, but there was an ex-Microsoft engineer who had a blog where he talked about the heroics MS developers would go to every major Windows release making sure their OS was compatible with popular user software. It didn't matter that they were the company setting the rules in their ecosystem... If the latest version of Windows broke Photoshop, they had to figure out why. In that particular instance, it was because Photoshop had gained some performance optimizations by baking binary images of default structs the OS gave it into their code instead of calling the right API to get a struct properly initialized, saving a library call. MS had to reimplement some C++ structures in C so they could maintain the memory image of the relevant structs to avoid breaking Photoshop).
Sure, i'm willing to accept that - but is your solution for me to buy a new graphics card?

How much of the market share is Nvidia? A stupid quick search's top result says 80%. So 80% of PCs can't run Wayland?

To be clear, i know nothing of compositors/etc, I've had nothing but problems with Xorg, and i want to use Wayland. _and yet_ - it seems like there is not a single PC in my house, or any of my family, that can run Wayland.

I'm happy to accept your statement of where the blame lies. But if you're telling me Nvidia can't run Wayland currently.. does it matter to the end user? When "Most PCs" can't run Wayland his statement of "precious use-case" seems off base.
They can; but they shouldn't expect a life free of complaints.

Commercial software, like most things in life, is responsive to incentives. The people who buy things get the most say in the product.

For open source where the end users aren't buying anything, and the developers are either creating product for their own gratification, or for some more nebulous corporate goal, the incentives are rather indirect. And that makes a big difference. Software, under those conditions, will frankly be worse for the majority of users.
One of the things "Request desktop site" is supposed to do is report a larger effective viewport. For a responsive site, that should switch it to a desktop view. Does iOS Safari not do that?
Ok. Thanks for the Information. But,last time i tried Wayland (sway to be specific) , it didn't ask me to allow/deny ,ie, no audit was present.
The author makes the assertion that if we are all celebrating Apple's latest hardware, it is because the focus on their user interface has faded into the background and they have lost their way.

But reading through the piece the only tangible evidence he provides is more spacing between elements that he is pulling up on 5 year old hardware?

Screen density and pixels have improved dramatically in that time frame, we have larger screens, more resolution, and retina display, it's like switching from Analog to HD. Not every new interface will work equally well on old hardware, but that doesn't mean that the interface has deteriorated.

Making something infinitely backwards compatible will ultimately destroy the user experience, as you can't take advantage of the present and the improvements it offers.

The OS is getting a bit iOS-ified - that I agree with, but it isn't forced upon you to the level Windows does, so it is easily avoided.

I would prefer to have a seen a more detailed breakout of the real degradation in user experience, otherwise it's just a complete opinion piece with no real facts or proof points to offer.
In my experience, emacs is ok with xwayland or in a terminal such as foot. I am using both.
Ah true, MTProto is unique, looks like.
How about less bitching and more making Sway not suck ass and freeze all the damn time?
Not the OP, but I'm on Fedora 33, using Gnome with Wayland (the default) and I have no issues taking screenshots (using PrtScn or Ctl-PrtScn or Shift-Ctl-PrtScn)
Why not? I use Steam under Wayland all the time. (Although it uses XWayland, but it is seamless for me). In fact I prefer it because a lot of games try to do stupid things under X like change the resolution or always put themselves on my "first" monitor (and often mess up mouse inputs if they are moved). Under Wayland they behave much better.

The only thing that I can imagine that you are talking about is lack of proprietary driver support but that doesn't really seem related to Steam.
Different worlds interact by interference. To interfere they must be in some sense "adjacent" so that they can both evolve into the exact same world - but with opposite phase. If you have a huge object like a human it's very hard to get every single atom to line up with those of the other world.
Welcome to globalization.

Some people try to implement fancy heuristics that fails for some users but not enough to care to fix.
Because if what's bothering you is the implementation and not the protocol, you should be talking about fixing the implementation instead of diverting attention to the protocol? I might not understand your question here.
Canada signs deal with Novavax to make Covid-19 vaccine at new Montreal facility
Been rocking wayland for over a year now, screenshots have always worked for me.
NASA pegs the risk of loss of crew for the Dragon at 1 in 276 (https://www.businessinsider.com/nasa-spacex-crew-dragon-loss... the demonstrated risk on the Shuttle over the lifetime of the program ended up being 1 in 68 (2 in 135 launches).

For comparison, the risk on a commercial airline flight is less than one in a million.
Thanks! Can you give a general idea of what the interview process is like?
> As an amateur developer, I've often found that "Why would you want to do that?" is followed by an explanation of a much better way that I hadn't even thought of.

Unfortunately in my experience it is often followed by an explanation of why what I'm trying to do isn't what I should want to do, as though I am not aware of my own goals and constraints.
I still have mouse and keyboard issues under wayland + gnome. This bug causes the ui to drop mouse and keyboard input events whenever the rendering takes too long to complete

Issue tracking:
https://bugzilla.gnome.org/show_bug.cgi?id=745032

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/749
Well, it's no surprise that a product with a battery is less resilient than a product without one. But those products don't compete with each other.

Also, cheaply available, standardized batteries don't address your e-waste concern either. So your post doesn't seem much different than someone being indignant or even sanctimonious about the wireless preference of others.
Better? Not even close.
The reverse is also true.
Don't blame people maintaining software for changing your routine. You make a lot of assumptions there but the reality is often much more nuanced.
Everything changes, all the time, that's a rule that is true for absolutely everything in life.
If nothing else, because X.Org is effectively no longer maintained. Redhat announced in 2019 that they are basically the only ones who even try to do any maintenance and they do not expect there to be a 1.21 release. In fact no one seems to want to manage a 1.21 release.

Wayland still have bugs, but as Drew DeVault writes: They are fixable and importantly there are people willing to work on Wayland.

One of the more pressing issue currently is the Nvidia drivers, but that's not the fault of the Wayland developers. Users need to complain to Nvidia about that.
What Happened to GME – Under $90 Track Live
> It's not just the FOSS community, look at how non technical people react every time gmail, outlook or excel makes a tiny change to the UI (not to mention big ones). It really makes people angry when things don't work the same anymore, let alone when it doesn't even work anymore for their use case.

Like you note, this isn't a problem unique to Linux/"free Unixy OSes". In some ways Linux is actually worse than others, consider Gnome/Gtk Updates for example. Or how things like having a library to read a particular image format are quite normal around here; except that library has like half a dozen incompatible but actively used versions and around 1000 released versions. The Linux environment is very volatile and everything constantly changes and breaks. Modern applications bitrot exceptionally fast in Linux, while the community points to "but look this Xchess binary from 1992 still works". That's neat but covers few real use cases. The same community is then bewildered that both people and enterprises opt for distributions which move at a glacial pace and only releases updated software once every five years or so.
Sounds like an awful lot of Apple elitism and not a lot of solution-brainstorming. I though people were aware that this was the Apple experience: You use their software, and when something breaks/doesn't work like you want it to, you forfeit your right to complain. Maybe OP would prefer a Linux machine and just doesn't know it...
"Here is the academic background of the writers of The Simpsons:

J. Stewart has a bachelor’s in mathematics from Harvard and a master’s in mathematics from UC Berkeley.

David S. Cohen has a bachelor’s in Physics from Harvard and a master’s in computer science from UC Berkeley.

Ken Keelers has a PhD in Applied Mathematics from Harvard.

Jeff Westbrook has a PhD in Computer Science from Princeton University."

Even better (from presentation of science) - Futurama!
Open Confidential Computing Conference 2021 (free and online)
> but can be hacked around by using a wrapper script to launch things with different DPIs

I have firefox windows on both monitors, and like to drag tabs over from one to the other.

Under X11, doing so is either impossible, or requires restarting firefox, which really isn’t something I’d wanna do.

There was an old XUL extension for firefox to parse QT_SCREEN_SCALE_FACTORS and apply it instead, but that’s long gone. And normal Gtk apps never worked properly.
In my experience Gnome is the worst major FOSS project for this. Ever since Gnome 3 the design philosophy of all of their projects seems to be "find out what the users want and do the opposite."
> I don't understand how that gives you dictatorial power over 100s of users who don't like the changes you've made.

It doesn't - you are completely free to roll back those changes, or make different changes of your own.
Ask HN: How to measure/determine the quality of the CSS code?
I hope we have CSS enthusiasts here.
I wonder how you would answer the following question:
How to measure/determine the quality of the CSS code?

These are my favorites:
File size, File structure (for Sass or similar), Usage of inline CSS code, Number of !importants, Usage of modern features (Variables, Grid, Flexbox, etc.).
Location: Mumbai, India

Remote: If needed

Willing to relocate: Yes

Technologies: .NET(C#), Azure Cloud stack, git, Unix, bash, C/++, SQL, NoSQL, Moq, XUnit testing, CI/CD, Jekyll

Résumé/CV: https://ohyash.github.io/YashY_Resume.pdf

Email: yashyadav.710@outlook.com

Hi, I am a backend developer with 2 years of experience.
I've written APIs, serverless functions and webjobs from scratch - keeping test coverage above 80%. For an Azure based cloud native webapp. That's mostly in C#.

I'm open to learning new technologies and also explore some for my personal projects - Ruby/Jekyll for by blog(https://knowledgeday.in), Python for a trading simulator, Embedded C for some board projects...

Portfolio: https://ohyash.github.io

Linkedin: https://linkedin.com/in/ohyash/

Twitter: https://twitter.com/Ohy4sh
For symmetric encryption, as your parent explained, yes, simply double the key length and you're fine. (In practice you might get away with less than double because it seems unlikely such quantum computers, even if eventually constructed, would be similarly cheap to conventional computers)

But for asymmetric (public key) encryption the larger key lengths barely help, so you'd need infeasibly enormous keys. e.g. terabyte RSA keys have been "proposed" facetiously for this purpose.

Thus, Post Quantum Encryption research is mostly interested in finding solutions for two asymmetric problems: Key Agreement (a replacement for today's Elliptic Curve Diffie Hellman) and Signatures (a replacement for things like ECDSA) that would survive an attack by a larger quantum computer able to execute Shor's algorithm.