skysight-inc/HackerNews huggingface dataset:
Absolutely love this product, this is such as stupid problem to still exist in 2021 and an elegant solution.

Many of the 3rd party tools described are installed specifically to improve UX and conversion rate - eg measure user behavior, add a chatbot, etc.

And yet these 3rd party tools are unquestionably the largest deficit to load time plus even worse have huge variability.

- - -

Pulling a bit of a copy paste from a previous recent thread but from a "Why, who cares" perspective website (and app) speed are highly correlated with conversion and engagement ->

Google's headline research on the subject says "Improving your load time by 0.1s can boost conversion rates by 8%."

Some add'l data, sourced by Neilsen Group below:

- Google found that increasing the load time of its SERPs by half a second resulted in a 20% higher bounce rate.

- Google found 53% of mobile visits ended if a page took longer than 3 seconds to load.

- Akamai aggregated data from 17 retailers (7 billion pageviews) and found that conversion rates were highest for pages that loaded in less than 2 seconds; longer load times correlated with 50% drops in conversion rates and increased bounce rates, especially for mobile visitors.

- BBC found that for every extra second of page load time, 10% of users will leave.

Here's the best three simple resource illustrating objective third party results from increasing site speed:

- https://blog.hubspot.com/marketing/page-load-time-conversion...

- https://wpostats.com/

- https://www.cloudflare.com/learning/performance/more/website...

Here is a more compelling deeper look from a leader in the UX space:

- https://www.nngroup.com/articles/the-need-for-speed/

Here's a really well written article about how to PROVE to the powers that be that site speed is worth testing:

https://web.dev/site-speed-and-business-metrics/

- - - - -

Very excited about this startup, saw on Twitter yesterday and instantly reached out - look forward to testing.
Hello, I am interested in this position. Can you send me your email so I can send you my info?
... and those developing X.
It's only vmem though is the point. It doesn't really matter that you have 100000 stacks of 8MB when all of that is vmem and you've got a page committed on each.
Caper | YC W16 | https://www.caper.ai/ | Remote | Fulltime Caper builds smart shopping carts - powered by deep learning and computer vision - to enable a seamless grab-and-go retail experience. We differ from other emerging cashierless technologies like Amazon Go because we are the scalable solution. Caper’s autonomous checkout technology is plug and play, meaning it requires no in-store renovation, no operational overhaul, no heavy computations or endless image labeling. Any retailers can buy the carts and their entire store is upgraded with cashierless capabilities. Caper costs less than 1% of Amazon Go's infrastructure. We are already live in-stores and our customers love us! See here: https://www.washingtonpost.com/technology/2021/01/29/smart-s...

SRE [Remote]: https://recruiterflow.com/caper/jobs/65

Software Engineer [Remote]: https://recruiterflow.com/caper/jobs/10

Android Engineer [Remote]: https://recruiterflow.com/caper/jobs/11

Sr. Computer Vision Engineer [Remote]: https://recruiterflow.com/caper/jobs/4

Reach out directly to me if interested at griffin.kelly at caperlab.com
This is completely false in my experience. Ukraine is among the top countries for IT talent, end of story. USSR education (until recently) coupled with very low COL make it a top destination. That's going to decline as most Ukr devs move out of the country though.
Thank you for your kind words! I definitely remember the first 3 months of development when I had 0 users and how it felt. I appreciate your support!
I for one welcome the decline of the desktop. Why, you ask?

Because 35 years ago the desktop was a machine built by nerds, for nerds. iOS has never been that, will never be that. If the desktop Mac goes back to being a machine used primarily by nerds, I'm okay with that.

Developing for the Mac was easy then, your customers were you. You knew that they wanted because it was what you wanted. The same can be said of the engineers working the OS: they had tech-leads, not "marketing". They knew what we wanted because it was what they wanted.

