skysight-inc/HackerNews huggingface dataset:
The app I work on is plagued with this issue. I just wish I was given the time to go around and fix it everywhere.

As with so many of the issues in web apps, its not even complex or hard to fix these issues. Its just no one cares enough to schedule time for it.
IPython for Web Devs
If you want more blog posts for Hacker News, take him up on the offer and then blog about it: "Cperciva replaced our millions of Lambda invocations with one m6g.medium and now I'm stuck as a FreeBSD admin!"
It is basically self-imposed carbon credits, since carbon credits are not politically viable or something.
72 means it wasn't stuck on 71 and something is still happening.
You know the thing I worry about next: how are apps going to inevitably bloat in inefficiency and claw back the improvements in CPU?
Laser fusion reactor approaches ‘burning plasma’ milestone – Science – AAAS
My ideal spinner would be a decreasing arch, telling the user how much time remains until their request timeouts and fails. Uses the same space as a spinner, but conveys more information.
Hey everyone, I designed this desk to solve the messy cabling in my home office. Cables are embedded inside the desk itself, organized and out of sight. Cable routing inspired by circuit boards. Do you guys see the value? Who would appreciate this the most?
I care; caps do suck but given the choice I'd rather have double the speed at half the transfer cap. To be clear, by double the speed I mean half the latency between requesting a resource and page load, which is a significant amount of my usage pattern.

If something (like uploading a backup or streaming a movie) is going to run for a long time, I don't care how fast the average speed is as long as it's enough to stream 1080p.

But if my next task demands some info from a 20MB datasheet that I don't have locally, I want that to load as fast as possible. And I'm not going to do that 25,000 times a month.
In other words, the interesting comparison is two log histograms (or overlaid).
Dupe: https://news.ycombinator.com/item?id=25194795
> In other words, the actual number is not important...what is important is real feedback that things are still happening and it's worth waiting.

And the inverse is that when progress bars are fake, they tell the user that everything is working even when it's not!

I MitM my SSL traffic. This causes Figma to fail to load documents in the most annoying way possible—it shows a progress bar that never stops moving, but becomes increasingly slow as it nears the end. I suspect the bar is programmed to never increase by more than half the remaining distance, or something like that.

After half an hour, I finally realized something had to be wrong, and I tried whitelisting figma.com in my proxy. The document loaded immediately.

If Figma hadn't lied to me with a fake progress bar, it would have saved so much time...
I often see the suggestion to display spin animations instead since estimation is often incredibly difficult if not impossible. I prefer progress bars because even if they aren't accurate, the relative directional growth shows me that something is actually executing. With a spin animation, for all I know, somethings caught in a loop.
A flat tax is predictable; that also has value and reduces economic friction.
That one has always felt suspicious to me too ...
Price/perf of this is hidden by the tiny slice of hardware you get. Equivalent to my Hetzner machine would be 116 Euro/mo. before accounting for the 10x higher peak bandwidth, 2x capacity dedicated NVMe, 4TB of magnetic storage and 100GB of backup space I get for 60 Euro/mo.

I have no idea what "1 vCPU" means in this context but severely doubt it even means "1 hyperthread", unless the physical hardware were something like dual 16 core or single 32 core chips.

Definite pass
> FWIW if they printed comics as half page color prints weekly (and not just gag strips) I'd subscribe to that. As newspapers were dying they seemed to cut back on that sort of thing though.

You might be interested in subscribing to the dead trees version of the Funny Times:

https://funnytimes.com/subscribe/
Yes and no. The XNU kernel is, to oversimplify greatly, BSD glued into Mach. At least historically, it had BSD kernel code in it. And it continues to implement many BSD APIs.

https://en.wikipedia.org/wiki/XNU
I wish there was some attention paid to upload speeds too. A 100Mbps connection often only has 1-5Mbps upload which seriously handicaps it for work and hobbyists.
Its incredible how much faster you can make an app feel by just making the UI respond faster and filling in the data later. As long as something happens instantly its satisfying.
>Do they have well-defined meaning?

