skysight-inc/HackerNews huggingface dataset:
I would be wary of new teammates whose motto is "think different" when it comes to operating services at $B scale, because if they break something, someone else on the team will have to work all day and night to get things fixed and it won't be them.

That does probably depend on whether you're doing greenfield work or not, but even then these costs are there but just not immediately visible.
This is nice! I just managed to find an article, I couldn’t find with Google.

Thus, I was able to solve the PDP-1 "Amherst Mystery" [1]: https://www.masswerk.at/nowgobang/2021/pdp1-spotting#update

[1] https://news.ycombinator.com/item?id=26313124
I don't think that you understand Bitcoin... Your first point is possibly the only valid point but it can be fixed if 51% of miners agree.
Maybe it’s just the hyper and related crates universe, but my perception (see my sibling comment) is that more and more of the ecosystem will be “async only”.

Like you, I think that’s sort of fine, because you can always roll your own. But it’s also kind of sad: one of the best things about the Rust ecosystem is that you can so effortlessly use a small crate in a way you really can’t in C++ (historically, maybe modules will finally improve this).
Speedrunning Windows 95 (2019)
ML to convert dark images as they were taken in light
This article puts to words my exact experience with Scrum. It has done irreversible damage to my mental health, which fortunately I learned how to manage with the help of a professional. Fortunately I get to work on a relatively more relaxed environment now, because I couldn't stand working in an environment like that another day, let alone the rest of my life.
I'm over 40 and stigma for not spending money was also a thing when I was a kid. I still remember discussions about who had the trendiest school backpack. I'm not saying that it's a good thing, just noticing that it would still be there even if you took a "no videogames" stance.
I like to joke that the best way to encounter the ugliest parts of Rust is to implement an HTTP router. Hours and days of boxing and pinning, Futures transformations, no async fn in traits, closures not being real first class citizens, T: Send + Sync + 'static, etc.

I call this The Dispatch Tax. Because any time you want more flexibility than the preferred static dispatch via generics can give you - oh, so you just want to store all these async fn(HttpRequest) -> Result<HttpResponse>, right? - you immediately start feeling the inconvenience and bulkiness of dynamic dispatch. It's like Rust is punishing you for using it. And with async/await taking this to a new level altogether, because you are immediately forced to understand how async funcs are transformed into ones that return Futures, how Futures are transformed into anon state machine structs; how closures are also transformed to anon structs. It's like there's no type system anymore, only structs.

That's one of the reasons, I think, why Go has won the Control Plane. Sure, projects like K8s, Docker, the whole HashiCorp suite are old news. But it's interesting and telling that even solid Rust shops like PingCAP are using Go for their control plane. It seems to me that there's some fundamental connection between flexibility of convenient dynamic dispatch and control plane tasks. And of course having the default runtime and building blocks like net and http in the standard library is a huge win.

That said, after almost three months of daily Rust it does get better. To the point when you can actually feel that some intuition and genuine understanding is there, and you can finally work on your problems instead of fighting with the language. I just wish that the initial learning curve wasn't so high.
I'm okay with my employer tracking me if I'm on their premises using their property that they've given me. I'm not okay with them knowing anything I do or where I am outside of work, but if I'm at work then I'd be confused if I wasn't being tracked in some way.

Not at all in the paranoid "are you slacking off?!" sense, but just security information like knowing when I've been in a server room, or knowing if my work computer sent traffic to a known botnet C&C. If there's a security or theft incident and they don't know who's been in their building or what their computers are doing, it's pretty much impossible to investigate anything.

I understand that in places like Europe there's a very different culture and workers have a lot of protections from things employers may want to do, but not everyone around the world feels that way. Basic record-keeping of when badge-restricted doors and computers are authenticated to doesn't feel invasive to me in the slightest, even if others may strongly feel it is invasive.

There are many things I would find egregiously invasive, such as a manager inspecting all the websites someone visits to assess how productive they are, or timing people's bathroom breaks, but I just avoid such companies.
> if we wanted to we could have probably owned half the internet in like a week.

Oh, skids. Pop a single shell in a disposable environment in some corporate hellscape cloud infra and they think they can pwn the interwebs. I'm sure you could root some shitty Fargate container of some shitty web app in my company, too, but you literally can't get to any other network from it.

They'll be dining out on this for years on irc. (do the kids still irc? is twitter the new irc?)

Blah blah Twitter makes for crap HN articles etc
I was unaware of hydrogen-fueled turbines or energy storage via electrolysis. I have some more research to do. Thank you.
Rust Security Advisory Database
>>No, because we can still do testing and tracing. A virus infecting a few hundred people that we can detect fast is a lot easier to contain than a virus infecting millions or one that we aren't aware of.