We all got the machine and upgrades we wanted. I would love for it to return to that.
Wayland adds a frame of latency? Do you have a source on this (no skin on this game just really want to find out more about this)
People spend $139 a year on router fees, 40% more than the cost of a new router
I don't know, because it hasn't come up. It's Just Worked (tm) thus far.
There are many things in macOS that have not been looked at properly. That has nothing to do with hardware. It's plain sloppyness.
"Nothing obliges the GNOME team to accede to the wishes of people who contribute nothing to the project"

Nothing, until users flee and they stop receiving bug reports, patches, donations, and so forth. Moreover, because of what Gnome is, if they drive users away it will also negatively impact other projects, because for a lot of those users leaving Gnome means ditching open source software entirely and switching to e.g. OS X.
The Rate of Return on Everything 1870-2015 [pdf]
This ignores the current tend of hosted gaming services. The pendulum regularly swings back and forth between thin and fat clients as cost and innovation evolve.
You can run any block cipher in CTR, there are 3DES CTR implementations out there, same goes for 3DES CFB/OFB modes.
The only one that got wide adoption I think is CBC since ECB was always known to be well a problem.

Counter modes were petty well known in the 80's already I'm not sure what the patent could've been applied for but then it's IBM and their lawyers can probably find a way to patent waking up in the morning.
Games: yes, albiet mostly through Xwayland, which is a compatibility layer. Most games Just Work through this compatibility layer. OBS works fine, but you need a plugin.

Caveat: this applies only to compositors based on wlroots, list of them here:

https://github.com/swaywm/wlroots/wiki/Projects-which-use-wl...

The most mature compositors from this list are sway, wayfire, hikari, and cage. YMMV with other Wayland compositors, and if you have issues with them, you should speak to them, but not blame Wayland in general. If you have Nvidia hardware, you will also have to use the nouveau driver, and YMMV with that, too. I recommend Intel or AMD GPUs, both companies are much more cooperative with the FOSS community.
> Don't blame people maintaining software for changing your routine.

IMO that depends if the software is paid for or not.
If I regularly pay for a software I can have demands.
The last time I tried to use the built in mail app (about a year ago?) I was met with some pretty serious bugs that made it unusable. Not to mention those smart filters didn't work.

It sucks that Apple has let it get so bad, but I personally wouldn't consider Mail part of the OS. It's just a built in App like garage band or something.
Perhaps they should be disappointed in nvidia? Or at least, think twice before buying from them? I don't think anyone here demands anything from nvidia. It's not wayland devs that feel entitled to better treatment by nvidia. It's nvidia users feeling entitled to support in wayland compositors.
Just a quick note about a very prominent user of vertical screens: Professor Martyn Poliakoff, known for the Periodic Videos channel (which I highly recommend).
https://www.youtube.com/watch?v=Oy8ZMFXS_5E
What I mean is there have been vanishingly few transmissions linked to airplanes. Those that have occurred to be on very long haul flights.
Giving a project feedback does not impose any obligation on the maintainers of that project to help you – even if they find the feedback useful. In general, it's rude (and ineffective) to try to unilaterally impose non-trivial obligations on people without getting their prior agreement.

Actual contributions are another matter. If you contribute to a project, then sure, you should get a say proportional to the size of your contribution. And I wonder how many of the people who complain about Wayland have made sizeable contributions?

An important point here is that it's up to the maintainers to evaluate the value of your contributions from their point of view. If you don't respect this, you're again trying to impose obligations unilaterally. That is, offering help that may not really have been wanted in the first place and then expecting something in return.

>If the Wayland developers do not want to hear those complaints, they should not be involved in developing software that millions of people depend on, nor should they have tried to replace software that millions of people depend on.

This seems way off base to me. I hope this attitude is not pervasive because it seems like it's a huge discouragement to people who want to write useful software. (If you succeed to any degree, millions of people are automatically entitled to shout at you whenever they experience some inconvenience.)
> Not because it is novel from a technical perspective.