Emotions don't have either. That's why emojis show them well. Plus people have learned for millenia to read other people, and face emojis are basically glorified magnified face expressions...
I can choose from Cox and CenturyLink in my area, both have a 1TB cap here.
Yes I do suppose that's true, but I don't think that makes it any less proprietary in nature. The same could be said of many mail providers such as Gmail, Outlook.com, etc. They have their own way of doing it that, externally, looks like mail. Internally it's something altogether different.

This is proven by sending an email from one Gmail account to another. It is all but instant. I swear once the email arrived before the Enter key had debounced! SMTP can't move things quite that fast.
This was the rage among event tickets about 10 years ago.

Of course the simple fix is to just sell items at the market price.

For tickets, the reason was that they were often sold at under-market price, as the comedian/musician/whatever wanted them affordable.

Why are shoes being sold low, I cannot figure out (I expected electronics to be the most sold).
While this may be the case, the Indian government was happy to turn a blind eye to the situation in Xinjiang till recently, when relations with China were good. Now that relations have soured, India is keen to highlight every stain on China's record.
No, that’s just cable companies allocating significantly more to download spectrum than upload. There isn’t anything fundamental in docsis preventing you from giving more spectrum to upload to have way less contention on the upload slots.
I don't understand. Don't those two things seem antithetical? Like why would you make your app inefficient at the same time you optimize it for the CPU?
Stonks only go up what more do you need to know?
It depends what you're looking for.

Best in class engineering and internet scale problems? Nope, you aren't going to find that at any hedge fund. They are much more like small start up cultures. Speed and results are favored over a mature engineering culture and maintainable code.

Want to have the potential to make a large direct impact and make a crap load of money? Well then, a hedge fund may be a good fit.
What is your ideal solution in these cases? In my experience, large enterprise customers (among others) tend to prefer managed versions of software where available. Cloud agnostic/interop versions would certainly seem like a good idea but I wonder what effect that would have on pricing and growth of the product.
I am afraid that is a shared concern for what Tapioca is doing as well. There are ways of mitigating that concern, by, for example, lifting all static methods on a model to be methods on the collection proxy in RBI files. This is certainly doable, and we are less interested in the correct signatures for such methods than having the method definitions in place, in the first place. On the other hand, we also have some Sorbet feature ideas that we want to experiment with where we might be able to annotate that a certain type delegates all missing methods to another type, for example.

This is indeed a problem in our codebase as well, and so far our team has been suggesting that people add shim (i.e. manual) RBI definitions for the methods that they find are missing from the types they've expected them on. This is a good stop-gap measure to solve a problem that is not very common with an easy solution to implement.
Vim Sessions
Its very possible I'm wrong. I just know that its a favorite based on the ease of use "pre paid credit cards" and the wide phone number exchange twilio provides so that they can keep swapping out with new number. Granted it could be something similar to twilio, I only pick them out since they are the top service currently and the probability they are using their services are high.
Hi Thomas,

Founder here.

Thanks for your questions:

- The use case of this is a portable multi monitor desktop with desktop class performance.

- I designed this to specifically facilitate my use case (DevOps, SecOps, SIEM, SOC/NOC stuff). I got frustrated and fedup waiting on the G Screen Spacebook and Project Valerie so one day I decided to just get on with making it myself. I am expected to respond to alerts for the many customer systems I manage so I usually have monitoring panels from Cisco, PRTG, Rapid7, Okta, Solarwinds, Vectra AI, open at the same time all day. Suffice to say this gets really stupid on a laptop with one screen especially when you sometimes have to spend whole days at customer sites or in the data center.

- Due to immense interest from people in the finance and content creation industries I decided to build these to specification.

- One crucial objective was that all the screens should slide out of the main chassis as this facilitates easy setup and folding down when leaving a customer site.