If we have effective detection methods, we don't need to lockdown. We just trace and isolate any cases that pop up.

>Asian nations (China, Japan, SK) are doing similar to New Zealand and they aren't nearly as isolated.

China had far more cases than New Zealand, which goes to my point; New Zealand's position as an isolated island made it easier to contain the virus.

AFAIK, Japan and Taiwan never did NZ-style lockdowns. Taiwan had very few deaths relying mostly on contact tracing.

>>Understand that, had we done this 2-month full lockdown, we would not even be locked down now. Young people wouldn't be nearly as affected as they are now.

NZ has been isolated from the world for a whole year and just recently locked down Auckland again.
Git-for-Windows may turn symlink support on by default under some specific circumstances. As the repo's wiki [1] says:

Short version: there is no exact equivalent for POSIX symlinks on Windows, and the closest thing is unavailable for non-admins by default unless Developer Mode is enabled and a relatively recent Windows 10 version is used. Therefore, symlink emulation support is only turned on by default when that scenario is detected.

[1]: https://github.com/git-for-windows/git/wiki/Symbolic-Links
Thanks! I didn't know that.

Getting endorsement seems a relatively low bar, but it's still a bar.
Its a business issue.
> My experience is to manage people effectively, and apply just enough process for each person and job.

Sounds like you have a decent lightweight process-making-and-revising process. Most organizations don't. Instead, most organizations create processes mostly ad-hoc in reaction to some trauma, and then never remove them. It accumulates, like scar tissue that only ever gets thicker unless it is ripped away, which just causes different scars.
It's not really a problem worth caring about. Just if you wanted to gripe about the complexity of async Rust it's the most obvious to me. "But pretty much no one even lets you do that" is a great counter argument.

But, it is kind of an anti feature. It's incredible that Rust allows custom async executors and the surface area for them is tiny! That said, it's kind of black magic, even for Rust. I'm willing to bet there's fewer than 20 people in the world that could make a production executor today (not that it's going to stay that way - don't get me wrong).

If there's one reason to write an async application today in Rust it's because you can write a custom executor and give it a ridiculous amount of information about how the application is running by communicating with it, while wrapping both callback and polling backed APIs from system libraries in C.

But that's really hard to do if writing an executor is harder than just writing callbacks or polling code manually.
> If people want to "invest," they'll figure out more pro-social ways to do it than the stock market

Here are 99% of the things you can invest in as a person without a very large amount of capital:

- real estate (your own home or rental units)

- bonds (another security - same issue as equities in your analysis)

- private business

Are any of those inherently more pro-social than equities?

The stock market encompasses both WSB speculators and “buy and hold forever” investors.
> and taxed like a vehicle.

and, critically, depreciates like one. Which is kind of the opposite of what you want in a house.
Right. People need to check up on the latest Nuclear advancements. We're getting quite good at refining waste products down to safe enough levels of radioactivity, and then we can even further utilize the remaining waste in other applications.

It's not like we've hit a dead end with nuclear research, people have just seen too much Chernobyl stuff and cast a large net on the whole science.
Yes, that's a better example!