If I understand correctly, it wasn't really trying to be technically novel. RISC-V wasn't mean to be a research ISA experimenting with interesting new ideas, it was meant to be a decent Free and Open ISA using modern but established design principles.
Because then you end up with something like X11, which we already have.

The codebase could be re-engineered, sure, but a lot of people championing Wayland tend to see this duplication of effort as good for some reason, and at least last I engaged with them did not like the idea of a "new X11."

Personally I think something like that is an inevitability.
Build a carousel without writing a single line of JavaScript (by Stimulus)
> I think your bar is much too low, sounds like you’re saying as long as we’re doing more than nothing that’s good enough.

That's not what I meant, and I'm sorry if it came off that way. What I meant was that we're doing a number of different things that aren't perfect... and I constantly see people complain about it not being perfect so why are we doing it... and my response is that every little bit helps. I agree that we can and should be doing more. I just think saying what is being done now is mostly useless theater is ridiculous and dangerous, and results in people not bothering to take even basic precautions "because it doesn't help".
Universities still do that. It's not that bizarre of a use case
That sounds great, but I'm happy with my hand-bent coat hanger
To be honest, everyone was always asking for this. I already had a public stats page back then, so it was very easy to just include it there (to save my time calculating this manually).
Serverless by Example: S3 to Lambda System Diagram and Invocation Tester
>Looks like their restrictions weren’t that significant in the grand scheme after all.

It's precisely the opposite: it looks like their restrictions made a huge impact in the grand scheme. Basically this dip was caused by their restrictions simply because they cut most of the demand that was driving prices.

It wouldn't make any impact if the supply side followed the demand loss, but it doesn't work like that. Even if people held, the ones that were still selling drove the prices down.

Any restriction on demand is a bottle neck.

Don't forget that this movement wasn't drove by few large players getting huge positions, it was basically done by tiny players with small positions but at volume - and Robinhood was the bulk of the volume.
But doesn't the text have language-like statistical properties that are hard to generate by chance?

I suppose that any sufficiently convoluted random/hoax process could result in a text which had the necessary properties, but it seems unlikely that the hoaxer just happened to have picked a process which was able to convince not just their target market but also generations of statisticians who had not yet been born.

On the other hand, I understand that some of the statistical properties (at the line or page level?) are quite unlike those that are found in known languages, which might be the fingerprint of a process which doesn't preserve meaning, and therefore suggests a hoax.
Okay but why not close angry issues immediately with a cookie-cutter response and avoid stale closing bots? Stale closing bots also have the tendency to close real issues just because nothing has changed regarding the issue in a while.
> The only reason that it isn't apparent to you

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

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

> Humans are simply better at resource extraction than other animals.

Claiming that humans are 'better' ignores my point that bacteria will happily exhaust whatever resources are given to them.
It seems that bonding atoms in 3D using an STM is very difficult, if not impossible. We'll probably have self-assembling molecular processors before then.
As a CTO at my company, I’ve done a lot of investigating of offshoring general cost saving for software development and my conclusions are that you can save ~50% in development costs by hiring a remote/distributed team outside SFBA/superstar cities and offering people a truly remote and autonomous job that doesn’t demand them being on their computers 9-5 and treats them like adults. We have a long track record of hiring extremely motivated and talented developers by offering them this basic non monetary compensation (freedom and trust lol). No need to worry about time zones or cultural differences, just measure folks on output and tell them it’s fine if they want to spend their afternoon with their kids and work mornings and evenings or whatever.
Cohere Health | Software/Machine Learning Engineer | Boston, MA | ONSITE OR REMOTE

Cohere Health is simplifying healthcare for patients, their doctors, and all those who are important in a patient’s healthcare experience, both in and out of the doctors office. We build software that is expressly designed to ensure the appropriate plan of care is understood and expeditiously approved, so that patients and doctors can focus on health, rather than payment or administrative hassles.

This is a unique opportunity to join a rapidly growing engineering team with great ambition. You will have an outsized influence on the future direction and technology decisions.

Our application stack:

- React
- Groovy Grails/Springboot
- MongoDB
- AWS