- The screen in the keyboard allows me test touch screen apps I'm writing for linux for another project that will be revealed shortly. The palmrest screen was originally designed to also support a WACOM pen but I'm still working on that.

- The tiny screen on the bezel is not connected to the GPU. It is connected to an Arduino micro controller and provides additional stats on battery life and system resource usage.

- YES to my surprise there are many digital nomad types, film studios, CEOs and other execs who are very interested in our prototypes.

- The battery in the Aurora 7 can be considered a mobile UPS however we are still working on that aspect. One of the big problems we have is Airplane regulations regarding the max Watt Hours for Lithium batteries...

There have been a few prototypes before this one and our latest that will be revealed shortly features various improvements.
I believe what you are referring to is the fix. Foreign exchange markets, that I am aware of, do not have closing auctions.

I have heard of some quants trading foreign exchange markets, agreeing to trade at the fix with their counter-party, and not realising that traders often manipulate the fix resulting in the quant's strategy appearing not to work. It is almost comical (I worked in finance but not in FX, everyone knew this was going on for decades before the SEC starting fining people) that someone who managed money was making this error.

You are 100% correct about all the other stuff. Lots of issues with "production"...that is why financial firms employ traders/risk people/etc. Most people who trade themselves tend to go for lower-frequency strategies that they can implement personally. I actually don't think there are huge barriers, smaller investors have a huge advantage (when you trade at scale, the market moves against you) but you have to work with what you have and realise that you will get crushed if you try to replicate what someone with more money is doing.

Also, data. Data is expensive, and a huge fixed cost.
From your link:

> There is evidence for global warming, though there's considerable reason to believe this is simply part of a natural cycle. There is some evidence that humans may contribute at least a bit to the change (though many sources suggest that human pollution is insignificant compared with forest fires, volcanos, etc.).

This is underhanded, weasel-word denialism. "Many sources suggest" my ass... Let's not give any credibility to this kind of bullshit.
I did all the design, my friend helped me out and machined it with his CNC.

This version has the apple magic keyboard and trackpad built in. Easily adaptable to any set up.
I've implemented quite a few lying progress bars.

It's impossible to estimate total completion percentage when one part of the operation is CPU-bound, and another part is disk-bound.

