skysight-inc/HackerNews huggingface dataset:
IMHO it would be good for Rust to become popular niche/specialist language for systems programming.

Currently Rust is not as complete or well defined as Ada/SPARK or MISRA C/C++ combined with commercial analyzers (Astree for example). At the same time Rust is "too sound and rigorous" for mainstream programmers.

Rust advocates are in the losing battle of of forcing mainstream to adopt "it does not compile unless computer says its ready" style. Reliability and soundness comes with a cost.

Most software is not worth of the cost. When you adopt subscription model, fixing bugs is where the money is. If your app works flawlessly without updates, Apple removes it after few years.
I can’t answer everything, but good debugging is a very important design goal of Loom, so the usual debug methods should work the exact same way they do with native threads.
>It sucked for him and he was in a position where it was either do felonious things or be homeless.

Can you elaborate? Cause this seems like extremely poor decision making on his part. If you are in sound mind (i.e not an addict), there is a lot you can do to avoid homelessness and be in a much better situation.
> For example, APL might look like an absolute mess to most people but to the people who know it, it's incredibly easy to read.

But if we use that as a bar ("you have to know it"), then all languages are equally readable.

Pretty much all the popular languages converge on similar syntax an/or grammar.

You can say that it is because that particular set of syntax is the first, or you can say that languages that didn't have similar syntax was abandoned by developers.

There is an equal evidence/lack of evidence for either claim.
The alternative is actually possible and works reasonably well from the browser: https://github.com/coder/code-server
With a good cross platform runtime (new .NET), what's the benefit, assuming no historical bagage, of choosing OCaml over F#?
Data collection. If you want Google to learn more about you, then this is the way to do it.
Excited for this, especially after Mozilla removed my and several other add-ons that simply loaded Google Translate's JavaScript library onto pages in 2019. https://www.jeremiahlee.com/posts/page-translator-is-dead/

Sadly, no support for Svenska (Swedish) to English yet.
Maybe they're trying to establish themselves as a place to leak military secrets.
Hungarian notarion to the rescue /s
You know, there are people who consciously select proprietary software because, for example, they don’t want to deal with complexities of managing it. They simply don’t care. They value their relationship with a supplier and care only that it works.

Such dogmatic views like “proprietary software is immoral” do not help anyone. You have a choice not to use any of it but don’t cross off people who choose otherwise.

Software engineers in vast majority do not live from donations. You are lucky enough to make it from open source? Well, good for you! You are very privileged.
"Sorry, your browser is not currently supported. Please try again using Chrome or Safari."
I generally go by the principle to borrow if I can without effort, otherwise I think a second of the code is in the critical path or the object is megabytes in size. If neither is the case, I clone without shame. The remaining 0.1% gets my attention (Arc, lifetime annotations, refactoring, or whatever is appropriate).

The important part is perspective. Nobody cares if you clone your command line arguments ten times during startup. As Dijkstra said, optimize the 2% of your program that matter, keep the rest simple
Yeah, it's implemented inversely, it seems. To enable collaborative development possibly. The thing is, collaborative development was not even a dream when Eclipse and RDT was first built, so they work well for their respective scenarios.

The nice thing is, Eclipse is extremely portable in terms of configuration and installation, so collaborative development is not a big hassle on the Eclipse side possibly.

Lastly, Eclipse has added "Compile to Container" target, so it's actually pretty usable for modern development in today's world.
I am interested in Rust because of its safeguards around multithreaded programming. This is is my main motivation to learn it.

What I've found good about rust is its modern toolchain and documentation.
The movie is infinitely better if you understand it within its real world context.

The Wachowskis did not want to make another Matrix movie but the studio approached them and said that they would make the movie either way but they would be given full artistic freedom if they agreed. They basically had the choice of doing this themselves or letting the studio turn it into a soulless franchise detached from their own vision.

The movie is mostly an allegory for how the movie was created and why it shouldn't exist. Aside from mindless indulgence the ending is also giving a middle finger to the production company. The philosophy is dull because everything that needed to be said was already said so the only thing left to do is repeat it more blatantly for the audience in the back.

That doesn't mean it's a great movie and you can argue that a movie should be enjoyable without context, but for me knowing this context allowed me to enjoy it through that lens a lot more than I probably would have had I not come into this knowing this.
Tracking carbon emissions is the most inefficient, ineffective and impractical method ever devised for reducing CO2 emissions.