Throughout the interview process you can expect the following during your time with us:

- A coding test
- Phone call to review with hiring manager
- Virtual pairing interview (system architecture and design)
- Hopefully a quick decision and offer!

Software Engineer - https://grnh.se/d56e23313us

Machine Learning Engineer - https://grnh.se/134c4c363us

Director of Machine Learning - https://grnh.se/1cd680c53us
Off-topic, but I find it funny that the domain you chose means "in a short moment" in Polish... That may not necessarily work for the kind of product you're making. :)
ʇxǝʇ uʍop ǝpᴉsdn sʇɹoddns uǝʌǝ NH 'uɐǝɯ I
First time reading about a distro like this. Looks pretty neat! Isn't this what /opt is for though?
all value is created by labor. raw resources embedded in the earth is useless without labor. food doesn't get prepared without labor. financial transactions cannot be made without labor (even if computers are involved, which require labor to make and program). productivity (growth) is simply labor applied to magnifying other labor, like building a winch rather than applying direct work.

there is a forceful ideological denial of this simple premise by the owner and managerial class, because it's an existential threat, but labor is still the essence of value. that technology can leverage labor and multiply its output doesn't change that. labor can create value that is not yet owned (depending on law), which itself is a threat and why owners focus so much legal fortification on that front.

also note that economists work for the owner and managerial class, providing a powerful incentive for bias in this regard.
Hey that's a bit dishonest. The guy is not calling you a problematic flat-earther if you're simply not using his product. He would be if you were writing angry reddit comments about how Wayland sucks because you heard it sucks, I guess. Are you?
The dissonance is weird: they all but admit that they were just looking for cheap wages all along (see why they left Argentina, for example), but then they come up with bullshit ("spreading the intellectual property", lol) just to avoid saying "we couldn't afford more devs at local rates".

But as someone who's not typically privy to this sort of reasoning, it's a fairly good read and I appreciate them for posting it.
The commonly heard demand is to start working on a common ground, like AMD and Intel seems to be able just fine.

What's your proposal? Requiring paid and free-time spending software developer to bent backward and maintain some complex parallel implementation for EGL-Streams just because NVIDIA always want to be a special snowflake? Even seemingly putting in extra effort to be a PITA for all involved and produce as much extra work as just possible to support it.

With that in mind really nobody can wonder why NVIDIA market share is continuously getting smaller in Linux systems
https://boilingsteam.com/amd-vs-nvidia-are-linux-gamers-swit...
OK. I may want to try it, in that case. Do you know if there is a good guide somewhere to how to do this? The idea seems a bit scary, as X11 is embedded pretty deeply into the system.
Took down their entire site, too, not just their blog. Better get those devs on the phone!
> as far as I can tell it doesn't explain why it suddenly stopped being a problem on OpenBSD.

It doesn't. It's just that as previously with macOS, Illumos, or Windows, the Go project ended up with its back against the wall: in this case, ultimately only the OpenBSD libc will be allowed to make syscalls so their choices are "use libc" and "no Go on OpenBSD".

And in all honesty the followup https://utcc.utoronto.ca/~cks/space/blog/unix/CLibraryAPIReq... is much more convincing as to why it's a hassle to go through libc.
I agree, I was also assuming a worse ratio. However, I tried comparing this with other dating sites and they report better ratios. At the same time, I suspect that FIRE community might be biased towards males (even though I heard that majority of Mr Money Mustache followers are women).
There are not enough developers to even create a new release or review contributor patches.

The Wayland community contributes a fair share due to xwayland, and we get stuck on this quite often.

And yeah, it'll need fixes. over time. It's big, complex, and interacts with device drivers that are very much in flux.
Hack a Human – Social Media, Social Engineering and Business Email Compromise
Rosetta is pretty effective, I don't see any significant difference in performance.
Covid-19: Captain Sir Tom Moore dies with coronavirus
They have other hilarious comments like this about Mexico:

