skysight-inc/HackerNews huggingface dataset:
Things that are easier with Rust's async:

• Timeouts and cancellation. Rust's async code can be aborted from the outside (with correct cancellation and cleanup of everything in progress). OTOH if you run imperative blocking code, you need every blocking function to cooperate.

• Full utilization of CPU and I/O in workloads that mix both. Async executor balances threadpools/polling queues for these automatically. OTOH if you just use regular blocking calls with no state machines/continuations, it will be hard to separate these two. A single mixed-use threadpool will oscillate between I/O-bound threads and underutilizing CPU, and CPU-bound threads and idling I/O.
The good recruiter matches the right candidate to the right company. The dysfunction is a property of the system and is borne by everyone.
A lot of people don't want a family and are happy in their twenties without a partner
We made an app that shows how much money you're wasting on meetings
Hi folks! I'm Flavio, part of the Retimer team. I'm really glad to present you Retimer. An app destined for project managers, freelancers, and coworkers that want to keep track of their meetings with a data-driven approach. You will be able to track your meeting times and other activities, add members and roles, set monthly spending limits, and more!

We would love to have your feedback and start a conversation!
Real capitalism has never been tried!
This was a great article, very easy to understand without leaving out the fundamental pieces (the saga that is async implementation difficulty). I think I can even boil this situation down to the simple thought that design & implementation of async in Rust has driven it to it's first "monad" moment. The question is now largely whether there exists a way that is better than monads to handle this problem.

It's in this (HN) comment thread and a bunch of informed comments on the original article:

https://github.com/eeeeeta/blog-comments/issues/10#issuecomm...

https://github.com/eeeeeta/blog-comments/issues/10#issuecomm...

https://github.com/eeeeeta/blog-comments/issues/10#issuecomm...

The comments are correct in my view -- Rust can't/shouldn't do what Haskell did, which was to create use a general purpose abstraction that is essentially able to carry "the world" (as state) along with easy-to-trade chained functions on that state (whenever it gets realized). Haskell might have solved the problem, but it has paid a large price in language difficulty (perceived or actual) because of it, not mentioning the structural limitations of what Rust can do and it's constraints. The trade-off just isn't worth it for the kind of language Rust aims to be.

Realistically, I think this issue is big but not enough to write off rust for me personally (as the author seems to have) -- I'd just do the move + Arc<T> shenanigans because if you've been building java applications with IoC and/or other patterns that generally require global-ish singletons (given example was a DB being used by a server), this isn't the worst complexity trade-off you've had to make, though the Rust compiler is a lot more ambitious, and Rust has a cleaner, better, more concise type system as far as I'm concerned.

I think another thing I've gained from this article is another nice little case where Haskell (if you've taken the time to grok it sufficiently, which can be a long time) offers a bit of a nicer general solution than Rust, assuming you were in a world where those two were actually even substitutes. In the much more likely world where you might compare Rust and Go2, this might be a win for Go2, but the rest of the language features would put rust on top for me.
I can pay external farms to spawn new favorable reviews though, and Google won't do shit.
I suppose my family was equipped ahead of it's time in 1990. By 2000 I think we had perhaps fallen behind :)
what is the advantage of 11.5 over 12?
It seems renewable strategies are still experimental and will rely on some sort of base load system for the foreseeable future. The base load systems being either gas plants or nuclear plants. We can place our bets on gas hoping we can one day turn those plants off using some sophisticated storage solution. The safer bet - however - is perhaps on small flexible nuclear reactors. Once mass produced (~ 10 years) I expect those will be taking over the energy market because of economic factors. Disrupting many complex solutions that are currently being invested in.
Article: many of the millionaires invested consistently in their 20s and 30s.