(I thought your initial point was good, just that the argument for it wasn't as strong as it could be.)
Assuming base 32 and we have 8char initially. That gives us around 32^8 = 1.099e12 of serial numbers. Might be enough for a while.
> Whatever Tokyo is doing to keep COVID under control with such a crazy high population density, it looks like we've got an entire state over here in the U.S. that could still learn some of the basics.

I lived in Japan, have many friends there whom I keep in touch with, and watch the local news regularly. The restrictions in the major cities have been substantially fewer than we've had here in the US. There have been two voluntary states of emergency, where businesses were encouraged (but not required) to reduce hours. Nearly all have remained open. This winter, the government discussed enacting emergency laws to allow fining businesses that don't comply (not sure if that went anywhere...), but mostly they tried to incentivize businesses by providing subsidies to places that reduced hours.

To be sure, fewer people are going out and using transit, but a large number of my friends are still going to work in the office, going out to eat, etc. Until late this past fall, the government was actually encouraging domestic travel, via a national voucher system. This was only suspended once cases were clearly spiking around the nation. Compared to (e.g.) New York, Tokyo looks basically normal, even today. The most visible difference is the lack of tourists.

AFAICT, the only broad conclusion one can draw from Japan is that most of the things that are held sacred here in the US don't seem to matter very much at all in their context.
You can see the resolution of the cameras in some of the account's other tweets. It's not high enough to see information on the screen. Watching keyboard inputs might be possible, but even then I doubt the framerate is high enough to get all the keys.

More importantly: at most companies, accessing sensitive systems requires more than just a username and password. Pretty much every place requires TOTP or HOTP, often via a hardware token. Many firms also restrict access to specific machines.
After re-reading your questions 1 and 2 I think interpolation basically answers them both. You want smooth and stable values for your counters at any time t, and the way to get that is define an interpolation function from (timeseries, absolute time) to value, or recreate a sufficient range of higher resolution timeseries values that can be graphed directly.

Linear interpolation will give you a line chart. Curve-fitting methods will smooth the charts out, but since you are working with counters you can put some constraints on the interpolation.

Since each bucket represents a change over a period of time it represents an area under the curve for the same interval which should match any graphic representation. https://stackoverflow.com/questions/34983360/create-a-piecew... is basically the question of how to interpolate between data points while preserving that area, which might be overkill for your application but is possible.
Ah, I wish that were true. There are some ISO standards that are not publicly available but still have value.

They'd have a lot more value if they were publicly available.
For those not up-to-date, the article covers "cultural Marxism" and "intersectionalism" in schools today. It's not exaggerating about anything.

LA is one of the worst areas because getting cancelled means certain loss of your job and any friends, both inside and outside your industry.
I am guessing you are a point D/D' in the diagram [1]
Although the diagram is for the Rust overall, I think something similar is true for async Rust.

All I would say is hang in there. It gets better (from my experience).

Rust is not something you can code along as you think. There is a bit a of upfront thinking what the data-structures & data-flow look like.

At present, I can know in advance without writing code whether implementation I am thinking in Rust will work or not (work => satisfy Rust compiler)

[1] https://imgur.com/kNkV7jm
Toxic Gatekeeping in the Technology Industry
I do wish they would let organizations apply earlier in the year (or even better the year before) so the organizers can know whether or not the organization will be accepted. In fact, many students start talking to us even the previous fall in preparation for an application to gsoc. But certainly, immediately after org announcements things really start, so everything, including project descriptions, mentors, etc. need to be set up. Handling the inquiries, getting the mentors set up, etc. is a nontrivial amount of work. We (Julia) missed out in 2015 and it was quite a scramble. We ended getting sponsorship to run a Summer of Code outside the Google umbrella to avoid disappointing the students, but more of a heads up would have been useful.
Economics of Language
Google fails to index so many good sources nowadays... I think that it has been gotten worst over the last 10 years.
1000 instances with 250 concurrent connections each is 250k, but I fear I may be missing your point
Tangential question, but I remember some HN link about a SaaS business that was doing some OCR on paper bills to make sense of it automatically, anybody remember the name of that service? I have like a thousands of these things to scan and extract tabular data from.
https://shakebuild.com/ agrees with you:

> Large build systems written using Shake tend to be significantly simpler, while also running faster. If your project can use a canned build system (e.g. Visual Studio, cabal) do that; if your project is very simple use a Makefile; otherwise use Shake.

For what it's worth, if I remember right, Shake has some support for interpreting Makefiles, too.

> [...] the way more complicated syntax of Shake [...]

For context, Shake uses Haskell syntax, because your 'Shakefile' is just a normal Haskell program that happens to use Shake as a library and then compiles to a bespoke build system.

Also:

> The original motivation behind the creation of Shake was to allow rules to discover additional dependencies after running previous rules, allowing the build system to generate files and then examine them to determine their dependencies – something that cannot be expressed directly in most build systems. However, now Shake is a suitable build tool even if you do not require that feature.
Well, if you are anyone that appreciates a grey and hopeless bureaucratic tarpit (with extra vipers), California is an option. At least it's expensive.
Just winging it.. about 90.
Yes. You can take a subset of Perl's syntax.
Yes, there was: the function was calling the passed in closure from a different thread.

It is just one thread that’s actually appending to the Vec, but it’s still a multi-threaded example.
Very interesting.

I'm also in Australia and have found your perspective to be identical to mine.

Unrelated undergrad + IT/CS Masters usually equals "I want money" or "X was terrible so I'm falling back to something safe". Obviously, that's not always the case, but it has been in many interviews (and a few hires).
Try for Amazon, good pay, not as hard as algorithms questions
Why? You may lose friends. I’d recommend getting equity and building
Ask HN: Those who quit their jobs to travel the world, how did it go?
In light of the pandemic and countries slowly opening up again, I thought I'd ask this question that appeared back in 2015 [0].

[0] https://news.ycombinator.com/item?id=9439286
Ah yes, the serious investigation surrounding which type of mushroom I am, or a list of ten reasons why Ryan Reynolds is just so darn cute.
I'm also curious about this. Boats wrote some about rust async and io-uring a while ago that's interesting[1], but also points out a very clear path forward that's not actually outside the framework of rust's Future or async implementation: using interfaces that treat the kernel as the owner of the buffers being read into/out of, and that seems in line with my expectations of what should work for this.

But I haven't touched IOCP in nearly 20 years and haven't gotten into io-uring yet, so maybe I'm missing something.

Really the biggest problem might be that switching out backends is currently very difficult in rust, even the 0.x to 1.x jump of tokio is painful. Switching from Async[Reader|Writer] to AsyncBuf[Reader|Writer] might be even harder.

[1] https://boats.gitlab.io/blog/post/io-uring/
Without introducing Rust 2? Highly unlikely.

I should have worded my message more carefully. Completion-based model is not a silver bullet which would magically solve all problems (though I think it would help a bit with the async Drop problem). The problem is that Rust async was rushed without careful deliberation, which causes a number of problems without a clear solution in sight.
>The cameras were located in offices that have been officially closed for nearly a year.

This explanation begs the obvious question, why were they still connected to Cloudflare's internal network for nearly a year? Does Cloudflare just keep paying rent for 'officially closed' offices? Obviously this ArsonCats group is exaggerating the extent of the hack but this official explanation from Cloudflare doesn't exactly pass the sniff test either.
May I ask why?

Case sensitivity is one of the things that really bothers me on Linux, it causes me to make mistakes for no reason. If I ever really switched to Linux full-time, I’d probably want to change that.
There was Shoeboxed over a decade ago, looks like it’s still around. I think there have been others in the meantime.
> If anything, async-await feels like an extremely non-functional thing to begin with

Futures/promises (they mean different things in different languages), like many other things, form monads. In fact async-await is a specialization of various monad syntactic sugars that try to eliminate long callback chains that commonly affect many different sorts of monads.

Hence things like Haskell's do-notation are direct precursors to async-await (some libraries such as Scala's monadless https://github.com/monadless/monadless make it even more explicit, there lift and unlift are exactly generalized versions of async and await).

To see how async-await might be generalized, one could turn to various other specializations of the same syntax, e.g. an async that denotes a random variable and an await that draws once from the random variable.

To see the correspondence with a flatMap method (which is the main component of a monad), it's enough to look at the equivalent callback-heavy code and see that it looks something like

Future(5)
.flatMap(x ->
doSomethingFutureyWithX(x)
.flatMap(lookItsAnotherCallback)
)
How do you differentiate background and worker processes? I’m currently running VMs for background processes processing pub sub topics. Is that not something that could go on cloud run?
See also https://fatcat.wiki (which is, I think, incorporated into Internet Archive Scholar.)
> Honestly, I don't get why people are complaining. An ISO standard costs fraction of what the developer's time reading said standard costs.

That'd be true if there was only one. But real-world systems often involve a vast number of standards (de facto and de jure).

> I would much rather like to hear if the value that ISO produces is proportional to what they charge.

ISO does not pay the developers of the standards it controls. It prints paper (which few want) or sends PDFs (which cost nearly nothing to store & send). It also manages votes, which today can be done cheaply. Many of ISO's current required costs are only required because they have to implement a paywall.

Don't get me wrong, I think standards have an important place in the world today. And I'd like to see ISO continue. But its antiquated approach involving charging for standards is impeding, not aiding, the use the standards.
Interesting!

For comparison, Haskell went with the library approach but has the syntactic sugar of the equivalent of `and_then` built into the language. (I am talking about Monads and do-notation.)

It's a bit like iterating in Python: for-loops are a convenient syntactic sugar to something that can be provided by a library.
Blackjack is an oddball game which involves skill and chance. But chance dominates such that it's still likely considered a game of chance.

Skill in blackjack is to play a perfect game. That is, you don't make errors. Counting cards may be considered part of playing a perfect game.

The rules of Blackjack set the house edge. In some cases, a perfect game (including counting cards) could elevate the player such that the player has a small edge. In that case, the player may come out ahead and the casino may eventually stop working with that player. It's rare that a casino hands this to the player as an option though AFAIK. I have heard of casinos negotiating rules with "whales."

Usually, a perfect game won't elevate a player above the line of house edge. Among the rules which narrow the edge is shuffling with multiple decks of cards. If the casino is using multiple decks, then card counting is useless.
From a different article, seems like the staff

> Inside Arizona’s Graham County detention facility, which has 17 cameras, videos are given titles by the center’s staff and saved to a Verkada account.

https://www.bloomberg.com/news/articles/2021-03-09/hackers-e...
Lifecycle of a Rust Developer (2018)
Do you guarantee these savings claims? Will you cover the difference if someone doesn't save at least 50%?
He says the problem is the proliferation of async libraries, which forces their use and pollute everything they touch in association with the closure problem. It's the combination of both.