"You would think that since we are so close to them, there would be less of a language barrier"

Because we all know if you get close enough to a person, they'll start speaking english.
> The value for gamers is debateable at best

I don't have a PC or a console and I can play Cyberpunk - in fact the Stadia controller+Chromecast came free with it (because of a promotion).
You are probably right. But directly advertising your product as "GMO-free" helps spread fake-news that GMO may be harmful. Please don't do it.
Clearly a bot or troll. RP2 is unreadable drek.
>Now why does wayland break xclip and vnc? Because "every program is a keylogger by default and can see any event, look at the contents of any window" is a major security issue, especially as it means the entire security model of screen lockers or containerized applications is useless.

XTerm has a secure mode, which even locks the keyboard.
>He predicted society's "collapse", that by now we'd be living in small bands. Global warming steadily making the worse a crappier place is an awful thing, to be sure, but we're nowhere near collapse, at least not at the moment.

Yeah, this is exactly the thing I'm stuck on when I go over these responses. I feel like people really aren't grasping the difference in scale between (a) 2008 financial crisis was pretty bad and (b) dollar becoming "worthless".

People are talking as if those two things are close, or taking up the tone of cautionary finger wagging and saying "well, you know he wasn't too far off" and going off to say this or that about a given poverty statistic.

My best theory as to what's going on here is that people are just cannibalizing the question and using it as a digression into various world problems in ways that don't clearly connect back to the wording of the question.
His proposed solution -- measuring screen size in physical display points -- is futile.

He writes it directly in his article:

> My monitor’s native resolution is [w × h device pixels]. But I find the fonts slightly too small at that resolution – given how far I sit from the screen. [So I use DPI scale factor R, what] translates to an effective screen resolution of [w/R × h/R virtual (CSS) pixels].

(In his case it is 1080 × 1920 / 1.5 = 720 × 1280). Measuring screen dimensions in physical display points, like

var dppx = window.devicePixelRatio;
var screenWidth = screen.width * dppx;
var screenHeight = screen.height * dppx;

reveals nothing about your preferences and conditions.

The moment he decides to get another second vertical monitor and put both just a bit farther he will be back on the square one.

You may have super tiny device with super high density display close to your nose, look at a screen on opposite side of your room that can have same density (what would be a bit wasting resources, but anyway) or look at super large billboard screen across the road.

Until the page will know exactly:
- how far is the screen from eye of its observer,
- observer's eyesight conditions,
- and observer's perceived visual size preferences,
there will be no way to solve virtual pixel problem the way that will make everyone happy.

(And that's quite OK, I think.)
In my professional experience, country really doesn't matter.

What we found to be most effective is clear cut punishments for poor code quality.

We have a itemized list of issues that if we find, the contract would be penalized in points.

Items like OWASP Top 10 count as '10 points' and items like abusing null types are 3 points.

If the contractors exceed more than 15 points of issues in a month we get reimbursed a percentage of the contract. If they exceed (contractMonths * 20 points) worth of issues then the contract is cancelled. Having the 'eject button' is something we've recently added and not had to use yet, thankfully.

Combining this with interviewing the contractors before the work begins has helped reduce defects and having to refactor the code that is build by them.

Overall contractors are a massive time sink, our benchmarks indicate you will need 3 FTEs per 8 contractors to coordinate everything and review the work that has been completed. The quality is usually not the same no matter how much you try.
I don't think Nouveau ever was ported before. I actually tried it myself (unsuccessfully). Kind of a painful codebase.

> usually some versions behind

Currently on 5.4-5.5, only Big Navi is not supported yet. With the state of the GPU market right now, we'll probably catch up before the prices on those become sane :D

Funnily enough, it's Intel that's slowing the updates down more than anything. amdgpu is rarely an early adopter of new Linux kernel API surface. i915 is very much one, all the time.
I personally perceived this as a signaling to female users to motivate them to join more. But the way you phrase this is also interesting.

To be fair, the ratio was not public at the very beginning.