skysight-inc/HackerNews huggingface dataset:
This is off the mark IMO, depending on your definition of esports.

As a founder of a competitive gaming startup, I can tell you that every single game publisher lives and dies on the casual players.

Most of these players have never seen a single pro match in their life, so the notion that popular games were built for PPV is misguided.

What these publishers realized is that giving people a rank makes them more dedicated to playing more and beating others, as well as a sense of progress. sprinkle some repetitiveness, awards, vanity stuff and the hook is even stronger.

It’s probably some intrinsic human behavior (monkey brain stuff), but it works well for their bottom line.

Do I miss the good ol’ Warcraft 3 dota days? Hell yeah. But I remember one times I set up a “community” match against several of my countrymen. My friends and I were demolished. It was obvious they knew something we didn’t.

We only discovered it when we moved to HoN - the meta.

The real fun was always custom maps - we kept playing those into our 30s.

But I do agree that wacky is fun. There’s still competitive mini games in Dota 2 that are super fun and wacky. Missed opportunity if you ask me.
Which is ironic because slack supposedly stands for “searchable log (of) all communications (and) knowledge”

https://www.theverge.com/2016/9/28/13098164/slack-is-an-acro...
I expect Germany to import the smallest amount of natural gas that the government can be confident will prevent economic collapse.

I also expect this quantity to be much lower than it would've been last year, as I also expect significant effort to be put into both improvements (e.g. home insulation) and alternatives (e.g. renewables).
Tor Browser 11.5 - July 7 2022 - Change Log (Text) : https://gitweb.torproject.org/builders/tor-browser-build.git...
> Is this 2018?

Nope [1].

[1] https://fred.stlouisfed.org/series/FEDFUNDS
It can certainly be a helpful feature, but I wonder whether it's really better than good, relevant search results presented in a readable way. For example I'd argue the manually curated infoboxes on Wikipedia are likely more reliable than the algorithmic versions Google shows in their results, especially as it's difficult to fix mistakes in Google's version. Google thinks their own solution is the best one because Google made it and so they circumvent the whole page ranking process. Some queries of course need more than just plain search results (see Semantic Web and related things) but for those most engines don't offer enough control and transparency.

But I'm glad people are trying to build alternatives. I'd love a search engine that ignores sites with antipatterns like required registration for any kind of usage, and this is the first step.
Same here. It did some cool stuff but really bent your mind.

Agree with the other comment that the amount of it at Goog should have a mixed interpretation. Obviously it was useful, but although Google systems were complicated, it still doesn't seem right that it's on the same magnitude as the main system langs.
The Manchu were not Han, but they were Chinese in a broader sense: they've lived for centuries in what is now considered Chinese territory, and by the 19th century they were already assimilated to such an extent that most Manchus spoke Chinese, not Manchu. Today there are still ~10 million Manchus in China, but virtually none speak the language anymore. (Admittedly this is in part because in the early days of Communist China it was not a great idea to show any traces of potentially reactionary Manchu heritage.)
My personal approach, after a decade in such roles - "Everyone owns and is responsible for the Architecture" you're just "Accountable" for it.

Let the team drive Architectural decisions - you just ensure the ship to steered towards the overall business goals.
Not sure about the U.S., but in at least in Russia and Estonia sole proprietorship is a form of business – in a sense that you have to register it, do annual reports (or more often), calculate taxes etc.

In Russia, it is a bit easier than running an LLC, so many entrepreneurs choose to start as an SP. In Estonia I've seen zero sole proprietors – the burden is the same, but LLC taxes are more favourable (0% income tax until you pay out dividiends) and limited liability (which you don't get as an SP).
The difficult problem of managing Java dependencies
I like it. The humor is a bit peculiar. If you like The Hitchhiker's Guide to the Galaxy you'll probably like Discworld.
> "Tere" means "hello" in Estonian. It also feels nice to type.

On qwerty I think that's the case :)
Forgot to disable pinch-zoom on mobile.
I don't personally have any experience with Rust, but I've been using Go for a good two to three years, so my opinion is biased. However, I believe that Go is better suited for general all-purpose programming, whereas Rust is more focused. I would choose Rust if you need to create high-quality, close-to-the-metal software, and use Go for more generic software, filling the role that NodeJS filled for you.
Back navigation capture is another one. You click back and the site has somehow created about 40 pages.
Well, your comparison might also be invalid because we haven't used nuclear power to the scale coal is used. Maybe if there were many nuclear plants we might have seen many disaster?
They delivered an excellent keynote address at this year's Libre Planet conference. I will look into the possibility of locating the link.
In addition to curated domains list, some searches would benefit of limiting display of old results, as usually you might find an answer, but solved in jQuery or older version of framework you are using.
Some people think banning drugs is a bad idea, and that it's better to allow free trade.