Based on r/wallstreetbets I'd say that many broke gambling addicts do the same.
ASP and ColdFusion, too. We had clients switch to PHP 3 because it was so much faster and less buggy (!) but that was definitely seen as a bit of a gamble.
N of 1 here, but, you may be right. My activity on this board is inversely proportional to my success and virility on the outernet.
This. Failing to understand public institutions as public hands is one of the reasons people misjudge politics so badly.
Aqueduct (web framework written in Dart) needs your help!!
Yeah... surely industrialised animal farming is to blame?
Fake heiress Anna Sorokin: 'Crime pays, in a way'
You could still send your resume to the company but not lie about having MOVA experience. They are called job "requirements" but companies often hire someone that is the best fit even if they miss out on one of the requirements. Of course, some companies also have a hard filter against requirements that you wouldn't get past, but you won't know unless you send your resume.
I think it comes from experiences of coming in to codebases and seeing that people are using the ORM for everything, even when it's obviously suboptimal and raw SQL would be better.

Compromise, best tool for the job, nuance, etc - all tend to get tossed out when people make tech decisions. Someone using an ORM may not even be aware that raw SQL is possible.
If you're newer to traveling I think a couple weeks is fine. When you visit enough places you'll figure out where you want to be long term
> In the case of Roubaix 4, the Datacenter is made with a lot of wood:

> Finally, we have other photos of the floor of the OVH "Roubaix 4" tower. It is clearly wood! Hope it's fireproof wood! A wooden datacenter ... is still original, we must admit.

> In France, data centers are mainly regulated by the labor code, by ICPE recommendations (with authorization or declaration) and by insurers.
At the purely regulatory level, the only things that are required are:

> - Mechanical or natural smoke extraction for blind premises or those covering more than 300m2

> - The fire compartmentalization beyond a certain volume / m2

> - Emergency exits accessible with a certain width

> - Ventilation giving a minimum of fresh air per occupant

> - Access to the firefighter from the facade for the premises are the low floor of the last level is more than 8 meters

> - 1 toilet for 10 people (occupying a position considered "fixed")

https://lafibre.info/ovh-datacenter/ovh-et-la-protection-inc...
I don't know any studies, but I always thought overall situational awareness was a bit part of defensive/safe driving. Always being aware of other vehicles around you and other potential hazards. Not getting tunnel vision.

I know I intuitively feel it is anyways.

We need much better driver training.
African payments company Flutterwave raises $170M, now valued at over $1B
> Also, all ORMs let you do raw SQL because there will be times where the ORM abstraction will be too cumbersome.

"Learn how to master {flavor} ORM and when you've spent hours digging through documentation, stack overflow posts, and src code to find it isn't simple to do in {flavor}, use raw SQL."

This argument that "you can always drop into raw SQL" skips the fact that the code will not be merged if it can be done in the ORM because ThisIsTheWay(tm).

I find query builders to be a nice blend between raw SQL and the ability to write programmatic queries. The APIs tend to be relatively consistent between libraries since they map directly to SQL statements.
I also have years of experience in Konami Code.
So what, you've listed like 5 years experience in UUDDLRLRBA?
It's not just 'simple CRUD apps' vs 'advanced apps', I find it's also language/ecosystem specific. I've worked on Java and .NET projects (typed languages) where ORM's are a fact of life, and actually make it a lot easier to navigate & refactor your codebase. I've also worked on Python and Node.js projects, where ORM's often did not significantly improve the developer workflow (navigation, refactoring etc.) because of the lack of strict types in these languages, and ORM's and their usage were therefore a point of daily team discussion.
Water is one aspect, and the other (in Kashmir) is land for their Belt-And-Road project.

https://www.youtube.com/watch?v=d_00Xx9b87A
If the result that experience with L2 seems to improve situational awareness is robust, then that raises the question of why that is so. Has experience taught them that they need to pay attention, in a way that is more effective than merely being told they need to? Are drivers new to L2 overconfident in its abilities, or perhaps merely unsettled by the unfamiliarity of the situation?

Note that the article also mentions that other studies have found increasing complacency with experience.

> Does it make them more likely to note and deal with unexpected risks or not? The article guesses the answer though the actual paper may not have.