(I haven't had to deal with network-bound operations, but I feel for those who do.)

Truth is probably possible, but more work than it's worth, when one part of the operation is O(n) and another part is O(m^2).

If the feature is a week late, it doesn't crash, the answers are right, and the operation completes in a reasonable amount of time, I'm moving on with my life.
The problem with progress bars is that they're ambiguous on many levels.

What does the progress mean? Is it the fraction of work done or an indication of time left?

Progress bars don't necessarily lie - they simply omit useful information. Estimating progress is hard if there's variables involved that are outside the application's control, e.g. network speed or task switches initiated by the OS.

Task-based progress bars suffer from being "jumpy" and terribly inconsistent, because some tasks take longer than others and the progress indication doesn't allow to estimate the remaining the time.

Time-based progress bars are bad, because they are dynamic by nature of factors mentioned earlier, so ETA might suddenly jump from 1:23 min to 58:07 min or just as bad from 15 minutes to 3 seconds.

This is also the reason why "this is how long it took for other users" is not a great solution either: if your particular circumstances (network speed, server load, ...) are vastly different at the time, this would solve nothing and result in the same complaints.

Progress bars are just an estimation and a mixture of tasks left, ETA and a generic activity indicator ("the app didn't crash and still makes progress") might be more informative.

EDIT: for short tasks (e.g. 20 seconds or less), a simple progression of messages like "working on it", "just a moment", "almost there", "finished" might be the best option.
Researchers Prove Water Has Multiple Liquid States
The lying and repeating your initial, seemingly innocuous but ultimately disingenuous request, in response to refutations of FUD is popular in political conversations, too. Usually by the "whataboutism" types. Not to mention the "I'm a victim because people are calmly correcting by FUD" routine.

But of course, this is a person, in good faith, trying to learn about Rust: https://news.ycombinator.com/item?id=24537534 :eyeroll: How dare he be downvoted!
This is a 3 hour interview with Blaine Garst by the Computer History Museum. Blaine is one of the people quoted in the main link. I listened to it the last time Blaine was mentioned here and it is pretty interesting.

https://www.youtube.com/watch?v=qtEIq7fe_KQ
Save the trees! Version without printing please. Cool idea
Sometimes the Handbook is dangerously outdated with bad info too. It can be hit or miss. Manual pages are often updated, but do check the modification date for a clue — last updated in 1996? Maybe double check other sources.

(For context: I'm a FreeBSD developer.)
Check, check, and check. Add to that no version control, no tests, no development environment, a custom ajax frontend framework, and the fact that it was mission critical. About the only thing it had going for it was daily database backups (which came in handy).

I did my best to clean up the code so it was at least somewhat maintainable, but there were sections (the most important ones, of course) that I just wouldn't touch because it was impossible to tell what they did -- oh yeah, I forgot to mention the global variables, didn't I?

So happy that app is dead and buried.
Yep - set up a scholar/artist/author-in-residence program.
A geometric mean might make more sense in this situation.
Thank you for the info, I will use this to confirm my findings.
I just got one. I’m blown away by the speed as well. Chrome runs insanely fast! Alas, it’s not developer ready yet. Brew is a mess. Docker doesn’t work. PyCharm is WIP although can use x86 version. I was skeptical of the hype but this little laptop has made me realize how slow everything else is.

Unfortunately, while the hardware has accelerated far beyond expectations, the software - specifically MacOS BigSur is a major step backward. So many fucking animations. Everything feels fluid like operating in molasses. The UI changes seem to be shoe horned into a desktop that doesn’t need giant white space for fat fingers. Menu bars are twice as tall taking up precious space. Top bar was already crammed with a lot of icons. Now, they’ve made them sparsely spaced by adding padding between the icons. Everything is baby-like with rounded corners and without borders. Segmentation UI elements are no more. I want to ask Apple’s UI team: WHY!? What is currently wrong with macOS Catalina UI? Until you can satisfactorily answer that, there shouldn’t be any change. Stop changing the UI like you’re working at Hermès. It’s not fashion. If the reason is to unify everything, all screen sizes, then you’re sacrificing all three. Perhaps making it easy to develop apps for all 3 platforms is a plus, but as a user, this all feels like a regression. I’ve lost hope in modern UI engineering. It’s not engineering anymore.

I want macOS that has a UI of Windows 95. That would be totally insane on Apple Silicon.
Posts in our company's page or on our own walls gave us the best clickthrough, and we did a lot of grinding to build up our audience there. Facebook ads did well also, we would pay about 30c/click and something like 10% of those turned into sales. Instagram actually didn't do well for us - we got a higher sales capture rate but fewer clicks. We just didn't give the insta account the attention that it deserved (before I left the business, anyway).
I think they're saying that devs won't spend as much time optimizing, since they know that the CPU is faster.
Really interesting article. For me this was an important takeaway:

>Although it should fail gracefully, it does not need to be optimised for failure.
Looks like your looking for our A5 15 or A5 13. send us a message on our website and we'll let you know when they are available.
*Future versions will be more adaptable.

This version is highly specialized.
It's a good question. The basic answer is not everyone has capital and risk, but they may have the time and intellect.
Have you tried Clockwise? We have it installed in our G Suite account; it performs decently well.
Waterson talked about how he was unhappy with the constraints of the newspapers; it's possible that he would have found webcomics, with essentially no restrictions, interesting enough to keep going?
Proposal 1 is the thing I want.

Please just list out a total number of steps and log when each of those steps is completed (with a short message describing what the step is so that we don't end up back on square one with fractional progress bars). If possible make the steps granular enough so that a step can be completed in under a second (so this may be hundreds or thousands of steps depending on the task length). In the case of say "bytes currently downloaded" this becomes essentially a continuous stream of steps (which is a good thing!).

First and foremost what this communicates to users is that the system is doing something useful. This is what frustrates me about spinners. They are functionally indistinguishable from a frozen system, to the point now that users synonymously identify an indefinitely spinning spinner with a frozen system. And progress bars that asymptotically approach completion even when the program is frozen have trained users to be similarly suspicious of progress bars.

Secondarily it offers the same vague assurances as a progress bar about approximately how much time is left. If you see 250 GB out of 500 GB downloaded you'll assume that you're half-way there, similarly if you see 250 steps out of 500 completed. Especially in the case of the latter, there's no guarantee that the total elapsed time is already 50% over, but that's true of progress bars as well.

Finally, if something goes wrong, there's usually a useful error message that can be shown since there's the context of all the previous steps that led up to this error.
I worked for a small time WISP for a while, partially servicing a town of ~10,000 (but mostly not because of interference) and large swathes of the rural surrounding areas. He was heavily harrassed by police for various nitpick infractions regarding the equipment on his truck and where things were placed and whatnot, things that the local power company and AT&T blatantly violated with regularity without repercussion. He was also met with resistance from the city board/mayor, who were trying to require some regulatory fees that they (come to find out) didn't even have on the books. I think the only reason his business survived this stupid pushback is because he is former law enforcement.
Ouch, too bad. I assume a browser connoisseur like you knows how to whip up a userstyle though? :)
From Joe Duffy's series of blog posts on Midori[1]:

> Error codes fail the test of “zero overhead for common cases; pay for play for uncommon cases”:

> There is calling convention impact. You now have two values to return (for non-void returning functions): the actual return value and the possible error. This burns more registers and/or stack space, making calls less efficient. Inlining can of course help to recover this for the subset of calls that can be inlined.

> There are branches injected into callsites anywhere a callee can fail. I call costs like this “peanut butter,” because the checks are smeared across the code, making it difficult to measure the impact directly. In Midori we were able to experiment and measure, and confirm that yes, indeed, the cost here is nontrivial. There is also a secondary effect which is, because functions contain more branches, there is more risk of confusing the optimizer.

> This might be surprising to some people, since undoubtedly everyone has heard that “exceptions are slow.” It turns out that they don’t have to be. And, when done right, they get error handling code and data off hot paths which increases I-cache and TLB performance, compared to the overheads above, which obviously decreases them.

[1] http://joeduffyblog.com/2016/02/07/the-error-model/
At the risk of being that (Linux) guy --

What is gained here if we're just still applying faster cycles to Apple-esque wasteful (and perhaps harmful, as we're apparently learning re: their telemetry) software?

If people really dig their Apple stuff, great. But I think its worth thinking about the likelihood that a "slower" computer running Linux could probably serve the actual user better in terms of "getting stuff done." Moreover, I think we're pretty close to "beauty" parity here as well. Apple's advantage now is probably mostly the networked devices, i.e. unity between phone and pc messages, etc.
Identity and Access Management with Google Cloud
Tandy did this many years ago, with better ergonomics.

[edit] It was really a Kyocera machine branded by Tandy (and others) I knew a Bell Labs department head that owned one back in the late 1980s and used it while traveling. The ergonomics on them was really quite good.
This is the primary reason I don't use Netflix.

I like endings, and I think they're important. When I get to the end of a Stranger Things episode (which I buy on BluRay), I want the scene to fade out, and I want the credits to roll, and then I want the universe to leave me in peace for a moment so I can contemplate what just happened.

Netflix absolutely will not allow this experience. You can turn off auto-playing the next episode, but Netflix will take over your screen with a giant promo instead. There's no way to let a video just end.
I hope I am wrong too. It is bleak! It might be the six months of grey rain that I'm looking at out the window, it might be a year of heavy burden bearing down on me, or it might just be a heroic dose of Depressive Realism.