A good response to that would be, "yeah, but it was for the Chinese to make their minds up about that, not the British!"

And a good response to that might be: "when you say the Chinese made their minds up, are you talking about a democratic process?"
Technically, assembly can do everything Rust can do, yet that doesn't help to make a decision for a language. Ergonomics matter.
The Art of the Family Photo
I figured I should have given some context to my question on deciding to learn either Rust or Go.

One of the reasons I started thinking which language to pick is when I started diving into web3 development. It seems like there is a trend into either using Go or Rust or both in some of the ecosystems. Think Tendermint, Cosmwasm, Solana, etc. While it makes sense to just learn both languages, I don’t think I have the mental capacity to learn both together quickly. It might work better to learn the one that has the most potential in the long run based on the trend.
Re-Hacking Wordle
Have you heard about Wordle? I hacked it (again) to get a solution in a first try every day.
I highly recommend the Ibis Trilogy by Indian novelist Amitav Ghosh
You can do that sort of thing with SGX very easily indeed. SGX enclaves can generate key material internally that's accessible only to themselves, sealed under the enclave identity, so no TPM is necessary. Actually SGX obsoletes TPMs for some use cases, they're independent technologies.

The way it'd work is you'd just use the public key emitted by the enclave. Grab a Xeon workstation and you can even do such a thing from your desktop.

If you want, you can even prototype such a thing right now. My guess is I could implement that in about an afternoon's worth of work using Conclave:

https://docs.conclave.net/

The thing is, if all it's doing is avoiding key rotation in case of compromise it's a bit hard to justify. Yes, HSM vendors have built a whole business on that, but in practice I'm not sure people are willing to rely on it. Compromised CAs get revoked, right, root store ops don't say "well luckily the HSM means the compromise was only temporary".

Intel did in the past prototype USB keyboards that could do a D/H key exchange and submit encrypted keystrokes. Likewise, apps can do D/H key exchange to tunnel encrypted bitmaps to the GPU where they get composited onto the screen, that's secure video path. Unfortunately there is a long history of them running out of steam before managing to get this stuff deployed in the real world. Seems to be the general PC problem of too many different vendors too coordinate, and PC vendors mostly care about cost reduction rather than new features. Apple is in a better place to do such tech but their whole model is closed-by-default, so they have a secure enclave like tech but only they are allowed to use it. Intel is still the best bet.

Unfortunately the developer experience without something like Conclave is pretty terrible, still. Disclaimer: I started the Conclave project, though I don't work on it anymore.
Do you have any source to support this claim ? AFAIK, France does not rely on Russia for uranium import. France imports uranium mainly (>90%) from Australia, Niger and Kazakhstan [1].

[1] https://www.liberation.fr/checknews/luranium-importe-en-euro...
This is what has always baffled me.

‘I don’t understand something therefore there is no God’ is one of the most common trains of thought that lead to atheism.

Especially and most commonly ‘How could a loving God allow x.’

There isn’t an easy answer to this stuff and I wouldn’t expect there to be. The notion that the universe is easily comprehensible is a framework of thinking that only gets there by discarding everything NOT easily comprehensible and calling the remainder ‘real.’

When people ask why a loving god would allow bad things to happen I want to reply ‘how would you do it better? Design a universe that has meaningful goodness without suffering and evil. Explain how it would work …’
I'm self-publishing "Rust From the Ground Up" which takes this approach: each chapter rewrites a classic Unix utility (head, cat, wc, ...) from the original BSD C source into Rust. I find for systems programming it's easier to understand how things work in C, and then teach the idiomatic way of doing it in Rust. C is pretty easy to follow along in "read-only" mode with some explanations.

https://rftgu.rs/
Ask HN: Experiences with low-code systems?
I'm thinking about introducing a low-code system to handle internal operational processes. I'm thinking things like viewing/handling dead-letter messages, manual intervention decision points, short lived operational tasks that haven't yet/won't be automated.

I'd expect the software engineering team to manage these apps, so the benefit I can see is the quick turnaround on the UI, rather than handing over to non-engineering users for development.

What are people's experiences with these tools? More specifically:

Can you do an effective SDLC with them? e.g. code on a staging environment, push to version control, promote to prod, rollback to old version

Have you actually saved time with them?

Did you avoid introducing unworkable complexity?
GP is also wrong.

At this point it's mostly a meme. Rust is slow to compile. I mean, yeah if you abuse meta programming or monomorphisation.

I've been programming in it, and while I like the language, I'm not on the language community bandwagon. E.g. CoC and it's enforcement (I think it's just pointless grandstanding).
Ever since I switched away from macOS I've noticed how much I miss Alfred (there was a workflow for exactly this), and how much time I waste fighting my browser's notion of relevance in omnibox results.