For example, my airline ticket has a line with how many tons of carbon are emitted by my share of the flight. What the heck is anyone going to do with that? But with the carbon tax on jet fuel, the price of the ticket is definitely going to affect behavior. And, of course, taxing fuel is FAR easier than trying to accurately measure the carbon in the jet blast at every stage of a flight.

An efficient, effective, and practical way to do it is to tax the carbon content of fuels, and let the market do its thing with prices.
>"You're trying to draw a comparison with a consumer product with a design flaw."

Not at all. I just do not like to dance around bonfire with tam-tam and being told that this is the one and only way
>Firefox is not supported

Alright then, keep your secrets
JEP 428: Structured Concurrency to Simplify Java Multithreaded Programming
the good thing about minetest is that it runs on a raspberry pi 400 with acceptable framerate, better then minecraft.

there is a minecraft mod in minetest:
https://content.minetest.net/packages/Wuzzy/mineclone2/
Interesting, that advice is exactly the opposite of the common wisdom. You mean overfitting as in aggressively maximizing your crossvalidation scores? How do you decide for which problems that is a good approach and for which a more conservative approach is better?
50M ? Come back when it's 50B.
Mapcreator | REMOTE-OK | Work visa possible | Eindhoven, Netherlands | Senior PHP Developer | Laravel | Salary + Annual Bonus + Insurance

https://mapcreator.io/about-us/careers/

Join our motivated team of internationals based in the heart of Brainport Eindhoven, the Netherlands, and help us scale our customizable online mapping tool Mapcreator.io. We believe that "Anyone can create maps": our aim is to make former cartography-knowledge and time-intense manual labour turn into seconds of work in an intuitive interface for businesses in need of high-quality cartographic output, like Washington Post, CNN or JLL.

What we need from you:

- You have experience with with writing PHP in Laravel, or other PHP frameworks like Symfony or CodeIgniter.

- You're great at Object Oriented Programming & designing and consuming APIs.

- You know how to apply your understanding of SSL/TLS, encryption, ciphers, hashing.

- You bring previous experience with handling & querying relational databases (e.g. PostgreSQL)

Eager to explore an exciting and fast-growing business domain and accept this mapping challenge? Email me your CV: magdalena[at]mapcreator.io
Or, and I find that more likely, they just didn't see the point to spend resources supporting other browsers if they don't have to. In the end, if you want to work at Google, they can probably expect you to use their products.
Yes, the extension is being developed here [1] and the engine[2]/wasm[3] wrapper here.

The models and training pipeline are in the urls your posted and the evaluation of those models are hosted here [4]

[1] https://github.com/mozilla/firefox-translations
[2] https://github.com/browsermt/bergamot-translator
[3] https://github.com/browsermt/bergamot-translator/tree/main/w...
[4] https://github.com/mozilla/firefox-translations-models/tree/...
> From the sound of it, the only "closed" part is configuration, like the endpoints for telemetry API.

I don't want to mention things I'm not 100% sure of but aren't fairly critical components of the editor itself not open source?

For example the Remote Containers feature and certain LSP related functionality are closed source? I remember there being some chat about this on HN where the general sentiment was they are benefiting from open source for a lot of LSP related features but decided not to open source some functionality they've added to their LSP implementation?
I'm not saying that implementation doesn't matter. I'm saying that that there isn't a fundamental implementation difference "async" vs "threads". Threads are used in both cases. It's a different choice of abstractions over the same underlying concepts.

FYI, Rust (the language) has no concept of prioritising workloads; there is no async runtime in the language.

Even with any of the async runtimes, workloads (i.e. tasks doing work) are prioritised by the OS. It's just threads executing code. Async runtimes are primarily concerned with the gaps between work, like waiting for I/O or other events.
There are plenty of articles and reports on the loss of effectiveness of the Google Search and the dying of the self hosted content. There’s also a lot of attempts to transform the web into something else because it has become horrible.

I would not say that Google’s incentives are aligned with the rest of the participants. Google may very well take defensive actions against anything that challenges the status quo.
The overall effect of Arcs being more usable is something that was true before Rust. It is an emergent property of Rust too, because it's still true. The alternative to using Arc or similar used to be validating your own lifetimes manually and inevitably making show-stopping mistakes in C/C++. Now the alternative is machine-checking it and being able to never make mistakes. But Arc is still more ergonomic than either.