Given that noticing a problem is a prerequisite of dealing with it, this is not an unreasonable supposition, though one should also wonder if their reaction times are slower. Note that even if that is so, noticing more things, or noticing them sooner, could more than compensate for this.
0.5cm smaller.
We had the same issue at a customer site. To add since the decibels were outside the rated environment the warranty was void on the harddisks and they had to be replaced even if they were not destroyed.
Use Urbit
I do this in a sort of roundabout way, by actually using a new heading for each paragraph (helps with outlining). You can make this work by adding the :ignore: tag to the headings, which means that the heading titles won't be exported when you export the document, but the text under them will. Basically, you get an invisible outline of your document that you can tag however you like.

It requires some light setup to get working, since it's not part of the base functionality of Org. First, add these lines to your config (more details on StackExchange[1]):

(require 'ox-extra)
(ox-extras-activate '(ignore-headlines))

Now you can add the :ignore: tag, and any other tags you want, to the heading for any paragraph. When you export, you'll just get the paragraphs, not the headings or tags.

[1] https://emacs.stackexchange.com/questions/38184/org-mode-ign...
People also have different priorities. I never wrote an application in C++ and don't care about boring but practical stuff like the file API or syntax.

But I like learning about C++. It has many interesting features and concepts. Understanding those, their design trade-offs, how and why it differs from other languages (e.g. Rust) is fun. So I know more about "advanced" C++ than I know about "basic" C++.
That question remains open.

https://thebulletin.org/2021/02/who-covid-19-didnt-leak-from...
There are so many programming languages out there, as a hiring manager it’s not uncommon for me to see resumes with languages I’ve never heard of and probably don’t care much about. The cheat code just depends on how it has been inserted into the resume.

If I threw out every resume with some weird quirk, spelling or grammar issue, layout problem, etc. I’d probably never hire anyone
Ahh! Got it. That's sad. One would hope that the law could instead shift this burden onto the whoever modifies the software :-/
Keycloak (you won't get fired for picking this) Not if you're just picking it, but possibly if you have to administer it. We're in the process of replacing it, possibly with Hydra.
Of course anyone can look anything up. The point I think the author is making is that the database is better positioned to tell us about potential performance issues. Would be wonderful if we could avoid reading through slow query logs, or paying big money for APM tools, if the db exposed more user friendly information about perf issues or other useful metadata.

The UX of 'damn I have to look that one weird query up again' to look up some metadata is not as good as it could be.
So in guessing ова is pronounced ova?
> ORMs always force their world view onto the database, which is completely backwards from how things should work.

I have different experience. There are situations where you work with database given of course, but in many projects ORM enforces good and unified practices (rows have unique id, constraints and indexes are properly named, relationships are done in always the same way), and generally database is just a servant to developer idea of data model, not a god to worship and bend to.
This isn’t a meaningful comparison unless the pre Chernobyl birth defect rate in Poland and Ukraine was at least as high as the global one. I doubt that, because among other reasons there are high population countries with a long history of close cousin marriages that almost certainly have significantly higher birth defect rates than Eastern Europe pulling the global rate up.
This runs afoul of the article’s warning to “ Never require a cache hit”

It's important never to
require a cache hit - even
as a soft requirement.
Evictions can happen at
inconvenient times - such
as when some other part of
the system is under load -
and there mustn't be any
negative consequences to a
cache miss

If the cache does empty unexpectedly and that is going to cause your infrastructure to die in a cascade, probably some kind of fallback will be needed.
As long as you have outside shareholders you can decide that. If you do you'd be surprised about how they will respond to an attitude like that. After all: you can decide the levels of risk that you personally are comfortable with leading to extinguishing of the business, but a typical shareholder is looking at you to protect their investment and not insuring against a known risk which at some point in time materializes is an excellent way to find yourself in the crosshairs of a minority shareholder lawsuit against a (former) company executive.
Write site-specific extensions to replace sites' JavaScript code
Totally disagree with your software claim.

The manufacturers should simply be held accountable in that they provide a means to have approved replacement hardware providers. Having software modification available could lead to cases where safety is jeopardized; any claim it cannot be is laughable; let alone who is liable if modified software causes the issue. The manufacturer would possibly be stuck proving it.

Plus people vastly underestimate how much replacement components will cost along with which components are reasonably designated as replaceable.

When you get to appliance level items TVs are an interesting case because its highly unlikely panels will be as cheap as new televisions and creating a case where they have to be less than the television will simply pass that cost onto anyone buying that television. The controller cards, power supply, and such, likely will be more readily available but of them the power supply is the only true part which would be more universal across items.

Which brings me to, the best way to have an easier to repair world is to eliminate non standard plugs along with customized power supplies or chargers within the same product type.

edit: another concern with software, the expectation that camera code be open does not protect the manufacturer intellectual property in regards to new and interesting methods to provide better picture quality.
Appreciate the correction, got to it in time!

And as others have noted, this is probably the most enterprise-grade/production-hardened solution out there in the list that I made that represents my current list in the F/OSS space. If I were to think hard about it, there are probably lots of much older options (depends on where you put the scope of AuthN to be, is LDAP a competitor?), but Keycloak is probably the one you're going to find the most resources and scrutiny around.

A large financial institution I worked with two years ago was using Keycloak. I was annoyed with some UI bits and terminology that was very confusing but it was overall a great choice back then IMO, has probably mostly/only gotten better since.
This is a wonderful vignette. Efficient use of dialogue.
I understand it but reject it.

If it's a problem for the platform owners, I'll be even more political. Screw them.
Thank you for the link! But immideately we can see the false equivalence: completion based API does not imply the callback-based approach. The article critigues the latter, but not the former. Earlier in this thread I've described how I see a completion-based model built on top of FSMs generated by compiler from async fns. In other words, the arguments presented in that article do not apply to this discussion.

>The performance issues it presented had nothing to do any sort of impedence mismatch between a completion based future and epoll

Sorry, but what? Even aturon's article states zero-cost as one of the 3 main goals. So performance issues with strong roots in the selected model is a very big problem in my book.

>You do not know what you are talking about.

>You are confused.

Please, tone down your replies.
That is not a correct reading of the situation. async/await was not rushed, and does not have flaws that could have been solved with more time. async/await will continue to improve in a backward compatible way, as it already has since it was released in 2019.
Oh, I mean, I mainly use update-in and assoc-in too. Specter is pretty powerful though. I once wrote CSS-like selectors to work on hiccup using Specter.
My experience in image to text conversion softwares has not given confidence to use in production or as part of reliable workflow. What's unique or different about this tool compared to its predecessors? Does it use any novel algorithms, neural nets or any other techniques?
I didn’t use CF professionally until 2000 and started with fusebox. I think fusebox was a good idea, but still CF sucked to use as a developer (me comparing it to cgi, php, asp, java).

I stopped using CF in 2001, but the fusebox ideas stuck with me as I worked with other web frameworks like struts, spring, other mvc stuff.
Censys: A Great Alternative to Shodan
I saw a demo of Censys this week. I was very impressed with the thoroughness and timeliness of the attack surface discovery features which are combined with an excellent user interface to analyze it. https://censys.io/
What about the classroom has anything to do with reality? If anything, the extent of the failure of any adult organization is perhaps the extent to which it has borrowed ideas from social programming in the classroom.
> Second, what do you tell your friends and family who ask if they should buy bitcoin?

I say "go ahead but don't put more than 5% of your portfolio on it, preferably 1% or less". Also, I'd recommend buying a crypto index fund instead of BTC directly.

Personally, I'm long term bearish. But the last decade has shown that "long term" may be reaaaaally long.
"Easily", not sure that is always easy to do. Is a clever approach to be sure, but to the author's point there could probably be better UX.
Yes, the SVO - Single Versioned Object - architecture is much trickier to implement.
What product do you imagine when you hear Content Management/File M/Knowledge M?
Not spoiling & explaining the product yet but want to see what you imagine when you hear these company descriptions:

1. Content Management Reinvented
2. File Management Reinvented
3. Knowledge Management Reinvented

We're currently deciding on our tag line and want to be aspiring, but mainly concrete.
Reminds me of the Blame! manga.
I agree with you. I am living in a country where FB is banned but some people like me can find some methods to access it. I find FB really boring but enjoy Twitter and Feedly ver much.
BTC incentivizes miners to find cheap power. As renewables become cheaper than non-renewables, this incentivizes innovation in green energy which will benefit the planet long term. The fact the most of the mining is done in China with coal is a geopolitical detail that will change in the coming years.
Yup, huge omission -- this was also on my list but for some reason I put in Gluu but not Ory
According to this [1] interview because it's approx the same size as a cassette tape.

[1] (pdf, dutch) http://docs.mfbfreaks.com/div/De_Ingenieur_Lou_Ottens.pdf
You've got to be joking. No one is going to vaccinate millions of wild bats and pangolins.
Nonsense. We had stable prices before the gambling functions were possible. The gambling functions of the market add nothing of value, and produce no economic output.
Of course it does, to a point.

The (secondary) purpose of the police and criminal justice systems is to ensure that the risk:reward ratio makes it unattractive. It seems to be failing at that all too often.
Went great. Met my wife, learned a new language, made a company with my other friends who quit, got much healthier and am enjoying the environment around me much more than when I was living in SF. I lived in a place that never shut down or had mass casualties like the USA did, and despite living in a city I’ve spent the whole last year out and about. And if I hadn’t gone I probably wouldn’t have been able to do most of what I’ve done because of COVID.
You can always contact various GNU projects directly. The list of projects we had available for 2021 are listed here: https://www.gnu.org/software/soc-projects/ideas-2021.html

You can also try to get in touch with multiple projects via the gnu-soc mailing list on the gnu domain.

If you'd like to contact me directly, you can reach me on my username on the gnu domain.
For a long while I felt oddly bitter that Apache AxKit, a pluggable XML transformation pipeline and web application framework, never enjoyed much attention. I always wanted to use it for serious work but could never justify it owing to lack of mindshare. I was never an XML advocate, but I never hated it either. Ditto for XSLT. AxKit just seemed so elegant and practical, smoothing over some of the problems with XML and XSLT and complementing them in a way that made their promise seem more attainable.

For a startup I vetoed Ruby on Rails in preference to an AxKit-like approach, extending the PoC I had originally cobbled together. In retrospect it was incredibly stupid. Most importantly, I should've just let our dedicated web developer use what he was comfortable with, even though I had strong opinions about the usefulness of that approach. (Object binding had like near zero utility in our particular case.)

Like with ColdFusion is was a hard-earned lesson in understanding that the best tools are the ones that maximize the productivity of your actual and prospective staff, not some hypothetical 10x coder. It's a seemingly obvious principle, but not so obvious and easy in application. It turned out that Ruby on Rails would still be on the upswing for some time afterward, so vetoing it was especially dumb. But ColdFusion, which made sense in context for similar reasons, was doomed to flame out quickly and so even if I teleported my post-RoR-veto self to my first ColdFusion job, I would have made the wrong decision as I had actually successfully advocated moving away from ColdFusion, the accidentally correct decision.
Get a job working at these companies and go out for drinks with the old-timers.
Maybe we should consider getting rid of esp problematic species of bats that are host to the most pathogens. I personally don't see much value in the species. They are like the mosquitos of the mammal world.
Find a New Way to Ski
Are you saying I'm inferior?
Is that unique to Japan though? (Had the impression that US hasn't been much better, and I'd guess Schengen as well at least to some level)
lol... that’s how most status pages are