There really needs to be a high quality cross platform version of a plugin friendly Alt+Space style launcher.
I highly recommend the Ibis Trilogy by Indian novelist Amitav Ghosh about the Opium Wars
My experience:

Google something

The result is linked to a Medium article, which's guarded by a Paywall or Firewall.

Give up on googling.

Find another solution for the problem.

Basically, i have about 80% probability of wasting my time on the internet.
I've done some research (which in this case is a fancy way of saying “opened up Wikipedia” [1]) and looks like in the U.S. you can just run a sole proprietorship without filing anything. Neat!

[1]: https://en.wikipedia.org/wiki/Sole_proprietorship#United_Sta...
I get the sentiment, but like to nuance it a bit.

The compile time story of rust and C++ is comparable, if you use it the same way. If you use deep include hierarchies and no precompiled headers, if you start using template heavy code like boost, or if you do code generation, the C++ compile times will quickly spiral out of control. Rust does not have the include problem, but the specialization/templating idea is shared with C++, and the code generation problem has an equivalent in the macro mechanism as used by e.g. serde.

In theory, you can get comparable compile times from both. Main difference is rust heavily emphasizes a programming strategy that depends on these 2, and it has a heavy cost in compile time. Meanwhile, a lot of the C++ code is still in the 'C-with-classes-and-every-vendor-creates-a-string-class' camp and while the abstraction level is lower, so is the compile time.

For the binary size, C++ can hide a lot of stuff in libraries, while rust compiles it in and duplicates it for each executable. So you pay a higher fixed cost per application. As long as rust has no stable ABI, rust will stay behind at this point. But it gets better optimization opportunities as it can merge the standard library code with yours, and inter library calls are more costly so runs wins there too. Presumably it's early day for a stable ABI in rust, big wins are still made. Long term, I'd personally like to see some ABI stability in the rust world.
Ehh, I think you’ve overestimated the quality of Wikipedia on highly specialist topics (like, say, the kinds of things you’d write academic papers on). It’s not so much that it doesn’t have the content, it’s that the coverage is super uneven; sometimes it has extremely detailed articles on a niche theorem in a particular field, and other times it has the barest stub of information on an entire sub-sub-field of study.
I’m going to offer a different suggestion to the sibling post, and say it’s probably referencing The Mother of all Battles - a phrase that kicked up a lot of fuss in 1991:
https://en.m.wikipedia.org/wiki/Snowclone#The_mother_of_all_...
Cool! Also, I really like your demo gif! Super effective and fun way to go through all the features.
Not a Rust expert but: doesn't Rust support this use-case via Box<dyn SomeTrait> , and leveraging default Trait methods, only overriding the defaults you want to for each type implementing the Trait?
They're cooperating! The maverick is helpful! This is good, this is all very good!

Make the maverick produce APIs and the copy-paster consume them. This way the former can work closely with their users(their teammate) and the latter can't wing it by copy-pasting, since there's no example online. Also the copy-paster can be productive this way with minimal effort, which is their aim.

I've been in a team of 11 where there were was one lead, two mavericks and the rest copy-pasters. Also there was me, disgruntled with my role. The lead and his lackeys produced a component set, and the rest was just writing configurations in JSON and were happy to do so. I wasn't, so I quit. It was a bad case of NIH, but it worked for them.
curl https://raw.githubusercontent.com/mgunyho/tere/master/Cargo.lock | grep source | wc -l
51

How come that such a simple tool has more than half a century of dependencies? This is terrifying.
True, it's not a very smooth experience on non-qwerty keyboards, and the keyboard shortcuts can't be customized yet. But it's high on the todo list!
This is a good example that really helps to explain things. SECCOMP's model of monotonically decreasing permissions seems the most intuitive. However with something like an SSH server I imagine the great fear is a remote exec compromise. pledge() fixes that, since after you call pledge, you can't create new PROT_EXEC memory. Plus OpenBSD enforces a W^X invariant so we can say for certain nothing like a pre-existing executable stack gets grandfathered in. So what they're doing seems reasonable to me. It's an added feature that our Linux polyfill can't offer. But that doesn't mean our pledge() doesn't work as advertised. We simply offer a subset of behaviors. It's not a disjoint paradigm that some people here have made it out to be.
My guess would be Mode X, it was quite popular in games at the DOS/VGA times: https://en.wikipedia.org/wiki/Mode_X
That's not fair to Rust. I think it's feature of community size and genuine interest/innovation in Rust.
And likewise, some uninteresting repos do have published packages.
I'm going to be a dick here, because someone will say it anyways, but how is this different from VIM's directory browser?

Essentially the same UI.