If Rust forces you to use Arc where in C/C++ you would normally just be freewheeling your lifetimes, by complaining about your lifetimes, a lot of people are going to see that as "Rust is really annoying and gets in my way, it's making me choose between a tangle of lifetime bounds and explicit Arcs". The truth is that it is teaching you that your normal style would have led to mistakes and you should never have been coding that way. So people go on complaining about being re-taught until their normal style works in Rust, or until they give up. (I don't think that's what you're doing, this is mainly just to say Arcs are not a waste of the language's power, rather an effect of the language's power to know when your freewheeling would be mere lifetime guesstimation and quite possible buggy in C++.)

The author's point is strong though.

> the process of designing APIs is affected by numerous arbitrary language limitations like those we have seen so far.

There's a long way to go in being able to perfectly express all the ways you might want to use lifetimes. Sometimes you come across a situation when a few of these limitations converge on one spot, and you get the author's problem. But equally, the author is trying to write something that has probably never had its lifetime rules described before. Yes, languages with GCs can do it easily. That was also true of lock-free queues & running destructors. GCs have it easy in a ton of different areas around lifetimes. The core complaint here is that Rust does not have a GC and we have had it really easy being able to rely on one & not having to write down exactly the lifetime bounds that could make it work statically. The author is complaining that there are hundreds of compiler issues preventing some of this being expressed... well, yeah, nobody has ever, EVER, tried to write this stuff down before in a machine-readable way, we are slowly covering the untrodden ground, and you might be in an especially untrodden area. I think that's a pretty good excuse for the compiler having issues and some things being not quite expressible, but it's also an important caveat to "fearless concurrency" and I think the post illustrated that well.
I agree, it's very hard to get me to subscribe to anything, but Kagi managed to do it.

I think the business model can be pretty good, if you are just aiming to build a sustainable business and not a billion dollar venture.

It might be useful for Kagi to look into business/family model that 1Password has. If you have the 1Password business account, you also get the family subscription. One could argue it makes sense for company to pay for Kagi since taking away the ads from the result page makes people more focused on the task and boosts productivity.
They provide a full list of questions. I had a look through them and actually found them quite good to prepare for an interview at any company.

No need to go through the interactive part to see these questions.
"Recognize that professional athletes train for at most 3-4 hours a day."

What is your source for this?

E.g., here https://wildfriendsfoods.com/blogs/community/a-typical-train... the author trains 5-6 hours per day and that is intense training.
But on the other hand, whenever I see a shop using Shopify, I feel the site being sluggish and the UX could be better. So it is not all about things being easy or not, but also about creating the best solution.

What that means depends on the business and the employees. If you got no developers, then maybe your only option is to use something that is ready and needs no development. If the shop is your main business and you got good developers, then you might want to do one better, even if it takes time and effort.

So I would not necessarily exclude the possibility, that creating your own might be best for you. You can still make use of third party APIs for things like credit card payment and so on. When you roll your own, you get to decide which parts you outsource and which parts you make yourself. This allows you to decide where you want to be flexible and where you limit yourself to what the limits of a third party software are.
Wanting to avoid running propietary software is a valid reason. It's opinion based, but valid.
> Much of what is routinely used to capture semantics into mainstream C++ libraries is wholly impossible to express in Rust. (C is not even a participant, here.) This is not about template metaprogramming, just ordinary stuff.

Do you have any examples?
This opinion seems to be very sure of things.
I quite like it - it gives me a chance to address areas where I might appear to be a great fit for the job, and set out why they shouldn't be blockers.
I'm starting to see a trend for all these carbon footprint and environmental impact tabs integrated into apps and even bank interfaces. I never use them because it is obviously PR stuff that will never contain any useful, actionable advice. On top of that, won't all of this logging and extra computation actually increase carbon emissions?
Thanks to you for giving the extension a try! This is a very interesting feature, and I'd like to consider it. Would you mind filing an issue in the repo so we could track and discuss it here [1]?

[1] https://github.com/mozilla/firefox-translations/issues
Anima App | Fully remote | Senior Full Stack Engineer

At Anima, our mission is to unleash creativity by enabling software teams to spend more time creating and less time doing menial tasks. With a community of over 500,000 designers and engineers, Anima is the leading design-to-code automation platform.

What challenges you will work on:
- Develop Javascript solutions for various design tools.
- Develop VueJS web application.
- Develop a backend API using Python/Flask, MongoDB, AWS.
- Develop backend microservices.
- Participate in design discussions with product manager and domain experts and assess the feasibility of new products and features.

Apply here: https://jobs.lever.co/AnimaApp/245b61e4-65ea-4388-aa2e-99f4c...
>if we were to program in Hindi, the very shape of our characters would depend of the context...

Eh? What context-dependent-shape-changing are you referring to? Hindi has a very normal alphabet. There are vowels, consonants, and a bunch of special ligatures for some combinations of those that are technically optional and could be done without. Nothing changes according to "context".
I'm pretty sure you can't negotiate a new Tesla price
how do test drives work?
Exactly, I don't get these complains. It's literally for people who want to work at Google. If you don't want to use Google products you're clearly not the target audience.
No, I'm not conflating. Especially when referring to those (like I mentioned) who don't place themselves at the top. That's the opposite of xenophobia, if anything.

I'm saying one in a hundred thousand is too few. The US has more than 3000 people who judge even by phrenology, I'm sure.
We used to get the money back with a pretty reliable mechanical method, stuffing a flattened MacDonald's straw into the machine above the spare change slot and jiggling in and out. You needed a coin for the call but could return and re use it each time or even for the same call.
FWIW I added a "Flaws" section to the end of my resume when I recently revised it. The section opens with, "I'm not an ideal fit for every role or organization", and then briefly covers a couple of less-flattering (but fairly normal) aspects of my character. For example, I'm good with short-term high-stress, but not long-term high-stress.

As I see it, it helps to filter out some of the kinds of places or teams I wouldn't want to work with in the long term, or at all.
This selection effect cannot explain Rust's standing relative to other new languages and neither can it explain why Rust's popularity (as measured by "most loved") increases over time as more and more companies are using it.
Here's the history of Rust's "most loved" percentage going back to 2015

Year - Most Loved Pct. - Rank
2015 - 73.8% - 3
2016 - 79.1% - 1
2017 - 73.1% - 1
2018 - 78.9% - 1
2019 - 83.5% - 1
2020 - 86.1% - 1
2021 - 86.98% - 1
The crypto plan to save our souls
https://archive.ph/ShIN9
I still see VSCode make connections to dc.services.visualstudio.com and az764295.vo.msecnd.net with telemetry and updates disabled.

Github issues relate these connections to extension black lists and extension recommendations based on my workspace rather than specific "telemetry", but I doubt the pipelines at MS care about that distinction.
I did have Problems with ceph many years ago but have many hyper-converged clusters that run ceph without any problems. In the last years I am running rook-managed ceph without any real problems.
I’ve been reading Ray for over a decade and do not find your comment accurate. He has criticised private ANT, he gives good reviews to Garmin competitors, he has been pretty critical of early Vector pedals. His writing style is focused on specific products and things he can measure. You might not like that he doesn’t go off on rants about the industry or write based on info from his comment section, but that doesn’t make him less trustworthy. I’d go so far to say there isn’t a writer in the sports tech space with more integrity than Ray.
For documentation, example code (and also working example) you need to download from itch.io

I hesitated at first, but then I saw it on HN for a 2nd time and actually did it. It's no big deal, I'm just used to see such things on a website (as everyone else too, I guess).

And to the other comment, it seems to be a desktop app only, yes.
I'm so glad we have cloud managed storage like EFS / EBS so we don't have to deal with this stuff...
Your experience with piano notes is interesting, I used to play the guitar 20-ish years ago, and what I find interesting is that even after 20 years of not playing my fingers still can play some compositions even though I don't remember notes anymore. Of course during my time with guitar I would spend hours practicing and at some point I would practice compositions every single day, maybe this is the main reason why I still remember how to play those compositions.
I don't mind JIRA or DevOps or YouTrack or other complex process management tools.

Sure, you might argue that merely having the possibility of making processes complex is what makes them complex, but I think that's making the argument too easy on yourself.

Further these tools - like most huge and complex web apps, are slow, clunky, and buggy. And that obviously deserves criticism. But usually the biggest critcism of Jira is based on that it represents the whole concept of bureaucratic work of various states, transitions, bookeeping and reporting, which to us devs steals time from actual work. It's the scrum feature factory monitoring system.

But having been in such processes without the Jira and ADO type of tooling (e.g. having to message 3 different people and use 3 different home built tracking pages and 3 different emails in order to push a bug through the system), I can tell you having the tooling beats not having it.
I may be an American, but sometimes it doesn't take an expert on the Indian caste system to spot caste discrimination. I have literally heard people say "I don't have to listen to him, he is of a lower caste" or some variation of that sentence. In fact, just yesterday, I was watching an episode of one of Gordon Ramsay's kitchen shows. The chef was Indian and said "he can't tell me what to do, we are the same caste and I am older."