I do think your program does add some features not found in VIM.
I doubt that last year was a good time to go public. At the stock market, the shares would likely have fallen by more than 28%. Plus, you can't sell RSUs right away, and watching them sit there and lose value is a pretty frustrating experience too...
The instructors at my elementary school used to make jokes about how they would all eventually contract bronchitis or TB from breathing in so much chalk dust over the course of their careers.
There are hardly any security issues here.
The app basically exports info that is intended to be public using read-only access.
I was in college when this game was released. I spent countless hours playing with my roommates.

The game holds up to this day for boys under 12. After that, maybe they expect better graphics, but my experience is that interest wanes.
The back button at the end, holy cow. Good job.
I liked that fasterthanlime article a lot too. The main thing it gave me was enough context to get enthusiastic enough about the language to sit down and read through the O'Reilly book¹ (which I thought was excellent).

I'm still very much a Rust beginner, but I've managed to build a couple of useful tiny projects and to hack a feature I wanted into someone else's big 'ol codebase!

¹https://www.oreilly.com/library/view/programming-rust-2nd/97...
You neglected to remember the popup that appears after thirty seconds of inactivity to inform you that new content is available. It appears that certain news websites now have that...
Yes, that's why I prefer apps where possible.

The problem with websites is that they need to be "installed" and they need to get something out of you for their services without the abilities of a proper app.

This cookie->email->adblock->subscribe flow is essentially an installers next->next->next flow.

The cookie dialog is there because they want to track you and EU wants it to be optional for the user and the user is aware of being tracked.

The first notification banner is a HTML one and it is there to make sure that the user doesn't waste the only chance(if the user rejects the browser on, you can't fire it up again) to subscribe to push notifications.

The second notification banner(if you accept the first one) is the actual batter by the browser to make sure that you actually want to subscribe.

The subscribe to the newsletter modal is there because as soon as you close the tab you will forget about that site and they want a way to remind you of their existence.

The adblock detected modal is there because they made that content and that website in hopes to show you an ad and make money of it.

The paywall is there because they want alternative revenue stream since ads are not ideal and they don't want to leave money on the table.

The ad banners everywhere is the money shot and the reason you have have an adblocker.

The modal that appears after scrolling is actually one with good intentions and bad implementation. The idea is that since you consumed the content maybe you would like more from it but most of the time the implementation is bad and its supper annoying. They wanted to show it to you once you finish your thing and you are happy.

The modal that appears when you switch tabs is there in another attempt to establish a way to connect with you. Since you switch a tab, maybe you are done with the site and it's a good time to ask you for your e-mail. If you are annoyed, who cares you are about to close the tab anyway.

The chat popup is there to engage with you if you are super interested in the website.

Rate your experience is there probably because the people who designed this horror show want to read back from you as another signal for their KPI.

The %50 off banner on top is a call for action, they still have a chance to sell you something.

The share buttons are there to remind you that you can share this horror show with your worst enemies.

And the alert you get when you try to close the tab is a last ditch effort to keep you interested. Usually contains %99 off first 10 years free kind of offer.

All this delivered to you through carefully studying the analytics data and doing A/B tests.

The apps have the advantage of sticking around the users sight, thus they don't have to achieve something the first time the user interacts with the app and as a result they can design the app around user satisfaction so that the user opens the app by itself.

Another advantage of the apps is that you get to see the app before going through the installation. You see the screenshots and user reviews on a clean screen before committing.
This is bad advice, and I hope OP ignores it.

Having a degree when you're looking for your first SW role almost certainly will improve your chances.

Not having a degree won't help, particularly when you have no professional experience, but it's not the end of the world.
https://read.first1000.co/p/-stripe

This might be of some interest
For someone writing node apps, Go is a better fit. Go is much simpler than Typescript and almost performs as well as Rust. The reality is most Rust apps written by average Rust programmers do not noticeably outperform Go apps. Getting Rust to outperform Go requires a high level of proficiency in Rust. The effort vs reward definitely favors Go for node type of apps.
I want to tell you that you are incorrect even I upvoted your comment :). There are industries which cannot use rolling distros for whatever reason. I switched jobs at the beginning of this year from a cloud-application development where everything could work on rolling releases and more or less lived on the bleeding edge to developing and provisioning a cloud platform (not everything can work on a public cloud: energy companies, essential telecommunication, many healthcare providers don't want to do that etc). Two worlds so close together physically but totally different philosophies.

We don't use CentOS or Rocky. Our customers pay for RedHat or SLES. But I can see that someone wants RHEL and don't want to pay for the license and don't want to switch to Ubuntu/Debian or OpenSUSE either. I don't understand that, they are not that expensive for what they are but ... I am a software developer by profession, not an accountant. (I even saw industries paying for Windows Servers or HP UX, the prices were pretty eye-watering; the Linux-based options are either cheaper or at the same level as MS Win which for multi-million Euro company is not THAT much and even can pay off when you need to call support.)
Tere from Tallinn here! :-)